ChanServ changed the topic of #aarch64-laptops to: Linux support for AArch64 Laptops (Asus NovaGo TP370QL - HP Envy x2 - Lenovo Mixx 630 - Lenovo Yoga C630)
<flowriser>
Ok so the EFI trick worked and I was able to boot the kernel; the problem is that it writes to fast for me to read O.o
<flowriser>
and when trying to supply the device tree it would simply error out; I have the dtb and the dts file but I don't know how to supply them to the kernel
<flowriser>
I tried `Image dtb=<name>.dtb`
Lucanis has quit [Read error: Connection reset by peer]
Lucanis has joined #aarch64-laptops
Lucanis has quit [Remote host closed the connection]
Lucanis has joined #aarch64-laptops
<amstan>
alyssa: "special", lol, they wouldn't be the first ones
<amstan>
my hobby is noticing how many downstream uart drivers a recent project i work on has had
sabt has joined #aarch64-laptops
sabt has quit [Excess Flood]
sabt has joined #aarch64-laptops
sabt has quit [Excess Flood]
sabt has joined #aarch64-laptops
sabt has left #aarch64-laptops [#aarch64-laptops]
skiesblue has joined #aarch64-laptops
ebdoweekly has joined #aarch64-laptops
ebdoweekly has quit [Excess Flood]
skiesblue has quit []
gomaat has joined #aarch64-laptops
gomaat has quit [Ping timeout: 480 seconds]
paper has joined #aarch64-laptops
paper has quit [Excess Flood]
paper has joined #aarch64-laptops
paper has quit [Remote host closed the connection]
<alyssa>
amstan: giggle
<alyssa>
I can't tell if Rockchip is legitimately less special (in a good way) than MTK and Amlogic, or mmind00 is just so good at what he does that it seems that way....
<amstan>
it was not rockchip
<alyssa>
Yeah okay.
<flowriser>
I am wondering if I am compiling the kernel with the right toolchain; What toolchain are you all using?
<alyssa>
gcc?
<flowriser>
I am using: ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu-
<flowriser>
And aarch64-linux-gnu comes from gcc-aarch64-linux-gnu, is this ok? alyssa, simply trying to boot anything at this point :D
<robclark>
yeah, that should be fine.. iirc kernel will tell you if you are using a too-old version of gcc.. I think min supported version now is v5.x? You'd have to try pretty hard to find something old enough to have a problem
<flowriser>
robclark, thanks :D
<robclark>
np
<steev>
flowriser: arm64 is *not* like x86_64, it's not generic enough, until/unless someone writes a dts for your device, it's unlikely to get very far in the boot process
<steev>
it's not your compiler, it's that the kernel doesn't know enough about your device to boot it properly
<alyssa>
to be fair, x86_64 is not magically more generic, just that people seem to think UEFI is optional on arm64 unlike x86_64...
<steev>
it's less about acpi and more about generic support for most devices, whereas arm* needs device tree bindings to tell the kernel what it has
<steev>
s/acpi/efi
<alyssa>
also ACPI i guess
<steev>
alyssa: is 3.1 the highest opengl that the mali g31 supports? i'm trying to figure out why chromium looks like garbage on my radxa zero here
<alyssa>
it's the highest panfrost supports
<alyssa>
arm doesn't support any opengl on any mali..