From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Gigabyte Quad Royal SLI Agere Gigabit Network Chip Not Supported Under 2.6.x?
Date: Mon, 3 Jul 2006 10:21:50 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0607031021480.20402@p34.internal.lan> (raw)
In-Reply-To: <1151936084.3108.34.camel@laptopd505.fenrus.org>
http://svn.sliepen.eu.org/et131x/trunk/
http://webpages.charter.net/decibelshelp/et131x.html
http://dadams1969.googlepages.com/et131x_20060131_v1-2-2.tar.gz
On Mon, 3 Jul 2006, Arjan van de Ven wrote:
> On Mon, 2006-07-03 at 10:09 -0400, Justin Piszcz wrote:
>> Note: I do not have this motherboard currently, I am just looking at
>> possible motherboards with many PCI-e slots, this one would fit nicely,
>> however, it does not have a driver built-in to the kernel for the first
>> gigabit nic.
>>
>> README: Release Notes for ET1310 Linux Driver
>> v1.2.2 -------------------------------------------------------------
>>
>> The ET1310 Linux Driver v1.2.2 is a driver which supports the ET1310
>> Customer Evaluation Board (Revision 1.1) This driver is subject to change
>> with subsequent releases.
>
>
> can you post a URL to the full driver source? I've not seen this driver
> yet, and chances are others haven't either...
>
>
> -
> 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/
>
prev parent reply other threads:[~2006-07-03 14:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-03 14:09 Justin Piszcz
2006-07-03 14:14 ` Arjan van de Ven
2006-07-03 14:20 ` Jeff Garzik
2006-07-03 14:21 ` Justin Piszcz [this message]
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=Pine.LNX.4.64.0607031021480.20402@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®