From: Daniel Drake <dsd@gentoo.org>
To: Alistair John Strachan <s0348365@sms.ed.ac.uk>
Cc: Matti Aarnio <matti.aarnio@zmailer.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: 2.6.16, sk98lin out of date
Date: Mon, 13 Feb 2006 19:48:20 +0000 [thread overview]
Message-ID: <43F0E284.2040805@gentoo.org> (raw)
In-Reply-To: <200602131110.34212.s0348365@sms.ed.ac.uk>
Alistair John Strachan wrote:
> Thanks Matti, I wasn't even aware of this driver. Might I suggest the
> "old" driver be marked as such in Linux 2.6.16. I guess I must've
> skipped over it because it begins with "New", and does not contain
> the word "Marvell", which is indicated exclusively by lspci.
I changed the help text of all 3 drivers (sk98lin/skge/sky2) to
point out which ones are/aren't interchangable in 2.6.16. The situation
is a little confusing.
The reason that the sk98lin diff is so huge is because SysKonnect
effectively added support for a substantially different range of cards
(Yukon-2) into the existing driver. This is far from the driver quality
required for the kernel today, so Stephen Hemminger (skge author) wrote
a new driver (sky2) for the Yukon-2 range.
The long term plan is to obsolete and remove sk98lin, but we aren't
ready yet: skge issues pop up every month or two, and sky2 is young.
Stephen's own words:
> I applaud the initiative, but this it is too premature to obsolete
> the existing driver. There may be lots of chip versions and other
> variables that make the existing driver a better choice.
Daniel
next prev parent reply other threads:[~2006-02-13 19:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-13 10:58 2.6.16, sk98lin out of date Alistair John Strachan
2006-02-13 11:05 ` Matti Aarnio
2006-02-13 11:10 ` Alistair John Strachan
2006-02-13 19:48 ` Daniel Drake [this message]
2006-02-13 23:15 ` Alistair John Strachan
2006-02-13 11:06 ` Mws
2006-02-13 19:03 ` Lee Revell
2006-02-13 20:34 ` Willy Tarreau
2006-02-13 20:40 ` Lee Revell
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=43F0E284.2040805@gentoo.org \
--to=dsd@gentoo.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matti.aarnio@zmailer.org \
--cc=netdev@vger.kernel.org \
--cc=s0348365@sms.ed.ac.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.