linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Frédéric DALLEAU" <frederic.dalleau@palmsource.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] A2DP and Alsa Plugin
Date: Wed, 02 Aug 2006 16:54:29 +0200	[thread overview]
Message-ID: <44D0BCA5.5000906@palmsource.com> (raw)
In-Reply-To: <44D0B1F7.2@xmission.com>

HI brad,

>Is the memory footprint acceptable when introducing the alsa dependency
>on your embedded platform? In my experience lib-alsa itself builds to
>about 800KB on arm. The difference in cpu load is probably negligible.
>
>  =

>
Depends on what you need, at first I wanted to see how small it could be.
I had similar result by dropping alsa link from the daemon saved me a =

bit less than 1Mb ram usage as opposed to 2.6 with alsa or something =

like that.
-rwxr-xr-x    1   100   100       1188601 Jul 26  2006 =

/usr/lib/libasound.so.2.0.0

Do you min memory or disk footprint? As the daemon did not need alsa at =

all, it was one free megabit! But this may change one day ...

Is it related to the build problem Andrew had? If so I think the linking =

can be put back for now. I will do it manually if I really need it...

Fr=E9d=E9ric


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2006-08-02 14:54 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-11  9:15 [Bluez-devel] A2DP and Alsa Plugin Frederic Dalleau
2006-05-12 17:10 ` Brad Midgley
2006-05-17 16:51   ` Frédéric DALLEAU
2006-05-17 17:40     ` Brad Midgley
2006-05-29  7:02     ` Brad Midgley
2006-05-30 10:20       ` Frédéric DALLEAU
2006-05-30 16:38         ` Brad Midgley
2006-05-30 20:28         ` Brad Midgley
2006-08-02 14:08 ` Brad Midgley
2006-08-02 14:54   ` Frédéric DALLEAU [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-05-10  8:17 Frederic Dalleau
2006-05-10 17:49 ` Brad Midgley
2006-05-05 12:38 Frederic Dalleau
2006-05-05 17:24 ` Brad Midgley
2006-05-04 15:58 Frederic Dalleau
2006-05-04 17:19 ` Brad Midgley
2006-05-04 15:34 Frederic Dalleau
2006-05-04 13:30 Frederic Dalleau
2006-05-04 14:36 ` Brad Midgley
2006-05-04 14:50 ` Brad Midgley
2006-05-04 15:20 ` 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=44D0BCA5.5000906@palmsource.com \
    --to=frederic.dalleau@palmsource.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).