All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Oe <toe@unlserve.unl.edu>
To: Benjamin Herrenschmidt <bh40@calva.net>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: [Fwd: Bug: 2.2.12 still hangs PPC after some PPP activity]
Date: Thu, 30 Sep 1999 11:21:47 -0500 (CDT)	[thread overview]
Message-ID: <Pine.LNX.3.96LJ1.1b7.990930111227.23148D-100000@ofey.inetnebr.com> (raw)
In-Reply-To: <19990930105030.013866@mailhost.mipsys.com>


On Thu, 30 Sep 1999, Benjamin Herrenschmidt wrote:

> I've heard of various possible issues with DMA hardware on the serial
> ports and G3 macs. There seem to be a problem with the Heathrow
> generation of Apple ASICs. (This was reported to me by people who made a
> special device that was plugged into those ports, with a custom driver
> under MacOS). They told me some characters end up beeing garbled when
> reaching the SCC. I'll do some testings with your driver and my
> powerbook's internal modem this week end to see if this problem actually
> occurs or not.

I suppose that can happen if DBDMA's FIFO wasn't flushed properly for
some reason.  Do you know if the problem occurs on receiving side (from
SCC to DMA) or transmitting side (from DMA to SCC)?  How many chars were
garbled?  If the FIFO were the cause of the problem, the number should be
between 1 and 7.


Takashi Oe


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

  reply	other threads:[~1999-09-30 16:21 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <37F1AD4B.585E99AB@chpc.utah.edu>
1999-09-29  7:11 ` [Fwd: Bug: 2.2.12 still hangs PPC after some PPP activity] Geert Uytterhoeven
1999-09-29  7:16 ` Takashi Oe
1999-09-29  7:40   ` Geert Uytterhoeven
1999-09-29  9:13   ` Benjamin Herrenschmidt
1999-09-30  0:46     ` Takashi Oe
1999-09-30  8:50       ` Benjamin Herrenschmidt
1999-09-30 16:21         ` Takashi Oe [this message]
1999-09-30 16:35           ` Benjamin Herrenschmidt
1999-10-06  5:33             ` update on macserial/DMA Takashi Oe
1999-10-06  8:35               ` Benjamin Herrenschmidt
1999-10-06 13:47                 ` Takashi Oe
1999-10-06 16:25                   ` Benjamin Herrenschmidt
1999-10-06 16:50                     ` Benjamin Herrenschmidt
1999-10-08  7:13               ` Lou Langholtz
1999-10-09 17:57                 ` Lou Langholtz
     [not found]             ` <Pine.LNX.3.96LJ1.1b7.991005234830.1210A-100000@ofey.inetne br.com>
1999-10-07  9:48               ` Franz Sirl
1999-10-07 15:37                 ` phandel
1999-10-12  7:20       ` [Fwd: Bug: 2.2.12 still hangs PPC after some PPP activity] Lou Langholtz
1999-09-29 16:44   ` Lou Langholtz
1999-09-29 17:02     ` Benjamin Herrenschmidt
1999-09-29 18:08       ` Lou Langholtz
1999-09-29 18:46   ` Lou Langholtz
1999-09-29 20:00   ` Lou Langholtz
1999-09-30  1:14     ` Takashi Oe
1999-09-30  5:33     ` Geert Uytterhoeven
1999-10-01 13:26     ` Franz Sirl
1999-10-01 13:46       ` Alvin Brattli
     [not found]       ` <Pine.OSF.3.96.991001153658.16772E-100000@mitra.phys.uit.no >
1999-10-01 14:08         ` Franz Sirl
1999-10-01 16:14       ` Lou Langholtz
     [not found] <37F1C0A3.B9F25580@chpc.utah.edu>
1999-09-29  7:39 ` Geert Uytterhoeven
1999-09-10 16:51 Lou Langholtz

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=Pine.LNX.3.96LJ1.1b7.990930111227.23148D-100000@ofey.inetnebr.com \
    --to=toe@unlserve.unl.edu \
    --cc=bh40@calva.net \
    --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 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.