From: Luis Carlos Cobo <luisca@cozybit.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 11/13 v2] o11s: support for on-demand Hybrid Wireless Mesh Protocol
Date: Mon, 25 Feb 2008 11:51:47 -0800 [thread overview]
Message-ID: <1203969107.6929.37.camel@localhost> (raw)
In-Reply-To: <1203968312.13162.142.camel@johannes.berg>
On Mon, 2008-02-25 at 20:38 +0100, Johannes Berg wrote:
> Huh. The draft says something like
>
> "includes frame headers, training sequences, access protocol frames,
> etc."
>
> That doesn't seem to depend on the hardware but rather on the PHY type
> used, i.e. whether you have short/long preamble or 5GHz etc. Am I
> misunderstanding it?
You are right, I assumed some of those values may vary among different
hardware but have not going very deep about how to compute them.
--
Luis Carlos Cobo Rus GnuPG ID: 44019B60
cozybit Inc.
next prev parent reply other threads:[~2008-02-25 19:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-22 4:23 [PATCH 11/13 v2] o11s: support for on-demand Hybrid Wireless Mesh Protocol Luis Carlos Cobo
2008-02-22 16:30 ` Johannes Berg
2008-02-25 19:30 ` Luis Carlos Cobo
2008-02-25 19:30 ` Johannes Berg
2008-02-25 19:36 ` Luis Carlos Cobo
2008-02-25 19:38 ` Johannes Berg
2008-02-25 19:51 ` Luis Carlos Cobo [this message]
2008-02-25 19:57 ` Johannes Berg
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=1203969107.6929.37.camel@localhost \
--to=luisca@cozybit.com \
--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).