From: Rik van Riel <H.H.vanRiel@phys.uu.nl>
To: Craig Schlenter <craig@is.co.za>
Cc: "Jon M. Taylor" <taylorj@ecs.csus.edu>, Linux MM <linux-mm@kvack.org>
Subject: Re: S3trio framebuffer on Intel?
Date: Mon, 3 Aug 1998 19:16:14 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.3.96.980803190939.3185A-100000@mirkwood.dummy.home> (raw)
In-Reply-To: <Pine.LNX.3.96.980803072540.18271D-100000@flashy.is.co.za>
On Mon, 3 Aug 1998, Craig Schlenter wrote:
> On Sun, 2 Aug 1998, Rik van Riel wrote:
>
> > It sure would be cool to have native S3trio support
> > from the kernel :)
>
> Agreed. I asked this a week or two back. It seems as if the s3 stuff in
> the kernel is ppc specific (but maybe someone can tune it a little) and
According to Geert, the S3triofb driver needs the video
mode setup to by some other code;
According to Jon, the KGI S3 driver works without prior
setup stuff.
Maybe the KGI S3 setup code could be ported into the
S3triofb driver? [preferably by someone with both
intimate knowledge of the video code and free time]
After that, the S3trio driver might still need some
endianness porting, but possibly that's just a minor
nuisance instead of real trouble.
Rik.
+-------------------------------------------------------------------+
| Linux memory management tour guide. H.H.vanRiel@phys.uu.nl |
| Scouting Vries cubscout leader. http://www.phys.uu.nl/~riel/ |
+-------------------------------------------------------------------+
--
This is a majordomo managed list. To unsubscribe, send a message with
the body 'unsubscribe linux-mm me@address' to: majordomo@kvack.org
next parent reply other threads:[~1998-08-03 21:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.3.96.980803072540.18271D-100000@flashy.is.co.za>
1998-08-03 17:16 ` Rik van Riel [this message]
1998-08-03 22:58 ` Jon M. Taylor
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=Pine.LNX.3.96.980803190939.3185A-100000@mirkwood.dummy.home \
--to=h.h.vanriel@phys.uu.nl \
--cc=craig@is.co.za \
--cc=linux-mm@kvack.org \
--cc=taylorj@ecs.csus.edu \
/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