public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Clark Pope" <cepope13@hotmail.com>
To: bluez-devel@lists.sourceforge.net
Cc: bluez-devel@lists.sf.net
Subject: Re: [Bluez-devel] Trouble with bluetooth headset
Date: Sat, 30 Jun 2007 14:09:48 -0400	[thread overview]
Message-ID: <BAY111-F3396AF6D1AA97A5F3F713CC10F0@phx.gbl> (raw)
In-Reply-To: <1183045954.9499.35.camel@aeonflux.holtmann.net>




>From: Marcel Holtmann <marcel@holtmann.org>
>Reply-To: BlueZ development <bluez-devel@lists.sourceforge.net>
>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
>
>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

Guess I should clarify, the original base was 2.6.10 but montavista has 
about 1200 patches applied to it so I'm not sure what the true rev level is 
compared to the stock kernel tree. But the other bluetooth devices seem to 
work okay. Just seems something odd particularly for audio and this 
authentication business with the headset. Any suggestions at all are 
appreciated. -Clark

_________________________________________________________________
Like puzzles? Play free games & earn great prizes. Play Clink now. 
http://club.live.com/clink.aspx?icid=clink_hotmailtextlink2


-------------------------------------------------------------------------
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

  reply	other threads:[~2007-06-30 18:09 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
2007-06-30 18:09         ` Clark Pope [this message]
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=BAY111-F3396AF6D1AA97A5F3F713CC10F0@phx.gbl \
    --to=cepope13@hotmail.com \
    --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