From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Cc: bluez-devel@lists.sf.net
Subject: Re: [Bluez-devel] Trouble with bluetooth headset
Date: Thu, 28 Jun 2007 17:52:34 +0200 [thread overview]
Message-ID: <1183045954.9499.35.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <BAY111-F1375482293258DA33AFC60C1090@phx.gbl>
Hi Clark,
> So you think the problem shown in the log is related to the kernel version,
> not just some configuration issue? I think the bluetooth part is working it
> just rejects the connect for some reason.
I don't even know, but I am simply not chasing any bugs from people that
don't run at least a reasonable new kernel. And 2.6.10 is ancient. If
someone else wanna look at it, it is fine by me, but I won't until you
have this issue with a recent kernel and latest bluez-utils.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-06-28 15:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <01c7b97e$58d4afe0$5a8bbe54@olavoo>
2007-06-28 13:40 ` [Bluez-devel] Trouble with bluetooth headset Clark Pope
2007-06-28 14:59 ` Marcel Holtmann
2007-06-28 15:48 ` Clark Pope
2007-06-28 15:52 ` Marcel Holtmann [this message]
2007-06-30 18:09 ` Clark Pope
2007-07-15 18:01 ` [Bluez-devel] PS3 compatibility list? Clark Pope
2007-07-17 4:21 ` Simon Ruggier
2007-07-17 17:00 ` TJ OConnor
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=1183045954.9499.35.camel@aeonflux.holtmann.net \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sf.net \
--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