When a driver challenges the kernel's assumptions

> The answer was as unhelpful as possible

Uh I think I think that's way too mean to the email. From a random web form they got some technical information, a useful CC, and offer to have a call. Not bad at all!

Also, my basic theory about hardware problems is that the problem is less that they won't share the docs, and more that even the internal docs suck. When you essentially co-evolve devices and software through many revisions of each over many years, it's easy to get a complete mess that nobody understands.

(Of course, in this specific case, DisplayLink was new, so it's maybe less of a problem.)

> The answer was as unhelpful as possible

Looking at the answer, I wouldn't call it unhelpful. They were planning to release a source for the library that would essentially implement all the needed data interfaces? That's more than helpful and at least they responded.

I tried contacting Nuvoton for example about their documentation for some of their super I/O chips which lack Linux support (they do document a bunch of their chips pretty well, but for some weird reason not all).

Not only I got no details, I literally didn't even get a response from them at all. So above case is hugely better.

[dead]