On Wed, Apr 18, 2012 at 7:41 PM, Yeoh Chun-Yeow <yeohchunyeow@xxxxxxxxx> wrote: >> Now we know what hardware *not* to use for this :P > What is the hardware that you referred to? > > Please advice. Thanks Johannes was just explaining that Intel wlan devices would not report timing info in the way required for mesh synchronization. Not a big deal considering that they don't support mesh mode. My comment should have been interpreted as a joke (and probably I should have sent it off-list, sorry!). Javier > On Wed, Apr 18, 2012 at 11:16 PM, Javier Cardona <javier@xxxxxxxxxxx> wrote: >> On Wed, Apr 18, 2012 at 8:05 AM, Johannes Berg >> <johannes@xxxxxxxxxxxxxxxx> wrote: >>> On 4/18/2012 7:56 AM, Javier Cardona wrote: >>>> >>>> On Tue, Apr 17, 2012 at 7:02 PM, Johannes Berg >>>> <johannes@xxxxxxxxxxxxxxxx> wrote: >>>>> >>>>> (...) >>>>> Keep in mind that TSF == start of TSF field, while rx_status->timestamp >>>>> == start of first symbol, which I didn't even remember when you guys did >>>>> all the Toffset things, I'm guessing they're all wrong :-) >>>> >>>> >>>> I think you guessed wrong :) >>> >>> >>> Nice! FWIW, our hardware (not that the driver supports mesh now) will give >>> the timestamp at the first symbol of the MPDU, so some more offset >>> calculations are needed and we don't give valid timestamps today. I started >>> working on this but haven't figured out HT preamble duration yet. >> >> Thanks for letting us know. Now we know what hardware *not* to use for this :P >> >> Javier >> _______________________________________________ >> Greenmesh mailing list >> Greenmesh@xxxxxxxxxxxxxxxxx >> http://lists.osll.spb.ru/mailman/listinfo/greenmesh -- Javier Cardona cozybit Inc. http://www.cozybit.com -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
