From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 216936] First attempt to upload firmware for Intel Bluetooth fails (a timing issue?)
Date: Fri, 12 Apr 2024 20:02:02 +0000 [thread overview]
Message-ID: <bug-216936-62941-2aTb1G2bda@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216936-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216936
--- Comment #22 from Artem S. Tashkinov (aros@gmx.com) ---
It's not a big issue that's why I kept it close.
I just wonder if it's possible to poll HW and ask it "Hey, do you already have
firmware uploaded?" because it surely looks like Linux tries to upload it
without much success twice only to fail and realize it's not necessary.
I'm not sure btqca is affected by the same issue and it's not like too many
people casually switch between OSes all the time.
At the same time AFAIK ALSA has quite a number of workarounds to deal with the
exact same situation: Windows initializes audio HW a certain way and then it
starts malfunctioning after rebooting into Linux. It was the case years ago,
I've not heard much if any about this recently.
TBO, it more looks like the case of Windows not using cold reboot (and AFAIK by
default Linux doesn't do it either) but why would it if e.g. makes booting
slower.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2024-04-12 20:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-15 20:35 [Bug 216936] New: [REGRESSION] The first attempt to upload firmware for Intel Bluetooth fails bugzilla-daemon
2023-01-15 20:38 ` [Bug 216936] First attempt to upload firmware for Intel Bluetooth fails (a timing issue?) bugzilla-daemon
2023-01-15 22:26 ` bugzilla-daemon
2023-01-16 12:42 ` bugzilla-daemon
2023-01-17 5:58 ` bugzilla-daemon
2023-01-31 3:01 ` bugzilla-daemon
2023-01-31 3:06 ` bugzilla-daemon
2023-01-31 9:11 ` bugzilla-daemon
2023-04-29 16:35 ` bugzilla-daemon
2023-04-30 8:44 ` bugzilla-daemon
2023-05-12 8:58 ` bugzilla-daemon
2023-05-13 10:59 ` bugzilla-daemon
2023-07-11 14:44 ` bugzilla-daemon
2023-07-11 14:48 ` bugzilla-daemon
2023-07-12 16:34 ` bugzilla-daemon
2023-07-12 23:11 ` bugzilla-daemon
2023-07-13 14:06 ` bugzilla-daemon
2023-07-29 20:09 ` bugzilla-daemon
2023-09-20 10:53 ` bugzilla-daemon
2023-09-24 10:11 ` bugzilla-daemon
2024-04-12 15:37 ` bugzilla-daemon
2024-04-12 19:56 ` bugzilla-daemon
2024-04-12 20:02 ` bugzilla-daemon [this message]
2024-04-12 21:40 ` bugzilla-daemon
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=bug-216936-62941-2aTb1G2bda@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.