maemo.org - Talk

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Alternatives (https://talk.maemo.org/forumdisplay.php?f=36)
-   -   Mer v0.7 release, and community firmware contents discussion (https://talk.maemo.org/showthread.php?t=26567)

neatojones 2009-02-03 05:30

Re: Mer v0.7 release, and community firmware contents discussion
 
maybe a dpkg --reconfigure whatever package installs the menu? I have no idea if that will work, but it would sure beat a reflash.

Edit: I looked it up, and it looks like that package would be hildon-desktop, so a reconfigure or reinstall may work, but it might also make any personalizations to the system be lost. Basically, you need to ensure you have /etc/xdg/menus/applications.menu and /home/users/.osso/menus/applications.menu

fatalsaint 2009-02-03 05:32

Re: Mer v0.7 release, and community firmware contents discussion
 
Ok.. I upgraded my MCE and now it starts good.. My apt-get runs good now.. but still having no menu.. so maybe it is something with the installer.

Odd.

neatojones 2009-02-03 05:54

Re: Mer v0.7 release, and community firmware contents discussion
 
Fatalsaint, see this bug, it may not be exactly your problem, but the fix might work: https://bugs.maemo.org/show_bug.cgi?id=3795
...
cp /etc/xdg/menus/applications.menu /home/users/.osso/menus
13. Application menu is restored with default menu arrangement.
14. Reorganizing menu in Panels works.

fatalsaint 2009-02-03 06:11

Re: Mer v0.7 release, and community firmware contents discussion
 
I love you......

ETA: 0 bytes of free space is usually a bad thing :D

fatalsaint 2009-02-03 08:32

Re: Mer v0.7 release, and community firmware contents discussion
 
Ok.. since I was bored tonight: I thought I would document a complete installation of Mer from beginning to end.

http://blog.linuxniche.net/?p=16

It has lots of perty pictures.. probably tons of bad spelling (it's 1:30 AM!) and I am messing with the format and templates/layout of my new blog right now.. so it may look funny/different throughout the days.. but I am going to bed now.. let me know what you think!

qwerty12 2009-02-03 08:39

Re: Mer v0.7 release, and community firmware contents discussion
 
Quote:

Originally Posted by solca (Post 261667)
Desn't link to an official Nokia domain...

Was illegally leaked? :rolleyes:

You're getting too excited if you think any company that wants to sell devices releases their schematics officially.

BTW, I searched for the schematics on the G1 and can't find any "official" schematics on the T-Mobile site, nor HTC's one.

Stskeeps 2009-02-03 08:48

Re: Mer v0.7 release, and community firmware contents discussion
 
Really crap picture, but this is Mer 0.7 running on a Beagleboard (and will hence have official image in 0.8)

http://www.daimi.au.dk/~cvm/mer-beagle.png

fanoush 2009-02-03 08:53

Re: Mer v0.7 release, and community firmware contents discussion
 
Quote:

Originally Posted by solca (Post 261649)
ten years from now everybody would benefit from updated open source drivers, updated kernels and documentation for the G1/ADP1; but for the tablets... you simply can't, you will always be stuck with the historic 2.6.21 Nokia release.

Huh? Fortunately you already proved yourself wrong by messing with Mer and newer kernels ;-)

Currently the only closed critical part is battery charging. Let' hope Nokia will give us at least static version of bme (not a solution for non-linux kernels of course).

Stskeeps 2009-02-03 09:15

Re: Mer v0.7 release, and community firmware contents discussion
 
Quote:

Originally Posted by fanoush (Post 261730)
Currently the only closed critical part is battery charging. Let' hope Nokia will give us at least static version of bme (not a solution for non-linux kernels of course).

Speaking of BME, did you see this?

fanoush 2009-02-03 09:28

Re: Mer v0.7 release, and community firmware contents discussion
 
Quote:

Originally Posted by Stskeeps (Post 261731)
Speaking of BME, did you see this?

Nice. What would be useful in addition to this is to get linkable object file (.o) implementing the charging procedure. One could feed it with proper file descriptor to retu and it would do the magic of banging the retu ADC charging channel bits properly. That would be a bit better than static version which could in theory break with some general kernel API changes. Also one could implement retu driver in non-linux kernel and pass compatible file descriptor to it.


All times are GMT. The time now is 00:11.

vBulletin® Version 3.8.8