[lkml]   [1999]   [Aug]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: New resources - pls, explain :-(
Alan Cox wrote:
> > Remember, readl() and friends are to be used for PCI mapped memory only! If you
> > want to generalize, accesses have to be done through e.g. device->readl().

> readl() is for all busses.

So is this "the standard"? It would be nice if I could make this
assumption in the future.

> If you wnt a PCI bus specific readl it should be called pci_readl(). Perhaps
> thats the root of the problem. Define pci_readl() to be strictly ordered,
> do the right byte swapping and be done with it. Define readl() to change
> no order.

Ah, wouldn't it be nice... Has anyone talked about making a concrete
decision on this issue?

I like rth's suggestion about having bus-specific ioremap() instead of a
generic one; then all readl() etc. would go through that, and do "the
right thing" for that bus. One could add "bigendian_writel()" and
"littleendian_writel()" to satisfy the Linus constraint of making
unusual usage of writel() obvious.



Entropy requires no maintenance.
-- Markoff Chaney

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:53    [W:0.076 / U:4.264 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site