Hacker News Reader

Comment by laurentoget | Hacker News Reader

I suspect some bearded guy at AMD is having his 'i told you so' hour of glory sometime this week.

Quite the opposite, somebody at AMD wanted to play along with the openness of the Linux kernel. Then to help unify their codes bases they push this - and get rejected. Somebody at NVIDIA is laughing their ass off, saying it would have much easier if AMD just did what NVIDIA does!

> Quite the opposite, somebody at AMD wanted to play along with the openness of the Linux kerne

Oh please.

No, the boss said "merge this" and the code has been developed "corporate style" (with a HAL, etc) now the "mean" kernel developers won't approve this

But the Kernel people are right, because the other option would be to introduce code that breaks every now and then and is unmaintainable. See all the ACPI issues for example, that only stopped when Linus said "no changes can break existing functionality anymore"

Don't see why you're getting downvoted. This is likely the closest to the truth.

> This is likely the closest to the truth.

This depends on whether there is at least 1 person at AMD who has experience with kernel development. If all of the team members all kernel outsiders, then this might confuse/surprise them. Otherwise someone likely raised this as a potential issue.

AMD had hired kernel developers to work on graphics drivers soon after taking over ATI.

well, the conclusion is obvious then

Because they were told months ago this could have happened.

They didn't listen.

Last time I heard NVIDIA had to divert some of their people to work on Tegra support in nouveau because their ARM customers want open drivers so I'm not sure if they are in position to laugh their asses off.

Reply on news.ycombinator.com