From: "Jerry Quinn" <jquinn@nortelnetworks.com>
To: Mark Abene <phiber@radicalmedia.com>
Cc: Tom Rini <trini@disparity.net>, linuxppc-dev@lists.linuxppc.org
Subject: Re: platinum video makes me cry...
Date: Mon, 2 Aug 1999 11:39:22 -0400 (EDT) [thread overview]
Message-ID: <14245.48042.697347.242992@gargle.gargle.HOWL> (raw)
In-Reply-To: <19990709095001.M822@radicalmedia.com>
>> "Mark" == Mark Abene <phiber@radicalmedia.com> writes:
Mark> I'll attach the "current" platinumfb.c file in its entirety. Although
Mark> I've just been informed (and I've verified) that 32bpp doesn't work. I
Mark> didn't originally notice because I normally use vmode 20 16, and hadn't
Mark> checked 32bpp. So the changes only fix 16bpp (8 still works as
Mark> before). I'm looking into why 32bpp doesn't work. I'm still irritated
Mark> at how much abstraction was done to make the driver "FBDev-aware". It
Mark> was so much simpler in 2.1.24, when ALL recognized modes worked in ALL
Mark> available bit-depths. Now I'm playing catch-up since I was previously
Mark> much too busy to know what was going on with newer kernels and FBDev.
I just tried out your revised platinumfb file. Kudos - I don't have to use
the OFfb anymore, the video driver works right. I don't have enough VRAM to
check out the 32bpp mode.
A couple of things I noticed, but don't know if they are directly due to the
driver or a more generic part. First, at the console, the block cursor is
invisible. The only way to tell where it is is because it is blinking (also
different) when over a character. Second, when I switch VT's, I get a resynch
disturbance. I'm running an Apple 21" fixed-freq monitor, so there shouldn't
be any attempt to change frequencies. This resync doesn't happen with 'no
video driver' checked.
I'm running a stock Linus 2.2.10.
As an aside, how do I get XF68_fbdev to work? It demands a config file.
I tried running Xconfigurator (vague memory since I haven't been following
those discussions), but it only detects 1M of VRAM instead of 2.
And more generally, why does Xpmac do the right thing and XF68_fpdev not?
There seems to be a lot of questions of the form "How do I get X set up
right?". I guess the question I have is why it's so seamless on the MacOS
side but hairy on the Linux side. What magic is Apple pulling and how do we
go about wrapping it up so that things work cleanly for Linux too?
Thanks
Jerry
--
Jerry Quinn Tel: (514) 761-8737
jquinn@nortelnetworks.com Fax: (514) 761-8505
Speech Recognition Research
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next prev parent reply other threads:[~1999-08-02 15:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-08 12:04 platinum video makes me cry Mark Abene
1999-07-08 18:29 ` Hollis R Blanchard
1999-07-09 13:32 ` Tom Rini
1999-07-09 13:50 ` Mark Abene
1999-08-02 15:39 ` Jerry Quinn [this message]
[not found] ` <Pine.BSF.3.96.990709093050.70746F-100000@silver.teardrop.n et>
1999-07-09 15:43 ` Franz Sirl
1999-07-11 11:24 ` 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=14245.48042.697347.242992@gargle.gargle.HOWL \
--to=jquinn@nortelnetworks.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=phiber@radicalmedia.com \
--cc=trini@disparity.net \
/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.