From: Dave Jones <davej@suse.de>
To: Zwane Mwaikambo <zwane@linux.realnet.co.sz>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Christer Weinigel <wingel@acolyte.hack.org>,
wingel@nano-system.com, jgarzik@mandrakesoft.com,
roy@karlsbakk.net, linux-kernel@vger.kernel.org
Subject: Re: [DRIVER][RFC] SC1200 Watchdog driver
Date: Thu, 21 Feb 2002 15:54:47 +0100 [thread overview]
Message-ID: <20020221155447.C5583@suse.de> (raw)
In-Reply-To: <E16dtPo-0006vd-00@the-village.bc.nu> <Pine.LNX.4.44.0202211619320.11932-100000@netfinity.realnet.co.sz>
In-Reply-To: <Pine.LNX.4.44.0202211619320.11932-100000@netfinity.realnet.co.sz>; from zwane@linux.realnet.co.sz on Thu, Feb 21, 2002 at 04:27:34PM +0200
On Thu, Feb 21, 2002 at 04:27:34PM +0200, Zwane Mwaikambo wrote:
> Thanks Alan and Jeff for the input, i'll cleanup this stuff. Out of
> interest, do we normally take in patches for specialised embedded boxes? I
> see the AMD Elan stuff got in but that only touched one area and was easy
> to integrate. I presume they'd get accepted if the code was broken up into
> seperate modules instead of being overly specialised. For example, the
> CRIS stuff in the Etrax tree (developer.axis.com).
It seems lately there has been a surge of interest in getting
niche x86 clones included in mainline (Voyager, numaq, Elan, etc).
I forget who it was who suggested it, but the idea came up of
using a similar approach to arm's subarchitecture support for x86.
The downsides would probably be a lot of code duplication,
The upside would be hiding away specialised code from the 99% of
people who don't need to see it. The Voyager patch for example
was ~150kb iirc, and was imo still quite intrusive even after
a first round of suggestions. Putting it into arch/x86-32/voyager/
would allow those that do care about it to do whatever they deem
necessary without inflicting dozens of #ifdefs and the likes
on the majority.
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-02-21 14:55 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-20 13:32 SC1200 support? Roy Sigurd Karlsbakk
2002-02-20 15:14 ` Alan Cox
2002-02-21 5:54 ` [DRIVER][RFC] SC1200 Watchdog driver Zwane Mwaikambo
2002-02-21 9:39 ` Jeff Garzik
2002-02-21 9:48 ` Zwane Mwaikambo
2002-02-21 10:15 ` Jeff Garzik
2002-02-21 10:10 ` Zwane Mwaikambo
2002-02-21 11:19 ` Christer Weinigel
2002-02-21 11:59 ` Christer Weinigel
2002-02-21 12:07 ` Zwane Mwaikambo
2002-02-21 13:37 ` Alan Cox
2002-02-21 14:27 ` Zwane Mwaikambo
2002-02-21 14:54 ` Dave Jones [this message]
2002-02-21 15:16 ` Alan Cox
2002-02-21 12:22 ` Jeff Garzik
2002-02-21 12:32 ` Zwane Mwaikambo
2002-02-21 12:46 ` Jeff Garzik
2002-02-21 12:57 ` Christer Weinigel
2002-02-21 13:20 ` Jeff Garzik
2002-02-22 19:57 ` Christer Weinigel
[not found] ` <20020222210107.A6828@fafner.intra.cogenit.fr>
2002-02-22 20:48 ` Christer Weinigel
2002-02-22 22:56 ` Joel Becker
2002-02-25 22:20 ` Randy.Dunlap
2002-02-26 1:22 ` Christer Weinigel
2002-02-26 1:37 ` Christer Weinigel
2002-02-26 1:59 ` Jakob Østergaard
2002-02-26 2:42 ` Alan Cox
2002-02-21 15:53 ` Joel Becker
2002-02-24 17:30 ` Roy Sigurd Karlsbakk
2002-02-25 8:22 ` Zwane Mwaikambo
2002-02-25 21:01 ` Roy Sigurd Karlsbakk
2002-02-21 0:02 ` SC1200 support? Christer Weinigel
2002-02-21 0:27 ` Keith Owens
2002-02-21 6:19 ` Zwane Mwaikambo
2002-02-21 6:35 ` nick
2002-02-21 6:31 ` Zwane Mwaikambo
2002-02-21 12:05 ` Christer Weinigel
2002-02-21 10:56 ` Christer Weinigel
2002-02-21 11:14 ` Keith Owens
2002-02-21 11:24 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2002-02-22 10:15 [DRIVER][RFC] SC1200 Watchdog driver Zwane Mwaikambo
2002-02-22 19:32 ` Roy Sigurd Karlsbakk
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=20020221155447.C5583@suse.de \
--to=davej@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roy@karlsbakk.net \
--cc=wingel@acolyte.hack.org \
--cc=wingel@nano-system.com \
--cc=zwane@linux.realnet.co.sz \
/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.