**** BEGIN LOGGING AT Sat Jun 15 02:59:59 2013
Jun 15 08:10:30 <vvu|Mobile> _av500_: ping
Jun 15 09:30:20 <vvu|Mobile> _av500_: when you have time please check this bootp reponse http://pastebin.com/D3h1pHBt for this request http://pastebin.com/6hXnh8Wz
Jun 15 09:31:14 <vvu|Mobile> i tried to set up isc-dhcp-server but it fails somewhere to start the service...bootpd does not make difference between vendor-class-identifier and does not work
Jun 15 09:31:41 <vvu|Mobile> at this point i can send the spl over usb and it runs smoothly.
Jun 15 09:40:17 <_av500_> so now MLO sends a bootp request?
Jun 15 09:40:33 <vvu|Mobile> nevermind, got it accepting my bootp response
Jun 15 09:40:33 <vvu|Mobile> :D
Jun 15 09:40:44 <_av500_> vvu|Mobile: in fact its not needed at all
Jun 15 09:40:52 <_av500_> at this point, we are in control
Jun 15 09:40:58 <_av500_> you can immediately start tftp
Jun 15 09:41:01 <_av500_> no need for ip etc
Jun 15 09:41:07 <_av500_> we control both ends of the pipe
Jun 15 09:41:15 <vvu|Mobile> mhmh i wanted to respect the implementation
Jun 15 09:41:24 <_av500_> which one?
Jun 15 09:41:27 <_av500_> well, ok
Jun 15 09:41:29 <_av500_> if it works fine
Jun 15 09:41:38 <_av500_> just saying
Jun 15 09:41:38 <vvu|Mobile> i am sending the same bootp response as in ROM bootp response
Jun 15 09:41:42 <_av500_> ok
Jun 15 09:42:10 <vvu|Mobile> we are going to have a problem with java
Jun 15 09:42:14 <vvu|Mobile> if there is no kernel driver
Jun 15 09:42:16 <vvu|Mobile> for rndis
Jun 15 09:42:27 <vvu|Mobile> the MLO does not start to send bootp requests
Jun 15 09:42:53 <vvu|Mobile> it hangs somewhere, lemme pastebin the output
Jun 15 09:44:36 <vvu|Mobile> _av500_: before bootp request 4 i disable the kernel driver with libusb_deatach_kernel_driver
Jun 15 09:44:37 <vvu|Mobile> http://pastebin.com/bnqT69Rf
Jun 15 09:45:01 <vvu|Mobile> and the kernel does not use a driver until i plug again the BBB
Jun 15 09:45:24 <vvu|Mobile> and when the spl starts again to send bootp it just hangs there
Jun 15 09:45:40 <vvu|Mobile> don`t know if it is normal behaviour or maybe something fishy
Jun 15 09:47:32 <_av500_> vvu|Mobile: we dont have a problem
Jun 15 09:47:35 <_av500_> we control MLO
Jun 15 09:48:39 <vvu|Mobile> perfect! at this point i will finish the linux implementation with this rndis+bootp+tftp if it is ok by you
Jun 15 09:48:52 <vvu|Mobile> mlo behaves exactly the same as rom
Jun 15 09:49:55 <_av500_> sure
Jun 15 09:50:16 <_av500_> we can try to redo that now in android
Jun 15 09:50:32 <vvu|Mobile> redo rom boot ?
Jun 15 09:50:33 <_av500_> get some leds blinking
Jun 15 09:50:47 <_av500_> well, do the same in java with android api
Jun 15 09:50:49 <vvu|Mobile> i can see serial output, have cable
Jun 15 09:51:00 <_av500_> vvu|Mobile: i know :)
Jun 15 09:51:05 <_av500_> but for extra show effect :)
Jun 15 09:51:31 <_av500_> a random user would not have the serial
Jun 15 09:51:46 <vvu|Mobile> okok :) mhmh i will stay and finish this linux implementations in like max 3-4 days to get kernel on the board
Jun 15 09:52:00 <vvu|Mobile> and after i have full here with good code i will start on android
Jun 15 09:52:09 <_av500_> 3ok
Jun 15 09:52:10 <_av500_> ok
Jun 15 09:52:12 <_av500_> bbl
Jun 15 09:52:18 <vvu|Mobile> me too a bit
Jun 15 19:23:47 <tarocco> ciao
Jun 15 22:37:54 <vvu|Mobile> _av500_: u-boot is now on the board!
Jun 15 23:36:19 <vvu|Mobile> _av500_: everything is on git but code is very very messy. 2morrow i will refactor it properly not to have compile warnings and a bit optimized.
**** ENDING LOGGING AT Sun Jun 16 02:59:58 2013