<shorne>
sven: re-nvme suspend/resume thanks for confirming, my tests showed that didn't seem to have issues
<DmitrySharshakov[m]>
<dottedmag> "Dmitry Sharshakov: https://..." <- This article mentions there *is* an I2C bus accessible for each display. So, I guess I'll try to look that up in ADT and then it could be posted on the yaks page as a nice to have kernel driver. If we can get knowledge of its address in ADT, then somebody with m1n1 hv and some knowledge could RE that. Maybe that's the same PASemi IP block, who knows. I will try to find info in a
<DmitrySharshakov[m]>
week.
e1eph4nt has joined #asahi-dev
<DmitrySharshakov[m]>
Well, or maybe those I2C calls go into the DCP firmware, who knows
<_jannau_>
it most likely gets through one of the dcp endpoints, probably 0x29 (av) judging by the name
e1eph4nt has quit [Ping timeout: 480 seconds]
Manouchehri_ has quit []
e1eph4nt has joined #asahi-dev
<DmitrySharshakov[m]>
<_jannau_> "it most likely gets through..." <- Likely, since DCP firmware can read edid on its own to set fb up, so it must be managing the i2c
dmmcf has quit [Quit: dmmcf]
e1eph4nt has quit [Ping timeout: 480 seconds]
e1eph4nt has joined #asahi-dev
e1eph4nt has quit [Ping timeout: 480 seconds]
derzahl has quit [Ping timeout: 480 seconds]
e1eph4nt has joined #asahi-dev
e1eph4nt has quit [Ping timeout: 480 seconds]
leitao has joined #asahi-dev
jluthra_ has quit [Server closed connection]
jluthra_ has joined #asahi-dev
e1eph4nt has joined #asahi-dev
off^ has quit [Server closed connection]
off^ has joined #asahi-dev
e1eph4nt has quit [Ping timeout: 480 seconds]
leitao has quit [Ping timeout: 480 seconds]
<kettenis>
some evil person dropped a lenovo x13s on my desk
<kettenis>
that machine also doesn't actually support EFI variables at runtime
<ar>
kettenis: is that the snapdragon thing?
<kettenis>
maybe this will lead to some sort of alternative way to set those variables
<kettenis>
ar: yes
<ar>
kettenis: is linux even bootable on it?
<kettenis>
about half the speed of an M1
<kettenis>
yes, folks are bootling linux on it (not sure how well it works yet)
<kettenis>
I'm obviously helping to make OpenBSD run on it
<ar>
but hey, at least it has a trackpoint, and the touchpad isn't overgrown to the point of causing palm rejection problems ;)
<kettenis>
the trackpoint defenitely is a plus for thinkpad addicts
pjakobsson has quit [Remote host closed the connection]
<kettenis>
but we're getting off-topic here
<ar>
right
kjm99[m] has quit [Quit: Client limit exceeded: 20000]
e1eph4nt has joined #asahi-dev
dmmcf has joined #asahi-dev
off^ has quit [Ping timeout: 480 seconds]
off^ has joined #asahi-dev
yamii_ has quit [Remote host closed the connection]
yamii_ has joined #asahi-dev
<maz>
kettenis: I still have an older c630 as a test machine, which also has a nice trackpoint. OK for email, but otherwise painful.
<maz>
same EFI problems, by the way -- half-baked QC stuff.
danielbriggs[m] was kicked from #asahi-dev by ChanServ [You are not permitted on this channel]
<jannau>
too late :(
rmk has joined #asahi-dev
<marcan>
rmk: this is the higher SNR channel :)
<rmk>
jolly good :)
<rmk>
the noise on #asahi didn't bother me much, but useful to have higher SNR nevertheless
<marcan>
yeah, it helps keep things more focused and easier to grep for actionable things I find
<marcan>
(especially for me, since I actually want to read or at least skim the full backlog here, I've given up on that for #asahi)
<rmk>
how many folk do you have working on pushing kernel bits upstream?
<marcan>
usually people upstream their own stuff, but I in particular have been behind on that because I have too many things to do...
<marcan>
(also, personaly, I'm still a bit dismayed at the blockers - we're coming up on 1 year after the t6000 release and still no DART2 support upstream, that's holding back all chips except the original M1)
<povik>
yeah, just ran into that recently
<povik>
didn't occur to me it wouldn't be upstreamed
<povik>
is it itself blocked on something?
<alyssa>
povik: review
<povik>
ah the ultimate blocker
<marcan>
the last review round of that was in june, after v1/v2 got crickets
<marcan>
jannau: think you can try submitting a v4 sometime soon with the few review comments addressed?
leitao has joined #asahi-dev
<povik>
ah i thought it didn't get any review but it just wasn't addressed yet
<marcan>
after t6000 goes in t8113 should be easy to get supported - that only touches the driver proper, and my series for that is ready
<marcan>
povik: it got two replies
<povik>
ok
<alyssa>
last I heard, extending arm-lpae with dart2 support is going to be NAK'd because it's too different,
<marcan>
the split did get an acked-by already at least
<alyssa>
but the dedicated dart pgtbl code (copypasted out) would be merged
<alyssa>
yeah
<marcan>
the problem is v1/v2 were forever stuck in "this is ugly but the maintainer doesn't have any better ideas" limbo, and the only reason we knew that was side channels, because there were no direct replies
<marcan>
(reminds me of ALARM...)
<marcan>
great way to demotivate developers, tbh :(
<povik>
that sucks
IcaroDextris[m] has joined #asahi-dev
<marcan>
well, at least if v4 gets stuck in limbo again we can try playing the poking Linus card... he depends on that (and my t8110 support series on top)
<marcan>
but hopefully that won't happen
<alyssa>
"this is ugly but the maintainer doesn't have any better ideas" limbo
<alyssa>
Hey, usually I'm the maintainer causing said limbo :v
kujeger[m] has joined #asahi-dev
<povik>
now you know what we think of that :D
<alyssa>
I already knew...
<alyssa>
What's the maintainer supposed to do exactly?
<povik>
say something at least
<marcan>
like "this is ugly but I don't have any better ideas"
<marcan>
at least that explicitly points towards trying something else as an option to explore :p
e1eph4nt has quit [Ping timeout: 480 seconds]
e1eph4nt has joined #asahi-dev
<dottedmag>
I am surprised Linux devs haven't evolved any way to resolve this state.
<rmk>
being on the "other side" sometimes it's down to "I don't like it, but I'll think about it and respond later" and then forgetting about it because the flood of stuff continues to come in or you get distracted and it gets forgotten
<alyssa>
^^ that
<dottedmag>
Being disorganized is not a reason for blocking someone for months (or even for weeks), IMHO
<alyssa>
You try maintaining the volume of code we have to...
<povik>
yeah, i wouldn't shrug it off as being disorganized, but i would advocate for a quick message right away before the thinking
* povik
is not a maintainer of anything
<j`ey>
povik: defacto m1 audio maintainer
<povik>
yeah, volume: zero
<povik>
j`ey: not defacto, i added the sound stuff under an extra section
<povik>
the MCA driver, i mean. we can change that later
<alyssa>
dottedmag: fwiw, I just finished up my review stack. So I think everything I've replied to now :)
<povik>
cheers
<dottedmag>
alyssa: o/ I'm not trying to pick on anyone in particular
<rmk>
dottedmag: if you think it's "disorganised" then you're so wrong. when arm32 was going strong, emails were coming in every few minutes every day all day. it used to take hours each day just to read that quantity of email, let alone reply to it. try to have a break from it? come back to a huge pile of email that needs sorting through.
<dottedmag>
rmk: The process is disorganized, not the particular people, of course. Sorry for not making it clear. I know the arguments pro/contra this kind of development process, and some changes still fall through the cracks and languish, like DART2 patches mentioned above
<sven>
yeah, the t6k dart was a bit demotivating because there was no reply at all even after two pokes
<sven>
other than there's only bluetooth missing for me (for which I should sent a v2) and atcphy/usb3/thunderbolt but I don't understand that part well enough yet :D
<rmk>
yea, I can think of a bugfix that's causing issues for people needs to be merged into 6.0-rc that has been missed - it needs to be resent so the maintainer gets a fresh copy with all the attributations added
<rmk>
or an ack from the maintainer so I can pick it up (since the original patch that broke stuff came via my tree as part of a bigger patch set, with his ack of course)
bluetail21514 has quit []
bluetail21514 has joined #asahi-dev
e1eph4nt has quit [Ping timeout: 480 seconds]
leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
leitao has joined #asahi-dev
leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]