<xdarklight>
are you using a .dtb which is configured for 512MB RAM?
<TheAssassin>
nope, reboot didn't fix the issue
<TheAssassin>
right now I'm using that image as-is
<TheAssassin>
i don#t seem to get any messages over the serial interface either... neither using 9600 baud nor 115200 (the two most common ones I had to use in other hardware)
<xdarklight>
115200 is used on virtually all Amlogic boards
<xdarklight>
you have connected the device's RX to your adapters TX and your device's TX to your adapter's RX, right?
<TheAssassin>
I just tried again with cu instead of minicom, et voila... all this embedded hardware stuf f:D
<TheAssassin>
yeah well, the kernel output stops after [ 16.143100@3] systemd[1]: Started Create Static Device Nodes in /dev.
<TheAssassin>
might really be the dtb img...
<TheAssassin>
suddenly, we have a login over serial ... strange stuff, but a lot farther than I got before
<TheAssassin>
can't get any characters sent over serial tho
<xdarklight>
I'd reboot and see if I can get into u-boots command prompt
<TheAssassin>
xdarklight: so, that image I linked to above doesn't have a dtb.img on its BOOT, but a lot of them in directories
<TheAssassin>
I'm trying to understand this dtb.img stuff -- any ideas how it behaves when there's no dtb image in the dir?
<xdarklight>
typically u-boot decides which dtb to load
<TheAssassin>
okay
<xdarklight>
you should see which one when you reboot and watch the output from before Linux is started
<TheAssassin>
"getting into the command prompt" what do I have to do over serial when it boots
<TheAssassin>
kk
<xdarklight>
typically pressing enter or space (keep hammering on these keys ;)) will make it enter the prompt
<narmstrong>
Ah yeah so you uses Lima then ! Even cooler !
<xdarklight>
I'm trying on-screen rendering with my hacked CVBS output code on Meson8m2 now
<narmstrong>
I’m sure it will work perfectly :-D
<xdarklight>
narmstrong: https://abload.de/img/vlcsnap-2018-12-08-16tmd7q.png that's the "fbv" output of some some random PAL test image I found online. colors are way off, but I didn't expect more from my HACK :)
<narmstrong>
Hehe you are not so far from something working !
<xdarklight>
it's a bit strange because I'm now sure that my Meson8m2 board uses OSD2 for CVBS video output
<xdarklight>
could not open drm device
<xdarklight>
:(
<narmstrong>
Hmm it should be the same, or osd1 is broken on meson8m2
<narmstrong>
xdarklight: yeah you need to force the device since lima probes first
<xdarklight>
ah
<xdarklight>
drmModeGetResources failed: Operation not supported
<dswizly>
i was wondering if i could get a little guidance with a T95Z Max s912 3/32 box i got :x
<ccaione>
it really depends on the kind of guidance you need
<dswizly>
i had an m8s pro+ and easily flashed a tvstock rom with twrp, but i cant find a flashable zip of decent rom for the t95z.. i looked into atvxperience but they both require using the usb burn tool or a burn card
<dswizly>
wasnt too sure where to ask for help so i looked up amlogic on freenode lol
<ccaione>
yeah, this is a channel for mainline kernel dev
<dswizly>
thats what i figured, just checking
<dswizly>
thanks for responding (:
<dswizly>
and thanks to everyone doing development on the kernel for these devices
dswizly has quit [Remote host closed the connection]
<xdarklight>
I don't have much time left today, but what you need to do is:
<xdarklight>
- build your own kernel, if you want the most features (this also means you'll have the highest chance to hit bugs - which is good because then we can fix them ;) ) then I suggest you build a kernel using https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/
<xdarklight>
Armbian probably has an "uInitrd" instead of "rootfs.cpio.uboot" - different name, same thing
<xdarklight>
(I've never tried the Armbian initramfs though, your mileage may vary)
<xdarklight>
in the "setenv bootargs" command you can also pass your SD card partition to the kernel so it'll use that as rootfs, for example: setenv bootargs "console=ttyAML0,115200 root=/dev/mmcblk1p2"
adema_ has quit [Ping timeout: 264 seconds]
<xdarklight>
expected result with linux-next and on top of that the updated .dts from above: SD card works, all USB ports are working (if the USB device is plugged in *prior* to booting Linux), all four CPU cores come up and CPU frequency scaling works, Ethernet works
adema has joined #linux-amlogic
<TheAssassin>
xdarklight: kk, will do as soon as Ifind time (might be tomorrow, but I got the instructions :))