From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Comments about the Logitech/HP stereo headphones
Date: Sun, 24 Apr 2005 14:28:42 -0600 [thread overview]
Message-ID: <426C017A.3040500@xmission.com> (raw)
In-Reply-To: <20050424171103.GB12143@externe.net>
Guylhem
> Brad who now has an xscale board now realise how much precious space
> is. Honnestly using alsa is only good if you consider existing
> applications.
I think the bottom line is that the general solution (alsa plugin)
doesn't scale down to very small devices.
That is fine. Very small devices do a lot of things differently and we
will continue to maintain something like a2play. It should be improved
to be a little more general (eg no hardcoded usleep) and have more
features (like mp3 decoding, live line-in streaming) but the basic
operation wouldn't change.
Apps on the desktop should get used to using an alsa plugin and then we
have the freedom to move whatever is appropriate into the kernel without
changing the app interface. I don't believe we'd ever move "enough" into
the kernel to eliminate alsa-lib.
One thing I've been trying on my gumstix is experimenting to see if the
plugin design might scale down to a fairly capable arm board (xscale
400mhz/64mb ram). alsa-lib is big but it might work. Another thing I've
been doing is tweaking our project so our stuff is easily cross-compiled
and works well as a buildroot module.
Brad
-------------------------------------------------------
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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-04-24 20:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-24 12:18 [Bluez-devel] Comments about the Logitech/HP stereo headphones Marcel Holtmann
2005-04-24 13:47 ` Guylhem Aznar
2005-04-24 14:28 ` Brad Midgley
2005-04-24 15:23 ` Marcel Holtmann
2005-04-24 15:16 ` Marcel Holtmann
2005-04-24 17:11 ` Guylhem Aznar
2005-04-24 18:09 ` Marcel Holtmann
2005-04-24 20:28 ` Brad Midgley [this message]
2005-04-24 16:19 ` Henryk Plötz
2005-04-24 16:48 ` Guylhem Aznar
2005-04-24 18:15 ` Marcel Holtmann
2005-04-24 18:12 ` Marcel Holtmann
2005-04-24 14:04 ` Brad Midgley
2005-04-24 14:34 ` Brad Midgley
2005-04-24 15:30 ` Marcel Holtmann
2005-04-25 17:39 ` Brad Midgley
-- strict thread matches above, loose matches on Subject: below --
2005-04-24 15:16 Mayank Batra
2005-04-24 15:35 ` Marcel Holtmann
2005-04-26 12:46 Mayank Batra
2005-04-26 13:28 ` Marcel Holtmann
2005-04-28 12:10 Mayank Batra
2005-04-29 9:51 ` Marcel Holtmann
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=426C017A.3040500@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.