From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: eiichiro.oiwa.nm@hitachi.com
Cc: David Miller <davem@davemloft.net>,
alan@redhat.com, jesse.barnes@intel.com, greg@kroah.com,
linux-kernel@vger.kernel.org
Subject: Re: Re[2]: pci_fixup_video change blows up on sparc64
Date: Thu, 19 Oct 2006 12:20:34 +0100 [thread overview]
Message-ID: <1161256834.17335.17.camel@localhost.localdomain> (raw)
In-Reply-To: <XNM1$9$0$4$$3$3$7$A$9002706U45374cd7@hitachi.com>
Ar Iau, 2006-10-19 am 19:01 +0900, ysgrifennodd
eiichiro.oiwa.nm@hitachi.com:
> It's impossible that multiple VGA cards, which have not the expansion
> ROM, exist in a system regardless of multiple PCI domain system.
Strange. I've worked on several machines where it could.
The 0xC0000 is a physical address only as far as the bridge is concerned
(if the bridge even implements it - not all do). The PCI bus or busses
may not even be the root busses of the system. On such systems you can
happily have multiple PCI root bridges each in their own address space
and each with their own idea of where 0xC0000 maps if anywhere.
next prev parent reply other threads:[~2006-10-19 11:18 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-19 6:31 pci_fixup_video change blows up on sparc64 David Miller
2006-10-19 7:54 ` eiichiro.oiwa.nm
2006-10-19 8:37 ` pci_fixup_video " David Miller
2006-10-19 9:22 ` Alan Cox
2006-10-19 9:25 ` David Miller
2006-10-19 10:49 ` eiichiro.oiwa.nm
2006-10-19 22:32 ` David Miller
2006-10-20 2:41 ` Greg KH
2006-10-20 3:21 ` eiichiro.oiwa.nm
2006-10-20 4:03 ` Greg KH
2006-10-20 4:28 ` eiichiro.oiwa.nm
2006-10-20 14:20 ` eiichiro.oiwa.nm
2006-10-20 19:31 ` David Miller
2006-10-23 6:14 ` eiichiro.oiwa.nm
2006-10-23 8:53 ` David Miller
2006-10-23 18:39 ` Greg KH
2006-10-23 21:02 ` David Miller
2006-10-27 18:05 ` patch pci-fix-pci_fixup_video-as-it-blows-up-on-sparc64.patch added to gregkh-2.6 tree gregkh
2006-10-19 10:01 ` Re[2]: pci_fixup_video change blows up on sparc64 eiichiro.oiwa.nm
2006-10-19 11:20 ` Alan Cox [this message]
2006-10-19 11:38 ` eiichiro.oiwa.nm
2006-10-19 18:03 ` Jesse Barnes
2006-10-19 22:58 ` David Miller
2006-10-20 2:57 ` eiichiro.oiwa.nm
2006-10-20 3:21 ` David Miller
2006-10-20 4:25 ` Re[2]: " eiichiro.oiwa.nm
2006-10-19 16:52 ` Jesse Barnes
2006-10-19 22:38 ` David Miller
2006-10-19 22:58 ` Jesse Barnes
2006-10-19 23:17 ` David Miller
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=1161256834.17335.17.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=alan@redhat.com \
--cc=davem@davemloft.net \
--cc=eiichiro.oiwa.nm@hitachi.com \
--cc=greg@kroah.com \
--cc=jesse.barnes@intel.com \
--cc=linux-kernel@vger.kernel.org \
/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