Quote:
|
is it possible to have a version with only minimal debian installation with no apps no games no develop?!? thanks
|
Of course. Debian is installed in chroot enviroment. It means that whole system is under "debian" folder on SD card. You can create as many subsystems (chroot folders) as you want. You may install ubuntu side by side with Deabian. You can choose which packets you need - or you can just remove unwanted packets from my demo image with apt-get command. It's a real distribution
That's a beauty of it.
I chose Debian because it's the only decent distrubution that supports armel architecture and I needed armel architecture to run mono 3.2.1 (also java runtime is compiled for armel too).
Newest ubuntu is compiled for armhf (that means faster float operations). But mono packet is unusable there - there is unsucessful hack for armhf - if you ask it for 2^10 it answers 0.078
Armhf is great if you want faster audio and video processing - but I think that's doesn't matter on Kobo at all.
Quote:
|
8gb is the minimum sd card needed?!? just because i have to to buy a new one
|
Yes, because the image is 8GB large. You can buy larger one (and resize partitions with gparted on linux or leave it as it is and resign from additional space). The image has 3GB free space on system partition and 2GB free space on user partition (only 3GB are used).
It is a sample installation. Like your system on your on PC - it's an individual thing and everyone may want to use different sizes and packets.
Quote:
|
The partitions look a little odd, compared to the Kobo ones.
|
Yes. They are. I deleted recovery partition. It had no sense for me to keep it. And I added swap partition for virtual memory. Kobo has only 256 MB of RAM. That's not very much. Is it true that Aura HD has 1GB of RAM??
As a side effect I've changed system drive partition from mmcblk0p3 to mmcblk0p2 to have swap partition at the end of SD card. Maybe it was wrong decision, because I had to replace all references to mmcblk0p3 to mmcblk0p2 (also in nickel.so.1.0.0 with hex editor). So if you want to customize your image, maybe it's better to repartition it that way that system partition is still mmcblk0p3 and swap file is mmcblk0p2 (and not vice-versa). It will be easier to upgrade kobo software later. Now there is firmware 2.5.2 installed.
The startup menu uses python for Kobo 2.5.2 from Kevin, so that's another thing that's need to be ugraded if you want to upgrade kobo software to 2.8.1 (or you can change startup menu to the one from tshering for example. That's why I love this forum - things from different people can work together. The replace of mmcblk0p3 -> mmcblk0p2 or repartitioning is needed, too of course.
Quote:
|
I tried the image on my Glo, and it does work (mostly). It still thinks it has an 800x600 resolution, so not all the screen is used and the touch calibration is off a bit, but it starts up fine. Very nice work, Marek!
|
Kevin! That's really great news! Of course everything can be tweaked. My x11 touch driver is one big hack. Probably I hardcoded resolution somewhere
.
So maybe it's working with Mini, too - it has 800x600 resolution.
I was excited that the chip inside Kobos supports two fingers at the same time but after making changes in the kernel I was also disappointed that I cannot find/configure any existing multitouch driver for X11 that has a) mouse emulation - movement and left click b) right click simulation c) gestures, so I started hacking my own and I implemented only a). But it's great that in the future the gestures may be supported (I can't wait for pinch zooming). Changes in kernel are done. We still need more expanded X11 driver for that.
Quote:
|
Are you planning on releasing your kernel changes?
|
Yes. I will upload it on git-hub
Maybe in the weekend.
There are a few things that may be improved later - like adding rules for automatic fullscreen refresh or adapting changes to support all devices (maybe changes in touch code for GLO are needed?).
Hm.. Kevin - is touch working accurately when you boot to original kobo software from start-menu? If yes, the problem is not in the kernel but in my hacky x11 touch driver. If not, the problem is in the kernel.