>You've totally missed my point.  We were talking about the Linux add-in side,
>and the virt_to_bus macro, which must know what settings the host places into
>the BAR at all times.
>
>I'm not interested in the host driver for the EBSA285 add-in board, since 
>while there is a driver actively using the add-in card, the BARs must remain 
>stable.  I am only concerned about the EBSA285 itself.

Yes, and my point is that it really doesn't matter.  If you put an EBSA-285 in 
a PC then for it to be any use you must have a host driver -- if you don't 
want it to communicate with the host, it might as well be a standalone device.
So, all the time the EBSA is running this driver will be loaded and the PCI 
configuration space will be stable.

p.


unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]

Reply via email to