>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. -- Justin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
- Getting at cardbus CIS data from inside drivers Bill Paul
- Re: Getting at cardbus CIS data from inside drivers Warner Losh
- Re: Getting at cardbus CIS data from inside drive... Justin T. Gibbs
- Re: Getting at cardbus CIS data from inside d... Warner Losh
- Re: Getting at cardbus CIS data from insi... Justin T. Gibbs
- Re: Getting at cardbus CIS data from... Warner Losh
- Re: Getting at cardbus CIS data ... Justin T. Gibbs
- Re: Getting at cardbus CIS d... Warner Losh
- Re: Getting at cardbus CIS d... Mike Smith
- Re: Getting at cardbus CIS d... Warner Losh
- Re: Getting at cardbus CIS d... Justin T. Gibbs
- Re: Getting at cardbus CIS d... Mike Smith
- Re: Getting at cardbus CIS d... Warner Losh
- Re: Getting at cardbus CIS d... Mike Smith
- Re: Getting at cardbus CIS data from... Mike Smith
- Re: Getting at cardbus CIS data ... Warner Losh
- Re: Getting at cardbus CIS d... Mike Smith
- Re: Getting at cardbus CIS d... Warner Losh
- Re: Getting at cardbus CIS data from... Jonathan Chen
- Re: Getting at cardbus CIS data from... Warner Losh