On Mon, 25 Dec 2000, Alan Cox wrote: > > One thing we _could_ potentially do is to simplify the CPU selection a > > bit, and make it a two-stage process. Basically have a > > > > bool "Optimize for current CPU" CONFIG_CPU_CURRENT > > > > which most people who just want to get the best kernel would use. Less > > confusion that way. > > 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. Linus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
- Re: About Celeron processor memory barrier pr... Erik Mouw
- Re: About Celeron processor memory barrie... Jeffrey Rose
- Re: About Celeron processor memory ba... Erik Mouw
- Re: About Celeron processor memory barrier pr... Matthias Schniedermeyer
- Re: About Celeron processor memory barrier pr... Kai Henningsen
- Re: About Celeron processor memory barrie... Tim Wright
- Re: About Celeron processor memory ba... Linus Torvalds
- Re: About Celeron processor memor... Tim Wright
- Re: About Celeron processor memor... The Doctor What
- Re: About Celeron processor memor... Alan Cox
- Re: About Celeron processor ... Linus Torvalds
- Re: About Celeron proces... Rogier Wolff
- Re: About Celeron processor memor... Riley Williams
- Re: About Celeron processor memory ba... Kai Henningsen
- Re: About Celeron processor memor... Ian Stirling
- Re: About Celeron processor memor... Pavel Machek
- Re: About Celeron processor memory ba... Albert D. Cahalan
- Re: About Celeron processor memory barrier problem Pavel Machek
- Re: About Celeron processor memory barrier problem Giacomo Catenazzi