From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 218943] No SuperSpeedPlus on AM4/5 Hubs
Date: Fri, 21 Jun 2024 02:24:13 +0000 [thread overview]
Message-ID: <bug-218943-208809-u8V53GmkQx@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218943-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=218943
--- Comment #32 from Jarrard (jarrard@proton.me) ---
To conclude this bug report I have moved the OBS server to windows as a temp
solution but would like to return it to Linux eventually.
However for that to happen I think 10Gbps would need to be manually flagged on
this vendor+device ID with some patch.
I have tried the suggested PATCH set already and it allows the HUB to connect
at 10Gbps but the device itself remains at 5Gbps so further patching would be
need. I do not know how to do this.
If anyone is able to help with a manual kernel patch to test other then the one
in the comments here then I'm happy to test.
Thankyou.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2024-06-21 2:24 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-07 0:01 [Bug 218943] New: No SuperSpeedPlus on AM4/5 Hubs bugzilla-daemon
2024-06-07 0:04 ` [Bug 218943] " bugzilla-daemon
2024-06-07 0:14 ` bugzilla-daemon
2024-06-07 0:15 ` bugzilla-daemon
2024-06-07 11:17 ` bugzilla-daemon
2024-06-07 13:42 ` bugzilla-daemon
2024-06-08 1:35 ` bugzilla-daemon
2024-06-08 1:36 ` bugzilla-daemon
2024-06-08 1:41 ` bugzilla-daemon
2024-06-08 1:43 ` bugzilla-daemon
2024-06-11 5:02 ` bugzilla-daemon
2024-06-11 5:03 ` bugzilla-daemon
2024-06-11 8:25 ` bugzilla-daemon
2024-06-11 8:43 ` bugzilla-daemon
2024-06-11 8:59 ` bugzilla-daemon
2024-06-11 9:02 ` bugzilla-daemon
2024-06-11 14:10 ` bugzilla-daemon
2024-06-11 14:33 ` bugzilla-daemon
2024-06-11 14:53 ` bugzilla-daemon
2024-06-12 20:38 ` bugzilla-daemon
2024-06-13 0:43 ` Thinh Nguyen
2024-06-13 0:43 ` bugzilla-daemon
2024-06-13 0:50 ` bugzilla-daemon
2024-06-13 13:01 ` bugzilla-daemon
2024-06-14 4:20 ` bugzilla-daemon
2024-06-14 4:34 ` bugzilla-daemon
2024-06-15 4:08 ` bugzilla-daemon
2024-06-17 2:50 ` bugzilla-daemon
2024-06-17 4:42 ` bugzilla-daemon
2024-06-17 4:48 ` bugzilla-daemon
2024-06-17 5:27 ` bugzilla-daemon
2024-06-17 5:52 ` bugzilla-daemon
2024-06-17 5:55 ` bugzilla-daemon
2024-06-21 2:24 ` bugzilla-daemon [this message]
2024-06-22 0:28 ` Thinh Nguyen
2024-06-22 0:28 ` bugzilla-daemon
2024-06-22 2:36 ` 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-218943-208809-u8V53GmkQx@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-usb@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.