narmstrong changed the topic of #linux-amlogic to: Amlogic mainline kernel development discussion - our wiki http://linux-meson.com/ - ml linux-amlogic@lists.infradead.org - official channel moved from Freenode - publicly logged on https://libera.irclog.whitequark.org/linux-amlogic
KyleS has quit [Quit: Connection closed for inactivity]
vagrantc has quit [Ping timeout: 240 seconds]
vagrantc has joined #linux-amlogic
chewitt has quit [Quit: Zzz..]
chewitt has joined #linux-amlogic
buzzmarshall has quit [Quit: Konversation terminated!]
vagrantc has quit [Quit: leaving]
Karyon_ is now known as Karyon
libera- has joined #linux-amlogic
buzzmarshall has joined #linux-amlogic
xdarklight has quit [Ping timeout: 268 seconds]
libera- is now known as xdarklight
xdarklight has joined #linux-amlogic
xdarklight has quit [Changing host]
ungeskriptet[m] has joined #linux-amlogic
warpme___ has joined #linux-amlogic
<ungeskriptet[m]> Hi guys,
<ungeskriptet[m]> I have a TrekStor tablet (https://wiki.postmarketos.org/wiki/TrekStor_SurfTab_ventos_7.0_HD_(mid-g30ref)) with an Amlogic AML8726-MX SoC which I am intrested in getting mainline Linux to run on. I wrote a small dts (based on meson6-atv1200.dts) which *should* give me a console via UART, however I only getting garbled output which reacts to my keypresses - nothing useful tho. (Here's the dts:
<ungeskriptet[m]> https://gist.github.com/ungeskriptet/25fd7f3d9e414c0f77ed68d2b57b7ba5). The commands I use to boot the kernel in uboot are: `mmc rescan 0; fatload mmc 0 0x82000000 uImage; fatload mmc 0 0x82000000 uInitrd` and `bootm 0x82000000 0x83000000`. The dts is appended to the kernel, because otherwise I get no output at all.
<xdarklight> ungeskriptet[m]: I suggest booting with the earlycon kernel cmdline argument to see if at least that works until the full-blown UART driver takes over
<ungeskriptet[m]> s/I have a TrekStor tablet (https://wiki.postmarketos.org/wiki/TrekStor_SurfTab_ventos_7.0_HD_(mid-g30ref)) with an Amlogic AML8726-MX SoC which I am intrested in getting mainline Linux to run on. I wrote a small dts (based on meson6-atv1200.dts) which *should* give me a console via UART, however I only getting garbled output which reacts to my keypresses - nothing useful tho. (Here's the dts:
<ungeskriptet[m]> Amlogic AML8726-MX SoC which I am intrested in getting mainline Linux to run on. I wrote a small dts (based on meson6-atv1200.dts) which _should_ give me a console via UART, however I only getting garbled output which reacts to my keypresses - nothing useful tho. (Here's the dts: https://gist.github.com/ungeskriptet/25fd7f3d9e414c0f77ed68d2b57b7ba5). The commands I use to boot the kernel in uboot are: `mmc rescan 0; fatload mmc
<ungeskriptet[m]> 0 0x82000000 uImage; fatload mmc 0 0x82000000 uInitrd`, `setenv bootargs "console=ttyAML0,115200"` and `bootm 0x82000000 0x83000000`. The dts is appended to the kernel, because otherwise I get no output at all./
<ungeskriptet[m]> https://gist.github.com/ungeskriptet/25fd7f3d9e414c0f77ed68d2b57b7ba5). The commands I use to boot the kernel in uboot are: `mmc rescan 0; fatload mmc 0 0x82000000 uImage; fatload mmc 0 0x82000000 uInitrd` and `bootm 0x82000000 0x83000000`. The dts is appended to the kernel, because otherwise I get no output at all./I have a TrekStor tablet (https://wiki.postmarketos.org/wiki/TrekStor_SurfTab_ventos_7.0_HD_(mid-g30ref)) with an
<xdarklight> ungeskriptet[m]: also the .dtb you linked sets 2GiB of RAM while the wiki page only mentions 1GiB... that seems problematic
<xdarklight> ungeskriptet[m]: and finally: I think it's been years since someone last tried making Meson6 boot - so status is "unknown" at best
<ungeskriptet[m]> Yep earlycon did the trick 👍️
<ungeskriptet[m]> Hmm it seems that it gets garbled again after the driver loads? https://bpa.st/YVAA
<ungeskriptet[m]> About the dts: Should I use `reg = <0x40000000 0x04000000>;` instead
<xdarklight> ungeskriptet[m]: yep, reg = <0x40000000 0x40000000>; is what we use on other 1GiB boards
<xdarklight> ungeskriptet[m]: if it's getting garbled again then the most likely cause is that one of the clocks (which are currently hardcoded in meson6.dtsi because there's no clock driver) is wrong or the UART driver has some assumptions about the UART IP which is not true on Meson6
ChanServ has quit [shutting down]
ChanServ has joined #linux-amlogic
vagrantc has joined #linux-amlogic
warpme___ has quit [Quit: Connection closed for inactivity]