Hi! I have troubles with my stealth port on a G3-blue. When it runs at 115200
ifconfig
shows a lot of overruns. At 57600 it works fine, but it's slow :-((
Does any of you own that serial port ? Suggestions ??
Bye.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
From: Benjamin Herrenschmidt <hidden> Date: 2000-07-28 08:34:26
Hi! I have troubles with my stealth port on a G3-blue. When it runs at
115200
ifconfig
shows a lot of overruns. At 57600 it works fine, but it's slow :-((
Does any of you own that serial port ? Suggestions ??
Which kernel ? With the DMA serial driver, it should work better than
that... The Stealth hardware is probaly not responsible, it's just a line
driver plugged instead of the modem, the actual zilog SCC is part of
Apple's ASIC.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
Hi! I have troubles with my stealth port on a G3-blue. When it runs at
115200
quoted
ifconfig
shows a lot of overruns. At 57600 it works fine, but it's slow :-((
Does any of you own that serial port ? Suggestions ??
Which kernel ?
2.2.16p (usb patches)
With the DMA serial driver, it should work better than
that... The Stealth hardware is probaly not responsible, it's just a line
driver plugged instead of the modem, the actual zilog SCC is part of
Apple's ASIC.
I just discovered a strange thing... It seems to work fine in console, but when
X is running it doesn't. (??)
Bye.
Giuliano Pochini ->)|(<- Shiny Corporation {AS6665} ->)|(<-
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
Hi! I have troubles with my stealth port on a G3-blue. When it runs at
115200
quoted
ifconfig
shows a lot of overruns. At 57600 it works fine, but it's slow :-((
Does any of you own that serial port ? Suggestions ??
Which kernel ? With the DMA serial driver, it should work better than
that... The Stealth hardware is probaly not responsible, it's just a line
driver plugged instead of the modem, the actual zilog SCC is part of
Apple's ASIC.
Now I run XF4 and the problem is even worse. I get underruns at 38400
:-(((((((((((((
What can I do ? And why X affects the serial port ??
Bye.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
Hi! I have troubles with my stealth port on a G3-blue. When it runs at
115200
quoted
ifconfig
shows a lot of overruns. At 57600 it works fine, but it's slow :-((
Does any of you own that serial port ? Suggestions ??
Which kernel ? With the DMA serial driver, it should work better than
that... The Stealth hardware is probaly not responsible, it's just a line
driver plugged instead of the modem, the actual zilog SCC is part of
Apple's ASIC.
I've just tried the old non-dma code. Same problem :-(((
If so, could you check if you have DMA enabled with dma code?
$ cat /proc/interrupts
CPU0
2: 0 PMAC-PIC MACE-txdma
3: 0 PMAC-PIC MACE-rxdma
4: 0 PMAC-PIC SCC-txdma
5: 0 PMAC-PIC SCC-rxdma
6: 0 PMAC-PIC SCC-txdma
7: 15593 PMAC-PIC SCC-rxdma
8: 17 PMAC-PIC AWACS out
12: 7 PMAC-PIC 53C94
13: 3411091 PMAC-PIC MESH
14: 0 PMAC-PIC MACE
15: 0 PMAC-PIC SCC
16: 594667 PMAC-PIC SCC
17: 0 PMAC-PIC AWACS
18: 991629 PMAC-PIC VIA
19: 0 PMAC-PIC SWIM3
25: 0 PMAC-PIC usb-ohci, ohci-usb
BAD: 0
$
If you don't see "SCC-rxdma", then it's not enabled. The reason I ask is
that a G3-blue's SCC device node has more than three addresses if I
remember correctly, and, if that's the case, the dma code won't be enabled
due to the following sniplet in chan_init() of macserial.c:
#if !defined(CONFIG_KGDB) && defined(SUPPORT_SERIAL_DMA)
if (ch->n_addrs == 3 && ch->n_intrs == 3)
zss->has_dma = 1;
#endif
It can be fixed if the above is changed to something like:
#if !defined(CONFIG_KGDB) && defined(SUPPORT_SERIAL_DMA)
if (ch->n_addrs >= 3 && ch->n_intrs == 3)
zss->has_dma = 1;
#endif
I think the last two addresses correspond to DMA addresses for all
SCC capable machines so far, so this change should be ok.
Takashi Oe
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
Hi! I have troubles with my stealth port on a G3-blue. When it runs at
115200
quoted
ifconfig
shows a lot of overruns. At 57600 it works fine, but it's slow :-((
Does any of you own that serial port ? Suggestions ??
Which kernel ? With the DMA serial driver, it should work better than
that... The Stealth hardware is probaly not responsible, it's just a line
driver plugged instead of the modem, the actual zilog SCC is part of
Apple's ASIC.
I've just tried the old non-dma code. Same problem :-(((
All works fine with Mac OS.
Bye.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
From: Michel D�nzer <hidden> Date: 2000-07-30 13:01:49
Giuliano Pochini wrote:
Now I run XF4 and the problem is even worse. I get underruns at 38400
:-(((((((((((((
What can I do ? And why X affects the serial port ??
I assume you are running an accelerated driver, which moves load from the CPU
to the graphics chip, which may increase interrupt and/or bus load/latency.
Michel
--
Chaos, panic and disorder -- my work here is done.
______________________________________________________________________________
Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \ member of XFree86, Team *AMIGA*, AUGS
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
Hi! I have troubles with my stealth port on a G3-blue. When it runs at
115200
quoted
ifconfig
shows a lot of overruns. At 57600 it works fine, but it's slow :-((
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 ??
Bye.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
I've just tried the old non-dma code. Same problem :-(((
If so, could you check if you have DMA enabled with dma code?
$ cat /proc/interrupts
CPU0
2: 0 PMAC-PIC MACE-txdma
3: 0 PMAC-PIC MACE-rxdma
4: 0 PMAC-PIC SCC-txdma
5: 0 PMAC-PIC SCC-rxdma
6: 0 PMAC-PIC SCC-txdma
7: 15593 PMAC-PIC SCC-rxdma
8: 17 PMAC-PIC AWACS out
12: 7 PMAC-PIC 53C94
13: 3411091 PMAC-PIC MESH
14: 0 PMAC-PIC MACE
15: 0 PMAC-PIC SCC
16: 594667 PMAC-PIC SCC
17: 0 PMAC-PIC AWACS
18: 991629 PMAC-PIC VIA
19: 0 PMAC-PIC SWIM3
25: 0 PMAC-PIC usb-ohci, ohci-usb
BAD: 0
$
If you don't see "SCC-rxdma", then it's not enabled.
Uhmm, IFAI can remember, there wasn't any SCC-XXdma (the G3 is at home, I'm
writing from workplace).
The reason I ask is
that a G3-blue's SCC device node has more than three addresses if I
remember correctly, and, if that's the case, the dma code won't be enabled
due to the following sniplet in chan_init() of macserial.c:
#if !defined(CONFIG_KGDB) && defined(SUPPORT_SERIAL_DMA)
if (ch->n_addrs == 3 && ch->n_intrs == 3)
zss->has_dma = 1;
#endif
It can be fixed if the above is changed to something like:
#if !defined(CONFIG_KGDB) && defined(SUPPORT_SERIAL_DMA)
if (ch->n_addrs >= 3 && ch->n_intrs == 3)
zss->has_dma = 1;
#endif
I think the last two addresses correspond to DMA addresses for all
SCC capable machines so far, so this change should be ok.
Ok, this night I'll try this. Tnx.
Bye.
Giuliano Pochini ->)|(<- Shiny Corporation {AS6665} ->)|(<-
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
#if !defined(CONFIG_KGDB) && defined(SUPPORT_SERIAL_DMA)
if (ch->n_addrs >= 3 && ch->n_intrs == 3)
zss->has_dma = 1;
#endif
I think the last two addresses correspond to DMA addresses for all
SCC capable machines so far, so this change should be ok.
I had the time to try the patch for just a few minutes. It enables the dma
code successfully and it seems to work fine. More testing this night.
Tnx !
Bye.
Giuliano Pochini ->)|(<- Shiny Corporation {AS6665} ->)|(<-
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
#if !defined(CONFIG_KGDB) && defined(SUPPORT_SERIAL_DMA)
if (ch->n_addrs >= 3 && ch->n_intrs == 3)
zss->has_dma = 1;
#endif
I think the last two addresses correspond to DMA addresses for all
SCC capable machines so far, so this change should be ok.
I had the time to try the patch for just a few minutes. It enables the dma
code successfully and it seems to work fine. More testing this night.
Tnx !