|To:||Geert Uytterhoeven <firstname.lastname@example.org>|
|Subject:||Re: [PATCH] Change PCI host bridge setup/resources|
|From:||Sergei Shtylyov <email@example.com>|
|Date:||Mon, 09 Apr 2007 18:44:39 +0400|
|Cc:||Thomas Bogendoerfer <firstname.lastname@example.org>, email@example.com|
|Organization:||MontaVista Software Inc.|
|References:||<20070408113457.GB7553@alpha.franken.de> <4619245F.firstname.lastname@example.org> <20070408230710.GA9092@alpha.franken.de> <Pine.LNX.4.64.0704091028010.1807@anakin>|
|User-agent:||Mozilla/5.0 (X11; U; Linux i686; rv:1.7.2) Gecko/20040803|
Hello. Geert Uytterhoeven wrote:
This is certainly *not* a PCI or [E]ISA resource. It's decoded by the *host* bridge.
so ? It's an IO address no device should use, because it won't work. Therefore mark it busy. That's all the code does.
Yep, it's transparently decoded ISA (which is behind PCI) to control the PCI bus. Just traditional PC legacy hacks :-)
Rubbish. I was complaining about the PCI config/data ports at 0xCF8/0xCFC which are by no means part of either [E]ISA or PCI. They're decoded by the host to PCI bridge.
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||Re: [PATCH] Change PCI host bridge setup/resources, Sergei Shtylyov|
|Next by Date:||Re: [PATCH] Register PCI host bridge resource earlier, Sergei Shtylyov|
|Previous by Thread:||Re: [PATCH] Change PCI host bridge setup/resources, Geert Uytterhoeven|
|Next by Thread:||Re: [PATCH] Change PCI host bridge setup/resources, Sergei Shtylyov|
|Indexes:||[Date] [Thread] [Top] [All Lists]|