From owner-freebsd-hackers  Mon Jul 14 22:59:59 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id WAA07754
          for hackers-outgoing; Mon, 14 Jul 1997 22:59:59 -0700 (PDT)
Received: from implode.root.com (implode.root.com [198.145.90.17])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA07749
          for <freebsd-hackers@FreeBSD.ORG>; Mon, 14 Jul 1997 22:59:56 -0700 (PDT)
Received: from implode.root.com (localhost [127.0.0.1])
	by implode.root.com (8.8.5/8.8.5) with ESMTP id XAA14352;
	Mon, 14 Jul 1997 23:00:25 -0700 (PDT)
Message-Id: <199707150600.XAA14352@implode.root.com>
To: Vinay Bannai <vinay@agni.nuko.com>
cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: PCI ethernet driver clarification?? 
In-reply-to: Your message of "Mon, 14 Jul 1997 22:16:29 PDT."
             <199707150516.WAA11817@agni.nuko.com> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Mon, 14 Jul 1997 23:00:25 -0700
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>Thanks for your response. But my question was how do I get hold of the map
>of the internal parameters on the card mapped to the memory? Meaning what
>do each of the bit fields in the fxp_cb_config mean? Does Intel make such
>information public and what is procedure to get this information from
>vendors? 

   The programming manual is available from Intel under an NDA. I was able to
get the manual via a special inside arrangement and didn't have to sign an
NDA...but this special arrangement will probably never happen again.
   The bitfields are described in the device driver where they are
initialized. 

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project