From: Michel Lanners <mlan@cpu.lu>
To: drow@false.org
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Q: control is a C&T 65550?
Date: Fri, 11 Jun 1999 07:43:15 +0200 (CEST) [thread overview]
Message-ID: <199906110543.HAA00297@piglet.cpu.lu> (raw)
In-Reply-To: <19990610165732.A3984@drow.res.cmu.edu>
On 10 Jun, this message from Daniel Jacobowitz echoed through cyberspace:
[snip'ed the details]
>
> I intend to see what I can do about documenting the hardware cursor.
> With all the excellent advice I've gotten, I expect it won't be too
> difficult.
One thing I have done to look at hoe this stuff is working is to put
the cursor under Macos and/or MacsBug at some precise location (top
left corner), and look at the data in the invisible last portion of
each scanline in VRAM. That should tell us how and in what format the
cursor bitmap needs to be drawn. Restricting the cursor movement to
horizontal movements, and looking at RaDaCal's registers, should tell
us where the horizontal position needs to be set.
Unfortunately, as to the registers that control the appearance of the
cursor (visible/not visible; its colors, etc...), I have no iddea where
exactly on RaDaCal they are, and how to identify them except by poking
at registers from a distance...
>> Obviously, all of the above information can be totally wrong ;-). If
>> there is any Apple engineer in the audience who knows better, please do
>> speak up!
>
> Unfortunately, the Apple engineers in the audience aren't allowed to :(
What a shame! After all, the control hardware can be seen as a legacy
device, being surpassed by any and all current video chips... or might
Apple be hiding some really cool and powerful feature deep inside
control? I doubt it....
Michel
-------------------------------------------------------------------------
Michel Lanners | " Read Philosophy. Study Art.
23, Rue Paul Henkes | Ask Questions. Make Mistakes.
L-1710 Luxembourg |
email mlan@cpu.lu |
http://www.cpu.lu/~mlan | Learn Always. "
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next prev parent reply other threads:[~1999-06-11 5:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-08 11:51 Q: control is a C&T 65550? Jason Y. Sproul
1999-06-08 13:58 ` Daniel Jacobowitz
1999-06-08 14:00 ` Geert Uytterhoeven
1999-06-08 14:12 ` Daniel Jacobowitz
1999-06-08 14:16 ` Geert Uytterhoeven
1999-06-08 23:54 ` Paul Mackerras
1999-06-09 0:16 ` Daniel Jacobowitz
1999-06-09 0:55 ` Paul Mackerras
1999-06-09 1:19 ` Daniel Jacobowitz
1999-06-10 21:14 ` Michel Lanners
1999-06-10 20:51 ` Michel Lanners
1999-06-10 20:57 ` Daniel Jacobowitz
1999-06-11 5:43 ` Michel Lanners [this message]
1999-06-11 16:08 ` Benjamin Herrenschmidt
1999-06-11 19:03 ` Jerry Quinn
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=199906110543.HAA00297@piglet.cpu.lu \
--to=mlan@cpu.lu \
--cc=drow@false.org \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).