From: Sven Luther <sven.luther@wanadoo.fr>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Sven Luther <sven.luther@wanadoo.fr>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: radeonfb on pegasos powerpc motherboard and X endianess problem
Date: Thu, 5 Jun 2003 15:12:53 +0200 [thread overview]
Message-ID: <20030605131253.GA1238@iliana> (raw)
In-Reply-To: <1054816042.1000.2.camel@gaston>
On Thu, Jun 05, 2003 at 02:27:23PM +0200, Benjamin Herrenschmidt wrote:
> On Thu, 2003-06-05 at 13:58, Sven Luther wrote:
> > On Thu, Jun 05, 2003 at 01:42:30PM +0200, Benjamin Herrenschmidt wrote:
> > > On Thu, 2003-06-05 at 10:19, Sven Luther wrote:
> > >
> > > > Err, is that the same devel tree as the one in linuxppc_2_4_devel ?
> > >
> > > No, it's linuxppc_2_4_benh bk, though you can use rsync to extract
> > > just radeonfb from rsync.penguinppc.org::benh-devel.
> >
> > Mmm, i think i am just a bit lost with all the ppc kernel trees ...
> > Which one should i work on.
>
> Yup, 2.4 is a mess ... For a new platform like that, I suggest
> working on linuxppc_2_4 or Marcelo tree directly
Ok.
> > .../...
> >
> > I don't know about the radeon driver exactly but the glint driver i did
> > work on did a mode setup when comming from the VT switch, after having
> > saved the registers it touches for the consoles benefit. It then
> > proceeded to reinitialize the accel pipeline, complete with a sync and
> > all. I guess newer hardware have easier way to do this, and this doesn't
> > speak about the DRI case, but probably all the X driver do it such. When
> > switching back, they restore the registers they have touched, more
> > probably only the mode setting registers, and don't care about the accel
> > regs, since text mode don't touch them.
>
> Which is the problem ;) radeonfb do use the accel engine for text
> rendering, which is why things aren't pretty when coming from X
> (actually, I noticed X tends to fuckup the accel engine when quit
> even while it's not the frontmost console, so there's probably also
> a bug in X)
Maybe a sync problem or somewhat related with DRI ?
> > 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.
>
> 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.
Anyway, i will look at it once i have ported the patches.
Friendly,
Sven Luther
>
> Ben.
-------------------------------------------------------
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.
next prev parent reply other threads:[~2003-06-05 13:13 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 [this message]
2003-06-06 6:02 ` Geert Uytterhoeven
2003-06-06 6:30 ` Sven Luther
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=20030605131253.GA1238@iliana \
--to=sven.luther@wanadoo.fr \
--cc=benh@kernel.crashing.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).