From: "Michael Lothian" <mike@fireburn.co.uk>
To: "Adrian Bunk" <bunk@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: Possibility of adding -march=native to x86
Date: Thu, 25 Oct 2007 23:58:36 +0100 [thread overview]
Message-ID: <fc94aae90710251558o36fc1be7nd20d515f4831a49d@mail.gmail.com> (raw)
In-Reply-To: <20071025222826.GY30533@stusta.de>
> > Half the time it's easier doing a lsmod when booted on a livecd and
> > trying to figure out what options are required from the module names
> > which sometime can be just as tricky.
>
> Sure, distributions already have solved this and you can use their
> work.
I like compiling my own kernel it's just a pain doing it the first
time on a new motherboard or when adding a new piece of hardware
> > Maybe even having a make addnewhardware option to quickly add extra
> > devices to your config file.
>
> Knowing your CPU is much easier to figure out than to figure out the
> BIOS settings of your SATA controller that determine how to access it.
So how do distro's figure out which driver to use? Isn't it a matter
of taking the pci-ids and selecting the correct driver?
> If you do not even know what CPU you have you should really not compile
> your own kernel.
It about ease of use, look at the new core2 architecture, if your gcc
is new enough there is a march=core2 else you use an older flag
Same with the new cell architecture you use cell if your using gcc 4.3
alpha or 930 if it's not that new.
What I'm saying is sometimes GCC or the Kernel is better at making
these decisions or at least make it easier
Mike
next prev parent reply other threads:[~2007-10-25 22:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0EC33A59AA72084CA28B83816B40929F02682BB3@REEDXCLSXM01V03.rbsres01.net>
2007-10-25 18:33 ` Michael Lothian
2007-10-25 18:50 ` Adrian Bunk
2007-10-25 19:09 ` Michael Lothian
2007-10-25 19:17 ` Adrian Bunk
2007-10-25 19:32 ` Michael Lothian
2007-10-25 19:50 ` Adrian Bunk
2007-10-25 20:12 ` Michael Lothian
2007-10-25 20:20 ` Adrian Bunk
2007-10-25 20:20 ` Arjan van de Ven
2007-10-26 10:41 ` Pádraig Brady
2007-10-26 11:45 ` Adrian Bunk
2007-10-25 20:40 ` Gabriel C
2007-10-25 21:30 ` Michael Lothian
2007-10-25 21:46 ` Adrian Bunk
2007-10-25 22:04 ` H. Peter Anvin
2007-10-25 22:42 ` Michael Lothian
2007-10-25 22:58 ` Adrian Bunk
[not found] ` <fc94aae90710251518l1cc129eahf570177e5b516197@mail.gmail.com>
[not found] ` <20071025222826.GY30533@stusta.de>
2007-10-25 22:58 ` Michael Lothian [this message]
2007-10-26 9:16 ` Thomas Gleixner
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=fc94aae90710251558o36fc1be7nd20d515f4831a49d@mail.gmail.com \
--to=mike@fireburn.co.uk \
--cc=bunk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®