robclark 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
<steev>
they should be in c:\windows\system32\driverstore\filerepository\
<Jasper[m]>
<steev> "they should be in c:\windows\..." <- Probably, but I'd rather have them stashed somewhere so other people can use them
<Jasper[m]>
i.e. to restore their system or to grab any needed firmware missing from upstream
<Jasper[m]>
Having them reproducibly fetched from windows update is probably a better idea then
<steev>
i've been grabbing the x13s, c630 and flex5g that way, though i lost most of the c630/flex5g because of a dd to sda that should have been sdb
<Jasper[m]>
steev: Well the C630 stuff can be grabbed off the Qualcomm-Reference-Drivers repo
<steev>
i just wish there was a good way to go back to 1.23 bios instead of the 1.33
<Jasper[m]>
They removed those from lenovo's site?
<steev>
no, i just don't know how to force it to downgrade
<steev>
1.33 is the one that won't boot from > 32GB usb
<Jasper[m]>
Ah in that sense
<steev>
they're iirc, both still on the windows partition
<steev>
i broke my c630 the other day though :(
<steev>
and by broke i mean i updated grub without updating grub
<Jasper[m]>
Also, if you're looking for Flex 5G drivers you can probably get those from windows update too using a different branch of uupmediacreator and some dmi data
<dgilmore>
It's a raw disk image with a very minimal install
<dgilmore>
You would need to tell grub to load the devicetree and add EFI=novamap
jglathe__ has quit [Ping timeout: 480 seconds]
<_[m]123>
sorry to read steev, sad sda
<steev>
my fault for not paying attention :)
<steev>
it's also why my blog isn't being updated anymore, i haven't felt like re-setting-up the scripting of it
<_[m]123>
disk destroyer ++
<Segfault[m]>
<jenneron[m]> "some devices don't have this..." <- the X13s probably does have that partition, just on the internal ufs that doesn't seem to be accessible by windows or linux (yet?)
<jenneron[m]>
Segfault: it is accessible for sure
abdberkana has joined #aarch64-laptops
louist103 has joined #aarch64-laptops
<louist103>
Since I am going through the build process again, which kernel modules and settings do I need to enable for the c630? I am hoping for this install to "just work". I already know about the i2c_hid_of, and hid_multitouch. Anything for wifi?
Evaia6310116 has joined #aarch64-laptops
<dgilmore>
Jasper[m]: you might want to run something like dnf --releasever 40 --enablerepo=fedora --disablerepo=rawhide --enablerepo rpmfusion-free --disablerepo rpmfusion-free-rawhide --enablerepo rpmfusion-nonfree --disablerepo rpmfusion-nonfree-rawhide update
<dgilmore>
Jasper[m]: at least if you want to follow along and end up with fedora 40 rather than continuing to run rawhide
Evaia631011 has quit [Ping timeout: 480 seconds]
Evaia6310116 is now known as Evaia631011
abdberkana has quit [Ping timeout: 480 seconds]
louist103 has quit [Quit: Page closed]
jglathe_x13s has joined #aarch64-laptops
<Segfault[m]>
alright jhovold yeah i reckon wifi's fixed
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
abdberkana has joined #aarch64-laptops
<Jasper[m]>
<dgilmore> "Jasper: at least if you want..." <- correct, already saw that rpmfusion was trying to install version 41 of theur repo's and thought something was happening. Thanks for the tip!
<steev>
well that command is a mouthful!
enick_50 is now known as go4godvin
<jhovold>
Segfault[m]: excellent, feel free to reply with a Tested-by: tag here:
<Segfault[m]>
i'm gonna be honest i have absolutely no idea how to do that, mailing lists mess with my head lol
xroumegue has quit [Ping timeout: 480 seconds]
<jhovold>
Segfault[m]: heh, yeah, you'd need to reply-to-all to that email and say something about this fixing the described and then a single line "Tested-by: N M <email>" which would go into the git logs when the patch is applied
<jhovold>
there are apparently some general instruction at the end of the page I linked to (e.g. on how to download the series as an mbox file)
<jhovold>
your call, I can also update the commit message and say it has been verified if there's a v2
<jhovold>
but we try to give credit to testers this way
<jhovold>
here's an example of a reviewed-by tag being provided:
<Jasper[m]>
Anyone here have an idea as to getting needed regulator values from a WoS laptop?
<Jasper[m]>
Something I can map to regulator-min/max-microvolt values in a device tree basically
<Jasper[m]>
I don't have schematics for this device and apparently PEP infers it in some complicated way from DSDT
<Jasper[m]>
With more possibilities than Linux has currently anyways
abdberkana has quit [Ping timeout: 480 seconds]
martiert has quit [Quit: WeeChat 4.2.1]
<jenneron[m]>
Jasper: ACPI tables
abdberkana has joined #aarch64-laptops
<konradybcio>
there's VREG entries in pstates
<jenneron[m]>
maybe a dumb explanation, but might be several definitions of the same regulator, having different voltages
<jenneron[m]>
it is usually when you need to find all of them and set the lowest to min value and the highest to max value
<konradybcio>
i'd say the max of low and high settings.. otherwise you can undervolt things
<Segfault[m]>
the dsdts do seem to have the maximum and minimum voltages for most of the regulators but sometimes they're voltages that the linux driver can't set for some reason
<jenneron[m]>
yeah
<konradybcio>
that's also true for android kernel devicetrees
<jenneron[m]>
there is something like this in downstream, where you copy voltage from downstream dts to mainline and driver can't set it
<konradybcio>
you gotta round it up/down to the closest value
<konradybcio>
you can infer it from the regulator driver
<Segfault[m]>
konradybcio: oh have you got a link to that? i should really check my np545 dts
<jenneron[m]>
Segfault[m]: you should also send it to sc8180x-mainline and to upstream
<konradybcio>
then check what data struct the compatible maps to
<konradybcio>
and then each regulator has a pointer to some regulator ops
<konradybcio>
the regulator ops in turn, have a set of linear ranges with min, step, count
<Segfault[m]>
ah yep i see
<konradybcio>
so, if we have min=1v, step =8mv, count=100, we have a 100-element set like {1, 1.008, 1.016 ... }
<konradybcio>
might be off by one with count, idr if it includes step_count=0
<Segfault[m]>
seems like it's min_uV, min_sel, max_sel, uV_step
<konradybcio>
yeah, sel = "amount of steps added to min_uV"
<konradybcio>
and you get max_uV by adding step the maximum amount of times
<Jasper[m]>
<konradybcio> "there's VREG entries in..." <- do you mean the PMICVREGVOTE packages in dsdt or is it in a different table?
<konradybcio>
yes
<konradybcio>
to the first one
<Jasper[m]>
konradybcio: to the what?
<konradybcio>
to PMICVREGVOTE
<Jasper[m]>
What do you mean?
<Jasper[m]>
I mean I see the packages, I see the regulator names that sort of line up with what's upstream, but I can't get a meaningful value from the data contained in it I think
<Jasper[m]>
Or at least I don't know
<Segfault[m]>
yep so there are a bunch of PMICREGVOTE entries with names like, for example, PPP_RESOURCE_ID_LDO10_E
<Segfault[m]>
the third entry in that should be a hex value, that's a voltage request, find the highest and lowest request for that (within reason, ignore things like 0x0) and those are your min and max voltages for that regulator, with some exceptions
<Segfault[m]>
the LDOX/SMPSX in the name is what regulator it is and the letter at the end is what PMIC it's in
KREYREN_oftc has quit [Remote host closed the connection]
KREYREN_oftc has joined #aarch64-laptops
<Jasper[m]>
<Segfault[m]> "yep so there are a bunch of..." <- > <@tuxthepenguin:matrix.org> yep so there are a bunch of PMICREGVOTE entries with names like, for example, PPP_RESOURCE_ID_LDO10_E
<Jasper[m]>
> the third entry in that should be a hex value, that's a voltage request, find the highest and lowest request for that (within reason, ignore things like 0x0) and those are your min and max voltages for that regulator, with some exceptions
<Jasper[m]>
I'll take a better look, I saw the significantly bigger hex value, didn't properly convert it I think
<Jasper[m]>
(out of pure laziness I mean)
<konradybcio>
Jasper: btw you can just paste hex values into the python shell
<Jasper[m]>
Yeah I threw it in an improperly set up cyberchef
<Jasper[m]>
lmai
<Jasper[m]>
* lmao
<konradybcio>
well, you can kill birds with a cannonball..
svarbanov has quit [Read error: Connection reset by peer]
svarbanov has joined #aarch64-laptops
<Jasper[m]>
<konradybcio> "Jasper: btw you can just paste..." <- Okay, that works
<Jasper[m]>
SMPS1 has 1 value that's inbetween the max and min of sc7280-idp.dtsi