public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hamish Marson <hamish@travellingkiwi.com>
To: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: SysKonnect ethernet support for Asus A8VE Deluxe Motherboard?
Date: Tue, 12 Jul 2005 18:29:25 +0100	[thread overview]
Message-ID: <42D3FDF5.4090501@travellingkiwi.com> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Hi all.

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).

Although it's easy enough when you fully understand what's hapening,
it a little disconcerting for the newbie user (Which my friend is)
when confronted by booting their new PC & discovereing the Linux
doesn't support their onboard ethernet card...

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...

TIA

Hamish.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFC0/30/3QXwQQkZYwRAjTrAJ4lbhuRyPyRnbw0V9GSZcdhXsTydgCggAwz
uss02KaVi1eVRyQLWdTZ0pI=
=iKsm
-----END PGP SIGNATURE-----


             reply	other threads:[~2005-07-12 20:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-12 17:29 Hamish Marson [this message]
2005-07-13 11:51 ` SysKonnect ethernet support for Asus A8VE Deluxe Motherboard? Daniel Drake
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=42D3FDF5.4090501@travellingkiwi.com \
    --to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox