Intro/ working mode (Hah, 06:05:10)

1. As you know from some of my emails, we are now operating as open project (Hah, 06:05:37)
2. That means everybody can join, propose and do some work related to N900 hw adaptation (Hah, 06:06:06)
3. We don't have to do list yet, that is one of the first things of course tbd (Hah, 06:11:02)
4. Testing of course makes more sense after 1.0 relase next week (Hah, 06:12:03)
5. we haven't really discussed dividing out tasks in a open manner - one way could be the bugtracker, but not sure where we belong there (Stskeeps, 06:12:36)
6. So far we have mostly contributed Fremantle sw towards upstream/meego (Hah, 06:13:40)
7. Now we are approacing the point where we have enough functionality for others to join and help (Hah, 06:14:51)

# May Release blockers ? (Hah, 06:15:26)

1. There will be MeeGo release in may, likely on next week (Hah, 06:16:33)
2. waiting to be merged is sgx, audio, bluetooth, watchdog and battery charging suppotr (Stskeeps, 06:23:12)
3. IDEA: we need to have a N900 kernel package maintainer on board the kernel package maintainers group. this should speed up N900 related merge requests. (quadros, 06:23:51)
4. IDEA: or alternatively, the ARM platform maintainer role being put into place (Stskeeps, 06:24:19)
5. As we are very late with N900 adaptation, some kind of hack is maybe needed for 1.0 (Hah, 06:25:04)
6. There has been some discussion going on about these maintainer roles (Hah, 06:26:50)
7. for N900 example. I hope TSG will come up with some nominations at some point (Hah, 06:27:40)

Status update (Hah, 06:42:11)

1. Kernel support for BME ? (Hah, 06:42:52)
2. IDEA: , shouldn't bme be disabled till this cpu hogging issue is fixed? (quadros, 06:45:30)
3. There is a problem with BME eating 95% of CPU .. (Hah, 06:47:54)
4. Some internal work on that is needed, as BME is closed component (Hah, 06:49:58)
5. and at this I don't expect that it will be opended as such (Hah, 06:50:56)
6. Potential open version of BME needs project of it's own, if someone is interested (Hah, 06:51:43)
7. there has been some community rumblings from former openmoko people who know the battery charging chip well in regard to open charging, but that's a thing to be discussed how to deal with if it turns out to work (Stskeeps, 06:51:58)

Originally Posted by johnel

Fingers-crossed this happens (my nipples itch just thinking about it)

<comment about hack>

<comment about BME being 99% CPU>


(Huge thanks to everyone that is making this possible)

Originally Posted by Stskeeps

Regarding hack, we've moved to a full mainline 2.6.33 kernel and upstreamed things - I'm personally not surprised we're a bit late to have it integrated, enormous effort.

At least we're noting something is wrong and we need to fix it

However, please set your expectations right:

08:10:54 <Hah> UI for N900 will not be part of May release

This is part of TSG decision to move Handset UX release to a little after May release, it was mentioned and indicated at the previous TSG meeting.

However, as you can see, in our little part of the world, a lot of effort is going in.

However, as you can see, in our little part of the world, a lot of effort is going in

Originally Posted by johnel

E.g. The foundation has call-making software and BME support.

If that is the case the UI - to a certain extent is "not that important".

If a "fully" functional foundation is released then will there be an ability to install your own gui and possible write your own gui apps for n900 MeeGo.
In theory could you write a phone app similar to what is available in maemo now?

Originally Posted by Optln

Correct me if I'm wrong: What we're getting is a vanilla MeeGo release with Harmattan UX. But unlike next MeeGo-Harmattan phone, our OS will be using RPM instead of DEB right?