[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <A6AD88C3F2289247BE726C37303E1EB894CF415D@orsmsx505.amr.corp.intel.com>
Date: Wed, 11 Feb 2009 14:13:30 -0800
From: "Yu, Fenghua" <fenghua.yu@...el.com>
To: "Winkler, Tomas" <tomas.winkler@...el.com>,
Johannes Berg <johannes@...solutions.net>
CC: David Woodhouse <dwmw2@...radead.org>, Ingo Molnar <mingo@...e.hu>,
Stephen Rothwell <sfr@...b.auug.org.au>,
"Grumbach, Emmanuel" <emmanuel.grumbach@...el.com>,
"Zhu, Yi" <yi.zhu@...el.com>, Chris Wright <chrisw@...s-sol.org>,
LKML <linux-kernel@...r.kernel.org>,
"iommu@...ts.linux-foundation.org" <iommu@...ts.linux-foundation.org>
Subject: RE: [PATCH]iwlan dma mapping read and write changes
>>> > >> Indeed the firmware/ucode write back to host memory to update retry
>>> > >> counter for APMDU packets. I'm not sure if this is needed for legacy
>>> > >> traffic, though.
>> > >
>> > >I don't think they can be seeing AMPDU packets since that is, well,
>> > >broken?
>> >
>> > Currently I'm not aware of any other cases where memory is accessed
>> > back but I may have not complete info. Will be back with the answer
>> > tomorrow.
>>
>> I don't think it really matters, since AMPDU packets will be fixed soon,
>> and for those you know it's necessary (and the report says that under
>> some other circumstances it's also necessary). Unless there'd be some
>> benefit from using BIDI only when we know it'll be needed, and using
>> TODEV in the other cases?
>
>Or if there's a firmware bug.
>That's why it's better to clear the picture.
>Fenghua
>What exact HW do you get this error?
This is Lenovo T400 wireless lan. Firmware version is 5.4.1.16. I think this issue happens on other platform/hw as well.
Thanks.
-Fenghua
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists