linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nikolay Kachanov <nikolay.kachanov@gmail.com>
To: Gustavo Padovan <padovan@profusion.mobi>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: BCM2035 problem
Date: Thu, 04 Aug 2011 10:05:50 +0400	[thread overview]
Message-ID: <4E3A36BE.5050409@gmail.com> (raw)
In-Reply-To: <20110803174652.GB28119@joana>

[-- Attachment #1: Type: text/plain, Size: 885 bytes --]

Hi Gustavo,

On 08/03/2011 09:46 PM, Gustavo Padovan wrote:
> * Nikolay Kachanov <nikolay.kachanov@gmail.com> [2011-08-03 09:15:40 +0400]:
>> With all versions of bluez above 4.84, including 4.96, my cellular
>> phone and PC can pair via Broadcom BCM2035 USB dongle, but every
>> attempt of file exchange ends with a complain about other side is not
>> responding.
>> Is that a bug or BCM2035 is not supported any more?
>> My OS is Arch Linux, both i686 and x86_64. I can provide more
>> information if necessary.
> 
> An hcidump output would be good. Also send the log of obexd -nd.

Please see attachment. I'm sending you the output of obex-data-server
-nd, not obexd. As far as I understand, obex-data-server is installed on
my PCs as a mandatory dependency of gnome-shell. There is obexd-server
package in official Arch repository, but it conflicts with obex-data-server.

Nikolay

[-- Attachment #2: dump.tar.gz --]
[-- Type: application/x-gzip, Size: 3677 bytes --]

      reply	other threads:[~2011-08-04  6:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-03  5:15 BCM2035 problem Nikolay Kachanov
2011-08-03 17:46 ` Gustavo Padovan
2011-08-04  6:05   ` Nikolay Kachanov [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=4E3A36BE.5050409@gmail.com \
    --to=nikolay.kachanov@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=padovan@profusion.mobi \
    /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).