From: Andrey Panin <pazke@orbita1.ru>
To: Osamu Tomita <tomita@cinet.co.jp>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCHSET] PC-9800 architecture (CORE only)
Date: Tue, 22 Oct 2002 10:50:28 +0400 [thread overview]
Message-ID: <20021022065028.GA304@pazke.ipt> (raw)
In-Reply-To: <20021021224919.A1509@precia.cinet.co.jp>
[-- Attachment #1: Type: text/plain, Size: 1129 bytes --]
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.
> 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.
Ok, you asked for it :))
> if (boot_cpu_data.hard_math && !cpu_has_fpu)
> - setup_irq(13, &irq13);
> +#ifndef CONFIG_PC9800
> + setup_irq(13, &fpu_irq);
> +#else
> + setup_irq(8, &fpu_irq);
> +#endif
> }
May be this should be done this way (with FPU_IRQ_NUMBER hidden in the
arch specific header):
- setup_irq(13, &irq13);
+ setup_irq(FPU_IRQ_NUMBER, &fpu_irq);
> diff -urN linux/arch/i386/kernel/pc9800_debug.c linux98/arch/i386/kernel/pc9800_debug.c
Why this file is not in mach-pc9800 directory ?
And what is IORESOURCE98_SPARSE flag in mach-pc9800/mach_resources.h file ?
--
Andrey Panin | Embedded systems software developer
pazke@orbita1.ru | PGP key: wwwkeys.eu.pgp.net
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-10-22 6:45 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 [this message]
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
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=20021022065028.GA304@pazke.ipt \
--to=pazke@orbita1.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=tomita@cinet.co.jp \
/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