Hi Arjan, > > I would like to know how will be the final kernel version that will be > > shipped with MeeGo 1.1.0.0. Because we are working in a Health Device > > Protocol (HDP) implementation for Bluez that relies in the > > implementation of Enhanced Retransmission Mode (ERTM) in the Bluetooth > > L2CAP kernel layer. The current MeeGo kernel has this feature > > enabled, but with some issues that are already fixed only in the > > bluetooth-next git tree (to be available in the 2.6.36 kernel version). > > currently, for the october release, we're looking at 2.6.35 (2.6.36 will > just not be out in time). > > are the changes you need considered for a -stable kernel ? > (we do follow those)
no they won't be. The 2.6.35 kernel can potentially be used for HDP, but we didn't finish the ERTM support on time. So there will be some hickups when it comes to ERTM. My recommendation is to NOT enable ERTM by default (yes, there is a kernel config option). Then for testing it can be enabled via l2cap.enable_ertm=1 kernel module option. The support for ERTM is compiled in anyway. The config option only decides about the default for it. The first kernel where upstream is enabling ERTM by default will be 2.6.36 kernel. It will be also the first kernel that got extensive testing via Bluetooth SIG test suite. Everything before 2.6.36 is just not ready for ERTM usage. Regards Marcel _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
