Hi
Am 15.10.19 um 13:48 schrieb Ville Syrjälä:
On Mon, Oct 14, 2019 at 04:04:15PM +0200, Thomas Zimmermann wrote:
Only code is being copied, no functional changes are made.
Signed-off-by: Thomas Zimmermann tzimmermann@suse.de
drivers/staging/mgakms/g450_pll.c | 539 +++++a
...
Personally I would start from scratch. In fact some years (*cough* decade) ago I did just that and started writing a new driver for matrox stuff. Unfortunately I ran out of steam after figuring out most of the interesting hardware quirks and whatnot, so I never finished it. The end result is that it still runs in userspace but kinda looks like a kernel driver if you squint a bit.
Anyways, I just slapped a MIT license on it dumped the whole thing here: https://gitlab.com/syrjala/mga The development history was, shall we say, not really useful so I just squashed it.
You, or someone else, might find it interesting. I think in terms of hardware support it's a superset of any other driver, apart from the blob.
Just to make this clear: I do not intend to port every single fbdev driver to DRM. :)
I did, however, began to convert that Matrox driver. First, to see if the approach does work in general; and because matroxfb is one of the more complex drivers. If it can be converted, any other driver should be convertible as well. I split up the driver code by HW generation and can now refactor each generation on its own. I expect to end up with several duplicated functions, which can be re-merged.
Maybe our repo can be helpful. Thanks for the link.
Best regards Thomas