ChanServ changed the topic of #linux-sunxi to: Allwinner/sunxi development - Did you try looking at our wiki? https://linux-sunxi.org - Don't ask to ask. Just ask and wait for an answer! - This channel is logged at https://oftc.irclog.whitequark.org/linux-sunxi
<MoeIcenowy> wens: I am using Zoho mail
<MoeIcenowy> and strangely when I send patch with git-send-email it easily get bounced
<MoeIcenowy> (when replying with Evolution it's okay
<MoeIcenowy> when using a 3rd party mail provider, is configuring reverse DNS necessary?
cakes has quit [Ping timeout: 480 seconds]
<gamiee> MoeIcenowy afaik it is not.
<gamiee> Send testing email with git-send-email to https://www.mail-tester.com/ . It will show you the problems and solutions
JohnDoe_71Rus has joined #linux-sunxi
koty0f has quit [Ping timeout: 480 seconds]
koty0f has joined #linux-sunxi
koty0f has quit [Read error: Connection reset by peer]
koty0f has joined #linux-sunxi
koty0f has quit [Ping timeout: 480 seconds]
koty0f has joined #linux-sunxi
apritzel_ has joined #linux-sunxi
koty0f has quit [Read error: Connection reset by peer]
koty0f has joined #linux-sunxi
private_sub2 has joined #linux-sunxi
private_sub2 has quit []
apritzel_ has quit [Ping timeout: 480 seconds]
koty0f has quit [Ping timeout: 480 seconds]
koty0f has joined #linux-sunxi
koty0f has quit [Read error: Connection reset by peer]
koty0f has joined #linux-sunxi
koty0f has quit [Read error: Connection reset by peer]
koty0f has joined #linux-sunxi
<wens> are you using your email host's SMTP service with git-send-email? or are you sending directly from your computer?
<wens> looks to be through Zoho's smtp
apritzel_ has joined #linux-sunxi
apritzel_ has quit [Ping timeout: 480 seconds]
apritzel_ has joined #linux-sunxi
koty0f has quit [Ping timeout: 480 seconds]
koty0f has joined #linux-sunxi
koty0f has quit [Read error: Connection reset by peer]
koty0f has joined #linux-sunxi
koty0f has quit [Read error: No route to host]
koty0f has joined #linux-sunxi
apritzel has joined #linux-sunxi
koty0f has quit [Read error: Connection reset by peer]
koty0f has joined #linux-sunxi
koty0f has quit [Ping timeout: 480 seconds]
koty0f has joined #linux-sunxi
koty0f has quit [Read error: Connection reset by peer]
koty0f has joined #linux-sunxi
koty0f has quit [Read error: Connection reset by peer]
koty0f has joined #linux-sunxi
koty0f has quit [Read error: Connection reset by peer]
koty0f has joined #linux-sunxi
JohnDoe_71Rus has quit []
JohnDoe_71Rus has joined #linux-sunxi
<apritzel> smaeul: palmer: What is the story about those watchdog(s) in the D1 devicetree having: status = "reserved"; ? Is that because for the RISC-V variants we should use the RISC-V watchdog instead?
<palmer> I don't know, sorry.
<palmer> I only really know the core stuff, once it gets to SOC it's tooucj to keep track of
digetx has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
digetx has joined #linux-sunxi
<palmer> I guess just LMK if you want me to look at anything, but I'd need some more context...
<apritzel> palmer: thanks, that's fine. I guess it's really to prevent the other watchdogs from being picked up, when there is a separate watchdog for the RISC-V variants.
<palmer> apritzel: I wouldn't be surprised if there's something like that going on. IIUC some of the IPs in the D1 are RISC-V-only (and some are Arm-only)
<palmer> IDK the watchdogs, though
<palmer> I think some people around here have D1s for experiements, if you've got some patch you want tested I'm happy to go poke folks
koty0f has quit [Read error: Connection reset by peer]
koty0f has joined #linux-sunxi
koty0f has quit [Read error: Connection reset by peer]
koty0f has joined #linux-sunxi
<apritzel> the patch would be just: &wdt { status = "okay"; }; in sun8i-t113s.dtsi, so that wouldn't affect D1 users at all
<apritzel> palmer: there is already a usable watchdog (riscv_wdt) added in sun20i-d1s.dtsi, but none of the nodes having a "allwinner,sun20i-d1-wdt" compatible string is enabled on the Arm side of the DT
<apritzel> palmer: don't worries, I will just wait for some explanation here, then send a patch
koty0f has quit [Ping timeout: 480 seconds]
koty0f has joined #linux-sunxi
<palmer> apritzel: ya, nothing's really jumping out as to why -- probably best to just send the patch, this is well outside of things I know about the D1 ;)
<palmer> I'm going to stop going down the rabbit hole, though ;)
<gamiee> bit offtopic: does V4L2 have request api for h.264 encoder?
apritzel has quit [Ping timeout: 480 seconds]
vagrantc has joined #linux-sunxi
<smaeul> aperezdc: the purpose was so the DSP could use its own watchdog (when it exists), and to reserve the special allwinner,sun20i-d1-wdt-reset instance for privileged firmware
<smaeul> er, apritzel:
<smaeul> my "ideal" solution would be to use the allwinner,sun20i-d1-wdt-reset in the PSCI implementation, and use the PSCI sysreset driver in U-Boot
<smaeul> unfortunately, U-Boot currently waits to jump from secure svc to hyp until bootm time, so PSCI can't be used from U-Boot itself
<smaeul> so the short-term solution is to add `&wdt { status = "okay"; };` to a -u-boot.dtsi file
apritzel_ has quit [Ping timeout: 480 seconds]
Guest3147 has quit [Remote host closed the connection]
Daanct12 has joined #linux-sunxi
koty0f has quit [Read error: Connection reset by peer]
koty0f has joined #linux-sunxi
koty0f has quit [Ping timeout: 480 seconds]
koty0f has joined #linux-sunxi
koty0f has quit [Read error: Connection reset by peer]
koty0f has joined #linux-sunxi
koty0f has quit [Read error: Connection reset by peer]
koty0f has joined #linux-sunxi
JohnDoe_71Rus has quit []
apritzel_ has joined #linux-sunxi
koty0f has quit [Ping timeout: 480 seconds]
koty0f has joined #linux-sunxi
ftg has joined #linux-sunxi
apritzel_ has quit [Ping timeout: 480 seconds]
koty0f has quit [Remote host closed the connection]
koty0f has joined #linux-sunxi
koty0f has quit [Read error: Connection reset by peer]
koty0f has joined #linux-sunxi
koty0f has quit [Ping timeout: 480 seconds]
koty0f has joined #linux-sunxi
koty0f has quit [Read error: Connection reset by peer]
koty0f has joined #linux-sunxi
koty0f has quit [Read error: Connection reset by peer]
koty0f has joined #linux-sunxi
apritzel_ has joined #linux-sunxi
apritzel_ has left #linux-sunxi [#linux-sunxi]
apritzel has joined #linux-sunxi
koty0f has quit [Ping timeout: 480 seconds]
koty0f has joined #linux-sunxi
koty0f has quit [Ping timeout: 480 seconds]
koty0f has joined #linux-sunxi
koty0f has quit [Remote host closed the connection]
koty0f has joined #linux-sunxi
koty0f has quit [Read error: Connection reset by peer]
koty0f has joined #linux-sunxi
<apritzel> smaeul: thanks for the explanation, I will have a think
<apritzel> not sure if the wdt needs to be exclusive to firmware, if it's all about reset, and firmware already owns the system on PSCI_SYSTEM_RESET again
<apritzel> if firmware really needs to own it exclusively, it could actually change "okay" to "reserved", on the fly
apritzel has quit [Ping timeout: 480 seconds]
ftg has quit [Read error: Connection reset by peer]