ChanServ changed the topic of #aarch64-laptops to: Linux support for AArch64 Laptops (Chrome OS Trogdor Devices - Asus NovaGo TP370QL - HP Envy x2 - Lenovo Mixx 630 - Lenovo Yoga C630 - Lenovo ThinkPad X13s - and various other snapdragon laptops) - https://oftc.irclog.whitequark.org/aarch64-laptops
hightower2 has quit [Ping timeout: 480 seconds]
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
mbuhl has quit [Ping timeout: 480 seconds]
mbuhl has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
nashpa has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
Ariadne is now known as Ariadne-ic
chrisl has joined #aarch64-laptops
Ariadne-ic is now known as Ariadne
Ariadne is now known as Ariadne-ic
Ariadne-ic has quit []
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
tobhe_ has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
tobhe has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
alpernebbi has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
alpernebbi has joined #aarch64-laptops
<valpackett>
uh oh does the boot entry dtb not override dtbloader? just had to recover from a bad kernel update by booting another thing
<valpackett>
since my known working backup entry wouldn't actually work
<valpackett>
and it was set up to override devicetree with a known working one..
<valpackett>
(talking about systemd-boot of course)
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
hexdump01 has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<valpackett>
or was it just not finding the override dtb because i put it into the root of the esp and not under dtbs..
<travmurav[m]>
Val Packett: boot entry should always override the dtbloader one in sd-boot, it just updates the configuration table
<travmurav[m]>
but I'd assume sd-boot would throw an error if the file is notthere
chrisl has joined #aarch64-laptops
<valpackett>
hmm it's probably not this then. just some kind of cursed issue that makes my backup entry break too when i break the main install 0.o
<travmurav[m]>
modules? xD
<valpackett>
the breakage is not being able to mount rootfs because pcie/usb/etc attachment is somehow blocked on some other dtb node..
<travmurav[m]>
but yeah checked sd-boot, it just overrides the config table (but for some reason keeps the old pointer, didn't quickly see where it's used) so it should work properly
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<valpackett>
so the broken kernel was after both rebasing and adding a bunch of various patches.. removing patches didn't help..
Werner[m] has joined #aarch64-laptops
<valpackett>
but the upstream changes for the last 2 days include some PCI stuff, hmm
chrisl has joined #aarch64-laptops
<valpackett>
yeaaaah i think linux-next is busted again. what's this breakage streak ugh
<steev>
that happens with next
<steev>
that's why when people are working on things they tend to stick to a specific day with -next and not move from it
<valpackett>
i mean i am kinda doing qa for next on purpose heh
<valpackett>
but display brightness being screwed and firmware not loading were okay to deal with and i fixed them easily
<valpackett>
while not booting at all now after all that is a bit much already >_<
<icecream95>
robclark: Can you take over with dealing with the ANGLE issue? At the moment I don't have the energy to fight with the ANGLE build system or with signing CLAs or whatever else...
mbuhl has quit [Remote host closed the connection]
chrisl has quit [Ping timeout: 480 seconds]
mbuhl has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
dliviu has joined #aarch64-laptops
jglathe_ has joined #aarch64-laptops
jglathe_ has quit [Killed (charon.oftc.net (Nick collision (new)))]
jglathe_ has joined #aarch64-laptops
jglathe__ has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
jglathe_volterra has quit [Ping timeout: 480 seconds]
jglathe_angrybox has quit [Ping timeout: 480 seconds]
<robclark>
icecream95: maybe.. not sure about the CLA situation or if it is already on list of approved projects..
chrisl has joined #aarch64-laptops
<robclark>
I'll ping some of my former teammates, since I guess this will eventually show up in CrOS