ArmbianHelper changed the topic of #armbian to: armbian - Linux for ARM development boards | www.armbian.com | Github: github.com/armbian | Commits: #armbian-commits | Developer talk: #armbian-devel | Forum feed: #armbian-rss | Off-Topic: #armbian-offtopic | Logs: -> irc.armbian.com
filt3r has joined #armbian
Herc has joined #armbian
Herc has quit [Remote host closed the connection]
Herc has joined #armbian
archetech has joined #armbian
lord_daemon has quit [Ping timeout: 245 seconds]
DC-IRC has quit [Remote host closed the connection]
DC-IRC has joined #armbian
<DC-IRC>
<forgedcactus> is there a reason that the `dtoverlay` tool seems to be specific only to raspbian? it seems quite good the little I have used it
jclsn has quit [Ping timeout: 260 seconds]
jclsn has joined #armbian
crabbedhaloablut has joined #armbian
<DC-IRC>
<Tonymac32> overlays are not a very standardized thing
<DC-IRC>
<Tonymac32> we handle them in Armbian with the bootloader, so in Armbian-config you can enable/disable them or you can modify the armbianEnv.txt file
<DC-IRC>
<Tonymac32> that said we likely need to change the approach thanks to EFI boards
<DC-IRC>
<forgedcactus> oh how does rpi handle them? I thought it also adds to some boot.txt config file
<DC-IRC>
<Tonymac32> well sure, but dtoverlay is their tool, and how the broadcom magic box actually applies them I have no idea 😉
<DC-IRC>
<Tonymac32> it is in that boot.txt or whatever (reaching back)
<DC-IRC>
<Werner> If the channel name starts with armbian it is relayed. This includes armbian-rockchip or armbian-devel for example.
<DC-IRC>
<Werner> The first-aid channel for example is not relayed and also does not exist on IRC.
buzzmarshall has quit [Quit: Konversation terminated!]
<sinned69150>
ok, i will ask for help there
<DC-IRC>
<sinned6915> oh wow, i see my irc posts here- cool!
<DC-IRC>
<sinned6915> i am stuck trying to roadmap a remote shutdown button and different button to trigger a GPIO controlled relay.
<DC-IRC>
<sinned6915> i use an orangepi 3 with nanoDPL.
<DC-IRC>
<sinned6915> i have a gpio connected opto isolated relay controlling main power to the printer.
<DC-IRC>
<sinned6915> driving the gpio pin high -> mains power on.
<DC-IRC>
<sinned6915> i have a seperate button for long press to shut down the orangepi
<DC-IRC>
<sinned6915> a python script 'watches' that pin
<DC-IRC>
<sinned6915> something i found for similar control with raspi's
<DC-IRC>
<sinned6915> what i want to do is somehow be able to trigger the power relay standing at the machine. i thought about just a SPDT switch to break the circuit from the gpio pin to a 5V line to drive the relay.
<DC-IRC>
<sinned6915> but that seems a bit 'dirty' and could send transient current back to the SBC.
<archetech>
a schottkey diode
<archetech>
in series w/ a hyfuldufenator
<DC-IRC>
<forgedcactus> it also can apply them in real time
<DC-IRC>
<forgedcactus> it also can apply them in run time
<DC-IRC>
<forgedcactus> is that something that can be done generally?
<DC-IRC>
<forgedcactus> presumably not if the bootloader is handling them
<DC-IRC>
<sinned6915> you are saying use the switch with the diode to prevent current backflow towards the pin?
<DC-IRC>
<sinned6915> i am going to have to check uncle jefe's for the hyfuldufenator
<DC-IRC>
<Tonymac32> run-time runs the risk of race conditions with driver loading
<DC-IRC>
<Tonymac32> that's why it's not part of the kernel unless a vendor patches it in
<DC-IRC>
<Tonymac32> in general the kernel doesn't have any "safe" way of doing that from a production point of view. Even when it's available I only do it to make sure the overlay is correct, then configure it for load at boot
<DC-IRC>
<Tonymac32> I had the Tinker board set to allow it long ago but I didn't keep up with it (constant maintenance of a patch set that is sort of orphaned gets tiring)
<DC-IRC>
<forgedcactus> Yes understood, that would be my usecase too
archetech has quit [Quit: Konversation terminated!]
archetech has joined #armbian
<DC-IRC>
<shivasiddharth> Hello
<DC-IRC>
<shivasiddharth> Running nextcloud on a opi0 is actually not that bad as i expected
<DC-IRC>
<shivasiddharth> There is lag buy not as much lag that it's unusable
<DC-IRC>
<shivasiddharth> There is lag but not as much lag that it's unusable
<DC-IRC>
<shivasiddharth> Im running it using the docker image
lord_daemon has joined #armbian
danilogondolfo has joined #armbian
archetech has quit [Quit: Konversation terminated!]
LanDi has joined #armbian
LanDi has quit [Quit: LanDi]
Net147 has quit [Quit: Quit]
Net147 has joined #armbian
lyri has quit [Ping timeout: 255 seconds]
lyri has joined #armbian
Net147 has quit [Quit: Quit]
Net147 has joined #armbian
lyri has quit [Ping timeout: 255 seconds]
lyri has joined #armbian
archetech has joined #armbian
val has quit [Read error: Connection reset by peer]
val has joined #armbian
val has quit [Remote host closed the connection]
val has joined #armbian
val has quit [Remote host closed the connection]
val has joined #armbian
alekksander has joined #armbian
indy has quit [Ping timeout: 255 seconds]
indy has joined #armbian
archetech has quit [Quit: Leaving]
archetech has joined #armbian
buzzmarshall has joined #armbian
Mangix has quit [Ping timeout: 240 seconds]
alekksander has quit [Quit: Konversation terminated!]
alekksander has joined #armbian
Perflosopher has quit [Read error: Connection reset by peer]