Hello.
On Mon, 2011-06-20 at 17:50, Stefan Schmidt wrote:
>
> On Mon, 2011-06-20 at 19:27, Dmitry Eremin-Solenikov wrote:
> >
> > To ease somehow patch-related tasks, I've installed patchwork system at
> > http://patchwork.lumag.spb.ru/. Currently it contains all of the patches
> > ever circul
Hello.
On Mon, 2011-06-20 at 19:27, Dmitry Eremin-Solenikov wrote:
>
> To ease somehow patch-related tasks, I've installed patchwork system at
> http://patchwork.lumag.spb.ru/. Currently it contains all of the patches
> ever circulated on this list. I've moved some of older patches to
> 'Accep
Dmitry Eremin-Solenikov wrote:
> I think Alexander also has added static buffer protection, which should
> help exactly in this case.
Oh, nice ! I hadn't spotted this feature. Yes, it works perfectly.
Sorry for the false alarm.
I'm still curious about setting RX_SAFE_MODE, though. I don't see the
Hello, colleagues,
To ease somehow patch-related tasks, I've installed patchwork system at
http://patchwork.lumag.spb.ru/. Currently it contains all of the patches
ever circulated on this list. I've moved some of older patches to
'Accepted', but full cleanup is still pending. You can help us by
Hi all,
this patch allows to process several response statuses and execute specified
handlers. Currently it's used in active scanning when you may receive a
beacon or end_of_scan signals.
Thank you,
Alexander
From 8516cb53c66ba883da9ceb30146479728d097cb6 Mon Sep 17 00:00:00 2001
From: Alexander S
Hi Werner,
thanks again for your patch, please find my comments below in the text.
2011/6/18 Werner Almesberger
> The is_tx flag did not protect adequately against races when switching
> from receiving to transmitting. This patch removes the unnecessary
> spinlock and enforces proper synchroniz
Hello,
On 6/20/11, Werner Almesberger wrote:
> I wrote:
>> A way to avoid this should be to retrieve the PHR with an SRAM
>> read and to use the frame buffer read only for the payload.
>
> Hmm no, that doesn't work either. SRAM read can't retrieve the PHR :-(
>
> I've now verified that, if pa
I wrote:
> A way to avoid this should be to retrieve the PHR with an SRAM
> read and to use the frame buffer read only for the payload.
Hmm no, that doesn't work either. SRAM read can't retrieve the PHR :-(
I've now verified that, if packet reception is followed by a frame
buffer read, a paus
