Date: Thu, 22 Mar 2001 12:41:42 -0600 From: Jonathan Lemon <jlemon@flugsvamp.com> To: Matthew Jacob <mjacob@feral.com> Cc: Jonathan Lemon <jlemon@flugsvamp.com>, scanner@jurai.net, hackers@FreeBSD.ORG Subject: Re: Intel driver doc's Take 2. Message-ID: <20010322124142.V82645@prism.flugsvamp.com> In-Reply-To: <Pine.LNX.4.21.0103221038150.14443-100000@zeppo.feral.com> References: <200103221807.f2MI7K421522@prism.flugsvamp.com> <Pine.LNX.4.21.0103221038150.14443-100000@zeppo.feral.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Mar 22, 2001 at 10:39:58AM -0800, Matthew Jacob wrote:
> >
> > 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.
Sure. If intel would simply say:
" we don't want the driver to support cisco ISL, checksum offloading,
VLAN, or Wake On Lan features "
I suppose I could work with that.
--
Jonathan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010322124142.V82645>