From: Martin Michlmayr <tbm@cyrius.com>
To: linux-mips@linux-mips.org
Subject: Creating infrastructure to allow one kernel for multiple machines
Date: Tue, 27 Feb 2007 14:48:18 +0000 [thread overview]
Message-ID: <20070227144818.GA25883@deprecation.cyrius.com> (raw)
On ARM and PowerPC, you can compile one kernel that will support
multiple machines, as long as they all belong to the same group (e.g.
have a compatible CPU). On ARM, each machine needs to register a
machine id at http://www.arm.linux.org.uk/developer/machines/ and then
the boot loader passes this value to the kernel via a register. On
PowerPC, information about the machine can be found in OF's
device-tree.
On MIPS, you need a separate kernel for each machine, which makes it
hard for distros to support many machines. For example, it would be
nice if you could compile one kernel for vr41xx devices since they
only differ slightly, e.g. in their PCI mappings. I'm therefore
wondering if there are any plans to introduce a scheme on MIPS that
would allow one kernel for several machines.
--
Martin Michlmayr
http://www.cyrius.com/
next reply other threads:[~2007-02-27 14:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-27 14:48 Martin Michlmayr [this message]
2007-03-03 15:03 ` Creating infrastructure to allow one kernel for multiple machines Ralf Baechle
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=20070227144818.GA25883@deprecation.cyrius.com \
--to=tbm@cyrius.com \
--cc=linux-mips@linux-mips.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