From: Ben Greear <greearb@candelatech.com>
To: "Gérard Roudier" <groudier@free.fr>
Cc: Manfred Spraul <manfred@colorfullife.com>,
Jeff Garzik <jgarzik@mandrakesoft.com>,
John Fremlin <john@fremlin.de>,
linux-kernel@vger.kernel.org
Subject: Re: [POLITICAL] Re: ECS k7s5a audio sound SiS 735 - 7012
Date: Mon, 05 Nov 2001 12:58:53 -0700 [thread overview]
Message-ID: <3BE6EF7D.40103@candelatech.com> (raw)
In-Reply-To: <20011105175245.X1658-100000@gerard>
Gérard Roudier wrote:
>
> On Sun, 4 Nov 2001, Manfred Spraul wrote:
>
>
>>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.
>>
>
> So you would have preferred, for example, to have dozens of different
> drivers for SYM53C8XX chips and probably as many for Adaptec aic7xxx ones.
> And, probably, one set of different drivers per O/S. And why not one set
> per O/S major version and even per adjacent ones of the same O/S.
>
> Given all the different brands that use similar or compatibles chips, the
> way you want drivers to be developped and maintained looks just
> unrealistic to me.
Jeff has intimate knowledge of the Tulip driver, one of the more complex
drivers that supports a bazillion different cards. And also one of the hardest
to get (and keep) working on all of the devices it seems....
I think he has a very valid point....
Ben
>
> Gérard.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
--
Ben Greear <greearb@candelatech.com> <Ben_Greear AT excite.com>
President of Candela Technologies Inc http://www.candelatech.com
ScryMUD: http://scry.wanfear.com http://scry.wanfear.com/~greear
next prev parent reply other threads:[~2001-11-05 19:59 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
2001-11-05 17:04 ` Gérard Roudier
2001-11-05 19:58 ` Ben Greear [this message]
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=3BE6EF7D.40103@candelatech.com \
--to=greearb@candelatech.com \
--cc=groudier@free.fr \
--cc=jgarzik@mandrakesoft.com \
--cc=john@fremlin.de \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
/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.