All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Lars Grunewaldt <lgw@dark-reality.de>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] question: what does this patch from snd-bt-sco do?
Date: Thu, 17 Jun 2004 22:28:16 +0200	[thread overview]
Message-ID: <1087504096.4309.76.camel@pegasus> (raw)
In-Reply-To: <40D1FA27.20407@dark-reality.de>

Hi Lars,

> you could as well say "an elephant won't fit into a mousewhole until it
> get's a dynamic interface". Of course mulaw and alaw differ from pcm/16
> bit only because they are 8bit/sample. so what. Would not work if it
> would be 7 or 9 bit, either. Also it's not likely that the bit count
> will change sooner or later :)

that is not the point here. The H:2 alternate setting for ISOC interface
only differs between 8bit or 16bit and the number of SCO connections.

> Suggestions are welcome. If anyone has an idea how to improve this
> "alternate setting" handling, i.e. make it possible for an
> application/driver to set the setting in runtime without rewriting the
> whole code, that would be a great thing.

Only the hci_usb driver has to take care of it and the needed notify()
framework from the BlueZ core is already in place.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2004-06-17 20:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-18 10:34 [Bluez-devel] question: what does this patch from snd-bt-sco do? Lars Grunewaldt
2004-05-18 10:44 ` Marcel Holtmann
2004-05-18 10:53 ` Jonathan Paisley
2004-05-18 11:06   ` Lars Grunewaldt
2004-05-18 11:35     ` Lars Grunewaldt
2004-05-18 11:59       ` Marcel Holtmann
2004-05-18 11:57     ` Marcel Holtmann
2004-05-18 13:37       ` Lars Grunewaldt
2004-05-18 14:00         ` Marcel Holtmann
2004-06-16 22:49           ` Lars Grunewaldt
2004-06-16 23:06             ` Marcel Holtmann
2004-06-17  0:04               ` Lars Grunewaldt
2004-06-17  0:24                 ` Marcel Holtmann
2004-06-17 11:24                   ` Jonathan Paisley
2004-06-17 13:35                     ` Lars Grunewaldt
2004-06-17 15:58                       ` Marcel Holtmann
2004-06-17 20:08                         ` Lars Grunewaldt
2004-06-17 20:28                           ` 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=1087504096.4309.76.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=lgw@dark-reality.de \
    /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.