From: Vojtech Pavlik <vojtech@suse.cz>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Vojtech Pavlik <vojtech@suse.cz>,
Osamu Tomita <tomita@cinet.co.jp>,
Andrey Panin <pazke@orbita1.ru>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCHSET] PC-9800 architecture (CORE only)
Date: Thu, 24 Oct 2002 12:29:30 +0200 [thread overview]
Message-ID: <20021024122930.E3243@ucw.cz> (raw)
In-Reply-To: <1035456308.8675.36.camel@irongate.swansea.linux.org.uk>; from alan@lxorguk.ukuu.org.uk on Thu, Oct 24, 2002 at 11:45:08AM +0100
On Thu, Oct 24, 2002 at 11:45:08AM +0100, Alan Cox wrote:
> On Thu, 2002-10-24 at 10:09, Vojtech Pavlik wrote:
> > For system resources you simply could allocate 0x00-0x2f and be done
> > without the sparse flag, but if there are any other devices that have
> > overlapping resources, which need separate drivers (IDE, sound, network,
> > ...) then the sparse ioresource flag is indeed needed. Is it so?
>
> Possibly although this is not an entirely unique problem. The other way
> would be (post 2.6) to add a mask. That will also let us properly handle
> the PCI/ISA partial decode for example.
Indeed.
--
Vojtech Pavlik
SuSE Labs
next prev parent reply other threads:[~2002-10-24 10:23 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 [this message]
[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=20021024122930.E3243@ucw.cz \
--to=vojtech@suse.cz \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=pazke@orbita1.ru \
--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