From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH] Register PCI host bridge resource earlier
Date: Sun, 08 Apr 2007 18:47:41 +0400 [thread overview]
Message-ID: <4619008D.1030803@ru.mvista.com> (raw)
In-Reply-To: <20070408135244.GA8016@alpha.franken.de>
Hello.
Thomas Bogendoerfer wrote:
>> If you read the comment to insert_resource() you'll see that it works
>>contrarywise, i. e. the inserted resource is made parent of the conflicting
>>ones. I.e. it should't work as you're intending it to.
> why don't you think I haven't testet this ?
> 00000000-03bfffff : PCIT IO
> 00000000-0000001f : dma1
> 00000020-00000021 : pic1
> 00000040-0000005f : timer
> 00000060-0000006f : keyboard
> 00000080-0000008f : dma page reg
> 000000a0-000000a1 : pic2
> 000000c0-000000df : dma2
> 000002f8-000002ff : serial
> 000003c0-000003df : cirrusfb
> 000003f8-000003ff : serial
> 00000c80-00000c83 : EISA device @@@0000
> 00000cf8-00000cfb : PCI config addr
> 00000cfc-00000cff : PCI config data
> 00001000-000010ff : Madge Smart 16/4 EISA Ringnode
> 00001400-000014ff : Madge Smart 16/4 EISA Ringnode
> 00001800-000018ff : Madge Smart 16/4 EISA Ringnode
> 00001c00-00001cff : Madge Smart 16/4 EISA Ringnode
> that's exactly what I wrote.
I'm just not seeing how using insert_resource() vs request_resource() for
i8259 ports can be relevant here.
> Thomas.
WBR, Sergei
next prev parent reply other threads:[~2007-04-08 14:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-08 11:28 [PATCH] Register PCI host bridge resource earlier Thomas Bogendoerfer
2007-04-08 12:20 ` Sergei Shtylyov
2007-04-08 13:12 ` Thomas Bogendoerfer
2007-04-08 13:26 ` Sergei Shtylyov
2007-04-08 13:52 ` Thomas Bogendoerfer
2007-04-08 14:47 ` Sergei Shtylyov [this message]
2007-04-08 16:10 ` Thomas Bogendoerfer
2007-04-08 16:58 ` Sergei Shtylyov
2007-04-08 23:24 ` Thomas Bogendoerfer
2007-04-09 15:11 ` Sergei Shtylyov
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=4619008D.1030803@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=linux-mips@linux-mips.org \
--cc=tsbogend@alpha.franken.de \
/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