There is already a thread about installing Debian on i5700 (without JTAG) and if I remember correctly it is also possible to make dual boot.
Запуск Debian Lenny на Samsung GT-I5700 Spica
But this discussion is already moving away from the topic.
@podtalje
Chrooting and using VNC doesn't make me 100% satisfied. I'm talking about other OS for serious (everyday?) use.
@tom3q
In theory, making 2 partitions (/ and /home) and swap on microSD card (or /home + swap) and then copying kernel, system folders, GNU apps, etc. should work. Am I right? Or is it impossible to do with Spica (for instance, because of bootloader)?
Why people can install Linux on HTC HD2 so easily and we can't?
Tapatalked from my Galaxy Spica
Tapatalked from my Galaxy Spica
sunbeam@my-spica
LOL Because Spica isn't HTC HD2!![]()
And the only way to partition Spica's internal memory is JTag?
It's rather expensive (I know it's worth the money) :/
Tapatalked from my Galaxy Spica
So only gotenks-sources would work? Or your future kernel?
Actually, I was thinking about replacing standard bootloader with GRUB or LILO. It should remove this silly limits.
Who knows, maybe other OS is the future of Spica. I don't like Android so much because of Google Java VM aka Dalvik.
Normal C/C++ gives better performance.
IMO Android drivers should be compatible with ordinary Linux ARM distro. Or is there a difference?
Tapatalked from my Galaxy Spica
Last edited by tom3q; 08-21-2011 at 03:30 AM. Reason: Merged two consecutive posts.
sunbeam@my-spica
No. There are no physical partition in the flash memory. You can get any partition layout, assuming that you force the driver to use your layout instead of the one stored in the XSR partition table. Actually this is very simple when the XSR driver isn't used, because the standard Linux MTD API doesn't have any idea about any XSR internal structures and it just takes all the information from platform data specified by the developer.
Why? Any sources working on Spica, this is what I meant.
Good luck.
Once, because GRUB and LILO are bootl oaders for x86 and one more time because without a JTAG you would have to guarantee that it would work on the first try.
What silly limits are you talking about? As I've written, you can boot any Linux distribution compiled for ARM v6 or less, but only with a kernel supporting Spica. This isn't a boot loader limit, this is how computers work.
Me neither, but it isn't that bad.
With JIT it should be comparable. Also many applications use native code for heavy tasks.
Well, I don't understand what you mean with Android drivers. There are kernel level drivers and so they are independent from the user space (=distribution) and there are user space libs bridging kernel drivers with Android-specific APIs (or common ones like X11). While my OpenGL implementation should be pretty compatible with anything, my EGL implementation is heavily dependent on Android, so it would have to be adapted for X11. Also X11 uses a different architecture than Android, separating 2D and 3D rendering paths, so a 2D DRI driver would be needed to get some 2D acceleration.
Generally, my recommendation is: forget it.
There are currently 1 users browsing this thread. (0 members and 1 guests)
Bookmarks