public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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.21] i386 arch subdivision into machine types
Date: Sun, 09 Jun 2002 13:29:49 -0400	[thread overview]
Message-ID: <200206091729.g59HTnv08471@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.

This code is a merger with the Patrick Mochel/Dave Jones setup and cpu split.  
It also includes documentation for all of the created hooks inside arch/i386.

The 165k diff file is at

http://www.hansenpartnership.com/voyager/files/arch-split-2.5.21.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-09 17:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-09 17:29 James Bottomley [this message]
2002-06-09 23:22 ` [PATCH 2.5.21] i386 arch subdivision into machine types Dave Jones

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=200206091729.g59HTnv08471@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox