From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] ACL connection handle
Date: Thu, 27 Mar 2008 16:10:32 +0100 [thread overview]
Message-ID: <A0B79457-4255-49EB-BDA5-A3D2B903B75C@holtmann.org> (raw)
In-Reply-To: <d89ddf300803262043qba89bb8r1a24ce91b04b5e45@mail.gmail.com>
Hi Brad,
>> shouldn't be a big problem, but in general this belongs into the
>> kernel since userspace is not dealing with ACL and SCO/eSCO
>> connection
>> handling.
>
> I'll agree it would be cleaner in kernel. If it's to be handled in the
> kernel then I think we need some way like an ioctl so the userspace
> app can tell the kernel, before opening the sco connection, whether it
> should happen on pcm or hci. It would be handy to have a way for the
> app to ask the kernel where sco is going, in case the preferred
> transport wasn't available.
we would need to push the actual code into the drivers since the core
has to stay vendor free. For selecting the routing we could use a
socket option.
Regards
Marcel
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2008-03-27 15:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-25 12:01 [Bluez-users] ACL connection handle Paul
2008-03-25 12:16 ` Brad Midgley
2008-03-25 13:00 ` Paul
2008-03-25 14:39 ` Brad Midgley
2008-03-26 16:27 ` Marcel Holtmann
2008-03-27 3:43 ` Brad Midgley
2008-03-27 15:10 ` Marcel Holtmann [this message]
2008-03-28 3:05 ` 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=A0B79457-4255-49EB-BDA5-A3D2B903B75C@holtmann.org \
--to=marcel@holtmann.org \
--cc=bluez-users@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