**** BEGIN LOGGING AT Fri Jul 11 02:59:58 2014
Jul 11 08:22:18 <Abhishek__> **
Jul 11 12:52:11 <vvu> av500: now i cannot usb flash with the new debian images
Jul 11 12:52:29 <vvu> they are too big to fit in the ram then extract
Jul 11 13:09:06 <av500> so you flash directly?
Jul 11 13:09:12 <av500> ah, cannot
Jul 11 13:09:20 <av500> well, make it work
Jul 11 13:23:47 <vvu> now i wanna attach tar to /dev/tty
Jul 11 13:23:53 <vvu> read from pipe and flash directl
Jul 11 13:23:56 <vvu> no saving no nothing
Jul 11 13:24:30 <vvu> any clue how tar is handling pipes, so from host i am doing bulk_transfer with 400 bytes at time
Jul 11 13:24:41 <vvu> that should not be fast for tar think so
Jul 11 13:27:36 <av500> tar should not care
Jul 11 13:27:54 <av500> you have to make sure the usb side can handle the stalls
Jul 11 13:28:48 <vvu> i have write with timeout 0 so just wait forever
Jul 11 13:30:22 <av500> ok
Jul 11 14:46:11 <vvu> av500: some debugging hint https://gist.github.com/anonymous/12333838b23b01c6eab0 ?
Jul 11 15:05:41 <av500> vvu: what is that
Jul 11 15:05:43 <av500> vvu: what is that?
Jul 11 15:25:26 <vvu> av500: a kernel panic, from the BBB
Jul 11 15:25:42 <vvu> i was using FIT style to boot up and now i changed the ramdisk and the busybox binary
Jul 11 15:25:45 <vvu> and this appeared
Jul 11 15:25:47 <vvu> le wild kernel panic
Jul 11 15:26:17 <vvu> on the BBB i have a full eMMC wrote with angstrom and deled the MLO to go into usb boot mode
**** ENDING LOGGING AT Sat Jul 12 02:59:58 2014