<das_coach>
oh, and i think, as i only have u-boot scripts and kernel + rootfs on the sd card that the preinstalled u-boot is used/"hijacked" for booting other distros from sd card
<chewitt>
sei610 and odroid-c4 are also SM1 devices
<das_coach>
yeah, i think at the moment my problem is more the u-boot/kernel format part
<chewitt>
there is a known issue with ethernet on most of the box devices where we have to force 100-BaseT to get it up/stable, GB is borked
<chewitt>
but that's something you can play with
<chewitt>
I wouldn't fiddle with u-boot
<das_coach>
i think i've got that problem, at least i thought it had gb lan, but the dtb for it didn't work, so i used the one without it
<das_coach>
no, i won't fiddle with u-boot if i don't have to
<das_coach>
and now that i know that it's "only" the scripts that i have to modify (if at all, for the moment i'm playing around by just replacing the kernel + system)
<das_coach>
i certainly won't^^ i want to leave the internal preflashed android as is
<chewitt>
vendor u-boot switches to some kind of HDR ready mode and this isn't handled somewhere in the drm driver yet in mainline kernel
<chewitt>
so the current scripts chain-load mainline u-boot from vendor, and since mainline u-boot doesn't support HDR stuff yet, it works around the issue
<das_coach>
thx=) i'd be happy if i got my kernel to boot in the first place=P but not having a uart adapter is making it hard to locate the issue^^
<das_coach>
so i would try out the a95xf3-air, right?
<chewitt>
or x96-air
<das_coach>
i honestly don't know, like i said, i'd be happy to get my kernel booting, i'll take care of network etc afterwards=)
<das_coach>
are those dts files compatible with the mainline 5.7 sources?
<das_coach>
and what are the dtsi files for? are they like additional layers?
<chewitt>
the 'amlogic' branch in my repo is 5.7.0
<chewitt>
dtsi is something shared between multiple dts
<chewitt>
dts can import dtsi
<chewitt>
dts can also import another dts, but that's considered poor ettiquette, it should really be dtsi
<das_coach>
ah, ok, makes sense, like common things among the boards
<chewitt>
exactly
<das_coach>
so i'd grab the meson-sm1.dtsi + 2-3 of the dts files that i think could be similar (meson-sm1-a95xf3-air.dts and meson-sm1-x96-air.dts)
<das_coach>
?
<chewitt>
nope
<chewitt>
when you compile the kernel, it takes all the required pieces and creates a 'dtb' that contains them all
<das_coach>
yes, i mean the files that i'll add to the kernel before compiling
<chewitt>
I would simply point buildroot at my kernel source, as there's a ton of additional patches added, it's a lot more than just the extra dts files
<das_coach>
i'd like to stay as vanilla as possible (for now, once i found all the kinks and quirks i'll start looking for patches and probably end up with some other kernel sources)
<das_coach>
for now, learning the basics =)
<chewitt>
there are some things you need in my branch, so start with something known-working, then later you can revert to a more 'pure' state
<chewitt>
note: most of the extra stuff in my branch is already merged/queued for 5.8, so it's most backports
<chewitt>
anything with FROMGIT is merged, FROMLIST is publicly submitted, only WIP is .. in progress
<das_coach>
nice, you're upstreaming your work? thank you very much for your effort, you're helping a lot of people with that
<das_coach>
(especially those who don't want to use blobs for their gpu or outdated software because of IPs^^)
<das_coach>
and if it's being upstreamed, i'll consider it vanilla-ish enough^^
<das_coach>
so you're an active/paid (kernel-) developer or doing this in your free time?
<das_coach>
(or maybe for some manufacturers to get their products supported, etc.?)
<das_coach>
(if one may ask)
<das_coach>
and do you have any idea why my buildroot stopped producing separate kernels? i only get my rootfs in the target output folder=( the option for the kernel is activated. i'd just start from scratch, but the initial build always takes forever and idk how to "reset" BR
<chewitt>
I'm a hobbyist, but my collection of upstreamed one-liner patches and device-trees is slowly increasing
<chewitt>
and I'm a bit monotheistic with Linux .. I understand the packaging for LE well, but I'm not familiar with buildroot and others
<chewitt>
but all build-systems do a similar thing
<chewitt>
take a designated kernel source, apply some patches, build a kernel
<chewitt>
in my case the patches are in the kernel source as commits, so you likely don't need more patches
<das_coach>
that is awesome=) but i guess your work is somehow related to this or how did you get into that?
<das_coach>
BR only created a kernel for me in the output directory if i link my initrd into it (i'd like to avoid that). does it assume i'll copy it out of the build-subfolder or is there something weird?
<chewitt>
my work is totally unrelated, although I do end up fiddling with linux things a lot
<das_coach>
well, same for me, but i never found myself fiddling with embedded kernel development xD
<das_coach>
(IT admin here)
<das_coach>
so you're learned that on your own? you definitely have my highest respect for that=)
<das_coach>
btw, shuold i use your master branch if i end up using your repo?
<chewitt>
no, master is 5.7
<chewitt>
(vanilla)
<chewitt>
amlogic is the branch to use
<chewitt>
I moved to a country with shit tv, wanted BBC content, ended up with a mk1 apple tv to play media recorded in the UK, and had to jailbreak it to add more codecs, then discovered you could put XBMC on it, and then discovered this minimal linux thing called openelec that ran xbmc better than the AppleOS
<chewitt>
and here we are a decade later .. and i'm still fiddling with stuff
<das_coach>
hmmm, if i try using your gh as kernel repo, it tries to download headers from buildroot as tar.gz and fails, as they're .xz on the server:-/ any idea?
<das_coach>
yeah, i started with xbmc on my original xbox and came across openelec when i got my first raspi
<das_coach>
oh, and is there a need for pics of PCBs? opened my box today to check for a serial port and took some pictures of everything that looked important=)
<das_coach>
(i mean somewhere, meson project, LE, etc.?)
<das_coach>
wohooo, it's building your kernel from GH, that's progress for me xD
<das_coach>
but wtf is my kernel about 350mb in size?^^ i've deactivated the linked initrd...
<das_coach>
aha, vmlinux vs image in buildroot=)
heldchen has quit [Ping timeout: 272 seconds]
chbmb has joined #libreelec
<chewitt>
if you have pics of the board I can tell you what wifi/bt bits it has
<chewitt>
and if you tell me which of the current device-trees work (or are least-worst) I can add a dts for the box
heldchen has joined #libreelec
<chewitt>
looks like the box is 10/100 ethernet on all models
<chewitt>
(doing some Google research)
<chewitt>
so the sei610 dts is worth testing, as this uses internal phy
<chewitt>
the a95x-f3 and x96-air are external phy
<chewitt>
mind you, looks like there's at leat two or three manufacturers peddling t95-max boxes, so what's inside could be a gamble :)
speeedy has joined #libreelec
<das_coach>
@chewitt i sent you a link to the pics via a direct message, the dtb i was using so far (under coreelec) is called "sm1_s905x3_4g.dtb" (like i said, i am unfortunately not that experienced in this whole thing yet, so that's unfortunately all the info i have for now
<das_coach>
but as soon as i get my uart adapter, i'll see what's going on and be more helpful hopefully
<das_coach>
ps: it seems to be loading something now, instead of freezing it is stuck in a boot loop, so without messages i guess this is a dead end for me now
_whitelogger has joined #libreelec
das_coach has quit [Remote host closed the connection]
lacrimosa has joined #libreelec
RedSoxFan07 has joined #libreelec
speeedy has quit [Remote host closed the connection]
RedSoxFan07 has quit [Quit: RedSoxFan07]
lacrimosa has quit [Quit: Konversation terminated!]
buzzmarshall has quit [Remote host closed the connection]