> > I hate to say it, but anything that gets axed out of the manual basically > means that those features of the chip will not be used. I honestly don't > think that the marketer you talked to really understands this; I can't > for the life of me see how anything less than the programming manual > will be sufficient. You should be allowed the whole manual, but some list of what can be made visible should not be all that hard to do- certainly after you've looked over the manual and you work with Intel to figure what is and isn't releasable. I have a personal contact with a manager in the LAN group at Intel who I'm visiting this weekend. We'll see if he has some influence in this matter. -matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
- old business (was Re: Intel dr... Matthew Jacob
- Re: old business (was Re: Inte... Dennis
- Re: old business (was Re: Inte... Matthew Jacob
- Re: Intel driver doc's Take 2. David O'Brien
- Re: Intel driver doc's Take 2. Peter Wemm
- Re: Intel driver doc's Take 2. Wes Peters
- Re: Intel driver doc's Take 2. Matthew Jacob
- Re: Intel driver doc's Take 2. Matthew Jacob
- Re: Intel driver doc's Take 2. Matthew Jacob
- Re: Intel driver doc's Take 2. Jonathan Lemon
- Re: Intel driver doc's Take 2. Matthew Jacob
- Re: Intel driver doc's Take 2. Jonathan Lemon
- Re: Intel driver doc's Take 2. Sergey Babkin
- Re: Intel driver doc's Take 2. Jonathan Lemon
- Re: Intel driver doc's Take 2. Olibert Obdachlos
- Re: Intel driver doc's Take 2. Jonathan Lemon
- Re: Intel driver doc's Take 2. Olibert Obdachlos
- RE: Intel driver doc's Take 2. Koster, K.J.
- Re: Intel driver doc's Take 2. David O'Brien
- Re: Intel driver doc's Take 2. Dennis
- Re: Intel driver doc's Take 2. Bruce A. Mah