linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan de Jongh <jfcmdejongh@gmail.com>
To: linux-wireless@vger.kernel.org
Subject: Re: 802.11p implementation...
Date: Sat, 12 Nov 2011 21:01:06 +0000 (UTC)	[thread overview]
Message-ID: <loom.20111112T202645-807@post.gmane.org> (raw)
In-Reply-To: CAFtRNNxGd7NSmjNhZboW5VOZ++j=D1E_G6E6RqXLA3Ssuu4XfQ@mail.gmail.com

Nick Kossifidis <mickflemm@...> writes:

> 
> 2011/11/6 Johannes Berg <johannes@...>:
> > On Sun, 2011-11-06 at 02:53 +0200, Nick Kossifidis wrote:
> >> It seems a group of people have released an 802.11p implementation on
> >> top of 2.6.31.
> >>
> >> http://www.gcdc.net/mainmenu/Home/downloads/Technology
...
> > johannes
> >
> 
...

Hi Nick, Johannes,

First, please note that I haven't checked on recent ath5k support for 802.11p.
If such support it already present, this mail is quite obsolete :-)...

The Grand Cooperative Driving Challenge succesfully used 802.11p in
vehicle-to-vehicle communications and vehicle-to-infrastructure communications,
using a modified ath5k driver (which you found on the gcdc.net site).
Apart from GCDC, there are many research and commercial projects/products
(SPITS/FREILOT/...) using patched ath5k drivers for half-clock-rate operation,
ocb, and access to the 5.9-6.0 GHz frequencies.
And there are many more to come,.
Simply because Atheros-based cards are among the few
(if not the only ones)
that support 802.11p/5.9GHz operation.
For GCDC, the patches had their origins in the CVIS project,
and in work by Eric Koenders of Peek Traffic.

However, the current situation is far from ideal...
By now, the 11p amendment has been ratified,
but maintaining 802.11p support for contemparory kernel/compat-wireless combos
is near to impossible without structural support from ath/ath5k developers.
The result of this effort, in short, would mean 802.11p operation
through module parameter and crda/regdb settings only,
and without the need to (re)compile kernels and/or kernel modules.
11p Operation would simply imply some configuration efforts
on well-known distributions (modules,conf, regdb/crda, iw, and stuff like that)
out-of-the-box...
I understand that there are regulatory issues
(crda, do we want anyone to operate on the ITS frequencies???) involved,
but we would be very interested in
structural 11p support in the ath5k driver (and, perhaps ath9k).
"We" referring to a substantial part of the ITS community.
If you can arrange substantial commitment to 11p support in ath5k,
I can mobilize people and funding for
development/testing/deployment/discussion/feedback.

Let me know what you think of this, best wishes,

Jan de Jongh
GCDC - Technology Leader


  reply	other threads:[~2011-11-12 21:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-06  0:53 802.11p implementation Nick Kossifidis
2011-11-06 13:10 ` Johannes Berg
2011-11-06 17:52   ` Nick Kossifidis
2011-11-12 21:01     ` Jan de Jongh [this message]
2011-11-17 20:59       ` Nick Kossifidis
2011-11-17 21:11         ` Johannes Berg
2011-11-19  3:20         ` Pat Erley
2011-11-19 23:46           ` Adrian Chadd
2011-11-20 21:05             ` Pat Erley
  -- strict thread matches above, loose matches on Subject: below --
2014-11-11 18:13 Hernán Maximiliano

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=loom.20111112T202645-807@post.gmane.org \
    --to=jfcmdejongh@gmail.com \
    --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).