From: Giuliano Pochini <pochini@shiny.it>
To: Takashi Oe <toe@unlserve.unl.edu>
Cc: linuxppc-dev@lists.linuxppc.org, Benjamin Herrenschmidt <bh40@calva.net>
Subject: Re: Stealth port problems
Date: Mon, 31 Jul 2000 09:01:36 +0200 (CEST) [thread overview]
Message-ID: <XFMail.000731090136.pochini@shiny.it> (raw)
In-Reply-To: <Pine.LNX.3.96LJ1.1b7.1000730071543.1508E-100000@ofey.inetnebr.com>
>> 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/
next prev parent reply other threads:[~2000-07-31 7:01 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-28 5:33 Stealth port problems 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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-30 13:01 Iain Sandoe
2000-07-30 14:01 ` Takashi Oe
2000-07-30 16:44 Iain Sandoe
2000-07-31 9:11 Iain Sandoe
2000-07-31 9:59 ` Timothy A. Seufert
2000-07-31 11:43 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-08-01 11:11 Iain Sandoe
2000-08-02 17:13 Iain Sandoe
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=XFMail.000731090136.pochini@shiny.it \
--to=pochini@shiny.it \
--cc=bh40@calva.net \
--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).