From: Martin Costabel <costabel@wanadoo.fr>
To: paulus@samba.org
Cc: Tom Rini <trini@kernel.crashing.org>,
linuxppc-dev@lists.linuxppc.org, debian-powerpc@lists.debian.org
Subject: Re: [PATCH] Minor changes to control/imstt/platinum/valkyrie/atyfb
Date: Sun, 02 Dec 2001 22:11:09 +0100 [thread overview]
Message-ID: <3C0AA2AF.97E7FCB4@wanadoo.fr> (raw)
In-Reply-To: 15369.65261.546405.15780@argo.ozlabs.ibm.com
Paul Mackerras wrote:
>
> Martin Costabel writes:
>
> > For the valkyriefb driver on my Pmac 6400, I can confirm from a first
> > short test that it still works. This is with your patch applied to
> > today's 2.4.17-pre1-ben0 kernel.
>
> Do you still have macos on the 6400? If so can you confirm whether,
Yes, I still have MacOS 8.6. No 9.x, though.
> if you set the screen resolution and colour depth in macos, that the
> value you have set in macos is the default that linux will use?
I did some tests with the 2 useful modes of the 6400: 1024x768x8bit at
72Hz (vmode 15, cmode 8) and 800x600x16bit at 60Hz (vmode 10, cmode 16).
The results, with or without Tom's patch, were the same as they always
were:
The vmode of MacOS is used by the Linux console; the cmode 16 is not
recognized, so instead of vmode 10 16 one always gets vmode 10 8 as
default. The log says
kernel: Monitor sense value = 0x62b, <6>using video mode 10 and color
mode 0
I think I never saw this differently. For 16bit color, I always had to
either put video=valkyriefb:vmode:10,cmode:16 into the kernel args or
say vmode 10 16 at the console (and then startx -- -depth 15 to get the
right colors in X; -depth 16 gives weird colors).
P.S. Rebooting into MacOS (first time for almost a year) seems to have
cured the crashes I had yesterday, too. Weird.
--
Martin
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-12-02 21:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-27 21:30 [PATCH] Minor changes to control/imstt/platinum/valkyrie/atyfb Tom Rini
2001-11-28 9:14 ` Geert Uytterhoeven
2001-12-28 11:28 ` Benjamin Herrenschmidt
2001-12-02 16:35 ` Tom Rini
2001-12-01 12:41 ` Martin Costabel
2001-12-02 10:14 ` Paul Mackerras
2001-12-02 21:11 ` Martin Costabel [this message]
2001-12-02 22:47 ` Paul Mackerras
2001-12-03 13:16 ` Geert Uytterhoeven
2001-12-03 15:09 ` Tom Rini
2001-12-05 11:22 ` Martin Costabel
-- strict thread matches above, loose matches on Subject: below --
2001-12-03 8:10 Bill Fink
2001-12-02 23:59 ` Benjamin Herrenschmidt
2001-12-03 15:29 ` Tom Rini
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=3C0AA2AF.97E7FCB4@wanadoo.fr \
--to=costabel@wanadoo.fr \
--cc=debian-powerpc@lists.debian.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@samba.org \
--cc=trini@kernel.crashing.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).