From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] LInux Bluetooth and Audio (OSS) interface
Date: Fri, 26 May 2006 08:30:41 -0600 [thread overview]
Message-ID: <44771111.60404@xmission.com> (raw)
In-Reply-To: <fe0a97c20605252311k20a25dffyfb37603a5d322d6f@mail.gmail.com>
Sowmya
Are you suggesting we wouldn't need the kernel mod at all?
The only way to avoid the kernel mod for an oss client is to do a
shared-object interceptor hack like libaoss that catches
read/write/ioctl to /dev/dsp and processes it in some other way.
Brad
> But Brad.... incase we write the OSS Api dependency in btsco we need not
> have to upgrade the kernel to have kernel with inbuilt ALSA drivers.....
> I feel this is the advantage we are filling up with SCO amd OSS appln
> incase if we have to.... isn't it??
>
> On 5/26/06, *Brad Midgley* <bmidgley@xmission.com
> <mailto:bmidgley@xmission.com>> wrote:
>
> 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.
-------------------------------------------------------
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
prev parent reply other threads:[~2006-05-26 14:30 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
2006-05-26 6:11 ` Sowmya Gattupalli
2006-05-26 14:30 ` Brad Midgley [this message]
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=44771111.60404@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).