Hi Harry, <[email protected]> writes:
> This is brief status update of "MeeGo to N900" project. This project > is currently running as Nokia project, and I am Nokia project lead for > it. The current closed mode of development is not the target for us at > all, but rather transitional condition. As already discussed by > Valtteri in TSG meeting, we are looking into going more open mode > shortly. One reason why we have done this on this way is that at the > same time we have been trying to handle opening of many currenly > closed components that are needed in MeeGo and to build feasible MeeGo > images for N900. > > However, a lot of related work is already done completely open, you > can find more info from places like ofono.org, connman.net and > meego.gitorious.org . So if you are eager to contribute or want to > closely follow whats happening, please work on those. > > As you know, we have delivered working MeeGo images for N900 as part > of first code drop in the end of March. At that state we were using > older kernel version on N900 than on Atom side, as we used the same > kernel (.28) than what is used in Maemo 5 based products today. We > ended up doing that simply because lack of time to contribute and port > all the drivers to the newer kernels. > > Now, for the upcoming May release of MeeGo, we are going to use the > same kernel version (.33) than Atom based devices are using. That's great news! > For that we need to submit number of ARM-architecture patches to MeeGo > as well, because many of the required ones have just been contibuted > upstream kernel and were not available in .33 version originally. > > We have already enabled most of the main drivers, like LCD, GFX, Wlan > and BT. Still, there is a lot to do in order to enable .33 on N900, > like audio drivers, and modem subsystem including SSI buss driver, > modem data and audio drivers etc. Our adaptation guys are in fact > contributing those modem subsystem related drivers as we speak, and if > you are following kernel mailing lists you can see how that goes on. I don't know if you noticed that: http://thread.gmane.org/gmane.linux.ports.arm.omap/34182 I'd be happy to drop my current effort and take part in yours (tests or reviews). If you already have raw material (git tree, set of patches, ... against a 2.6.33 or current l-o tree) you can share, I'd be happy to take a look and providing some feedback. Among other thing, if you have updated version of TI GPU code and SSI (CMT speech, ...) and camera stfuff, that could possibly save my week end ;-) > Besides of enabling the new kernel, we are working with number of > smaller and bigger issues for N900. Starting from the beginning, we > are now based on ARMv7 combiled code, so the code should be better > optimised for N900 now. ARMv5 compilation that was in use for code > drop will still be there, and it also seems to be used at least by > community project that is planning to release MeeGo for good old N810 > tablets ;) > > Also, we are planning to enable dual booting of Maemo 5 and MeeGo for > the upcoming release. So that will be offered as 3rd way to setup > MeeGo to N900, including the existing "native" MeeGo only on N900 and > chroot based MeeGo on Maemo 5 setups. Taking the dual boot mode into > use likely includes upgrade to Maemo5 kernel as well, but that should > not be big issue in the process of enabling that. > > As I don't want to go ahead of others working on MeeGo architecture > and other issues I will stop now, but I will report again when we have > more to tell about the subject. Cheers, a+ _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
