KREYREN_oftc has quit [Remote host closed the connection]
Daanct12 has joined #linux-sunxi
colinsane has quit []
montjoie has joined #linux-sunxi
colinsane has joined #linux-sunxi
montjoie_ has quit [Ping timeout: 480 seconds]
apritzel has quit [Ping timeout: 480 seconds]
KREYREN_oftc has joined #linux-sunxi
hexdump01 has joined #linux-sunxi
chewitt has quit [Quit: Zzz..]
hexdump0815 has quit [Ping timeout: 480 seconds]
JohnDoe_71Rus has joined #linux-sunxi
<ity>
apritzel: Which AW boards do you have? Jw, since you recommended stuff with the A523 & A527 if I remember right...?
sunshavi_ has quit [Ping timeout: 480 seconds]
chewitt has joined #linux-sunxi
warpme has joined #linux-sunxi
evgeny_boger has joined #linux-sunxi
inf has joined #linux-sunxi
evgeny_boger has quit [Ping timeout: 480 seconds]
warpme has quit []
szemzoa has quit [Quit: Leaving...]
warpme has joined #linux-sunxi
mripard_ is now known as mripard
apritzel has joined #linux-sunxi
<apritzel>
ity: far too many! But tbh most AW SoCs are somewhat old and wimpy, they just happen to be cheap.
<apritzel>
The new A523/A527/T527 chips are at least a step in the right direction, with "new" cores (Cortex-A55 is from 2017), and stuff like PCIe and USB3.0
<apritzel>
so we need hardware out there for people to help out with development
anarsoul has quit [Read error: Connection reset by peer]
anarsoul has joined #linux-sunxi
hitechshell has joined #linux-sunxi
hitechshell has quit [Remote host closed the connection]
dsimic is now known as Guest1168
dsimic has joined #linux-sunxi
bauen1 has quit [Ping timeout: 480 seconds]
Guest1168 has quit [Ping timeout: 480 seconds]
evgeny_boger has joined #linux-sunxi
hramrach has quit [Quit: WeeChat 3.4.1]
<libv>
apritzel: i just discovered sunxi-fw
<libv>
cool stuff
warpme has quit []
<gamiee>
libv : yeah, I didn't knew about sunxi-fw too, and just few weeks ago apritzel mentioned it. really really handy tool
warpme has joined #linux-sunxi
<libv>
pooled a lot of knowledge and compressed it into what we basically all need when we get $image
<libv>
i do wonder about the boot0 parsing...
<libv>
first off, is there a reason why structs are not used more?
<libv>
the boot0 top header seems like a fixed quantity
<libv>
second, if we use structs for dram params, we can more easily access is individual values and do some sanity checks on them and narrow down the structure to just a few socs
<libv>
s/is individual/individual/
<libv>
for instance: A20 data gives a 0x40000000 clock for A64 and H616
<libv>
or A64 gives a "ODT enabled value" of 0x1000, whereas this seems to be more of a boolean
<libv>
for H616
<libv>
so even if we have no means of easily figuring out which soc an image is meant for, we can narrow it down significantly
<MoeIcenowy>
oh looks like a good tool from apritzel
bauen1 has joined #linux-sunxi
<apritzel>
libv: hey, it's Open Source, feel free to extend that. I wrote that just to scratch *my* itch(es).
<apritzel>
and I gave up on finding rhyme or reason in Allwinner data structures. We did some decoding on the A64 boot0, but AW changed that already for the H5
<apritzel>
so those A64 and H616 columns are basically like "old" and "new" ways of storing DRAM parameters, I didn't try to figure out which boot0 version a given image is
<apritzel>
with that being said: happy to take patches ;-)
Daanct12 has quit [Quit: WeeChat 4.2.1]
<apritzel>
one thing I have in some prototype stage is to replace parts of a given image, for instance to update a devicetree
<libv>
apritzel: ok, so you have no sentiment either way as to how to handle the dram patches
<libv>
will poke at it for a bit
<libv>
s/dram patches/dram structure/
<libv>
i love the tool, i was looking up how i used to do that in the olden days and it was non-trivial
<libv>
sunxi-fw makes it trivial, and i will also try to work it into the wiki usefully
<apritzel>
glad you like it!
<gamiee>
I might contribute to it too, I think it will be very helpful in my upcoming playing with Tina-Linux :D
aperezdc has quit [Remote host closed the connection]
<apritzel>
gamiee: oh, Tina Linux, sorry to hear that ;-)
<gamiee>
apritzel : :D haha, it got worse over last time I was working on it 3 years ago . It got more messier. But still semi-possible to work with. Although, I plan to just extract bits and pieces I need and integrate it to buildroot somehow.
<apritzel>
what is interesting in there? I thought it's just the same botched and slightly misguided kernel code, but just without the Android bits?
<gamiee>
in Tina? Kernel, uboot, tee and media user space stuff.
<gamiee>
(chip is not supported by mainline right now. I need to get firstly working on BSP, and then I might take look on mainline)
<apritzel>
any interesting chip? Or just yet another dual core A7 with an ISP?
<gamiee>
V853S :D (I know someone posted patches here, just I need to have proof of concept done with BSP first)