From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] linux 2.4.20 & alsa 0.9.6
Date: Sun, 08 Jan 2006 18:33:05 -0700 [thread overview]
Message-ID: <43C1BD51.9090703@xmission.com> (raw)
In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAmaUem1Nm8k+FVVBwbPkbkcKAAAAQAAAADKpAtBuY3EiXO2W2Etn2/QEAAAAA@gmail.com>
pdjj14
I understand there are a lot of embedded platforms that are still on
kernel 2.4. You may be able to get audio working with 2.4.x using old
versions of everything, but you aren't likely to get help on the mailing
lists for doing that. Good luck.
Brad
> Thank you Brad...
> I have a question...
> To communication between PC and Headset using the bluez, I don't work in
> my environment?
> I can change bluez-utils' version, but, I can't change kernel version.
> Are there other methods?
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2006-01-09 1:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060106055011.0AA19F94F@sc8-sf-spam2.sourceforge.net>
2006-01-06 5:59 ` [Bluez-devel] linux 2.4.20 & alsa 0.9.6 pdjj14
2006-01-06 6:13 ` Brad Midgley
2006-01-06 6:42 ` pdjj14
2006-01-09 1:33 ` 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=43C1BD51.9090703@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).