|  06:16  |  Coburn  |   cbxbiker61: your latest kernel apparently turns off the led?  | 
|  06:35  |  cbxbiker61  |   Coburn, yes somewhere along the line rabeeh added a patch that dims the led once the cubox is booted  | 
|  06:40  |  Coburn  |   Well, it's completely off...  | 
|  12:54  |  Bochi  |   moin  | 
|  12:55  |  Bochi  |   what distro is currently recommended for xbmc on cubox, or what's the best way to get xbmc running nicely on cubox?  | 
|  12:56  |  Bochi  |   from what I read on the forums experiences differ from "running very well" to "argh"  | 
|  13:26  |  Thirsty  |   Bochi: I think Geexbox is now one of the best.  | 
|  13:27  |  Thirsty  |   geexbox now heavy under development to make it more smooth and perfect  | 
|  13:27  |  Thirsty  |   I can't wait for a new snapshot build.  | 
|  13:28  |  Thirsty  |   I read the last version commits and they are very promissing.  | 
|  13:33  |  Bochi  |   hmm ok thank you Thirsty, I will give it a shot  | 
|  13:37  |  Thirsty  |   here you will find the latest snapshots. http://download.geexbox.org/snapshots/geexbox-xbmc-armada5xx-cubox/  | 
|  13:39  |  rabeeh  |   there should be a new build on the way that make fps higher  | 
|  13:39  |  Bochi  |   yeah the geexbox site soulds promising  | 
|  13:39  |  Bochi  |   solidrun partnership and everything  | 
|  13:39  |  dbsx  |   wtf is it with oct3 uboot? It refuses to allow you to update bootcmd  | 
|  13:40  |  dmitrijus  |   dbsx: yes, i hate too!  | 
|  13:41  |  Thirsty  |   did anyone tried u-boot with v3.8 kernel with device tree support?  | 
|  13:41  |  dbsx  |   Nice idea if only the usb functions were made to work first. Inordinately stupid move  | 
|  13:41  |  dbsx  |   gnite folks its nearly midnight its hot and I am most annoyed  | 
|  13:42  |  Thirsty  |   good night.  | 
|  13:44  |  rabeeh  |   dbsx: yes - it overrides that  | 
|  13:49  |  rabeeh  |   dbsx: i though it was a good idea not letting people mess with bootcmd.  | 
|  14:50  |  dbsx  |   rabeeh: it might be a good idea if uboot was tested and perfect, which it is not. Not being able mod uboot means that I am stuck with situation where  I cannot modify uboot to demonstrate a ported application to a corporate client. Time does not permit a rebuild. Which means I have cancelled the demonstration. As it stands the uboot setup is a total disaster. Losing a corporate client is a bigger disaster.  | 
|  15:16  |  punkt_  |   change from uboot to barebox  | 
|  15:35  |  dmitrijus  |   rabeeh: restricting users is never a good idea..  | 
|  15:36  |  `jpi  |   dmitrijus: true i have a ethernet console where the u-boot time is 0. depending on a hardware switch  | 
|  15:37  |  rmull  |   Thirsty: Your new kernel updates fixed some audio glitching I was having. Thanks!  | 
|  15:37  |  `jpi  |   i wanted to ignore the status of the pin by modifying u-boot but i messed something . now can't boot it :(  | 
|  15:37  |  `jpi  |   needs jtag :p  | 
|  15:37  |  `jpi  |   but there are no pins on it=> soldering  | 
|  15:38  |  punkt_  |   `jpi: why do you need jtag  | 
|  15:38  |  `jpi  |   i hate when things like this poorly designed :(  | 
|  15:38  |  `jpi  |   messed up u-boot  | 
|  15:38  |  punkt_  |   `jpi: the cubox can load the bootloader via serial  | 
|  15:38  |  `jpi  |   hey i was talking about an ethernet consloe  | 
|  15:38  |  `jpi  |   not cubox  | 
|  15:39  |  punkt_  |   `jpi: oh, i see, whatever ethernet console that is  | 
|  15:39  |  `jpi  |   opengear  | 
|  15:40  |  `jpi  |   they also gave me a pinout of the jtag but it needs soldering the board :)  | 
|  15:40  |  punkt_  |   `jpi: to sad  | 
|  15:43  |  dmitrijus  |   `jpi: why would you ever want to ignore that pin?  | 
|  15:57  |  rabeeh  |   dmitrijus: what do you suggest then? i'm stuck between pros and beginners  | 
|  15:57  |  rabeeh  |   pros wants everything tweakable and beginners wants things more easy  | 
|  16:01  |  rabeeh  |   tomlohave-away: ping  | 
|  16:09  |  dmitrijus  |   rabeeh: i suggest just: if (! getenv("dont_override_because_im_an_engineer")) { :)  | 
|  16:09  |  rabeeh  |   hehe  | 
|  16:10  |  rabee  |  16:10  * rabeeh cuts and pastes from IRC  | 
|  16:10  |  dmitrijus  |   :D  | 
|  16:10  |  bencoh  |   ^^  | 
|  16:11  |  bencoh  |   (I definitely wouldn't like being able to tinker with my bootcmd, btw)  | 
|  16:11  |  bencoh  |   (it would just prevent me from working ;)  | 
|  16:13  |  dmitrijus  |   well, not just bootcmd, maybe tip: changing trydev order to "mmc ide usb", since usb takes about 10 seconds to initialize  | 
|  16:13  |  rabeeh  |   http://pastebin.com/yyu1CBtE  | 
|  16:13  |  dmitrijus  |   :DD  | 
|  16:13  |  dmitrijus  |   thanks  | 
|  16:16  |  rmull  |   What problem does this solve?  | 
|  16:16  |  rabeeh  |   the 10 seconds is mainly if someone is using a mechanical usb drive, which gives extra time to spinup the drive  | 
|  16:16  |  rabeeh  |   rmull: overriding bootcmd on every boot  | 
|  16:17  |  rmull  |   Why would we do that in the first place?  | 
|  16:17  |  rabeeh  |   :)  | 
|  16:17  |  rabeeh  |   scroll up  | 
|  16:17  |  rmull  |   Isn't the default bootcmd acceptable? If someone is a novice, why would they change it?  | 
|  16:17  |  rabeeh  |   because he is a novice  | 
|  16:18  |  rabeeh  |   well... resetenv would fix it  | 
|  16:18  |  rmull  |   I strongly disagree with this decision  | 
|  16:18  |  dmitrijus  |   yep  | 
|  16:18  |  rmull  |   FWIW  | 
|  16:18  |  rmull  |   Obviously flipping switches and turning knobs is something that may have undesired results if you don't understand what you're doing  | 
|  16:18  |  rabeeh  |   ok. i can change that and give it a month or two  | 
|  16:19  |  dmitrijus  |   rmull: well, so, don't  | 
|  16:19  |  rabeeh  |   ok.. there are tricky parts -  | 
|  16:20  |  rabeeh  |   i force the following too -  | 
|  16:20  |  rabeeh  |           setenv("mmc_started","0");  | 
|  16:20  |  rabeeh  |           setenv("ide_started","0");  | 
|  16:20  |  rabeeh  |           setenv("usb_started","0");  | 
|  16:20  |  dmitrijus  |   these are okay  | 
|  16:21  |  dmitrijus  |   the only problem is the bootcmd, if you have that, you can override everything else :)  | 
|  16:22  |  rmull  |   Maybe you should override the 'rm' command so that people don't accidentally delete things <_<  | 
|  16:22  |  rmull  |   Being sarcastic, of course  | 
|  16:25  |  dmitrijus  |   rmull: well, the current situation (in my eyes) is that people wanting to do some non-standard bootup end up patching/flashing u-boot, which has much more potential for screwing up  | 
|  16:26  |  rmull  |   I understand, but I would expect that people understand the implications when they start mucking about with things like that. Perhap the documentation should stress the point or something.  | 
|  16:28  |  dmitrijus  |   sure  | 
|  16:28  |  dmitrijus  |   i agree  | 
|  16:29  |  bencoh  |   btw, what's the real problem with someone unexperimented messing with its own bootcmd ?  | 
|  16:30  |  bencoh  |   I mean, he can still reflash with xmodem as a last resort  | 
|  17:07  |  Thirsty  |   rmull: Great!  | 
|  17:07  |  Thirsty  |   back to home  | 
|  23:41  |  dbsx  |   I just read the irc archive from when I was asleep. It seems that rabeeh is confused about whether he is supporting consumer electronics or a DEVEL kit  | 
|  23:48  |  dotarray  |   yes.  | 
|  23:48  |  dotarray  |   ...in a word, yes.  | 
|  23:56  |  dbsx  |   So [.] (thats a dotarray), maybe you change the website to say 'CuBox unmodifiable kit'  rather than 'CuBox devel kit'  |