public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
* Re: [Bluez-users] rfcomm tty lost packets
       [not found] <48C1160B.7060705@wurmsdobler.org>
@ 2008-09-05 16:55 ` Marcel Holtmann
  0 siblings, 0 replies; only message in thread
From: Marcel Holtmann @ 2008-09-05 16:55 UTC (permalink / raw)
  To: Peter Wurmsdobler; +Cc: Bluez-users

Hi Peter,

> It appears that rfcomm tty packets are lost on my linux 2.6.22 based 
> embedded system at the startup, but also during the bluetooth 
> connection. There are patches to fix that on :
> 
> http://git.kernel.org/?p=linux%2Fkernel%2Fgit%2Faegl%2Flinux-2.6.git&a=search&h=HEAD&st=commit&s=kenzior 
> 
> 
> However, these patches appear to be against a newer version of the 
> kernel. Is it safe to apply the patches mentioned above manually?

that kernel is ancient and the patches might work or not. I am not
planning to look through the list of changes and check if it might
create any possible race conditions.

> Is there an alternative to "upgrade" the bluez part of the kernel and 
> apply the patches?

No.

Regards

Marcel



-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2008-09-05 16:55 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <48C1160B.7060705@wurmsdobler.org>
2008-09-05 16:55 ` [Bluez-users] rfcomm tty lost packets Marcel Holtmann

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox