From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Leisner, Martin" <Martin.Leisner@xerox.com>
Cc: linuxppc-dev <Linuxppc-dev@ozlabs.org>
Subject: Re: nap/dfs on 7448
Date: Tue, 02 Oct 2007 16:01:57 +1000 [thread overview]
Message-ID: <1191304917.6310.99.camel@pasglop> (raw)
In-Reply-To: <556445368AFA1C438794ABDA8901891C0738E1E8@USA0300MS03.na.xerox.net>
On Mon, 2007-10-01 at 17:32 -0400, Leisner, Martin wrote:
> I asked this on linuxppc-embedded a week ago (I didn't even know this
> list existed until last week -- another reason to get rid of
> linuxpcc-embedded).
>
> Has anyone gotten NAP/DFS to reliably work on a 7448?
>
> I'm seeing strange problems with peripherals...(using a ram disk
> works fine).
Could it be that your host bridge isn't properly waking up the CPU to
DOZE state for snooping DMA ? (It might require some delays on QACK in
some cases, I know Apple had workarounds in those areas, maybe something
along those lines need to be configured in the chipset).
Ben.
next prev parent reply other threads:[~2007-10-02 6:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-01 21:32 nap/dfs on 7448 Leisner, Martin
2007-10-02 6:01 ` Benjamin Herrenschmidt [this message]
2007-12-27 22:37 ` update: " Leisner, Martin
2007-12-28 5:19 ` Benjamin Herrenschmidt
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=1191304917.6310.99.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=Linuxppc-dev@ozlabs.org \
--cc=Martin.Leisner@xerox.com \
/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.