M1 Thunderbolt ports don’t fully support USB 3.1 Gen 2

Re:M1 Thunderbolt ports don’t fully support USB 3.1 Gen 2 by cycomanic on Monday April 18, 2022 @06:38AM (#31069129)

I think the should really just use sha hashes of the standard document, to avoid all this version name issues.

[ Parent | on HN ]

Re:M1 Thunderbolt ports don’t fully support USB 3.1 Gen 2 by gumby on Monday April 18, 2022 @08:34AM (#31069817)

Sadly this might be more user friendly then the current setup.

Even just a bit vector of the capabilities, expressed as a decimal or hex number, would be more comprehensible.

[ Parent | on HN ]

Re:M1 Thunderbolt ports don’t fully support USB 3.1 Gen 2 by anticensor on Monday April 18, 2022 @10:56AM (#31071503)

You would then get USB Type 61513 port and USB Type 48757 device, which could only communicate at Type 45151.

[ Parent | on HN ]

Re:M1 Thunderbolt ports don’t fully support USB 3.1 Gen 2 by rowanG077 on Monday April 18, 2022 @11:43AM (#31072229)

Yes you would. But that doesn't mean you can't represent it with 16 nice graphics that clearly show if something is supported or not.

[ Parent | on HN ]

Re:M1 Thunderbolt ports don’t fully support USB 3.1 Gen 2 by gumby on Monday April 18, 2022 @11:20AM (#31071903)

At least you’d know what you were getting.

[ Parent | on HN ]

Re:M1 Thunderbolt ports don’t fully support USB 3.1 Gen 2 by TheRealSteel on Monday April 18, 2022 @09:25AM (#31070217)

I think they should use the Chrome/Firefox numbering system. Every time you put out an update that's big enough for users to be affected, increase the integer by one. It's the most intuitive system to humans.

[ Parent | on HN ]

Re:M1 Thunderbolt ports don’t fully support USB 3.1 Gen 2 by Kwpolska on Monday April 18, 2022 @11:45AM (#31072259)

The Chrome/Firefox numbering system is “new number every month”. Most of those updates don’t bring any new notable features.

[ Parent | on HN ]