| 07:45 | vpeter | Nice. |
| 08:44 | topi` | trying to compile a buildroot for my usb-otg sessions... How can I append the resulting buildroot image to a zImage? |
| 08:44 | topi` | to create this famous 30 MB zImage ;) |
| 08:45 | topi` | do I need to enable BR2_KERNEL? |
| 10:03 | topi` | if I mistakenly configure the kernel "make menuconfig" without setting ARCH=arm, do I lose all my changes to config? |
| 10:03 | topi` | I guess I do, since it started make oldconfig |
| 10:03 | topi` | ls .. |
| 10:18 | jnettlet | yes, unfortunately. |
| 10:27 | topi` | I need a separate git repo for .configs ;) |
| 10:29 | topi` | I compiled a buildroot with "micropython" integrated, this is way cool. The upython binary is 411K and can import all the good stuff |
| 10:29 | topi` | >>> hashlib.sha256("foo").hexdigest() |
| 10:29 | topi` | '2c26b46b68ffc68ff99b453c1d30413413422d706483bfa0f98a5e886266e7ae' |
| 12:13 | topi` | rabeeh: you should install micropython onto your buildroot ramdisk, and build the tests upon it ... it's easy to do, say, mmap.mmap(open("/dev/fb0"), mmap.MAP_SHARED, 0) and then push some pixels in any desired locations... |
| 12:14 | topi` | also, from fcntl import ioctl and then do any ioctl you desire, without compiling a line of C code |
| 12:14 | topi` | it's also possible to write functions in pure arm assembly (in the same source file) |
| 14:14 | jnettlet | topi`, it probably doesn't run under micropython but I am reworking our tests into RedHat's Avocado framework. https://github.com/avocado-framework/avocado |