Linux wireless drivers development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	"Jouni.Malinen" <Jouni.Malinen@atheros.com>,
	Johannes Berg <johannes@sipsolutions.net>,
	Gaurav Jauhar <gaurav.jauhar@atheros.com>,
	Senthil Balasubramanian <senthilkumar@atheros.com>,
	Jothikumar Mothilal <jothikumar.mothilal@atheros.com>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	Kevin Hayes <kevin@atheros.com>
Subject: Re: Synching trees for BT 3.0 and a possible compat-bluetooth
Date: Wed, 23 Sep 2009 16:27:06 -0700	[thread overview]
Message-ID: <1253748426.2931.9.camel@localhost.localdomain> (raw)
In-Reply-To: <43e72e890909221001m19f076d8n64fb012b486f666a@mail.gmail.com>

Hi Luis,

> I forgot to poke about BT 3.0 synching at the summit. To work on
> bluetooth 3.0 we'll need some synching of trees between
> wireless-testing and Marcel's bluetooth tree. Also a compat-bluetooth
> might be in order to accomplish the same as we do with
> compat-wireless, only it would seem logical to consider tying to just
> merge this with compat-wireless to get the features required for
> bluetooth 3.0; to do this having one tree with both would be nice with
> the added benefit of all the same compat-2.6.3x.[ch] files being
> reused. Synching of the trees would be required only when a feature on
> one tree is not yet available on the latest rc kernel (provided marcel
> rebases on Linus' latest rc as well, not sure), this will probably be
> important during initial implementation, not sure how much divergence
> we should expect after this goes through a release through Linus.
> 
> So any thoughts on synching bluetooth and wireless-testing other than
> doing so on a private tree for development purposes?

we don't need this right now. For the initial development of the WiFi
AMP, we will use the fact that you can create HCI RAW devices from a
driver. These are skipped by BlueZ and only show up in hciconfig. That
should be enough for testing.

Regards

Marcel



  reply	other threads:[~2009-09-23 23:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-22 17:01 Synching trees for BT 3.0 and a possible compat-bluetooth Luis R. Rodriguez
2009-09-23 23:27 ` Marcel Holtmann [this message]
2009-09-23 23:30   ` Luis R. Rodriguez

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=1253748426.2931.9.camel@localhost.localdomain \
    --to=marcel@holtmann.org \
    --cc=Jouni.Malinen@atheros.com \
    --cc=gaurav.jauhar@atheros.com \
    --cc=johannes@sipsolutions.net \
    --cc=jothikumar.mothilal@atheros.com \
    --cc=kevin@atheros.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mcgrof@gmail.com \
    --cc=senthilkumar@atheros.com \
    /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