Philip Blundell writes:
> Well, as I mentioned before, drivers routinely cache BAR and other
> configuration values. So the PnP OS must either perform the appropriate setup
> prior to loading the driver, or provide some mechanism for the driver to keep
> abreast of what's happening.
>
> The fact that the card in question is running Linux isn't really significant
> at all.
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.
_____
|_____| ------------------------------------------------- ---+---+-
| | Russell King [EMAIL PROTECTED] --- ---
| | | | http://www.arm.linux.org.uk/~rmk/armlinux.html / / |
| +-+-+ --- -+-
/ | THE developer of ARM Linux |+| /|\
/ | | | --- |
+-+-+ ------------------------------------------------- /\\\ |
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
