All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 219571] Previous handle short-transfer fix for fake CSR controllers does not account for other fake devices
Date: Sat, 07 Dec 2024 09:44:05 +0000	[thread overview]
Message-ID: <bug-219571-62941-CIeakQQPW2@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219571-62941@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=219571

--- Comment #1 from Mohamed Sohail (sohailsameja@gmail.com) ---
[  +2.061002] Bluetooth: hci0: Opcode 0x1004 failed: -110
[  +0.000003] Bluetooth: hci0: command 0x1004 tx timeout


Forgot the above lines. Either reverting to the old code size handling code i.e
        size = le16_to_cpu(data->intr_ep->wMaxPacketSize); or changing the
device identifier to match 0x10d7, 0xb012  fixes this.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

      reply	other threads:[~2024-12-07  9:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-07  9:41 [Bug 219571] New: Previous handle short-transfer fix for fake CSR controllers does not account for other fake devices bugzilla-daemon
2024-12-07  9:44 ` bugzilla-daemon [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=bug-219571-62941-CIeakQQPW2@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.