Closed Thread
Thread Tools
Posts: 174 | Thanked: 193 times | Joined on Nov 2007 @ Bologna, Italy
#11
Originally Posted by Stskeeps View Post
On a silly sidenote: I had MeeGo base system running on my N810 with 2.6.33 kernel (+ Termanas, luke-jr's patches) some weeks ago.
where are? .diff ? git repo? .deb ?
__________________
User:rlinfati
 

The Following User Says Thank You to rlinfati For This Useful Post:
Posts: 751 | Thanked: 521 times | Joined on Mar 2007 @ East Gowanus
#12
I have an N800 I could loan to someone actively working on this or use it for testing.
 

The Following 3 Users Say Thank You to mobiledivide For This Useful Post:
Posts: 2,803 | Thanked: 4,469 times | Joined on Nov 2007
#13
Crap, after various unsuccesful attempts to build & boot a modern kernel it seems I managed to fry my N810's camera:

Code:
[    1.101562] OMAP GPIO switch handler initializing
[    1.101562] gpio-switch: required switch not found (-1, cam_act)
[    1.101562] gpio-switch: required switch not found (-1, cam_turn)
[    1.101562] slide (GPIO 110) is now open
[    1.101562] kb_lock (GPIO 102) is now open
[    1.101562] headphone (GPIO 107) is now disconnected
[    1.101562] menelaus 1-0072: Setting voltage 'VMEM' to 1500 mV (reg 0x0a, val 0xb4)
[    1.117187] menelaus 1-0072: Setting voltage 'VIO' to 2500 mV (reg 0x0a, val 0xb8)
[    1.164062] tcm825x_read_reg: trying again (-121)
[    1.179687] tcm825x_read_reg: trying again (-121)
[    1.195312] tcm825x_read_reg: trying again (-121)
[    1.210937] tcm825x_read_reg: trying again (-121)
[    1.226562] tcm825x_read_reg: trying again (-121)
[    1.242187] tcm825x_read_reg: trying again (-121)
[    1.257812] tcm825x_read_reg: trying again (-121)
[    1.273437] tcm825x_read_reg: trying again (-121)
[    1.273437] mmci-omap mmci-omap.1: command timeout (CMD8)
[    1.273437] mmci-omap mmci-omap.1: command timeout (CMD8)
[    1.289062] mmci-omap mmci-omap.1: command timeout (CMD8)
[    1.289062] mmci-omap mmci-omap.1: command timeout (CMD8)
[    1.289062] dev_init(): Failed to detect TCM825x sensor chip
[    1.289062] omap24xxcam omap24xxcam: cannot initialize sensor, error -16
(No, flashing vanilla Diablo, leaving the battery out for a while etc didn't help)

No one's to blame but me of course, but be careful out there!
 

The Following 2 Users Say Thank You to lma For This Useful Post:
Bundyo's Avatar
Posts: 4,190 | Thanked: 2,827 times | Joined on Oct 2007 @ Bulgaria
#14
Or just messing up the kernel options? What does booting a Diablo say?
__________________
Technically, there are three determinate states the cat could be in: Alive, Dead, and Bloody Furious.
 
Posts: 2,803 | Thanked: 4,469 times | Joined on Nov 2007
#15
That was Diablo :-(
 
Stskeeps's Avatar
Posts: 1,586 | Thanked: 10,165 times | Joined on Jun 2008 @ Warsaw, Poland
#16
As we now have some kernels to play with on recent versions for N8x0, I suggest we start the real work.

Tools of the choice: Fedora chroot or VM. There's problems with MIC2 currently that needs to be fixed before we have proper support on Debian/Ubuntu. This guide should get you started building RPM packages for MeeGo.

I have some tasks we need to get started on in order to get N8x0 properly supported. Who will take these?

1) Adapt the kernel source package from MeeGo to make a kernel build for the N8x0. There is some work regarding 2.6.33 already we can probably piggyback on for ARM support. The patches Termana and tmr has provided should provide a good basis for this.

2) Package up Xomap for MeeGo - there is no good omapfb driver for N8x0 for Xorg sadly. Alternatively, someone can put in effort to work on this.

3) Integrators - someone good with RPM packaging that developers can contact regarding questions.

4) Testers - we need 2-3 committed testers to test the output, documentation provided, etc.

Testers so far: rlinfati

Discussion topics:

* What should be our deployment target? My suggestion is to target at least a 2GB (mini/micro)SD card and boot from there.
* What should be initial (realistic) hardware usable for MeeGo 1.0 with N8x0 HW adaptation? Remember, MeeGo 1.0 is in May
* Should we even care about the 3d drivers or should we look into OpenVG for Qt for instance?
* What would be useful to have Nokia provide in a tablets-dev.nokia.com RPM repository (closed source bits), so people can generate images with the bits.
__________________
As you go on to other communities, remember to build them around politeness, respect, trust and humility. Be wary of poisonous people and deal with them before they end up killing your community.. Seen it happen to too many IRC channels, forums, open source projects.

Last edited by Stskeeps; 04-10-2010 at 03:06 PM.
 

The Following 10 Users Say Thank You to Stskeeps For This Useful Post:
Posts: 174 | Thanked: 193 times | Joined on Nov 2007 @ Bologna, Italy
#17
i have a n800, i can test...
__________________
User:rlinfati
 

The Following User Says Thank You to rlinfati For This Useful Post:
Posts: 99 | Thanked: 48 times | Joined on Jan 2007 @ Tampere, Finland
#18
Originally Posted by Stskeeps View Post
* What should be our deployment target? My suggestion is to target at least a 2GB (mini/micro)SD card and boot from there.
2GB sounds good to me.

Originally Posted by Stskeeps View Post
* What should be initial (realistic) hardware usable for MeeGo 1.0 with N8x0 HW adaptation? Remember, MeeGo 1.0 is in May
I would like to have WiFi and/or Bluetooth and touchscreen. HW keyboard would be a bonus .

Originally Posted by Stskeeps View Post
* Should we even care about the 3d drivers or should we look into OpenVG for Qt for instance?
I haven't seen much activity regarding 3D driver here in TMO so I guess it's not really working? I would choose the easier route and if OpenVG for Qt is easier, I would vote for that. 3D acceleration is nice-to-have feature, not must-have.
 
Termana's Avatar
Posts: 32 | Thanked: 74 times | Joined on Sep 2009 @ South Australia
#19
I am willing to adapt the n8x0 patches to the MeeGo kernel (though I'll need to have someone else test the n800 kernel), but as I mentioned in #mer, the kernel source is only available in RPM format. Can the MeeGo Project make the source for the kernel available in plain .tar.gz format? Or is anyone willing to do this independently?
__________________
Follow me @Termana on Twitter
 

The Following User Says Thank You to Termana For This Useful Post:
Posts: 2,803 | Thanked: 4,469 times | Joined on Nov 2007
#20
I may be missing your point entirely, but you should be able to extract the contents of the source RPM with rpm -i or rpm2cpio on any LSB-compliant distribution.
 
Closed Thread

Tags
hardware adaptation, meego

Thread Tools

 
Forum Jump


All times are GMT -4. The time now is 10:19 PM.