From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: David Vrabel <dvrabel@cantab.net>
Cc: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Support for GEODE CPUs
Date: Thu, 10 Mar 2005 00:06:39 +0000 [thread overview]
Message-ID: <1110413198.3116.278.camel@localhost.localdomain> (raw)
In-Reply-To: <422F8623.4030405@cantab.net>
On Mer, 2005-03-09 at 23:26, David Vrabel wrote:
> Alan Cox wrote:
> > - If you can't turn it off use solid areas of colour to speed the system
> > up (The hardware uses RLE encoding to reduce ram fetch bandwidth)
>
> How much of a difference does the compression make to performance?
Depends on the resolution but a display that is mostly solid can drop to
1/10th of a fancy background for memory fetch cost. Big deal on 66MHz
SDRAM
> > - The onboard audio is a software SB emulation on older GX. It burns
> > CPU.
>
> Presumably one could write a native audio driver that didn't use the
> soundblaster emulation?
The newer ones have native audio, the older ones you could but it would
be hard as the native audio is chip dependant, undocumented and the IRQ
it raises is hard coded to the SMI/SMM line.
next prev parent reply other threads:[~2005-03-10 0:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200503081935.j28JZ433020124@hera.kernel.org>
2005-03-09 17:01 ` [PATCH] Support for GEODE CPUs Alan Cox
2005-03-09 17:33 ` Lennart Sorensen
2005-03-09 21:59 ` Alan Cox
2005-03-09 22:23 ` Lennart Sorensen
2005-03-09 23:26 ` David Vrabel
2005-03-10 0:06 ` Alan Cox [this message]
2005-03-11 1:42 ` Andrew Morton
2005-03-11 11:02 ` Alan Cox
2005-03-11 14:13 ` Lennart Sorensen
2005-03-21 23:41 ` Andrew Morton
2005-03-22 1:09 ` Kianusch Sayah Karadji
2005-03-22 7:13 ` Andrew Morton
2005-03-22 8:01 ` Kianusch Sayah Karadji
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=1110413198.3116.278.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=dvrabel@cantab.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
/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