linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Daniel Drake <dsd@gentoo.org>
Cc: linuxppc-dev@ozlabs.org, dliana@frontiernet.net,
	linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: can't mmap PCI legacy_mem on Powerbook G4
Date: Tue, 13 Jan 2009 08:41:09 +1100	[thread overview]
Message-ID: <1231796469.22571.33.camel@pasglop> (raw)
In-Reply-To: <496B2983.2030601@gentoo.org>

On Mon, 2009-01-12 at 11:29 +0000, Daniel Drake wrote:
> Hi,
> 
> Dave reports a 2.6.28 regression here:
> https://bugs.gentoo.org/show_bug.cgi?id=253149
> 
> X (server v1.5.3) no longer starts, it aborts with a mmap() error.
> 
> 
> This is because X tries to use sysfs pci legacy_mem to map the VGA frame 
> buffer if it is available, and this became available in 2.6.28 for ppc, 
> but the mmap() fails with -ENXIO.

Argh... Can the X folks stop being full of sh*t ? I'll have to have a
look there, fortunately, I'm occasionally one of them :-)

I made the files available on all powerpc, however, not all platforms
support legacy mem access. The PowerBook doesn't, which is why it
returns the error. It would be more complicated to make the file's
existence conditional instead, but I'll loo kat it.

In the meantime, please file an X bug. It shouldn't fallback to /proc or
whatever junk it did with /dev/mem, it should understand that as "the
kernel supports the legacy interfaces, and tells you this machine has no
access to legacy mem" and thus disable all attempts at whacking VGA text
mode.

Ben.

      reply	other threads:[~2009-01-12 21:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-12 11:29 can't mmap PCI legacy_mem on Powerbook G4 Daniel Drake
2009-01-12 21:41 ` Benjamin Herrenschmidt [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=1231796469.22571.33.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=dliana@frontiernet.net \
    --cc=dsd@gentoo.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).