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)
hail_eris has joined #aarch64-laptops
hail_eris has left #aarch64-laptops [#aarch64-laptops]
hail_eris has joined #aarch64-laptops
alpernebbi has joined #aarch64-laptops
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
<steev>
bamse: https://github.com/steev/linux/commits/linux-v5.19-rc3-tests is my 5.19 with the c630 stuff and your flex 5g stuff and "a few" other misc patches - haven't pulled in the ones qzed asked me to test yet, but i wanted to push it so i can build my cd here
<steev>
Added bonus is that it includes the patch that you asked me to submit a long time ago :/ I’ll try to get to that this week
mani_s has joined #aarch64-laptops
<bamse>
steev: little bit odd that they are shipping a gen2 soon...but looks like a nice device
<bamse>
hmm, seems i can buy it on the german site...althoguh my german is a little bit rusty
<bamse>
steev: invited mani_s here as well, he's been poking at the debian installer to get it up to snuff for the x13s
<bamse>
and now it's tomorrow already, time to call it a yesterday...
<steev>
yarp, and cool, i look forward to him showing up )
<mani_s>
steev, I just got the laptop last week and been trying to get the installer work with devicetree (not using acpi tables)
<steev>
oh, interesting
<steev>
i think part of not using devicetree was so that it wasn't device specific, using acpi tables allows us to use the 1 installer across all the devices (in theory)
<mani_s>
steev, right but we still need to use devicetree anyway for the debian kernel. So I thought why not for the installer also
<mani_s>
plus bamse and me are thinking that it will allow us to have more functionalities compared to acpi
<steev>
if the installer were to use grub, it would be possible, while debian doesn't have the patch that ubuntu has, afaik, grub does support the devicetree directive, so you could modify the entries to point to each different device tree - but i don't believe it does
<steev>
it does use grub, i mean
<mani_s>
steev, I tried the ubuntu installer and yes, it has the grub support to boot using devicetree
<steev>
right, but they use... ubiquity? i think? xnox can correct me if i'm wrong
<steev>
debian's grub supports device tree too, it just doesn't have the patch afaik yet
<mani_s>
yeah they were
<steev>
the patch that adds that entry
<mani_s>
hmm. Now I'm building the debian-installer. Maybe we need to add that patch in aarch64-laptops
<steev>
right, it's supported, but afaik, there is no way to add the option like that patch does automatically
<steev>
xnox's patch, i mean
<mani_s>
hmm
<steev>
like, you can just edit the grub config at boot time and add it, and it'll use it (though we use dtbloader to use the chid and then we have the python3 script to install the dtbs to /boot/efi/dtbs or whatever it is (and i wrote a hook but i don't believe it's in the repo)
<steev>
it's also not a great hook because it copies them every time you do anything with kernels
<mani_s>
steev, yeah, that's for not hardcoding the devicetree entry in grub I believe
<mani_s>
eventually that logic should also be part of the installer
<steev>
there is/was another reason, but i can't recall - i blame robclark, since he wrote the dtbloader thingie
<steev>
but maybe it was just not hardcoding
<mani_s>
well leif wrote it and robclark improved it ;)
<steev>
all above my paygrade, i could never figure that edk2 stuff out at all
<mani_s>
:)
<steev>
i'm just smart enough to be dangerous
broonie_ has joined #aarch64-laptops
rfs613- has joined #aarch64-laptops
leezu has quit [synthon.oftc.net larich.oftc.net]
leezu has joined #aarch64-laptops
iivanov has joined #aarch64-laptops
matthias_bgg has joined #aarch64-laptops
falk689 has quit [Remote host closed the connection]
falk689 has joined #aarch64-laptops
klardotsh has quit [Remote host closed the connection]
broonie_ is now known as broonie
matthias_bgg has quit [Ping timeout: 480 seconds]
matthias_bgg has joined #aarch64-laptops
matthias_bgg has quit [Ping timeout: 480 seconds]
matthias_bgg has joined #aarch64-laptops
rfs613- is now known as rfs613
matthias_bgg has quit []
jhovold has quit [Ping timeout: 480 seconds]
iivanov has quit []
<steev>
alright, got the mail, the x13s should be on its way/here soon
<bamse>
nice!
klardotsh has joined #aarch64-laptops
alpernebbi has quit [charon.oftc.net helix.oftc.net]
hexdump01 has quit [charon.oftc.net liquid.oftc.net]
jonasbits has quit [charon.oftc.net liquid.oftc.net]
ajhalaney[m] has quit [charon.oftc.net liquid.oftc.net]
djakov has quit [charon.oftc.net liquid.oftc.net]
ungeskriptet[m] has quit [charon.oftc.net liquid.oftc.net]
djakov has joined #aarch64-laptops
hexdump01 has joined #aarch64-laptops
ungeskriptet[m] has joined #aarch64-laptops
jonasbits has joined #aarch64-laptops
ajhalaney[m] has joined #aarch64-laptops
abelvesa has joined #aarch64-laptops
qzed has joined #aarch64-laptops
travmurav[m] has joined #aarch64-laptops
alpernebbi has joined #aarch64-laptops
klardotsh has quit [Ping timeout: 480 seconds]
<Dylanger>
<hexdump0815> "Dylanger: thx for the config" <- Is there anything I can try to get jump start this?
<qzed>
is `cpu cpu4: Voltage update failed freq=3072000` a known issue for the sc8180x?
<qzed>
also there's one CPU core that seems to have a constant high usage
<hail_eris>
Dylanger: which kernel did you use for the dts? 5.15 doesn't have tomato, it's in the 5.10 branch
<Dylanger>
Currently trying with 5.18
<Dylanger>
Yeah I'm currently trying to add cherry + tomato DTS myself
<Dylanger>
Into mainline, oh wait, tomato is already in 5.10 mainline?
<hail_eris>
I mean it's in Chromium's fork
klardotsh has joined #aarch64-laptops
<hail_eris>
Try with the latest kernel (5.19-rc3), i'm able to at least build the dtbs by copying over chromium 5.10's arch/arm64/boot/dts/mediatek if I copy over mt6359.dtsi mt8192* mt8195*, then modify Makefile to include only those files. I doubt it'll work without a lot of hacking around, though. May be more fruitful to first boot chromium's fork before trying.