From: Daniel Drake <dsd@gentoo.org>
To: Hamish Marson <hamish@travellingkiwi.com>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: SysKonnect ethernet support for Asus A8VE Deluxe Motherboard?
Date: Wed, 13 Jul 2005 12:51:15 +0100 [thread overview]
Message-ID: <42D50033.9040009@gentoo.org> (raw)
In-Reply-To: <42D3FDF5.4090501@travellingkiwi.com>
Hamish Marson wrote:
> I just installed Gentoo distribution on a new PC for a friend who's
> new to Linux, and discovered that although SysKonnect kindly provide
> full source code drivers for their various products on their website,
> that even the latest released kernel sources (i.e. 2.6.12) still don't
> support the device on this motherboard (Along with a whole host of
> other PCI id's that appear in the syskonnect sources).
Gentoo 2.6.12 kernels provide the skge driver which supports this hardware (I
believe). skge will be included in mainline 2.6.13.
> I've logged a bug on gentoo.org about it, but thought I'd ask, if
> there's any reason that the syskonnect (sk98lin) drivers are so back
> leve in the kernel sources when syskonnect seem to have published the
> drivers for so many more of their devices in source...
The driver updates that syskonnect released are ugly and have been rejected by
the network driver maintainers. skge was written as a response to this.
The very latest sk98lin updates add support for the new Yukon-II PCI-express
adapters. These are not supported by skge -- the Yukon-II is very different
and will eventually be supported by a separate driver. The techniques which
sk98lin uses to support two vastly different network chipsets (yukon/yukon-II)
in the same driver are generally not accepted in the kernel.
Daniel
next prev parent reply other threads:[~2005-07-13 11:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-12 17:29 SysKonnect ethernet support for Asus A8VE Deluxe Motherboard? Hamish Marson
2005-07-13 11:51 ` Daniel Drake [this message]
2005-07-13 11:57 ` Mws
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=42D50033.9040009@gentoo.org \
--to=dsd@gentoo.org \
--cc=hamish@travellingkiwi.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 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.