From: R.E.Wolff@BitWizard.nl (Rogier Wolff)
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, Tim Wright <timw@splhi.com>,
Kai Henningsen <kaih@khms.westfalen.de>,
linux-kernel@vger.kernel.org
Subject: Re: About Celeron processor memory barrier problem
Date: Tue, 26 Dec 2000 23:31:55 +0100 (MET) [thread overview]
Message-ID: <200012262231.XAA15382@cave.bitwizard.nl> (raw)
In-Reply-To: <Pine.LNX.4.10.10012261012330.8122-100000@penguin.transmeta.com> from Linus Torvalds at "Dec 26, 2000 10:14:03 am"
Linus Torvalds wrote:
> > If we do that I'd rather see a make autoconfig that does the lot from
> > proc/pci etc 8)
>
> Good point. No point in adding a new config option, we should just have a
> new configurator instead. Of course, it can't handle many of the
> questions, so it would still have to fall back on asking.
>
> That _would_ be a nice addition eventually. It's a bigger project than the
> one I envisioned, though.
The way I interpreted Alan is that
make autoconfig
would spit out the default config, modified for the current setup, as
far as possible. So "my PCI devices" would be configured into the
kernel automatically (the way Linus likes it ;-). Similarly the
"complicated" CPU selection would be "don't touch unless you really
know what you're doing: autoconfig analized your cpuinfo".
It would at least NOT INPACT anything in the current setup.
Roger.
--
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2137555 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
* There are old pilots, and there are bold pilots.
* There are also old, bald pilots.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-26 23:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-23 9:24 About Celeron processor memory barrier problem michael chen
2000-12-23 11:04 ` Erik Mouw
2000-12-23 17:21 ` Linus Torvalds
2000-12-23 23:27 ` Erik Mouw
2000-12-24 9:45 ` Jeffrey Rose
2000-12-24 11:48 ` Erik Mouw
2000-12-23 23:36 ` Matthias Schniedermeyer
2000-12-24 9:36 ` Kai Henningsen
2000-12-24 20:50 ` Tim Wright
2000-12-24 22:25 ` Linus Torvalds
2000-12-25 2:38 ` Tim Wright
2000-12-25 7:19 ` The Doctor What
2000-12-26 1:40 ` Alan Cox
2000-12-26 18:14 ` Linus Torvalds
2000-12-26 22:31 ` Rogier Wolff [this message]
2001-01-01 11:55 ` Riley Williams
2000-12-25 11:12 ` Kai Henningsen
2000-12-25 19:37 ` Ian Stirling
2000-12-26 20:38 ` Pavel Machek
2000-12-26 0:15 ` Albert D. Cahalan
2000-12-23 22:34 ` Pavel Machek
[not found] <fa.gm0b5nv.1h2mope@ifi.uio.no>
[not found] ` <fa.n7l96dv.2nah0l@ifi.uio.no>
2000-12-26 19:24 ` Giacomo Catenazzi
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=200012262231.XAA15382@cave.bitwizard.nl \
--to=r.e.wolff@bitwizard.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=kaih@khms.westfalen.de \
--cc=linux-kernel@vger.kernel.org \
--cc=timw@splhi.com \
--cc=torvalds@transmeta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox