#asahi-gpu · 2022-09-27 10:44
boulabiar[m]contact*#asahi-gpu · 2022-09-27 10:43
chadmedsmdh are we gonna have to start preparing press material #asahi-gpu · 2022-09-27 10:43
boulabiar[m]I've also seen an article claiming that Linus ported Linux into the M1 by himself. The solution would be to directly connect the author about the article or in the comments section.#asahi-gpu · 2022-09-27 10:42
TheLinkjust a clickbait headline#asahi-gpu · 2022-09-27 10:41
TheLinkwell, at least they clarify it in the text#asahi-gpu · 2022-09-27 10:41
boulabiar[m]I hope they don't report the same way about winter energy problems#asahi-gpu · 2022-09-27 10:41
jannauthe author published at least one bad apple silicon/linux article before but not quite as bad as this one#asahi-gpu · 2022-09-27 10:40
TheLinkif it was heise, I wouldn't have expected any better#asahi-gpu · 2022-09-27 10:39
TheLinkuh, quite disappointing this coming from golem.de#asahi-gpu · 2022-09-27 10:37
jannausigh, a german tech news site claims that the M1 GPU linux driver is now available. It's not just the headline. the article claims the driver was released in the 1st paragraph#asahi-gpu · 2022-09-24 12:35
Tramtristabsolutely#asahi-gpu · 2022-09-24 10:06
kode54hope you had a good rest#asahi-gpu · 2022-09-24 10:06
kode54welcome back to the world of the living#asahi-gpu · 2022-09-24 09:03
linaThank you <3#asahi-gpu · 2022-09-24 09:03
lina^^;;#asahi-gpu · 2022-09-24 07:00
chadmedim still awestruck by what an unbelievably mammoth effort lina put in last night/this morning. absolutely unreal youre an inspiration to us all (health concerns notwithstanding heh) #asahi-gpu · 2022-09-24 00:22
Tramtristwait .. what.. ? How can the stream still be going?#asahi-gpu · 2022-09-24 00:01
zzywysm_lina: are you remembering to hit Ctrl-Alt-F7 to switch to the rendered cube?#asahi-gpu · 2022-09-21 19:41
linajannau: It's okay! I'm rebooting for every test anyway so... ^^#asahi-gpu · 2022-09-21 18:48
jannaulina: sorry about the dcp crash, it's the method to clear the active surface. it seems to work on the mbp 14" but not on the mac studio/mini#asahi-gpu · 2022-09-17 07:47
jannauyes, I haven't seen firmware updates changing this yet. it's a constant address range per SoC#asahi-gpu · 2022-09-17 07:27
linaBut the GPU has a whole bunch of per-SoC parameters, so I don't think it's practical to try to make it generic across SoCs with just DT changes...#asahi-gpu · 2022-09-17 07:27
linaI think for DCP it makes sense to keep that in the DT, since I think the DCP interface is mostly the same for every SoC, at any given firmware version?#asahi-gpu · 2022-09-17 07:26
linaThat's different from the GPU though. For the GPU, the driver just maps everything ahead of time and tells the firmware what the virtual addresses are.#asahi-gpu · 2022-09-17 06:48
jannauthe coprocessor requests the mapping by index (into apple's regs array)#asahi-gpu · 2022-09-17 06:47
jannauthe in progress DCP driver maps 1 "foreign" (iirc pmp) address range for the co-processor. So far it is in regs as that's what apple does in their device tree#asahi-gpu · 2022-09-17 06:04
linaRight now it's hardcoded like this: https://github.com/AsahiLinux/linux/blob/gpu/rust-wip/drivers/gpu/drm/asahi/hw/t8103.rs#L23#asahi-gpu · 2022-09-17 06:04
linaNote that the driver doesn't use any of those mappings, it only directly uses the firmware coprocessor mailbox/start stuff, and the GPU registers directly in special cases (those would be in the DT as regular reg entries)#asahi-gpu · 2022-09-17 06:02
linaAnd since currently we don't mess with the device tree based on firmware in the bootloader, that's probably an argument *not* to include it? Since it would require more complex firmware -> DT mapping in m1n1#asahi-gpu · 2022-09-17 06:01
linaThis can also somewhat change between firmware versions, but the driver also needs explicit support for each firmware version so being flexible there also doesn't help#asahi-gpu · 2022-09-17 06:01
linaThis is different per SoC. Since I think the driver will need explicit support for each SoC anyway, I'm tempted to just hardcode it in the driver as part of the per-SoC data... but do you think it should be in the device tree instead?#asahi-gpu · 2022-09-17 06:00
linaIn terms of data, it's a sparse list of <phys_start, len, readonly> tuples#asahi-gpu · 2022-09-17 05:59
linarobher: I have a question about reg mappings. The GPU driver needs to map a bunch of miscellaneous hardware into the GPU firmware page tables (not just the GPU itself, also random temperature sensors, power management, and interrupt related register ranges)#asahi-gpu · 2022-09-17 05:50
marcanwe don't even support any EPIC calls at all in the current driver and likely won't for a while unless it's necessary for external monitor support#asahi-gpu · 2022-09-17 05:49
marcanbut this is nowhere near a priority for DCP, so if you're not going to help out yourself, you'll have to wait until we get there#asahi-gpu · 2022-09-17 05:49
marcanDCP has a SetVirtualEDIDMode method on some EPIC I think, which will might let you set a custom EDID. I do not see anything to add custom modes.#asahi-gpu · 2022-09-17 05:44
marcanunless you're going to help with that, until that happens, you're just wasting everyone's time hypothesizing about EDIDs and modelines#asahi-gpu · 2022-09-17 05:44
marcanbluetail: just wait until DCP is done and merged and we have a good understanding of the DP control interfaces#asahi-gpu · 2022-09-17 05:31
bluetailit out. That said, I will look into EDIDs, perhaps there is a benefit of having those versus passing a modeline.#asahi-gpu · 2022-09-17 05:31
bluetailphire is the process of overriding EDID's more involved? I know there are a couple of scripts to make a new EDID - but you also have to enforce it, which probably includes a couple kernel parameters. I know modeline is pretty obsolete at this point but at least in my experience is more integrated in a way that you can change it on the fly to test#asahi-gpu · 2022-09-17 01:32
phireWhat you really want there is EDID override #asahi-gpu · 2022-09-16 23:52
rkjnsnRe custom modeline usecases: I used one on my previous projector, which could happily run at 48 Hz but, but the EDID it fed to computers only advertised 60 Hz. Using a custom 48 Hz modeline allowed for judder-free playback of 24fps content.#asahi-gpu · 2022-09-16 18:07
bluetailSo it is even a different issue. Perhaps I'll never figure what the issue really is. I thought I figured it, felt great. But now everything I had reached is to embarrass myself. Thanks for the scolding, I guess...#asahi-gpu · 2022-09-16 18:05
linaIt's completely different hardware from Intel so it doesn't make any sense to think you'd have any of the problems you had on Intel!#asahi-gpu · 2022-09-16 17:56
bluetaillina: So in other words, being able to raise or lower pixelclock (assuming its working the same way), wouldn't affect it the way it does in an intel system. Gotcha. #asahi-gpu · 2022-09-16 17:53
linaAnd that also doesn't have anything to do with the GPU, which is what this channel is about...#asahi-gpu · 2022-09-16 17:52
linaI'm pretty sure DCP manages memory bandwidth by itself properly...#asahi-gpu · 2022-09-16 17:52
linabluetail: no offense, but none of what you are talking about any sense and also extrapolating from Intel systems to Apple Silicon doesn't make sense either.#asahi-gpu · 2022-09-16 17:42
bluetailidk if my issue is even solvable as I dont know anything about clocks / bandwidth in arm systems... Perhaps these systems should not be 'abused' with those demands. #asahi-gpu · 2022-09-16 17:37
bluetails/98Hz/98MHz