Date: Tue, 21 Nov 2000 23:23:09 -0700 From: "Justin T. Gibbs" <gibbs@scsiguy.com> To: Warner Losh <imp@village.org> Cc: Mike Smith <msmith@FreeBSD.ORG>, wpaul@FreeBSD.ORG (Bill Paul), freebsd-current@FreeBSD.ORG Subject: Re: Getting at cardbus CIS data from inside drivers Message-ID: <200011220623.eAM6N9473750@aslan.scsiguy.com> In-Reply-To: Your message of "Tue, 21 Nov 2000 21:42:02 MST." <200011220442.VAA39910@harmony.village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>In message <200011220427.eAM4RYF00772@mass.osd.bsdi.com> 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200011220623.eAM6N9473750>