From: Jeff Garzik <garzik@gtf.org>
To: Tobias Ringstrom <tori@ringstrom.mine.nu>
Cc: Arnaldo Carvalho de Melo <acme@conectiva.com.br>,
casdcsdc sdfccsdcsd <computrius@yahoo.com>,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jeff Garzik <jgarzik@mandrakesoft.com>
Subject: Re: davicom 9102 and linux 2.5
Date: Sun, 19 May 2002 10:56:14 -0400 [thread overview]
Message-ID: <20020519105614.A10528@gtf.org> (raw)
In-Reply-To: <20020518181821.GA3683@conectiva.com.br> <Pine.LNX.4.44.0205191056070.31419-100000@boris.prodako.se>
On Sun, May 19, 2002 at 11:06:30AM +0200, Tobias Ringstrom wrote:
> Jeff, would you care to enlighten us as to why this was done? To educate
> users that the Davicom chip is really a (bad) tulip clone?
The move was mainly motivated by long term programmer direction, not a
Config.in user interface change (which in hindsight could have been
done better).
Davicom and other tulip-related files are being organized into
drivers/net/tulip, and eventually they will be sharing code from a
tulip_lib.c file or similar.
My long term idea is to have a shared lib providing the core for drivers
which support:
21040/1 chips
21140/2/3 chips
Xircom chips
...and then all other tulip clones will probably be rolled into a
"tulip_clone.c".
i.e. organize the tulip chips into major families, with a central
tulip_lib.c from which they all share code.
Jeff
next prev parent reply other threads:[~2002-05-19 14:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-18 23:58 davicom 9102 and linux 2.5 casdcsdc sdfccsdcsd
2002-05-18 18:18 ` Arnaldo Carvalho de Melo
2002-05-19 9:06 ` Tobias Ringstrom
2002-05-19 14:56 ` Jeff Garzik [this message]
2002-05-19 13:11 ` Zwane Mwaikambo
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=20020519105614.A10528@gtf.org \
--to=garzik@gtf.org \
--cc=acme@conectiva.com.br \
--cc=computrius@yahoo.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tori@ringstrom.mine.nu \
/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