From: ebiederm@xmission.com (Eric W. Biederman)
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i386 arch subdivision into machine types for 2.5.8
Date: 16 Apr 2002 13:30:19 -0600 [thread overview]
Message-ID: <m1r8lfigqc.fsf@frodo.biederman.org> (raw)
In-Reply-To: <200204161555.g3GFtmH03317@localhost.localdomain>
James Bottomley <James.Bottomley@HansenPartnership.com> writes:
> This patch tries to split arch/i386 up into machine specific directories
> (similar to the way arch/arm is done). The idea is to separate out those
> machines which don't look like standard PCs (particularly from an SMP
> standpoint). For the current kernel, all it really does is to get the visws
> stuff into a separate directory (arch/i386/visws). I've also taken some files
> which aren't going to be used by non-pc SMP machines (mainly related to mpbios
> and ioapic) and placed them into arch/i386/generic.
A couple of comments.
- There is no way to build a generic kernel, that just needs
a command line to select the architecture. Something that is important
for installers. Even better would auto detection of the platform from
firmware information, but you can't always do that.
- By just allowing redirecting setup_memory_region you don't allow for
architectures that don't have the 384K memory hole.
- The hooks you add aren't used and are so generic it isn't obvious what
they are supposed do from their names.
- setup_arch.h is nasty. What code it has depends on what it is defined
when it is included. Couldn't 2 headers to this job better? Or better yet
can't you just use function calls?
And of course you don't look at allowing different firmware implementations,
but I'm doing that, so it is covered. :)
Eric
next prev parent reply other threads:[~2002-04-16 19:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-16 15:55 [PATCH] i386 arch subdivision into machine types for 2.5.8 James Bottomley
2002-04-16 16:46 ` Patrick Mochel
2002-04-17 0:55 ` Keith Owens
2002-04-16 19:30 ` Eric W. Biederman [this message]
2002-04-16 20:51 ` James Bottomley
2002-04-16 21:06 ` Dave Jones
2002-04-16 21:44 ` Eric W. Biederman
2002-04-16 23:27 ` James Bottomley
2002-04-16 23:43 ` H. Peter Anvin
2002-04-17 7:00 ` Eric W. Biederman
2002-04-17 16:31 ` James Bottomley
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=m1r8lfigqc.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=James.Bottomley@HansenPartnership.com \
--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