| 09:25 | Kernel | Morning all |
| 09:39 | frilled | I just picked up that we should not user the Installer on the CuBox Pro, but I could not find any other information on that. Does anyone have some background on that? |
| 10:04 | rabeeh | Kernel: hi |
| 10:04 | rabeeh | frilled: CuBox installer? |
| 10:06 | frilled | rabeeh, yes |
| 10:06 | frilled | It was mentioned on the forums, I think |
| 10:11 | rabeeh | http://www.solid-run.com/mw/index.php/CuBox_Installer |
| 10:11 | rabeeh | there is a user called _undo_ that has been hammering (for good and bad) the wiki |
| 10:12 | frilled | huh? |
| 10:12 | frilled | I don't see anything about the Pro there. I don't really care about it, but it seemed the easiest way to update uboot ... |
| 10:28 | rabeeh | it is the easiest way to update u-boot |
| 10:28 | rabeeh | pro and regular are almost identical, except memory size which is auto detected on boot. |
| 10:36 | purch | rabeeh: who is this undo? |
| 10:36 | rabeeh | undo is dung disguised. |
| 10:41 | purch | undo sounds a good nick to edit wiki pages =) |
| 10:47 | frilled | yeah, that's why I was wondering about "don't use the installer on the Pro" in the forst place! ;-) |
| 10:51 | frilled | first, even |
| 11:21 | dbsx | the easiest way to update uboot is |
| 11:21 | dbsx | # flashcp spi.bin /dev/mtd0 |
| 11:23 | rabeeh | dd if=u-boot.bin of=/dev/mtdblock0 |
| 11:30 | dbsx | dd works too? |
| 11:31 | rabeeh | yes. but only for the block device |
| 11:32 | dbsx | flashcp only erases and writes the pages it needs. Does dd on the block device wipe all of flash or just the required pages? |
| 11:33 | frilled | dd writes as much data as it read from if=, really |
| 11:34 | rabeeh | that's what the u-boot script that is in the installer. |
| 11:34 | dbsx | aha |
| 11:34 | rabeeh | http://download.solid-run.com/pub/solidrun/cubox/u-boot/cubox-installer-script/install-u-boot |
| 11:35 | rabeeh | but i'm not sure if the rest of the sector after the end of the u-boot image is reset to 0xff or the kernel knows how to keep |
| 11:36 | dbsx | I am guessing that the block driver does the required erasing (presumably for size of mtdblock0) |
| 11:37 | dbsx | or size of inout rounded up to 64k |
| 11:37 | dbsx | input that is |
| 11:39 | frilled | iirc there's no default for "bs=", so you should end up with the size of the original file padded to the next block size of the sd card |
| 11:40 | dbsx | frilled: catch is that writes to flash do not work unless they are erase beforehand. And you can only erase in either 4k or 64k lumps |
| 11:41 | dbsx | I have one box where the flash is in 512k pages |
| 11:42 | dbsx | make that 64k for my cubox |
| 11:43 | frilled | uh, but shouldn't the wear leveling in the controller redirect you to different cells anyway, so that you read the old block and write to a new one? |
| 11:44 | frilled | but true, you have to flatten that beforehand, too |
| 11:44 | dbsx | thats why people use UBIFS |
| 11:49 | frilled | the question is where to get raw flash devices ... never seen them for consumer use |
| 12:11 | dv_ | got a working yocto image with my custom layer :D |
| 12:38 | rabeeh | dv_: great |
| 12:38 | rabeeh | if you want i can add it to the installer |
| 12:43 | dv_ | okay, I'm still adding stuff, and need to get it looked at by OE experts |
| 12:43 | dv_ | one note though - I am using the contents of cubox-packages.tar.gz . |
| 12:44 | dv_ | building the packages from source (if there are any) etc. and I am also using your 3.6.9 kernel. you see any problems with that? |
| 12:50 | rabeeh | kernel no |
| 12:50 | rabeeh | the big package; it's way too big |
| 12:51 | rabeeh | i can untar it if you want (on the website) |
| 12:51 | rabeeh | it's simply original package that i'v downloaded from Marvell extranet |
| 12:56 | dv_ | the package is somewhat confusing at times |
| 12:57 | dv_ | for example, the libgfx headers and libraries are present twice, and the libraries in bin/ are larger than the ones in debian/ (probably stripped?) |
| 13:24 | dv_ | rabeeh: the package is somewhat confusing at times for example, the libgfx headers and libraries are present twice, and the libraries in bin/ are larger than the ones in debian/ (probably stripped?) |
| 13:25 | dv_ | also, what is all that tslib stuff? what is it needed for? same for the mtd-utils package. is this just extra stuff that happened to be in the package? in other words, not relevant to the cubox at all? |
| 14:07 | rabeeh | dv_ as i said; it's original from Marvell |
| 14:07 | rabeeh | tslib is for touch screen drvier that marvell used |
| 16:06 | jgroot86 | hello. Im new and i do want to know things about the cubox. |
| 16:09 | jgroot86 | is that oke here? |
| 16:12 | jgroot86 | could i? |
| 16:17 | undo | just ask |
| 16:20 | undo | or wait until rabeeh is back |
| 16:34 | `jpi | jgroot86: :) |
| 16:34 | `jpi | irc rule no 1: do not ask to ask :p |
| 16:35 | jgroot86 | thecubox is 1 core 800 mhz processor? |
| 16:41 | `jpi | yes |
| 16:52 | jgroot86 | and i heard and i did read on the internet that full hd movies arny working well yet? |
| 16:57 | jgroot86 | and could i use my android tablet as remote or me mobile in xbmc? |
| 17:05 | dv_ | rabeeh: alright, then I'll skip it |
| 17:08 | dv_ | rabeeh: so the mtd-utils, dove-av-d1-touch-conf, avengers-dove-SD8688 packages can all be skipped? |