21 Oct
2008
21 Oct
'08
5:06 p.m.
Dear Kumar Gala,
In message A16160A4-977E-48A0-83D1-FBAB41E1C0B6@kernel.crashing.org you wrote:
If this is desired to be configurable should I introduce a pci_addr_t/ pci_size_t? Coupling to phys_addr_t/phys_size_t doesn't make sense to me because its perfectly reasonable to have a 64-bit PCI device work in a 32-bit system.
I think using pci_addr_t/pci_size_t is the most reasonable suggestion, then (but it may turn into fighting a lot of new warnings about incompatible types for one board or another).
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Am I your nanny? The kernel is there to support user programs, but
it's a _resource_ handler, not a baby feeder. - Linus Torvalds in
Pine.LNX.3.91.960425074845.22041C-100000@linux.cs.Helsinki.FI