All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Iain Sandoe" <iain@sandoe.co.uk>
To: Giuliano Pochini <pochini@shiny.it>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Stealth port problems
Date: Mon, 31 Jul 2000 10:11:51 +0100	[thread overview]
Message-ID: <200007310911.KAA04511@hyperion.valhalla.net> (raw)


On  Mon, Jul 31, 2000,  Giuliano Pochini wrote:
>>> The problem is definitely X.  I made a lot of tests: with dma and non-dma
>>> serial driver, X accelerated, non accelerated, X bare.bone (started with
>>> xinit). The problem is X. When X is running the serial ports looses packets
>>> :-((
>>> Am I the only one who is having this problem ???  Why does X cause overruns
>>> ??
>
>> If you can try 2.2.17pre10ben2 or pre13ben2 (linuxcare linux-pmac-benh) then
>> you can apply the IRQ latency test and see if it is that which is blocking
>> you.  Scan the dev list for "[ANN} IRQ".
>
> I'll try a soon I have a bit of free time...

There's a pre-built kernel, modules & system.map (with IRQ latency &
dmasound stuff already applied ) linked to:

http://www.drfruitcake.com/linux/linuxppc.html

The IRQh app - which you need to start the profiling is linked to :

http://www.drfruitcake.com/linux/irq_blk.html

>> The RX buffer in an 85230 (which is actually the chip - IIRC - an enhanced
>> 8530) is 8 characters deep - so any more that about 700 us IRQ block will
>> cause a drop out at 115200 continuous...
>
> On the Amiga I used to rtx stuff at 230K with no problems. It has 1 byte
> buffer...

BTW st SCC-XXdma stuff *is* enabled on my G3 by default.

Iain.

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

             reply	other threads:[~2000-07-31  9:11 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-31  9:11 Iain Sandoe [this message]
2000-07-31  9:59 ` Stealth port problems Timothy A. Seufert
  -- strict thread matches above, loose matches on Subject: below --
2000-08-02 17:13 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-30 16:44 Iain Sandoe
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=200007310911.KAA04511@hyperion.valhalla.net \
    --to=iain@sandoe.co.uk \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=pochini@shiny.it \
    /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.