All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brad Midgley <bmidgley@xmission.com>
To: BlueZ development <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 10:18:27 -0600	[thread overview]
Message-ID: <4634C553.6080400@xmission.com> (raw)
In-Reply-To: <loom.20070429T141323-596@post.gmane.org>

Klaus

> In plugz/../pcm_sco.c: sco_headset_hw_params(), 
>    setsockopt(...,SOL_SCO,...) is called, but it fails with ENOPROTOOPT
> "Protocol not available".
> 
>    setsockopt() for protocol level SOL_SCO is implemented in the kernel in
> net/bluetooth/sco.c: sco_sock_setsockopt(), but this function only does one
> thing - it returns ENOPROTOOPT:
> 
> ...
>         switch (optname) {
>         default:
>                 err = -ENOPROTOOPT;
>                 break;
>         }
> ...
> 
> I am a bit curious - how can this work for anybody?

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.

we did actually change the constants for the setsockopt call, but if you
have a recently updated plugz it should actually try both the old and
new constants.

brad

-------------------------------------------------------------------------
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

  parent reply	other threads:[~2007-04-29 16:18 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 [this message]
2007-04-29 20:58       ` Klaus
  -- 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=4634C553.6080400@xmission.com \
    --to=bmidgley@xmission.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.