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 20:58:42 +0400 [thread overview]
Message-ID: <46191F42.6020409@ru.mvista.com> (raw)
In-Reply-To: <20070408161027.GA8265@alpha.franken.de>
Hello.
Thomas Bogendoerfer 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.
No, it shouldn't according to what I'm seeing in the code. Perhaps I'm
missing something and need to actually try executing alike code a see...
> 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'm not at all sure that giving out I/O addresses from 0 to PCI is a great
idea -- is it indeed necessary?
> 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 ?
Did you mean options, opinions, or something else? :-)
> Thomas.
WBR, Sergei
next prev parent reply other threads:[~2007-04-08 16:58 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
2007-04-08 16:58 ` Sergei Shtylyov [this message]
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=46191F42.6020409@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