linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Harald Dunkel <harald.dunkel@t-online.de>
Cc: linux-kernel@vger.kernel.org,
	Nerijus Baliunas <nerijus@users.sourceforge.net>,
	Reuben Farrelly <reuben-lkml@reub.net>,
	dsd@gentoo.org
Subject: Re: why sk98lin driver is not up-to date ?
Date: Sat, 14 Jan 2006 20:57:59 -0500	[thread overview]
Message-ID: <20060115015756.GC32206@tuxdriver.com> (raw)
In-Reply-To: <43C93760.7040502@t-online.de>

On Sat, Jan 14, 2006 at 06:39:44PM +0100, Harald Dunkel wrote:
> Daniel Drake wrote:
> > Nerijus Baliunas wrote:
> > 
> >> Which one is better and what is a difference between them? Which one
> >> will support Marvell Technology Group Ltd. 88E8050 Gigabit Ethernet
> >> Controller
> >> (rev 17)? skge in 2.6.14 does not support it.
> > 
> > 
> > skge supports Yukon
> > sky2 supports Yukon-2
> > 
> > 88E8050 is Yukon-2.
> > 
> 
> Probably you need some testers for sky2. The -mm kernel would be a
> little bit too experimental for me, but it seems to be in -git10.
> Does this mean that it might appear in 2.6.15.1, or do I have to
> wait for 2.6.16?

If you happen to be a Fedora user, sky2 is available in the kernels here:

	http://people.redhat.com/linville/kernels/fedora-netdev/

Hth!

John
-- 
John W. Linville
linville@tuxdriver.com

      parent reply	other threads:[~2006-01-15  1:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-12  9:09 why sk98lin driver is not up-to date ? Eric Belhomme
2006-01-12  9:39 ` Chase Venters
2006-01-12 10:45   ` Reuben Farrelly
2006-01-12 10:58     ` Eric Belhomme
2006-01-12 18:18     ` Nerijus Baliunas
2006-01-13 14:59       ` Daniel Drake
2006-01-14 17:39         ` Harald Dunkel
2006-01-14 17:54           ` Adrian Bunk
2006-01-15  1:57           ` John W. Linville [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=20060115015756.GC32206@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=dsd@gentoo.org \
    --cc=harald.dunkel@t-online.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nerijus@users.sourceforge.net \
    --cc=reuben-lkml@reub.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).