> >That's what I mean. You call this, and it will remap the CIS (if it > >has been unmapped), walk it for you and pass you a pointer to each CIS > >entry one at a time to the function you specify. > > > >Warner > > I'd rather have a seek/read interface than have a callback. Let's be realistic; the right way to do this is going to be to use the ivar interface; cardbus_get_cistuple(dev, index) just like all the other PCI bus accessor functions. PCI will just need to pass the request through to its parent, assuming its parent is a cardbus bridge, or veto it otherwise. -- ... 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
- Re: Getting at cardbus CIS data from inside drivers Justin T. Gibbs
- 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 inside d... Mike Smith
- Re: Getting at cardbus CIS data from inside d... Warner Losh
- Re: Getting at cardbus CIS data from inside d... Justin T. Gibbs
- Re: Getting at cardbus CIS data from inside d... Mike Smith
- Re: Getting at cardbus CIS data from inside d... Warner Losh
- Re: Getting at cardbus CIS data from inside d... Mike Smith
- Re: Getting at cardbus CIS data from inside drivers Mike Smith
- Re: Getting at cardbus CIS data from inside drive... Warner Losh
- Re: Getting at cardbus CIS data from inside d... Mike Smith
- Re: Getting at cardbus CIS data from inside d... Warner Losh
- Re: Getting at cardbus CIS data from inside drivers Jonathan Chen
- Re: Getting at cardbus CIS data from inside drivers Warner Losh