From: "Odysseus Flappington" <deriziotis@gmail.com>
To: "Marcel Holtmann" <marcel@holtmann.org>
Cc: "Dave Young" <hidave.darkstar@gmail.com>,
"BlueZ users" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] hciconfig hci0 reset bug
Date: Mon, 21 Jul 2008 21:53:34 +0100 [thread overview]
Message-ID: <5eee8c670807211353u49afeb71gc7aa02ce15b684a@mail.gmail.com> (raw)
In-Reply-To: <9CBA2065-DBBE-4342-BF35-2C24BDF829C5@holtmann.org>
[-- Attachment #1.1: Type: text/plain, Size: 1158 bytes --]
Hi Marcel,
I keep reading kernel developers saying that we should be persistent, so I'm
following up on this, has any progress been made regarding the following
issue?
This one's a bit of an old one, regarding bluetooth adapters after a certain
build number to require a reset command every boot before they'll work
properly, I've attached a previous discussion as a reminder to the issue.
If there's anything I can do (non-code writing though), please let me know,
I'll be glad to help get this sorted.
Alexander Deriziotis
On 26/03/2008, Marcel Holtmann <marcel@holtmann.org> wrote:
>
> Hi Dave,
>
> I've been looking around to see if I could figure out the build id where
>>> the
>>> dongles started shipping with the correct HCI_Reset. I think I may have
>>> found something.
>>>
>>
>> Thanks a lot.
>>
>> Marcel, I think it's what you want. I would like to file a patch.
>>
>
> yes, but I already got it via CSR internals. They have always been helpful
> when it comes to BlueZ. CSR is an open source friendly company. I didn't
> have time to actually produce that patch since we have to turn the whole
> logic around.
>
> Regards
>
> Marcel
>
>
[-- Attachment #1.2: Type: text/html, Size: 1845 bytes --]
[-- Attachment #2: Google Mail - hciconfig hci0 reset bug.html --]
[-- Type: text/html, Size: 4088 bytes --]
next prev parent reply other threads:[~2008-07-21 20:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 22:51 [Bluez-users] hciconfig hci0 reset bug Odysseus Flappington
2008-03-03 1:21 ` Dave Young
2008-03-03 1:24 ` Dave Young
2008-03-03 11:35 ` Odysseus Flappington
2008-03-03 22:19 ` Odysseus Flappington
2008-03-17 12:28 ` Odysseus Flappington
2008-03-18 7:14 ` Dave Young
2008-03-20 17:19 ` Odysseus Flappington
2008-03-22 0:29 ` Dave Young
2008-03-26 16:22 ` Marcel Holtmann
2008-04-04 8:58 ` Odysseus Flappington
2008-07-21 20:53 ` Odysseus Flappington [this message]
2008-07-22 5:02 ` Dave Young
2008-03-26 12:50 ` Peter Stephenson
2008-03-26 16:24 ` Marcel Holtmann
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=5eee8c670807211353u49afeb71gc7aa02ce15b684a@mail.gmail.com \
--to=deriziotis@gmail.com \
--cc=bluez-users@lists.sourceforge.net \
--cc=hidave.darkstar@gmail.com \
--cc=marcel@holtmann.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