From: Max Krasnyansky <maxk@qualcomm.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] What's the purpose of the new btusb driver ?
Date: Sat, 27 Oct 2007 23:01:15 -0700 [thread overview]
Message-ID: <472425AB.9080802@qualcomm.com> (raw)
In-Reply-To: <1193352893.6184.301.camel@violet>
Marcel Holtmann wrote:
> Hi Max,
>
>> Sounds good. Thanks for the explanation.
>
> any time :)
>
> I heard rumors that Qualcomm is working on a BlueZ based project.
Hmm. Heard from whom ?
> Any chance you are coming back to help me out with the kernel stuff. All
> this new Alternate MAC/PHY stuff is a lot of work.
It is ? I haven't been following BT spec development. I get these emails
from SIG (I'm still subscribed to their mailing list). But they are being
redirected to /dev/null because of lack of time.
Can you give me some pointers to that MAC/PHY stuff you're talking about ?
Is it in the latest spec ?
Max
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-10-28 6:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-23 7:52 What's the purpose of the new btusb driver ? Max Krasnyansky
2007-10-23 11:35 ` [Bluez-devel] " Marcel Holtmann
2007-10-23 16:23 ` Max Krasnyansky
2007-10-25 22:54 ` [Bluez-devel] " Marcel Holtmann
2007-10-28 6:01 ` Max Krasnyansky [this message]
2007-10-28 15:35 ` Tom Allebrandi
2007-10-28 17:49 ` Marcel Holtmann
2007-11-10 19:20 ` Max Krasnyansky
2007-11-11 1:53 ` Marcel Holtmann
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=472425AB.9080802@qualcomm.com \
--to=maxk@qualcomm.com \
--cc=bluez-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.