All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jerry Quinn" <jquinn@nortelnetworks.com>
To: Benjamin Herrenschmidt <bh40@calva.net>
Cc: linuxppc-dev@lists.linuxppc.org, mlan@cpu.lu
Subject: Re: Q: control is a C&T 65550?
Date: Fri, 11 Jun 1999 15:03:51 -0400	[thread overview]
Message-ID: <37615D97.EF08C746@americasm01.nt.com> (raw)
In-Reply-To: 19990611180811.016528@mail.mipsys.com


Benjamin Herrenschmidt wrote:
> 
> On Fri, Jun 11, 1999, Michel Lanners <mlan@cpu.lu> wrote:
> 
[snip] 
> >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.

Do you have any guess what the graphic accelerator for Platinum does? 
At the moment, platinum is also used just as a frame buffer. 

-- 
Jerry Quinn                             Tel: (514) 761-8737
jquinn@nortelnetworks.com               Fax: (514) 761-8505
Speech Recognition Research

[[ 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.   ]]

      reply	other threads:[~1999-06-11 19:03 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
1999-06-11 19:03           ` Jerry Quinn [this message]

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=37615D97.EF08C746@americasm01.nt.com \
    --to=jquinn@nortelnetworks.com \
    --cc=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 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.