>The problem with a read/seek interface is that you are consuming a >resource (a memory window) while you are using it. Yes, but this is the client's resource to use anyway. >You'd need an >open/close on top of that as well to properly map things in to start >and then free them at the end. Plus you might want a ftell sort of >interface as well. I'll likely punt on the seek/ftell part. I think it was Jonathan that mentioned that at times when you read one entry you want to skip to another entry that it may reference. I don't have the spec to know, but that is why I thought the flexibility of having a seeking interface might be necessary. -- 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