From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: linux-kernel@vger.kernel.org
Cc: davej@suse.de, James.Bottomley@HansenPartnership.com
Subject: [PATCH 2.5.24] i386 arch subdivision into machine types
Date: Sat, 22 Jun 2002 11:53:35 -0400 [thread overview]
Message-ID: <200206221553.g5MFrZF03680@localhost.localdomain> (raw)
This code rearranges the arch/i386 directory structure to allow for sliding
additional non-pc hardware in here in an easily separable (and thus easily
maintainable) fashion. The idea is that all the code for the particular
problem hardware should be able to go in a separate directory with only
additional build options in config.in.
The current patch really only pulls out the visws code from the core and
places it into a separate directory (sort of a simple example case). It also
creates a generic directory (for standard x86 PCs) with all of the hooks
documented.
The current patch moves mpparse.c back into arch/i386/kernel with it's own
subordinate config option and upports to 2.5.24.
http://www.hansenpartnership.com/voyager/files/arch-split-2.5.24.diff
There's also a bitkeeper repository with all this in at
http://linux-voyager.bkbits.net/arch-split-2.5
James Bottomley
reply other threads:[~2002-06-22 15:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200206221553.g5MFrZF03680@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=davej@suse.de \
--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 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.