From: Max Filippov <jcmvbkbc@gmail.com>
To: Christian Lamparter <chunkeey@web.de>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org
Subject: Re: p54spi - mesh mode summary
Date: Fri, 27 Mar 2009 04:55:23 +0300 [thread overview]
Message-ID: <200903270455.24129.jcmvbkbc@gmail.com> (raw)
In-Reply-To: <200903261933.53998.chunkeey@web.de>
> > I see constant beacon resubmission cycle. How does it work on pci/usb
> > p54?
>
> firmware does it... all we need is to submit a beacon template. The
> firmware knows how to extract everything it needs (e.g intervals/dtim etc.)
> out of the frame itself...
> > But if there's real problem in firmware, I'd consider it mere
> > workaround and put it back.
>
> yes please do... And don't worry the frame which we'll pass to mac80211
> will always have the correct length, even when the extra padding wasn't
> used.
Thanks for your explanation, it is very useful and encouraging (:
--
Max
next prev parent reply other threads:[~2009-03-27 2:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 18:33 p54spi - mesh mode summary Christian Lamparter
2009-03-27 1:55 ` Max Filippov [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-03-26 12:49 Chunkeey
2009-03-26 15:15 ` Max Filippov
2009-03-25 5:30 [PATCH 1/2] p54spi: mask value read from SPI_ADRS_DMA_WRITE_CTRL in p54spi_wait_bit Max Filippov
2009-03-25 13:42 ` [PATCH 2/2 v2] p54spi: fix p54spi_upload_firmware Christian Lamparter
2009-03-25 14:34 ` Christian Lamparter
2009-03-26 6:22 ` p54spi - mesh mode summary Max Filippov
2009-03-26 8:12 ` Johannes Berg
2009-03-27 5:03 ` Max Filippov
2009-03-27 14:06 ` Christian Lamparter
2009-03-28 3:21 ` Max Filippov
2009-03-28 21:51 ` Christian Lamparter
2009-03-29 4:41 ` Max Filippov
2009-03-29 13:49 ` Christian Lamparter
2009-03-30 4:38 ` Max Filippov
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=200903270455.24129.jcmvbkbc@gmail.com \
--to=jcmvbkbc@gmail.com \
--cc=chunkeey@web.de \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
/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).