From: Michel D nzer <daenzerm@student.ethz.ch>
To: "Kevin M. Myer" <kevin_myer@iu13.k12.pa.us>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Control fb problem on 8500
Date: Tue, 15 Aug 2000 20:26:22 +0200 [thread overview]
Message-ID: <39998B4F.2AD2E17E@student.ethz.ch> (raw)
In-Reply-To: Pine.LNX.4.21.0008151339190.734-100000@pegmatite.iu13.k12.pa.us
"Kevin M. Myer" wrote:
> Secondly, the video chip doesn't show up on the PCI bus. Although XFree86
> 4.0 apparently supports the controlfb (which is what the 8500 has), it
> also needs a BusID to be used. Am I out of luck with using XFree86 4.0 or
> newer with my machine? Or generically, is anyone without a card on the
> PCI bus out of luck?
No, the contrary, you're very lucky! :)
As the chip doesn't show up, the X server can't deactivate it. So you don't
need to specify a bus ID (which would prevent the server of disabling the chip ;).
Michel
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-08-15 18:26 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-15 17:45 Control fb problem on 8500 Kevin M. Myer
2000-08-15 18:26 ` Michel D nzer [this message]
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 14:15 ` XF4 hangs on 2.4 kernel (was: Re: Control fb problem on 8500) Michel Lanners
2000-08-19 15:16 ` Martin Costabel
2000-08-23 12:18 ` Kostas Gewrgiou
2000-08-19 12:12 ` Control fb problem on 8500 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
[not found] <200008160459.XAA20764@lists.linuxppc.org>
2000-08-22 10:51 ` William H. Schultz
2000-08-22 11:56 ` Benjamin Herrenschmidt
2000-08-22 16:52 ` Geert Uytterhoeven
2000-08-23 14:03 ` William H. Schultz
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=39998B4F.2AD2E17E@student.ethz.ch \
--to=daenzerm@student.ethz.ch \
--cc=kevin_myer@iu13.k12.pa.us \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.