@kiwa fair enough. But if you start standardizing on USB-C then it is a good option for legacy or non USB-C devices.
linux4kix
- 152 Followers
- 69 Following
- 286 Posts
@never_released peaceful isn't it?
@kiwa Just note 12V is an optional voltage and not supported by all these adapters, but some like this one do. Unfortunately they aren't nicely packaged so you need to heat shrink them, or 3d print a case for them. I use them everywhere.
@kiwa FYI, you can get these kits on Amazon pretty cheap. They come with the 5.5mm adapter and take USB-C in. They can autodetect voltage, or you can program them to only take one of the standard USB-C PD delivery voltages. They are perfect for using a standard USB-C brick, or port that supports PD protocol and powering / charging 5, 9, 12, 15, 20.
@never_released @hrw Do laws count as standardizations?
@hrw except that the chicken and egg problem has existed for almost a decade now, and Microsoft still has an exclusivity deal with Qualcomm who have proven they don't care about SBSA. This means Linux needs to make the difference and even including x86_64 they are still a very small part of the desktop market. Arm had a window open until about 2-3 years ago and they missed it.
@hrw You answered your questions with the edit. Windows will only certify Qualcomm hardware on Arm64 due to exclusivity licensing. Linux integration takes years to get into mainline, so hardware is "old" before it just boots...and well BSD. Final answer...there is no money in it.
@hrw may have something to do with it being a rental. Not that I would ever defend a Peugeot...just saying.
Never. There is no reason to. ACPI is cultural flexible so the developer culture is fine excepting quirks and other hardware issues that arise that "bend" the standard. The only reason ACPI isn't being used more for other architectures is a failure in the culture to accept that hardware isn't perfect.
Your efforts are appreciated