Rockbox Development > Starting Development and Compiling

Rockbox on Motorola Linux phones

<< < (2/2)

saratoga:

--- Quote from: rasputin007 on February 20, 2010, 05:51:00 PM ---That is what I meant with "preconfigured options". Naturally there is no Motorola V8 option in that configure script. And that was my question if it would be possible for me to add one to it and what would I need.

--- End quote ---

You need to actually port rockbox to your phone:

http://www.rockbox.org/wiki/NewPort

As Bagder said, the port to your phone was done independently of us, so we don't have any code at all written for it.

A better approach for now might be to get the code for the build you're using and start with it.  Then once you understand it start changing things. 

Bagder:
When writing "Rockbox As An App" to run within another OS and system, like the one you suggest, I think the only sensible thing is to make sure it builds with the stock compiler everything else in that OS is built with - rather than stick out your neck and build just this app with the Rockbox-endorsed compiler set.

I believe that old Motorola hack was more or less a simulator running on the phone, so they probably picked a configure target with a screen size that matched and then they built a simulator for that.

rasputin007:
I ran it with the arm-eabi (cross-compiler for V8 gcc 3.4.3 and libc.2.3), but it always complains that it can not find the "...-elf-..." gcc.
I could symlink and rename them from "arm-linux-gnueabi-..." to "arm-elf-....". Did the same on the arm-Debian that runs in Qemu, so that I could compile the V8 kernel with a newer gcc and libc version, as I am not able to bootstrap an arm-Debian rootfs, but still have problems as the 2.6.10 kernel and the gcc 4.3 do not seem to get on too well.

Well, as you can see I am not scared to try new paths, but it might take some time until I get somewhere.
I think the "original" Motorola Rockbox was build for the E8, which is also a Linux based OS, but quite different to Motomagx.

The suggestion about using an emulator as the platform to run Rockbox sounds actually quite convincing, as the Rockbox app has 2 executables (Rockbox.portrait and Rockbox.landscape) which are called by a shell script (run.sh or run2.sh). I just combined those 2 shell scripts into one, so you can chose how you want Rockbox to run.

Thanks for your input, and I am sure I have to come back with some more questions.

Chronon:
It is a simulator, not an emulator.  All communication with hardware is handled through SDL.  There's no emulation of specific hardware involved in it.

rasputin007:
Thanks Chronon for pointing this out.
I am looking now for support from the Motorola modding community, especially on the programming side, as I am not feeling competent enough there.

btw I was playing with the Rockbox 3.4 on the V8 last night and actually the volume buttons are working. It was the fact that usually you have not more then 10 volume steps (often less) on Moto apps, but Rockbox has far more volume steps and pressing the volume down button just 4 times hardly made any impact.
However it can easily happen that the keypad freezes after pressing some buttons in succession, or the flip gets closed and opened again, but still the power-off button works to turn off the phone in a "proper" manner.

Navigation

[0] Message Index

[*] Previous page