From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] LInux Bluetooth and Audio (OSS) interface
Date: Thu, 25 May 2006 23:49:32 -0600 [thread overview]
Message-ID: <447696EC.4080804@xmission.com> (raw)
In-Reply-To: <c4cf8c660605252058n622d6dfak5ad964349551d662@mail.gmail.com>
Timmy
Maybe you could rewrite btsco.c (the userspace daemon) so it only uses
oss interfaces to the kernel. Hmm... the hooks may not all be there
however. If it could be done, the kernel mod wouldn't really have to
change since you can use alsa-oss-emulation.
There are a lot of directions we could take this. Pure oss isn't one of
the most promising.
I think an interesting option is gstreamer drivers entirely in
userspace. That should embed more easily which is one big strike against
alsa. gst events might cover the complexity we have now in interacting
with a daemon.
Brad
> I am a newbie to bluetooth. It seems that there are no integration
> on linux bluetooth (SCO link) and audio (OSS) interface, so that there
> are no standard API for the user mode audio applications when using or
> not using bluetooth handset.
> Bluetooth-alsa seems to be something like that, but it focuses on
> Bluetooth + ALSA, I am not sure whether it is a good starting point.
>
> Can anyone give me some advice on how to provide an uniform
> interface for user mode audio applications ? Since it could be
> paintful for user mode audio applications to use SCO socket interface
> directly and handle the details for bluetooth handset.
>
> Thanks,
>
> Timmy
>
>
> -------------------------------------------------------
> All the advantages of Linux Managed Hosting--Without the Cost and Risk!
> Fully trained technicians. The highest number of Red Hat certifications in
> the hosting industry. Fanatical Support. Click to learn more
> http://sel.as-us.falkag.net/sel?cmd=k&kid\x107521&bid$8729&dat\x121642
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-05-26 5:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-26 3:58 [Bluez-devel] LInux Bluetooth and Audio (OSS) interface Timmy Li
2006-05-26 5:49 ` Brad Midgley [this message]
2006-05-26 6:11 ` Sowmya Gattupalli
2006-05-26 14:30 ` 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=447696EC.4080804@xmission.com \
--to=bmidgley@xmission.com \
--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 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.