mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: Dave Jones <davej@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] modularization of i386 setup_arch and mem_init in 2.4.18
Date: Fri, 08 Mar 2002 17:54:49 -0500	[thread overview]
Message-ID: <200203082254.g28MsnO08634@localhost.localdomain> (raw)

> As a sidenote (sort of related topic) :
>  An idea being kicked around a little right now is x86 subarch
>  support for 2.5. With so many of the niche x86 spin-offs appearing
>  lately, all fighting for their own piece of various files in
>  arch/i386/kernel/, it may be time to do the same as the ARM folks
> did,
>  and have..

>   arch/i386/generic/
>   arch/i386/numaq/
>   arch/i386/visws
>   arch/i386/voyager/
>   etc..

I'll go for this (although it's probably a 2.5 thing rather than 2.4).  The 
key to making an effective split is to get the abstractions in the generic 
part correct.  I suspect that each of the different arch's has slightly 
different abstraction requirements of the i386 routines, but if we begin the 
split in one arch and pass it around to the others we'll end up with something 
that is roughly correct.

I'll look at doing at least a generic and voyager in the next week (if I get 
time).

James



             reply	other threads:[~2002-03-08 22:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-08 22:54 James Bottomley [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-03-11 16:51 James Bottomley
2002-03-12  3:43 ` James Bottomley
2002-03-08 21:08 Patricia Gaughen
2002-03-08 21:33 ` Dave Jones
2002-03-08 21:34   ` Greg KH
2002-03-09  1:15   ` Josh Fryman
2002-03-09  1:21     ` Dave Jones
2002-03-10  7:42   ` Eric W. Biederman
2002-03-10 13:08     ` Alan Cox
2002-03-11  3:17       ` Eric W. Biederman
2002-03-08 23:48 ` Christer Weinigel
2002-03-09  1:22   ` Christer Weinigel
2002-03-10  7:27   ` Eric W. Biederman

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=200203082254.g28MsnO08634@localhost.localdomain \
    --to=james.bottomley@steeleye.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

all inboxes | Powered by JetHome®