Re: [PATCH Cobalt 1/1] 64-bit fix

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



>>>>> On Wed, 18 Jan 2006 09:59:54 -0800, Jim Gifford <maillist@xxxxxxxxx> said:

jim> We all need to understand the concerns with the current
jim> method. The only issue I see from Ralf is the following:

jim>     Broken on multiple PCI busses.

Yes, it is an only reason I have ever seen.

jim>     Now the way I understand the issue is the current iomap.c
jim> only handles a single bus, Ralf's point is that if there are
jim> multiple busses this patch may not work properly. Is that a
jim> correct statement Ralf.

I think the current iomap can handle multiple busses.

The traditional way (ioremap + read[bwl] for memory space and in[bwl]
for IO space) can be used on multiple PCI busses if pci resources were
properly configured.  (Though IO space address might be a bit strange
value due to single global mips_io_port_base, it works anyway.)  The
current iomap basically do same jobs.

---
Atsushi Nemoto


[Index of Archives]     [Linux MIPS Home]     [LKML Archive]     [Linux ARM Kernel]     [Linux ARM]     [Linux]     [Git]     [Yosemite News]     [Linux SCSI]     [Linux Hams]

  Powered by Linux