On 12/15/2010 9:26 AM, Thomas B. Ruecker wrote:
Now at least Nokia for the N900 provides a much newer kernel for MeeGo,
so those of us who own N900's are in good shape, but the conflict I'm
trying to point out is real... and there will be a point where, even if
you ignore the hard compliance topic of what applications can expect,
the core OS just expects newer kernel functionality.
Yes, we've seen this happen with previous hardware where we are stuck
with 2.6.22 and a kernel config that clashes with newer udev.
That's the moment where we either find a way to patch in the needed
feature or say 'tough luck, no cookie for us'. It's not how it should
be, yes. Newer kernel would be lovely, but often it won't happen.

it's hard. Some of the more trivial things are easy to backport, but once you start hitting whole subsystems or
core infrastructure you're going down fast.

To run MeeGo 1.3, you will need things like full 2.6.37 level CGROUPS (needed for systemd), the latest mac80211 wifi stack including rfkill subsystem (needed for Connman), a somewhat current TTY layer (needed for proper GSM support in Ofono), a current sysfs layer (for udev), a current LSM set (for the security system), the list goes on and on.

And when we decide to switch to Wayland, there's a deep dependency on various pieces of the DRM graphics subsystem (that likely go beyond just the kernel) of course.


For MeeGo to be innovative not just in the UI layer, but also below that to make attractive UI innovations possible, it's going to need to use as much of the relevant interesting new functionality from various open source components as it can get. This comes with a toll, and I appreciate that it puts a project like the one you are working on in a tough position of either moving kernels, or doing exceedingly tricky backports. I would like there to be a place in MeeGo for projects like yours, but I don't want that to turn into a gridlock on MeeGo as a whole in terms of being able to use innovations from the open source ecosystem.




_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev

Reply via email to