public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Peter Wurmsdobler <peter@wurmsdobler.org>
Cc: Bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] rfcomm tty lost packets
Date: Fri, 05 Sep 2008 18:55:55 +0200	[thread overview]
Message-ID: <1220633755.6714.83.camel@californication> (raw)
In-Reply-To: <48C1160B.7060705@wurmsdobler.org>

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

           reply	other threads:[~2008-09-05 16:55 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <48C1160B.7060705@wurmsdobler.org>]

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=1220633755.6714.83.camel@californication \
    --to=marcel@holtmann.org \
    --cc=Bluez-users@lists.sourceforge.net \
    --cc=peter@wurmsdobler.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