> >In message <[EMAIL PROTECTED]> Mike Smith writes:
> >: No; the CIS parser should know which function it's being called on behalf 
> >: of, and simply elide the tuples that don't relate to that function.
> >
> >This isn't always the right thing to do.  At least in the 16-bit
> >world, there are drivers that want to look at the CIS entries for the
> >other function of the card for various reasons (some of them need to
> >know what kind of modem is present, iirc, to initalize some things in
> >a non-standard way, the example was the NetBSD driver mhz, iirc).  I
> >don't wish to preclude that.
> The ROM BAR is only implemented for function 0 and the ROM
> contains information for all functions of the chip.  So, functions
> greater than 0 must have the flexibility to activate at least the ROM
> BAR on function 0 as well as access that region.

Does the driver need the ROM, or the CIS which may be inside the ROM?

If the driver needs structured information from inside the ROM, this 
falls into the same category as the CIS.

... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also.  But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view.  [Dr. Fritz Todt]
           V I C T O R Y   N O T   V E N G E A N C E

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to