From: Christer Weinigel <wingel@acolyte.hack.org>
To: Rob van Nieuwkerk <robn@verdi.et.tudelft.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Cyrix IRQ routing is wrong?
Date: 05 Jul 2002 17:02:26 +0200 [thread overview]
Message-ID: <m3sn2y43r1.fsf@acolyte.hack.org> (raw)
In-Reply-To: Rob van Nieuwkerk's message of "Thu, 04 Jul 2002 10:48:53 +0200"
Rob van Nieuwkerk <robn@verdi.et.tudelft.nl> writes:
> PS: anyone else seeing screen corruption in console/text mode with these
> boards ? (some chracters from before a screen update stay on the screen).
>
> board:
> ------
> Axiom Technology, SBC84510VEE, 3.5" Capa board, 300 MHz Geode
The Geode doesn't really have a text mode, VGA is simulated in SMI
mode by the "VSA BIOS", which is more or less buggy depending on what
exact BIOS revision you are using. In text mode, each byte written to
the screen will result in a SMI interrupt that then draws into the
real hardware frame buffer.
My suggestion is to never ever use the text mode on a Geode platform
and instead use the VESA framebuffer to seleect a framebuffer mode
that is directly supported by the hardware. That way mode, only
modifications of the resolution or the palette will result in SMI
interrupts and that code does not seem to be as buggy as the text mode
emulation.
/Christer
--
"Just how much can I get away with and still go to heaven?"
next prev parent reply other threads:[~2002-07-05 14:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-01 23:50 Cyrix IRQ routing is wrong? Pavel Roskin
2002-07-03 23:31 ` Alan Cox
2002-07-04 0:02 ` Pavel Roskin
2002-07-05 14:12 ` Alan Cox
2002-07-05 14:49 ` Christer Weinigel
2002-07-05 20:43 ` Alan Cox
2002-07-05 21:13 ` Pavel Roskin
2002-07-04 0:36 ` Linus Torvalds
2002-07-04 8:48 ` Rob van Nieuwkerk
2002-07-05 15:02 ` Christer Weinigel [this message]
2002-07-05 21:29 ` Alan Cox
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=m3sn2y43r1.fsf@acolyte.hack.org \
--to=wingel@acolyte.hack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robn@verdi.et.tudelft.nl \
/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.