rellla changed the topic of #linux-sunxi to: Allwinner/sunxi /development discussion - did you try looking at our wiki? https://linux-sunxi.org - Don't ask to ask. Just ask and wait! - https://github.com/linux-sunxi/ - Logs at http://irclog.whitequark.org/linux-sunxi - *only registered users can talk*
lurchi_ has joined #linux-sunxi
swiftgeek has quit [Ping timeout: 256 seconds]
swiftgeek has joined #linux-sunxi
lurchi_ has quit [Ping timeout: 256 seconds]
lurchi_ has joined #linux-sunxi
ldevulder has quit [Remote host closed the connection]
ldevulder has joined #linux-sunxi
luke-jr has joined #linux-sunxi
lurchi_ is now known as lurchi__
popolon has quit [Quit: WeeChat 3.0]
ChriChri_ has joined #linux-sunxi
Mangy_Dog has quit [Ping timeout: 256 seconds]
ChriChri has quit [Ping timeout: 272 seconds]
ChriChri_ is now known as ChriChri
ganbold_ has quit [Read error: Connection reset by peer]
kaspter has joined #linux-sunxi
ganbold has joined #linux-sunxi
apritzel has quit [Ping timeout: 264 seconds]
lurchi__ is now known as lurchi_
mripard has quit [Ping timeout: 240 seconds]
megi has joined #linux-sunxi
lurchi_ is now known as lurchi__
kaspter has quit [Ping timeout: 256 seconds]
kaspter has joined #linux-sunxi
kaspter has quit [Ping timeout: 265 seconds]
kaspter has joined #linux-sunxi
sunshavi has quit [Read error: Connection reset by peer]
tuxillo has quit [Ping timeout: 256 seconds]
tuxillo has joined #linux-sunxi
megi has quit [Ping timeout: 260 seconds]
megi has joined #linux-sunxi
ec0 has joined #linux-sunxi
victhor has quit [Ping timeout: 258 seconds]
sunshavi has joined #linux-sunxi
kaspter has quit [Ping timeout: 265 seconds]
kaspter has joined #linux-sunxi
tuxd3v has joined #linux-sunxi
swiftgeek has quit [Ping timeout: 256 seconds]
swiftgeek has joined #linux-sunxi
[7] has quit [Ping timeout: 260 seconds]
TheSeven has joined #linux-sunxi
tis_me has joined #linux-sunxi
swiftgeek has quit [Quit: WeeChat 2.9]
swiftgeek has joined #linux-sunxi
kaspter has quit [Ping timeout: 240 seconds]
kaspter has joined #linux-sunxi
jstein has joined #linux-sunxi
camus has joined #linux-sunxi
kaspter has quit [Ping timeout: 258 seconds]
camus is now known as kaspter
lurchi_ has joined #linux-sunxi
lurchi__ has quit [Ping timeout: 260 seconds]
camus has joined #linux-sunxi
tuxd3v has quit [Remote host closed the connection]
kaspter has quit [Ping timeout: 256 seconds]
camus is now known as kaspter
tis_me has quit [Quit: Leaving]
sunilmohan has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]
sunilmohan has joined #linux-sunxi
sunilmohan has joined #linux-sunxi
apritzel has joined #linux-sunxi
reinforce has joined #linux-sunxi
kaspter has quit [Ping timeout: 258 seconds]
camus has joined #linux-sunxi
camus is now known as kaspter
JohnDoe_71Rus has joined #linux-sunxi
apritzel has quit [Ping timeout: 265 seconds]
asdf28 has joined #linux-sunxi
camus has joined #linux-sunxi
kaspter has quit [Ping timeout: 260 seconds]
camus is now known as kaspter
cmeerw has joined #linux-sunxi
cmeerw has quit [Ping timeout: 272 seconds]
\\Mr_C\\ has quit [Quit: (Read error: Connection reset by beer)]
mripard has joined #linux-sunxi
tnovotny has joined #linux-sunxi
\\Mr_C\\ has joined #linux-sunxi
Asara has quit [Ping timeout: 240 seconds]
Asara has joined #linux-sunxi
mripard has quit [Read error: Connection reset by peer]
mripard has joined #linux-sunxi
mripard_ has joined #linux-sunxi
ldevulder_ has joined #linux-sunxi
ldevulder has quit [Ping timeout: 272 seconds]
faruk has joined #linux-sunxi
AneoX has joined #linux-sunxi
iyzsong has quit [Quit: ZNC 1.7.5 - https://znc.in]
iyzsong has joined #linux-sunxi
corecode has quit [Quit: ZNC - http://znc.in]
ldevulder_ is now known as ldevulder
corecode has joined #linux-sunxi
camus has joined #linux-sunxi
kaspter has quit [Ping timeout: 260 seconds]
camus is now known as kaspter
reinforce has quit [Remote host closed the connection]
reinforce has joined #linux-sunxi
AneoX has quit [Quit: Textual IRC Client: www.textualapp.com]
apritzel has joined #linux-sunxi
tuxillo has quit [Remote host closed the connection]
tuxillo has joined #linux-sunxi
matthias_bgg has joined #linux-sunxi
jonkerj has quit [Ping timeout: 246 seconds]
jonkerj has joined #linux-sunxi
camus has joined #linux-sunxi
kaspter has quit [Ping timeout: 260 seconds]
camus is now known as kaspter
victhor has joined #linux-sunxi
chewitt has quit [Quit: Zzz..]
chewitt has joined #linux-sunxi
matthias_bgg has quit [Ping timeout: 258 seconds]
Mangy_Dog has joined #linux-sunxi
rex_victor has quit [Quit: Bye]
febs has joined #linux-sunxi
matthias_bgg has joined #linux-sunxi
JohnDoe_71Rus has quit [Quit: KVIrc 5.0.1 Aria http://www.kvirc.net/]
lkcl has quit [Ping timeout: 256 seconds]
rex_victor has joined #linux-sunxi
Craphunzio has joined #linux-sunxi
<Craphunzio> Hello everyone. I am trying to work on a board I own, this is my first ever attempt to do anything similar.
<Craphunzio> The board is naed Sg.Gme.R3.95h5a/tw. It is not listed in the wiki and it is not an Android board. According to what I found on the wiki, that is the most common (if not the only?) type of board dealt with in this project, is that correct? My board is a retrogaming console, namely a "pandora's box".
lkcl has joined #linux-sunxi
<Craphunzio> That runs an A13 SoC and it has been "hacked" already. It runs the kernel and everything from a SD card and there are images that work fine by replacing the original one provided with the board. I would like to develop mine though so here I am searching for hints. Thanks to anybody.
chewitt has quit [Ping timeout: 240 seconds]
lurchi_ has quit [Ping timeout: 258 seconds]
kaspter has quit [Ping timeout: 258 seconds]
kaspter has joined #linux-sunxi
lurchi_ has joined #linux-sunxi
<plaes> Craphunzio: please start with the wiki page :)
kaspter has quit [Ping timeout: 265 seconds]
niceplaces has quit [Ping timeout: 256 seconds]
niceplace has joined #linux-sunxi
AneoX has joined #linux-sunxi
lurchi_ has quit [Ping timeout: 264 seconds]
lkcl has quit [Ping timeout: 240 seconds]
reinforce has quit [Quit: Leaving.]
JohnDoe_71Rus has joined #linux-sunxi
lkcl has joined #linux-sunxi
chewitt has joined #linux-sunxi
Nakaori has quit [Remote host closed the connection]
Nakaori has joined #linux-sunxi
tuxd3v has joined #linux-sunxi
kaspter has joined #linux-sunxi
lucascastro has joined #linux-sunxi
arti has quit [Ping timeout: 264 seconds]
arti has joined #linux-sunxi
AneoX has quit [Ping timeout: 264 seconds]
AneoX has joined #linux-sunxi
febs has quit [Remote host closed the connection]
<Craphunzio> plaes: you mean by creating a wiki page?
<diego71> Craphunzio: yes that would be nice
cmeerw has joined #linux-sunxi
<Craphunzio> diego71 (are u italian by any chance btw?) that sounds like hell of a lot of work :sweat; but let's try that :-D
AneoX has quit [Quit: Textual IRC Client: www.textualapp.com]
tnovotny has quit [Quit: Leaving]
<asdf28> :-> Craphunzio :->
<asdf28> i think plaes meant start reading the wiki page, not creating one
<asdf28> ?
<asdf28> because you were asking for info
<Craphunzio> asdf28 well I did but I'm still quite clueless. I am creating a new page though with the few infos I got
Craphunzio has quit [Ping timeout: 240 seconds]
lurchi_ has joined #linux-sunxi
Craphunzio has joined #linux-sunxi
<asdf28> a good starting point would be to look at how the images you already have were built
<asdf28> if they were built using a build system, you can look at that to see how it's done
<asdf28> as soon as you understand it, you can play around and exchange parts of it to your liking
<asdf28> a build system is a set of scripts that automates all the parts of creating an embedded linux system
<asdf28> which is very complicated, at least to me
<asdf28> if you're into retro gaming, you could have a look at lakka. you could download it and add your own board to the config files to build your own image
BorgCuba has joined #linux-sunxi
dev1990 has quit [Excess Flood]
dev1990 has joined #linux-sunxi
tuxd3v has quit [Ping timeout: 258 seconds]
Putti has quit [Remote host closed the connection]
selfbg has joined #linux-sunxi
Putti has joined #linux-sunxi
selfbg has quit [Client Quit]
\\Mr_C\\ has quit [Quit: (Read error: Connection reset by beer)]
selfbg has joined #linux-sunxi
selfbg has quit [Client Quit]
jelly has quit [Remote host closed the connection]
jelly-home has joined #linux-sunxi
Kwiboo has quit [Quit: .]
Kwiboo has joined #linux-sunxi
kaspter has quit [Quit: kaspter]
JohnDoe_71Rus has quit [Quit: KVIrc 5.0.1 Aria http://www.kvirc.net/]
Craphunzio has quit [Ping timeout: 256 seconds]
laurentC has joined #linux-sunxi
Craphunzio has joined #linux-sunxi
<Craphunzio> this is the picture I took of that chip. Please do share any experience you may have with anything alike. I am really puzzled.
<BorgCuba> Craphunzio, what has this to do with allwinner chios?
<BorgCuba> chio chips
<Craphunzio> BorgCuba that is another chip on the same PCB.
<Craphunzio> I mean, on the same PCB featuring an Allwinner A13 SoC.
<Craphunzio> is that non-relevant?
<BorgCuba> Its a FPGA
<BorgCuba> What kind of board is this?
<Craphunzio> That is so strange! I am trying to document that here: https://linux-sunxi.org/Sg.Gme.R3.95h5a_tw
<BorgCuba> It could be that the FPGA is used for HDMI output since the A13 does not have it (only a guess)
<BorgCuba> whats on that sd-card?
<BorgCuba> Craphunzio, but strange indeed
<BorgCuba> Craphunzio, where did you get it?
<Craphunzio> I just added a few informations some seconds ago. I got it second hands from a friend which ordered it from china. Those are mainly sold as "pandora's box" but they also have several other names such as "pandora's key"
<Craphunzio> using an fpga chip that is currently sold at 40+ USD on a board "boasting" an 1.2 USD System-on-chip would be quite absurd
<Craphunzio> I am afraid I cannot reach out for the SD card right now as it lies in the sleeping baby room (that's also my workshop lol).
<Craphunzio> I a seeing if I saved some part of it here on my laptop...
tuxd3v has joined #linux-sunxi
<Craphunzio> I have indeed! I actually found the whole boot partition of the system provided with the board. Would you be interested in taking a look?
<Craphunzio> (and I also have the "uBoot legacy uImage" of the alternative system.
<Craphunzio> I am still wondering what that is, if that's the kernel, or the bootloader, or both.
<BorgCuba> uBoot would be the bootloader
<BorgCuba> What do you want to do with it?
<BorgCuba> Have you hooked it up to your tv?
<Craphunzio> to a monitor, yes. Well I want to play retrogames on it :-D and learning plenty of things in the process.
<asdf28> finally, someone who wants to play retro games
<BorgCuba> Same for me :-)
<Craphunzio> The original system was very limited software-wise. It had a few bugs and a plethora of limitations - you could configure next to nothing
<BorgCuba> Craphunzio, I have an a13 device myself and I build a minimal rootfs with retroarch
<BorgCuba> but your challenge will be the fpga!
<Craphunzio> in the alternative one there's retroarch which can be tuned a lot. But I still find the overall thing bloated (the front-end is good looking but a loss of startup time)
<Craphunzio> BorgCuba <3 that's what I'm after
<BorgCuba> Craphunzio, I started downloading buildroot and added retroarch package as well as the mali drivers etc.
<Craphunzio> a modern version of retroarch (that one is from 2018 afaik) and configured to my taste
<BorgCuba> does the alt. version have a git repo or is it closed source?
<Craphunzio> well. I'm noob. I don't even know what "mali" is, yet :-(. For what matters retroarch I found this https://www.reddit.com/r/RetroArch/comments/fw9trz/i_added_retroarch_to_buildroot_so_you_can_build/ ) but looks like the project is quite dead
<BorgCuba> retroarch is not dead
<Craphunzio> the alt version is totally closed. The discussions about its development happened on a forum that has been taken off the internet and there's no reference in archive.org either to those posts
<Craphunzio> I meant that that project of "buildrooting retroarch" looks dead
<BorgCuba> 1st step would be to find the serial port on the pcb
<Craphunzio> https://github.com/retroroot-linux/retroroot here's the link to the github proect
<BorgCuba> and then I would start by preparing a bootable sd-card and see what happens
<Craphunzio> yup I tried searching for those pins and I have very good candidates, although I could not try them out yet since I'm waiting for my USB-to-Serial adapter from china
<Asara> ~/win 2
<Asara> sorry :(
<Craphunzio> that is why I was also trying to reverse-engineer the current SD cards, so to speak. Both use uboot and that's one of the few infos I was able to retrieve so far
<Craphunzio> oh Borgcuba I misread our post. you built a minimal rootfs not a minimal buildroot image.
<BorgCuba> thats the same I think
<Craphunzio> :facepalm:
<BorgCuba> although somebody may see that different
<BorgCuba> I think for a13 you can also go with mainline uboot und kernel
<asdf28> you should take a look at lakka, because this is essentially that. a minimal linux system with retroarch
<BorgCuba> a device that uses the a13 and might have readymade config files is the olinuxino a13 -> https://www.olimex.com/wiki/A13-OLinuXino
<BorgCuba> I also own that one
<BorgCuba> asdf28, thats true
<asdf28> https://github.com/libretro/Lakka-LibreELEC <-- this is the source code for lakka
<asdf28> you could have a look at the supported allwinner devices here: https://github.com/libretro/Lakka-LibreELEC/tree/master/projects/Allwinner/devices
<asdf28> and try to add your board, see how it was done for the others
<asdf28> the advantage is that most of the system is already configured, you only need to tinker with your board-specific settings
<asdf28> i built lakka for my A20 banana pi this way
lurchi_ is now known as lurchi__
<asdf28> the problem is that it doesn't work well with the newer mali and lima drivers, so it was useless in the end
<BorgCuba> asdf28, and you did not make a pull request -> I can see a20 there
<asdf28> yes i planned to add it some day, but it did not run well, so it makes no sense
<BorgCuba> but i recently read that lime should be working now?
<BorgCuba> For the a13 I used mali r4p0 in the end and it was working pretty good
<asdf28> lima is working, but it's not working well together with the mesa 3D drivers
<asdf28> maybe it's just me, but i could not get it working on my allwinner and amlogic boards
<BorgCuba> some ps1 games played mostly smooth
<asdf28> it's very choppy on my A20, and on my amlogic box all games are running too fast
<asdf28> performance (in raw fps) is very good on both devices
<asdf28> but it's not playable due to these bugs
<BorgCuba> strange
<Craphunzio> asdf28 thanks. Unfortunately the last time I tried it on a raspberry it took a very long time to boot and I am looking for something almost instantaneous. The original SD card system gets me up and playing in like 4 or 5 seconds. The alternative is a tad slower,
<asdf28> oh.. yes it could be the services that it's loading
<Craphunzio> I guess I should now read what mali and lima are.
<BorgCuba> asdf28, s905?
<asdf28> if you want to go for the fastest boot time, there might be better options
<asdf28> but i am fine wit it
<asdf28> yes, an s905x box
<Craphunzio> nice, Mali is an art Museum in Lima. Very good.
<asdf28> :->
<asdf28> mali is the graphics driver from ARM for most allwinner devices, lima is a free open source variant of that, it comes with the linux kernel
<Craphunzio> oh, thank you very much. And there are not good drivers then for the A13?
<asdf28> i don't have an A13 board, sorry. you'd have to look at which graphics chip it uses
<asdf28> but mostly, the stock driver (the one that comes with most pre-installed images) is the one that has the best performance
<BorgCuba> Craphunzio, I used the r4p0 which was working best from the drivers I tried
<asdf28> BorgCuba have you tried one of the newer ones?
<asdf28> how were they?
<BorgCuba> asdf28, no, I havent been doing anything like that recently
<asdf28> i was especially interested in the newer drivers that enable KMS mode
<asdf28> these drivers have the lowest input lag in my experience
<Craphunzio> in the while I found a pic of the whole board I took a few weeks ago. Here it is if you are curious https://linux-sunxi.org/File:Sg.Gme.R3.95h5a_tw_board.jpg
<Craphunzio> I wonder how to reverse-engineer the drivers used in the currently working images. I am trying with binwalk so far with not much succes
<asdf28> nice, it has a VGA port
<asdf28> why do you want to reverse engineer them? are they not open source?
<BorgCuba> maybe the fpga gets its configuration from that so8 chip and the fpga just takes the rgb signals from the a13 and turns them into hdmi output?
<BorgCuba> then it would be easy
<BorgCuba> "easy"
<BorgCuba> Craphunzio, do you use linux or windows or something else?
<Craphunzio> asdf28 nope they are not open source. More in detail: the original system is not open source. The alternative should be, but all its development has been discussed on a board that is not online anylonger.
<Craphunzio> I use Linux
<BorgCuba> thats good
<asdf28> oh, that sounds complicated
<Craphunzio> I am a system administrator. Unix-wise I'm good for what matters the userspace It's the embedded world my problem.
<BorgCuba> have you installed arm gcc?
<Craphunzio> well buildroot built its own cross compiler
<BorgCuba> well, if you use buildroot you dont need to
<BorgCuba> yes indeed
<Craphunzio> the problem is how the TURBOPHUCK fill those "make menuconfig" ncurses menu options :sweat:
<BorgCuba> have a look at this: board/olimex/a13_olinuxino/
<BorgCuba> from the 2020.02.8 buildroot
<BorgCuba> I would start from there
<BorgCuba> so: "make olimex_a13_olinuxino_defconfig"
<Craphunzio> so you think that would be similar enough. Thank you
<BorgCuba> but it uses a very old kernel 4.11
<Craphunzio> https://mega.nz/file/0UJmiBZR#1iDcQvWGD_25EvzKRT8f-ftNXzz1r6HoRoZipjFXqfQ this is the boot partition of the original OS in case you might kindly want to take a look.
<Craphunzio> the alt one contains much more files as long as the fex files to be used with VGA or HDMI or CGI output. Unfortunately I don't have them at hands and I can't get that SD card until tomorrow.
<BorgCuba> Craphunzio, there much more to configure
<BorgCuba> it seems like the old mali drivers gor removed and mainline-mali ist only for arm64
<BorgCuba> do "/" "MALI" in make menuconfig
<BorgCuba> maybe an older buildroot version works better. The kernel is stupidly old anyway
<Craphunzio> well maybe it doesn't have to be super modern to work well
<Craphunzio> after all it's quite an old SoC
<Craphunzio> Thank you for all the feedback guys. It has been very nice to have someone who listened and gave a direction. Going to bed. Have a good night, or whatever time is it in the part of the world you're living onto.
<asdf28> good night!
<asdf28> come back soon
lurchi__ is now known as lurchi_
<BorgCuba> Good night!
laurentC has quit [Remote host closed the connection]
<jernej> Apritzel: sorry, I took few days off Linux stuff
<jernej> not sure which way is better (regarding syscon)
<jernej> easy way out would be to introduce another emac compatible
<jernej> but since emac is completely the same, syscon with cells sound better
<apritzel> jernej: yeah, was thinking similarly
<apritzel> just not sure that syscon actually supports cells? Or at least if it would be accepted?
<apritzel> ah, there is prior art ;-)
<jernej> I think Rockchip uses cells?
<jernej> not sure
<apritzel> well, it's fairly easy: you just use of_property_read_u32_index(np, "syscon", 1) in the emac driver, and use that value as an offset into the regmap
Craphunzio has quit [Ping timeout: 240 seconds]
<apritzel> I think...
<apritzel> but it looks like just having a separate emac_variant_h616_emac2 with a differing syscon_field is a lot easier and cleaner
<apritzel> don't we need a new compatible anyway due to the internal PHY handling? Or is that identical to the H6?
<jernej> apritzel: handling is the same
<jernej> however, you can mark support for gigabit disabled
<apritzel> is that a generic property?
<jernej> no, capability associated with compatible in emac driver
<apritzel> so two compatibles for the H616, you mean?
<jernej> yeah
<apritzel> we could have one compatible, and if that is used, require an argument to the syscon phandle in this case, to use as an offset
<apritzel> jernej: I pushed a preview of v2 to https://github.com/apritzel/linux/commits/h616-v2-pre, with an AXP, syscon and USB fix
<jernej> USB now fully works?
<apritzel> though USB is still not working, compared many register already, against U-Boot and the BSP kernel, that looks the same
<apritzel> I mean it probes, and I see the root hubs, but then comes this USB cable bad? message as soon as I plug something in
<apritzel> works fine in U-Boot, though, with a patch equivalent to the Linux change
apritzel has quit [Ping timeout: 265 seconds]
lkcl has quit [Ping timeout: 240 seconds]
cmeerw has quit [Ping timeout: 264 seconds]
lkcl has joined #linux-sunxi
\\Mr_C\\ has joined #linux-sunxi
lkcl has quit [Ping timeout: 256 seconds]
niceplace has quit [Ping timeout: 246 seconds]
niceplace has joined #linux-sunxi
andy25225 has quit [Ping timeout: 256 seconds]
lkcl has joined #linux-sunxi
jstein has quit [Ping timeout: 240 seconds]
andy25225 has joined #linux-sunxi
jemk has quit [Remote host closed the connection]
jemk has joined #linux-sunxi
gumblex_ has quit [Quit: ZNC 1.8.1+deb1 - https://znc.in]
gumblex has joined #linux-sunxi
BorgCuba has quit [Quit: Leaving]