linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sven Luther <sven.luther@wanadoo.fr>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Sven Luther <sven.luther@wanadoo.fr>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: radeonfb on pegasos powerpc motherboard and X endianess problem
Date: Fri, 6 Jun 2003 08:30:40 +0200	[thread overview]
Message-ID: <20030606063040.GC1173@iliana> (raw)
In-Reply-To: <Pine.GSO.4.21.0306060801070.864-100000@vervain.sonytel.be>

On Fri, Jun 06, 2003 at 08:02:23AM +0200, Geert Uytterhoeven wrote:
> On Thu, 5 Jun 2003, Sven Luther wrote:
> > On Thu, Jun 05, 2003 at 02:27:23PM +0200, Benjamin Herrenschmidt wrote:
> > > On Thu, 2003-06-05 at 13:58, Sven Luther wrote:
> > > > Ok, so it must be another kind of problems, but then, my matrox board,
> > > > which Geert (or someone else) said did run on his chrp board, did not
> > > > work well for me.
> 
> Not me, as I don't have any Matrox cards (just S3 and Mach64 GT).
> 
> > > Could be a problem with how the firmware did/did not initialize it
> > 
> > Actually, the OF has a x86 emulator which runs the x86 bios of the
> > graphic card. 
> 
> Aha, so you get VGA text mode on bootup instead of linear graphics?

Yep, Ralph (who wrote the OF or something such) is telling me that the
linear fb apperture doesn't fit in the vga aperture or something such,
and that graphic mode would need vesa 3.x cards.

Friendly,

Sven Luther


-------------------------------------------------------
This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.

  reply	other threads:[~2003-06-06  6:30 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-04 14:54 radeonfb on pegasos powerpc motherboard and X endianess problem Sven Luther
2003-06-04 15:27 ` Michel Dänzer
2003-06-04 15:39   ` Sven Luther
2003-06-05  8:01     ` Benjamin Herrenschmidt
2003-06-05  7:59 ` Benjamin Herrenschmidt
2003-06-05  8:19   ` Sven Luther
2003-06-05 11:42     ` Benjamin Herrenschmidt
2003-06-05 11:58       ` Sven Luther
2003-06-05 12:27         ` Benjamin Herrenschmidt
2003-06-05 13:12           ` Sven Luther
2003-06-06  6:02             ` Geert Uytterhoeven
2003-06-06  6:30               ` Sven Luther [this message]
2003-06-06  6:35                 ` Geert Uytterhoeven
2003-06-06  6:41                   ` Sven Luther
2003-06-10 11:04                     ` Jochen Roth
2003-06-13  9:27                       ` Michel Dänzer
2003-06-13 10:05                         ` Jochen Roth
2003-06-13 16:57                           ` Michel Dänzer
2003-06-06  6:00       ` radeonfb on pegasos powerpc motherboard and " Geert Uytterhoeven
2003-06-06  5:58     ` Geert Uytterhoeven
2003-06-10  9:54   ` Sven Luther
2003-06-10 10:45     ` Sven Luther

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=20030606063040.GC1173@iliana \
    --to=sven.luther@wanadoo.fr \
    --cc=benh@kernel.crashing.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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).