linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: hollis@austin.ibm.com
To: Michel Lanners <mlan@cpu.lu>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: RFC: vesafb
Date: Thu, 24 Jan 2002 16:17:36 -0600	[thread overview]
Message-ID: <20020124221736.GZ510@austin.ibm.com> (raw)
In-Reply-To: <E16Tbiw-00008o-00@piglet.grunz.lu>


On Thu, Jan 24, 2002 at 05:42:46AM +0100, Michel Lanners wrote:
> On  23 Jan, this message from hollis@austin.ibm.com echoed through cyberspace:
> > The attached patch allows vesafb to work on PPC. vesafb does surprisingly
> > little with the BIOS (which I thought was the whole point of VESA). With
> > some ifdef's I'm able to use it as sort of a VGA offb -- the firmware
> > initializes the card, and the driver just uses it and never mucks with it.
>
> Wouldn't this be a good start to use generic PC-type grafic cards on PPC
> machines in general? Or do you lack initialization if nobody (neither
> firmware nor OS) can talk to the card 'natively'?

Yes, we would lack initialization on Power Mac (for example). PReP firmware
does proper setup for a very limited range of chips, which is why this is
useful at all.

-Hollis

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-01-24 22:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-23 19:20 RFC: vesafb hollis
2002-01-24  4:42 ` Michel Lanners
2002-01-24 22:17   ` hollis [this message]
2002-01-25  9:28     ` Gabriel Paubert
2002-01-24  8:52 ` Geert Uytterhoeven
2002-01-24 18:03 ` Tom Rini
2002-01-25  9:22   ` Geert Uytterhoeven
2002-01-25 13:59 ` Leigh Brown

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=20020124221736.GZ510@austin.ibm.com \
    --to=hollis@austin.ibm.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=mlan@cpu.lu \
    /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).