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
ftg has quit [Read error: Connection reset by peer]
apritzel has quit [Ping timeout: 480 seconds]
montjoie has joined #linux-sunxi
montjoie_ has quit [Ping timeout: 480 seconds]
flyback has quit []
flyback has joined #linux-sunxi
flyback has quit []
flyback has joined #linux-sunxi
arti has quit [Remote host closed the connection]
arti has joined #linux-sunxi
junari_ has joined #linux-sunxi
junari has quit [Read error: Connection reset by peer]
hexdump0815 has joined #linux-sunxi
hexdump01 has quit [Ping timeout: 480 seconds]
macromorgan__ has joined #linux-sunxi
macromorgan_ has quit [Read error: Connection reset by peer]
warpme has joined #linux-sunxi
colinsane has quit []
colinsane has joined #linux-sunxi
colinsane has quit []
colinsane has joined #linux-sunxi
warpme has quit []
apritzel has joined #linux-sunxi
warpme has joined #linux-sunxi
JohnDoe_71Rus has joined #linux-sunxi
Syter has joined #linux-sunxi
warpme has quit []
dsimic is now known as Guest426
dsimic has joined #linux-sunxi
Guest426 has quit [Ping timeout: 480 seconds]
warpme has joined #linux-sunxi
bauen1 has quit [Ping timeout: 480 seconds]
f_ has quit [Ping timeout: 480 seconds]
f_ has joined #linux-sunxi
tnovotny has joined #linux-sunxi
bauen1 has joined #linux-sunxi
KREYREN_oftc has quit [Remote host closed the connection]
bauen1_ has joined #linux-sunxi
bauen1 has quit [Ping timeout: 480 seconds]
tnovotny has quit [Quit: Leaving]
<machinehum> Just a general "gut feel", would you guys think the D1 might be too slow for a "router type thing"
<machinehum> ?
<jakllsch> depends what sort of performance you want. if you want wire speed gigabit with SQM, it's underpowered
<machinehum> Nah just ... super basic routing
<jakllsch> if you want wirespeed Fast Ethernet w/o SQM, might work Ok
<machinehum> Getting some interesting action: https://pastebin.com/raw/x8sJYmtR
<machinehum> For contect there's a wlan0 and wlan1, wlan1 connected to the internet and wlan0 hosting an AP
<machinehum> context*
<jakllsch> those are PCIe? SDIO?
<machinehum> wlan0 is sdio and wlan1 is usnb
<machinehum> usb*
<machinehum> rtw88_8723du/s
vagrantc has joined #linux-sunxi
warpme has quit []
evgeny_boger has joined #linux-sunxi
warpme has joined #linux-sunxi
junari_ has quit [Ping timeout: 480 seconds]
apritzel has quit [Ping timeout: 480 seconds]
Halamix2 has left #linux-sunxi [Leaving]
warpme has quit []
warpme has joined #linux-sunxi
evgeny_boger has quit [Ping timeout: 480 seconds]
warpme has quit []
JohnDoe_71Rus has quit [Quit: KVIrc 5.2.0 Quasar http://www.kvirc.net/]
bauen1_ has quit [Ping timeout: 480 seconds]
warpme has joined #linux-sunxi
apritzel has joined #linux-sunxi
macromorgan__ has quit []
macromorgan has joined #linux-sunxi
KREYREN_oftc has joined #linux-sunxi
<KREYREN_oftc> what's sun8i_tcon_top ?_
<KREYREN_oftc> like the tcon_top part
ftg has joined #linux-sunxi
bauen1 has joined #linux-sunxi
<Jookia> KREYREN_oftc: _top means LCD i think
<Jookia> or rgb
<KREYREN_oftc> it's not described in the src
<Jookia> ah, that's it
<Jookia> i haven't touched the panel stuff in a while
warpme has quit []
<KREYREN_oftc> apritzel, thanks!
ity has joined #linux-sunxi
<ity> Hello, I am attempting to debug HDMI on an Allwinner A64 (On an OLIMEX TERES-1). What is required to get it working? sun8i_drm_hdmi is loaded, and there are no messages in dmesg, and no output device in /sys/class/drm/
<anarsoul> ity: my guess is display pipeline is not there in dts
<ity> Hmm, I am still new to this whole system, what's DTS?
<KREYREN_oftc> Device Tree ehh standard? the file extension used for DTS
<ity> I am really confused, is the device tree not fetched during boot? Or am I misunderstanding this whole thing
<KREYREN_oftc> the BL31's responsible for identifying the device and then u-boot loads it
<ity> The built-in LCD thing works though, so at least part of the display thing should be functional
KREYREN_oftc has quit [Remote host closed the connection]
KREYREN_oftc has joined #linux-sunxi
<apritzel> ity: it looks like the HDMI output is not described in the devicetree, so the kernel simply doesn't know about that
<apritzel> KREYREN: BL31 doesn't identify anything, the DTB is part of the FIT image (as is BL31), so baked in at build time, and is loaded by the SPL
<apritzel> KREYREN: if you refer to "Found U-Boot DTB at ...", this is just a debug message, BL31 looks for a DTB at the end of the U-Boot image, and uses it for its own purposes
<KREYREN_oftc> oh i see
<apritzel> ity: looks like the pinetab.dts describes both HDMI and a panel, so one could copy from that
<apritzel> KREYREN_oftc: patch opportunity for you!
<KREYREN_oftc> apritzel, mhm!
<KREYREN_oftc> that's why we are looking into it :D
<ity> Ooh, so the issue is in a .dts file somewhere?
<apritzel> ity: yes, in the kernel tree there is the authoritative sun50i-a64-teres-i.dts, which lacks the proper description of the HDMI connector
<ity> Ooooh
<apritzel> so someone needs to look at the pinetab.dts, which describes both, and transplant that to the Teres DT
<KREYREN_oftc> oooo
<KREYREN_oftc> because krey is slowly loosing his mind from trying to document needed modules for tsvetan ^-^
<KREYREN_oftc> or likely already lost it
<ity> Hmm, is the hdmi-connector the only part needed?
<ity> There's also a few other things referencing HDMI
<apritzel> ity: basically everything that says hdmi needs to go in the DT, it's admittedly a bit convoluted, but you will figure it out
<ity> There is some reg_dldo1 that references hdmi both in pinetab & in teres-1, except the contents are diff
<ity> regulator-name is different, and regulator-always-on is not present in teres-1
<apritzel> the regulator name doesn't matter, it's purely for display (and documentation, to some degree)
<apritzel> and it's always-on for the PineTab because DLDO1 supplies something else (this ominous "sensor" I guess), which has apparently no reference in the DT
<apritzel> but is needed for some operation?
<apritzel> so you keep the dldo1 part in the teres.dts as it is, that looks correct
<ity> Ah, okis, thx!