linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "William H. Schultz" <whschult@uncc.edu>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: Control fb problem on 8500
Date: Tue, 22 Aug 2000 06:51:02 -0400	[thread overview]
Message-ID: <39A25B16.4A3DD5BC@uncc.edu> (raw)
In-Reply-To: 200008160459.XAA20764@lists.linuxppc.org


For all of you saying that controlfb is broken...  I rsynced the
bitkeeper tree a few days ago, got it to compile, booted, etc...
however:  I have a voodoo3 card, and it is set as my main display.  The
voodoo3 was ignored, and the video went straight to the built in
controlfb on my 8500.  It worked just fine, and it worked the best it's
worked in quite some time.  I had no video artifacts at all, and
everything worked...  nice and smooth...  etc....  etc...

But the only way for me to use the voodoo3 (which is the card supporting
my BIG monitor) is to completely disable the video drivers from Boot
X...  odd quirk...

but now...  the bitkeeper tree doesn't compile again...  can't find
adbhid.o...  another story...



Hank

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

       reply	other threads:[~2000-08-22 10:51 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200008160459.XAA20764@lists.linuxppc.org>
2000-08-22 10:51 ` William H. Schultz [this message]
2000-08-22 11:56   ` Control fb problem on 8500 Benjamin Herrenschmidt
2000-08-22 16:52   ` Geert Uytterhoeven
2000-08-23 14:03     ` William H. Schultz
2000-08-15 17:45 Kevin M. Myer
2000-08-15 18:26 ` Michel D nzer
2000-08-15 19:41 ` Michel Lanners
2000-08-18 21:02 ` Michel Lanners
2000-08-19  6:47   ` Daniel Jacobowitz
2000-08-19  7:18     ` Michel Lanners
2000-08-19 11:59       ` Benjamin Herrenschmidt
2000-08-19 12:12       ` Geert Uytterhoeven
2000-08-21 11:25         ` Michael Schmitz
2000-08-21 13:19           ` Michel Dänzer
2000-08-21 16:44             ` Geert Uytterhoeven
2000-08-21 17:11             ` Michael Schmitz
2000-08-19 13:20       ` Michel Dänzer
2000-08-21  8:57         ` Michel Dänzer
2000-08-21 10:46           ` Geert Uytterhoeven
2000-08-21 13:14             ` Michel Dänzer
2000-08-21 16:45               ` Geert Uytterhoeven
2000-08-22  8:33                 ` Michel Dänzer
2000-08-22  9:42                   ` Geert Uytterhoeven
2000-08-22 10:14                     ` Michel Dänzer
2000-08-22 21:15                       ` Michel Lanners
2000-08-22 21:55                         ` Michel Dänzer
2000-08-23 11:51                           ` Geert Uytterhoeven
2000-08-22 21:10                   ` Michel Lanners
2000-08-22 22:39                     ` Michel Dänzer
2000-08-23  8:11                       ` Michael Schmitz
2000-08-23  8:21                         ` Michel Dänzer
2000-08-21 11:33           ` Michael Schmitz
2000-08-19 14:40     ` David Riley

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=39A25B16.4A3DD5BC@uncc.edu \
    --to=whschult@uncc.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;
as well as URLs for NNTP newsgroup(s).