#asahi-dev · 2026-01-23 12:36
fl0_idyuka oh I should try that too...#asahi-dev · 2026-01-23 12:36
fl0_idnoopwafel not much, I have only suspicions. I added uart to my device tree, but that didn't seem to do anything. I rebased on asahi-wip, no observable change. somewhere along there I lost my symbols for whatever reason despite using the same config...#asahi-dev · 2026-01-23 12:10
fl0_idat least after enabling early_uart_base and putc I have some console output from the kernel, so at least it works in theory#asahi-dev · 2026-01-23 12:07
fl0_idor a memory function that's used in lots of places#asahi-dev · 2026-01-23 12:07
fl0_id:/ feels almost like once when i put a hvc in bsearch or sth like that and then ofc it was like everywhere lol#asahi-dev · 2026-01-21 18:49
fl0_idand this should prob go to #asahi-offtopic#asahi-dev · 2026-01-21 18:49
fl0_idI wasn't talking about speed. just pure overload imo#asahi-dev · 2026-01-21 18:44
fl0_idtouch discord is an adwall of a UI, and a pain if you have more than a few "servers"#asahi-dev · 2026-01-20 18:20
fl0_idok, I should also try asahi-wip just in case#asahi-dev · 2026-01-20 18:19
fl0_idrebased on what? asahi branch?#asahi-dev · 2026-01-20 18:19
fl0_idlol nice#asahi-dev · 2026-01-20 18:19
fl0_idyuka thx#asahi-dev · 2026-01-20 17:59
fl0_idwould linux:asahi vs linux:asahi-wip have meaninful changes that could impact m3 bringup things? so far I always used asahi#asahi-dev · 2026-01-20 00:34
fl0_idjannau 16 core. I thought it was referred to as t6031 as well... but yeah I'll try to check that#asahi-dev · 2026-01-16 18:38
fl0_idright ok#asahi-dev · 2026-01-16 18:38
fl0_idgatallah make sure it's the other one, not the macos install you want to keep#asahi-dev · 2026-01-15 12:55
fl0_idoh sorry wrong channel#asahi-dev · 2026-01-15 12:54
fl0_idthey were very cautious about their work, so not impossible. they said they "were not sure their host country is as liberal as rest of europe" re license breaking, so prob not NSA#asahi-dev · 2026-01-15 12:44
fl0_idanyway thx for commenting, good to know I wasn't completely wrong#asahi-dev · 2026-01-15 12:43
fl0_idsven I apologized b/c I can't fully judge it and they also dm'ed saying it was a really shitty thing to say. And I didn't want to drive away ppl doing work. They gave some more details, like saying they didn't want to test b/c it's a work device and how much time they spent etc and that ai was just for writeup.#asahi-dev · 2026-01-12 12:52
fl0_idor you mean in the kernel? I can only check that later#asahi-dev · 2026-01-12 12:52
fl0_idI didn't know that it needs a config option#asahi-dev · 2026-01-12 12:52
fl0_idintegegralpilot shouldn't be aic3 support on main m1n1? In my logs it says sth like AIC: Version 3 @ 0x292400000, AIC: AIC3 with 1/2 dies, 2528/4096 IRQs, reg_size:40004, config:10000, extintrcfg_stride:04a00, intmaskset_stride:04a00, intmaskclear_stride:04a00, AIC: Configuring 1 external interrupts#asahi-dev · 2026-01-12 01:05
fl0_idit was like a new job present for myself lol#asahi-dev · 2026-01-12 01:05
fl0_idShiz m3 max#asahi-dev · 2026-01-12 00:59
fl0_idright, but others like integralpilot have. in any case, macos also worked badly for me. but maybe I should try that again. people had worked on it in the past, but at least the counter chickens in m1n1 did not seem right for me somehow#asahi-dev · 2026-01-12 00:56
fl0_idah ok. god these are confusing. just lookign for someone to test if things are only messed up for me or not ^^#asahi-dev · 2026-01-12 00:48
fl0_idmine is j516ac or sth if the characters at the end are shiown#asahi-dev · 2026-01-12 00:48
fl0_idShiz isn't th j516 an m3 max? did you try booting linux on it yet?#asahi-dev · 2026-01-10 21:18
fl0_idbut stepping didn't seem to get me anywhere. maybe someone with better assembly knowledge would see sth not sure#asahi-dev · 2026-01-10 21:17
fl0_idfl0_id sven mmh, that part I posted, it went on for a while, but when I left it a for a bit it was somewhere else. so if this is the loop it is bigger#asahi-dev · 2026-01-09 20:40
fl0_idchaos_princess hvc bisect looks promising btw, at least now I know it reache init_el in head.S. haven't had time to bisect further yet#asahi-dev · 2026-01-09 14:40
fl0_idty#asahi-dev · 2026-01-09 14:40
fl0_idright#asahi-dev · 2026-01-09 14:40
fl0_idyes#asahi-dev · 2026-01-09 14:38
fl0_id*right now#asahi-dev · 2026-01-09 14:38
fl0_idright. ok. looking at that right. I'm not interested in a particular function atm, just trying to figure out where it reaches before exception/crashing#asahi-dev · 2026-01-09 14:36
fl0_idchaos_princess you mean hypervisor calls, not hvc tty driver, right?#asahi-dev · 2026-01-09 14:20
fl0_idthis is through EL1, when running run_guest_kernel.sh, as integralpilot said debugging/output would be better/easier than when just running with linux.py directly#asahi-dev · 2026-01-09 14:15
fl0_idI did also try to put some assembly in head.S, which had the intended result of rebooting, also when starting cpu 3 or 4, but not as that output is from m1n1, not sure if that is strictly related.#asahi-dev · 2026-01-09 14:14
fl0_idf.e. I put some printk(KERNEL_EMERG "Some text") into start_kernel() and I assume these should come through on the second serial port. (they don't) The do seem to do something, just not sure what. (it seemed to crash/reboot earlier than ususal, but then that also happened 2-3 times with the same setup as before (exception somewhere on starting cpu 3 or 4)#asahi-dev · 2026-01-09 14:12
fl0_idhey. does anybody have a good link about early boot kernel debugging? reading kernel code and blog posts etc that I could find were ok. but still not sure if I'm doing things right#asahi-dev · 2026-01-09 00:08
fl0_idjannau yeah that did it. thanks#asahi-dev · 2026-01-08 23:50
fl0_idyeah, that's what I get for vmlinuz. there is just no Image.gz. Image is there, but that's uncompressed. I thought it should be there as I though I just used the asahi fedora config originally#asahi-dev · 2026-01-08 23:27
fl0_id least clarify the help text? Or is my kernel build wrong because it should always create Image.gz#asahi-dev · 2026-01-08 23:27
fl0_idfor run_guest_kernel.sh, is it possible that this detection of gzipped Image is kinda wrong? As I read that script, if a kernel argument is supplied, (but no -k option) it sets kernel to <path>/Image.gz. In my kernel tree, kernel build never gzips the image (or well it does but calls it vmlinuz) The proyclient/tools script only gzips it if the -k option is used iirc. If my understanding is correct, is it ok to improve this handling or to at#asahi-dev · 2026-01-07 21:19
fl0_idleio somehow I just thought it was a simple style...#asahi-dev · 2026-01-07 21:05
fl0_idnice#asahi-dev · 2026-01-07 20:48
fl0_idwow i like this kind of markup :) https://eiln.github.io/posts/10-05-2023-avd-notes/draft.png#asahi-dev · 2026-01-07 15:00
fl0_idchaos_princess I assume that is similar to some nvram things on x86? Which is why some x86 with built in battery have a like a little extra hole to "cut power" but I had f.e. an example with a hackintosh where even that didn't work. reflashing the bios chip fixed it...