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)
<steev>
alrigh, based on 20221118 - pushed out the audio bits, but i'm not sure what i'm missing config-wise,
<steev>
srinik: ^ (and note that with that defconfig both tx/rx macros do get enabled)
hexdump0815 has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
jhovold has joined #aarch64-laptops
SSJ_GZ has joined #aarch64-laptops
SSJ_GZ has quit [Remote host closed the connection]
SSJ_GZ has joined #aarch64-laptops
matthias_bgg has joined #aarch64-laptops
<jenneron[m]>
mothenjoyer69@ I've found that my galaxy book s artifacts only when modem is enabled (maybe I will catch it later with disabled modem?) at least with disabled modem it now seems fine
iivanov has joined #aarch64-laptops
<jenneron[m]>
definitely a hardware issue because it happens in both Linux and Windows
<jenneron[m]>
I'm still not sure whether it could be caused by efforts of porting Linux
matthias_bgg has quit [Ping timeout: 480 seconds]
Guest2337 has joined #aarch64-laptops
matthias_bgg has joined #aarch64-laptops
Guest2337 has quit [Quit: Guest2337]
alpernebbi_ has joined #aarch64-laptops
alpernebbi has quit [Read error: Connection reset by peer]
iivanov has quit [Remote host closed the connection]
iivanov has joined #aarch64-laptops
leezu has quit [Quit: WeeChat 3.0]
* gwolf
agrees with steev -- I also love my C630 :-)
<gwolf>
Cannot contribute much to the channel besides loving the machine ;-)
kettenis_ has quit [Remote host closed the connection]
<mani_s>
steev, johan fixed the nvme timeout issue
<mani_s>
you just need to add "dma-coherent" property to the pcie node in dts
<mani_s>
this is present in downstream but somehow we didn't use it in upstream for any SoCs
<steev>
hm, most of the other boards put it into the dtsi, so i did that... but i can't reboot a bunch to test yet
ajhalaney[m] has quit [Quit: Client limit exceeded: 20000]
<calebccff>
I managed to get some signs of life on the C630 using the same kernel we run on the SDM845 phones, it flashes the kernel logs for about a second with efifb and then goes blank with the kb backlight on
<calebccff>
is there a mechanism to dump logs from this thing or get serial out?
<jenneron[m]>
calebccff: maybe too obvious suggestion, but make sure all panel-related configs are enabled, check CONFIG_DRM_TI_SN65DSI86 and CONFIG_DRM_PANEL_EDP
<calebccff>
no... not too obvious at all...
* calebccff
sheepishly rebuilds kernel
<jenneron[m]>
for taking logs in such cases I usually connect my phone to USB and use SSH, but that works only when device is booted into rootfs
<calebccff>
cheers, I guess I'll go for something similar here
<jenneron[m]>
this device is armv7, so change `--format="arm-efi"` and rename bootarm.efi > bootaa64.efi
<jenneron[m]>
also, this device package does not install grub modules related to efi gop because it is broken on surface rt
<jenneron[m]>
you can use this instead: grub-mkimage --prefix="/grub" --output="bootaa64.efi" --format="arm64-efi" --compression="xz" all_video disk efi_gop fat gzio iso9660 linux normal part_gpt part_msdos
<calebccff>
I've been using device-tablet-x64uefi as a base and modifying it for aarch64 lol
<jenneron[m]>
surface rt example is a bit more appropriate because it uses dtb, but that one is useful too
<steev>
android on the c630... why do you make santa sad
<jenneron[m]>
android?
<calebccff>
steev: pmOS is based on Alpine Linux
<steev>
oh
<steev>
i always think it's a custom android for some reason
<calebccff>
we scrap all the proprietary android stuff and run mainline + mobile optimised userspace