From: "Michel Dänzer" <michel@daenzer.net>
To: Jeffery von Ronne <jronne@ics.uci.edu>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: two aty128 frame buffers?
Date: 08 Feb 2002 02:34:26 +0100 [thread overview]
Message-ID: <1013132066.23818.3341.camel@pismo> (raw)
In-Reply-To: <20020207171550.L3189@reepicheep.ics.uci.edu>
On Fre, 2002-02-08 at 02:15, Jeffery von Ronne wrote:
>
> On Thu, Feb 07, 2002 at 11:55:59AM -0800, Jeffery von Ronne wrote:
> > FYI, hacking the kernel's aty128fb driver---by removing the return 0;
> > in aty128fb_init's PCI probe loop---I can get an aty128fb for both cards.
> > So far, I've only gotten X's fbdev driver to work with it. I looks closer
> > into why r128/UseFB isn't working some other time.
>
> I can get X's r128_drv/UseFB driver to work with /dev/fb0, but attempting
> to use anything other than X's fbdev with /dev/fb1 sig-11's (it seems to
> be the same no matter what driver /dev/fb0 is using).
The r128 driver lacks Option "fbdev" to choose the framebuffer device to
use, so it will always try to use /dev/fb0. Should be easy to add
looking at the fbdev driver.
> > Second, it seems to have trouble erasing things (e.g. instead of putting
> > up the X background grid when I move a window or even initially.)
>
> This actually happens on both /dev/fb0 and /dev/fb1 when X's fbdev driver
> is used. It seems that it often just forgets to copy its shadow framebuffer
> to the real framebuffer. Setting ShadowFB to false, seemed to fix that.
Bummer, sounds like there's a problem with the mishadow code.
> PS An XF86Config-4 and XFree86.0.log from when I tried to use fbdev on /dev/fb0
> and r128 on /dev/fb1 is at http://www.ics.uci.edu/~jronne/tmp
I guess the segfault is due to both drivers trying to use /dev/fb0, but
keep in mind that vgaHW only works for bus 0 unless you change that in
lnx_video.c.
--
Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer
XFree86 and DRI project member / CS student, Free Software enthusiast
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-02-08 1:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-04 23:46 two aty128 frame buffers? Jeffery von Ronne
2002-02-05 5:21 ` Kaoru Fukui
2002-02-05 6:22 ` Jeffery von Ronne
2002-02-05 9:28 ` Michel Dänzer
2002-02-05 23:16 ` Jeffery von Ronne
2002-02-06 0:08 ` Michel Dänzer
2002-02-06 23:37 ` Jeffery von Ronne
2002-02-07 1:11 ` Michel Dänzer
2002-02-07 5:12 ` Ani Joshi
2002-02-07 18:29 ` Derrik Pates
2002-02-07 19:26 ` Ani Joshi
2002-02-07 22:35 ` Jeffery von Ronne
2002-02-07 20:35 ` Timothy A. Seufert
2002-02-07 19:55 ` Jeffery von Ronne
2002-02-08 1:15 ` Jeffery von Ronne
2002-02-08 1:34 ` Michel Dänzer [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=1013132066.23818.3341.camel@pismo \
--to=michel@daenzer.net \
--cc=jronne@ics.uci.edu \
--cc=linuxppc-dev@lists.linuxppc.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