public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Lars Grunewaldt <lgw@dark-reality.de>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] BlueZ and the ALSA support
Date: Sun, 21 Nov 2004 23:11:01 +0100	[thread overview]
Message-ID: <41A11275.1090108@dark-reality.de> (raw)
In-Reply-To: <1101069548.7250.77.camel@pegasus>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Marcel Holtmann wrote:
|>don't you think it should be possible to
|>a) block the submit of new urbs when a change notify has arrived
|>b) queue until the queue is empty
|>c) change the endpoint setting and release the block
|>
|>I don't know to which bad runs or locks this could lead...
|
|
| To be honest, I don't know. This ISOC stuff is still a mystery to me and
| so far I don't know of any Linux driver that is using the ISOC transfers
| and have to change the alternate setting at the same time. Selecting it
| at probe() time is very easy.


Maybe we simply have to try what happens *shudder*... any ideas whom we
could ask for more information? linux usb devlist?

cu,
~  Lars

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFBoRJ1QWC6DTWkDAoRAnonAKCur76BoMJjdiW1C1Hr4+1UNXStgQCeNQR9
+PjiFwiOMa8LrOTjDE0/xMw=
=f1x7
-----END PGP SIGNATURE-----


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2004-11-21 22:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-21  0:01 [Bluez-devel] BlueZ and the ALSA support Marcel Holtmann
2004-11-21  2:10 ` Lars Grunewaldt
2004-11-21  5:29 ` Brad Midgley
2004-11-21 17:14   ` Marcel Holtmann
2004-11-21 17:41     ` Lars Grunewaldt
2004-11-21 18:26       ` Marcel Holtmann
2004-11-21 20:13         ` Lars Grunewaldt
2004-11-21 20:39           ` Marcel Holtmann
2004-11-21 22:11             ` Lars Grunewaldt [this message]
2004-11-21 22:45               ` Marcel Holtmann
2004-11-21 22:59                 ` Lars Grunewaldt
2004-11-21 20:12     ` Brad Midgley
2004-11-21 20:25       ` Marcel Holtmann
2004-11-22  4:09         ` Brad Midgley

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=41A11275.1090108@dark-reality.de \
    --to=lgw@dark-reality.de \
    --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