4 ms·
The other reason for is that the developers of the USB-C specifications left us with a terrible confusing mess where visually identical cables have different ca
by JshWright 7y ago
The other reason for is that the developers of the USB-C specifications left us with a terrible confusing mess where visually identical cables have different capabilities and behaviors.
- derefr 7y agoIf it’s confusing, just don’t use it. They could have stuck with a micro-B charger, or a custom charger, and no one would have questioned it. Instead, they decided they were confident enough in their understanding of USB-C to implement it on their device. And they were wrong.
- JshWright 7y agoI said the "other" reason. I am not absolving the RPi team here... The fact that they shipped this reveals significant gaps in their engineering and QA processes. That doesn't change the fact that USB-C is a mess, and that mess contributed to this failure.
- TremendousJudge 7y ago>They could have stuck with a micro-B charger Somebody here said they were running into the maximum rated current for the port >or a custom charger Literally everyone would have complained
- tracker1 7y agoI don't think anyone would complain much if they supported a popular barrel connector with a popular power draw. As it stands, I'll only ever use a Pi with a charger sold as working with it after all the 3B+ issues I had (7 chargers, none worked without a warning on screen).