From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] bluetooth issues with 2.4.19 kernel.
Date: Thu, 06 Oct 2005 12:14:15 +0200 [thread overview]
Message-ID: <1128593655.5492.32.camel@localhost.localdomain> (raw)
In-Reply-To: <4344F97C.5010206@ncoretech.com>
Hi Zaheer,
> I am having other issues with 2.6 we haven't started working on it yet,
> and getting Bluetooth working on 2.4.19 will solve all my issues.
> Hope you understand. This is for an immediate requirement put by a
> customer.
> Request you guys to please come up with any solution.
please understand that nobody pays me for working on BlueZ and so I
don't think that I will spend my rare freetime to please a costumer of
you. I am happy to help you to resolve any issue based on a 2.6 kernel,
but the 2.4 series has been closed a long time ago.
However you might find others to help you. So include the output of
"hciconfig -a" and "hcidump -X -V". Also make sure that you run the
latest versions of the BlueZ library, utils etc.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2005-10-06 10:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-06 9:31 [Bluez-devel] bluetooth issues with 2.4.19 kernel Zaheer Ahamed
2005-10-06 9:59 ` Marcel Holtmann
2005-10-06 10:16 ` Zaheer Ahamed
2005-10-06 10:14 ` Marcel Holtmann [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=1128593655.5492.32.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--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