public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Suriyan" <suriyan@netgadgets.co.th>
To: <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] Re: Re: Re: Re: multi rfcomm/sco connection
Date: Wed, 12 Jan 2005 21:12:18 +0700	[thread overview]
Message-ID: <020801c4f8b0$b9cb2f90$6f04a8c0@ZBOX> (raw)

Hi Lars,

> I looked into this problem back "than", but due to a shortage of time I
> never had a chance to really fix this (Marcel stated that the best thing
> would be a complete rewrite of hci_usb anyway).

I have try to make change in hci_usb.c first.

> There should be plenty of discussion in the mailing list archive about
> how to fix the stuff and how it might be done (main problem was the
> interrupt context in the notify function and the not-send urbs (queue
> must be empty before setting the new alternate setting...)

By added debug code for checking interrupt context on serveral functions
in hci_usb.c, I cannot found any functions that in not in_interrupt
context except in hci_usb_probe().

Then I added ioctl() in hci_usb.c and call it from sco_connect() [sco.c]
that not in_interrupt context, it does dynamically change alternate setting
vary by sco_num but it's work only for outgoing connection. However this
solution is not recommended by Marcel previously that I used to proposed.

> would be great if you could fix it, as I don't think I'll have time for
> this in the next... months... :(

If you have better solution to fix it please let me known before. 

Thanks.

Regards,
Suriyan.




-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

                 reply	other threads:[~2005-01-12 14:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='020801c4f8b0$b9cb2f90$6f04a8c0@ZBOX' \
    --to=suriyan@netgadgets.co.th \
    --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