From: Benjamin Herrenschmidt <bh40@calva.net>
To: Giuliano Pochini <pochini@denise.shiny.it>,
<linuxppc-dev@lists.linuxppc.org>
Subject: Re: Stealth port problems
Date: Mon, 31 Jul 2000 20:27:15 +0200 [thread overview]
Message-ID: <20000731182715.23487@192.168.1.10> (raw)
In-Reply-To: <3986152C.992C3CE8@denise.shiny.it>
>> >
>> > 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 !
>
>I confirm. It works fine.
I'm pushing this fix to my rsync 2.2 tree and bk 2.4
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-07-31 18:27 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
2000-07-31 13:01 ` Giuliano Pochini
2000-08-01 0:09 ` Giuliano Pochini
2000-07-31 18:27 ` Benjamin Herrenschmidt [this message]
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=20000731182715.23487@192.168.1.10 \
--to=bh40@calva.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=pochini@denise.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 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).