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> looks like it's a bit transposed, so the digits are segments and vice versa...
<apritzel> ah, there is titanmec,transposed to fix that, and with that it's actually already perfect, it seems
Schimsalabim has joined #linux-sunxi
apritzel has quit [Ping timeout: 480 seconds]
ftg has quit [Read error: Connection reset by peer]
vagrantc has quit [Quit: leaving]
bauen1 has quit [Ping timeout: 480 seconds]
Sensu_Be1 has joined #linux-sunxi
Sensu_Bean has quit [Read error: Connection reset by peer]
Sensu_Bean has joined #linux-sunxi
Sensu_Be1 has quit [Ping timeout: 480 seconds]
hexdump01 has joined #linux-sunxi
Sensu_Bean has quit [Ping timeout: 480 seconds]
Sensu_Bean has joined #linux-sunxi
hexdump0815 has quit [Ping timeout: 480 seconds]
Hypfer has quit [Ping timeout: 480 seconds]
Danct12 has joined #linux-sunxi
sdfgsdfs has quit [Ping timeout: 480 seconds]
JohnDoe_71Rus has joined #linux-sunxi
Hypfer has joined #linux-sunxi
Sensu_Be1 has joined #linux-sunxi
Sensu_Bean has quit [Read error: Connection reset by peer]
gsz has joined #linux-sunxi
gsz has quit []
gsz has joined #linux-sunxi
apritzel has joined #linux-sunxi
warpme has joined #linux-sunxi
apritzel has quit [Ping timeout: 480 seconds]
Sensu_Bean has joined #linux-sunxi
Sensu_Be1 has quit [Read error: Connection reset by peer]
bauen1 has joined #linux-sunxi
BroderTuck has joined #linux-sunxi
<BroderTuck> apritzel: Great. Now if I could only figure out why "dmesg |grep -i tm16" still gives a null response (and a black auxdisplay) on my end...
<BroderTuck> Turns out the android does infact still work and it works there at least...
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
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
bauen1 has quit [Ping timeout: 480 seconds]
warpme has quit []
apritzel has joined #linux-sunxi
warpme has joined #linux-sunxi
<apritzel> BroderTuck: if /sys/class/spi is empty, you are probably missing CONFIG_SPI_GPIO
szemzoa has quit [Remote host closed the connection]
szemzoa has joined #linux-sunxi
<BroderTuck> Right, s
szemzoa has quit [Remote host closed the connection]
szemzoa has joined #linux-sunxi
<BroderTuck> apritzel: Success!
<BroderTuck> So, another config to add to the "turn on manually" list, like the pck600 one
<apritzel> distros seems to enable SPI_GPIO=m
Schimsalabim has quit [Ping timeout: 480 seconds]
Schimsalabim has joined #linux-sunxi
<BroderTuck> wlan-hi and wlan-lo are flipped, otherwise all the symbols seem to be correctly mapped
<apritzel> BroderTuck: can you prepare a DT patch for mainline? That's pending on those bindings, of course, but would be good to have this out
<BroderTuck> Bah, seems i fixed the wlan order on the v2 file on my website but not in the local version. Will post a v3 with all fixes and based on linux-next rather than a p
<BroderTuck> *rather than -rc7-with-many-upcoming-patchsets
<apritzel> BroderTuck: I meant can you please prepare a proper patch, with a commit message and a Signed-off-by:, and then send this to the mailing list?
<BroderTuck> I'll see what I can do but I'm gonna need to read up on patch submitting guidelines first
<BroderTuck> Anyway, I added some simple setup in rc.local, and then added an all-star line in crontab with /usr/bin/date +"%H%M" >/sys/class/leds/display/value
<apritzel> BroderTuck: don't forget to setup a timer trigger for the colon, to get that full clock feeling ;-)
<BroderTuck> apritzel: Yeah, that's part of the setup
<apritzel> BroderTuck: feel free to send a patch email to me first, if you want to have a quick check
warpme has quit []
<BroderTuck> Just a shame that the box is upside down for now, since the serial cable sticks out that way
Danct12 has quit [Ping timeout: 480 seconds]
Schimsalabim has quit [Ping timeout: 480 seconds]
chewitt has joined #linux-sunxi
Schimsalabim has joined #linux-sunxi
Schimsalabim has quit [Read error: Connection reset by peer]
Schimsalabim has joined #linux-sunxi
warpme has joined #linux-sunxi
warpme has quit []
gnarface has quit [Remote host closed the connection]
Schimsalabim has quit [Ping timeout: 480 seconds]
Schimsalabim has joined #linux-sunxi
gnarface has joined #linux-sunxi
Schimsalabim has quit [Read error: Connection reset by peer]
Schimsalabim has joined #linux-sunxi
<BroderTuck> apritzel: you have mail :)
<BroderTuck> and as I said in there, I don't really have things setup properly for serious development
gnarface has quit [Quit: Leaving]
Schimsalabim has quit [Ping timeout: 480 seconds]
Schimsalabim has joined #linux-sunxi
bauen1 has joined #linux-sunxi
warpme has joined #linux-sunxi
warpme has quit []
gnarface has joined #linux-sunxi
dsimic is now known as Guest22645
dsimic has joined #linux-sunxi
Guest22645 has quit [Ping timeout: 480 seconds]
<BroderTuck> New projector SoC: H727
<BroderTuck> listed on the allwinner homepage
mripard has quit [Ping timeout: 480 seconds]
<apritzel> meh, A53s and G31, so probably a H616 variant
<Lightsword> apritzel, is NAND using mtd subsystem drivers normally able to read data from NAND originally written using BSP drivers?
Sensu_Be1 has joined #linux-sunxi
junari has joined #linux-sunxi
<apritzel> AFAIK NAND access in mainline (if you have it) is incompatible to how the BSP writes it
<junari> A537 and A333 much interesting. Looks like variation of a523 with A73 cores
<apritzel> junari: I wouldn't call it "variation", it's quite a different chip, although it might share a lot of peripherals with the A523
<junari> ok, I will say that these chips are most similar to the A523
Sensu_Bean has quit [Ping timeout: 480 seconds]
<Lightsword> apritzel, yeah...we have it mostly brought up on mainline
<Lightsword> "the bad block marker in the OOB area seems to be at the end of the OOB instead of the begining"
<apritzel> Lightsword: is that with old limitation of treating MLC chips as SLC only, halving the capacity?
<apritzel> or do you have SLC chips on your boards?
<Lightsword> nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128
<apritzel> 256MiB? Is that SPI-NAND then? Or attached to the raw NAND interface?
<Lightsword> apritzel, raw nand, SLC
<junari> but a537 results not so impressive https://browser.geekbench.com/v6/cpu/13002972
Sensu_Bean has joined #linux-sunxi
Sensu_Be1 has quit [Read error: Connection reset by peer]
junari_ has joined #linux-sunxi
<apritzel> junari: well, while the A73 is^Wwas quite an efficient big core, it's also like 9 years old by now, so go figure ...
junari is now known as Guest22649
junari_ is now known as junari
<junari> Yes, I realize that, but the A527 has a better score, which shouldn't be
<apritzel> do you mean the single-core score?
Guest22649 has quit [Ping timeout: 480 seconds]
<junari> single and multicore, here a523 score https://browser.geekbench.com/v6/cpu/11015499
<junari> and it's higher in both cases
<apritzel> well, there is also the core frequency at play here, which might be different, but on average the A537 seems to score like 250, over the more like 240 for the A523
<Lightsword> apritzel, so the bootloader needs to be written using the BSP ECC format? or how does mainline nand work then?
<apritzel> I am trying to stay away from NAND, so don't have much experience, but IIUC you can play some tricks to make the BROM happy, but it needs to be somewhat compatible, yes
<apritzel> but that affects only the first few dozen KB or so, so the rest can be used differently, in a way to suits mainline better
<Lightsword> apritzel, ah, so allwinner uses BROM compatible format for entire NAND though? or do they use multiple formats as well?
mripard has joined #linux-sunxi
apritzel has quit [Ping timeout: 480 seconds]
flyback has quit [Ping timeout: 480 seconds]
flyback has joined #linux-sunxi
chewitt has quit [Quit: Zzz..]
hazardchem has quit [Read error: Connection reset by peer]
hazardchem has joined #linux-sunxi
junari has quit [Ping timeout: 480 seconds]
Sensu_Be1 has joined #linux-sunxi
Sensu_Bean has quit [Read error: Connection reset by peer]
hazardchem has quit [Read error: Connection reset by peer]
hazardchem has joined #linux-sunxi
JohnDoe_71Rus has quit [Quit: KVIrc KVIrc Quasar 5.2.6, revision: 5.2.6+git-7614-6f23368f1, build type: debug, sources date: 20160102, built on: 2025-03-30 13:34:35 UTC 5.2.6+git-7614-]
apritzel has joined #linux-sunxi
<apritzel> Lightsword: I think I read that the BROM readable part is different (simpler?), https://linux-sunxi.org/NAND#Background seems to support this
<Lightsword> apritzel, I guess https://github.com/linux-sunxi/sunxi-tools/blob/master/nand-image-builder.c was designed for building images the BROM will accept?
<apritzel> yes, but keep in mind that this is all old stuff, >10 years ago, around the Allwinner A20 times, not sure how much of this still applies
<Lightsword> apritzel, is the h6 the newest allwinner SoC with nand support in mainline?
gsz has quit [Ping timeout: 480 seconds]
<apritzel> H6? You wish, I think it's more like A10, maybe A23, judging by the compatible string in the kernel
warpme has joined #linux-sunxi
<paulk> IIRC it's A33
<paulk> at least I know a device running mainline with A33 that used NAND
<paulk> and I haven't seen any every since
<BroderTuck> Yeah, my poor little H3 box (R.I.P) never saw mainline support for its NAND
warpme has quit []
<Lightsword> weird that NAND wasn't more common on these sort of boards, it's generally cheaper than emmc right?
Sensu_Bean has joined #linux-sunxi
Sensu_Be1 has quit [Read error: Connection reset by peer]
<apritzel> that used to be indeed the case, but we haven't seen many raw NANDs in the more recent past (although some pop up once in a while in very cheap devices)
<Lightsword> and most were MLC NAND not SLC like mine?
Sensu_Be1 has joined #linux-sunxi
<apritzel> yes, because SLC are nowadays much more expensive, which defeats the purpose
<Lightsword> apritzel, is SLC more reliable than emmc usually?
<apritzel> maybe yours is cheaper than eMMC because it's so small? Even back in the A20 days I think the NANDs were like 4 or 8GB, so 256MB is really tiny
<Lightsword> yeah, everything on mine is tiny, but the overall systems are quite expensive so reliability is important I'm sure
Sensu_Bean has quit [Ping timeout: 480 seconds]
<Lightsword> they just don't need much storage/ram
<apritzel> hard to say, I guess with raw NAND you have more control over it (in software), but that means that you also have to provide the software to do this cleverly
BroderTuc1 has joined #linux-sunxi
BroderTuck has quit [Ping timeout: 480 seconds]
Sensu_Bean has joined #linux-sunxi
Sensu_Be1 has quit [Ping timeout: 480 seconds]
hramrach has quit [Ping timeout: 480 seconds]
hramrach has joined #linux-sunxi
ftg has joined #linux-sunxi
Schimsalabim has quit [Read error: Connection reset by peer]
Schimsalabim has joined #linux-sunxi
BroderTuc1 has quit [Ping timeout: 480 seconds]
Schimsalabim has quit [Ping timeout: 480 seconds]
Schimsalabim has joined #linux-sunxi
Schimsalabim has quit [Ping timeout: 480 seconds]
Schimsalabim has joined #linux-sunxi
evgeny_boger has quit [Ping timeout: 480 seconds]
ftg^ has joined #linux-sunxi