From: Matthew Dharm <mdharm-kernel@one-eyed-alien.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Riley Williams <rhw@MemAlpha.CX>,
Ion Badulescu <ionut@moisil.cs.columbia.edu>,
Shawn Starr <spstarr@sh0n.net>,
linux-kernel@vger.kernel.org
Subject: Re: Gigabit Intel NIC? - Intel Gigabit Ethernet Pro/1000T
Date: Thu, 14 Jun 2001 14:52:21 -0700 [thread overview]
Message-ID: <20010614145221.H17427@one-eyed-alien.net> (raw)
In-Reply-To: <Pine.LNX.4.33.0106142155360.16844-100000@infradead.org> <E15AegA-0005Pt-00@the-village.bc.nu>
In-Reply-To: <E15AegA-0005Pt-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Thu, Jun 14, 2001 at 10:29:26PM +0100
[-- Attachment #1: Type: text/plain, Size: 1574 bytes --]
I know, jumping in at this late-stage is bad form... but if we're talking
about the Intel 82543GC Gigabit MAC, why doesn't someone just use the
FreeBSD if_wx.c driver as a starting point?
It took me a while to find, as they refer to it as the LIVENGOOD instead of
the 82543, but the PCI ProductID values seem to match...
Matt
On Thu, Jun 14, 2001 at 10:29:26PM +0100, Alan Cox wrote:
> > As I see it, if Shawn has permission to freely distribute the specs,
> > he can send a copy to Alan Cox for forwarding to the relevant driver
> > developers. However, if he has to sign an NDA to get them, they're
> > useless...
> >
> > Alan: Am I right in assuming this?
>
> It depends on the NDA. Lots of vendors NDA their docs because they give enough
> info to cloen the hardware, or explain how to fab the chip, or include personal
> details of employees .. and a million other reasons. Many sensible, many quite
> daft.
>
> But in my experience you have a better chance of getting a straight answer out
> of a politician than intels networking folks. Maybe they have reformed
>
> Alan
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Matthew Dharm Home: mdharm-usb@one-eyed-alien.net
Maintainer, Linux USB Mass Storage Driver
It was a new hope.
-- Dust Puppy
User Friendly, 12/25/1998
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-06-14 21:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-11 17:37 softirq bugs in pre2 Andrea Arcangeli
2001-06-11 19:09 ` Linus Torvalds
2001-06-11 19:41 ` Andrea Arcangeli
2001-06-11 20:55 ` Alan Cox
2001-06-11 22:42 ` Gigabit Intel NIC? - Intel Gigabit Ethernet Pro/1000T Shawn Starr
2001-06-12 16:34 ` Alan Cox
2001-06-12 17:20 ` Riley Williams
2001-06-13 10:25 ` Ion Badulescu
2001-06-13 12:40 ` Ralf Baechle
2001-06-13 17:07 ` James Sutherland
2001-06-14 20:59 ` Riley Williams
2001-06-14 21:10 ` Jeff Garzik
2001-06-14 21:14 ` Matthew Jacob
2001-06-14 21:29 ` Alan Cox
2001-06-14 21:52 ` Matthew Dharm [this message]
2001-06-14 21:58 ` Alan Cox
2001-06-14 22:03 ` Matthew Jacob
2001-06-15 2:20 ` Shawn Starr
2001-06-12 2:54 ` softirq bugs in pre2 Andrew Morton
2001-06-11 21:58 ` Pavel Machek
[not found] <200106112259.RAA20183@asooo.flowerfire.com>
2001-06-12 0:39 ` Gigabit Intel NIC? - Intel Gigabit Ethernet Pro/1000T Shawn Starr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010614145221.H17427@one-eyed-alien.net \
--to=mdharm-kernel@one-eyed-alien.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ionut@moisil.cs.columbia.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=rhw@MemAlpha.CX \
--cc=spstarr@sh0n.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).