demirok has quit [Quit: Leaving.]
Shadyman has joined #beagle
set_ has joined #beagle
thinkfat_ has quit [Ping timeout: 244 seconds]
thinkfat_ has joined #beagle
akaWolf has quit [Ping timeout: 255 seconds]
johanhenselmans has quit [Ping timeout: 255 seconds]
akaWolf has joined #beagle
johanhenselmans has joined #beagle
insurgent has joined #beagle
vagrantc has quit [Quit: leaving]
demirok has joined #beagle
demirok has quit [Client Quit]
otisolsen70 has joined #beagle
Guest540 has joined #beagle
Guest540 has quit [Client Quit]
ikarso has joined #beagle
nparafe has joined #beagle
javaJake_ has joined #beagle
javaJake has quit [Ping timeout: 240 seconds]
javaJake_ is now known as javaJake
Shadyman has quit [Quit: Leaving.]
Manul has joined #beagle
Manul has quit [Client Quit]
nparafe has quit [Quit: - Chat comfortably. Anywhere.]
nparafe has joined #beagle
indigaz9 has joined #beagle
indigaz has quit [Ping timeout: 240 seconds]
indigaz9 is now known as indigaz
florian has joined #beagle
CygniX has quit [Ping timeout: 255 seconds]
xet7 has joined #beagle
CygniX has joined #beagle
demirok has joined #beagle
starblue has quit [Ping timeout: 248 seconds]
starblue has joined #beagle
mixotricha has joined #beagle
mixotricha has left #beagle [#beagle]
xet7 has quit [Remote host closed the connection]
ikarso has quit [Quit: Connection closed for inactivity]
alan_o has joined #beagle
Guest62 has joined #beagle
Guest62 has quit [Client Quit]
CrazyEddy has quit [Ping timeout: 244 seconds]
CrazyEddy has joined #beagle
calrama has joined #beagle
calrama has quit [Quit: Client closed]
demirok has quit [Quit: Leaving.]
calrama has joined #beagle
<calrama> Hey, so using the device tree to enable a (pwm) timer on the beaglebone ai seems a bust. Using the devicetree suggested by zmatt ( ) just gives me dmesg errors for any timer I try it with ( ).
v0n has joined #beagle
Posterdati has quit [Ping timeout: 255 seconds]
xet7 has joined #beagle
xet7 has quit [Ping timeout: 258 seconds]
Posterdati has joined #beagle
<zmatt> huh, that's weird
<zmatt> based on that kernel log I'm guessing you added declarations for all three?
<zmatt> calrama: lemme take a quick peek at the driver
<calrama> zmatt: yeah, I did that for debugging^^
<calrama> What I'm currently trying is setting the registers manually via /dev/mem
<zmatt> and you were using 4.14-ti kernel series right?
<calrama> Correct.
<zmatt> please don't
<calrama> Yeah, it doesn't work, either.
<zmatt> like, if you want to go the manual register setting route, use uio instead of /dev/mem
<calrama> I can select the clock.
<zmatt> don't try to mess with PRCM (power/reset/clock management) behind the kernel's back
<calrama> But when I try configuring the timer itself, the kernel throws `Data Access in User mode during Functional access` errors.
<calrama> I just tried the /dev/mem route since I found an old example for beaglebone black and tried adjusting that.
<calrama> I don't really want to use it, either.
<zmatt> yeah, because the module is disabled. uio allows a module's registers to be exported to userspace with the kernel's knowledge, so it'll keep the module enabled while the device is open
<zmatt> but yeah it shouldn't be needed for this obviously
<calrama> If you want, I can give you ssh access to the device^^
<zmatt> I don't think that's useful right now... I first want to check the pwm driver ... if git ever finishes checking out this branch
<calrama> No worries, I'm grateful for any help.
florian has quit [Quit: Ex-Chat]
<calrama> I found this old kernel patch:
<zmatt> oh that may very well be it
<calrama> But if that's the issue, that means I'd have to backport that patch to 4.14 and compile the kernel myself...
<zmatt> or ask rcn to include it
xet7 has joined #beagle
<zmatt> building customized kernel packages (with custom patches and/or config) is relatively easy thanks to rcn-ee's build scripts though
<calrama> How would one contact him preferably? With my previous issue I tried GH ( ) but there has been no reply so far.
<calrama> Could you point me to those build scripts?
<zmatt> well, the problem there is also with the issue itself... like, obviously it's desirable to get TIDL to work on a newer kernel, and if it were easily done then the TIDL images would already *have* a newer kernel ;)
<zmatt> my notes on building a custom kernel: (in your case you'd want the ti-linux-4.14.y branch of the ti-linux-kernel-dev repo)
<calrama> Well, there was no official word on if it's even still being worked on or not, hence the issue. If I got a reply like "nope, we don't have time to ever realistically suport that" I'd be fine at least knowing that^^
<calrama> Thanks for the notes
<zmatt> rcn-ee: can you backport this patch to the 4.14-ti series to un-bork the dmtimer pwm driver?
<zmatt> it cherry-picks cleanly
<calrama> I'm setting up a cross tool rn to try building and see if it fixes the issue.
<zmatt> calrama: no need, the build script downloads a toolchain
<calrama> Ah, ok
<zmatt> if you're missing any packages it needs installed, it'll tell you
<calrama> Let's see, I'm on Funtoo Linux, so that'll be fun ;p
<zmatt> ah okay its powers may not apply to all distros equally ;)
<calrama> yeah no worries, if it crashes with a missing command I'll figure it out.
xet7 has quit [Quit: Leaving]
calrama has quit [Quit: Client closed]
otisolsen70 has quit [Quit: Leaving]
Posterdati has quit [Read error: Connection reset by peer]
Posterdati has joined #beagle
demirok has joined #beagle
buzzmarshall has joined #beagle
zjason has quit [Read error: Connection reset by peer]
zjason has joined #beagle
vagrantc has joined #beagle
Guest14 has joined #beagle
Guest14 has quit [Client Quit]
Shadyman has joined #beagle
nparafe has quit [Quit: - Chat comfortably. Anywhere.]
nparafe has joined #beagle