<rz2k>
lets extract stuff out of that timesys rootfs
<rz2k>
and have normal hfp linaro running
<abrasive>
maybe now i can consider arch again.
<rz2k>
yes, this too
ajayr has quit [Remote host closed the connection]
ajayr has joined #imx6-dongle
hste has joined #imx6-dongle
hroth has joined #imx6-dongle
hroth has quit [Quit: irc2go]
hroth has joined #imx6-dongle
<hroth>
I'm using the compiled uboot (u-boot_multi_boot.imx from stende) - can it boot Android? I don't quite understand Android but u-boot says it doesn't recognize much when I put in an Android image 1.65.4 in the external SD slot.
<abrasive>
it probably can but you might need to have a little chat to it about where the kernel is and what its args are.
<hroth>
Good point. As I page through ext2ls mmc 1:5, 1:6, etc. I'm not sure I even understand where it is myself!
<hroth>
I'm thinking I'm missing a pretty big README file but this partition and directory structure is totally different from a typical Linux environment.
hste has quit [Ping timeout: 240 seconds]
<projectgus>
hroth: my understanding is android often has a weird composite boot partition which is its own kernel+initrd+header format
<projectgus>
that might be a device-specific thing not an android-specific thing though
<projectgus>
the "boot.img" i think it is usually called
jas-hacks_ has joined #imx6-dongle
<jas-hacks_>
abrasive: I tested the timesys gpu libs against a linaro armhf, they seem to work.
<hroth>
projectgus: Yes it does look strange, at least to me. mmc 1:4 looks like it can only be read by fatls too! Reviewing the Freescale Android user guide doesn't seem to help - it's all about their reference board.
Noskcaj has quit [Quit: good bye]
<hroth>
Also the Freescale docs talk about "booti".
<projectgus>
it's not just the kernel image dd-ed to that partition is it?
<projectgus>
(nb: I haven't read the page, sorry!)
* projectgus
reads page
<projectgus>
no i see it clearly says there's a filesystem
<projectgus>
i'd maybe check that partition for either a zImage header or an android boot.img header
<projectgus>
you'll have to look up that format I'm afraid, I don't know much about it although have come across it before
<hroth>
Probably Boundary Devices' designs are more organized that the GK802.
<jas-hacks_>
hroth: are using the multi-boot uboot?
<projectgus>
seems likely :)
<hroth>
jas-hacks_: yes, I was just wondering if it could boot the GK802 Android image.
<hroth>
(the 1.65.4 Richtechie image)
<hroth>
I'm sure you're right, projectgus - probably partition 1 is just a raw image of the kernel. I'm not finding whether the multi-boot uboot can load binary directly without a filesystem.
<hroth>
Maybe "iminfo" or "imxtract"..
<jas-hacks_>
hroth: then you have to modify the boot.scr on the internal SD so that it can load the kernel from the offset position where it is "dd" on the sd card. Furthermore it is most likely that you have to change some of the android properties files to refer to mmc1 make it boot/run correctly.
Noskcaj has joined #imx6-dongle
<hroth>
jas-hacks_: The boot.scr on the internal SD? Right now the internal SD just has the multi-boot uboot and the external SD has the 8GB RichTechie image. I'm not even sure there is a boot.scr on the internal SD to modify.
<jas-hacks_>
hroth: You need to create a boot.scr on the internal SD, which tells it to load and launch the kernel from the external SD.
<hroth>
Is there a posting or web page describing how this Richtechie distribution is set up partition wise? I'm not sure where the kernel is offset (I suppose I could try to sift through the binary?) and the first 3 partitions all seem raw.
<hroth>
jas-hacks_: Thanks. I'll try that.
<jas-hacks_>
hroth: kernel offset should be same as what we used to use on ubuntu.
<hroth>
jas-hacks_: Ah, right. Because we were also using the stock u-boot along with the stock image.
<jas-hacks_>
hste: I installed KDE which is support GLES acceleration, some of which works well.
<Kaiyoti>
awesome
<Kaiyoti>
that fixed it
<Kaiyoti>
thanks jas-hacks_
<hste>
:)
<jas-hacks_>
hste: The main issue is that we will be stuck on ubuntu precise armhf as the gpu xorg drivers support up to xorg 1.11. Quantel is on xorg 1.13
Noskcaj has joined #imx6-dongle
Noskcaj has quit [Changing host]
Noskcaj has joined #imx6-dongle
<hste>
jas-hacks_: but its still armhf
<hste>
jas-hacks_: and I guess its a good thing for xbmc too
<jas-hacks_>
hste: :)
<hste>
jas-hacks_: did u manage to get vpu working?
<jas-hacks_>
hste: Won't have time to look at it until the weekend
jas-hacks_ has left #imx6-dongle [#imx6-dongle]
Noskcaj has quit [Remote host closed the connection]
hste has quit [Ping timeout: 240 seconds]
<abrasive>
oh yeah... xorg ABIs
<abrasive>
arch is probably least likely to work with any given binaries then, they roll so fast.