From: Daniel Jacobowitz <drow@false.org>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: Q: control is a C&T 65550?
Date: Tue, 8 Jun 1999 09:58:44 -0400 [thread overview]
Message-ID: <19990608095844.A5496@drow.res.cmu.edu> (raw)
In-Reply-To: <Pine.GSO.4.05.9906080749180.27396-100000@mail.wesleyan.edu>; from Jason Y. Sproul on Tue, Jun 08, 1999 at 07:51:39AM -0400
On Tue, Jun 08, 1999 at 07:51:39AM -0400, Jason Y. Sproul wrote:
>
> Is it correct that the /chaos/control chip is essentially a Chips &
> Technologies 65550? If so, does anyone have the variances from the 65550
> datasheet, and if not, what the heck is it? :^)
It's my understanding that it's not. No one has any documentation on
it to my knowledge... I'd love to add hardware cursor support, which
I'm fairly sure it has, to controlfb. But I can't do it without some
sort of reference.
Dan
/--------------------------------\ /--------------------------------\
| Daniel Jacobowitz |__| SCS Class of 2002 |
| Debian GNU/Linux Developer __ Carnegie Mellon University |
| dan@debian.org | | dmj+@andrew.cmu.edu |
\--------------------------------/ \--------------------------------/
[[ 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-08 13:58 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 [this message]
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
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=19990608095844.A5496@drow.res.cmu.edu \
--to=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).