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
apritzel has quit [Ping timeout: 480 seconds]
Danct12 has joined #linux-sunxi
cnxsoft has joined #linux-sunxi
moteen has joined #linux-sunxi
moteen_ has joined #linux-sunxi
moteen has quit [Ping timeout: 480 seconds]
moteen_ has quit [Ping timeout: 480 seconds]
Daaanct12 has joined #linux-sunxi
Danct12 has quit [Read error: Connection reset by peer]
chewitt has joined #linux-sunxi
apritzel has joined #linux-sunxi
apritzel has quit [Ping timeout: 480 seconds]
chewitt has quit [Quit: Zzz..]
Daaanct12 has quit [Read error: Connection reset by peer]
Danct12 has joined #linux-sunxi
szemzoa has quit [Remote host closed the connection]
szemzoa has joined #linux-sunxi
apritzel has joined #linux-sunxi
apritzel has quit [Ping timeout: 480 seconds]
szemzoa has quit [Remote host closed the connection]
szemzoa has joined #linux-sunxi
nikbor has joined #linux-sunxi
<nikbor> hello, is there some outstanding kernel work on the A64?
paulk has joined #linux-sunxi
moteen has joined #linux-sunxi
moteen has quit [Remote host closed the connection]
moteen has joined #linux-sunxi
<gamiee> hi nikbor, what you mean?
<nikbor> i have a pine64-lts board
<nikbor> and would like to do some kernel hacking on the a64 chip tha this board has
<nikbor> so i was wondering if there is missing kernel support for a particular peripheral of the chip?
rajkosto has quit [Read error: Connection reset by peer]
<gamiee> Best is to check this
<gamiee> Looks like everything is almost done :D but there is still room for improvement
<gamiee> For example, video encoding drivers are missing
paulk has quit [Quit: WeeChat 3.5]
moteen has quit [Remote host closed the connection]
szemzoa has quit [Remote host closed the connection]
moteen has joined #linux-sunxi
evgeny_boger has joined #linux-sunxi
moteen has quit [Remote host closed the connection]
moteen has joined #linux-sunxi
montjoie_ is now known as montjoie
szemzoa has joined #linux-sunxi
moteen has quit [Remote host closed the connection]
moteen has joined #linux-sunxi
Danct12 has quit [Ping timeout: 480 seconds]
bauen1 has quit [Ping timeout: 480 seconds]
Danct12 has joined #linux-sunxi
moteen_ has joined #linux-sunxi
moteen has quit [Ping timeout: 480 seconds]
apritzel has joined #linux-sunxi
moteen_ has quit [Remote host closed the connection]
szemzoa has quit [Remote host closed the connection]
szemzoa has joined #linux-sunxi
szemzoa has quit [Remote host closed the connection]
szemzoa has joined #linux-sunxi
moteen has joined #linux-sunxi
moteen_ has joined #linux-sunxi
moteen has quit [Ping timeout: 480 seconds]
bauen1 has joined #linux-sunxi
moteen_ has quit [Remote host closed the connection]
moteen has joined #linux-sunxi
moteen has quit [Remote host closed the connection]
moteen has joined #linux-sunxi
moteen has quit [Remote host closed the connection]
Danct12 has quit [Remote host closed the connection]
moteen has joined #linux-sunxi
Guest3173 is now known as jelly
moteen has quit [Remote host closed the connection]
moteen has joined #linux-sunxi
moteen has quit [Remote host closed the connection]
moteen has joined #linux-sunxi
moteen_ has joined #linux-sunxi
moteen has quit [Ping timeout: 480 seconds]
chewitt has joined #linux-sunxi
nikbor has left #linux-sunxi [Leaving]
moteen_ has quit [Remote host closed the connection]
moteen has joined #linux-sunxi
moteen has quit [Ping timeout: 480 seconds]
linusw___ has joined #linux-sunxi
Daanct12 is now known as Danct12
moteen has joined #linux-sunxi
moteen has quit [Remote host closed the connection]
moteen has joined #linux-sunxi
bauen1 has quit [Ping timeout: 480 seconds]
JohnDoe_71Rus has joined #linux-sunxi
moteen has quit [Remote host closed the connection]
cnxsoft has quit []
bauen1 has joined #linux-sunxi
bauen1_ has joined #linux-sunxi
moteen has joined #linux-sunxi
bauen1 has quit [Ping timeout: 480 seconds]
dliviu has quit []
dliviu has joined #linux-sunxi
Danct12 has quit [Remote host closed the connection]
Danct12 has joined #linux-sunxi
moteen_ has joined #linux-sunxi
moteen has quit [Ping timeout: 480 seconds]
apritzel has quit [Ping timeout: 480 seconds]
vagrantc has joined #linux-sunxi
moteen has joined #linux-sunxi
moteen_ has quit [Ping timeout: 480 seconds]
hlauer has joined #linux-sunxi
apritzel has joined #linux-sunxi
JohnDoe_71Rus has quit []
moteen_ has joined #linux-sunxi
moteen has quit [Ping timeout: 480 seconds]
moteen_ has quit [Remote host closed the connection]
moteen has joined #linux-sunxi
moteen has quit [Ping timeout: 480 seconds]
hentai has joined #linux-sunxi
hentai has quit [Remote host closed the connection]
hentai has joined #linux-sunxi
wingrime1 has joined #linux-sunxi
wingrime_ has quit [Ping timeout: 480 seconds]
hlauer has quit [Ping timeout: 480 seconds]
<LordKalma> I know this will be a very broad and random question, but do any of you experts know if something pertaining to clocks and timers changed between kernel 5.8 and 5.9? That driver I reverse engineered works fine on 5.8 kernels, but looks a bit weird on 5.9... A user reported that changing CPU governor to performance helped (on our particular device)
<LordKalma> but others couldn't verify that. Something weird is going on...
<apritzel> LordKalma: how easily and reliably can your reproduce it? Have you thought about bisecting that?
<LordKalma> I have. The thought of doing that is daunting, but we'll have to haha
<LordKalma> A member using build root could see the problem, another building armbian with the driver patched in also sees the problem.Text looks weird, bit as if pixelated, some yellowish borders on things... Neofetch has those color boxes in the bottom and they are as if unaligned, its weird
<LordKalma> I don't have a good picture, I think, but let me see here
<apritzel> I understand that bisecting sounds daunting, but actually it's straightforward, once you wrapped your head around it
<apritzel> and it's very powerful (if you have a clear regression), since you don't need to guess or make assumptions or dig into code
<apritzel> you just follow the procedure
<apritzel> just one advice: don't go to lunch in the middle of it, or you will forget where you were ;-)
<apritzel> or you write down exactly in which state you left ;-)
vagrantc has quit [Quit: leaving]
<LordKalma> Hahah yeah, I'd do it with a spreadsheet
<LordKalma> Notice the squares
<apritzel> I was just asking if you can quickly judge whether a particular build is good or bad
<apritzel> there are regressions that take hours to reproduce, and bisecting that is much less fun
<LordKalma> Well, testing is just looking at the screen after boot
<LordKalma> It's more or less the time it takes to build the kernel I guess
<apritzel> that's good, one thing less to worry about
<apritzel> and yeah, you need a box that can build a kernel rather quickly, and an easy and quick way to get that kernel booted
<apritzel> can you do FEL boot/
<apritzel> ?
<LordKalma> FEL?
<apritzel> that BootROM USB mode, where you upload firmware and/or kernels via the USB-OTG port
<apritzel> so no SD card swapping
<LordKalma> They left access to the debug serial port in, yes, so I guess that's a possibility
<apritzel> well, you need access to USB port 0
<apritzel> which might require a special cable (USB-A to USB-A), unless there is a micro-B USB port
<LordKalma> USB-C, fortunately
<apritzel> ah, might be even better!
<apritzel> because it's OTG and host in one, so you just need an USB-C to A cable
<apritzel> is there some "FEL" or "UBOOT" button on the board?
<LordKalma> Which, hilariously doesn't work with a USB-C to C cable. Haha I don't know what they botched but you can't connect to a USB-C on the host
<LordKalma> Probably both the computer and the radio try to host?
<LordKalma> Although the radio has two USB ports, one says host and the other says dev, and we use the dev port
<apritzel> use for what?
<apritzel> anyway, if you have a rather reliable and not too complicated way of booting a new kernel, that's fine
<LordKalma> It's the one with access to serial debugging, sorry, didn't explain properly
<LordKalma> I'm myself learning all of this still, sometimes I may say something dumb
<apritzel> so it has a USB->serial chip on the board?
<LordKalma> The dev port, when connected to a computer, shows up as two serial ports and a sound card
<LordKalma> So yes, plus another serial to USB, plus a codec ic, plus a hub
<apritzel> I see
<LordKalma> Ou well, bissect it is
<apritzel> do you know how to do that?
<LordKalma> Yes, not new to git at least :)
<apritzel> oh, almost forgot: I made a sun8i-r16-x6100.dts the other day ;-)
<apritzel> based on the de-compiled DTB from that image
<LordKalma> Haha you have to send me the link for that 😂
<LordKalma> I think I have also one of those someone sent me as well, not sure where
<apritzel> but adapted to the mainline DTs, so it includes the sun8i-a33.dtsi, and fits right into the kernel or U-Boot build system
<LordKalma> I put my driver here, out of tree, because I'm still unsure about the copyright/licensing of it
<LordKalma> That's really cool!
<apritzel> I was curious what it would take, and if there is an easy way to automate this
<apritzel> the sad answer is "no" ;-)
<LordKalma> Haha that's a shame
<apritzel> so I had to manually match the nodes, remove the parts that are SoC (and not board) specific, to be just left with the differences
<apritzel> it's probably easier to take an existing DT from the kernel and adjust this
<LordKalma> And no easy way to just get the diff to the dtsi
<LordKalma> Would you mind sharing that dts?
<LordKalma> I'll have to prepare some scripts to do the bissecting
<apritzel> it's just compile tested, and surely contains some bugs, so no guarantees
<apritzel> (actually that's the DT that applies to mainline Linux, so it's >=v5.13)
<LordKalma> thanks, that's already amazing work :)
<LordKalma> In fact, speaking of
<LordKalma> this is the code a member of the community is using to make their images: https://github.com/sstjohn/x6100-wspr
<LordKalma> I'm trying to build the most bare-bones possible thing: https://github.com/ruilvo/AetherX6100
<LordKalma> I stripped almost every package, added just my panel driver
<LordKalma> I copy-pasted this, of course
<LordKalma> but where does this come from, how do you actually choose what to put in a defconfig? (for example)
<apritzel> well, this is too embedded for my taste ;-)
<LordKalma> hahah Linux from scratch kinda person? :D
<apritzel> I made the DTS because it's the only actual complicated thing you need, the rest is bog standard Allwinner A33
<apritzel> LFS: not really
<apritzel> the A33 is well supported in the kernel and U-Boot, so all you need is the DT to describe your *board*
<apritzel> the rest is off-the-shelf Linux/U-Boot
<apritzel> you just need a distro that supports ARMv7
<apritzel> so I like to split things up: there is U-Boot(firmware), the kernel, userland
<apritzel> in your case you probably need some special userland, because that contains the actual radio app and the right tools for the UI (those rotary encode knobs, for instance)
<LordKalma> yes, but for testing it's okay the radio doesn't radio :D
<apritzel> yeah, the actual radio is for people without imagination, I guess :-D
<LordKalma> I bought it for the radioing aspect of it
<LordKalma> only after I discovered everybody was "hacking" it
<LordKalma> wanted to get in on the fun