00:06 <modwizcode> I tried to workaround the interrupt/console issues by adding a second UART and declaring it as the exynos uart instead of the apple one but linux seemed a little annoyed with that and so I'm just going to try and solve the actual IRQ issue

01:45 <amw> modwizcode: Got your qemu booting m1n1 - need to work out next step after lunch - thanks

01:46 <modwizcode> amw: glad to hear it :)

01:47 <amw> Thinking of tapping a few notes on the wiki on it

01:47 <amw> Perhaps on the the Getting started page under m1n1 or perhaps should have a seperate page?

01:47 <modwizcode> As long as nobody minds that sounds good.

01:47 <modwizcode> Does m1n1 have it's own wiki?

01:48 <amw> Not that I can see - might just add one under "Places to start"

01:49 <modwizcode> Seems reasonable I guess

01:52 <modwizcode> I think someone should probably edit the tasks page to mention that MMU, SMP spin-up and chicekn bits are all completed for m1n1

01:52 <modwizcode> At least as far as I can tell

01:52 <modwizcode> Also maybe UP linux booting but I'm not sure if that's waiting for like... proper support and not chainloading via serial

01:56 <modwizcode> From some bits I was poking it seems that maybe the M1 supports an ARM feature that makes the data and instruction caches coherent? I can't find enough specifics about what the feature actually means to fully understand it, it's a virtualization support feature but it requires that the cache coherence be defined in a weird way.

02:14 <amw> modwizcode: Added brief wiki page: https://github.com/AsahiLinux/docs/wiki/SW:m1n1

02:14 <amw> Will add more later if I get Linux booting under it - Thanks again modwizcode

02:15 <modwizcode> no problem!

02:15 <modwizcode> you might want to add a bit about how to run the proxy tools with it, since it's not super obvious you can just point them at the PTY

02:16 <modwizcode> Also I never figured out the correct mapping for picocom to not screw up the newlines

02:16 <modwizcode> but if you know it you should add it too

02:18 <amw> modwizcode: I've gotten no where with the serial port or even tried the proxy tools - so that's all to be learnt!

06:08 <amw> modwizcode: Got Marcan's kernel booting under your qemu - still missing an initramfs

06:09 <amw> Will add some Wiki notes on that - new page perhaps?

07:58 <amw> marcan: Hope it's ok - added a page on getting m1n1 and kernel booting under modwizcode's qemu

08:33 <amw> It would be nice to add some screen shots to the Wiki - anyone know the

08:33 <amw> ... the way to do this? e.g. fork the project and do an pull request?

08:33 <amw> Or upload an image?

09:05 <marcan> amw: you can put images in the wiki repo, but there is no UI for it and no UI for fork/merge, which is kind of annoying

09:06 <marcan> amw: try cloning git@github.com:AsahiLinux/docs.wiki.git, adding an image, and pushing. since the wiki is world-editable, maybe that works?

09:06 <marcan> just make a /images folder

09:06 <marcan> if you can't push, make a repo under your own namespace and I'll pull the commit

09:06 <amw> I'll try later - perhaps tomorrow - thanks

09:25 <cdesai> No UI for fork/merge / needing perms to the git repo to edit the wiki is why I moved off of github/gitlab wikis - otherwise they're super nice.

09:25 <cdesai> Just putting markdown files in the repos is better for collab

09:26 <amw> Would be nice to have a binary blob archive which we could reference with URLs

09:27 <amw> e.g. for kernel images / m1n1 images / initramfs images / screen shot images....

09:39 <marcan> well the wiki git repo can do that

09:39 <marcan> otherwise we could put it in the main repo, since it's a dummy anyway

09:40 <amw> marcan: I'm not sure git is so good for binary blobs though...

09:41 <marcan> it's perfectly fine for images

09:42 <amw> Not so much for larger kernel / ramisk images that are frequently obsoleted I guess

09:43 <marcan> yeah, those are a bad idea

09:43 <marcan> but it's perfectly fine for rarely-changing images in the <1MB range

09:44 <marcan> I mean we have artwork.git :)

09:45 <amw> Yep perhaps you could donate a screen shot of the a linux bash prompt on your frame buffer?

09:46 <marcan> heh, never got one of those because there's no keyboard so what's the point :)

09:46 <marcan> I always put the ash prompt on serial

09:47 <amw> ok - still struggling to get my initramfs give a shell prompt on qemu - but it's just a matter of time

11:56 <cdesai> git with lfs is not so bad for binary blobs - although it only starts becoming a problem if there's lots of big files, or they change often.

12:30 <Namidairo> or in the case of github, your repo is vaguely popular?

12:31 <Namidairo> I have seen a couple repositories that I've tried to clone from hit the bandwidth limits

13:02 <Glanzmann> I can setup a minio on a server with a 1 Gbit/s link if necessary.

13:04 <Glanzmann> or we could use a s3 bucket ...

15:15 <marcan> we aren't going to have any such problems