From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Cc: linuxppc-dev@ozlabs.org, linux-fbdev-devel@lists.sourceforge.net
Subject: Re: vga16fb doesn't build on powerpc (vgacon_remap_base)
Date: Wed, 17 Oct 2007 19:01:19 +1000 [thread overview]
Message-ID: <1192611679.11899.160.camel@pasglop> (raw)
In-Reply-To: <Pine.LNX.4.62.0710171047430.29856@pademelon.sonytel.be>
On Wed, 2007-10-17 at 10:49 +0200, Geert Uytterhoeven wrote:
> >
> > So VGACON probably doesn't work either on 32bit. I'm guessing
> arch/powerpc
> > doesn't support PREP.
>
> It's not only useful for PREP, but also for CHRP.
>
> > How best could this be fixed up? Or should I just let the thing
> > be? This is obviously not a new thing, and I don't have any
> hardware
> > that supports this stuff either.
>
> I remember this problem was present when I still had a working
> LongTrail (which
> is CHRP), long before arch/powerpc/ was created.
It's all very old stuff that needs to be dusted. If you have a setup
where legacy VGA is useable, feel free to do a bit of work on that :-)
Ben.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Cc: linuxppc-dev@ozlabs.org, linux-fbdev-devel@lists.sourceforge.net
Subject: Re: vga16fb doesn't build on powerpc (vgacon_remap_base)
Date: Wed, 17 Oct 2007 19:01:19 +1000 [thread overview]
Message-ID: <1192611679.11899.160.camel@pasglop> (raw)
In-Reply-To: <Pine.LNX.4.62.0710171047430.29856@pademelon.sonytel.be>
On Wed, 2007-10-17 at 10:49 +0200, Geert Uytterhoeven wrote:
> >
> > So VGACON probably doesn't work either on 32bit. I'm guessing
> arch/powerpc
> > doesn't support PREP.
>
> It's not only useful for PREP, but also for CHRP.
>
> > How best could this be fixed up? Or should I just let the thing
> > be? This is obviously not a new thing, and I don't have any
> hardware
> > that supports this stuff either.
>
> I remember this problem was present when I still had a working
> LongTrail (which
> is CHRP), long before arch/powerpc/ was created.
It's all very old stuff that needs to be dusted. If you have a setup
where legacy VGA is useable, feel free to do a bit of work on that :-)
Ben.
next prev parent reply other threads:[~2007-10-17 9:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 19:14 vga16fb doesn't build on powerpc (vgacon_remap_base) Joseph Fannin
2007-10-16 21:31 ` Antonino A. Daplas
2007-10-16 21:31 ` [Linux-fbdev-devel] " Antonino A. Daplas
2007-10-17 8:49 ` Geert Uytterhoeven
2007-10-17 8:49 ` Geert Uytterhoeven
2007-10-17 9:01 ` Benjamin Herrenschmidt [this message]
2007-10-17 9:01 ` Benjamin Herrenschmidt
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=1192611679.11899.160.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.