All of lore.kernel.org
 help / color / mirror / Atom feed
From: Manfred Spraul <manfred@colorfullife.com>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: "Gérard Roudier" <groudier@free.fr>,
	"John Fremlin" <john@fremlin.de>,
	linux-kernel@vger.kernel.org
Subject: Re: [POLITICAL] Re: ECS k7s5a audio sound SiS 735 - 7012
Date: Sun, 04 Nov 2001 23:52:09 +0100	[thread overview]
Message-ID: <3BE5C699.4FF8322B@colorfullife.com> (raw)
In-Reply-To: <20011104180055.F2312-100000@gerard> <3BE5C136.2259F283@mandrakesoft.com>

Jeff Garzik wrote:
> 
> Gérard Roudier wrote:
> > different from Tekram adapters. Btw, my Netgear FA311 board is not handled
> > by the sis driver of linux-2.2.20 and my little finger tells me that it
> > could be so given a few code addition.
> 
> Unless you have a really strange board I haven't seen, NetGear FA311 are
> the natsemi DP83815/6 chips, handling by either "natsemi" or "fa311"
> drivers, not "sis900" driver...
>
sis900 and natsemi are similar, probably both could be handled with one
driver.
e.g. freebsd has one driver for natsemi and sis900.

But I'm not a big fan of huge drivers that handle multiple 99%
compatible controllers and always break for one controller if you try to
fix another controller, so I won't try to merge them.

--
	Manfred

  reply	other threads:[~2001-11-04 22:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-04 19:29 [POLITICAL] Re: ECS k7s5a audio sound SiS 735 - 7012 Manfred Spraul
2001-11-04 17:28 ` Gérard Roudier
2001-11-04 22:29   ` Jeff Garzik
2001-11-04 22:52     ` Manfred Spraul [this message]
2001-11-05 17:04       ` Gérard Roudier
2001-11-05 19:58         ` Ben Greear
2001-11-05 18:11           ` Gérard Roudier
2001-11-05 22:40         ` Alan Cox
     [not found] <20011103055053.J761-100000@gerard>
2001-11-03 12:59 ` Alan Cox
2001-11-04 18:38   ` [POLITICAL] " John Fremlin
2001-11-04 19:23     ` Alan Cox

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=3BE5C699.4FF8322B@colorfullife.com \
    --to=manfred@colorfullife.com \
    --cc=groudier@free.fr \
    --cc=jgarzik@mandrakesoft.com \
    --cc=john@fremlin.de \
    --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.