From: Andi <andi@fischlustig.de>
To: Matthew Wilcox <matthew@wil.cx>
Cc: parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] framebuffer drivers, sound
Date: Wed, 09 May 2001 02:00:12 +0200 [thread overview]
Message-ID: <3AF8888C.A8AB2BC9@fischlustig.de> (raw)
In-Reply-To: 20010509004136.R4917@parcelfarce.linux.theplanet.co.uk
Matthew Wilcox wrote:
> On Wed, May 09, 2001 at 12:53:31AM +0200, Andi wrote:
> > The stifb driver is working for me, but the colors are completely wrong
> > and the
> > system crashes if i try to cat /dev/fb0.
>
> Yup, the stifb is buggy. Please, if you have time, it would be great
> if you could help clean it up and get it working.
I hope that I will find the time, but I cant promise anything.
> sticon works rather
> better but it is still not great.
well, sticon has correct colors, but works worse than stifb
(swiching a vt does not redraw the whole screen,
dselect is not usable ...)
> The STI docs are publically available
> from the documentation page.
Yeah, the STI docs.... HP should release the hardware level
docs, this is the only way to implement a full featured fbdev
driver. A stifb would still be usefull since it is works for
every HP gfxcard with STI BIOS, but a special driver for each
gfxcard would be nice to have things like mode switching.
Andreas - "I want color recovery!!!" ;-)
next prev parent reply other threads:[~2001-05-09 0:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-08 22:53 [parisc-linux] framebuffer drivers, sound Andi
2001-05-08 23:41 ` Matthew Wilcox
2001-05-09 0:00 ` Andi [this message]
2001-05-09 0:02 ` Matthew Wilcox
2001-05-09 13:03 ` Brian S. Julin
2001-05-09 20:18 ` Helge Deller
2001-05-09 21:43 ` Andi
2001-05-09 22:07 ` Helge Deller
[not found] ` <873dacx0q1.fsf@rover.gag.com>
2001-05-11 10:01 ` Helge Deller
[not found] ` <3AF8FF5E.B9442562@esiee.fr>
[not found] ` <3AF9B4F9.17956B05@fischlustig.de>
2001-05-11 11:34 ` Matthieu Delahaye
2001-05-13 19:35 ` Andi
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=3AF8888C.A8AB2BC9@fischlustig.de \
--to=andi@fischlustig.de \
--cc=matthew@wil.cx \
--cc=parisc-linux@parisc-linux.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