From what I gather, it is an open source driver meant for the 2.4 kernel. It would take a bit of work to port to 2.6, but not a real problem.
The biggest problem I have is: Are they the RIGHT drivers? The copyright inside the source readme says 2003... so it can't be too old...
It's possible that these are the wrong drivers. If I understand things correctly, Kyro was their product before MBX.. So MBX was more of a rebranding than a complete different product? So these old drivers could be tweaked and updated?
different model
different interface
different target
different mechanism
sorry, you get points for looking but if it was that easy we would have drivers by now
at the summit we heard small private mumblings about the 3d drivers but there has been nothing officially updated and as far as I am aware no drivers were on show anywhere.
beta drivers and community developer involvement hinted at on the driver justification discussion page has so far turned to nothing.
I have 2.4.x drivers for the omap2430, however it's not trivial to port them, mainly as they need to be reverse engineered and are also for a slightly different chipset.
It's a better use of my time (and others') to wait and see if we do eventually get drivers to go along with Fremantle (which will probably need them). If not, we can look again at doing some reverse engineering.
Fremantle's production release will, presumably, be concurrent with the N9xx hardware shipping. This presumed combo event is generally predicted for 2q/3q of 2009, but nobody who really knows can talk.
The roadmap gives some more short-term guidance, though; first alpha in December.
This all sounds good, but what I'm afraid is that even if we do get drivers with Fremantle, they won't be backwards compatible with current hardware (n800/810).
Omap 3 uses the SGX chipset instead of MBX. That makes sense, it's the new stuff. But it won't help us! We'll still have to reverse engineer something...
This all sounds good, but what I'm afraid is that even if we do get drivers with Fremantle, they won't be backwards compatible with current hardware (n800/810).
They wont be, OMAP3 drivers have absolutely nothing to do with OMAP2 drivers.
This all sounds good, but what I'm afraid is that even if we do get drivers with Fremantle, they won't be backwards compatible with current hardware (n800/810).
Omap 3 uses the SGX chipset instead of MBX. That makes sense, it's the new stuff. But it won't help us! We'll still have to reverse engineer something...
Unless Nokia pulls an FremantleHE with existing, closed, not-up-to-snuff MBX drivers (which they have, but haven't released) to keep Fremantle about.
Then again, any FremantleHE could also use software rendering, if the actual necessary OpenGL stuff for the desktop environment is(/can be made) basic enough.
rivers_justification
