From owner-freebsd-hackers Thu Mar 22 10:40: 7 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id E15D537B719 for ; Thu, 22 Mar 2001 10:40:04 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id KAA15366; Thu, 22 Mar 2001 10:40:03 -0800 Date: Thu, 22 Mar 2001 10:39:58 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Jonathan Lemon Cc: scanner@jurai.net, hackers@FreeBSD.ORG Subject: Re: Intel driver doc's Take 2. In-Reply-To: <200103221807.f2MI7K421522@prism.flugsvamp.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > 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 majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message