From: "mirabilos" <eccesys@topmail.de>
To: "Linux-Kernel ML" <linux-kernel@vger.kernel.org>
Subject: Hercules Graphics Card
Date: Wed, 24 Jan 2001 15:22:57 -0000 [thread overview]
Message-ID: <006001c0861a$0c85c960$0100a8c0@homeip.net> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="x-user-defined", Size: 1148 bytes --]
So I'm not the only... -- surprise for me, too.
I'm too using this, mostly because I like it, got up with it, and it's better than those pixelled displays today. And who needs colours?
For me, it says (2.4.0-prerelease) I'd got a HGC with 8 kB of RAM.
This surely isn't true because under DOS some pgmz work problemless
which use the whole 64K of &hB0000 to &hBFFFF (when I deactivate the VGA
card), and even Turbo Debugger 1.0's dual-screen option works in both gfx and
text mode, with the other card as debugging display in text mode, no matter whether the PGM uses HGC or VGA as primary display.
I'm sorry I've got no correction, but prolly you could try to read-modify-write-read-write_original, and compare the read value with the written bzw. the original.
And - do we get a HGC gfx framebuffer hgc1fb? (Btw, the vga16fb must be called vga4fb - it uses 4 bit colour, not 16)
What about dual-screen X... (this is OT - I know)
(Sorry about my English) - mirabilos
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-01-24 15:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-24 15:22 mirabilos [this message]
2001-01-26 17:51 ` Pavel Machek
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='006001c0861a$0c85c960$0100a8c0@homeip.net' \
--to=eccesys@topmail.de \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®