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
montjoie_ has joined #linux-sunxi
montjoie has quit [Ping timeout: 480 seconds]
fraolt has joined #linux-sunxi
fraolt_ has quit [Ping timeout: 480 seconds]
gnarface has quit [Quit: Leaving]
xypron has quit [Quit: xypron]
xypron has joined #linux-sunxi
gnarface has joined #linux-sunxi
junari_ has joined #linux-sunxi
junari__ has joined #linux-sunxi
junari_ has quit [Ping timeout: 480 seconds]
junari__ has quit [Ping timeout: 480 seconds]
junari has joined #linux-sunxi
hexdump01 has joined #linux-sunxi
hexdump0815 has quit [Ping timeout: 480 seconds]
junari has quit [Ping timeout: 480 seconds]
rubberduck has quit [Quit: https://quassel-irc.org - Komfortabler Chat. Überall. ]
rubberduck has joined #linux-sunxi
JohnDoe_71Rus has joined #linux-sunxi
gnarface has quit [Quit: Leaving]
junari has joined #linux-sunxi
gnarface has joined #linux-sunxi
Nemo_bis has joined #linux-sunxi
junari has quit [Remote host closed the connection]
sunshavi_ has joined #linux-sunxi
sunshavi has quit [Ping timeout: 480 seconds]
kilobyte_ has joined #linux-sunxi
tnovotny has joined #linux-sunxi
evgeny_boger has joined #linux-sunxi
dliviu has quit [Ping timeout: 480 seconds]
dliviu has joined #linux-sunxi
evgeny_boger has quit [Remote host closed the connection]
nashpa has joined #linux-sunxi
dliviu has quit [Ping timeout: 480 seconds]
kuba2k2 has joined #linux-sunxi
bauen1 has quit [Ping timeout: 480 seconds]
tnovotny_ has joined #linux-sunxi
tnovotny has quit [Ping timeout: 480 seconds]
tnovotny_ has quit [Ping timeout: 480 seconds]
bauen1 has joined #linux-sunxi
kuba2k2 has quit [Ping timeout: 480 seconds]
kuba2k2 has joined #linux-sunxi
tnovotny_ has joined #linux-sunxi
rajkosto has joined #linux-sunxi
kuba2k2 has quit [Ping timeout: 480 seconds]
Okhunjon007 has joined #linux-sunxi
Okhunjon007 has quit []
kuba2k2 has joined #linux-sunxi
tnovotny_ has quit []
ftg has joined #linux-sunxi
rajkosto has quit [Read error: Connection reset by peer]
vagrantc has joined #linux-sunxi
kuba2k2 has quit [Ping timeout: 480 seconds]
Asara has quit [Quit: leaving]
Asara has joined #linux-sunxi
xypron has quit [Ping timeout: 480 seconds]
juri__ has joined #linux-sunxi
juri_ has quit [Ping timeout: 480 seconds]
juri_ has joined #linux-sunxi
kuba2k2 has joined #linux-sunxi
juri__ has quit [Ping timeout: 480 seconds]
kuba2k2 has quit [Ping timeout: 480 seconds]
JohnDoe_71Rus has quit []
xypron has joined #linux-sunxi
kuba2k2 has joined #linux-sunxi
bauen1 has quit [Ping timeout: 480 seconds]
jason123santaonirc has joined #linux-sunxi
apritzel has joined #linux-sunxi
jason123onirc has quit [Ping timeout: 480 seconds]
<apritzel> libv: re: U-Boot wiki page: what do you mean? separate wiki pages? Or just resorting the paragraphs of the "Build" section?
<libv> apritzel: i'm thinking about splitting the build bit out and have two build pages
<libv> and to also clearly mark which SoC are armv7 and which are armv8
mps_ has joined #linux-sunxi
mps has quit [Ping timeout: 480 seconds]
bauen1 has joined #linux-sunxi
kuba2k2 has quit []
<apritzel> libv: well, apart from the cross-compiler to use, armv7 and armv8 should not differ too much in U-Boot, conceptually
<apritzel> and there is support for H3 in crust as well, which requires a similar build line for armv7 then, just s/BL31/SCP/ (patches pending)
<apritzel> besides, the build lines are just convenience, the real documentation is in doc/board/allwinner/sunxi.rst
<apritzel> ItsKaitlyn03: there is no official information, but indeed the A100 vanished from the website without any trace
<apritzel> as far as we know, the A100 was a lower bin of the A133, so we assume that software-wise it's the same, just a different name
<apritzel> but we don't know for sure, and we try to avoid speculation in the wiki
paulk-bis has joined #linux-sunxi
paulk has quit [Ping timeout: 480 seconds]
<ItsKaitlyn03> looking at it closer the A100 is afaik a lower specced A133
<ItsKaitlyn03> and all A133 software is compatible with A100, so
ftg has quit [Read error: Connection reset by peer]
<ItsKaitlyn03> apritzel: I wonder if A100 is the base variant of the A100 series SKU as a whole, where A133 is a slightly faster A100
<apritzel> that's what I wrote above ;-)
<apritzel> and rumour has it that all A1xx dies qualified for the A133 bin, so the A100 became unnecessary
<ItsKaitlyn03> ah so probably just a last minute rename, interesting
<apritzel> though it's still weird that the A100 vanished in an Orwellian fashion: back then it was on the Allwinner website, and even Allwinner employees provided upstream patches
<ItsKaitlyn03> the DTS for it exists in the linux repo
<ItsKaitlyn03> (mainline)
<apritzel> yes, that's what I meant: two Allwinner employees worked on that, though reportedly more in their spare time than supported by their company
<ItsKaitlyn03> I might take a shot at porting uboot to my tablet but I don't think a100 support is in uboot atm
<apritzel> no, it isn't
<apritzel> but it shouldn't be so hard
<apritzel> the H616 brought it most of the driver changes already
<ItsKaitlyn03> I did notice that someone had actually forked u-boot already and added A100/A133 support? https://github.com/aodzip/u-boot-2022.10-Allwinner-A133 interesting
<apritzel> graphics is a more complicated story, as we would need both display engine support, as well as some kind of panel driver
<apritzel> yeah, actually caring about mainlining stuff doesn't seem to be popular here anymore :-(
<ItsKaitlyn03> Never did linux kernel dev or uboot dev so entirely new territory to me haha
<apritzel> ItsKaitlyn03: that comment of mine wasn't really targeted at you ;-)
<ItsKaitlyn03> ah xP, I might take a shot at getting u-boot going. I did already find UART on my board, I'll likely solder to that at some point.
<ItsKaitlyn03> Also, assuming I'd use u-boot as a FEL payload if I'm correct?
<apritzel> yes, that's the easiest, and having serial is almost required
<apritzel> I have an A133 tablet as well, with serial and FEL working, but as usual the DRAM driver is the showstopper
<ItsKaitlyn03> ah yeah I heard about DRAM being a pain
<ItsKaitlyn03> I did find a downstream A133 linux kernel from some other board
<ItsKaitlyn03> But it is unfortunately behind baidu and I do not feel like finding some way to grab it
<apritzel> the kernel is less of a problem, as the existing A100 support covers it already
<apritzel> and I have rebased and updated the second A100 Linux patch series already
<apritzel> this repo you pointed to seems to have DRAM support, based on the H616 support, it seems
<ItsKaitlyn03> yeah i noticed that, i guess the a100/a133 have stuff in common with the h616?
<apritzel> if that indeed works, there would be clean way of upstreaming it
<apritzel> DRAM is always undocumented, so we can only guess and disassemble ;-)
<apritzel> one would need to compare those files against the original H616 files
<apritzel> if the differences are small(ish), there could even be one single driver (we have that for the H3/A64/R40)
<apritzel> ItsKaitlyn03: maybe that is something you could look at? Find out what was changed compared to the H616 code?
<apritzel> there were some changes recently in the mainline H616 DRAM code, so you would need to compare against an older version (2022.10, I guess)