From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Leisner, Martin" <Martin.Leisner@xerox.com>
Cc: linuxppc-dev <Linuxppc-dev@ozlabs.org>
Subject: Re: update: RE: nap/dfs on 7448
Date: Fri, 28 Dec 2007 16:19:45 +1100 [thread overview]
Message-ID: <1198819185.7209.18.camel@pasglop> (raw)
In-Reply-To: <556445368AFA1C438794ABDA8901891C07C113CC@USA0300MS03.na.xerox.net>
On Thu, 2007-12-27 at 17:37 -0500, Leisner, Martin wrote:
> Turns out the Tundra TSI109 has various "problems" trying
> to nap -- its not a 7448 issue...
>
> We're working with tundra to get a workaround (in software, they
> won't respin the part). It seems DMA while napping is an issue, we
> have to turn off the tsi109 ethernet queues before entering nap mode...
>
> If anyone needs this work, let me know (it will be covered under GPL).
This looks like yet another f*cked up bridge ... I wonder if we'll ever
get a half decent working northbridge for those processors...
Unfortunately, it looks like the market for those is limited to junk
from vendor A and shit from vendor B...
Is the problem limited to the TSI internal ethernet or it happens with
any DMA ?
Looks to me like turning off DMA in NAP mode basically makes NAP mode
unuseable, perdiod. You can't start loosing packets because your
processor is idle. So no power saving, and let's eat the watts since
they won't respin the part. Great !
Ben.
prev parent reply other threads:[~2007-12-28 5:19 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
2007-12-27 22:37 ` update: " Leisner, Martin
2007-12-28 5:19 ` Benjamin Herrenschmidt [this message]
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=1198819185.7209.18.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 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).