#asahi-dev · 2023-06-22 09:15
sid-linux4 4 1 7#asahi-dev · 2023-06-22 09:15
sid-linux`cat /proc/sys/kernel/printk` gives me#asahi-dev · 2023-06-22 09:14
sid-linuxHowever I still don't see a higher level of detail via dmesg#asahi-dev · 2023-06-22 09:14
sid-linuxA question related to asahi linux (arch) debugging. I set `loglevel=7` in /etc/grub.d/10_linux , run `update-grub` successfully#asahi-dev · 2023-06-22 06:58
sid-linuxjannau: Thanks !#asahi-dev · 2023-06-22 04:09
sid-linuxThe highest number before IPI0 is 106. Also all AIC2 interrupts do have a number have something like AIC2 66NNN . How do I find the interrupt number mentioned in the dtbi ?#asahi-dev · 2023-06-22 04:06
sid-linuxBut if I do `cat /proc/interrupts` I am not able to find them there#asahi-dev · 2023-06-22 04:05
sid-linuxMany devices have AIC IRQ numbers that are in > 500#asahi-dev · 2023-06-22 04:03
sid-linuxQuestion relating to device tree. The IRQs for `mtp_mbox` for instance is `<AIC_IRQ 864 IRQ_TYPE_LEVEL_HIGH>` (etc)#asahi-dev · 2023-06-19 06:20
sid-linuxHello folks, for those using ALARM I have posted a question on #asahi-alt since it may be slightly off topic. The question is regarding the appearance of (many!) new packages on ALARM and whether updates are finally OK on ALARM now.#asahi-dev · 2023-06-18 10:48
sid-linuxsven: thanks -- this is useful#asahi-dev · 2023-06-18 10:43
sid-linux(and therefore not permitted in the top half -- which is what `dockchannel_irq()` is in )#asahi-dev · 2023-06-18 10:42
sid-linuxwhich is going to be slow??#asahi-dev · 2023-06-18 10:42
sid-linuxbut that readl is is reading from the dockchannel device#asahi-dev · 2023-06-18 10:41
sid-linuxHere `dockchannel_irq` is reading from the device#asahi-dev · 2023-06-18 10:40
sid-linuxMy understanding is that we can't do IO in the top half. We can only read from memory. IO could take a really long time#asahi-dev · 2023-06-18 10:35
sid-linuxAlso, I'm wondering how this can be done in a top half interrupt handler? Wont this communication with the device be subject to sleep issues?#asahi-dev · 2023-06-18 10:35
sid-linuxso here read and write achieve different outcomes in hardware...#asahi-dev · 2023-06-18 10:33
sid-linuxs/IRQ_FLAG/dcc->irq_base + IRQ_FLAG/#asahi-dev · 2023-06-18 10:32
sid-linuxj`ey and similarly since the IRQ_FLAG doesnt 'store' anything the read can ask the hardware to present it for a bit map of currently asserted IRQs? See `static void dockchannel_irq(struct irq_desc *desc)`#asahi-dev · 2023-06-18 10:27
sid-linuxs/HW_FLAG/IRQ_FLAG/ ?#asahi-dev · 2023-06-18 10:25
sid-linux(thanks for your reply -- can you please write your message with the typos fixed. I don't know where the *IRQ_FLAG and *bit needs to be subsituted)#asahi-dev · 2023-06-18 10:20
sid-linuxare the reads and writes "orthogonal" here because this is iomem?#asahi-dev · 2023-06-18 10:19
sid-linuxbefore writing out BIT(hwirq) to prevent overwriting other entries ?#asahi-dev · 2023-06-18 10:19
sid-linuxQuestion: why is there not a `readl_relaxed` to get the current value of dcc->irq_base + IRQ_FLAG#asahi-dev · 2023-06-18 10:18
sid-linux}#asahi-dev · 2023-06-18 10:18
sid-linux writel_relaxed(BIT(hwirq), dcc->irq_base + IRQ_FLAG);#asahi-dev · 2023-06-18 10:18
sid-linux unsigned int hwirq = data->hwirq;#asahi-dev · 2023-06-18 10:18
sid-linux struct dockchannel_common *dcc = irq_data_get_irq_chip_data(data);#asahi-dev · 2023-06-18 10:18
sid-linux{#asahi-dev · 2023-06-18 10:18
sid-linuxstatic void dockchannel_irq_ack(struct irq_data *data)#asahi-dev · 2023-06-18 10:17
sid-linuxIn function#asahi-dev · 2023-06-18 10:17
sid-linuxnewbie question. Looking at the dockchannel codebase#asahi-dev · 2023-06-16 13:40
sid-linuxmps: thanks ! basically if I understood you correctly -- upgrading to chromium 114 also fixes the problem? (did you also confirm that hardware acceleration is still on in 114?)#asahi-dev · 2023-06-15 21:45
sid-linuxlike spi or i2c etc are#asahi-dev · 2023-06-15 21:45
sid-linuxbut it does not seem to be listed in /sys/bus#asahi-dev · 2023-06-15 21:45
sid-linuxsounds like dockchannel is a bus#asahi-dev · 2023-06-15 21:43
sid-linuxmtp = multitouch touchpad on your keyboard?#asahi-dev · 2023-06-15 21:40
sid-linux(mtp = mailbox transfer protocol?)#asahi-dev · 2023-06-15 21:40
sid-linuxwhat about dockchannel and mtp? Once I have a mental model of what these things are, it becomes easier to understand the code#asahi-dev · 2023-06-15 21:39
sid-linuxprotocol#asahi-dev · 2023-06-15 21:37
sid-linuxSo rtkit in linux communicates with coprocessors running the rtkitos via the mailbox#asahi-dev · 2023-06-15 21:21
sid-linuxAnother newbie question. I see references to Apple rtkit and apple mbox in very many places in code -- can someone tell me what its role is very generally. #asahi-dev · 2023-06-15 20:52
sid-linuxChaosPrincess: your explanation was helpful -- thanks#asahi-dev · 2023-06-15 20:51
sid-linuxso basically m1n1 does not need to do the tough part of virtualizing (sharing machine between host and VM) because there is only 1 VM and it "owns" everything#asahi-dev · 2023-06-15 20:42
sid-linuxNow if m1n1 is able to run macOS in a VM, surely it should be possible to write similar code to run the VM within linux? KVM gets in the way? Some other complexity?#asahi-dev · 2023-06-15 20:40
sid-linuxj`ey +1#asahi-dev · 2023-06-15 20:39
sid-linuxah#asahi-dev · 2023-06-15 20:38
sid-linuxbut m1n1 also has a hypervisor mode that runs macOS in a VM as a i understand...#asahi-dev · 2023-06-15 20:35
sid-linux*to work on Asahi bring