Date: Tue, 10 Aug 1999 23:21:23 +0100 From: Scott Mitchell <s.mitchell@computer.org> To: Warner Losh <imp@village.org> Cc: obrien@NUXI.com, ade@lovett.com, phk@FreeBSD.ORG, freebsd-xircom@lovett.com, mobile@FreeBSD.ORG Subject: Re: Reading CIS from kernel? Message-ID: <19990810232123.07703@goatsucker.org> In-Reply-To: <199907260027.SAA36187@harmony.village.org>; from Warner Losh on Sun, Jul 25, 1999 at 06:27:09PM -0600 References: <19990717235407.55307@goatsucker.org> <19990714185101.09845@goatsucker.org> <19990713182203.A68393@nuxi.com> <19990710162730.60563@goatsucker.org> <19990713182203.A68393@nuxi.com> <199907140652.AAA53151@harmony.village.org> <19990714185101.09845@goatsucker.org> <199907142219.QAA58852@harmony.village.org> <19990717235407.55307@goatsucker.org> <199907260027.SAA36187@harmony.village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jul 25, 1999 at 06:27:09PM -0600, Warner Losh wrote: > In message <19990717235407.55307@goatsucker.org> Scott Mitchell writes: > : On Wed, Jul 14, 1999 at 04:19:39PM -0600, Warner Losh wrote: > : > Can I get your comments on the following interface? > > : The only thing I'd add right now would be something to 'get me the next > : tuple with id X', maybe > : > : vaddr_t pccard_cis_next_tuple(int slot, int id, vaddr_t start) > : > : where start is the address of the tuple to start searching from. I guess > : you could also use id == -1 as a wildcard to step through all the tuples. > : Pretty much every driver would need something like this, it'd be nice if > : they didn't all have to reinvent it. > > Agreed, so maybe... Where does one get the start address from, > however? I thought the CIS always started at address 0 in attribute memory? Once you've got the first tuple, finding the rest is easy... > : How will the map function deal with the multiple chains of tuples that some > : cards can have (perhaps split between attribute and common memory)? I've > : never actually seen this myself, but I assume it must be used by some > : cards. ISTR multifunction cards can have branches in their tuple chains > : too. Ugh. Which would require imposing more structure on the CIS than > : just a pointer to some mapped memory. But, that's just another layer on > : top of the basic mapping and could easily be added later. > > I've never seen those either. I didn't see any special code in the > current pccard code, but I could have overlooked it. It was my > understanding, which I must admit I haven't checked, that the CIS > could not overflow into the common memory area. I think that the > mindshare book says something to this effect. I'm pretty sure that the dumpcis code in pccardc deals with the various link tuples. Not sure about the common memory thing, but I doubt that not implementing it will break any existing drivers. > : For my needs though, the interface you've presented is fine. Many thanks! > > OK. I'll write a man page and implement the functions. This should > fix the xe driver in -current, no? Should do. Apologies for the lack of feedback over the last couple of weeks BTW. I was moving house, and the computers stayed packed up rather longer than I would have liked. Thank goodness for nationwide local-call ISPs though :-) Cheers, Scott -- =========================================================================== Scott Mitchell | PGP Key ID | "Eagles may soar, but weasels Cambridge, England | 0x54B171B9 | don't get sucked into jet engines" s.mitchell@computer.org | 0xAA775B8B | -- Anon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990810232123.07703>