ChanServ changed the topic of #asahi-dev to: Asahi Linux: porting Linux to Apple Silicon macs | Non-development talk: #asahi | General development | GitHub: https://alx.sh/g | Wiki: https://alx.sh/w | Logs: https://alx.sh/l/asahi-dev
kidplayer666 has quit [Quit: Connection closed for inactivity]
millenialhacker has joined #asahi-dev
millenialhacker has quit [Ping timeout: 480 seconds]
malfunction54 has quit [Quit: Leaving]
mariogrip has joined #asahi-dev
eiln has joined #asahi-dev
jeisom has quit [Ping timeout: 480 seconds]
crabbedhaloablut has joined #asahi-dev
tristan2_ has joined #asahi-dev
tristan2 has quit [Ping timeout: 480 seconds]
billak has joined #asahi-dev
billak has quit [Remote host closed the connection]
millenialhacker has joined #asahi-dev
millenialhacker has quit [Ping timeout: 480 seconds]
kidplayer666 has joined #asahi-dev
al3xtjames has quit [Read error: Connection reset by peer]
<janneg>
kettenis: \o/ why is smc needed? due to the current dts? early september dcp shouldn't have dptx / dp2hdmi iirc
i509vcb has quit [Quit: Connection closed for inactivity]
eiln has quit [Quit: WeeChat 4.1.2]
millenialhacker has joined #asahi-dev
millenialhacker has quit [Ping timeout: 480 seconds]
flom84 has joined #asahi-dev
<kettenis>
janneg: the code I added to map the dcp crashlog buffer also mapped the smc crashlog buffer
<kettenis>
which led to random SErrors whenever the CPU happened to speculatively fetch data from it
<kettenis>
and yes, no dptx or dp2hdmi for now
<kettenis>
will definitely update to more recent code now that I have things working
<kettenis>
but I think I need update the dts for that and I think many of my machines are still on 13.3 OS firmware
flom84 has quit [Quit: Leaving]
seb4nih38 has quit [Quit: -a- Connection Timed Out]
seb4nih55 has joined #asahi-dev
millenialhacker has joined #asahi-dev
millenialhacker has quit [Ping timeout: 480 seconds]
chadmed_ has joined #asahi-dev
chadmed has quit [Ping timeout: 480 seconds]
jeisom has joined #asahi-dev
chadmed_ is now known as chadmed
seb4nih55 has quit [Quit: -a- Connection Timed Out]
seb4nih66 has joined #asahi-dev
malfunction54 has joined #asahi-dev
seb4nih66 has quit [Read error: Connection reset by peer]
seb4nih3 has joined #asahi-dev
jeisom has quit [Quit: Leaving]
jeisom has joined #asahi-dev
jacksonchen666 has joined #asahi-dev
<marcan>
hey folks, sorry for things being so quiet here lately
<marcan>
full disclosure, back when the Fedora release was announced in August we had a Matrix room to coordinate the pre-announcement at Flock, and it became a "let's get the release wrapped up" private Fedora dev room
<marcan>
as the Fedora release got delayed well beyond August, it slowly morphed into a secret Asahi dev chat and I failed to stop that going out of control, and meanwhile the set of people in the room was very arbitrary
<marcan>
I want to apologize for that, I screwed up and we are shutting down the room now
<marcan>
we've created a new, public Asahi/Fedora dev room on matrix now: #asahi-devel:fedora.im
<marcan>
Fedora-specific and general Asahi talk is welcome. we're also keeping IRC, of course.
<marcan>
we have quite a spread of people who prefer either platform, so until the world decides on the One True Chat Platform, I think it's worth keeping both
<marcan>
again, sorry to everyone who was kept in the dark. it wasn't intentional, it just snowballed out of control, but I want to personally take responsibility for not stopping it.
<j`ey>
we've missed you on irc <3
<marcan>
(there was also a side snafu where, since I switched to Asahi as a main devbox myself some time ago, I've been rebooting *very* often for testing and that has really screwed with my IRC workflow, even with a bouncer. I really need to get something smarter, but for now I'm moving irssi to one of my less often rebooted boxes)
<leio>
Is that new matrix dev room bridged to IRC anywhere or will it be made sure it's mostly Fedora specific? I've managed to stay away from Matrix so far, and hope to continue doing so; though even Fedora specifics are relevant to other distros integration usually
<j`ey>
leio: I had to cave and join matrix
<marcan>
it's not bridged because I'm not sure there's any terribly great bridging setup (see the Libera snafu), but I'm open to suggestions for setting up a bridge from people more knowledgeable about that
<leio>
I know that at least gstreamer has things bridged for their new matrix rooms, as far as channels in OFTC are concerned
<leio>
or well, the main room only
<j`ey>
it looks ugly from the IRC side (at least how #mesonbuild is bridged)
<leio>
In that sense I'd be even happy with a read-only mirror in IRC if really need be
millenialhacker has joined #asahi-dev
<marcan>
I'm assuming all of those options involve running our own infra? (I'm trying to minimize infra creep)
millenialhacker has quit [Ping timeout: 480 seconds]
<as400>
marcan: matterbridge does not require own matrix server.
<as400>
So it would be easiest on infra.
<marcan>
if it involves running infra at all I'm not sure it makes much difference, it's still a service at that point
<marcan>
put another way: if someone wants to sign up to run and maintain this for us I'm all for it :)
<as400>
ok, will do this
<as400>
So it would be these two from fedora.im: asahifedora and asahi-devel to oftc, right ?
<marcan>
largely #asahi-devel:fedora.im to #asahi-fedora-dev here or similar (we need to create that channel). not sure if it's worth bridging the user room since we effectively already have #asahi for that here, and there isn't as much value in it for general user discussion.
<as400>
ok, I'll see how it goes and report.
<marcan>
registered #asahi-fedora-dev
<marcan>
from matrix: davide> no preference, but I would recommend using something that does double puppeteering so conversations look native on both ends
<marcan>
> I'm in some rooms where all bridged messages come out of the same account and it's really annoying to follow
<as400>
yeah, it's a problem. Let me test what can be done
<marcan>
no rush, feel free to take your time and investigate
<marcan>
I'm probably going to mostly sign out until next year, I desperately need a break
<as400>
have a great time off then
<j`ey>
marcan: I hope you get some rest and maybe there'll be a M3 stream next year? ^_^
<marcan>
sure :)
eiln has joined #asahi-dev
<eiln>
ATTENTION AGAIN EVERYONE
<eiln>
I'm gathering a technical progress report for the fedora release
<eiln>
yes it's late but it's better than nothing
<eiln>
We've released so many new features that I can't even remember them all
<eiln>
M2 (esp desktop/HDMI), opengl 3.3, 3.1 es, system sleep, dcp backlight, hunk of broadcom fixes, touchbar, camera, hwmon (is that in?), hdmi out, speakers
<eiln>
oh, hwmon is not yet in
<eiln>
What am I missing?
<eiln>
Also notable bugfixes if you remember any, e.g. jannau's bluetooth mouse bisect
<eiln>
ALSO if anyone else has something up their sleeve that they'd like me to mention
<eiln>
e.g. I see FDE has been PR'd
<eiln>
I won't mention WIP features unless explicitly given ok
john-cabaj has joined #asahi-dev
<marcan>
yeah, FDE will probably need a bit of a do-over but that PR is a good start
<marcan>
let's keep it to released features
<ChaosPrincess>
installer fde - while working, the implemenation is a RFC at most
<ChaosPrincess>
so, if it breaks - you get to keep the pieces :P
<eiln>
I don't think bless was mentioned in last release?
<ChaosPrincess>
yea, im not sure they were anything more than some random repos at that point
<marcan>
there's so much stuff that happened in the last few months
<eiln>
will include
<marcan>
and also, the work of the Fedora team getting almost all this stuff packaged
<marcan>
and packaged upstream at that
<marcan>
which is actually a very important point (this isn't downstream fork repo stuff any more, this is all in Fedora period)
<eiln>
I plan on segueing into distro work with -edge stabilizations
<marcan>
sgtm
<janneg>
eiln: correct limit sensor / size for the trackpad on devices != j314
<marcan>
ooh yeah that one
ydalton has joined #asahi-dev
<balrog>
is there a writeup on what is missing for microphone support?
<marcan>
I think we need some state transfer from povik on that, but from my POV I'd like to see it reworked to use AOP the way macOS does
<marcan>
not sure entirely how that ties together with the existing non-AOP work
<balrog>
(Looking at the list of supported features, that's probably the main annoyance I'd run into)
<balrog>
(Second would be USBC displays, only because some machines don't have HDMI)
<ChaosPrincess>
if its for video conferencing, iirc we have mic via headphone jack
<ydalton>
dp alt mode is being worked on by sven and janneg iirc
<balrog>
Yeah, external mic is an option but not an ideal one :P
<balrog>
ydalton: ah nice
<sven>
yeah, we're slowly picking away at dp altmode
<sven>
as usual, the last 20% take the most of the time
<balrog>
TBT/USB4 is nice to have but quite useful; Touch ID is entirely nice to have :)
<ydalton>
i heard dp alt mode does work with the laptops, just not on the desktops
<sven>
no
<sven>
dp alt mode doesn't work anywhere
<eiln>
Looking at this list, this does feel like a child waking up to a tree full of presents
<eiln>
but I am cautious of being overtly "festive"
<sven>
we know how it (and all the other usbc mess like tbt) works and very slowly getting there
<sven>
there's random crap like dumping and reversing what feels like half of that cd321x firmware e.g. that just takes time
<balrog>
hmmm AOP... I'm guessing most laptops do microphones that way but handle that part in separate DSP?
<ChaosPrincess>
this is basically apple cloning the ios model where they have a coprocessor for "hey siri"
<janneg>
I probably regressed dp-altmode slightly with hdmi out via atc3-phy
<ydalton>
well take your time!
<sven>
janneg: no worries, i completely broke dp altmode with that new tipd code anyway :D
<sven>
usb3 seems to be very stable now, including switching dwc3's PIPE phy over
<sven>
(0x14 vs. 14 *sigh*)
<sven>
my vacation finally starts tomorrow so i'm planning to clean that up a bit and get more people to test it
<sven>
janneg: that hdmi out didn't need change inside atcphy, did it?
<janneg>
sven: the dp-phy callbacks can now configure things and are called from dptx
<janneg>
we need to find a way to bring thta together with the type-c mux/switch
<j`ey>
sven: that 0x will haunt you :-)
buroa has joined #asahi-dev
<sven>
ok, i'll take a look at the atcphy changes and merge them with my current code then
<janneg>
I did some pointless changes to make diffing of macos and linux traces easier
<janneg>
eiln: upcoming projects: make hdmi out on m2 desktops and 14/16-inch macbook pros robust, hdmi audio
<eiln>
sick, added
<sven>
you can also mention that dp altmode and thunderbolt is in progress and should come sometime in 2024
<eiln>
added
millenialhacker has joined #asahi-dev
millenialhacker has quit [Ping timeout: 480 seconds]
<eiln>
Starting writing and interviewing peeps now, pls lmk of structure changes early
<janneg>
eiln: trackpad fix is by marcan
<eiln>
ack
<janneg>
missing: EAS (energy aware scheduler) support by chadmed
<eiln>
I think chadmed's gonna write a good chunk of this
jacksonchen666 has quit [charon.oftc.net dacia.oftc.net]
jacksonchen666 has joined #asahi-dev
lena6 has quit [Remote host closed the connection]
lena6 has joined #asahi-dev
millenialhacker has joined #asahi-dev
millenialhacker has quit [Ping timeout: 480 seconds]
<mariogrip>
Hey eveyone, i have gotten a macbook pro (m3 pro), how can i help out with development on this? I have good experiene with arm and embedded devices, but new to this type of development. (i also have an m1)