From: "Gustavo F. Padovan" <gustavo@padovan.org>
To: Mike Tsai <Mike.Tsai@Atheros.com>
Cc: "linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
"marcel@holtmann.org" <marcel@holtmann.org>
Subject: Re: [RFC] Release Plan for ERTM, Streaming Mode, FCS and SAR on L2CAP
Date: Tue, 23 Mar 2010 21:57:36 -0300 [thread overview]
Message-ID: <20100324005736.GA10636@vigoh> (raw)
In-Reply-To: <35B17FE5076C7040809188FBE7913F983A1DDCF3F4@SC1EXMB-MBCL.global.atheros.com>
Hi Mike,
Again, no top posting, please. ;)
* Mike Tsai <Mike.Tsai@Atheros.com> [2010-03-23 16:36:46 -0700]:
> Hi Gus,
>
> My comments will be that it is probably better to implement eRTM mode first because many existing implementations do not support stream mode but definitely support eRTM mode.
They are under development already. Streaming Mode, FCS and SAR is
implemented and need some stabilization, heavy tests and bug fixes only.
ERTM is not completely done and need some work on it already. That's why
I wanna delay ERTM's upstream.
>
> You shall be able to verify the testing with Bluetooth SIG PTS,
Sure. The code will be tested with PTS before go upstream.
>
> Thanks,
>
> Mike
>
> -----Original Message-----
> From: linux-bluetooth-owner@vger.kernel.org [mailto:linux-bluetooth-owner@vger.kernel.org] On Behalf Of Gustavo F. Padovan
> Sent: Tuesday, March 23, 2010 1:39 PM
> To: linux-bluetooth@vger.kernel.org
> Cc: marcel@holtmann.org
> Subject: [RFC] Release Plan for ERTM, Streaming Mode, FCS and SAR on L2CAP
>
> Hi People,
>
> I was thinking about a release plan for Enhanced Retransmission Mode,
> Streaming Mode, Frame Check Sequence(FCS) and Segmentation and
> Reassembly(SAR).
>
> 2.6.35: Upstream Streaming Mode, FCS, SAR and add a sub-menu option
> to L2CAP at Kconfig for ERTM with an EXPERIMENTAL flag. So we will have
> a chance to test ERTM more intensively.
>
> 2.6.36: Upstream ERTM. After that ERTM will be the default mode with
> SOCK_STREAM and also enabled by default under L2CAP. If you think it's
> not worth release Streaming Mode, FCS and SAR without ERTM we can
> upstream them together on 2.6.36.
>
> Comments, ideas?
>
> --
> Gustavo F. Padovan
> http://padovan.org
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Gustavo F. Padovan
http://padovan.org
prev parent reply other threads:[~2010-03-24 0:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-23 20:39 [RFC] Release Plan for ERTM, Streaming Mode, FCS and SAR on L2CAP Gustavo F. Padovan
2010-03-23 23:36 ` Mike Tsai
2010-03-24 0:57 ` Gustavo F. Padovan [this message]
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=20100324005736.GA10636@vigoh \
--to=gustavo@padovan.org \
--cc=Mike.Tsai@Atheros.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.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).