From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] hci_scodata_packet: hci0 SCO packet for unknown connection handle 1
Date: Mon, 25 Feb 2008 02:29:13 +0100 [thread overview]
Message-ID: <261228FD-F5FF-4D64-9D65-FC873DF95F9F@holtmann.org> (raw)
In-Reply-To: <d89ddf300802241225l1a352768x94afccdc2b120be6@mail.gmail.com>
Hi Brad,
>> I follow the steps in http://wiki.bluez.org/wiki/HOWTO/AudioDevices
>> Feb 23 20:06:37 pc kernel: [20254.788127] hci_scodata_packet: hci0
>> SCO packet for unknown connection handle 1
>
> I've added the kernel patch that is supposed to handle this problem to
> the end of the wiki page. Please let us know if it helps. It's
> ostensibly going to be an issue if you have a bluetooth adapter
> capable of esco but your headset is not.
the patch you sent me is fully broken. First of all the coding style
is wrong. Does nobody have learned this by now? I always look for that
first before even reading the patch. Second the case where an
ESCO_LINK returns NULL is broken and will fall over and crash.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2008-02-25 1:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-24 1:09 [Bluez-users] hci_scodata_packet: hci0 SCO packet for unknown connection handle 1 Brian J. Murrell
2008-02-24 20:25 ` Brad Midgley
2008-02-25 1:02 ` Brian J. Murrell
2008-02-25 1:29 ` Marcel Holtmann [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=261228FD-F5FF-4D64-9D65-FC873DF95F9F@holtmann.org \
--to=marcel@holtmann.org \
--cc=bluez-users@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