=== zz_chihchun is now known as chihchun [04:34] hi guys, I wanna to learn arm, is there some place I can go from there, such as newbie tutorial [04:34] thanks [05:08] jenenliu: best way to learn is to figure out a goal, something real that you want to achieve. And then start doing it. It's not really efficient to just "learn arm". [05:21] kulve: thanks [09:22] hi [09:23] this documentation https://wiki.ubuntu.com/Nexus7/UsingTheDevice states under Attaching a USB Device to the Nexus 7 -> There is no way to charge the device while it is connected to the OTG cable. why? [09:24] with the OTG cable the device is the USB host, so it's giving power out through the USB cable. Where would it take power in for charging? [09:27] rnix: grab cheap chinese powered hub, connect it to OTG and check what will happen [09:27] <[mbm]> https://bugs.launchpad.net/ubuntu-nexus7/+bug/1072320 [09:27] Launchpad bug 1072320 in ubuntu-nexus7 "please consider adding OTG charging support to kernel" [High,In progress] [09:28] so if i build something like this -> http://www.instructables.com/files/deriv/FDR/71ZI/GINP15VZ/FDR71ZIGINP15VZ.LARGE.jpg -> and connect to a usb hub it might work? [09:29] <[mbm]> but basically kulve is right; otg doesn't really provide a way to charge, the above is just a driver hack [09:30] <[mbm]> rnix: yes, a combination of that and a patched driver [09:35] thx [09:38] and that driver hack makes the USB driver hardlock ... thats why we dropped it again (after testing it) [09:40] <[mbm]> I'd be a bit scared of accidentally having both the nexus and the external power active at the same time [09:41] heh [09:49] ogra_: what do you mean with "makes the USB driver hardlock" ? [09:50] rnix, you can charge but not use any devices [09:50] which kind of defeats the purpose :) [09:51] hmpf, true [09:51] and since that image most likely will die anyway in favour of ubuntu touch there is nobody actuvely looking into that bug [09:51] <[mbm]> not entirely surprising when hacking the usb controller into undefined modes [09:51] *actively [09:51] <[mbm]> they gave up on the full desktop experience? [09:52] no, but the desktop will be replaced by unity next and mir [09:52] which esssentially is ubuntu touch :) [09:53] <[mbm]> long as there's an x11 compatibility layer I suppose [09:54] there isnt atm [09:54] ogra_: just to understand right -> what i want to do is connect a serial port (to write to, via /dev/ttyUSB[n]) while charging. and this is not supported and never will be? [09:54] there will be once the desktop gets replaced [09:54] rnix, right [09:54] i wouldnbt say "never" but it isnt any priority (not even low) [09:55] <[mbm]> rnix: officially, when your device is controlling a perhiperal (like your serial dongle) it's in usb host mode and is supplying +5v out of the usb port [09:55] ubuntu touch uses adb all over the place so even serial support is questionable [09:55] <[mbm]> rnix: to do charging you have to hack the usb driver not to switch on the 5v output and instead take 5v as a charge input [09:56] ogra_: well, it already works if i connect my serial adapter to the otg cable [09:56] but without charging [09:56] yes it works in this image ... [09:56] it wont/doesnt work in ubuntu touch [09:57] since the gadget is claimed by adb so you cant load the serial gadget driver in parallel [09:57] ok, and ubuntu touch will replace the patced 13.04 image for n7 in future? [09:57] <[mbm]> (hacking the usb driver, as described above makes it prone to crashing) [09:58] rnix, most likely ... it isnt decided yet [09:58] we need *one* classic desktop image to test apps on until the desktop did get replaced [09:58] its not clear if that will just be the pandaboard image or probably the nexus7 one [09:59] but given that we dont want to maintain two n7 kernels and given that they need to differ between the two images its likely to go away if it turns out we cant use the same kernel on both images [10:06] finally all i can do is either use a bluetooth or wireless bright to my bus or hack the hardware with an external power supply instead of battery. latter one makes the ose of a tablet obsolete... [10:06] s/bright/bridge [10:07] you could use your own patched kernel (and fix the issue alongside) [10:07] hi all. Login takes time as wifi interface is not up correctly. It is defined as dhcp, but I have an ipression that udhcpc is not started. How to verify this? [10:13] hi all. Login takes time as wifi interface is not up correctly. It is defined as dhcp, but I have an ipression that udhcpc is not started. How to verify this? [10:15] !ask [10:15] Please don't ask to ask a question, simply ask the question (all on ONE line and in the channel, so that others can read and follow it easily). If anyone knows the answer they will most likely reply. :-) See also !patience [10:15] !patience [10:15] Don't feel ignored and repeat your question quickly; if nobody knows your answer, nobody will answer you. While you wait, try searching https://help.ubuntu.com/ or http://ubuntuforums.org/ or http://askubuntu.com/ [10:19] ..oO( same in every tech channel ;) ).. [10:19] actually, look at the list of open bugs instead [10:20] same with every oss project ;) [11:16] would it be possible to load via docking station while using micro usb to write? [11:16] * ogra_ has never seen an n7 docking station ... [11:16] i would assume not though ... it will likely claim the usb port for charging [11:17] http://www.blogcdn.com/www.engadget.com/media/2013/01/nexus-7-dock.jpg [11:18] well, that's what i fear as well - xor usage [11:19] it wont change the kernel or driver ... so it will likely do the same ... === hggdh_ is now known as hggdh === chihchun is now known as zz_chihchun === NekoXP is now known as Neko === hggdh_ is now known as hggdh === XorA is now known as XorA|gone === zz_chihchun is now known as chihchun