public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: approach <wuyunb@neusoft.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] When can it support bluetooth spec 1.2?
Date: Thu, 22 Apr 2004 06:31:27 +0000 (UTC)	[thread overview]
Message-ID: <loom.20040422T082709-98@post.gmane.org> (raw)

 The spec1.2 do update some function( such as Flow Control , retransmission on 
L2CAP ).I want to know when bluez can support bluetooth spec1.2 ).
 Thank you so much!



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

             reply	other threads:[~2004-04-22  6:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-22  6:31 approach [this message]
2004-04-22  9:15 ` [Bluez-devel] When can it support bluetooth spec 1.2? 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=loom.20040422T082709-98@post.gmane.org \
    --to=wuyunb@neusoft.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox