<apritzel>
montjoie: Hi, do you have some tests somewhere for the (sun8i-ce) crypto engine? I added H616 support, and TRNG looks good (according to rngtest), but I have no clue how to verify the other algorithms
<libv>
apritzel: do we want to list cpu core architecture or possible toolchain architectures in the sunxi-support sections of device pages?
<apritzel>
libv: what do you mean, exactly? 32/64 bit, or ARMv8.0/ARMv8.2?
<libv>
so user clearly see what toolchain and rootfs to choose
<libv>
so users clearly see even
<libv>
adding pmic to infobox as we speak btw
<libv>
also renaming video field to display, and adding a second entry to use a display variable so we can transition away from the video name
<libv>
someone actually went and listed media encoding/decoding capabilities on a device page
<libv>
i prefer to stick to display and media these days, and steer clear of the word video
<libv>
the only appropriate use is for something like the fosdem videobox, where it does display, capture, encoding and streaming all in one instance
<apritzel>
though "display" is a bit misleading when the device just has a HDMI port, isn't it? Or do you plan to have another field for that?
<apritzel>
I mean in the end it's the question whether the contributor understands the subtleties, and "video" is quite a self-explanatory term, I'd say
<libv>
i still regret coming up with xf86-video- for xorg drivers back in 2004
<libv>
xf86 was correct, but the video bit should have been display or graphics
JohnDoe_71Rus has joined #linux-sunxi
macromorgan has joined #linux-sunxi
<apritzel>
you might have a point, but I am not sure if this argumentation appeals to Joe Random adding a device page ;-)
KREYREN_oftc has joined #linux-sunxi
junari has joined #linux-sunxi
KREYREN_oftc has quit [Remote host closed the connection]
KREYREN_oftc has joined #linux-sunxi
junari has quit [Read error: No route to host]
warpme has quit []
KREYREN_oftc has quit [Remote host closed the connection]
KREYREN_oftc has joined #linux-sunxi
KREYREN_oftc has quit [Remote host closed the connection]
KREYREN_oftc has joined #linux-sunxi
KREYREN_oftc has quit [Remote host closed the connection]
KREYREN_oftc has joined #linux-sunxi
KREYREN_oftc has quit [Remote host closed the connection]
KREYREN_oftc has joined #linux-sunxi
warpme has joined #linux-sunxi
KREYREN_oftc has quit [Remote host closed the connection]
KREYREN_oftc has joined #linux-sunxi
warpme has quit []
Schimsalabim has quit [Ping timeout: 480 seconds]
Schimsalabim has joined #linux-sunxi
KREYREN_oftc has quit [Remote host closed the connection]
KREYREN_oftc has joined #linux-sunxi
Schimsalabim has quit [Quit: Quit]
Schimsalabim has joined #linux-sunxi
Schimsalabim has quit []
Schimsalabim has joined #linux-sunxi
<Schimsalabim>
is anyone aware of work being done on DDR4 support for H616 ? are there any boards in the wild that actually carry DDR4 (and run a form of linux) on Allwinner SoC that we know of ?
<apritzel>
we haven't heard of any, and I wonder if there are any at all. I mean what would DDR4 give you? Are you hoping for modules?
<apritzel>
Schimsalabim: any particular reason you ask?
<Schimsalabim>
client asked me to make custom board with 64 bit SoC running DDR4 mem. was thinking of H616. Datasheet is hopeful but practice seems lacking.
<jakllsch>
why DDR4 and not LPDDR4?
<apritzel>
Schimsalabim: well, the user manual mentions DDR4 support, but that's about the only thing you will learn about it from there :-(
<Schimsalabim>
jakllsch: Not sure. they had an interest in a particular Micron chip-combo 2x16.
<apritzel>
adding DDR4 support to U-Boot DRAM "driver" is not trivial
<Schimsalabim>
apritzel: i figured that out already ;)
<Schimsalabim>
ouch
<Schimsalabim>
lots of magic numbers in there
<Schimsalabim>
altough phy_init looks like direct transcript of the pinout there is still too much voodoo
hentai has quit [Remote host closed the connection]
<apritzel>
junari and jernej might know more about it. typically either of them needs a board and some motivation/convincing ;-)
<apritzel>
but if you can help it, just avoid DDR4, though it sounds like it's not your decision
<Schimsalabim>
indeed. is difficult to change their minds.
<jernej>
since support for other types is pretty much complete, DDR4 shouldn't be *that* hard, but it still some effort
warpme has joined #linux-sunxi
<Schimsalabim>
jerney: my attempts so far (with absolutely insufficient DRAM knowledge) led to repeatedly hitting the calibration failure.
<Schimsalabim>
quite difficult to make steps without validated hardware.
junari has joined #linux-sunxi
<jernej>
if you design HW from scratch there is always of question of DRAM config values
<jernej>
I heard AW can determine them if you sent HW to them, but don't hold me on that
<Schimsalabim>
so far i have not gotten any response from their formal communication line.
<Schimsalabim>
i can persuade my client to donate a board for good cause though i am sure
<Schimsalabim>
how to get a foot between the AW door ?
<jernej>
tbh, I'm not sure, mainline effort here is completely separate from them
<junari>
I think it should be via official distributors
<Schimsalabim>
junari: sounds reasonable, but i am guessing its not mouser or farnell....
<Schimsalabim>
maybe LCSC might be an entry. let me check on that.
<junari>
My local distributor has contacts with AW. We were planning to use som for now, but if we switched to a completely custom version, I think it would be possible to solve this issue through it
<junari>
One of the Chinese companies very strictly controls its supplies to some countries. Actually, my distributor tried to influence this through allwinner. But failed
<junari>
As far as I know, sputnik2019 has some developments with DDR4 and h616. Maybe he can help with the initial configuration for DDR4. you can find him on github
<apritzel>
FreeBSD should work on the A64, at least it has several drivers, but I don't know how complete the support is
gnarface has quit []
gnarface has joined #linux-sunxi
<gnarface>
i had a openbsd install booting a while back on A64, but there was no cpu frequency governor support and every time i attempted an update it rendered the install unbootable and i couldn't figure out how to repair it
<gnarface>
also, anyone happen to know why i just got the error "#linux-sunxi :Cannot send to channel (You are not registered and verified. '/msg NickServ help' to learn how to register and verify)" before reconnecting just now?
<gnarface>
i've clearly been registered and verified this whole time, did something go wrong with NickServ?
<gnarface>
should i change my password?
<KREYREN_oftc>
> also, anyone happen to know why i just got the error "#linux-sunxi ... < -- Because we are on OFTC? :p
<gnarface>
goodness, i didn't know it was known for being bad at that
<gnarface>
this is the first sign of trouble i've had
<gnarface>
i probably would have stuck with it if i could have figured out the boot corruption issue, but i couldn't so i ended up using devuan instead
<KREYREN_oftc>
gnarface, i though that OFTC is well known for having all kinds of issues :D i keep hearing people complaining about issues alike
* KREYREN_oftc
prefers hackint for that reason also
<gnarface>
noted
<KREYREN_oftc>
gnarface, that's for the link i will note that in my issue and the freebsd ppl said that A64-OlinuXino is officially supported so that should make things easier too :D
<gnarface>
not that it matters much but the board i put openbsd on wasn't the LTS board mentioned in that article, it was the previous "pine64 plus" model the LTS one is based off
<KREYREN_oftc>
noted
<KREYREN_oftc>
the A20 seems to have the best support on freebsd and A64 seems to lack a lot of things actually