linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michel Dänzer <michdaen@iiic.ethz.ch>
To: Michael Schmitz <schmitz@opal.biophys.uni-duesseldorf.de>
Cc: Kostas Gewrgiou <gewrgiou@imbc.gr>,
	"Kevin B. Hendricks" <khendricks@ivey.uwo.ca>,
	linuxppc-dev@lists.linuxppc.org
Subject: Re: patch to get latest XFree 4.0 snapshot (xf3918) to workonppcwithr128
Date: Tue, 14 Mar 2000 11:58:18 +0100	[thread overview]
Message-ID: <38CE1B4A.7BC9AFD5@iiic.ethz.ch> (raw)
In-Reply-To: Pine.LNX.4.10.10003131729540.1152-100000@opal.biophys.uni-duesseldorf.de


Michael Schmitz wrote:

> There's a lot more going on: in 32 bit mode the X server complains about
> invalid weight (000) and refuses to probe OK. In 16 bit mode some part of
> the server assumes 565 bit weighting but the kernel code only ever sees
> 000.

I don't know for sure, but I guess the fbdev driver gets the weight from
atyfb? That would strongly point to a bug there.


> I'm a bit confused here. In 8 bit mode, I get the X server to print a
> message like:
>
> fbdev trace: FBDevScreenInit: before screeninit8/16/32
> fbdevHW: fbScreenInit: before fbSetupScreen             < my trace message
>
>         This should not happen!
>         An unresolved function was called!
>
> That's in programs/Xserver/fb/fbscreen.c. fbSetupScreen ought to print
> another message on entry but that never happens. fbSetupScreen is defined
> in the very same source file. Funny.

Indeed... Looks like fbSetupScreen is the unresolved function, or is there an
earlier warning about unresolved symbols?


Michel


--
Columbus had a fourth ship. It sailed over the edge.
______________________________________________________________________________
Michel Dänzer                             ///           mdaenzer@earthling.net
                                     __  /// 	     AmigaOS/Linux(Debian/PPC)
Student of computer science at the   \\\///   Team *AMIGA*      ICQ #: 5675698
Swiss Federal Institute of Technology \\\/   AUGS member #163      IRC: CoOpER

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

  reply	other threads:[~2000-03-14 10:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.10.10003131026030.29249-100000@opal.biophys.uni-duesseldorf.de>
2000-03-13 12:10 ` patch to get latest XFree 4.0 snapshot (xf3918) to work onppcwithr128 Kostas Gewrgiou
2000-03-13 13:05   ` Michael Schmitz
2000-03-13 16:24     ` Kostas Gewrgiou
2000-03-13 17:02       ` Michael Schmitz
2000-03-14 10:58         ` Michel Dänzer [this message]
     [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
2000-03-13 17:34     ` Michael Schmitz
     [not found] <Pine.LNX.4.10.10003141911250.17573-100000@opal.biophys.uni-duesseldorf.de>
2000-03-14 21:10 ` Michael Schmitz
2000-03-15  9:44 Michel Danzer
2000-03-15 11:13 ` Michael Schmitz
2000-03-15 14:09   ` Kostas Gewrgiou
  -- strict thread matches above, loose matches on Subject: below --
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=38CE1B4A.7BC9AFD5@iiic.ethz.ch \
    --to=michdaen@iiic.ethz.ch \
    --cc=gewrgiou@imbc.gr \
    --cc=khendricks@ivey.uwo.ca \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --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).