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
deathmist1 has joined #aarch64-laptops
deathmist has quit [Ping timeout: 480 seconds]
deathmist1 is now known as deathmist
Norbert011 has joined #aarch64-laptops
hipboi has joined #aarch64-laptops
hipboi has quit []
hexa- has quit [Quit: WeeChat 4.2.2]
hipboi has joined #aarch64-laptops
hexa- has joined #aarch64-laptops
hipboi has left #aarch64-laptops [#aarch64-laptops]
todi_away has quit []
todi has joined #aarch64-laptops
Norbert011 has quit [Quit: bye]
<steev>
and 6.12 is tagged
tobhe_ has joined #aarch64-laptops
tobhe has quit [Ping timeout: 480 seconds]
hexdump0815 has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
chrisl has quit [Read error: Connection reset by peer]
srinik has quit [Remote host closed the connection]
srinik has joined #aarch64-laptops
srinik has quit [Remote host closed the connection]
aradhya7 has quit [Quit: Connection closed for inactivity]
jhovold has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
Dalphon_ is now known as unalmasIRC
chrisl has joined #aarch64-laptops
<kalebris>
are there any rumors on features/goodies targeted to be added to 6.13? for t14s or x13s?
chrisl has quit [Ping timeout: 480 seconds]
<JensGlathe[m]>
Full dp altmode I hope
<deathmist>
robclark: I would maybe consider that but I'd have yet another project I'd never finish on top of having to get very much down to the metal and learning all about both aarch64 and aarch32 assembly; partially I wanted this device to speed up a project of mine actually but seems like I'll be suffering with cross-compile hacks for eternity
Jasper[m] has joined #aarch64-laptops
<Jasper[m]>
<JensGlathe[m]> "Full dp altmode I hope" <- Better modeswitching would be nice in general, I think that patchset has been on the mailing list for months hahaha
lak has joined #aarch64-laptops
alfredo has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
alfredo1 has joined #aarch64-laptops
alfredo has quit [Ping timeout: 480 seconds]
alfredo1 is now known as alfredo
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
davidinux has joined #aarch64-laptops
SpieringsAE has joined #aarch64-laptops
<SpieringsAE>
Just saw a patch for the crd fingerprint scanner, and that reminded me that I am still confused about the USB topology on my asus, it has 3x ps8830 retimer, 2x usb4 type c and 2x usb3 type a
<SpieringsAE>
Does 1 retimer do both type a ports?
<SpieringsAE>
some usb hub chip after it or something?
<SpieringsAE>
Somebody mentioned that there would be nxp,ptn3222, but that is only usb2, so I doubt that
davidinux has quit [Quit: WeeChat 4.3.1]
chrisl has joined #aarch64-laptops
<SpieringsAE>
I should just open that thing up and check the chips around the usb type a ports
<JensGlathe[m]>
Are you sure that there are 3 x PS8830? You usually have one per type-c port. For type-a you have ptn3222 per port. Should be 2
<SpieringsAE>
that's what is in the dsdt, and what the comments in the dtb suggest, but yeah I should just open it up
<SpieringsAE>
but the ptn3222 is usb2
<SpieringsAE>
my ports are usb3
<JensGlathe[m]>
Yeah you need 2 phys for a complete usb3 port. Usb2 and usb3
<SpieringsAE>
ah okay yeah that makes sense
<SpieringsAE>
so then there would also be 2 more for the usb3 parts which are currently unknown?
<JensGlathe[m]>
The t14s dtb (on my repo at least) has 2 type a ports, but 3 type-c
<JensGlathe[m]>
My hp x14 has 2x ps8830 ans 1x ptn3222
juergh_ has quit [Read error: Connection reset by peer]
juergh has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<SpieringsAE>
huh the t14s only has 2 usbc ports
<SpieringsAE>
it has a very similar layout to the asus
<SpieringsAE>
its only missing the sd card slot, besides that it is identical
<JensGlathe[m]>
See š¤·āāļø
<JensGlathe[m]>
Beware of i2c0 though, use the definition you already have
<JensGlathe[m]>
You also need smb2360 nodes
<SpieringsAE>
could that third ps8830 somehow have something to do with the hdmi port? because the t14s has the same thing, 3 ps8830 in dsdt, but only 2 usb type c
<SpieringsAE>
that the hdmi is just a goofy usb/dp converter thingy
<JensGlathe[m]>
Thought about that, too.
<SpieringsAE>
okay when I come home, I am opening it up and finding all the ps8830 chips on there
alfredo has quit [Quit: alfredo]
pinskia has quit [Read error: Connection reset by peer]
pinskia has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
nothorseface has quit []
davidinux has joined #aarch64-laptops
nothorseface has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
flokli has quit [Ping timeout: 480 seconds]
davidinux has quit [Ping timeout: 480 seconds]
flokli has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
alfredo has joined #aarch64-laptops
nothorseface has quit [Ping timeout: 480 seconds]
nothorseface has joined #aarch64-laptops
nothorseface has quit [Remote host closed the connection]
nothorseface has joined #aarch64-laptops
jkm has quit [Quit: leaving]
<jhovold>
Here's an updated wip branch for the X13s:
<robclark>
jhovold: re UEFI fw bugs, is it possible to better list out what devices/configurations are problematic.. AFAIU it is various lolz on x1e devkit and problems with 64GB RAM devices? Might also be worth pointing to grub workaround patches so distro's know what is needed
<robclark>
also link to T14s/x1e page from wiki front page ;-)
<deathmist>
on some devices (like X1E HP OmniBook) keyboard doesn't seem to work for non-default boot entries once reaching the bootloader, any others or just a quirk with the HP?
<jhovold>
robclark: my t14s has 32 GB and the UEFI fw is still buggy as hell
<jhovold>
could never get grub to boot at all, and sd-boot only works sometimes
<tobhe_>
same but 64GB, there is 64GB issues we have workarounds for and the seemingly random issues everyone gets
<jhovold>
s/boot/start the kernel/
tobhe_ is now known as tobhe
<robclark>
hmm, ok.. I had non-working keyboard on my 7x until I installed fw update, and hadn't really seen any problems since (it is only 32GB)
<tobhe>
it seems to only affect the t14s
<jhovold>
I made sure to update to the latest UEFI fw so whatever it is it still isn't fixed for the T14s at least
<robclark>
hmm, ok
<tobhe>
all we know so far is that it gets into a state where things don't work and you have to reboot multiple times until it boots again
<tobhe>
some people think adding or removing usb devices makes a difference
<jhovold>
(fixed the wiki front page now, robclark)
<tobhe>
hard to tell if it actually does because of how random it seems
<deathmist>
happens to list some other projects of interest in readme too
<robclark>
fwiw, alternatively maybe you can find a used x13s.. which IIRC did have arm32 support (making it probably the fastest thing you can get that still has arm32 support, since later cortex-x cores dropped arm32)
<HdkR>
Dynarmic is no longer maintained, and it is only the JIT side of things. The OS integration is expected to be done by a different project
<HdkR>
The Tango emulator is a more complete solution for AArch32->AArch64
SpieringsAE has quit [Quit: Leaving]
davidinux has quit [Quit: WeeChat 4.3.1]
davidinux has joined #aarch64-laptops
<craftyguy>
The new x13s bt fw didn't make it into the linux-fw 20241110 release, did it?
nothorseface has quit []
nothorseface has joined #aarch64-laptops
nothorseface has quit [Remote host closed the connection]
davidinux has quit [Read error: Connection reset by peer]
alfredo has quit [Ping timeout: 480 seconds]
<robclark>
the strange thing was, that previously, `alsactl info` did work.. which I _assume_ meant I had all the bits and pieces
<JensGlathe[m]>
davidinux: I have the HP X14, seems to be very similar. Iād like to try it out
nothorseface has quit []
<tobhe>
I'll see if I can package it all up nicely this week, including tplg and ucm conf
nothorseface has joined #aarch64-laptops
alfredo1 has quit [Ping timeout: 480 seconds]
davidinux has joined #aarch64-laptops
jglathe_x13s has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
<agl>
steev: Do you want to push a Version of your Kernel of 6.12 on your github web site?
<agl>
steev: For the x13s.
<steev>
when i rebase on johan's stuff sure, but i'm working at the moment
<agl>
ok
<agl>
jhovold have released a wip version for the x13s of kernel 6.12 since 4 hours.
<steev>
4 hours ago i was asleep, and 2 hours ago i started my work day
<agl>
steev: I forgot your Nickname.
<steev>
my nickname is steev
<agl>
yes i forgot it in the message of jhovold.
<steev>
you don't need to tag me every time
<agl>
ok
<agl>
steev: Have a good work.
<agl>
Here in Europe/Germany is it 6:38pm .
chrisl has quit [Ping timeout: 480 seconds]
nothorseface has quit []
nothorseface has joined #aarch64-laptops
<deathmist>
HdkR: Tango seems really cool and exactly what I'm looking for, too bad I'm not interested in paying for commercial stuff for (dumb) non-commercial/personal projects
<HdkR>
deathmist: Yea, I figured as much. There aren't a lot of solutions in the space
<JensGlathe[m]>
there's a bit more, but on the T14s dt its complete for 2 ports
<JensGlathe[m]>
mybe they have compatible protocol
<SpieringsAE>
I will try it out next weekend I guess, I don't think I'll have much time/energy for furthur tinkering this week
<SpieringsAE>
I will try that too, maybe just skipping the tusb redrivers for now
<SpieringsAE>
no idea what will happen then
<SpieringsAE>
I wonder if the t14s has the same hdmi converter, has anybody already opened theirs up?
<JensGlathe[m]>
how many of these chips are there
<SpieringsAE>
the tusb ones?
<SpieringsAE>
2
<SpieringsAE>
one for every type a port
<JensGlathe[m]>
no, dp to hdmi converters, at all
<SpieringsAE>
ah only one
<JensGlathe[m]>
I would suspect that tusb522 and ptn3222 are compatibles from different vendors
<JensGlathe[m]>
meaning same design, multiple vendors
<SpieringsAE>
but same protocol?
<SpieringsAE>
seems unlikely to me
<JensGlathe[m]>
yeah
akaWolf has joined #aarch64-laptops
<JensGlathe[m]>
why not, its a little more complex, but standardized logic chip, like those TTL gates a few gates ago
<JensGlathe[m]>
decades*
chrisl has joined #aarch64-laptops
<macc24>
idk idk, tusb522 is usb3 redriver, ptn3222 is eusb2 -> usb2
<JensGlathe[m]>
just producing them in their fab with their process node is a "different design" from Si perspective, but can simply be the same logic, and you like to have multiple sources
<SpieringsAE>
and also I guess debug serial next to it
<SpieringsAE>
as solder points
<macc24>
jtag?
<SpieringsAE>
the chip under it doesn't bring anything up
Caterpillar has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<SpieringsAE>
macc24: I guess this does explain why that program of yours didn't work for me lol
<SpieringsAE>
about the EC
<macc24>
SpieringsAE: idk i still see similarities between other x1e laptop and your asus
<macc24>
wrt ec
<SpieringsAE>
there are other ones with this chip?
<SpieringsAE>
wait
<SpieringsAE>
that tusb522p chip doesn't have anything like a i2c/spi bus
<SpieringsAE>
its just passive?
<SpieringsAE>
big if true
<SpieringsAE>
if both that one and that dp to hdmi chip are indeed passive as it seems right now, this might be easier than expected
<JensGlathe[m]>
would sound too easy
<macc24>
<SpieringsAE> "there are other ones with this..." <- which chip? it8987 is what i usually see on x1e, it5120 is something new, but it might be running compatible-enough firmware as the dsdt of vivobook has a bunch of familiar calls to the ec
<SpieringsAE>
ah okay that is nice
<maz>
some of the IT5xxx line seem to use an Andes core instead of a 8051.
<maz>
probably risc-v based.
<SpieringsAE>
neat
<SpieringsAE>
is there a way to define some device that just has an enable pin and regulator? because that is what both of these are I guess
<SpieringsAE>
simple redriver or something
<macc24>
quick hack would be to tack the device enable pin onto pinctrl of parent device
<kettenis>
that is what we currently ship for the vivobook
<SpieringsAE>
hdmi, doesn't seem to work in firmware so I am afraid that one will have to be actually enabled
hightower3 has joined #aarch64-laptops
<SpieringsAE>
does this cause a weird licensing issue if I look at this/
<SpieringsAE>
or is the bsd license compatible with linux
<kettenis>
pretty much expected that, which is probably why I didn't try it
<SpieringsAE>
wow that is very minimal
<kettenis>
this is just a diff to the linux files so the original license applies
<SpieringsAE>
ah its a patch
hightower3 has quit [Remote host closed the connection]
<SpieringsAE>
okay cool
<SpieringsAE>
hows openbsd on these things? I tried installing it for the first time on one of my x86 laptops, but it was not very great sadly
<SpieringsAE>
biggest one is no touchpad, some funky elan thing
<kettenis>
touchpad on the vivobook works
<kettenis>
ni display controller driver yet, so all you'll get is the firmware framebuffer
<kettenis>
no wifi yet either
<SpieringsAE>
pretty rough
<kettenis>
gotta start somewhere ;)
<SpieringsAE>
yep that is definetly true
<ppd[m]>
question, does the slim 7x have some sort of speaker protection? I've seen some mumbling about needing speakersafetyd in here (a while back) but I still have no idea if such a thing is needed
<SpieringsAE>
yeah I'm pretty sure not at least right now
<SpieringsAE>
doing anything with speakers is trying to set everything very low I guess
<ppd[m]>
ah, ok. nothing hardware wise. to quote someone(?) in here, they're doing that all via software
<SpieringsAE>
pretty sure yeah
<ppd[m]>
hm. I wonder if there is anything in the windows install that has the parameters for modelling the speakers
SpieringsAE has quit [Remote host closed the connection]
<ppd[m]>
also, as a semi-random aside: is there any good sources for everything linux audio? (eg: from ALSA to pulse/pw/jack) I've been looking for a while but can't seem to find anything
<steev>
kernel docs
<ppd[m]>
noted, thanks steev.
<steev>
for the pulse/pw/jack though, probably their docs?
<ppd[m]>
I guess that figures.
<ppd[m]>
tbh maybe I should write a comprehensive document on linux audio from the ground up
<abby>
ar h wi
<abby>
arch wiki perhaps
<steev>
nah, arch is good but it's not write stuff from scratch good
<JensGlathe[m]>
Is there no foundation to build from?
<steev>
the docs :P
<steev>
i would also think you'd kinda need the datasheet(s)
<ppd[m]>
I mean this would be a rather generic book about Linux audio, from alsa to pipewire, and writing applications for them.
<ppd[m]>
Also archwiki doesn't have the stuff to, say, reverse engineer speaker parameters
<JensGlathe[m]>
Sounds like a lot of work, though. Would be useful, too.
<ppd[m]>
Yeah. I've run into this too many times. Would be very nice to have some help with pro audio, too.
<wizzard>
Hi,
<wizzard>
I accidently removed myself from wheel, did not set a root password v
<wizzard>
v
chrisl has joined #aarch64-laptops
<wizzard>
I am now tring to edit the grub command to set a root password. My issue is that, when I press esc, to enter grub with the `normal` command, the screen flashes and then boots. Does anyone know how to edit the grub entry with `e`. I think I am making some stupid mistake
nothorseface has quit []
<steev>
after you edit, you should be pressing ctrl+x to boot, i think
chrisl has quit [Ping timeout: 480 seconds]
<wizzard>
I think I did not describe my problem well. After running normal from the grub cli, I only see a black screen, where the is flashing. I am pressing key down and e with the goal of stopping the boot. I cannot edit the grub entries
<wizzard>
My plan b is to chroot from a livestick.
<steev>
sounds like plan b is easier :)
nothorseface has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
nothorseface has quit []
chrisl has quit [Ping timeout: 480 seconds]
<kuruczgy[m]>
Does anyone have the device tree changes needed to get DP output on the yoga slim 7x? (I guess everything else should be already there on Johan's wip branch, and the devicetree changes should be very similar to the ones for the CRD and the t14s?)
<robclark>
kuruczgy[m]: abelvesa had a patch at one point.. I was able to get 2 of the 3 usb-c's to work.. but after some rebasing it stopped working
jhovold has quit [Ping timeout: 480 seconds]
<kuruczgy[m]>
robclark: is there any major chance of breaking anything, if I just... copy-paste the changes from the CRD device tree and try that?
<robclark>
I don't think you'll set anything on fire
<robclark>
so no permanent damage
<kuruczgy[m]>
ok, thanks
nothorseface has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
<tobhe>
kuruczgy[m]: I think the dtb from the Ubuntu tree should work
<tobhe>
if you believe the people in the bug tracker at least. I don't have a machine here to test
chrisl has quit [Ping timeout: 480 seconds]
<kuruczgy[m]>
oh cool, will check that out, thanks
norwoodites has joined #aarch64-laptops
pinskia has quit [Read error: Connection reset by peer]
pinskia has joined #aarch64-laptops
norwoodites has quit [Ping timeout: 480 seconds]
<kuruczgy[m]>
Aand I am getting DP output. I cherry picked the two relevant commits from the ubuntu tree (87f07f4fe544 and 350f8e8802be), and reduced the lanes to only two (not sure if needed). During boot the screen goes black (I have to type disk pw blind, maybe an initramfs module is missing? (Maybe drm_dp_aux_bus?))
<kuruczgy[m]>
The output appears gray/low contrast (mode: 1920x1080@60.000 Hz). I am using the HDMI adapter that came with the laptop. Also only the ports on the left work, on the right one the link training fails.
<tobhe>
you might not need the two lanes on the yoga