#
…

2021-08-09

01:06skipwich has joined #asahi
01:07pinskia has quit [Read error: Connection reset by peer]
01:09amwIt would be nice to have a linux with nvme, dart and a fresher upstream update as a basis for new work
01:09pinskia has joined #asahi
01:27_whitelogger has joined #asahi
01:28lethalbit has quit [Read error: Connection reset by peer]
01:29chadmed has quit [Ping timeout: 480 seconds]
01:30chadmed has joined #asahi
02:06null has quit [Quit: oh no.]
02:06null has joined #asahi
02:19phiologe has joined #asahi
02:23PhilippvK has quit [Ping timeout: 480 seconds]
03:14marvin24_ has joined #asahi
03:17marvin24 has quit [Ping timeout: 480 seconds]
06:04marvin24 has joined #asahi
06:08marvin24_ has quit [Ping timeout: 480 seconds]
06:28svenyeah, and i think it's also nice to be able to do some kind of early internal review while we still iterate. we can probably catch lots of common gotcha long before we need to annoy maintainers on the mailing lists ;)
06:49DarkShadow4444 has quit [Ping timeout: 480 seconds]
06:56pipcet[m]sven: please keep bringing on the "nits", they're great :-)
06:56DarkShadow44 has joined #asahi
07:00svensure! i would've been happy to get those before my first upstream submission as well :)
07:00marvin24_ has joined #asahi
07:03marvin24 has quit [Ping timeout: 480 seconds]
07:16pipcet[m]well, certainly the first ones since that new-fangled DT stuff happened ;-)
07:18svenfair enough :)
07:24phofe has joined #asahi
07:35DarkShadow44 has quit [Quit: ZNC - https://znc.in]
07:35DarkShadow44 has joined #asahi
07:45DarkShadow44 has quit [Quit: ZNC - https://znc.in]
07:46DarkShadow44 has joined #asahi
07:46DarkShadow44 has quit []
07:47DarkShadow44 has joined #asahi
09:41arndsven: joro just merged the dart patches for 5.15 \o/
09:45chadmedoh wow yeah as of 20 mins ago neat
09:49marcan:o nice!
09:52svenawesome :-)
10:07pipcet[m]sven: did you look at the locked page table workaround that we need yet?
10:28marcanthe page table isn't locked, only the registers are
10:29marcanthat should be implemented together with mapping adoption from the bootloader, since the two problems kind of go together
10:29j_eydo we know / guess why theyre locked?
10:30sveni think there are more important things i want to do first (do asc/rproc in a sane way, nvme, 4k/16k dma-iommu, pcie, usb-phy)
10:31marcanj_ey: protecting the firmware, for one, I think
10:31svenand this is probably better implemented by the people (read: marcan/alyssa) working on DCP
10:32j_eymarcan: I dont follow
10:32marcanI think the DCP firmware is mapped via DAPF
10:32marcanwhich is locked together with the DART
10:32marcanso are some MMIO mappings, and that weird stream #15 backdoor
10:33marcanso clearly they're trying to protect DCP from the AP to some extent, much like DART protects the AP from DCP
10:33svenDAPF lock is a different bit than DART lock though i think
10:33svenand that #15 stream... for some reason it seems to be set to bypass to that other DART (sio i think) which also has a DAPF as well
10:34marcanso maybe the reason DART is locked is that #15
10:34sveneven more weird: that SIO DART cannot even read its first level pagetable. so maybe somehow that stream #15 is also involved in that
10:35marcanyou mean the pagetable is also locked out from the AP?
10:35svenif i setup the SIO DART as i usually would i get a fault with the "no ttbr" (and another unknown) error bit set on any access
10:36svenso somehow that DART cannot even read the pagetable. that DART/DAPF is also not locked so we can play around with it
10:36svenand it has the AES engine behind it which should make peeking into the device address space painless
10:36marcanthis is if you *don't* set #15 to bypass?
10:37sveni haven't tried what happens with #15 set to bypass yet fwiw
10:37marcanso you're saying the DART goes through the DART?
10:37sveni don't know. maybe. maybe not.
10:37svenit's just strange that the ADT also wants to set stream #15 to bypass for that DART
10:37svenand the DAPF is completely missing the in the ADT
10:38marcanwild idea: this is a VM thing and #15 is meant for a hypervisor to set up 2-stage DART translations
10:38svenhah, could be
10:38sventhat would be cute actually
10:39marcan"no ttbr" doesn't just mean TTBR is unconfigured, right?
10:39sveni thought it meant TTBR is unconfigured at first
10:39marcanthis sounds interesting, I'll probe around later
10:39marcanSIO DART, DAPF one page later as usual right?
10:39svenwaaaaiit... the thunderbolt DARTs also have #15 set to bypass. so.. uh... maybe to give the thunderbolt ports to a guest?
10:40marcanis there a DART features bit that just happens to be set on these DARTs (and not others)?
10:40svenah, no. acio is actually not the thunderbolt dart. my mistake.
10:41marcanacio is the thunderbolt *controller* dart
10:42marcansven: so on the DCP DART stream #15 is mapped out in DAPF to all RAM IIRC
10:42marcanmaybe SIO needs something like that
10:42marcanwould be interesting to copy some DAPF settings and poke around
10:43svenyeah, and as i said: the AES engine is behind SIO. let's see if i can dig up my old code to drive that one
10:44sveni never could get it to work without enable DART and DAPF bypass back then. but i didn't try much
10:44sven*enabling
11:07svenno idea if it still works. i last touched this in march or so
11:07svenanyway, back to $work for me
11:23arndmarcan: do you have any DT updates for 5.15 that you can send? This week would be great so I don't have to queue it into a 'late' branch. I haven't kept track of which drivers got merged since the original version that would need DT nodes
12:07marcanarnd: I *think* with DART that means USB should work, but there was a PHY binding thing, I think sven knows more
12:07marcanI've been neglecting the kernel side, I'll catch up this week
12:08marcanalso I might have to prioritize the clock stuff because even though nobody cares it's kind of important for DT correctness :)
12:08marcanI've been doing all the fun DCP/HV/etc reversing and alyssa wants me to look into graphics ASAP, but I think I need to spend some time getting all the non-fun stuff done for a change :p
12:15arndOk, good. Having USB working would already turn it from barely working into something one can actually play around with on an upstream kernel. I was originally hoping we could get PCI and NVMe in 5.15, but since NVMe certainly isn't getting in this time, I guess it will be 5.16 at the earliest for a mostly functioning system
12:16marcanyeah, sounds like it
12:16arndhttp://phb-crystal-ball.org/ tells me that 5.15 is the next LTS kernel that next year's distros will ship
12:19marcantbh I think it's wishful thinking to expect much from distros this early, but if we can get things in real nice shape for the *next* LTS, that's definitely something to aim for... :-)
12:21arndright, even if we had basic functionality in the kernel, there is not much point if distros don't come with an working installation method for the machine
12:21svenUSB would work, but just once per port because dwc3 only sees a single "device connected" event. to use a port twice we need to hook up something from SMC or the USB-PD chip to the not-yet-existing usb phy driver to issue a reset there :/
12:21marcanwe're mostly going to be handling installation for distros, at least initially, I expect
12:22marcani.e. dumping out a rootfs
12:22pipcet[m]sven: if the SMC knows...
12:22marcanarnd: how important is it to get the DT updates in for this round for whatever works so far, vs waiting until the other pieces fall in place a bit better?
12:23marcankeep in mind we have a backwards compat break ahead of us anyway in the power/clock driver stuff, which is why I really should push for that
12:23marcanuntil that's done we can't really hope for smooth upgrades
12:24marcanwhich is probably another reason why we shouldn't worry too much about distros shipping 5.15, too late for that
12:24arndmarcan: it's not important to me to have it in there now, I'm mainly interested in not getting a large pull request just before the merge window
12:24marcanah nah, if you're okay with leaving it for 5.16 we can just do it like that
12:24marcanI'd rather get back in kernel mode and start putting together pieces, maybe write a few drivers
12:25marcanand seeing how much of that I can get into 5.16
12:25marcanthere's lots of little loose ends to be tied
12:25marcansven: no i2c still either, right?
12:25marcan(upstream I mean)
12:25svenuh.. i have some WIP i2c somewhere, but i never event sent that for review anywhere
12:26marcanI can take over that if you want
12:26marcani2c and spi are dumb things we should tick off
12:26marcanthat then makes the keyboard work, and the USB-PD stuff doable
12:26svenyeah, i think i2c, spi and at least the clocks-gates would be very useful
12:27marcanalright, if nobody else wants to take those, after I get the installer PoC done I'll get in kernel mode for a while and work on that
12:27marcanshould get there this week
12:27sventhere's also gpio/pinctrl iirc
12:27marcanwe never settled on the issue of the clock dependencies, right?
12:27svennope :(
12:27svenand it gets more fun: some clocks have two parents
12:27marcanalright, then it's gonna be whatever I can come up with :p
12:28svensounds good!
12:28marcanwe've had enough chitchat, time to throw implementations at people and figure out if they stick
12:29svenhttps://github.com/AsahiLinux/linux/tree/i2c/dev that's what i had for i2c. iirc i wasn't happy with that yet
12:30marcandid we ever figure out if spi is a thing that already has a similar driver? IIRC it was "samsung stuff" but I wonder if it's like UART or not
12:31sveniirc there are two kexts: samsung and apple. no idea if the apple is just a new variant of the samsung one or a completely new thing
12:34marcanstrings suggests it does dma, but there's no DART... I'm going to assume they don't actually use that here
12:34pipcet[m]not for the keyboard, no.
12:35jannauI have time this week and will continue working on pinctrl/gpio
12:35marcanspi-s3c24xx.c matches at least *one* of the register names
12:36marcanI'll just hvtrace it and see how close it is
12:36marcanjannau: cool!
12:41chadmedwhen i said the other day that we should "force" everyone to just use gentoo, i was only half joking. it might be a good idea to try and get gentoo's arm team on board wrt testing and general liason work. it's an easy starting point since rn the only userspace changes needed would be to add an "agx" VIDEO_CARDS flag for mesa
12:42marcanthat driver has a bunch of fake FIQ DMA stuff we are definitely not using, and doesn't mention FIFOs which apple's controller has, so this might be a good case for writing a new driver rather than trying to shoehorn apple mode into that one
12:42marcanbut we'll see
12:42marcanchadmed: I'm a gentoo user fwiw :)
12:42chadmedlikewise, its why im shamelessly shilling for early gentoo integration heh
12:42marcanbut gentoo is easy, just have an overlay
12:43chadmedwell yeah of course, but having the
12:43chadmed"blessing" of a big distro and the eyes of the arm maintainers might encourage the binary titans to sit down at the table sooner too
12:44marcanis gentoo even "big" any more? :-)
12:45marcanbut sure, I'd be happy to have some of the gentoo ARM folks around
12:48TheLinkIsn‘t ChromeOS based on Gentoo?
12:48marcanit's basically a fork IIRC
12:49TheLinkThat would make it huge 😊
12:49chadmedyeah but its like calling android linux. sure, it uses the linux kernel but its pretty philosophically incompatible with what one would call a linux system
12:50chadmedthat GNU/Linux copypasta unironically makes a pretty salient point lmao
12:51chadmedchromeos might use portage or whatever but do you really have all the tools and power at your disposal that distinguishes gentoo from any other distro? i would argue that having those tools in the first place would be ridiculous on a chromebook, building a vanilla gentoo install with plasma is sad enough on a pi4 8gb let alone a chromebook
12:53archadmed: it might be an unpopular opinion here, but I'm kinda glad I no longer use gentoo (despite using it for ~15 years)
12:54chadmedyeah its not for everyone, and most would probably become fatigued by it. fwiw samba's hard dependency on libunwind still breaks my clang-only portage setup every time i sync the repos, meaning i have to manually edit the ebuild to accept llvm-libunwind at least once a week :P
12:54chadmedthats starting to wear on my nerves
12:55ari recently even considered trying gentoo out again, but then i learned that on a friends pc that's mostly similiar to mine in terms of specs, chrome still (or rather, again) takes a bit over an hour to compile
12:56chadmedthree things a certain in life; death, taxes, and chrome taking over an hour to build from source
12:57arfor a while, on a ryzen 2700x and enough ram (for tmpfs), it took around 40-50 minutes
12:58tophevich[m]how long for firefox?
12:58artophevich[m]: when i stopped using gentoo, it was about 15 minutes
12:58ar(on a 2700x)
12:58chadmedfirefox takes me about 15-25 mins on a 5600x with 16gb 3400mbps 14-14-14-14-28
12:59aron a 5950x i have now, i'd expect it to still take around 10-15 minutes, because huge parts of the firefox build don't parallelize well
12:59chadmedyeah, plus the amount of rust that now makes up firefox
13:00chadmedrustc is not very good
13:00tophevich[m]can't live without chrome? or why take that compile time penalty all the time?
13:02chadmedyea idk youd willingly use chrome let alone build it but such is the beauty of gentoo, the "to each his own" principle taken to comical heights
13:02chadmeds/idk/idk why/
13:26pipcet[m]alyssa: FWIW, with the asahi/devel branch I have both a usb gadget console and a usb keyboard now, simultaneously. was it just eem that was broken?
13:34jeff_miw has joined #asahi
13:38jeff_miwmarcan: regarding spi and i2c, I'll be happy to help with some guidance, I need to catch-up to bring something useful. Is the devel branch the right one to start from ?
13:41jeff_miw has quit [Remote host closed the connection]
13:50amwFor what it's worth I was trying to use shell to test pinctrl + spi3 to get to the keyboard
13:51amwBut I found the keyboard uses large 256 byte, crc'ed messages so it's quite a lot of work to get some keyboard input via that
13:52amwI was just trying to use info in the corellium drivers and I think it was kind of talking to the spi3 and possibly pinctrl - no interrupts
13:53amwFor what it is worth I have pasted some very hacky notes at https://paste.debian.net/?show=1207032;lines=0
13:54amwPretty useless mess at the moment, but with a few more days of work might do some non-interrupt driven transfers, proof concept
13:55amwI don't really understand how to get the interrupts to report under shell.py so I ignored them - but that might be a good way to check things are working
13:56amwTime for bed and see if anything happens by tomorrow...
14:02Andalu30 has joined #asahi
14:02yuyichao has quit [Ping timeout: 480 seconds]
14:20arndmarcan: for the spi driver, I see some resemblance between its registers and both the s3c24xx and s3c64xx drivers, but it does seem different enough to need a third driver.
14:21yuyichao has joined #asahi
14:21arndIf someone wants to push corellium's driver, that might actually work in this case, it seems well written, and fairly simple, much smaller than the two samsung drivers that implement DMA mode
14:43arndI just looked at all the other spi drivers to see if there was a closer match: it looks like half the drivers in the kernel have roughly the same design, with config/status/transmit/receive registers in that order, but they all have them at slightly different offsets, and with slightly different bit definitions, so the similarity to the s3c driver may just be coincidence
14:44arndor the hardware designers all read the same book on the topic
14:44skipwich has quit [Quit: DISCONNECT]
14:44skipwich has joined #asahi
15:02Andalu30 has quit [Remote host closed the connection]
15:06Andalu30 has joined #asahi
15:20skipwich has quit [Ping timeout: 480 seconds]
15:22Raito_Bezarius has quit [Ping timeout: 480 seconds]
15:30Raito_Bezarius has joined #asahi
15:31skipwich has joined #asahi
15:36Andalu30 has quit [Ping timeout: 480 seconds]
15:48DarkShadow44 has quit [Quit: ZNC - https://znc.in]
15:50DarkShadow44 has joined #asahi
15:51DarkShadow44 has quit []
15:51DarkShadow44 has joined #asahi
15:53DarkShadow44 has quit []
15:54arndsven: well, duplicating that nvme driver at least makes it easier to get the initial version merged
15:54DarkShadow44 has joined #asahi
15:54arndI guess you can start with a copy of the code you already have, and then remove everything that isn't currently getting used.
15:55DarkShadow44 has quit []
15:55DarkShadow44 has joined #asahi
15:58svenyeah. the bigger issue is probably that i'm not really sure how to handle that mailbox part yet.
15:58svenessentially there's a low-level dumb mailbox interface backed by some hardware FIFO.
15:58svenand then most of these sub-processors have some shared endpoints (management to boot them, syslog, etc.). the code to handle that doesn't seem to really fit into drivers/mailbox
16:02svenand because that's not fun enough these endpoints require shared memory buffers that sometimes go through a DART IOMMU, other times through a simple DMA address filter Apple calls SART (that's where these HMB buffers are configured) and other times the shared memory is just exposed on the MMIO bus
16:04arndsven: what is the mailbox needed for in case of nvme?
16:04svenjust to boot the co-processor
16:04jeffmiw has joined #asahi
16:04svenwhich requires syslog, etc. to be up.
16:05sventhe nvme mmio interface we see is emulated by the firmware running on that processor
16:05pipcet[m](I think it requires just the panic EP, but that's bad enough)
16:06svenin my current hack those endpoints are just implemented in my mailbox driver and that 0x20 channel i request in the nvme code is a lie
16:13jeffmiwjust lost a couple of hours fixing my python install to get correct python 3.9 and latest construct module ... to chainload latest m1n1 mainly because I'm using an old ubuntu 18.04 distrib :). I thought it is a good time to ask: which distrib are you using for your dev for M1 ?
16:47marcansven: honestly I'm leaning towards ignoring mailbox/etc and just doing our own driver
16:47marcanit doesn't seem useful to use an abstraction for us
16:47marcannothing says we have to use kernel abstractions
16:48marcanthose abstractions are only useful when they either provide enough useful primitives to reduce code, or existing higher level drivers can hook into the interface
16:48marcanneither seems to be the case here
16:48Andalu30 has joined #asahi
16:48marcannothing other than apple stuff is ever going to use the ASC driver
16:48marcanand apple stuff is never going to use another mailbox driver
16:50svenSEPOS uses the same dumb mailbox HW but not the RTKit stuff. and iirc acio or something uses a slightly different dumb mailbox interface but the same RTKit stuff again
16:51marcanyeah, so all those can be variations in one driver
16:51svenso it might make sense to reuse the mailbox interface but build some custom abstraction for the RTKit stuff, but dunno
16:52marcanlike, we can have the core mailbox/ep handling stuff, that is instantiated by downstream drivers that actually handle devices like DCP
16:52marcanand as part of that they instantiate the default endpoints, or not
16:52marcanit doesn't even really need to be a driver
16:52marcanit would just be a library
16:52marcanthe drivers would be DCP, ANS, etc
16:52svensure, that's also fine
16:53svenANS could also just special-case that SART stuff then and SMC the MMIO shmem buffers
16:53marcanjust tell the library not to use a DART but something else instead
16:53marcanthere's many ways to do this once it's our own code everywhere
16:54svenDART is transparent through the dma_map_ops anyway
16:55marcanyeah, we justr need a separate hook for SART
16:56pipcet[m]I think a basic (tiny) mailbox driver exposing the dumb 128-bit mailbox still makes sense, marcan's library or whatever can talk to that.
16:56svenand those MMIO shmem buffer need special treatment as well
16:58svenpipcet[m]: maybe, but i'm not 100% convinced about that. the mailbox driver implements a fifo and is usually used for even dumber mailboxes. apple's hw at least has a HW fifo that's 16 messages or so deep
16:58j_eymarcan: wow, i seem to be doing really dumb stuff all the time. earlier I was passing the uncompressed initramfs, now I was passing: Image dtb dtb-from-m1n1 initramfs, and getting very confused why none of my dtb changes were doing anything :||
16:59svenand the mailbox driver also assumes that all endpoints are separate, but on the m1 they all go to the same FIFO anyway. now that can all be worked around and maybe that's worth it
16:59sveni'm just not convinced it's a good fit
16:59pipcet[m]sven: no, the mailbox driver would not know anything about endpoints.
16:59pipcet[m]it'll expose a single channel for the library to use.
16:59svenok, sure
17:00sventhat only leaves the fifo thing then. might be worth it, dunno
17:01pipcet[m]my driver only queues one message at a time at the hw level, I'm not sure it's worth it to do something more complicated.
17:03pipcet[m]so then the FIFO becomes useful because it makes writing the library easier, as long as MBOX_TX_QUEUE_LENGTH is greater than the number of endpoints used in parallel.
17:03DarkShadow44 has quit [Quit: ZNC - https://znc.in]
17:05svenbut then we always need to wait for an interrupt to deliver every single message, don't we?
17:05DarkShadow44 has joined #asahi
17:28Andalu30 has quit [Ping timeout: 480 seconds]
17:43pipcet[m]only to tell us transmission is done
17:44pipcet[m]which we need to know because some messages have no response.
17:44marcanwhat is the benefit of using the mailbox interface?
17:44marcanjust the FIFO?
17:45marcanmight make sense to use, but I need to look at the framework to convince myself
17:46marcanalso, if it's instantiated separately, that still leaves the issue of the cpu boot and other things we might need to do, which might end up outside of the mailbox driver's API
17:47marcanpipcet[m]: is there any case where we need to know that message transmission is done? that sounds wrong.
17:47pipcet[m]they should, yes. this just takes away the tiny part that we have a good abstraction for, but it's a clear fit
17:47pipcet[m]marcan: endpoint startup
17:47marcanyes but why do we need to wait for anything?
17:47marcanit's a fire and forget message
17:47pipcet[m]>16 endpoints?
17:47pipcet[m]more than, sorry.
17:48marcanwell sure, but that's just a standard FIFO thing, nothing about specific messages
17:48marcanif the FIFO is full we block until IRQ
17:48marcanstandard queueing stuff
17:48arndthe mailbox framework is a little strange in the way it works, but for this particular use case it actually sounds like a good fit to me, just exposing a fixed-length message fifo
17:48marcanmessages would be 64+8 bits, probably 64+64 in practice
17:49arndthe main advantage of the mailbox framework is that there is an existing DT binding to describe how the various endpoints related to the shared mailbox driver
17:49marcanbut we can't use those endpoints
17:50marcanthere will be a single endpoint
17:50marcandue to the architecture mismatch
17:50pipcet[m](I'm also hoping for some debug features to make their way into the mailbox framework.)
17:50marcanso it's going to be 1:1 an RTKit-lib driver and the mailbox, in every case
17:50marcan(except SEP which won't use that lib probably)
17:50marcanthe endpoints are at a level that is the driver's responsibility
17:50marcanif we want separate drivers for this, which we might, that will have to be our own thing with another layer
17:51marcanI'm not sure yet if we do though
17:51marcanApple certainly does things that way
17:51marcanand DCP has a pile of endpoints for different drivers
17:52marcanso that might be a good argument for a bespoke driver, if we actually want to have this be a DT node with multiple clients, the same way apple does it
17:52pipcet[m]marcan: well, what I did, but you're going to hate it and I haven't decided whether I do, is have a funnelling driver that provides one mailbox per endpoint and consumes the single-channel mailbox (with its two different implementations), providing infallible FIFO'd mailboxes to the endpoint drivers.
17:53marcanyeeeeah let's not do that :p
17:53marcanthe thing is, at some point we might have ordering requirements between endpoints
17:53marcanor some bullshit bug to work around related to that
17:54marcanand if we do it like that that's just too many layers to the onion
17:54marcanand do we even need the FIFOs? honestly I think the hardware FIFO is sufficient
17:54marcanthings will block if they need to and that's okay
17:54marcanthe kernel knows how to block
17:58pipcet[m]the main point for me is not to hide in the DT the fact that communication uses a piece of hardware clearly identified as a mailbox, which behaves like a mailbox. The secondary aspect is that the mailbox abstraction might evolve to actually be useful, by including debug facilities.
17:59pipcet[m]and for debugging and performance analysis, we need to know when a message has arrived at the ASC end...
18:05svenfwiw, it's also not too bad to have the mailbox driver already correctly expose the channels and mux them into the single fifo
18:05svenit's just.. a little bit awkward
18:06svenregarding debug feature for the mailbox framework: i used tracepoints because i was sick of spamming dmesg with every single message and that worked out quite nicely
18:06svenand either way i'd move the cpu control register (which is like a page or so away from the mailbox regs) out of that mailbox driver
18:08pipcet[m]you need to have an endpoint to know how many endpoints there are, though :-)
18:08marcandoes the CPU need to be running for the mailbox to work?
18:08pipcet[m]no, mailbox just queues stuff
18:09svenuh, why do i need an endpoint to know how many endpoints there are?
18:09pipcet[m]because the endpoint map comes in over endpoint 0?
18:09marcanthe endpoint map is not useful
18:09sven^-- that
18:09marcaneither we have a driver that wants an endpoint, or we don't
18:09sventhe endpoint map would be the responsibility of the rtkit lib
18:10sventhe mailbox driver would be very dumb
18:10svenliterally just "take this message, get the endpoint from the client priv data, stuff it to the fifo"
18:10marcananyway, I'm talking out of my ass right now since I haven't even looked at any of the code
18:10marcanand I need to go to sleep
18:10marcanonce I get a look at that mailbox framework I might have to start shouting the right answer :p
18:10svenyeah, right
18:11pipcet[m]marcan: good night, then, and thank you. I think you've actually convinced me with the rtkit library stuff :-)
18:12tophevich[m]marcan: Have a good refreshing night sleep, vax side-effects all gone?
18:12marcanah, yeah, that was only the t+[12h, 36h] interval
18:13pipcet[m]sven: speaking of mailboxes (not dumb ones though) and queue depth, how many PRs does it make sense to keep open on asahi/devel at once? I'm not planning to open more unless you explicitly request it
18:14marcanwe really shouldn't have any PRs on asahi/devel
18:14marcanthat branch ought to become an auto-merge
18:14svendunno, but i think that first one could actually be sent to the 'real' upstream at this point
18:14marcaninstead features should be developed on feature branches and upstreamed from there
18:14svenwe should have PRs somewhere though for quicker internal review
18:14svento catch common mistakes, etc.
18:14marcanyes, but against the feature branches
18:15svensure, but for now devel works.
18:15marcanand we can have a stupid fixes branch if we need one for things that don't fit nicely anywhere else
18:15marcansure, but I'm about to change that, likely this week :-)
18:15svensounds good :)
18:15tophevich[m]"asahi-next"
18:15sventhen i guess we'll keep the PRs open for now
18:15marcanit'll be a new branch, but devel will probably be deprecated
18:16marcanmight end up moving those PRs elsewhere, depends
18:16marcanI reserve the right to tear apart the branch scheme of that repo :D
18:16svenwe just created that branch yesterday, feel free to remove it again :D
18:16svenit's literally just rc3 + dart or so
18:16marcanyeah, so that should be asahi-next :) (once I have the automation)
18:17svensounds good
18:17pipcet[m]I'm happy any way, just let me know what you decide on
18:17marcan(which *grumble* is going to involve a stupid webhook reflector hosted on my server, because github seems to have no way to point webhooks at itself, nor to have actions run *without* the workflow file in the current branch)
18:17marcan(and I don't want to pollute our kernel trees with github workflows)
18:17svenpipcet[m]: anyways, feel free to open more PRs for now
18:18svenmaybe i should actually open one with the dumb mailbox with N channels things so that we have some actual code to discuss and see how things fit
18:19marcanif y'all want to prototype a few of the approaches, that will give us more data
18:19marcanand this all seems simple enough anyway
18:19svenpipcet[m]: might make sense to open one with the "0 channels as well"
18:19marcanmeanwhile I'll work on the installer, merge infra, and tying up i2c/spi/clocks
18:19svenyeah, it's like 1 fix for the aic-irqchip (if you disable irq N while you're in the handler for N you can never enable it again) + 300 lines of code or so
18:20marcanthe aic fix is probably a good thing to send upstream asap anyway
18:20marcanbut anyway, I should sleep :)
18:20sveni'm not sure it's correct yet, but yeah :D
18:20sven(as in, i haven't traced through all the code to know why it works. i just have a good guess)
18:20pipcet[m]marcan: I started writing pseudocode and stopped when I ended up with a working brightness backlight driver, but it's, uhm, prototype quality code at best and totally faked its way around the dcp dart.
18:21tophevich[m]marcan: any plans to stream your endeavours again in the near future? (Your streams are currently my fav. procrastination excuse, and I feel like I need that or a holiday :D)
18:21marcantophevich[m]: I'm still streaming, I did some last week
18:21marcanlikely one tomorrow
18:22tophevich[m]nice, I'm gonna watch out for it, realy enjoing those!
18:23marcanI'm still amazed people like watching me hmm and haw while spending hour trying to make stuff work :-)
18:24j_eytalking about marcans streams, is there a way to increase the font size on the simple-framebuffer?
18:24marcanah, like the m1n1 console?
18:24j_eyno, once Linux takes over
18:24marcanhaven't done that recently though
18:25marcanbut there are several built in fonts, yes
18:25marcanI think there's a larger one for retina stuff these days?
18:25tophevich[m]you are good at narrating, and thus it makes it realy nice to follow along your workflow/thinking. also you have a good narration voice :)
18:25j_eyhm ok, I'll have a poke around, I keep having to squint to read it
18:25j_ey(locally I mean)
18:25marcanin the stream?
18:26pipcet[m]j_ey: the retina font is nice and large, should be easy enough to use that :-)
18:26marcanj_ey: CONFIG_FONTS and descendants
18:26j_eypipcet[m]: is that in menuconfig?
18:26marcanCONFIG_FONT_TER16x32 perhaps
18:27pipcet[m]oh, you meant the linux framebuffer, sorry. For the kernel just compile in a large font and you'll be fine, it's what my .config does.
18:27svenhttps://github.com/AsahiLinux/linux/pull/6 so that's essentially the mailbox thing that just exposes N endpoints and muxes them to the single FIFO + some (maybe) hack to the mailbox core to introduce a fast-path for submission
18:27j_eyoh I see it now, ty, will try it
18:32j_eywhen I try `bt` I never get an actual backtrace :/ even after loading the system map and setting the pac mask, I always get _end. amw have you had any recent success with bt?
18:32JTL> 18:23 <@marcan> I'm still amazed people like watching me hmm and haw while spending hour trying to make stuff work :-)
18:32JTLsudoku for nerds :D
18:32tophevich[m]marcan: your streams are very educational and also are most likely very good for growing a support for the project, I think SerenityOS and Zig (lang) are good examples of projects, where (main) contributers streaming/showing of the work gives the project a nice "human face" that gives supporters a greater (closer) sense of community.
18:32tophevich[m]Also they give ppl confidence to try stuff they thought impossible, as they see them being done infront of their eyes. If you see that mount of work only as a finished product, it seems impossible.
18:33marcanI guess that's true :)
18:33marcanalso I don't know about my voice, but at least I can be reasonably proud of my audio quality :p
18:33JTLI like your accent
18:33DarkShadow44 has quit [Remote host closed the connection]
18:34marcanyou mean my american-spanish-irish-plus-alpha accent?
18:34etaitt: everyone crushing on marcan
18:34eta(in all seriousness though, the streams are indeed awesome!)
18:34JTLeta: no u
18:34DarkShadow44 has joined #asahi
18:35marcanwell I'm glad everyone enjoys them then :)
18:35marcanalright, really though, zz
18:40tophevich[m]alyssa: Btw. I enjoy your streams also quite a lot. Wouldn't mind to see you stream more often. Also very educational, good at narrating along, plus a good sense of humor :)
18:43marcantophevich[m]: is she in here? if so, one of us is desynced...
18:44marcan has left #asahi [#asahi]
18:44marcan has joined #asahi
18:44marcan... not me I think :)
18:44marcanshe's in -dev though
18:45etathat kind of desync would be impressiv
18:58alyssa has joined #asahi
18:58marcanit happens sometimes with IRC clients, especially with a bouncer in the way to muck things up
19:00krbtgti like the fact there's videos for audiovisual people but i do like projects with like a good progress report too
19:01krbtgtas someone who doesnt want to watch a video zig and serenity putting out videos is harder for me
19:01alyssamarcan: she's omnipresent and omniscient
19:06tophevich[m]yes, yes she is xD
19:07alyssapipcet[m]: hm, will try again. maybe I botched something with my config
19:07tophevich[m]marcan: sorry for the confusion, I was not looking if she is online, I was just counting on her reading it at some point
19:13alyssatophevich[m]: thanks :) maybe soon
19:16jixafter trying to stream coding (completely unrelated to asahi) myself, I have even more respect for both of you for your streams
19:22erincandescent has quit [Remote host closed the connection]
19:23erincandescent has joined #asahi
19:34svenyeah, i couldn't even imagine to code and stream at the same time
19:34svenand then make it all seem to effortless like you two
19:35jixthe coding part works for me... the debugging part also works for me... the "oh shit this approach won't work, I need to think about what to do instead" part doesn't work at all ^^
19:37j_eypipcet[m]: hmm I'm getting a data abort in gpio_set_reg, when i try to enable the keyboard :/
19:37j_ey(using your branch, and a cut down dtb)
19:38pipcet[m]using which branch? Probably some clock that's not enabled...
19:38j_ey'pearl'
19:38j_eyI have the spi3/keyboard node, and all clocks and pinctrls that those reference
19:39pipcet[m]oh, sorry. not really asahi, but you need to pass clk_ignore_unused I think
19:40pipcet[m](in the kernel command line .. this is where we all give marcan a hand for wanting to look at the clk stuff :-) )
19:40j_eyhm ok, I'll try that!
19:42pipcet[m](I'm running pearl right now and it works, but then I booted through the .macho and the first thing that does is (try and fail to) enable all the clocks :-) )
19:49PhilippvK has joined #asahi
19:53phiologe has quit [Ping timeout: 480 seconds]
20:29quarkyalice has joined #asahi
20:42quarkyalice has quit [Remote host closed the connection]
20:42quarkyalice has joined #asahi
20:55skipwich has quit [Quit: DISCONNECT]
20:55skipwich has joined #asahi
21:12jeffmiw has quit [Ping timeout: 480 seconds]
21:18phiologe has joined #asahi
21:22PhilippvK has quit [Ping timeout: 480 seconds]
22:11amwj_ey: bt under run_guest has worked for me - except when I had CONFIG_RANDOMIZE
22:12amwYou can look at bt() in proxyclient/m1n1/hv.py around line 821 and try dumping out the registers it mentions
22:12j_eyah, I'll turn that off then
22:13amwe.g. hv.ctx.regs[29] et cetera to see what's actually go on
22:13amwThat can be called directly at the shell
22:16j_eyyeah, I had a play with that
…