From: Michel Dänzer <michdaen@iiic.ethz.ch>
To: Michael Schmitz <schmitz@opal.biophys.uni-duesseldorf.de>
Cc: "Kevin B. Hendricks" <khendricks@ivey.uwo.ca>,
Kostas Gewrgiou <gewrgiou@imbc.gr>,
linuxppc-dev@lists.linuxppc.org, Kevin Puetz <puetzk@iastate.edu>
Subject: Re: patch to get latest XFree 4.0 snapshot (xf3918) to workonppcwithr128
Date: Mon, 13 Mar 2000 14:55:12 +0100 [thread overview]
Message-ID: <38CCF340.363C70A7@iiic.ethz.ch> (raw)
In-Reply-To: Pine.LNX.4.10.10003131356430.32105-100000@opal.biophys.uni-duesseldorf.de
Michael Schmitz wrote:
>
> > > A clean patch against XFree 4.0 would help to decide if I just missed some
> > > more cache flush magic or if it's a real atydb bug.
> >
> > I suspect it is the latter as Kevin Puetz has reported a similar problem with
> > Mach64 on the debian-powerpc list. The server locked the machine in
> > fbdevHWModeInit(). If you could rebuild libfbdevhw.a with DEBUG defined (in
> > fbdevhw.c), we might get more valuable information from the log.
>
> Sounds like the very bug I'm chasing. It chokes on the FBIOPUT_VSCREENINFO
> ioctl. The mode in question is reported as:
>
> xfree init mode: 64902 1024 1064 1200 1344 768 771 777 806
> fbdev init mode: 15407 1024 40 136 144 768 3 6 29 16 0:0:0
>
> with the only thing that seems fishy the 0:0:0 as the res:blue:green
> length values.
If it's for 16 bpp, this might be the problem.
Have you tried with several depths? (15, 8, 24, 32, ???)
Michel
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-03-13 13:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <38CCC0A9.576D34FC@iiic.ethz.ch>
2000-03-13 13:00 ` patch to get latest XFree 4.0 snapshot (xf3918) to workonppcwithr128 Michael Schmitz
2000-03-13 13:55 ` Michel Dänzer [this message]
2000-03-13 17:34 ` Michael Schmitz
2000-03-13 17:02 patch to get latest XFree 4.0 snapshot (xf3918) to work onppcwithr128 Michael Schmitz
2000-03-14 10:58 ` patch to get latest XFree 4.0 snapshot (xf3918) to workonppcwithr128 Michel Dänzer
[not found] <Pine.LNX.4.10.10003141911250.17573-100000@opal.biophys.uni-duesseldorf.de>
2000-03-14 21:10 ` Michael Schmitz
-- strict thread matches above, loose matches on Subject: below --
2000-03-15 9:44 Michel Danzer
2000-03-15 11:13 ` Michael Schmitz
2000-03-15 14:09 ` Kostas Gewrgiou
2000-03-15 11:22 Michel Danzer
[not found] <20000316112537.6597.qmail@web124.yahoomail.com>
2000-03-16 21:15 ` Michael Schmitz
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=38CCF340.363C70A7@iiic.ethz.ch \
--to=michdaen@iiic.ethz.ch \
--cc=gewrgiou@imbc.gr \
--cc=khendricks@ivey.uwo.ca \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=puetzk@iastate.edu \
--cc=schmitz@opal.biophys.uni-duesseldorf.de \
/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).