07:34 <mansson> Hi out there! Has anyone succeeded in building Android for rock960 and boot it from SD card? Build instructions stop at creating "update.img", but I guess that's not an image you can dd to the card. At least my board still boot from emmc when I try that. What am I missing?

09:09 <stdint> mansson, it is not used for dd but an rockchip android flash tool

09:16 <mansson> Yes. So my point is that instructions for creating an image suitable for SD card are missing. Correct me if I'm wrong. I'd rather not overwrite the factory supplied emmc Android system until I have verified that I can recreate it by building myself. So let me put it like this: If I build and flash emmc according to the instructions, will I still get the customized Android home screen that was factory supplied, or will

09:16 <mansson> I get the standard AOSP home screen?

09:43 <stdint> mansson, you can extract the update image as you want

11:08 <mansson> stdint, thanks. Yes, I have done that for Debian and it works, but prebuilt Android SD card images are currently not available for download at www.96boards.ai. I still need to transform my built Android "update.img" to a dd-able "system.img". Can't find out how.

11:08 <Ke> I just can't get the "images" for general purpose OS, after you have the kernel any userland should be portable

14:53 <Ke> eballetbo: now X is less slow, I got 100 on small window and 3 on fullscreen glxgears

14:54 <Ke> not that I care about 3d so much

15:25 <Ke> anyone using mwifiex (Kevin) with wicd

15:26 <Ke> scans do not find any ssids, iw does and wpa_supplicant can connect

17:45 <ezequielg> mmind00: for that Ficus board, I haven't been able to make USB work... however, I wouldn't like to block the entire support just for lack of USB.

17:46 <ezequielg> mmind00: having at least basic support there is useful, as we are planning to add this board to the LAVA lab and test general rk3399 regression with it.

19:57 <eballetbo> Ke: I get 22FPS on a fullscreen glxgears

19:57 <Ke> with blobs?

19:57 <eballetbo> nope

19:58 <eballetbo> without any blob

19:58 <Ke> which kernel and X etc.=

19:59 <Ke> I have 4.17.2 and whatever debian buster is shipping

19:59 <eballetbo> debian sid + 4.18-rc1 + X + lxde

19:59 <Ke> almost the same

19:59 <Ke> I guess I'll try rc2 next

19:59 <Ke> assuming it's released on sunday

20:00 <eballetbo> hmm, not sure if the problem is in the kernel

20:00 <Ke> do you use some xorg.conf?

20:01 <Ke> I just have automatic config

20:02 <eballetbo> Ke: if you are interested I have a tool that I use for kernel development that creates a bootable sd-card for kevin. I builds latest mainline kernel and install a debian stretch rootfs with lxde

20:02 <eballetbo> Ke: https://gitlab.collabora.com/eballetbo/chromebooks

20:03 <Ke> I can have a look, but I doubt it's different from what I am doing

20:03 <Ke> thanks

20:03 <eballetbo> ./chromebook-setup.sh --architecture=arm64 --storage=/dev/sdX do_everything

20:03 <eballetbo> will create a bootable sd-card, is the one I am using

20:04 <eballetbo> just that I updated from stretch to sid

20:06 <Ke> ARM64_DEBIAN_ROOTFS_URL="https://people.collabora.com/~eballetbo/debian/images/debian-stretch-chromebook-arm64.tar.gz"

20:06 <Ke> I guess this is just it

20:11 <Ke> are you using 32-bit system?

20:11 <Ke> ah no, there is ARM64 toolchain

21:56 <fysa> eballetbo, this is chrome OS with debian stretch linux apps available that works on rock64?