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
<macc24>
someone on lm-sensors github reached out to ite about the datasheet
<JensGlathe[m]>
nice
<JensGlathe[m]>
how many pages 🤯
<macc24>
more pages = more documented
<macc24>
i just wish there was a way to put all those register addresses into ghidra and have it figure out all the references to them
<macc24>
tho i think i found "smbus setup thingy at the 0x5b device address for some reason" function at 0x700
<macc24>
* tho i think i found "smbus setup thingy for both 0x5b and 0xf6 addresses" function at 0x700
<macc24>
this might actually be getting somewhere
<travmurav[m]>
is this risc-v or the 8051 based one?
<travmurav[m]>
if it's rv then maybe not too hard to decompile, if 8051 then probably more suffering
<macc24>
it's 8051
<travmurav[m]>
but well, in the end it'd be mostly firmware defined anwyay
<travmurav[m]>
f
<macc24>
it actually has hardware support for LPC which goes unused
<travmurav[m]>
I think 8051 has memory banking which is pain so I gave up very quickly
<travmurav[m]>
well I'd hope you'd not use lpc (iirc it's just ISA?) on modern platforms xD
<macc24>
afaik it's still standard to use
<travmurav[m]>
I mean I don't think it makes sense to implement ISA on something like arm
<macc24>
which is probably why they used smbus
SpieringsAE has joined #aarch64-laptops
jhovold has joined #aarch64-laptops
hipboi has joined #aarch64-laptops
hipboi has quit []
_dbalan has joined #aarch64-laptops
dbalan has joined #aarch64-laptops
_dbalan has quit []
<macc24>
turns out fwupdmgr install-blob can update uefi firmware on slim7x
<macc24>
oh my
<macc24>
it even worked after the update
<macc24>
s/worked/workes/
<macc24>
s/worked/works/
<macc24>
this is how i updated it - fwupdtool install-blob ./AlaxBIOS.cap 21fd282d5783d787a6db9432325221d3b24edbf3
<maz>
macc24: you like living dangerously! :)
<macc24>
there is a fine line between passion and madness
<maz>
hear hear!
<JensGlathe[m]>
what is that sha
<macc24>
it's the device-id for the uefi firmware
<macc24>
fwupd device-id*
<robclark>
macc24: care to share the bios update.. I'm back from xdc now so good time to try fw update
<macc24>
sure, there's also an ec update
<macc24>
i'll dm you both uefi updates later today
<robclark>
thx
bylaws has joined #aarch64-laptops
<nirik>
lenovo still hasn't released updates on their support site? Or is this some other update?
<JensGlathe[m]>
Hmm HP has
<JensGlathe[m]>
Now look at that. Even with WiFi disabled I get these odd RX cb errors eventually. https://pastebin.com/q2kX4BYP Also, spinlocking the whole cb function doesn't resolve the issue, it is just a call from the ath firmware with incorrect data
<JensGlathe[m]>
Had this on 2 volterra boxes. One with spinlocked cb, the other without
<JensGlathe[m]>
if you route the whole traffic via WLAN, it occurs way sooner
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
SpieringsAE has quit [Remote host closed the connection]