**** BEGIN LOGGING AT Thu Feb 02 03:00:02 2017 Feb 02 06:12:30 hi all Feb 02 08:55:56 apt-cache show bb-wl18xx-firmware Feb 02 08:56:03 Depends: bc, bsdmainutils, connman, coreutils, dnsmasq Feb 02 08:56:05 wtf? Feb 02 08:56:30 Why does a firmware package depend on connman? Feb 02 09:04:56 good question Feb 02 09:05:13 what's in that package anyway? (dpkg -L bb-wl18xx-firmware) Feb 02 09:06:04 It has firmware and also some systemd service files for wlan0 and bluetooth. Feb 02 09:07:33 a bit sloppy to combine those in one package yeah Feb 02 09:08:15 The systemd services seem to handle setting mac address for wlan and run hciattach so that bluetooth can work. Feb 02 09:10:33 Now I see. The firmware package also contains a tether script that needs connman. Feb 02 09:10:57 that sounds weird Feb 02 09:11:16 I mean, tethering is a primary feature of connman Feb 02 09:12:02 i.e. it shouldn't require a script to tether Feb 02 09:12:45 I think the package should be split to a firmware package and a tether package. Feb 02 09:20:08 l Feb 02 10:30:18 hi all Feb 02 10:32:04 hoi lore4 Feb 02 10:39:33 hi KotH ;) Feb 02 12:05:50 Hello guys, Have a problem installing BONE_D64 driver on my Win10 Feb 02 12:06:36 Also cannot open "http://192.168.7.2/" Feb 02 12:08:14 Any idea anyone ? Feb 02 12:12:02 "does not work" is not a problem description ;) Feb 02 12:13:12 Ah thats the point ;) so now i have your attention. so "doesnt work" = "windows doesnt instal rndis driver" Feb 02 12:13:32 uh... Feb 02 12:13:35 err... Feb 02 12:13:39 i havent used windows in years Feb 02 12:14:10 much less installed non-standard drivers Feb 02 12:14:48 ask tbr, he is ex-damager, he knows windows like his pocket Feb 02 12:14:55 he can even use word! Feb 02 12:18:54 hi all! is there anyone experienced with OpenGL drivers on bbb and Yocto (or any linux flavour in general)? i want to compile qt5.8 for bbb having hardware graphics acceleration but probably i miss video drivers Feb 02 12:23:48 rrrrright Feb 02 12:24:11 too bad I never used the windows drivers for BBB Feb 02 12:24:34 there are instructions on beagleboard.org and if that doesn't work there is the google group Feb 02 12:25:31 err.. windows drivers? Feb 02 12:25:56 Talorno: you just stumbled into an ongoing discussion Feb 02 12:26:06 KotH, ah :D Feb 02 12:26:08 tbr: son, i'm dissapoint Feb 02 12:26:14 tbr: i expected more from you Feb 02 12:31:15 KotH: proud not to do damagement nowadays ;-) Feb 02 12:33:36 Talorno: I'd send a manual to the buildroot community Feb 02 12:34:04 Talorno: I mean an e-mail. I need a lunch brak Feb 02 12:34:52 yegorich, first i have to discover what buildroot is :D Feb 02 12:38:16 yegorich, got what buildroot is. Yocto vs buildroot? any experience? Feb 02 12:42:09 buildroot is easier to grasp if you are new, YÖP is more enterprisey Feb 02 12:48:49 Talorno: I've gotten the old (1.10) drivers to work when I looked into it a while back, I recently tried getting the new drivers (1.14) to work and sorta succeeded but hit some bumps in the road... haven't had much time to look at it Feb 02 12:48:55 in both cases on debian Feb 02 12:49:09 well i actually develop my stuff using Yocto but personally i feel like sometimes is too fat or complicated. Should i evaluate moving to buildroot? Feb 02 12:49:33 zmatt, any working tutorial/guide to point me at? Feb 02 12:50:51 I have no experience with yocto or buildroot, and I compiled the drivers using a script made by rcn-ee Feb 02 12:51:33 (included in his kernel build script trees) Feb 02 13:00:18 ad-hoc wifi is never going to be supported: https://e2e.ti.com/support/wireless_connectivity/wilink_wifi_bluetooth/f/307/t/367550 Feb 02 13:00:33 But should I be able to get "mesh point" mode to work somehow? Feb 02 13:01:39 mesh point is listed in supported tx and rx frame types but not in supported interface modes. Feb 02 13:01:49 I mean: iw list Feb 02 14:16:53 inch: take a look at this thread: https://www.spinics.net/lists/hostap/msg02580.html Feb 02 14:17:35 inch: mesh was working with the latest fw and vanilla kernel, but without encryption Feb 02 14:19:24 inch: encryption was working only with TI's kernel 4.4 or 4.1. I don't remember exaclty Feb 02 14:20:32 Thanks. Feb 02 14:21:35 inch: do you need encryption for your project? Feb 02 14:22:10 I don't know yet. I was just asked to get a mesh running at this point. Feb 02 14:24:42 inch: OK :-) Feb 02 14:25:26 In this case I don't think I need secure communication between mesh memebers, but secure communication between mesh members and a server outside the mesh. That could be handled with a vpn or perhaps even with https. Feb 02 16:29:49 bb Feb 02 16:32:43 hey, what's the latest image that got PRU support ? Feb 02 16:33:12 Last time I had my hands on, I worked on 3.15 Feb 02 16:43:38 Need help with the push button interrupt on the BeagleBone Black. /HELP Feb 02 16:50:36 I tried this approach with the glib2( https://www.linux.com/learn/beaglebone-black-how-get-interrupts-through-linux-gpio ) but dint work Feb 02 17:05:37 kkk0306: you used a polling approach, that can be good if you know the gpio the button is using Feb 02 17:09:12 Catslab: i know which button i'm going to be using. Unfortunately that code is not working. While debugging i noticed this in the Console "Program received signal SIGINT, Interrupt. 0xb6e419b4 in poll () from target:/lib/arm-linux-gnueabihf/libc.so.6" Feb 02 17:10:26 While the program does not get terminated, it just hangs up completely. Feb 02 17:12:06 you can get gpio interrupts in two ways Feb 02 17:13:42 you can do it using the usual sysfs gpio interface by setting the 'edge' attribute of the gpio to something other than 'none', Feb 02 17:14:27 then if you open the 'value' attribute it will receive sysfs notifications whenever the configured edge is detected Feb 02 17:15:52 Oh. Thanks! I will try that. Feb 02 17:15:53 how sysfs notifications work is a bit unusual (like everything in sysfs really), since it generates the poll flags POLLPRI | POLLERR Feb 02 17:16:54 the POLLERR doesn't indicate an error here, it's just used to allow people to use select() if they really want to (POLLERR maps to the exceptfds) Feb 02 17:17:07 I never tried sysfs Feb 02 17:17:33 what are you then using for gpios? Feb 02 17:17:43 Prus .... Feb 02 17:17:44 lol Feb 02 17:17:57 that works too :) Feb 02 17:18:14 I had something working on 3.15 but I need to dust things out Feb 02 17:18:35 so I'm back on it after over a year and I'll try 4.4 Feb 02 17:18:46 the sysfs interface has the benefit that you get one directory per exported pin, so you can easily symlink to it and configure permissions Feb 02 17:18:57 yep Feb 02 17:19:38 but I nver went that way because I need precise timing to read ADCs Feb 02 17:20:06 I saw a cape lately, I must check that Feb 02 17:20:08 yeah this is not for speed-critical stuff Feb 02 17:20:27 it's for that big pile labeled "Misc" Feb 02 17:20:28 ;) Feb 02 17:21:15 ahahah Feb 02 17:21:24 got it: prudaq Feb 02 17:21:52 will check what they did Feb 02 17:22:08 I need only 4 channels at 100kSPS Feb 02 17:24:25 with my gpio-sysfs enhancements and a suitable udev rule, I get e.g. this -> http://pastebin.com/raw/iARc2Tsa automatically exported and configured based on declarations in the DT Feb 02 17:24:57 (my patches have been integrated by rcn-ee in the 4.9 kernels, but not backported I think) Feb 02 17:27:29 zmatt: Thank you so much!! That worked!! :) Feb 02 17:28:08 you're welcome :) Feb 02 17:29:21 the other option is uio (specifically uio_pdrv_genirq), which you can use to route interrupts to userspace, both from gpio (edge or level) and from peripherals (level) Feb 02 18:14:07 I'm trying to get analog pins to read on a rev. A5A board with the latest Debian 4.x build. Device mapping isn't available anymore. Could use a link to a solution. Feb 02 18:22:44 "device mapping" ? Feb 02 18:23:58 this woefully incomplete wiki page attempts to document how to get stuff working again on the 4.x kernel Feb 02 18:24:20 including how to enable the ADC Feb 02 18:26:10 So sorry. Device "TREE" overlay Feb 02 18:26:34 Those don't work anymore. So where is the wikipage you mention? Feb 02 18:28:27 oh sorry, forgot to paste the link... http://elinux.org/Beagleboard:BeagleBone_Debian_Image_Migration Feb 02 18:34:59 Thanks! Feb 02 20:02:39 Is "echo BB-ADC > /sys/devices/platform/bone_capemgr/slots" persistent? Meaning, do I need to run that at boot? Feb 02 20:03:04 minnesotags, yes you do Feb 02 20:03:43 Thx Feb 02 20:05:49 My plan is just to "cat in_voltage1_raw" for example to a log file, unless there is a "better" way to do that? Feb 02 20:21:13 there is, but I'm not really familiar with the IIO subsystem and its api Feb 02 20:22:46 but afaik the /dev/iio* devices are the primary interface Feb 02 21:02:44 ssh Feb 02 21:06:53 lol. Sorry **** ENDING LOGGING AT Fri Feb 03 03:00:00 2017