From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] BlueZ and the ALSA support
Date: Sun, 21 Nov 2004 23:45:43 +0100 [thread overview]
Message-ID: <1101077143.7250.83.camel@pegasus> (raw)
In-Reply-To: <41A11275.1090108@dark-reality.de>
Hi Lars,
> | 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?
when you try, expect kernel freezes or crashes. The only place to ask is
the Linux USB developer mailing list, but I think we should first clean
up our URB management mess.
Regards
Marcel
-------------------------------------------------------
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
next prev parent reply other threads:[~2004-11-21 22:45 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
2004-11-21 22:45 ` Marcel Holtmann [this message]
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=1101077143.7250.83.camel@pegasus \
--to=marcel@holtmann.org \
--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