From: tsbogend@alpha.franken.de (Thomas Bogendoerfer)
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH] Register PCI host bridge resource earlier
Date: Sun, 8 Apr 2007 18:10:27 +0200 [thread overview]
Message-ID: <20070408161027.GA8265@alpha.franken.de> (raw)
In-Reply-To: <4619008D.1030803@ru.mvista.com>
On Sun, Apr 08, 2007 at 06:47:41PM +0400, Sergei Shtylyov wrote:
> I'm just not seeing how using insert_resource() vs request_resource()
> for i8259 ports can be relevant here.
request_resource will fail, because the range is already taken by
sni_io_resource, while insert_region inserts the resource into
sni_io_resource. The problem is that init_i8259 doesn't have the right
resource for doing the request_resource, if ioport_resource starting from
0x0000 is already taken by a PCI host bridge. I could probably write a
patch, which adds a parameter to init_i8259 for the resource, where the
request_resource is correct. No idea, whether this is worth the efford.
Opions ?
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessary a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2007-04-08 16:14 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
2007-04-08 16:10 ` Thomas Bogendoerfer [this message]
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=20070408161027.GA8265@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=linux-mips@linux-mips.org \
--cc=sshtylyov@ru.mvista.com \
/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