#asahi-gpu · 2022-06-27 21:36
khronokernel[m]s/thatnk/thank/#asahi-gpu · 2022-06-27 21:36
khronokernel[m]<balrog> "khronokernel: unsupported macs..." <- Yeah I am one of the authors of OpenCore Legacy Patcher ;p... (full message at https://matrix.org/_matrix/media/r0/download/matrix.org/EFFUSBmuGLrLPZkiTOzExDLg)#asahi-gpu · 2022-06-27 18:58
balrogbut we're already way offtopic :)#asahi-gpu · 2022-06-27 18:57
balrogkhronokernel[m]: unsupported macs (well, opencore patcher specifically) is related to backporting stuff from older OS to newer OS to bring back support for older GPUs#asahi-gpu · 2022-06-27 18:37
khronokernel[m]Unsupported Macs discord isn't really related to newer OS development, was hoping to find other groups that might've researched it#asahi-gpu · 2022-06-27 18:37
khronokernel[m]<balrog> "khronokernel: that's really..." <- Unfortunate but understandable#asahi-gpu · 2022-06-27 18:29
balrogkhronokernel[m]: that's really out of scope for Asahi... you'll probably have better success on the Unsupported Macs discord#asahi-gpu · 2022-06-27 17:41
khronokernel[m]Hello, I hope this is the right channel to ask.... (full message at https://matrix.org/_matrix/media/r0/download/matrix.org/FMDWxQuERUKgxktIqeCgIySI)#asahi-gpu · 2022-06-23 10:55
cr1901Sobek[m]: Re: "apart from mrustc", mrustc is a bootstrap compiler- it's not intended to compile all the world's existing Rust code. Rust devs don't seem to have a problem w/ _that_.#asahi-gpu · 2022-06-21 17:59
Sobek[m]<cr1901> "The gcc backend is much more..." <- Apart from mrustc ?#asahi-gpu · 2022-06-21 16:29
_jannau_lina: FYI https://www.phoronix.com/scan.php?page=news_item&px=Rust-For-Linux-5.20-Possible#asahi-gpu · 2022-06-21 16:12
cr1901The gcc backend is much more likely to survive in the long term than the front end IMO. I can't speak for the Linux ppl, but a lot of rust devs Just Don't Want an alternative frontend impl existing#asahi-gpu · 2022-06-21 09:05
Sobek[m]The GCC rustc backend / Gcc rust frontend work were important pieces that were required for rust inclusion got considered seriously.#asahi-gpu · 2022-06-21 09:05
Sobek[m]Unless you have patches somewhere about Zig in Linux. Also as far as I know, Zig doesn’t bring to the table anything like rust’s guarantees, and is also a LLVM based language.#asahi-gpu · 2022-06-21 09:03
Sobek[m]Hmm, unlikely I think#asahi-gpu · 2022-06-21 08:58
alethkitIt would be quite funny if Zig manages to reach 1.0 and get accepted into the kernel before Rust does due to superior ergonomics.#asahi-gpu · 2022-06-20 18:47
Sobek[m](I’ve read something suggesting that it is likely getting merged in 5.19 to be precise)#asahi-gpu · 2022-06-20 18:44
Sobek[m]Isn’t rust in Linux getting merged in the next version ?#asahi-gpu · 2022-06-20 14:18
linaI'd also be open to starting work in C and then starting to sneak Rust in once it goes upstream, if that isn't ready in time.#asahi-gpu · 2022-06-20 14:15
chadmed_it would merely be cool if things did line up fortuitously so as to allow a high quality, upstreamable driver to be written in rust#asahi-gpu · 2022-06-20 14:14
_jannau_merge window for 5.19++ should be closed by end of july#asahi-gpu · 2022-06-20 14:14
chadmed_i didnt mean that we should any% a rust driver just for the sake of it/bragging rights, that would of course be ill advised#asahi-gpu · 2022-06-20 14:13
chadmed_alyssa: "flex" might have been a slightly too loaded word :P#asahi-gpu · 2022-06-20 14:09
linaSo then it depends on what state Rust is in by then, and how I feel about it.#asahi-gpu · 2022-06-20 14:09
alyssaThat's fair#asahi-gpu · 2022-06-20 14:09
linaSo I would say mid august-september for a sensible timeline for actually starting to work on a real driver. And then, if I'm right about how I'm doing things, it should go very quickly since we'll understand this GPU enough.#asahi-gpu · 2022-06-20 14:08
linaRealistically though, I'm going to be off a couple weeks next month, and there is still work to be done figuring out how this thing works before I'm comfortable starting to hack on a real driver, especially a C driver (C is definitely more painful to refactor than Rust)#asahi-gpu · 2022-06-20 14:06
linaWe're definitely not going to gate the driver on hopes and dreams of Rust getting upstreamed, that's a hard dependency for taking that path.#asahi-gpu · 2022-06-20 14:06
alyssa(Or more to the point, running userspace on bare metal Linux without drm-shim hacks)#asahi-gpu · 2022-06-20 14:06
alyssasure#asahi-gpu · 2022-06-20 14:06
linaIt doesn't, but nor does Rust if it's already upstream#asahi-gpu · 2022-06-20 14:05
linaThe kernel does a terrible job at that in all the exceptional cases, just try yanking a Thunderbolt cable and seeing how many different NULL derefs you manage to hit...#asahi-gpu · 2022-06-20 14:05
alyssaFinalizing the UABI doesn't block merging into asahilinux/linux and shipping to users ..#asahi-gpu · 2022-06-20 14:05
linaOOP C isn't that bad, but object lifetime management in C *is* bad.#asahi-gpu · 2022-06-20 14:04
linaAnd besides, with the UABI to work out before it can go upstream, it's not like writing it in C would get us there quickly anyway... and all that time spent working out the UABI is also time to figure out Rust things (if, and only if, Rust support is already in by the time we start, of course)#asahi-gpu · 2022-06-20 14:04
alyssaOOP in C isn't that bad#asahi-gpu · 2022-06-20 14:03
alyssathis is "old man [young girl] C programmer yells at cloud [newfangled language]" i admit :p#asahi-gpu · 2022-06-20 14:03
alyssaI guess so#asahi-gpu · 2022-06-20 14:02
linaI'm not saying it's the right choice, but I'm saying I don't want to dismiss it from the get-go#asahi-gpu · 2022-06-20 14:02
linaYou've seen the Python driver, the design has a lot of very object-oriented concepts going on at the firmware ABI level. It could a better fit for rust, especially managing the lifecycle of all those things...#asahi-gpu · 2022-06-20 14:01
linaI care about the driver working properly, and if Rust helps us get there faster and with fewer bugs...#asahi-gpu · 2022-06-20 14:01
alyssaI care more about getting stuff working upstream than making "neat" engineering decisions, IDK#asahi-gpu · 2022-06-20 14:00
alyssaI guess#asahi-gpu · 2022-06-20 14:00
linaAssuming Rust support makes it in before we start#asahi-gpu · 2022-06-20 14:00
linaIt doesn't have to all be Rust or even have bindings... we don't know how much it makes sense to write in Rust yet#asahi-gpu · 2022-06-20 13:59
alyssaand even for a 3D-only driver it'd be a pile of bindings work to do acceptably#asahi-gpu · 2022-06-20 13:59
alyssawe're a community backed reverse-engineered driver. getting it working upstream at all is enough of a flex.#asahi-gpu · 2022-06-20 13:59
alyssathat's not a trophy we want. we do want the "it works at all" trophy.#asahi-gpu · 2022-06-20 13:59
alyssa-1 on being the first rust drm driver in the kernel#asahi-gpu · 2022-06-20 09:46
_jannau_so the solution will be to hanle each dcp as crtc but I'm unsure if the drm helpers can easily deal with crtc with separate IOMMUs