IRC channel logs
2023-03-28.log
back to list of logs
<aggi>2023-03-25 23:55:55 <oriansj> aggi: and I am guessing you have no desire to add the subset of USB support you require <aggi>the problem i see, are ACPI/APIC/BIOS/Firmware related <aggi>which is what i stumbled upon when testing a linux-2.4 kernel... it's a principle issue, to avoid ACPI-malware <aggi>and if you do, chances are USB host controller hasn't got assigned an IRQ, even when the driver-support is ready <aggi>at least, i made some progress with tcc-compiler support on linux-2.4 <aggi>which is, i could fully detangle from Kbuild, to compile with either gcc or tcc, to compare what's broken and why, and i could narrow down why the tcc-compiled kernel crashes <aggi>what's holding me back is, the USB-problem, because it's alot of work, in the end, with limited hardware-support only ... no USB <aggi>except, for some rather old hardware.. meaning there won't be much relevance with any kernel i worked on, because ACPI blocks it <aggi>and i am not interested in qemu that much, it's no solution to this problem, even when Bellard invested very much work into emulation x86 junk <aggi>the whole ACPI/BIOS/firmware related part, that's malicious <oriansj>aggi: well the only solution to that is making our own custom firmware and hardware; which honestly could be good fun <aggi>oriansj: ao486 is a starting point <aggi>i'll continue debugging linux-2.4/tcc-compiler, maybe one day this can be moved onto such a device <fossy>rickmasters, stikonas, I agree if disk is proving too difficult, let's leave it for the time being