00:00 <set_> But...

00:00 <set_> I like to try to keep up w/ old traditional ways and new, "fascinating" trends that may in turn circumvent itself.

00:00 <set_> Cyclic! Like loops.

00:01 <zmatt> ???

00:01 <set_> I want to stick around and with the least friction possible.

00:01 <zmatt> set_: you keep doing weird shit, and then end up complaining/asking here because unsurprisingly stuff isn't working because you keep doing weird shit

00:01 <set_> So, if beagleboard.org does not want to have me boasting and bragging about random findings. This is okay.

00:01 <zmatt> and in doing so, waste other people's time

00:02 <set_> It is not so weird to try new ventures so I am told.

00:02 <zmatt> why does your even readme mention gpiod? your code doesn't actually use it (obviously, since it doesn't work)

00:03 <set_> Oh.

00:03 <set_> Is it broken already?

00:03 <set_> Dang it.

00:03 <zmatt> it's incompatible with declaring gpios in DT

00:03 <set_> I am seeing the LED light up and the BBBW and RelayCape work in tandem.

00:04 <set_> On/Off.

00:04 <set_> Until I quit the program.

00:04 <set_> Were you sent by NY city to make me quit?

00:04 <set_> The entire city wants set_ to quit. I knew it.

00:05 <set_> Everyone, everywhere. This is not fair. If I need to dumb things down to not tarheel people, so be it.

00:05 <set_> I can slow things into a fashion.

00:06 <zmatt> actually, I misspoke... gpiod *shouldn't* work, but rcn hacked the kernel to make gpiod ignore the fact that the gpio is already in use, which means that using gpiod will end up stealing the gpio from the sysfs interface

00:08 <zmatt> (and upon release also leaves the gpio in high-impedance mode even if DT configured it to be output-only)

00:08 <zmatt> gpiod just sucks, it's worse than sysfs-gpio in almost every way possible

00:09 <set_> Oh.

00:10 <set_> I knew you knew of ideas relating to GPIO more than I.

00:10 <set_> I am not discussing your knowledge of embedded systems and the am335x over my knowledge here.

00:12 <set_> I just like trying "weird shit" here and trying to better my knowledge surrounding embedded systems in general. I picked you guys and gals b/c of the TI relationship.

00:12 <set_> I always wanted to learn more.

00:12 <set_> People are in my way. I have to break. brb!

00:13 <set_> I will research the difficulties of high-impedance since my notes due to the blog are dead.

00:15 <set_> Gone pecan!

00:19 <set_> I made a long post about impedance and MOSFETs but it got shafted and beat. I had to erase everything over anger towards the blogger site. They should allow for specific math entries to be made willy-nilly.

00:22 <set_> Good != anger && blogging != math entries < peace of mind

00:22 <set_> But...the show must go on.

00:22 <set_> @zmatt: Why are you scolding me over this libgpiod and sysfs stuff? Did I make an error?

00:27 <set_> Did I try something confounded?

01:40 <set_> @zmatt: Are we done w/ this altercation or do I have to dread doing "well?"

01:42 <set_> I can make things more complicated if necessary and do other things to avoid pitfalls in Eye Sight.

01:43 <set_> Like, for instance, I can run things by you so you can say nay. Understudy type hoopla. And then, I will just give!

01:43 <set_> The pathlib thing was a bit silly. Okay.

01:44 <set_> I can update things with tons of ideas and add other, harder-to-decipher source if necessary.

01:44 <set_> I am sorry! Sheesh.

01:44 <set_> I got excited.

01:44 <set_> It blew me away.

01:46 <set_> The idea that I, set_, could finally fix things where things would work "blew me away."

01:47 <set_> I was overwhelmed and exacerbating things by vidily giving away simple source to run am335x w/ RelayCape and dually noted, w/out a guiding hand or overseer.

01:47 <set_> There.

01:48 <set_> Orders, orders. I know what is right. Orders, orders.

01:49 <set_> Fine.

01:49 <set_> i will try something out-of-the-ordinary and see how far things go w/ a working system.

01:53 <set_> I am cowering here and trying to be kind to get viewpoints on my actions. So?

02:00 <set_> Forget it. Blah.

02:16 <set_> Okay. WIP on the pathlib source. enjoy.

02:16 <set_> anything else?

02:53 <set_> Okay, I understand now. Please forgive me.

03:00 <set_> 10:00, no more fun and games. Okay.

10:18 <zmatt> set_: using pathlib is fine... it's the only part of your python script that makes any sense whatsoever

12:18 <Keeni> Hey guys. I have a question related to shared memory in PRU. Assume that I have a register 3 (R3) with this address 0x000007ff - 4 byte in share memory. How can I read the value in this register in a Linux environment?

14:25 <Keeni> (y) (y) (y)

14:31 <set_> @zmatt: Sorry about yesterday. I was a bit perturbed by the rant about libgpiod and okay about pathlib file. I changed it a bunch so far b/c I figured it was too easy to decipher what actually was going on in it. It is broken now and a WIP.

16:33 <jfsimon1981_b> Hi, I don't remind how we read analog device on the beagle black, can one please help ?

16:33 <jfsimon1981_b> i have 2 channels to read adc 0 and 2

16:34 <jfsimon1981_b> there's a device iio:device0 related to adc, that's about all i found back at the moment

16:46 <jfsimon1981_b> It seems i got it back:

16:46 <jfsimon1981_b> echo 1 > /sys/bus/iio/devices/iio:device0/scan_elements/in_voltage0_en

16:46 <jfsimon1981_b> echo 1 > /sys/bus/iio/devices/iio:device0/scan_elements/in_voltage2_en

16:46 <jfsimon1981_b> echo 1 > /sys/bus/iio/devices/iio:device0/buffer/enable

16:46 <jfsimon1981_b> Finally read from /dev/iio:device0 [uint16]

17:35 <Keeni> bye chat!!@.@