6 ms·
>Fundamentally, "one port and protocol to rule them all" is probably just a bad idea I disagree. The situations are: 1)ports are the same, protocol match
by jayd16 7y ago
>Fundamentally, "one port and protocol to rule them all" is probably just a bad idea
I disagree. The situations are:
1)ports are the same, protocol match : works
2)ports are the same, protocol mismatch : won't work, some user confusion
3)ports are different, protocol match : could work but won't without an adapter
4)ports are different, protocol mismatch : won't work. Adapters might exist but those won't work either.
I'd much rather deal with situation 2 over 3 and 4. Display adapters already have situations where you can get adapters to cobble together DVI and VGA ports but still fail to get a proper connection, so its not really a fix anyway.
The USB foundation should just come up with better branding around what kinds of things a port supports. No reason we can't have a thunderbolt icon next on a USB port. Its strictly better than a new physical port, IMO.
- chrisweekly 7y agoPardon my ignorance, but isn't (2) really dangerous when it comes to things like power delivery?
- hunter2_ 7y agoThere's nothing dangerous about drawing less current than is available, or a device trying to upgrade voltage and/or current from a base level (5V 500mA) but being disappointed when the source can't oblige.
- spancap 7y ago(2) has killed people, such as the patient who was electrocuted in 1986 due to an IV pump power supply using the same connector as EKG leads. (Casey, "Set Phasers On Stun" 2nd edition, pp.177-180)
- hannasanarion 7y agoUSB doesn't automatically deliver maximum power to whatever is plugged into it. The client device has to ask for it. The default 5v 500mA isn't going to hurt anybody.
- gsich 7y agoNeither is 5V 2A, but that's more to skin resistance that's really high at such low voltages.
- magduf 7y ago5V at 1000A is completely safe too. The only thing that matters with electrical safety is voltage, and anything under 50V is generally safe for humans, all because of skin resistance.
- mortenjorck 7y agoIt would be if the different protocols didn’t have the same baseline power specifications and require negotiation between controllers to supply anything else. This is generally the case across everything sharing the type-C connector, though occasionally you will see a company make the terrible decision of trying to pass off their out-of-spec implementation as a “proprietary port,” as Nintendo did with the Switch.
- rkangel 7y agoIs there something special about the USB-C connector on the Switch?
- Miraste 7y agoIt's slightly off-spec in some odd ways: https://arstechnica.com/gaming/2019/08/heres-why-nintendo-switch-consoles-keep-frying/?comments=1&unread=1 https://arstechnica.com/gaming/2019/08/heres-why-nintendo-sw...
- Dylan16807 7y agoThere were some slightly off-spec things in current draw but none of that is relevant to the article you linked. That pin is supposed to use data signals of less than two volts. The nyko charger uses nine volts. The switch has no over-voltage protection on that pin, and breaks at more than six volts. The part about a slightly thinner plug isn't relevant at all.
- izacus 7y agoNo, because power delivery is negotiated from a safe USB1 type base levels. If the device doesn't request it, it won't get delivered. The only outliers are moronic implementations like Nintendo, where they ask for capabilities, receive the charger capabilities and then just start pulling power at hardcoded levels even if the charger doesn't specify it supports those power levels. But there's nothing you can do against that - you even with different port shape, a broken implementation can still fry your device.
- sschueller 7y agoDidn't the charger from the Pixel not implement this correctly and send full power down the line even if a device can't handle it?
- ProZsolt 7y agoThe Pixel charger was fine AFAIK. The Nexus 5x and 6P had rogue chargers
- chrisweekly 7y agoYou started with "no" (ie, it's safe)... then ended with "can still fry your device". I infer your point: the shape of the connector in theory is decoupled from risks in power delivery... but in reality the prevalence of cheap knockoffs and "moronic implementations" makes me question the wisdom of combining [potentially dangerous levels of] power delivery with data transfer.
- gumby 7y agoYou forgot the case 5) ports match, some protocols match, port works at much reduced capability. This is great for backwards compatibility, but can confuse users. You could have a TB3 drive attached to a TB3 computer by a USB cable with type C connectors that only operates at USB 2 speeds. It will silently fall back to a very slow transfer. I don't know how the committee could have done much better though; this kind of fallback is important. Some mandated labeling would have helped a lot though.
- k__ 7y agoJust try to get some quick charge with third-party equipment going these days. It's a lottery.
- bobbyi_settv 7y ago> It will silently fall back to a very slow transfer. Why would it be silent? The computer would hopefully show a small notification that the transfer is happening slower than it would with a newer cable
- sroussey 7y agoThis. Apple does something similar if you try to pull too much power
- gumby 7y agoOnly in the power case -- how can it know that you didn't intend to use USB 1? It wouldn't be able to tell what the other side is capable of in that case, hence the fallback.
- bonzini 7y agoIt could know via USB descriptors, and match the device capabilities from the descriptors against what the cable allows.
- egypturnash 7y ago
- Stratoscope 7y ago> No reason we can't have a thunderbolt icon next on a USB port. In fact, my ThinkPad X1 Yoga has two USB-C ports with Thunderbolt icons next to them. They support USB 3.1 Type-C Gen 2 with Thunderbolt 3 (including DisplayPort).
- suvelx 7y agoHow many DisplayPort channels do each ports support? How many PCI-E lanes does each port get? Do the ports share the channels/lanes? Do they both support Power Delivery? How many Watts does the thinkpad need to charge? Even with 'clear' labelling, it can still be a crapshot as to the full capabilities of the device.
- Stratoscope 7y agoWell, this is where we get the phrase "Plug and Pray", isn't it! ;-) Right now I have an Uptab Mini-DisplayPort adapter in one port, and a StarTech full size DisplayPort adapter in the other. The Uptab adapter has its own USB-C input for power, so that is where the power supply is connected. The mini and full size DisplayPorts are each connected to a 4K monitor, and I use all three - the two externals and the ThinkPad's WQHD. This all works great when the Uptab is in the rearmost USB-C port and the StarTech is in the other port. But if I switch the two around, one of the monitors goes into low resolution mode! This kludgy configuration is just because these were the adapters I had on hand. There are a number of adapters that plug into a USB-C port and give you two mini-DisplayPort outputs - I have been meaning to try one out.
- flyingfences 7y ago> They support USB 3.1 Type-C Gen 2 with Thunderbolt 3 (including DisplayPort) And therein lies the problem. Used to be, we could call a USB port a USB port. Everybody knew that if the computer had the port, it could work with the peripheral; if the computer didn't have the port, it would not work with the peripheral. If the peripheral required different functionality then it required a different port that was equally straightforward and obvious. Now, it's all supposed to run over USB - at least, over some USB. Consumers go out and buy a device and then are confused when it doesn't work. They know their computer has a USB port, but that's not enough. The port no longer represents a definite protocol, or even a definite power supply capacity. Are they supposed to check to see whether each of their USB ports says "USB 3.1 Type-C Gen 2 with Thunderbolt 3 (including DisplayPort)" next to it (which it doesn't)?
- thaumasiotes 7y ago> 4)ports are different, protocol mismatch : won't work. Adapters might exist but those won't work either. Why would adapters necessarily not work in this case? It looks like you're claiming that translating one protocol to another is always impossible, but that can't actually be the idea... right?
- jayd16 7y agoThat would be case 3...
- thaumasiotes 7y agoNo, in case 3 there's a protocol match. In case 4 there isn't. I'm asking why an adapter is supposedly unable to deal with a protocol mismatch. Dealing with mismatch is the whole idea of an "adapter".
- infogulch 7y ago"could work but won't without an adapter" The adapter is the downside. And there's no guarantee that the perfectly suitable adapter actually exists.
- jayd16 7y agoIf an adapter exists we can categorize it as case 3 for the sake of this discussion. I think you're needlessly hung up on the word protocol when that really doesn't matter.
- thaumasiotes 7y ago> I think you're needlessly hung up on the word protocol when that really doesn't matter. In that case, you've described two situations: 1. Ports are the same. 2. Ports are different. This doesn't seem like a particularly fruitful analysis.
- johncolanduoni 7y agoMost of these kind of adapters (usb-c/usb-a, dvi-d/hdmi) don’t actually do any protocol conversion, they merely take advantage of fallback/cross-compatibility that the endpoints actually implement and rearrange some wires. Adapter that need to do something more complicated (like dvi-d to vga) have to be powered. And in some cases like USB 3 to thunderbolt or DisplayPort it’s simply impossible for the host controller to provide the necessary IO. Thunderbolt expects to provide a full PCIe interface to the CPU that doesn’t fit within how USB 3 controllers communicate with your CPU. DisplayPort requires a connection to your graphics adapter, which is also not under the USB 3 controller’s purview.
- unixhero 7y agoIsn't that too late. They aren't going to publish any new specs after this.