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
nothorseface has joined #aarch64-laptops
pabs has quit [Read error: No route to host]
pabs has joined #aarch64-laptops
nothorseface has quit [Ping timeout: 480 seconds]
nothorseface has joined #aarch64-laptops
tobhe has joined #aarch64-laptops
tobhe_ has quit [Ping timeout: 480 seconds]
nothorseface has quit [Remote host closed the connection]
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
nothorseface has joined #aarch64-laptops
nothorseface has quit []
f_ is now known as funderscore
nothorseface has joined #aarch64-laptops
nothorseface has quit []
patrickm has quit [Ping timeout: 480 seconds]
patrickm has joined #aarch64-laptops
nar001[m] has joined #aarch64-laptops
whiskey9 has quit [Ping timeout: 480 seconds]
zdykstra has quit [Quit: WeeChat 4.5.0]
weirdtreething has quit [Remote host closed the connection]
zdykstra has joined #aarch64-laptops
<macc24>
so i'm looking at dsdt of hp omnibook x14
<macc24>
and at around 43700 lines in, i see a bunch of field definitions
<macc24>
and then i see that F25G and F25S have no explicit Offset mention in them
<macc24>
so does FC24 point at 0x24(explicit Offset), F25G point at 0x25, F25S point at 0x26, FC26 point at 0x27, FC27 point at 0x28, F28G at 0x29(overlap with FC29) etc until FC29 which points at 0x29 with explicit Offset?
<macc24>
there's also FC20 which is right after CMD5 with no Offset so is it 0x6 instead of 0x20(which name seems to point at)
funderscore is now known as f_
weirdtreething has joined #aarch64-laptops
owokitty[m] has joined #aarch64-laptops
<kettenis>
macc24: F25G is AttribRawProcessBytes so the "command" offset doesn't matter
<kettenis>
F25S is similar; AttribRawBytes also doesn't use the "command" offset