Mamona


INdT and Mamona28 Aug 2007 06:15 pm

Thinking to leave the main flash memory free for Mamona tests I looked for a way to have dual boot in the N800. Then I found a good documentation explaining how to easily boot from MMC card.

The only step that I skipped was the “How to install a dual boot menu?”.

To use the system in memory card I’ve edited the initfs manually  to access directly the partition created in the memory card. The only thing that I did was to add the code below in the begin of boot() function in linuxrc of initfs (My last post  explains how to edit and flash the initfs in your pc).

load_mmc_modules
root_dev=mmcblk0p2
root_dev_name=”MMC”
root_dev_set=1
root_fstype=”"
root_fsoptions=”"

As you can easily notice it is hard coded. Actually I’m not using a real dual boot because when testing mamona I need to flash the kernel too, so I prefer to flash a different initfs for mamona every time instead of have to press a button during the boot.

However it is possible to have a dual boot changing the begin of boot() function of linuxrc in initfs to be like that:

boot()
{
load_wlan_module
if ! grep -q new_root /proc/mounts; then
text2screen -t “Press any key for MMC boot” -H left -y 80 -s 2 -B 0xffff
key_pressed 1
if [ $? -ne 0 ]; then
load_mmc_modules
root_dev=mmcblk0p2
root_dev_name=”MMC”
root_dev_set=1
root_fstype=”"
root_fsoptions=”"
fi
mount_device “$root_dev”
fi
if [ $? -ne 0 ]; then
return 1
fi

Or following that step that I haven’t tried.

It is important to clarify that when you flash only the initfs and/or the kernel you don’t loose any data in your main flash memory or in your MMC card.

Another important thing to say is about performance. I’ve been using it for more than a week from  internal MMC slot and couldn’t notice any lost of performance when compared to a system booting from main flash memory.

Are you curious about Mamona booting on N800? This is a topic for another post…

INdT and Mamona06 Aug 2007 12:43 pm

mamona logo
This is a short post just to announce that now Mamona has a beautiful logo made by INdT designers, and that we finally added questions and answers to Mamona’s FAQ. But if your doubts weren’t answered by this FAQ, please contribute sending me your questions.

INdT and Mamona27 Jul 2007 05:36 am

I support mamona

“I support Mamona!” with a Mamona (castor oil plant in English) below – This was the support message that Marcelo Lira (setanta) left on my desk this morning. Nice, isn’t it? :-P

Impressions and INdT and Mamona26 Jul 2007 10:37 am

Today I read an email from Quim Gil where he was saying that a distro is a lot more than code, there are humans around it.

I completely agree with him. But I’d like to add that in a distro there are human believes, human expectations and human sweat.

There is no distro without believe. When someone decide to make a new distro he believes that it will be someway useful and somehow better than others that already exists. So this guy (or company) expects to do something with his distro. He expects to fill a need. After this job was started people start to believe (or not) and to expect something of his work.

I’ve already heard “Why there are too many Linux distributions? It is so complex, why don’t you join efforts and code just one distro?”, but the answer for that is quite simple: Humans are complex. We have different needs, different expectations and different believes so we code different distributions. It is completely normal.

But, there is no free lunch. Code a new and different distribution isn’t a very easy job. You need to work hard, and every help are welcome. Mainly from those who believes.

What I want and need to say is that if you believe and expect something of this new distribution, please, contribute. This kind of contribution that makes the free software community even better.

Finaly I’d like to say that I believe in Mamona, I expect that mamona will be used by community as a completely Open Source alternative and I’m working hard to code Mamona.

For those that don’t know yet:

Mamona is a completely open source distribution for arm that intends to be an useful and open SDK for Maemo platform. Running a simple chroot command you will easily have a complete arm distribution running in your pc emulated by QEMU (user-mode emulation).

http://mamona.garage.maemo.org/

INdT and Mamona and OpenEmbedded24 Jul 2007 02:25 pm

I’m pleased to announce that we already have the source code of base packages available under mamona’s repository (http://dev.openbossa.org/mamona).

Finally I could code a bbclass to OpenEmbedded to generate all files that are necessary to add the source to a deb repository:

* .dsc – debian source package control file
* .orig.tar.gz – Original source package
* .diff.gz – patches that we apply
* .changes – changes file

The sourcedsc.bbclass that generates these files is not under the OE repository yet. It is under evaluation by OE team. But it is available under OE bugtrack http://bugs.openembedded.org/attachment.cgi?id=1751
or under our svn: http://dev.openbossa.org/trac/mamona/browser/openembedded/trunk/org.openembedded.dev/classes/sourcedsc.bbclass

INdT and Mamona02 Jul 2007 12:22 pm

I’m planing to run mamona distribution in a real nokia device. My first challenge is related to usability of this: How to use a distribution that doesn’t have X and consequently doesn’t have a virtual keyboard in a device (n770/n800) that doesn’t have a real keyboard?

My first thought was try to use a n800 but I’ve realized that it wasn’t a good idea. First of all mamona packages are compiled to armv5te since qemu doesn’t support armv6 yet. I know that in theory armv5te programs should run in the armv6 arch but definitively it is *not* a good idea try to run a complete distro compiled for armv5te in an armv6 device. At least I don’t want to test it right now.

Another problem for this test in n800 is that I couldn’t use a real keyboard in the n800 because I couldn’t enable the usb host mode. I’m not sure, but I believe that it is impossible for n800. Please let me now if I’m wrong.

Then I changed my target to n770 because its arch is armv5te and I could use a real external common usb keyboard. See the video below:

I hope to post soon a video with mamona distro running in a n770 device.

INdT and Mamona20 Jun 2007 05:18 pm

Building Mamona

This file is a presentation that I’ve made to show to my team how BitBake / OpenEmbedded works to build Mamona packages.

I believe that it make easy to understand how OpenEmbedded is organized and how BitBake works.

I made this presentation usgin latex-beamer. The code is available under our svn.

INdT and Mamona12 Apr 2007 10:48 am

Mamona distribution is officially under OpenEmbedded repository!As soon as possible we will publish instructions how to use OE to build your own deb package. It is really very easy.

You’ll see …

INdT and Mamona10 Apr 2007 01:34 pm

We are proud to announce that our first (and non-official) beta public repository is already available at http://osmtc.indt.org/projects/mamona
It is just a repository with deb packages built using OpenEmbedded.

At this first public version all that you can do is try the debootstrap script installation and the chroot running all over qemu.

For us this first version is very important because it was a proof of concept that we can use OpenEmbedded to easily build .deb packages and setup it in our repository.

Unfortunately for a common user it is not useful yet, but you can try to install and see how easy and modular it is.

So, Try It !

INdT and Mamona31 Mar 2007 08:52 am

We are changing Mamona starting to use OpenEmbedded (OE – http://www.openembedded.org/) that is a great build system.

There are at least 4 good reasons to use openembedded:

- Avoiding monkey work – OE uses bitbake to build the packages. BitBake is a simple tool for the execution of tasks. It is derived from Portage.

- Avoiding monkey work – OE already has a lot of package descriptions.

- Community interaction – OE has a great and active community.

- Open Source.

Our plan is to use OE as a build system to build .deb packages and then setup a repository with these packages. Then, using a debootstrap script, the final user will be able to easily install the Mamona.

« Previous PageNext Page »