11 ms·
> One of the unfortunate facts about open source operating systems like Linux is that specialized hardware support sometimes lags behind commercial operating sy
by stavros 5y ago
> One of the unfortunate facts about open source operating systems like Linux is that specialized hardware support sometimes lags behind commercial operating systems like Windows and MacOS.
Well that's just because the manufacturer just doesn't write one, not because of some intrinsic factor of FOSS. That's an odd point to make when it's the manufacturers' fault.
- bheadmaster 5y agoIn most cases, it's not that the manufacturer doesn't write drivers - it's that they don't even release any hardware specification at all. There are a lot of people in the Free Software community that can write drivers, but not so many that can reverse engineer unknown hardware.
- franga2000 5y agoI wonder if it might be time for some legislation around this. Manufacturers are already required to include operating instructions with products they release, so why not protocol specs? They don't need to release anything secret, just the instructions for software to interact with their hardware.
- alimov 5y agoThis is an interesting point. While this would be nice for some folks that just want drivers to be functional I could also see why a manufacturer might be reluctant to offer such information. One reason they could bring up is that it may put undue burden on them to document and provide such information. Another possible issue a manufacturer may have with this is that it offers a more direct route for abuse of their software/hardware (maybe?). Or in some cases it may be a liability to offer such information (if there is a potential for misuse) Edit: or maybe they don’t want to release that kind of info for product/brand lock-in reasons?
- kwhitefoot 5y ago> it may put undue burden on them to document and provide such information. How can documenting something be an undue burden? In order to write the drivers that they do write, for say Windows, they must have written some documentation. And if I want to abuse some piece of hardware, such as making a musical instrument out of a pile of floppy disk drives, what business is that of the manufacturer?
- brk 5y agoThe documentation is not the burden as much as the requirement, or at least expectation, to adhere to the published specs once they are published. By not releasing any info they are not burdened with having to stay consistent on driver details from one product or version to the next.
- monetus 5y agoI called my ebike company and apparently my year and make could have one of three different batteries. Seems infuriating, but hardware manufacturers don't have to be consistent I guess, just release some new/updated docs?
- bluGill 5y agoSome documentation, but when the guy who wrote the hardware is down the hall from the guy writing the documentation it typically isn't very good, saving a lot of effort
- ILMostro7 5y agoI wonder if it has to do with any underlying 3rd-party components. Otherwise, yeah, makes no sense. It might be worth clarifying that Wacom is not taking that approach. But their statement there suggests that the underlying reason for lack of hardware support in Linux is the OpenSource nature of the software.
- alimov 5y agoWell one way that comes to mind for why it could be considered a burden is breaking down internal documentation into public and private, and making sure that the private one is never exposed. As much as we don’t want to imagine business constraints on some manufacturers, they could always come up with reasons. > And if I want to abuse some piece of hardware, such as making a musical instrument out of a pile of floppy disk drives, what business is that of the manufacturer? As an example (maybe not a fair one) we can ask Tesla why they don’t want to expose some/all APIs that Tesla owners might want access to. I expect they would bring up a thousand reasons why, maybe safety related, maybe not. I generally agree with you though, you paid and own something, and you wish to use it as you see fit. Unfortunately it seems like what we think we own and what we actually own are in some cases two separate things.
- ponow 5y agoPlease no. Get the government and their violence out. No one has an inalienable right to APIs and such. You have the right to buy what you want. If the market is not serving you, then look in the mirror and pick your priorities.
- Kolja 5y agoNot everything that would be a net benefit to society has enough people interested in it that they can control markets through their wallets.
- Buttons840 5y agoThe right compromise here is that if the government is going to "protect" the company from copyright infringement, and reverse engineering, and enforce the companies' patents, then the government also has the moral right to regulate the company for the benefit of the people. Comments like yours seem to advocate a very beneficial situation for the companies where they have all protections, all authority, without any responsibilities. If your serious about getting the government out, including out of copyright and patents, then let's talk. Until then, let's regulate these companies.
- ponow 5y ago> If your serious about getting the government out, including out of copyright and patents, then let's talk. Until then, let's regulate these companies. I'm all for eliminating all government privileges and cronyism (which are really rights violations of the competition). In this world, there is no way we're going to get a grand bargain where all things will simultaneously change in that way. For each proposed change, ask whether we increase or decrease natural rights (especially to life and property). "Intellectual" property is a creation wholly new in human history before a few hundred years ago. Property in land and goods goes back to evolutionary times: it's basic territoriality, and respecting that keeps the peace. Free trade is the way forward to widespread prosperity.
- an_ko 5y ago
- PaulHoule 5y agoOne reason to be cagy about how systems work is to avoid patent lawsuits.
- Moru 5y agoThe hardware manufacturer does not want to make it any easier to compete with a similar product either. If you have the protocol, you make it easier to create a drop-in replacement without bothering with any drivers.
- Epiphany21 5y agoThis is why good customer support and warranties are as important as the product itself. It doesn't matter how big the company is either. It's why people pay more for certain brands, especially in the enterprise and professional creative markets.
- novocantico 5y agoMost likely because those who can, don't unless they're paid for it. Which FOSS discourages by its nature.
- divs1210 5y agoIt's a problem with FOSS. Microsoft, Apple, Google have lots of resources to incentivize h/w manufacturers. Apple is even making its own chips now.
- stavros 5y agoMicrosoft didn't write the drivers that came on a CD with my device.
- tmoravec 5y agoThey are conflating two different issues: Linux' lack of stable binary interface for drivers, and Linux being open source. It's the lack of stable ABI that's preventing third parties from maintaining decent drivers for Linux (plus the lack of economic incentives of course).
- marcodiego 5y agoThe lack of stable ABI is not a problem if the driver is merged.
- hef19898 5y agoI think it is much more the latter, the missing economic incentives, than anything else.
- cerved 5y agothat would be the first point if anything
- Lorkki 5y agoI believe USB HID drivers have been in userspace for quite some time, in part precisely to provide a stable interface. I'm not sure why the Wacom drivers are an exception though: https://linuxwacom.github.io/ https://linuxwacom.github.io/
- tremon 5y agoYou are conflating two issues as well: the manufacturers' insistence on closed-source drivers and Linux' non-stable (binary!) ABI. If the manufacturers were to upstream their drivers in the Linux kernel, they wouldn't need to update their drivers for every ABI change.
- stavros 5y agoHm, interesting, I hadn't thought of that. I know that Linux is fine mainlining drivers and updating them whenever the ABI changes, but what's the rationale behind not offering a stable ABI?
- nsonha 5y ago> that's just because the manufacturer just doesn't write one That's just because there is no commercial incentive to do so, which is kind of the issue with FOSS
- stavros 5y agoThe commercial incentive is that I bought their hardware.
- lucozade 5y ago> The commercial incentive is that I bought their hardware The commercial incentive would be if you, and a lot of other people, didn't buy their hardware because it doesn't work with desktop Linux. Until that's a problem, there's little to no commercial incentive.
- askvictor 5y agoIt's not necessarily just the hardware spec and the drivers, though. I ran Linux on a Fujitsu convertible tablet/laptop circa 2010, which had a stylus that worked directly on the screen. The Wacom stylus worked great, as long as I was just using the laptop. But when I plugged in an external monitor, linux tried to apply the stylus across the entire combined screen area of the laptop screen and external screen. It was a relatively rare use-case, but wasn't an issue in Windows. I'm not blaming Linux, just wanting to point out that sometimes systematic issues are overlooked.
- McMiniBurger 5y agosame here. solution: press 'rotate screen' button 4 times...
- hutzlibu 5y ago"Well that's just because the manufacturer just doesn't write one, not because of some intrinsic factor of FOSS" Linux wants to force the manufactors to open source their drivers by intentionally changing the ABI, which makes it harder to write a driver as a binary blob once. I want open source drivers. But I am not sure this is the right way to get them. Hardware makers feel forced to protect their trade secrets, this is the current buisness reality. Open hardware the rare exception. Reality also is, I gave up with linux on many machines because of bad drivers. With more stable drivers avaiable, even if proprietary, I would have been able to convince many more people of linux as well as getting rid of windows on my laptops. And more people using linux on a daily basis, means more people exposed to the idea of software freedom. And not just hackers.
- BenGosub 5y agoIndeed, it's also the case with audio interfaces, no major audio interface company releases Linux drivers.
- n3k5 5y agoInteresting; can you or someone please elaborate? I thought that device-specific drivers wouldn't be needed for the vast majority of audio interfaces, because they're connected via USB and all they need to do to ‘just work’ upon plugging in is implementing the relevant USB device class. From my (programmer's) point of view, all I need to know to work with an audio interface is the number of input and output channels and the respective arrays of sample rates and bit depths. In theory, a generic USB driver can handle that. In practice, I observe that my Linux-using colleagues have 99 problems with audio, but none of those is related to plugging in a $1 dongle from AliExpress. (Therefore, I used to think that those audio interfaces ‘just work’, but now I'm curious about what I've been missing all along.) Why is releasing Linux drivers for an audio interface even a thing?
- dTal 5y agoThat's true for the cheap dongles. Where it gets problematic are the high end "Audio Interfaces" for studio recording work. The USB Audio Class 1 standard was released in 1998 and supports 2 channels at 24/96, over USB 1.0. This is obviously anemic for all but the most basic work. The upgraded USB Audio Class 2 standard was released in 2009, but was unsupported in Microsoft Windows until an update to Windows 10 brought it in 2017. Therefore, prior to that, any manufacturer who wanted to support Windows were put in the position of writing their own drivers for anything with more than 2 channels. https://www.thewelltemperedcomputer.com/KB/USB.html https://www.thewelltemperedcomputer.com/KB/USB.html
- n3k5 5y agoAha, that's a good point! It was silly of me to assume that if any cheap dongle works, that should mean ‘proper’ interfaces would work at least as well. However, it seems like that explains why we needed Windows drivers, but not why device-specific Linux drivers are a thing? Unless the implication is that manufacturers who needed to make custom drivers anyway didn't bother to make their devices class compliant?
- shocks 5y agoNot necessarily. Ubuntu LTS kernel is often very far behind and you have to rely on Canonical to backport drivers for you. e.g. Vulkan on my 5700 XT didn't work (despite AMD being very good at writing kernel drivers!) because the Ubuntu kernel was so far behind. Switching to an up-to-date vanilla kernel and all my problems went away...
- judge2020 5y agoThey don't write one because of the size of the userbase. They end up supporting 99.99%+ of their potential customers by having Windows and MacOS support for something like a drawing tablet; the amount of money to support Linux doesn't justify the potentially low-four digit amount of customers that would buy the product if it had Linux support.
- petemir 5y agoAs a Linux power-user and the tech referral of my family, extended family and friends, if something works nicely on Linux I am obviously going to recommend it to everyone. That has to mean something...
- judge2020 5y agoIt still either has to be a passion project for an engineer or it has to make business sense. Even if it only takes a collective week's worth of work in a year to keep it supported, that's 1/52 of an engineer's salary, and that has to be made up/exceeded by profit generated from the extra sales. Regarding this product, pens and drawing tables for personal computers are already a relatively niche category, so the subsection of those users who also use Linux is probably very small.