**** BEGIN LOGGING AT Mon Sep 14 02:59:57 2020 **** BEGIN LOGGING AT Mon Sep 14 03:09:52 2020 **** BEGIN LOGGING AT Mon Sep 14 05:36:02 2020 **** BEGIN LOGGING AT Mon Sep 14 05:38:52 2020 **** BEGIN LOGGING AT Mon Sep 14 09:54:18 2020 **** BEGIN LOGGING AT Mon Sep 14 09:59:59 2020 Sep 14 11:44:26 hi people Sep 14 11:44:43 how can i get a spi port working on beagleboard-x15 Sep 14 11:45:07 i know its something with dts but dont know more Sep 14 11:45:55 give me an example or a working dts file Sep 14 11:46:01 will be gratefull Sep 14 11:46:02 thanks Sep 14 11:52:05 mount, i guess then u have to read up about dts and pinmuxing in general Sep 14 12:05:25 rob_w it seems too complex for me Sep 14 12:05:47 i know about pinmuxing but dont know dts **** BEGIN LOGGING AT Mon Sep 14 12:51:41 2020 **** BEGIN LOGGING AT Mon Sep 14 13:05:47 2020 Sep 14 15:24:48 What does the stereotypical communication between sitara and tps65217 look like on a beagle, is it a set-and-forget type of comm(minus any powerscaling on processor speed change)? Sep 14 15:25:36 and irq handling (e.g. for the power button) Sep 14 15:26:38 So there is no polling communication? and for the power button, it's a pass through connection, so it appears as a typical gpio to the sitara right? Sep 14 15:29:31 there's no polling since there's an interrupt line Sep 14 15:29:51 and the driver doesn't expose the power button as gpio, it generates a key event instead Sep 14 15:32:06 it does that by handling the interrupt to generate key event? Sep 14 15:33:10 Alright, sweet, Thank you, and damn, that was a quick response, 48 seconds, wow. Sep 14 15:33:13 hahah Sep 14 15:33:24 oops, pre-typed that. Sep 14 15:48:59 drivers/mfd/tps65217.c registers as an interrupt controller that demultiplexes the various irqs, and drivers/input/misc/tps65218-pwrbutton.c turns it into a key event **** BEGIN LOGGING AT Mon Sep 14 16:56:54 2020 **** BEGIN LOGGING AT Mon Sep 14 17:45:38 2020 **** BEGIN LOGGING AT Mon Sep 14 20:30:32 2020 **** BEGIN LOGGING AT Mon Sep 14 20:57:22 2020 **** BEGIN LOGGING AT Mon Sep 14 23:12:46 2020 Sep 15 00:14:03 does anyone know what all is required to be able to get bluetooth audio from beaglebone blue? i am on dev console version of debian and when i do "sudo apt-get install -y bluetooth pulseaudio pulseaudio-module-bluetooth alsa-utils" it wants to install a bunch of gui stuff Sep 15 00:14:25 i am following this https://github.com/imfatant/test#extras Sep 15 00:14:32 https://pastebin.com/9dU06uAg Sep 15 00:14:35 or am i wrong Sep 15 00:14:56 that pastebin link doesn't work Sep 15 00:15:02 i dont want a bunch of extra stuffs Sep 15 00:15:07 oh bummer Sep 15 00:15:12 expired? Sep 15 00:16:02 define "bunch of gui stuff" Sep 15 00:16:33 i will get it booted and re paste Sep 15 00:17:14 pulseaudio has dependencies on a few low-level x11 libraries but other than that I don't think it should have any dependency on "gui stuff" Sep 15 00:19:52 https://pastebin.com/Qrj4JCf3 Sep 15 00:20:12 that does seem silly Sep 15 00:20:22 maybe some bullshit is being pulled in via "recommends" Sep 15 00:22:03 try passing -o Apt::Install-Recommends=false to apt Sep 15 00:24:10 also, hmm... avahi-daemon isn't installed by default on the console image? I thought it was Sep 15 00:24:40 https://pastebin.com/w9jwk9Ke Sep 15 00:24:54 a little better but not much Sep 15 00:25:23 i have no idea about the avahi-daemon Sep 15 00:29:30 it does seem pulseaudio itself pulls in a lot of dependencies Sep 15 00:30:02 the alternative seems to be https://github.com/Arkq/bluez-alsa Sep 15 00:32:19 (or compile pulseaudio with fewer of its optional dependencies enabled) Sep 15 00:33:15 it seems that pulseaudio itself actually doesn't *require* much at all: http://www.linuxfromscratch.org/blfs/view/svn/multimedia/pulseaudio.html Sep 15 00:33:29 but of course the debian package has everything and the kitchen sink enabled Sep 15 00:33:59 hmmm **** BEGIN LOGGING AT Tue Sep 15 01:43:13 2020 **** BEGIN LOGGING AT Tue Sep 15 02:01:12 2020 **** ENDING LOGGING AT Tue Sep 15 02:59:57 2020