From: Osamu Tomita <tomita@cinet.co.jp>
To: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCHSET] PC-9800 architecture (CORE only)
Date: Tue, 22 Oct 2002 22:36:25 +0900 [thread overview]
Message-ID: <3DB55459.ACC5D447@cinet.co.jp> (raw)
In-Reply-To: 20021021175211.A642@nightmaster.csn.tu-chemnitz.de
Thanks for comment.
Ingo Oeser wrote:
> On Mon, Oct 21, 2002 at 10:49:19PM +0900, Osamu Tomita wrote:
> > This is a part of big patchset for support PC-9800
> > architecture, one of i386 sub architectures.
>
> I'm courious, what the PC-9800 architecture is.
Please visit our web page. We put summary information there.
http://www.kmc.gr.jp/proj/linux98/index-english.html
PC-9800 has support hardware for japanese language, so in 80's
many people use PC-9800 to run "Word processor" applications.
Recently, PC-9800 is mostly used as network client in enterprise,
goverment or school.
> > Core part cleanup has done. (But device drivers are still working.)
> > Many "#if" are killed by using "mach-xxx" framework.
> > If someone pick up this, we are very happy.
> > Comments are always welcome. Please tell me.
>
> This patch is a good spring cleanup of arch/i386. You nicely
> replace many "magic hex values" with defines. That makes it very
> readable for other arch maintainers and even for the i386
> maintainers.
>
> Good work!
Thanks, But other components need much more cleanup, sigh...
Best regards
Osamu Tomita tomita@cinet.co.jp
prev parent reply other threads:[~2002-10-22 13:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-21 13:49 [RFC][PATCHSET] PC-9800 architecture (CORE only) Osamu Tomita
2002-10-22 6:50 ` Andrey Panin
2002-10-22 15:36 ` Osamu Tomita
2002-10-23 12:02 ` Alan Cox
2002-10-23 13:20 ` Osamu Tomita
2002-10-24 9:09 ` Vojtech Pavlik
2002-10-24 10:45 ` Alan Cox
2002-10-24 10:29 ` Vojtech Pavlik
[not found] ` <20021021175211.A642@nightmaster.csn.tu-chemnitz.de>
2002-10-22 13:36 ` Osamu Tomita [this message]
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=3DB55459.ACC5D447@cinet.co.jp \
--to=tomita@cinet.co.jp \
--cc=ingo.oeser@informatik.tu-chemnitz.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