From: Brad Midgley <bmidgley@xmission.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] a2play error...
Date: Mon, 09 Jan 2006 10:28:43 -0700 [thread overview]
Message-ID: <43C29D4B.9030608@xmission.com> (raw)
In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAmaUem1Nm8k+FVVBwbPkbkcKAAAAQAAAAwZyW1fiQXke0+pFdteryAwEAAAAA@gmail.com>
pdjj14
> My environment is 'Redhat9(kernel 2.4.20-8) + bluez-utils,-libs-2.24 +
> bluez-hcidump-1.18 + alsa-libs-1.0.10 + btsco-0.41 + mpg123-0.59r-4'.
do you have to run 2.4.x? if you do, can you update it to 2.4.31 and
apply mh1 from http://www.bluez.org/patches.html ?
I don't believe a2play does anything that requires features in the new
kernels but bluez will work better if you track something current.
> I am modifying the code 'a2play.c'.
>
> Is correct what I do?
>
> I want to know good methods.
I would try to update the kernel as much as you can first, then look at
modifying a2play.c
are you running on an x86 cpu?
> write failed: Connection reset by peer
this may be an underlying problem in bluez.
brad
-------------------------------------------------------
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-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2006-01-09 17:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-09 5:25 [Bluez-devel] Browsing web on cell my phone through bluetooth connection to Linux desktop Blue Hammer
2006-01-09 5:36 ` Henryk Plötz
2006-01-09 9:31 ` Blue Hammer
2006-01-09 14:26 ` [Bluez-devel] a2play error pdjj14
2006-01-09 17:28 ` 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=43C29D4B.9030608@xmission.com \
--to=bmidgley@xmission.com \
--cc=bluez-users@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).