All of lore.kernel.org
 help / color / mirror / Atom feed
From: Osamu Tomita <tomita@cinet.co.jp>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Andrey Panin <pazke@orbita1.ru>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCHSET] PC-9800 architecture (CORE only)
Date: Wed, 23 Oct 2002 22:20:18 +0900	[thread overview]
Message-ID: <3DB6A212.74D592D0@cinet.co.jp> (raw)
In-Reply-To: 1035374538.4033.40.camel@irongate.swansea.linux.org.uk

Alan Cox wrote:
> 
> On Tue, 2002-10-22 at 16:36, Osamu Tomita wrote:
> > IORESOURCE98_SPARSE flag means odd or even only addressing.
> > We modify check_region(), request_region() and release_region().
> > If length parameter has negative value, addressing is sparse.
> > For example,
> >  request_region(0x100, -5, "xxx"); gets 0x100, 0x102 and 0x104.
> 
> Does PC-9800 ever have devices on 0x100/2/4/8 overlapping another device
> on 0x101/103/105 ?
Yes.
Here is io resource definition for PC-9800. (extract from patch)
struct resource standard_io_resources[] = {
        { "pic1", 0x00, 0x02, IORESOURCE_BUSY | IORESOURCE98_SPARSE},
        { "dma", 0x01, 0x2d, IORESOURCE_BUSY | IORESOURCE98_SPARSE },
        { "pic2", 0x08, 0x0a, IORESOURCE_BUSY | IORESOURCE98_SPARSE },
        { "calender clock", 0x20, 0x22, IORESOURCE98_SPARSE },
PIC1 uses 0x00 and 0x02.
DMA controler uses 0x01, 0x03, 0x05,....0x2d.
PIC2 uses 0x08 and 0x0a.
RTC uses 0x20 and 0x22.
They are overlapping.

Regards
Osamu Tomita

  reply	other threads:[~2002-10-23 13:15 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 [this message]
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=3DB6A212.74D592D0@cinet.co.jp \
    --to=tomita@cinet.co.jp \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pazke@orbita1.ru \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.