IRC log of #cubox of Tue 21 Oct 2014. All times are in CEST < Back to index

00:48 quitte Hi again. Where can I supply the hummingboard with 5V?
00:49 Exaga 5v 2AMP
00:50 quitte Exaga: I meant at which solder pads
00:50 Exaga you mean the GPIO?
00:51 quitte No. I will not run it at anywhere near full clock for a long time. so powering it from the jtag adapter would be convenient. So I'd like to know at which pads I can attach the 5V line from the jtag adapter
00:52 Exaga that i do not know... sorry :>
11:40 kbouhara Hello, did anyone here already had test mxc adv7180 ?
12:14 rabeeh hi kbouhara
12:14 rabeeh how do you use this decoder?
12:14 rabeeh how is it connected?
13:44 kbouhara rabeeh: I use it with 8 data bits in cvbs mode
13:45 kbouhara rabeeh: I can't figure out how to get the MXC_CAPTURE option activate on branch linux-linaro-lsk-v3.14-mx6 ?
13:45 rabeeh do you use HummingBoard for that?
13:46 rabeeh which board are using?
13:46 kbouhara rabeeh: no, actually it's for a custom board based on imx6 soc too
13:46 kbouhara rabeeh: I wanted to use latest backports from your kernel tree
13:46 rabeeh SolidRun imx6 microsom based
13:48 kbouhara rabeeh: I use imx_v7_defconfig as base configuration but I can't find MXC ADV7180 option in menuconfig ?
13:48 rabeeh i think that the MXC capture patchset is not merged yet
13:48 rabeeh thats why you are not seeing them on LK 3.14.x tree
13:49 jnettlet it needs to be reworked for 3.14 compatibility
13:52 kbouhara jnettlet: ok so still in progress, is there a patchset that I can test right now?
13:53 jnettlet kbouhara, nothing to release yet.
14:02 kbouhara jnettlet: what about lk 3.10 ?
14:04 jnettlet kbouhara, the patchset is there in 3.10.30, but I have not tested it.
14:05 kbouhara jnettlet: thanks
15:20 Exaga Artox: o/
15:32 Artox \o Exaga
15:32 Artox hows the slackware going?
15:34 matoking I've tried three different type B microUSB cables for the serial console. One of them doesn't fit in at all and the rest don't work
15:36 matoking Some technical detail I need to worry about to make the cable work?
15:36 matoking I've tried checking for new ttyUSB entries with dmesg | grep ttyUSB but nothing has appeared
16:25 matoking When I plug in the microUSB -> USB cable I get a bunch of "[ 3143.241728] usb 3-12: new full-speed USB device number XX using xhci_hcd" messages with different numbers followed by "[ 3145.210619] hub 3-0:1.0: unable to enumerate USB device on port 12"
16:28 matoking Do you suppose it could have something to do with the cable not being plugged in all the way
16:28 jnettlet matoking, xhci_hcd is the USB 3.0 driver. It shouldn't be using that.
16:29 jnettlet ehci,uhci, or ohci should work
16:30 matoking jnettlet: Yeah, I just feel that the cable isn't plugged in all the way through what with the microUSB port being inside this narrow gap
16:31 matoking Well, all the contacts seem to be lining up and look like they would connect
16:31 matoking Unless there are some in the back
16:33 matoking Both of the cables I've tried were bundled with smartphones
16:35 matoking Oh, and I don't have a power cable or anything plugged in the Cubox-i except for the microUSB cable, which should be all that's needed for the /dev/ttyUSB0 device to appear
16:36 jnettlet correct
16:37 jnettlet matoking, well you need to be careful. Some of the usb cables that come with smartphones are charging only cables
16:38 matoking jnettlet: Both of them are also data cables
16:38 matoking Or would it be a problem if I happened to plug a charging cable in
16:55 matoking I've gone through the 12 or so USB ports I have on this system and all of them end up loading xhci_hcd
16:55 matoking That said, at least two of them should be USB 2.0 ports so I don't know why it's doing that
16:56 jnettlet matoking, I would try blacklisting the xhci_hcd module and letting ehci_hcd take over those ports. See if you have any better success
16:57 matoking jnettlet: Yeah, there's also a chance I could disable in the BIOS
16:57 matoking From what I've heard the USB 3.0 support in the kernel isn't that stable yet
16:57 matoking Or at least 100% working in all cases
16:59 matoking Well, xhci_hcd module is blacklisted
16:59 matoking Hope nothing goes wrong on reboot :P
17:02 matoking Blacklisted xhci_hcd on /etc/modprobe.d, it still used xhci_hcd for every USB device
17:02 matoking Time to try my luck with BIOS settings
17:06 matoking Disabled xHCI in the BIOS, USB devices are now loaded using ehci-pci but I still can't get the serial console to work
17:07 matoking Same sequence of errors but with xhci_hcd replaced with ehci-pci
17:18 matoking Oh, I'm also getting "[ 829.220380] usb 2-1.5.4: device descriptor read/64, error -32" messages
17:19 matoking I had filtered messages to those with USB on it so I didn't catch that at first
17:52 quitte Hi. I'd still like to power my hummingboard via the jtag adapter. could someone point me at suitable solder points?
17:53 quitte D6 and the usb ports GND shield?
20:32 matoking Do you guys think I should reinstall my Cubox-i with a distro which already has systemd installed? I accidentally installed systemd due to it being a dependency of network-manager, which ended up preventing my Linux installation from booting up.
20:32 Fluttershy0 matoking, I'd say setting up systemd yourself is nott fun
20:33 Fluttershy0 so, yeah
20:33 matoking Yeah
20:33 Humpelstilzchen ..just stay on sysvinit...
20:33 matoking It's not very fun to have your Linux installation become broken after you have spent hours getting it into a working shape :P
20:33 matoking just because some package manager had added systemd as a dependency
20:34 matoking Well, I'll just have to prevent systemd from being installed somehow
20:35 Humpelstilzchen you can do that with apt_preferences
20:35 Humpelstilzchen if debian
20:59 matoking Well, if anyone has a good starting point for a distro sans the kernel, I would appreciate a link, seeing as I'll probably have to reinstall everything again anyway :)