12 ms·
I really don't understand why AMD cares so much about getting their driver upstreamed. If their code doesn't meet the kernel standards and they don't want to fi
by Spivak 10y ago
I really don't understand why AMD cares so much about getting their driver upstreamed. If their code doesn't meet the kernel standards and they don't want to fix it then just package it up as kernel module and ship it like Nvidia does. Distributions will package it using DKMS and other than some occasional troubleshooting they wont even notice. It's really no difference than Windows in that respect.
His arguments seem really weak. Apparently the AMD team believes that the kernel should accept this code despite it not meeting their standards because:
* Otherwise they'll write angry blog posts about how mean the kernel maintainers are.
* They're a primarily Windows shop.
* They don't have the resources to do it right.
* They don't have the time to do it right.
* They're 'trying' to do the right thing.
* They believe that AMD is a big enough company to get special treatment.
* "But Andrrroid gets special treatment"
* There are lots of people with unreleased hardware that desperately need driver support.
* They're doing in wrong, but the current kernel maintainers are doing it wrong in a different way so it should be okay.
* Graphics drivers are what's preventing the 'year of the Linux desktop'.
- izacus 10y agoThat's a lot of strawmen you managed to build here :/
- x0x0 10y agoThat list really is sourced from Alex' email.
- scrollaway 10y agoIt's a really unfair reading of that email. Yes, some of them are true, but that post is no better than turning a random quote into a clickbait headline.
- vacri 10y agoYou missed the bit where AMD chides kernel maintainer for attacking AMD's corporate culture rather than technical merits, and then goes on to chide maintainer culture in the same paragraph. And it's not even true what AMD says - that to commit to the kernel you need to be a funky part-time hacker or an immense behemoth. There are tons of small hardware shops out there with drivers in the kernel, written by paid developers. True, a graphics card is much more complex than any other appliance, but the characterisation is extremely wrong - the most active part of the kernel is the drivers, and they're not written by "redhat + movie-style hackers", but largely by the companies that make the hardware.
- deleted 10y ago[deleted]
- geezerjay 10y ago> You missed the bit where AMD I don't believe he is speaking on behalf of AMD. He is speaking for himself and trying very desperately to shift his blame onto anything he could think of at that time. He clearly tried to blame the problems caused by his technical decisions on subjective and social reasons. I don't believe that a AMD PR employee would be so stupid to ever think of saying such nonsense, particularly in such an eggregious manner. The developer claims he has been working for AMD for 10 years, and yet he still is unable to write a driver, let alone get one accepted. Facts speak for themselves.
- fbreduc 10y ago> They don't have the resources to do it right. Honestly I hear this quite often from big companies and it always is the biggest load of BS ever..
- bhouston 10y agoIt is hard to get resources to do things right sometimes, even in big companies. There are a lot of competing priorities.
- toomuchtodo 10y agoIf only there was some way to use leverage to require them to assign resources to a project.
- phkahler 10y ago>> It is hard to get resources to do things right sometimes, even in big companies. There are a lot of competing priorities. AMD has the resources. The problem seems to be getting them allocated to this particular issue. I also find your phrasing interesting. Doing it "right" is always my top priority and every compromise from that is considered and balanced. In my experience, not doing it right is almost always more costly but sometime necessary to appease someone. It's interesting that Dave is standing his ground against a multi-billion dollar company for their own long-term good - or at least what he perceives it to be.
- deleted 10y ago[deleted]
- trome 10y agoAMD could likely allocate the resources, but what will they cut to do so? At this point they are a token competitor to Intel and are losing money and have been losing money for years, so how much of their financial runway are they willing to burn up on a platform that doesn't use them for servers and minimally uses them for gaming (where the platform has no marketshare). I as a full time debian user for the past few years get it. AMD's Linux devs heavily dislike direct rendering manager and want to provide all the cool crap their proprietary driver does to Mesa, cause DRM is legacy tech and they have over 1000 SKUs of cards to support, 2 competitors breathing down their neck on both the GPU, CPU and SOC sides, and they wanna get this shipped. I hope I've illuminated the state of the situation for you, I do think the right decision was made to not merge this code, but be realistic about AMD's position, they are so far in the hle financially that customers are having chips made to order after paying, meaning its at least 3 months from the time f order until you get your chip. They spend nearly all that time making the silicon, then packaging it so it can go onto your motherboard.
- lvs 10y agoThe claim that AMD, a company with gross profit in the $1 - 2 billion range, does not have the resources to support a dedicated development team that can do a good job on upstream-able code is just farcical. That's a question of corporate priorities, not resources, and gets precisely to the critique of corporate culture that was in question. > There's only so much time in the day; we'd like to make our code perfect, but we also want to get it out to customers while the hw is still relevant. And this has always been the damn problem with AMD's drivers, even in their wheelhouse, Windows. They just have a slipshod attitude toward the software end of their core business.
- dzhang50 10y agoAMD doesn't have "gross profit in the $1 - 2 billion range". They have about $1B in revenue per quarter and have had negative profits (i.e. they lose money) for quite some time now. They were on the verge of bankrupcy about a year ago. Maybe Zen can turn their fortunes around, but they're correct in that they don't have the resources for a dedicated development team right now.
- deleted 10y ago[deleted]
- deleted 10y ago[deleted]
- Dylan16807 10y agoWriting the software that makes your hardware work is much more of a revenue-based issue than a profit-based issue. Even if you're losing money you need to balance your development budget, and not cut any segment too far.
- AlphaSite 10y agoTheir revenue is from Windows, Apple and Cknsoles, not from Linux.
- 10y ago
- CamperBob2 10y agoThey don't have the resources to do it right. I loved that line from his post, in particular. "We have the resources to design a billion-transistor GPU, but not to write a Linux driver for it." Poor management on AMD's part does not constitute an emergency on the Linux kernel's part.
- threeseed 10y agoHow is that poor management ? Linux gaming is a blip when you compare it to (a) the total gaming market, (b) the professional creative market and (c) the big data/deep learning market. All of which AMD is selling graphics cards into. And it's not like Linux is even some massive growth market that justifies some risky investment.
- greendesk 10y agoGraphics cards are used for professional work too, not only gaming.
- sangnoir 10y ago> the professional creative market This is not true for the animation/CGI/effects industry where Linux not only looms large but is growing. I'm also sceptical of Linux having a small share of big data/machine learning since this is adjacent to servers where Linux dominates- would you mind sharing your sources? Nvidia's CUDA is cross-platform, this sets a baseline for whatever response AMD is planning.
- nitrogen 10y agoAlso GPU-as-a-service seems to be a growth market, and Linux is usually the first choice in X-as-a-service.
- macawfish 10y agoThat's what's frustrating to me. I have an AMD R9 290 and an Intel integrated GPU. I want to use them together for GPGPU stuff (simulating dybamical systems), but the driver situation has consistently been kindof a mess. I get it working and then all the sudden things shift and I have to configure again... Reminds me of the good old days of configuring xorg.conf in 2004.
- lamontcg 10y ago> the 'year of the Linux desktop'. What was that 2001? I can probably dig up an old slashdot and find it...
- rwmj 10y agoOr even better, give us an open source out-of-tree driver, and wait. Someone in the community will do the cleanup and get it upstream eventually. For free.
- MayeulC 10y agoWhile that's probably true, it won't happen overnight, and I understand their position of wanting it merged before rolling out new hardware, or more generally, as soon as possible.
- pjz 10y ago...fast, correct, cheap: pick two.
- anonbanker 10y agoHow come Intel can do this, but ATi/AMD can't?
- solatic 10y agoIt's the labor theory of value in action. "We put in the labor, labor is intrinsically worth something, because we're giving you something that's worth something, it should be appreciated by you and by the wider community." But that only works when you're in the programming equivalent of a 20 member socialist commune. It doesn't work at scale, and the Linux kernel is the effing king of large open-source projects. At scale, you must have standards to ensure the value added is higher than the cost of maintenance. Who's going to set the standards if not the kernel maintainers? The contributors? That's anarchy, leading to collapse. The wider community, in some democratic fashion? Easiest way to kill momentum and thus kill the project.