linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Iain Sandoe" <iain@sandoe.co.uk>
To: Takashi Oe <toe@unlserve.unl.edu>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Stealth port problems
Date: Sun, 30 Jul 2000 17:44:03 +0100	[thread overview]
Message-ID: <200007301643.RAA16451@hyperion.valhalla.net> (raw)


On  Sun, Jul 30, 2000, Takashi Oe wrote:
> On Sun, 30 Jul 2000, Iain Sandoe wrote:
>
>> > Ok, this is a news to me.  I'm certain that SCC on oldworld pmacs is
>> > 85C30.  When did the change to 85230 occur?  If I remember correctly,
>> > some DMA setup codes in macserial.c need to know about it if it's dealing
>> > with 85230 rather than 85C30.
>>
>> OK - I don't know for certain - but the code refers to an "ESCC" which is
>> the name of the 85230 - the 8530 should just be called "SCC".
>
> It's not 8530.  I got an impression from Zilog's manual that ESCC refers
> to both 85230 and 85C30 loosely.

That manual has "Iain's all-time-award-for-the-worst-written-chip-manual"
:-(

>  Actually, on some pages, the term was
> used to refer to functionalities only available on 85230, and, on other
> pages, it was used to describe something 8530 doesn't support but both
> 85C30 and 85230 do.  AMD's usage of the term ESCC is yet slightly
> different, IIRC.
>
> Anyway, Apple's documentation uses the term ESCC and 85C30
> interchangeably, and I think the driver's usage of the term "ESCC" comes
> from there.

OK.  Well, that makes things worse - rather than better (re. the original
problem - if DMA is not enabled).  The 8530 had only 4 bytes of RX buffer &
only 2 Tx (the ESCC doubled these) - can't remember about the 85C30.  Wrote
drivers for the other two some years ago on a different OS (so memory might
be a shade foggy).

Of course, Apple has implemented the devices as a cell in an ASIC - so who
knows?

Iain.

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2000-07-30 16:44 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-30 16:44 Iain Sandoe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-08-02 17:13 Stealth port problems Iain Sandoe
2000-08-01 11:11 Iain Sandoe
2000-07-31 12:22 Iain Sandoe
2000-08-01 10:28 ` Timothy A. Seufert
2000-08-02 16:22   ` Benjamin Herrenschmidt
2000-07-31 11:43 Iain Sandoe
2000-07-31  9:11 Iain Sandoe
2000-07-31  9:59 ` Timothy A. Seufert
2000-07-30 13:01 Iain Sandoe
2000-07-30 14:01 ` Takashi Oe
2000-07-30 10:31 Iain Sandoe
2000-07-30 12:39 ` Takashi Oe
2000-07-31  7:12 ` Giuliano Pochini
2000-07-31 12:03   ` Geert Uytterhoeven
2000-07-28  5:33 Giuliano Pochini
2000-07-28  8:34 ` Benjamin Herrenschmidt
2000-07-28 14:23   ` Giuliano Pochini
2000-07-30  0:16   ` Giuliano Pochini
2000-07-30 13:01     ` Michel Dänzer
2000-07-30 12:59   ` Giuliano Pochini
2000-07-30 12:29     ` Takashi Oe
2000-07-31  7:01       ` Giuliano Pochini
2000-07-31 13:01       ` Giuliano Pochini
2000-08-01  0:09         ` Giuliano Pochini
2000-07-31 18:27           ` Benjamin Herrenschmidt
2000-07-30 14:11     ` Giuliano Pochini

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=200007301643.RAA16451@hyperion.valhalla.net \
    --to=iain@sandoe.co.uk \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=toe@unlserve.unl.edu \
    /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).