Hi,
adding to what Patrik said:
- You need to use your real name for kernel patches. Fancy pseudonyms
are not allowed, sorry.
- DRM kernel drivers need a free user space before being merged. In your
case, this would be Mesa (you mentioned this already). Present both
drivers at the same time and reference from each review to the other.
- Hardware support doesn't have to be feature complete, but generally
useful.
Am 08.11.26 um 04:35 schrieb Operating System's Depression:
Also Patrik, about the KMS modernization you mentioned, I can help
with that too, I have GMA500 hardware available for testing, and I
might be able to send patches for that as well
- Modernizing KMS to implement atomic modesetting would be even more
useful then 3d rendering. Gma500 is behind other drivers and could use
some help. It would also benefit users immediately. And you'd get
experience in working with upstream kernel devs.
Best regards
Thomas
Btw, I'm also working on 3D support for the SGX544MP2 used in Intel
Atom Clover Trail+ devices. Since it's a different platform from
Poulsbo, would a separate DRM driver make more sense, or could some of
the gma500 infrastructure be reused?
I think a separate DRM driver might be the better option, probably
--
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstr. 146, 90461 Nürnberg, Germany, www.suse.com
GF: Stefan Gaiser, Jochen Jaser, Abhinav Puri, (HRB 36809, AG Nürnberg)