public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: eiichiro.oiwa.nm@hitachi.com
To: "Jesse Barnes" <jesse.barnes@intel.com>
Cc: "Bjorn Helgaas" <bjorn.helgaas@hp.com>, <akpm@osdl.org>,
	<tony.luck@intel.com>, <greg@kroah.com>,
	"Alan Cox" <alan@lxorguk.ukuu.org.uk>,
	<linux-ia64@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.6.18] PCI: Turn pci_fixup_video into generic for embedded VGA
Date: Mon, 19 Mar 2007 12:12:55 +0900	[thread overview]
Message-ID: <XNM1$9$0$4$$3$3$7$A$9002870U45fdffb3@hitachi.com> (raw)
In-Reply-To: 200703161142.39854.jesse.barnes@intel.com

>On Friday, March 16, 2007 10:20 am Bjorn Helgaas wrote:
>> Are there really ia64 machines where we need to use the option ROM
>> copy at 0xC0000?  If so, is this documented somewhere?  I couldn't
>> find any mention in DIG64, EFI, or internal HP architecture specs.
>>
>> If we do need to use it, ia64 has a bit of a problem because on some
>> boxes, the 0xC0000 memory supports only cacheable access, the VGA
>> frame buffer at 0xA0000 supports only uncacheable access, and the
>> usual ia64 ioremap mapping is a 16MB page that covers both.
>
>Apparently Eichiro's machine needs it, and of course there are i386 and 
>x86_64 machines that need it to, so it makes sense that it be generic.
>
>Jesse
>

Yes, our machine need it.

>> Are there really ia64 machines where we need to use the option ROM
>> copy at 0xC0000?  If so, is this documented somewhere?  I couldn't
>> find any mention in DIG64, EFI, or internal HP architecture specs.

"System Abstraction Layer Specification" describes it in section 2.6.

Eiichiro


      reply	other threads:[~2007-03-19  3:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-28  4:55 [PATCH 2.6.18] PCI: Turn pci_fixup_video into generic for embedded VGA eiichiro.oiwa.nm
2006-09-28 11:18 ` Alan Cox
2006-09-28 16:36 ` Jesse Barnes
2006-09-29  2:33   ` eiichiro.oiwa.nm
2007-03-16 17:20   ` Bjorn Helgaas
2007-03-16 18:42     ` Jesse Barnes
2007-03-19  3:12       ` eiichiro.oiwa.nm [this message]

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='XNM1$9$0$4$$3$3$7$A$9002870U45fdffb3@hitachi.com' \
    --to=eiichiro.oiwa.nm@hitachi.com \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bjorn.helgaas@hp.com \
    --cc=greg@kroah.com \
    --cc=jesse.barnes@intel.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tony.luck@intel.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