From: Benjamin Herrenschmidt <bh40@calva.net>
To: linuxppc-dev@lists.linuxppc.org, mlan@cpu.lu
Subject: Re: Q: control is a C&T 65550?
Date: Fri, 11 Jun 1999 18:08:11 +0200 [thread overview]
Message-ID: <19990611180811.016528@mail.mipsys.com> (raw)
In-Reply-To: <199906110543.HAA00297@piglet.cpu.lu>
On Fri, Jun 11, 1999, Michel Lanners <mlan@cpu.lu> wrote:
>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...
This could probably be found by tracing Apple's control driver. There are
a few video driver calls used to control the hw cursor, they are
documented, and I know at least two ways of tracing that: one is the
mac-on-linux emulator, and the other is Apple's serial-based 2 machines
debugger using the ROM stub. (It should be downloadable on Apple site
along with other ETO/MPW stuffs). This debugger can debug HW device
drivers loaded at very early boot time or hardware interrupts, and so
should have no problem tracing the control driver.
>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....
I don't think so. There is however some kind of "graphic accelerator" for
control in MacOS, It's quite small, I don't know if it only provides
better blit routines optimised for non-cachable space, or eventually
hacks the MMU to make the fb space cahable (for bursts), I don't think
there's anything like a blitter or a DMA engine in control.
--
Perso. e-mail: <mailto:bh40@calva.net>
Work e-mail: <mailto:benh@mipsys.com>
BenH. Web : <http://calvaweb.calvacom.fr/bh40/>
[[ 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 16:08 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
1999-06-11 16:08 ` Benjamin Herrenschmidt [this message]
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=19990611180811.016528@mail.mipsys.com \
--to=bh40@calva.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mlan@cpu.lu \
/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).