mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: jesse.barnes@intel.com
Cc: eiichiro.oiwa.nm@hitachi.com, alan@redhat.com, greg@kroah.com,
	linux-kernel@vger.kernel.org
Subject: Re: pci_fixup_video change blows up on sparc64
Date: Thu, 19 Oct 2006 16:17:49 -0700 (PDT)	[thread overview]
Message-ID: <20061019.161749.08321831.davem@davemloft.net> (raw)
In-Reply-To: <200610191558.06473.jesse.barnes@intel.com>

From: Jesse Barnes <jesse.barnes@intel.com>
Date: Thu, 19 Oct 2006 15:58:05 -0700

> On Thursday, October 19, 2006 3:38 pm, David Miller wrote:
> > > Right, I guess we should have been a bit more careful in making
> > > this code generic.  At least ia64, i386 and x86_64 systems often
> > > have video BIOSes in system memory at 0xc0000 (note that this isn't
> > > in PCI space).
> >
> > Even if it is in system memory there, accessing physical RAM using
> > ioremap() and asm/io.h accessors is not exactly legal.  On sparc64,
> > for example, accessing physical RAM as if it were I/O memory will
> > result in a BUS ERROR and in fact that's how the bootup crashes
> > on sparc64 due to this changeset.
> 
> Good point, we shouldn't use ioremap for the system memory case at all.  
> Should be __va or something I guess.

That's one part, but this won't update all the pci_map_rom() callers
who use asm/io.h accessors on the mapping they get back.  Even
pci_read_rom() in the sysfs code this change was aimed at uses
memcpy_fromio().

Also, as an aside, if we're on a system where the x86 BIOS is unlikely
to be executed anyways, we should always use the PCI ROM bar mapping
to access the video card's ROM.

      reply	other threads:[~2006-10-19 23:17 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-19  6:31 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
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 [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=20061019.161749.08321831.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=alan@redhat.com \
    --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

Powered by JetHome