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
<bryanodonoghue>
steev dgilmore udmabuf + libcamera 0.3.1 should be all you need
<bryanodonoghue>
+ firefox > 126
<steev>
bryanodonoghue: yeah, turns out debian doesn't have qcom_camss or video_ov5675 enabled :(
<bryanodonoghue>
hmm maybe if I ask nicely :)
<steev>
i was gonna submit a merge request after testing the build (currently building with qcom_camss)
<bryanodonoghue>
it would be great to use debian's upstream kernel on x13s
<steev>
you can already, just no webcam :)
<steev>
someone said something here last week or so, and i just started looking into it
<bryanodonoghue>
heh you can also use openbsd the same way
<steev>
it would also be nice if qualcomm/lenovo would submit the venus firmware so we can finally have venus
<bryanodonoghue>
that would be an ecumenical matter
<steev>
bryanodonoghue: when i try to use the cam, i get an i2c device deferred for ldo7, do you happen to know/remember which config option i might be missing? i went back through your repo, and in 6.7 the only things were adding CAMSS and the OV5675 and i've added both of those
laine has quit [Remote host closed the connection]
<steev>
ah, it's probably CONFIG_MFD_QCOM_PM8008
<steev>
blah, that HTC Rx bug is really fucking annoying
weirdtreething has quit [Ping timeout: 480 seconds]
weirdtreething has joined #aarch64-laptops
sally has joined #aarch64-laptops
funderscore is now known as f_
ungeskriptet_ has joined #aarch64-laptops
ungeskriptet has quit [Ping timeout: 480 seconds]
ungeskriptet_ is now known as ungeskriptet
alfredo has quit [Ping timeout: 480 seconds]
hawer has joined #aarch64-laptops
alfredo has joined #aarch64-laptops
<pstef>
should upstream debian (trixie) handle bluetooth on the x13s properly? Recently it's been unreliable for me, but it may be a skill issue
proycon has quit [Ping timeout: 480 seconds]
proycon has joined #aarch64-laptops
iivanov has joined #aarch64-laptops
<bryanodonoghue>
pm8008 is required too yep
alfredo has quit [Quit: alfredo]
rmsilva has joined #aarch64-laptops
<_mike>
hi
srinik has joined #aarch64-laptops
<spawacz>
xrandr and wlr-randr show only one resolution option on x13s. Is it a hardware limitation?
iivanov_ has joined #aarch64-laptops
<jannau>
yes, the panel has a fixed number of pixel and it's preferable adapt rendering in software than to invent lower resolutions out of thin air and scale them up to the panel resolution in the display block or a separate scaler in the panel / display path
iivanov has quit [Ping timeout: 480 seconds]
hightower2 has quit [Remote host closed the connection]
hightower2 has joined #aarch64-laptops
hightower2 has quit [Read error: Connection reset by peer]
hightower2 has joined #aarch64-laptops
kettenis has quit [Ping timeout: 480 seconds]
kettenis has joined #aarch64-laptops
iivanov_ has quit [Remote host closed the connection]
<anthony25>
I'm confused about one thing there: The problem is that, when you have more than one devicetree blob (DTB) packed into the firmware package flashed on the device, there is no standard way of selecting a devicetree to pass on to the kernel.
<anthony25>
the firmware really contains the dtbs or is it worded incorrectly?
<macc24>
depends on what do you define as "firmware"
<anthony25>
depends what *they* defined as "firmware" :p
<\[m]>
soooo who's selling his t14s yet 😄
<robclark>
anthony25: something along the lines of https://github.com/TravMurav/dtbloader is probably the most reasonable way to have a single linux image that works across different laptops without the user having to fiddle with grub cfg to load the correct dtb
<anthony25>
that makes sense, I thought also about dtbloader
<anthony25>
but I was wondering what they meant by "the firmware package flashed on the device"
<anthony25>
considering that the dtbs are shipped with the kernel
<robclark>
ideally we wouldn't ship dtb's with kernel.. something like a fwupd plugin would be a nice way to deliver dtb updates as "firmware updates".. it would require being a bit more careful about decoupling dtb from kernel version, but at least after early device bringup, I think it could be possible
<travmurav[m]>
Iirc qcom was showcasing some new thig that was just different take on msm-id/board-id for their "official" in firmware devicetrees but not like many commercial devices would use it anyway I feel...
patrickm has quit [Ping timeout: 480 seconds]
patrickm has joined #aarch64-laptops
patrickm has quit [Ping timeout: 480 seconds]
<anthony25>
ha that makes it clearer, thanks!
<anthony25>
so the current firmwares don't contain a dtb, or we don't know?
<travmurav[m]>
presumably there are some internal dtbs but I think those aren't conformant to ""canonical""(mainline linux) dt bindings
<travmurav[m]>
i.e. qcom uses FDT as data format extensively
<robclark>
even for the dsp fw
<travmurav[m]>
but well FDT is quite a nice format, a lot of people use it for random things xD
<travmurav[m]>
like FIT images for example
<anthony25>
that would be great if we could extract them
<travmurav[m]>
well you can rather trivially I think, but not sure how useful they are
alfredo has joined #aarch64-laptops
<robclark>
hmm, so now there are x1e, x1p, and plain 'ol x1? Hopefully the plain x1 is just purwa? (The specs at least seem similar to 8 core x1p from what I can tell so far)
<travmurav[m]>
uh was somehting announced?
<travmurav[m]>
uhhh
<travmurav[m]>
x1-26-100
<travmurav[m]>
duh
<travmurav[m]>
I hate their marketing naming scheme so much
<travmurav[m]>
X Elite, X Plus, X Plus, X
<travmurav[m]>
but the low end chip is exciting
deathmist1 has joined #aarch64-laptops
<JensGlathe[m]>
This is Purwa binning I would assume... hope so.
<JensGlathe[m]>
what is that odd x1p46, never seen so far
<JensGlathe[m]>
oh x1e-00 -1de has higher graphics perf, that explains my impression. angrybox is pretty quick with a display
hightower2 has quit [Ping timeout: 480 seconds]
<robclark>
JensGlathe[m]: the speedbin stuff is still missing for gpu (and ACD is on list but not merged yet).. so you aren't yet hitting the higher clock speeds that you have (with linux, I guess if you are also running windows some of the time then you'd hit the higher speeds there)
<JensGlathe[m]>
it was just an impression when using as desktop, that thing is quick
<travmurav[m]>
robclark: but hm I think there is only hamoa and purwa of those that were pushed to windows update
<travmurav[m]>
there is also x2e there so I'd make a guess that the x1-2xx are also purwa
<travmurav[m]>
so hopefully just bad bin then, and I'd really hope those devices would be cheap
<robclark>
yeah, cache size, etc, looks the same, so I'm guessing as far as x1* it is all just various bins of hamoa and purwa
<travmurav[m]>
tbh I was wondering what adjective they will use that is below both "elite" and "plus", not sure if I'm disappointed xD
alexeymin has quit [Remote host closed the connection]
<JensGlathe[m]>
wit for the "minus" binning with 4 cores only
<travmurav[m]>
well we all know that marketing people will never pick diminishing words and I was like "there is quite a gap between "elite" and "plus"" xD
alexeymin has joined #aarch64-laptops
<travmurav[m]>
but the brilliant marketing people were like "well use the plus for that other thing I guess, and that worse thing uhhh... well just call it without any prefix, that won't confuse anyone, right?"
<robclark>
plain "x1" was kinda what I was expecting.. even if it is a bit annoying for dt bindings regexp :-P
<travmurav[m]>
here I'm actually struggling with looking up things that aren't "X Elite" since "X Plus" and uh "Snapdragon X" are too vague to search for :/
<travmurav[m]>
that is, if I'm looking to get one that isn't in the list of like 4 devices sold in normal retail for insane price
<travmurav[m]>
I guess if you have proper search filters its the shop problem not consumer's xD
<travmurav[m]>
and the new mobile Snapdragon 8 X won't help me either xD
alfredo has quit [Ping timeout: 480 seconds]
deathmist has joined #aarch64-laptops
deathmist1 has quit [Ping timeout: 480 seconds]
Caterpillar has quit [Quit: Konversation terminated!]
srinik has quit [Ping timeout: 480 seconds]
<steev>
pstef: yes bluetooth should be handled
<pstef>
I see, thanks
alfredo has joined #aarch64-laptops
Caterpillar has joined #aarch64-laptops
alfredo has quit [Quit: alfredo]
SpieringsAE has joined #aarch64-laptops
SpieringsAE has quit []
<steev>
ergh, i did mfd but forgot about the regulator
hawer has quit [Ping timeout: 480 seconds]
hogliux has joined #aarch64-laptops
<hogliux>
kurzugy: do you have windows 11 guest working in qemu with kvm acceleration? Other VMs work find for me but I can't get Windows 11 to work. It always just freezes when the Windows boot progress spinner appears.
<hogliux>
kurzugy: I'm on qemu version 8.2.2 (default debian version). Everything works if I use emulation/disable kvm (i.e. -cpu max etc.) but of course it's dead slow then
<hogliux>
maz: which kvm/kernel version are you using?
<hogliux>
And yes, I'm booting in EL2. I can boot linux images with kvm acceleration without any issues. It's only Windows.
hogliux has quit [Quit: Page closed]
hawer has joined #aarch64-laptops
alfredo has joined #aarch64-laptops
patrickm has joined #aarch64-laptops
<freekurt[m]>
Looks like an x13s in tablet form is being mainlined.