From: Klaus <projectu@gmail.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Unable to set number of SCO buffers : please upgrade your Kernel !
Date: Sun, 29 Apr 2007 20:58:49 +0000 (UTC) [thread overview]
Message-ID: <loom.20070429T224443-848@post.gmane.org> (raw)
In-Reply-To: 4634C553.6080400@xmission.com
Brad Midgley <bmidgley <at> xmission.com> writes:
>
> you're looking at the upatched sco.c or maybe one hunk failed.
> sco-flowcontrol-v4.2.diff has changes for setsockopt() around line 550.
hrmp, my fault! You are so right, and everything is working fine with the patch!
Now I just have to figure out how to use the headset from Ekiga.
(If you are curious, then I had updated my Fedora kernel-2.6.spec file with the
patch - but forgot the %patchxxx to actually enable the patch).
Thanks, Klaus
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-04-29 20:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-15 9:57 [Bluez-devel] Unable to set number of SCO buffers : please upgrade your Kernel ! Brandon Philips
2007-04-15 18:34 ` Brad Midgley
2007-04-16 7:35 ` Brandon Philips
2007-04-24 18:48 ` Marc Haber
2007-04-29 12:34 ` Klaus
2007-04-29 16:17 ` Klaus
2007-04-29 16:18 ` Brad Midgley
2007-04-29 20:58 ` Klaus [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-04-22 6:52 John Frankish
2007-04-22 16:50 ` Brad Midgley
2007-04-23 4:07 ` John Frankish
2007-04-24 13:45 ` Brad Midgley
2007-04-25 5:56 ` John Frankish
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=loom.20070429T224443-848@post.gmane.org \
--to=projectu@gmail.com \
--cc=bluez-devel@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