From: Josh Huber <huber@mclx.com>
To: Linux/PowerPC Devel List <linuxppc-dev@lists.linuxppc.org>
Subject: Re: dual head r128
Date: Wed, 11 Oct 2000 14:52:49 -0400 [thread overview]
Message-ID: <20001011145249.B1437@missioncriticallinux.com> (raw)
In-Reply-To: <39E4B4D0.FA62D929@student.ethz.ch>; from daenzerm@student.ethz.ch on Wed, Oct 11, 2000 at 08:43:28PM +0200
[-- Attachment #1: Type: text/plain, Size: 1375 bytes --]
On Wed, Oct 11, 2000 at 08:43:28PM +0200, Michel D?nzer wrote:
> I don't think that's the cause, it fails much later.
That is true, but I thought that if perhaps int10 wasn't able to init
the card fully, that it might cause problems later. Let's assume
that's not a problem for the moment though :)
> Have you built X yourself? If yes, you need patches from Ani Joshi. The memory
> and clock values it probes are obviously bogus.
> Wait a minute, I see you are using debs, which should contain Ani's stuff.
> Does aty128fb work on the second card? If yes, try Option "UseFBDev".
Yeah, I'm using the debs, but it looks like the latest xserver-xfree86
ppc packages are still at phase2v5, while the other packages are up to
phase2v15. Perhaps the code is just a little too old?
BTW, no...I don't have aty128fb working on the secondary head -- is
there some option to tell the driver to scan for all cards? does it
do this by default?
The secondary card is a PC card, so it's not initialized by OF, but I
think the r128 fb driver does a proper initialization of the card, so
that shouldn't be the problem.
btw, I'm using the debian kernel that shipped with potato -- perhaps I
should try a newer one? ben's or a 2.4 kernel perhaps?
Thanks,
--
Josh
| huber@mclx.com |
1024D/6B21489A 61F0 6138 BE7B FEBF A223 E9D1 BFE1 2065 6B21 489A
[-- Attachment #2: Type: application/pgp-signature, Size: 0 bytes --]
next prev parent reply other threads:[~2000-10-11 18:52 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-11 18:17 dual head r128 Josh Huber
2000-10-11 18:43 ` Michel Dänzer
2000-10-11 18:52 ` Josh Huber [this message]
2000-10-11 19:04 ` Tom Rini
2000-10-11 19:09 ` Michel Dänzer
2000-10-11 19:26 ` Josh Huber
2000-10-11 22:48 ` Michel Dänzer
2000-10-13 17:16 ` Josh Huber
2000-10-12 13:09 ` Kostas Gewrgiou
2000-10-12 15:13 ` Benjamin Herrenschmidt
2000-10-12 15:49 ` Gabriel Paubert
2000-10-12 16:40 ` David Edelsohn
2000-10-17 0:12 ` Paul Mackerras
2000-10-17 5:56 ` Michel Lanners
2000-10-17 10:41 ` Benjamin Herrenschmidt
2000-10-17 13:45 ` Geert Uytterhoeven
2000-10-17 17:17 ` Benjamin Herrenschmidt
2000-10-12 16:44 ` Kostas Gewrgiou
2000-10-11 21:01 ` Gabriel Paubert
-- strict thread matches above, loose matches on Subject: below --
2000-10-12 13:41 Hendricks, Kevin
2000-10-12 14:10 ` Kostas Gewrgiou
2000-10-12 14:30 Hendricks, Kevin
2000-10-12 16:11 ` Kostas Gewrgiou
2000-10-12 17:22 ` Michel Dänzer
2000-10-12 17:44 ` Kostas Gewrgiou
2000-10-12 21:25 ` Michel Dänzer
2000-10-13 15:26 ` Kostas Gewrgiou
2000-10-13 16:21 ` Geert Uytterhoeven
2000-10-12 16:25 Hendricks, Kevin
[not found] <200010121619.TAA27476@ns0.imbc.gr>
2000-10-12 17:08 ` Kostas Gewrgiou
[not found] <19340906102959.14429@192.168.1.2>
2000-10-12 17:57 ` Gabriel Paubert
[not found] <Pine.LNX.4.10.10010132302530.381-100000@cassiopeia.home>
2000-10-13 21:36 ` Benjamin Herrenschmidt
2000-10-13 21:47 ` Michel Lanners
2000-10-14 10:13 ` Benjamin Herrenschmidt
2000-10-14 10:21 ` Geert Uytterhoeven
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=20001011145249.B1437@missioncriticallinux.com \
--to=huber@mclx.com \
--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).