linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jorge Miguel <jmiggal@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Stanislaw Gruszka <sgruszka@redhat.com>, linux-wireless@vger.kernel.org
Subject: Re: Setting my WiFi adhoc connection in power save mode
Date: Fri, 13 May 2011 23:15:45 +0200	[thread overview]
Message-ID: <BANLkTin741=RL4Q4Tsn6w8LOv45xALyqMQ@mail.gmail.com> (raw)
In-Reply-To: <1305290751.3487.33.camel@jlt3.sipsolutions.net>

Hi,

I am really glad I got all your answers. Thanks a lot. Now it is clear to me.
Jorge.



On 13 May 2011 14:45, Johannes Berg <johannes@sipsolutions.net> wrote:
> On Fri, 2011-05-13 at 14:39 +0200, Stanislaw Gruszka wrote:
>
>> > I doubt it, iirc it was just some DMA issue that was discovered at some
>> > point and nobody could really pinpoint it. Those old devices stored some
>> > internal data into a host memory buffer, and reading them back sometimes
>> > corrupted them.
>>
>> Ok, so I will probably not try to reenable PS (as long someone clearly
>> state that it works in the past, and this is a regression).
>
> Well, problem is that it _did_ work for some people, since it seemed to
> depend on the platform. I don't remember all the details though.
>
>> Does this problem happen on both 4965 and 3945 ?
>
> I'm not sure on 3945. ISTR there was an issue, but I don't know if it
> was the same one.
>
> johannes
>
>

      reply	other threads:[~2011-05-13 21:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-12 17:02 Setting my WiFi adhoc connection in power save mode Jorge Miguel
2011-05-13 11:50 ` Stanislaw Gruszka
2011-05-13 11:55   ` Johannes Berg
2011-05-13 12:22     ` Stanislaw Gruszka
2011-05-13 12:27       ` Johannes Berg
2011-05-13 12:39         ` Stanislaw Gruszka
2011-05-13 12:45           ` Johannes Berg
2011-05-13 21:15             ` Jorge Miguel [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='BANLkTin741=RL4Q4Tsn6w8LOv45xALyqMQ@mail.gmail.com' \
    --to=jmiggal@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sgruszka@redhat.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).