From: Reuben Farrelly <reuben-lkml@reub.net>
To: Chase Venters <chase.venters@clientec.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: why sk98lin driver is not up-to date ?
Date: Thu, 12 Jan 2006 23:45:53 +1300 [thread overview]
Message-ID: <43C63361.103@reub.net> (raw)
In-Reply-To: <200601120339.17071.chase.venters@clientec.com>
On 12/01/2006 10:39 p.m., Chase Venters wrote:
> On Thursday 12 January 2006 03:09, Eric Belhomme wrote:
>> So this archive is more recent than sources included in stock kernel, but
>> older than 2.6.14 kernel, so I wonder why this revision of sk98lin is not
>> included in kernel ?
>
> Eric,
> IIRC, the SysKonnect official GPL driver attempts to support two different
> chipsets / possibly has other coding issues as well. I think this is the
> reason SysKonnect's driver is still out of tree. I think some netdev folks
> might be working on newer drivers, but I haven't been keeping track honestly.
Yes, look at the skge driver in 2.6.15 and the upcoming sky2 in 2.6.16.
I think you'll find those drivers much better than sk98lin and support most if
not all of the cards that the sk98lin driver works with. Certainly those two
replacement drivers are better maintained.
My understanding is that is that sk98lin is in the process of being deprecated.
reuben
next prev parent reply other threads:[~2006-01-12 10:45 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 [this message]
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
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=43C63361.103@reub.net \
--to=reuben-lkml@reub.net \
--cc=chase.venters@clientec.com \
--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;
as well as URLs for NNTP newsgroup(s).