From: Pavel Machek <pavel@ucw.cz>
To: Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>,
kernel list <linux-kernel@vger.kernel.org>
Cc: "Pali Rohár" <pali.rohar@gmail.com>, sre@kernel.org
Subject: Bluetooth on N900 status
Date: Thu, 16 Jun 2016 00:43:08 +0200 [thread overview]
Message-ID: <20160615224308.GA5671@amd> (raw)
In-Reply-To: <575F0176.2060609@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1872 bytes --]
Hi!
(I added l-k to cc list).
> Pavel, while we are at it, could you briefly explain what has happened with
> bluetooth patches you were trying to upstream? I can take over those, but it
> is not clear to me what exactly needs to be done.
I thought they stopped working and some ugly bisect would be needed,
but I tried again, and it seems they still work in v4.7:
root@n900:/my/modules# ./run
hci0 Set Public Address complete, options:
Inquiring ...
6C:23:B9:9B:57:7D clock offset: 0x5074 class:
0x0020fc
hci0: Type: BR/EDR Bus: UART
BD Address: 01:02:03:04:05:06 ACL MTU: 1017:4 SCO
MTU: 64:1
DOWN
RX bytes:1652 acl:0 sco:0 events:101 errors:0
TX bytes:10692 acl:0 sco:0 commands:99
errors:0
root@n900:/my/modules# cat run
#!/bin/bash
chvt 1
insmod nokia_h4p.ko
rmmod nokia_h4p
insmod nokia_h4p.ko
hciconfig hci0 up
hciconfig hci0 down
rmmod nokia_h4p
insmod nokia_h4p.ko
hciconfig hci0 up
hciconfig hci0 down
../bluez-5.26/tools/btmgmt public-addr 01:02:03:04:05:06
hciconfig hci0 up
hcitool inq
hciconfig hci0 down
hciconfig hci0
rmmod nokia_h4p
root@n900:/my/modules#
...which is kind of interesting given the dmesg:
[ 206.219451] Bluetooth: hci0 command 0xfc4c tx timeout
[ 209.219482] nokia_h4p 4806c000.serial: ...sending cmd fc4c len 255
failed -110
[ 209.219543] nokia_h4p 4806c000.serial: Cannot read firmware
[ 209.219573] Bluetooth: hci_setup: something failed, should do the
clean up
[ 219.272918] nokia_h4p 4806c000.serial: Registering HCI H4P device
Patch is attached. Probably contains some unneccessary changes. Config
does not work with video, so you may want to supply working config or
fix it.
So that's the latest version, if you want to play.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: delme.gz --]
[-- Type: application/gzip, Size: 59160 bytes --]
parent reply other threads:[~2016-06-15 22:43 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <575F0176.2060609@gmail.com>]
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=20160615224308.GA5671@amd \
--to=pavel@ucw.cz \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pali.rohar@gmail.com \
--cc=sre@kernel.org \
/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