#
…

2022-04-29

00:11bisko has quit [Read error: Connection reset by peer]
00:13bisko has joined #asahi
01:12psykose has quit [Remote host closed the connection]
01:13psykose has joined #asahi
01:20vmeson has quit [Quit: Konversation terminated!]
01:29vmeson has joined #asahi
01:42yuyichao has quit [Ping timeout: 480 seconds]
02:07bisko has quit [Read error: Connection reset by peer]
02:08bisko has joined #asahi
02:27sdafman has joined #asahi
02:27kibomo[m]input test
02:29Moprius has quit [Quit: Konversation terminated!]
02:32PhilippvK has joined #asahi
02:33derzahl has quit [Ping timeout: 480 seconds]
02:35phiologe has quit [Ping timeout: 480 seconds]
02:36sdafman has quit [Quit: Page closed]
02:40darkapex has joined #asahi
02:57Techcable has quit [Remote host closed the connection]
02:59Techcable has joined #asahi
02:59Telvana has quit [Remote host closed the connection]
03:02Telvana has joined #asahi
03:10marvin24_ has joined #asahi
03:14marvin24 has quit [Ping timeout: 480 seconds]
03:21kov has quit [Quit: Coyote finally caught me]
03:22kov has joined #asahi
03:43darkapex1 has joined #asahi
03:45darkapex has quit [Ping timeout: 480 seconds]
03:46kenzie has quit [Quit: The Lounge - https://thelounge.chat]
03:50Techcable has quit [Remote host closed the connection]
03:59kenzie has joined #asahi
04:05bisko has quit [Read error: Connection reset by peer]
04:06bisko has joined #asahi
04:09PasteldeCocoa[m] has joined #asahi
04:23nafod has joined #asahi
04:23calcium has quit [Quit: Ping timeout (120 seconds)]
04:23nafod has quit [Quit: Ping timeout (120 seconds)]
04:23Gaelan has quit [Quit: ZNC 1.8.2 - https://znc.in]
04:23calcium has joined #asahi
04:23tbodt has quit [Quit: ZNC 1.7.5+deb4 - https://znc.in]
04:23Death_Syn has quit [Quit: ZNC 1.8.2+deb1+focal2 - https://znc.in]
04:24tbodt has joined #asahi
04:24Death_Syn has joined #asahi
04:24Hotswap has quit [Remote host closed the connection]
04:24Z750 has quit [Remote host closed the connection]
04:24Z750 has joined #asahi
04:24Gaelan has joined #asahi
04:24skoobasteeve has quit [Quit: No Ping reply in 180 seconds.]
04:26skoobasteeve has joined #asahi
04:26llrcombs has joined #asahi
04:26Hotswap has joined #asahi
04:27rcombs has quit [Read error: Connection reset by peer]
04:51user982492 has joined #asahi
05:15akemin_dayo has quit [Ping timeout: 480 seconds]
05:17Techcable has joined #asahi
05:20akemin_dayo has joined #asahi
05:23derzahl has joined #asahi
05:45GlanzmannDarkShadow44 / VinDuv: Maybe we should prepare you one patch with 4k and VinDuv timing patch so that you can have the right resolution as well as monitor output
05:53VinDuvGlanzmann: I’ll be a bit busy until next week but if you want to play with my patch, it’s here: https://github.com/AsahiLinux/m1n1/pull/183
05:54VinDuvIf you apply both patches and boot with display=wait,3840x2160, it should boot in 4k and m1n1 will say “waiting for monitor disconnect” and then wait 10 seconds
05:59VinDuvbtw I’m working on a Python script that detects, from macOS, if a monitor disconnects during wakeup (so it needs m1n1 to wait) as well as its native resolution. If it works well and is integrated into the installer, it could autoconfigure the display= option in m1n1 during installation.
06:02bisko has quit [Read error: Connection reset by peer]
06:05bisko has joined #asahi
06:08nicolas17 has quit [Quit: Konversation terminated!]
06:12greguu has joined #asahi
06:13GlanzmannVinDuv: Maybe I have later tonight time for it during a train ride. Thank you for the instructions.
06:15greguu has quit []
06:17greguu has joined #asahi
06:25derzahl has quit [Quit: auf wiedersehen]
06:33greguu has quit [Quit: WeeChat 3.0]
06:34greguu has joined #asahi
06:36greguu has quit []
06:36Glanzmannjannau: About 4k screens, is display_fb_alloc or display_fb_alloc2 better?
06:37greguu has joined #asahi
06:40gpanders has quit [Read error: Connection reset by peer]
06:40andg has joined #asahi
06:40greguu has quit []
06:41greguu has joined #asahi
07:01GlanzmannDarkShadow44: I updated https://tg.st/u/4k.bin according to VinDuv instructions. If you have time you can try it (need to be copied to boot.bin). It should give you a picture and the right resolution.
07:09greguu has quit [Quit: WeeChat 3.0]
07:24MajorBiscuit has joined #asahi
07:24greguu has joined #asahi
07:34bisko has quit [Read error: Connection reset by peer]
07:36bisko has joined #asahi
08:16neatsquirrel has joined #asahi
08:54tarachan291[m] has joined #asahi
08:55user982492 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
09:19ciggi has quit [Quit: No Ping reply in 180 seconds.]
09:19ciggi has joined #asahi
09:27MajorBiscuit has quit [Quit: WeeChat 3.4]
09:30bisko has quit [Read error: Connection reset by peer]
09:32bisko has joined #asahi
09:40MajorBiscuit has joined #asahi
10:09user982492 has joined #asahi
10:13akemin_dayo has quit [Ping timeout: 480 seconds]
10:17user982492 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
10:17jluthra has quit [Remote host closed the connection]
10:18jluthra has joined #asahi
10:19akemin_dayo has joined #asahi
10:24user982492 has joined #asahi
10:39user982492 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
10:40Major_Biscuit has joined #asahi
10:42MajorBiscuit has quit [Ping timeout: 480 seconds]
10:48user982492 has joined #asahi
10:52jboettcher2605[m] has joined #asahi
10:58bisko has quit [Read error: Connection reset by peer]
10:58user982492 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
10:59bisko has joined #asahi
11:09m1n1m4[m]<Sobek[m]> "Is a NNPU as hard to reverse and..." <- I think, honestly apple would gain a lot "opening the curtain", if they really want to be in a better place on the desktop market. I mean ms last past patch tuesday had 47 ( think about this ), 47 remote code execution patches and one no click...
11:10m1n1m4[m]m1n1m4[m]: so windows is a slowly sinking boat, being patched all the time and "facelifted" to make people look the other way.
11:12m1n1m4[m]m1n1m4[m]: So really apple opening up to finally replace wintel on mainstream destops and also considering linux would be their best market offer at this moment. At least their profits were historically high last semester / year.
11:12Major_Biscuit has quit [Ping timeout: 480 seconds]
11:22victorhooi[m] has joined #asahi
11:23victorhooi[m]Is there any way to install Asahi Linux on a bootable usb stick?
11:23victorhooi[m](reason is I'm hoping to run k3s, with rook (to deploy ceph), and I want to hand over the internal NVMe drive in the M1 completely over to k3s/rook
11:24m1n1m4[m]<j`ey> "ylebars: https://twitter.com/..." <- BRILLIANT!!!
11:25j`eyvictorhooi[m]: you still need the m1n1 bootloader on the nvme (uses 3gb)
11:25j`eybut otherwise u-boot can boot from usb
11:25Major_Biscuit has joined #asahi
11:26victorhooi[m]the issue isn't so how much space it would consume
11:26victorhooi[m]as in, 3gb is fine
11:26victorhooi[m]the issue is more ceph ideally needs full control over the disk
11:26victorhooi[m]as in, you hand it a raw block device
11:26victorhooi[m]is there any other way or workaround, you could do this with a mac m1?
11:27j`eyexternal storage for ceph?
11:27mpsm1n1m4[m]: apple is not in this 'bandwagon'
11:31arndvictorhooi[m]: last year I experimented with an external Thunderbolt SSD. At the time it was possible to install a bootable copy of MacOS on that, but I could not have two separate copies, or m1n1/Linux installed on it, because of the way the boot process is done. I don't know if this has changed in the meantime, I now use m1n1 on the internal disk to boot from an external USB-attached SSD
11:31victorhooi[m] yeah, I guess the other way is to use a thunderbolt drive and pass that through to ceph
11:32victorhooi[m]but then I'm wasting the very expensive (and fast) 2TB NVMe drive inside the mac mini m1
11:32arndat the moment, thunderbolt doesn't work in Linux, so it has to be a USB attached SSD
11:32victorhooi[m]I don't need dual boot for mac/linux (assuming I can still revert to macos sometime in future)
11:32victorhooi[m]so if that's not a limitation
11:32victorhooi[m]is there perhaps a way just to get linux running on the m1 with an external drive?
11:33victorhooi[m]basically I just want a 3-node ceph cluster - that's asahi linux + k3s + ceph
11:34arndNot sure if you can create an additional nvme 'namespace' on the internal drive as you could on a proper nvme disk. The internal drive is close to the nvme spec, but not quite the same
11:35sveniirc the "create namespace" commands doesn't work
11:36sventhere's also two more special namespaces that seem to contain some kind of macos panics or something. i think they abuse the namespaces for their own purpose
11:36svenvictorhooi[m]: do you just need to pass along a single partition or the entire disk?
11:41victorhooi[m]ideally the whole disk
11:41victorhooi[m]as a raw device
11:41victorhooi[m]you can try to do clever things with partitions - I used lvm on linux - but performance takes a hit, and it's not as reliable
11:41svenso it would try to use the entire disk and overwrite e.g. the partition table?
11:44ChaosPrincessyou can't use the whole internal disk, the bootloader expects certain partitions to be there and will refuse to work if they are gone
11:45svenyeah, you could pass through the entire disk but you'd have to make sure ceph doesn't mess with the GPT or the required system partitions
11:52victorhooi[m] hmm - I'm curious - the limitation around the bootloader expecting to be on the internal disk
11:52victorhooi[m]is that just as it's currently designed
11:52victorhooi[m]or is there some technical reason for that?
11:53victorhooi[m]sven: and yeah - ceph would likely zap the disk (ceph zap) - which I assume would render the mac mini unbootable?
11:53svenand this is all Apple's code fwiw
11:53sven(which we can't change)
11:56svenwe only get control long after apple's bootloader already expected certain partitions with firmware, etc. on the internal nvme
11:56j`eyI dont understand this bit "There is no external storage boot support in the bootloader flow on these machines. Behind the scenes, booting macOS from an external drive involves the moral equivalent of copying /boot to internal storage"
11:57j`eywhat bit copies from the external drive, if there is no external drive support?
11:57ChaosPrincessboot picker is actually something like a full macos
11:57svenyeah, the external disk setup doesn't happen inside iBoot. it happens from macOS
11:57Sobek[m]Basically if you want to boot macOS from an external drive, you'll end up with a preboot + recovery volum on the internal drive that can only then hand-off to the external root.
11:57j`eydoes that mean you can only boot external drivers from the boot picker, and not as the default startup disk?
11:58svenyou set it up once, macos copies the required stuff to the internal disk (~ cp /mnt/external-disk/boot /mnt/internal-disk/boot)
11:58j`eyI thought it copied on every boot
11:59sveni don't think so
11:59m1n1m4[m]<mps> "m1n1m4!: apple is not in this '..." <- That is sad, have you seen this?
12:00svenafter all whatever is in these system partitions only changes during an update and that update runs a ramdisk with a stripped down macos anyway which can just update that partition
12:00mpsm1n1m4[m]: yes, I saw it
12:00m1n1m4[m]> <@asahi-test:matrix.org> That is sad, have you seen this?
12:00m1n1m4[m]Maybe apple could change their approach no?
12:00m1n1m4[m]m1n1m4[m]: has anyone tried to reach them recently?
12:01Sobek[m]I think the person behind OpenBSD on M1 has been discussing with the Asahi folk quite a bit. There may have even been some exchanges of codes in addition to knowledge.
12:01mpsI doubt, I know apple from apple II iirc
12:01j`eySobek[m]: yes mark (ket_tenis without the _ is here)
12:01mpsSobek[m]: I think kettenis did most for m1 in openbsd
12:02Sobek[m]So much for not hl ing him ^^'
12:02millenialhacker has joined #asahi
12:02m1n1m4[m]Sobek[m]: ah, so not with apple themselves, i see...
12:02mpsyes, and I forgot to put _
12:03m1n1m4[m]m1n1m4[m]: still i insist they have a narrow perspective. However they did not lock the bootloader...
12:03j`eym1n1m4[m]: none of this has been with any contact from apple
12:03Sobek[m]I don't remember, given the license Darwin is released under, is it possible to look at and possibly reuse some Darwin code in Linux, or is this impossible ? (Ignoring the fact that Darwin releases hardly any of the interesting bits of drivers, anyways)
12:04m1n1m4[m]j`ey: WOW...
12:04svenapple only cares about macos because that's what makes them money
12:04svenif you look at it through that perspective + their design (and security) goals all this makes perfect sense
12:05Sobek[m]m1n1m4[m]: Not only did they not lock the bootloader, they actually designed it so that something like asahi be possible (extra efforts), and even added small features that help asahi (raw image after making breaking change to the Mach-O boot protocol, bless support, etc).
12:05m1n1m4[m]Sobek[m]: WOW, that might lead to a perspective change in the future no?
12:06svenadding external boot support increases the attack surface for ~no gain from their perspective
12:07m1n1m4[m]sven: because if they want to really compete with wintel they have to leave space for linux
12:07m1n1m4[m]* with wintel on desktop they have
12:07svenanyway, this is also getting off-topic and i should get back to $work
12:08m1n1m4[m]sven: yes, thanks but we might be surprised...
12:15Sobek[m]The lack of straight from external device boot make the bootloader code extremely simpler. For what it is worth, a mac mini / studio whose internal drive has been wiped is only able to communicate with the external world using the led colour and blink (Amber + morse SOS blinking), and getting a recovery software blob (signed by apple) through USB recovery. The attack surface is quite small. And once the bootloader first stage is on the internal
12:15Sobek[m]drive, having the second stages be on the drive two doesn't change much the equation, and allows configs to have their integrity checked pretty easily, and the first iBoot stage is simpler too.
12:16victorhooi[m]Sobek: got it - so you think Apple not allowing direct external boot is for security reasons?
12:16victorhooi[m]hence - it'd be unlikely they'd allow it in the future?
12:17Sobek[m]The whole design is pretty much with security in mind. See what marcan said about its security
12:19m1n1m4[m]Sobek[m]: in the wiki?
12:20mpsSobek[m]: strange idea of security by cutting out usability. I would rather call this 'lock in'
12:21Sobek[m]Your usual evil maid from the SDECE or whatever secret service is after you won't be able to install a rootkit simply with physical access. Managing boot security actually requires both physical access (physical button press to get in 1TR), and an owner password. I haven't done any external boot of standard macOS stuff so I don't known if that can be set-up without password, but anything that involves downgrading security will require a
12:21Sobek[m]password.
12:21m1n1m4[m]Sobek[m]: yes makes sense
12:23Sobek[m]Security and usability have always been kind of at odds. Yet apple made something where the proper owner (and only them), can pretty much boot any code they want. It requires them to do a few things to get there, but it is completely doable, that's what marcan has been doing here actually. m1n1 is a big example of running code kind of unfettered.
12:23mpsSobek[m]: if you are target of security service you don't have chances
12:24Sobek[m]Well, if they hit me with a wrench, I know I've been compromised at least
12:24Sobek[m]<m1n1m4[m]> "in the wiki?" <- Yes in the Wiki, where he describes the Apple Silicon boot process.
12:24m1n1m4[m]Sobek[m]: yep things are pretty much in the dark nowadays, even on the news you get "sink holes" ...
12:25mpsthis solution around is just security theater, to lock users and extract money from them
12:25victorhooi[m]hmm ok - is all this external boot limitations documented in the wiki somewhere?
12:25m1n1m4[m]m1n1m4[m]: "specially crafted"
12:25victorhooi[m]and the explanations about security for it?
12:26Sobek[m]mps: Usually there are way too many ways we humans fail at opsec, that they don't need to actually go break the boot security to get where they want, but at least that's going to make them work more than stupid Lenovo rootkit certificates etc.
12:28m1n1m4[m]mps: Well, if you consider there are businesses that sell "keys" to states particularly for apple ecosystem like nso group... They literally built an OS inside a "load" to wreck iphone into noclick
12:28mpsSobek[m]: if you want to discuss this subject more we could join #asahi-offtopic
12:29m1n1m4[m]mps: How to i get there?
12:29Sobek[m]Same way you got here, but with -offtopic added to the name of the channel right after #asahi ;)
12:29mps /join #asahi-offtopic in irc client
12:30victorhooi[m]hmm ok - so for the ceph on M1 use case
12:30victorhooi[m]it seems like there's no way around it
12:30victorhooi[m]the internal drive in the Mac M1 will still need ot have special apple partitions on it - hence we cannot pass through the raw device
12:30m1n1m4[m]Sobek[m]: i got there with a click on the community page of asahi
12:31m1n1m4[m]* of asahi. Let me look at the link...
12:31m1n1m4[m] * i got here with a click on the community page of asahi. Let me look at the link...
12:31j`eyvictorhooi[m]: seems so
12:31victorhooi[m]fair enough - at least now I know
12:32victorhooi[m]ok, will need to figure out a way to do this with partitions then
12:32victorhooi[m]have a lot of people tried k3s on asahi linux?
12:33victorhooi[m]so the ceph-volume tool relies on LVM
12:33victorhooi[m]which I assume isn't supported on asahi, rihgt?
12:33victorhooi[m]I'm guessing that apple has their own partition format and all that?
12:33j`eyI think people have used LVM
12:36Moprius has joined #asahi
12:44victorhooi[m]oh - LVM can work with M1/Asahi?
12:51milek7why wouldn't it? you just create ordinary gpt partition
12:51Glanzmann/clear/clear
12:52victorhooi[m]ah right - apple just uses GPT these days?
12:53victorhooi[m]there's no weird quirks due to it being apple/mac?
12:53victorhooi[m]sorry I didn't realise - but you're saying it should be the same as any other windows/linux GPT partitioning then?
12:54j`eyyep since all the usual fdisk etc Just Work
12:55victorhooi[m]ok - but I think somebody mentioned above
12:55bisko has quit [Read error: Connection reset by peer]
12:56victorhooi[m]there's some special system partition that is needed for m1 boot, right
12:56victorhooi[m]I just need to to leave that one partition alone?
12:56j`eyit's just a normal partition
12:56j`eywith special contents
12:56victorhooi[m]anything else to keep in mind here, if I'm playing around with the partition table on an m1
12:59j`eydont touch the first and last partitions
12:59milek7somebody said that you should keep gpt entries sorted otherwise macos diskutil could be confused
12:59j`eyit renumbers them, so you have to pay attention to the numbers
13:00bisko has joined #asahi
13:17tpw_rulesit will list them wrong if they are not sorted
13:20user982492 has joined #asahi
13:27david_ has joined #asahi
13:27marcanyes, just keep them sorted to avoid confusing it
13:28david_hi, I ran the script on my 2020 mac mini (m1) and when it boots I can tell that the machine is on (mouse light is on), but nothing is coming out of the HDMI
13:28david_I never even got the Asahi set up screen or anything, I just got to the boot security disabling bit
13:28david_anyone have any ideas? thanks in advance, this looks like a really cool project :)
13:29tpw_rulestry a different monitor if you have one
13:29tpw_rulesotherwise, there might be a solution here: https://github.com/AsahiLinux/m1n1/issues/159
13:30david_thank you very much, I'll try and report back :)
13:31tpw_rulesyou'll have to turn the mini completely off when you try them. the basic underlying cause is that monitors can't be hot-swapped yet
13:31tpw_rulesand some monitors do a logical hot-swap every time something tries to connect
13:42david_ has quit [Quit: Page closed]
13:47david_ has joined #asahi
13:50david_ok so I'm going to try the fixes on the github... where is the /boot/efi directory? sorry for all the beginner questions :P
13:58yuyichao has joined #asahi
13:59j`eydavid_: diskutil list, and find the EFI partition
13:59j`eythen: diskutil mount <that disk> and cd /Volumes/EFI
14:01david_ok I am making notes so I can make a github post
14:03david_ has quit [Quit: Page closed]
14:10millenialhacker has quit [Remote host closed the connection]
14:18david_ has joined #asahi
14:29bisko has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
14:31millenialhacker has joined #asahi
14:34bisko has joined #asahi
14:50LinuxM1 has joined #asahi
14:52david_ has quit [Remote host closed the connection]
14:55bisko has quit [Read error: Connection reset by peer]
14:57bisko has joined #asahi
16:18PthariensFlame[m]Has this commit been seen here?
16:18PthariensFlame[m]It’s pretty direct confirmation that M2 will be A15 cores, but not identical sysregs for some reason?
16:43___nick___ has joined #asahi
16:43___nick___ has quit []
16:43user982492 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
16:45___nick___ has joined #asahi
16:47LinuxM1 has quit [Quit: Leaving]
16:52bisko has quit [Read error: Connection reset by peer]
16:53bisko has joined #asahi
16:54eroc1990 is now known as Guest3177
16:54eroc1990 has joined #asahi
17:00Guest3177 has quit [Ping timeout: 480 seconds]
17:26opticronPthariensFlame[m], they yanked it already
17:56Sobek[m]Has anyone managed to archive it ?
17:57jannauGlanzmann: display_fb_alloc2 - main reason why it's not submitted is that hv/macos panic immediately on boot
18:00user982492 has joined #asahi
18:00Major_Biscuit has quit []
18:05PthariensFlame[m]IIRC it said something like "Use Staten for A15/H14 targets because it has the same core designs but a few more sysregs.", and the commit information was already gone before, just the message was there.
18:06Sobek[m]H14 ? What's that ?
18:06Sobek[m]Staten is the code name for M2 isn't it ?
18:06PthariensFlame[m]We already know H14 is the internal codename for the entire A15/M2 family, like H13 is for A14/M1.
18:07Sobek[m]Ah. Hmm but why H = A-1 ? Did they start with H0 ? Or did those code name start at another point ?
18:08svenmarketing
18:09jannauthey started AN at A4
18:10PthariensFlame[m]Didn't find it in any archives; oh well.
18:10svenwasn’t it because the iphone4 should have the a4?
18:10PthariensFlame[m]The information was relatively minimal.
18:10j`eyPthariensFlame[m]: how did you find it at all? the commit was from 2020
18:11jannauhmm, I still saw te commit message but the commit was already gone. I assumed it was just a leftover since the date is 2020-11-12
18:12PthariensFlame[m]I randomly searched for A15 in the LLVM Phabricator, on a whim.
18:12PthariensFlame[m]It came up in that search pretty directly at the time.
18:13Sobek[m]I wonder if a. You were very lucky to be in a very short time frame where this think had been mistakenly pushed and yanked or b. The thing got pulled just after you saw it by sheer unluck after being there for a while ?
18:14PthariensFlame[m]Can't have been that tight a window because I first spotted this commit days ago.
18:14zvperhaps people in high places lurk here
18:14j`eybut only linked it here just now :)
18:15PthariensFlame[m]I sadly didn't think to until this morning.
18:15PthariensFlame[m]When I submitted it, I double-checked right then to make sure it was still up.
18:15Glanzmannjannau: Thank you.
18:15PthariensFlame[m]So it got yanked in the period between me sending and anyone looking.
18:15j`eyi saw the commit message
18:16Sobek[m]Perhaps one apple person lurking here saw it and got it yanked within an hour. Does it seem that bad ? Perhaps apple has its opsec team keeping an eye on us ?
18:16svenI’m pretty sure there are apple people lurking in here ;)
18:16* svenwaves
18:16Sobek[m]Well yes, but them lurking hear doesn't necessarily mean they snitched and got that commit removed.
18:17PthariensFlame[m]I mean it did have a user id of someone who might not want to have association with apple broadly published? 🤷
18:18Sobek[m]A15 got released in to teh general public in september 2021, so roughly a year before it got out, they were updating compilers to support the target. probably a point where engineering samples for A15 might have been used for prototypes and testing stuff ?
18:18PthariensFlame[m]The thing is, LLVM (public version) still doesn't have any A15 target.
18:18PthariensFlame[m]That's the primary reason I was searching in the first place—to see if there was any progress.
18:19Sobek[m]wait, that's in spite of A15 being out and a supported target for Apple LLVM ?
18:19Sobek[m]Or even apple LLVM doesn't have support for A15 ?
18:20PthariensFlame[m]Don't know; all that's confirmable is that open-source LLVM only goes up to M1.
18:20j`eyPthariensFlame[m]: its no secret that t northover works for apple
18:20PthariensFlame[m]j`ey: Oh, okay. Scratch that supposition, then.
18:20Sobek[m]M1 Max / Ultra included or some M1Pro/Max/Ultra bits are missing too ?
18:21j`eyPthariensFlame[m]: I used to sit opposite him for a bit! (at a different company)
18:21PthariensFlame[m]Sobek[m]: Everything's bundled under the same M1 target, because they're identical from the perspective of CPU targets.
18:21neatsquirrel has quit [Quit: neatsquirrel]
18:22PthariensFlame[m]Compiling for Firestorm.Icestorm is gonna be the same no matter how many of each there are, and the compiler doesn't care what peripherals are around.
18:22Sobek[m]It look like the branch for A15 support and M2 support was like mixed up in a way it shouldn't have. Perhaps next time round they'll do stuff in a way such that they can release A16 first and then push the M3-A16 diff later ?
18:22headscracher[m] has joined #asahi
18:30penguwin has joined #asahi
18:32nicolas17 has joined #asahi
18:34darkapex1 has quit [Ping timeout: 480 seconds]
18:37user982492 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
18:47bisko has quit [Read error: Connection reset by peer]
18:48bisko has joined #asahi
18:49user982492 has joined #asahi
18:49user982492 has quit []
18:52bpye has quit [Quit: The Lounge - https://thelounge.chat]
18:58user982492 has joined #asahi
19:01user982492 has quit []
19:03user982492 has joined #asahi
19:04user982492 has quit []
19:11user982492 has joined #asahi
19:17bpye has joined #asahi
19:28nicolas17 has quit [Quit: Konversation terminated!]
19:28nicolas17 has joined #asahi
19:43nicolas17 has quit [Quit: Konversation terminated!]
19:44nicolas17 has joined #asahi
19:47nicolas17 has quit []
19:47nicolas17 has joined #asahi
20:08___nick___ has quit [Ping timeout: 480 seconds]
20:18bisko has quit [Read error: Connection reset by peer]
20:19bisko has joined #asahi
20:31darkapex has joined #asahi
21:15buildingsteam[m] has joined #asahi
21:16buildingsteam[m]hey, I'm david_ from earlier, joined on Matrix because I don't know IRC. Managed to get my monitor to work by making sure it wasn't asleep by spamming the menu button during boot :P
21:34millenialhacker has quit [Quit: Konversation terminated!]
21:50user982492 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
21:51user982492 has joined #asahi
22:01nicolas17 has quit [Quit: Konversation terminated!]
22:02nicolas17 has joined #asahi
22:02nicolas17 has quit []
22:03nicolas17 has joined #asahi
22:05crabbedhaloablut has joined #asahi
22:06nicolas17 has quit []
22:06nicolas17 has joined #asahi
22:08loki_val has quit [Ping timeout: 480 seconds]
22:14bisko has quit [Read error: Connection reset by peer]
22:15bisko has joined #asahi
22:27jakebot has quit [Quit: The Lounge - https://thelounge.chat]
22:30jakebot has joined #asahi
22:34poplar has quit [Remote host closed the connection]
22:34poplar has joined #asahi
22:36user982492 has quit [Ping timeout: 480 seconds]
22:44ashtez[m] has joined #asahi
23:08feta[m] has joined #asahi
23:09feta[m] is now known as feta
23:36user982492 has joined #asahi
23:40user982492 has quit []
23:41user982492 has joined #asahi
23:51yuyichao has quit [Ping timeout: 480 seconds]
23:59user982492 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
23:59user982492 has joined #asahi
…