From: Matthew Grant <matthewgrant5@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: Re: Dell Wireless 360 Bluetooth HID devices not being remembered over suspend/reboot
Date: Wed, 21 Jan 2009 21:32:48 +1300 [thread overview]
Message-ID: <b3f4dcd00901210032g2d0056afx2e03077272436046@mail.gmail.com> (raw)
In-Reply-To: <1232291616.5095.13.camel@californication>
Hi,
Been a few days as I have been busy.
On Mon, Jan 19, 2009 at 4:13 AM, Marcel Holtmann <marcel@holtmann.org> wrote:
> check with "hciconfig hci0 revision" and "bccmd buildname" (both as
> root) if they have a special Dell firmware running on it. If not then
> there can be still a Dell custom application running in the VM of the
> Bluetooth chip.
Here they go:
en-gedi: -root- [~]
# bccmd buildname
Build name: cyt_8unified_fl_bt2.0_kymodo_21d_0702212310_encr56 2007-02-21
en-gedi: -root- [~]
# hciconfig hci0 revision
hci0: Type: USB
BD Address: 00:21:86:D0:37:F0 ACL MTU: 310:10 SCO MTU: 64:8
Build 4315
Chip version: BlueCore4-External
Max key size: 56 bit
SCO mapping: HCI
Does this show anything unusual? I don't think this thing is standard.
Running Vista home, everything works across reboots. I did this as a
lot of the information posted about Dell computers suggested doing
this. I am also going to try running 3.36 bluez and see if that
helps.
> Best bet is to ask Mario from Dell if he can help us out here and maybe
> make HID/HCI switching persistent across reboots. If not then we might
> have to write a bluetoothd plugin that does the job for us.
Is Mario on this list? It would be good if he is party to this.
Thanks for getting back to me!
Regards,
Matthew Grant
prev parent reply other threads:[~2009-01-21 8:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-16 22:41 Dell Wireless 360 Bluetooth HID devices not being remembered over suspend/reboot Matthew Grant
2009-01-18 15:13 ` Marcel Holtmann
2009-01-20 20:10 ` Mario Limonciello
2009-01-21 8:32 ` Matthew Grant [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=b3f4dcd00901210032g2d0056afx2e03077272436046@mail.gmail.com \
--to=matthewgrant5@gmail.com \
--cc=linux-bluetooth@vger.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