#
…

2021-03-11

00:46aquijoule_ has joined #asahi
00:48richbridger has quit [Ping timeout: 264 seconds]
01:18br377 has left #asahi ["WeeChat 1.9.1"]
01:23br377 has joined #asahi
01:49amboar has quit [Ping timeout: 245 seconds]
01:51Namidairo_ has quit [Ping timeout: 260 seconds]
01:52Namidairo has joined #asahi
02:04amboar has joined #asahi
02:05zkrx has quit [Ping timeout: 264 seconds]
02:29zkrx has joined #asahi
02:32Mrmaxmeier3 has joined #asahi
02:33Namidairo_ has joined #asahi
02:33gabiruh_ has joined #asahi
02:34marvin24 has quit [Ping timeout: 240 seconds]
02:34marvin24 has joined #asahi
02:35angelXwind has joined #asahi
02:36Mrmaxmeier has quit [Quit: Ping timeout (120 seconds)]
02:36Namidairo has quit [Quit: ZNC - https://znc.in]
02:36gabiruh has quit [Quit: ZNC 1.7.5 - https://znc.in]
02:36akemin_dayo has quit [Remote host closed the connection]
02:36Mrmaxmeier3 is now known as Mrmaxmeier
02:43riker77_ has joined #asahi
02:44riker77 has quit [Ping timeout: 260 seconds]
02:44riker77_ is now known as riker77
03:09porkbone has quit [Ping timeout: 260 seconds]
03:09porkbone has joined #asahi
03:11nicolas17 has quit [Quit: Konversation terminated!]
03:44phiologe has quit [Ping timeout: 260 seconds]
03:44PhilippvK has joined #asahi
04:03br377 has quit [Remote host closed the connection]
04:04br377 has joined #asahi
04:10br377 has quit [Ping timeout: 264 seconds]
04:13br377 has joined #asahi
04:16Glanzmann has quit [Quit: leaving]
04:43marvin24 has quit [Ping timeout: 260 seconds]
04:43marvin24_ has joined #asahi
05:36odmir has quit [Remote host closed the connection]
06:00korzq has joined #asahi
06:00korzq has quit [Changing host]
06:00korzq has joined #asahi
06:07zkrx has quit [Ping timeout: 260 seconds]
06:09amboar has quit [Ping timeout: 260 seconds]
06:18taziden has quit [Ping timeout: 260 seconds]
06:25dsR1904 has joined #asahi
06:27zkrx has joined #asahi
06:30VinDuv has joined #asahi
06:39taziden has joined #asahi
07:05alvaro_fe has quit [Ping timeout: 260 seconds]
07:05alvaro_fe has joined #asahi
07:07vimal has quit [Ping timeout: 260 seconds]
07:10mxw39 has quit [Quit: Konversation terminated!]
07:32VinDuv has quit [Quit: Leaving.]
07:45amboar has joined #asahi
08:04raster has joined #asahi
08:09M1f4a9[m] has joined #asahi
08:11TheJollyRoger has quit [Remote host closed the connection]
08:12TheJollyRoger has joined #asahi
08:13M1f4a9[m] has left #asahi [#asahi]
08:13M1f4a9[m] has joined #asahi
08:17marcanI'll wait a bit before firing off the tweets
08:19winocmnice article
08:22JTLGave it a brief skim (will read more later). Very impressed with the progress so far.
08:35svennice article :)
09:00user1tt[m] has quit [Quit: Idle for 30+ days]
09:00dpatterbee[m] has quit [Quit: Idle for 30+ days]
09:19bpye has joined #asahi
09:27eric_engestrom has quit []
09:27eric_engestrom has joined #asahi
09:27vimal has joined #asahi
09:34vimal has quit [Ping timeout: 272 seconds]
09:52vimal has joined #asahi
10:29pipcet[m]Hello everyone. I'm a GNU/Linux developer who just got an M1 MacBook Pro to run Linux on.
10:31pipcet[m]I'm a bit confused about the different Linux kernel ports. I'm currently using the Corellium kernel and running Debian on top of that, and that appears to work. At what point would it make sense to start working with the Asahi kernel repo instead?
10:32j`eypipcet[m]: what's your goal?
10:33maz|pipcet[m]: I guess it depends what you want to do. the current state of the Asahi kernel is much more primitive, but does the right thing in terms up upstreaming.
10:35pipcet[m]Are you planning on reimplementing everything the Corellium kernel does, but doing so in a better way?
10:35j`eythat's the eventual goal
10:35pipcet[m]My goal, right now, is to compile my own kernel and debug it.
10:35j`ey(well the goal is to upstream them)
10:36j`eypipcet[m]: debug the kernel?
10:36maz|heresy!
10:36pipcet[m]sorry, work on the drivers :-)
10:36pipcet[m]I didn't mean running a debugger on it.
10:38jn__debug also means, in general, to find and eradicate bugs
10:38j`eypipcet[m]: we dont know what corellium plans on doing with their code
10:39sventheir code is at least a good reference as to how parts of the hardware work, but I expect much of it will look very different when upstreaming it
10:42jannaupipcet[m]: do you have a way to access the serial over the USB-C port? If not it's working with m1n1 or the asahi kernel is currently quite limited and annoying
10:42j`eysounds like sven is making some progress on USB stuff though :-)
10:42svenI haven't looked at it very much but the parts I've seen look like they more or less reimplement what apple does instead of figuring out how linux would handle it
10:43svenj`ey: yeah, if everything works out I should be able to get a cdc device up and running this weekend. so probably another 2-3 weeks ;)
10:43jannaualthough testing a different kernel with coerllium's preloader is as annoying
10:43pipcet[m]jannau: I don't think so. I don't have a second M1 Mac, at least :-)
10:44jn__in case anyone hasn't seen it yet
10:45j`eypipcet[m]: what sven is working on should allow using a normal usb cable with m1n1
10:46svenessentially enumeration (i.e. descriptors, set address, set configuration etc.) and control transfers work with a linux host. Mac OS doesn't like what I'm doing at all though and balks directly after a reset so far
10:46pipcet[m]jannau: it certainly is annoying to have to go through 1TR whenever I want to boot a new kernel.
10:47pipcet[m]sven: are you at the point yet where you can bitbang data from/to a Linux computer connected with a standard USB cable?
10:48svenpipcet[m]: essentially yes. I could abuse control transfers to do that
10:48svenbut implementing the CDC device side shouldn't take much work at this point
10:49svenand after that all of m1n1's tooling should just work with a normal usb cable
10:51pipcet[m]sven: awesome, I think that would mean many more people could help and test.
10:51svenyup :-)
11:41Ravenheart has joined #asahi
11:49odmir has joined #asahi
11:53odmir has quit [Ping timeout: 245 seconds]
12:03klaus has joined #asahi
12:21amonakov has joined #asahi
12:43amonakovhi folks. I wonder if someone could enlighten me about interrupt handling conventions on Linux: is there some mechanism that would prevent invoking a handler while it is in progress on another CPU for a previous interrupt from the same device?
12:43amonakovafaict it is not covered in the usual books and docs. details and context of my curiousity: https://lore.kernel.org/netdev/alpine.LNX.2.20.13.1802012234510.5946@monopod.intra.ispras.ru/T/
12:53maz|amonakov: invoking a handler from interrupt context involves taking a lock on the interrupt descriptor. by construction, you can't have the same interrupt being handled on another CPU.
13:03commandoline_ has joined #asahi
13:03tpw-rules has joined #asahi
13:03zarvox_ has joined #asahi
13:04br377_ has joined #asahi
13:04PendulumSwinger9 has joined #asahi
13:04balrog_ has joined #asahi
13:06tarzeau_ has joined #asahi
13:06krbtgt_ has joined #asahi
13:06ml_ has joined #asahi
13:06amonakovmaz|: thank you, this helps, but unfortunately doesn't answer my Real Question about interrupt disabling for netconsole (from the link)
13:06scubasteve has joined #asahi
13:06dfff has joined #asahi
13:07e9 has joined #asahi
13:07kallsyms has joined #asahi
13:07milek7_ has joined #asahi
13:07_ghost_ has quit [Ping timeout: 256 seconds]
13:07commandoline has quit [Ping timeout: 256 seconds]
13:07tpw_rules has quit [Ping timeout: 256 seconds]
13:07br377 has quit [Ping timeout: 256 seconds]
13:07balrog has quit [Ping timeout: 256 seconds]
13:07zarvox has quit [Ping timeout: 256 seconds]
13:07scubasteve_ has quit [Ping timeout: 256 seconds]
13:07Janhouse has quit [Ping timeout: 256 seconds]
13:07PendulumSwinger has quit [Ping timeout: 256 seconds]
13:07krbtgt has quit [Ping timeout: 256 seconds]
13:07tarzeau has quit [Ping timeout: 256 seconds]
13:07vup has quit [Ping timeout: 256 seconds]
13:07Shiz has quit [Ping timeout: 256 seconds]
13:07crabbedhaloablut has quit [Ping timeout: 256 seconds]
13:07nico_32 has quit [Ping timeout: 256 seconds]
13:07ml has quit [Ping timeout: 256 seconds]
13:07dff has quit [Ping timeout: 256 seconds]
13:07emptynine has quit [Ping timeout: 256 seconds]
13:07milek7 has quit [Ping timeout: 256 seconds]
13:07Shiz has joined #asahi
13:07agraf has quit [Ping timeout: 256 seconds]
13:07PendulumSwinger9 is now known as PendulumSwinger
13:07balrog_ is now known as balrog
13:07e9 is now known as emptynine
13:07crabbedhaloablut has joined #asahi
13:08vup has joined #asahi
13:08agraf has joined #asahi
13:08Jangal has joined #asahi
13:10nico_32 has joined #asahi
13:11maz|amonakov: maybe you could as your "Real Question" directly then...
13:11j`eyjust ping him!
13:11j`eyerr, wrong channel
13:18amonakovmaz|: for netconsole, drivers implement "ndo_poll_controller" callback which in many cases is implemented as invoking the device's interrupt handler, bracketed by interrupt disable-enable
13:18amonakovthe issue is, some drivers do disable_irq/enable_irq (which is fine), but other drivers do local_irq_save/restore, which looks quite suspicious as it wouldn't do anything to prevent the handler running on another CPU as a result of a hardware interrupt
13:18amonakovI couldn't find any explanation as to why local_irq_save is sufficient in that context (apart from "netconsole in those drivers is unsafe on SMP")
13:24robinp_ has quit [Read error: Connection reset by peer]
13:24simjnd[m] has joined #asahi
13:26mandresic[m] has joined #asahi
13:28simjnd has joined #asahi
13:29simjnd has quit [Client Quit]
13:33marcanpipcet[m]: basically we're working on doing everything in an upstreamable way, so it takes a bit more time but it should be more efficient in the long term (since linux kernel forks aren't sustainable long-term)
13:33marcanI don't really know what corellium's plans are, since unfortunately they haven't interacted with the linux kernel community at all to date
13:34marcanso lacking further info and a communications channel, we're basically working on our own
13:34marcanthe goal is indeed to support all the hardware, including the GPU, and upstream it :)
13:35simjnd[m]have you tried to reach out to them to see if you could share information?
13:35marcanI did invite them to our IRC (over twitter) and the corellium guy writing the linux patches was CCed on my upstream submissions
13:35pipcet[m]thank you, that's really interesting. Weird that they don't want to communicate, apparently.
13:35maz|amonakov: I wouldn't be surprised if these drivers were just broken on SMP, having been implemented on (old) UP systems.
13:36krbtgt_ has quit [Changing host]
13:36krbtgt_ has joined #asahi
13:39pipcet[m]what's also weird is that they've continued working on the kernel after producing the mach-o image they offer for download. Which, if it's based on the code on github, must do things in the initrd that I don't know about yet, because just rebuilding it from the relevant commit results in a broken kernel.
13:40thestr4ng3r has quit [Read error: Connection reset by peer]
13:42thestr4ng3r has joined #asahi
13:45thestr4ng3r has quit [Read error: Connection reset by peer]
13:46thestr4ng3r has joined #asahi
13:53jannaupipcet[m]: the last time I looked (end of january, before nvme support) corellium did not use a initrd. Using the config extracted from their kernel resulted in booting kernel
13:54amonakovmaz|: alright, then perhaps I was not too off base with my initial understanding. thank you
13:54jannauuse scripts/extract-ikconfig to extrac the confg from their kernel image
13:55pipcet[m]jannau: CONFIG_INITRAMFS_SOURCE="~/cmw/avirt/psc/linux64/initrd-autofs.cpio.gz"
13:55pipcet[m]this is from a running system with their nvme kernel, /proc/config.gz
13:58pipcet[m]and the kernel boots, but usb, keyboard, touchpad, wifi are all broken (framebuffer works, though)
14:01jannauare the relevant drivers built-in or loadable modules? wifi requires a firmware blob which might be in their initrd\
14:06pipcet[m]modules, I believe.
14:07pipcet[m]their firmware blob is on the nvme disk which it does find
14:07pipcet[m]er, the firmware blob
14:07pipcet[m]but now I know it's gzip, I can just find the cpio image in the macho by looking for the signature! How did I miss that?
14:46vimal has quit [Remote host closed the connection]
14:49vimal has joined #asahi
15:13chivay_ is now known as chivay
15:22br377_ has quit [Remote host closed the connection]
15:22thestr4ng3r has quit [Read error: Connection reset by peer]
15:22br377_ has joined #asahi
15:24thestr4ng3r has joined #asahi
15:30br377_ has quit [Quit: WeeChat 1.4]
15:36odmir has joined #asahi
15:40tpw-rules is now known as tpw_rules
15:41odmir has quit [Ping timeout: 276 seconds]
16:15br377 has joined #asahi
17:05mxw39 has joined #asahi
17:16roxfan has quit [Ping timeout: 260 seconds]
17:27zopieux has quit [Ping timeout: 260 seconds]
17:28zopieux has joined #asahi
17:31wmehilos has joined #asahi
17:49roxfan has joined #asahi
17:50davidrysk[m]pipcet: does their initrd contain busybox or similar stuff?
17:55roxfan has quit [Ping timeout: 276 seconds]
17:57vimal has quit [Remote host closed the connection]
18:06VinDuv has joined #asahi
18:06vimal has joined #asahi
18:12roxfan has joined #asahi
18:13roxfan2 has joined #asahi
18:16thestr4ng3r_ has joined #asahi
18:16thestr4ng3r has quit [Ping timeout: 256 seconds]
18:17roxfan has quit [Ping timeout: 256 seconds]
18:20taziden has quit [Ping timeout: 272 seconds]
18:31dsR1904 has quit [Quit: Connection closed]
18:41choozy has joined #asahi
19:00pipcet[m]just a rather small stripped binary /init
19:01pipcet[m]but I built their kernel with their initrd, and it still doesn't work. So I must be doing something else wrong.
19:02taziden has joined #asahi
19:16KindTwo has joined #asahi
19:17KindOne has quit [Ping timeout: 272 seconds]
19:17KindTwo is now known as KindOne
19:44jaalsa has quit [Quit: jaalsa]
19:47commandoline_ has quit [Changing host]
19:47commandoline_ has joined #asahi
19:49commandoline_ is now known as commandoline
20:01VinDuv has quit [Quit: Leaving.]
20:01VinDuv has joined #asahi
20:10aquijoule_ has quit [Remote host closed the connection]
20:11aquijoule_ has joined #asahi
20:17roxfan2 is now known as roxfan
21:10raster has quit [Quit: Gettin' stinky!]
21:13nicolas17 has joined #asahi
21:36odmir has joined #asahi
21:51ender| has joined #asahi
22:03klaus devs (such as myself). i wish all courage and good progress. i hope to free my laptop from prison-bsd (macos) asap ;)
22:03klausthe progress report blog post was very thorough. that must be the deepest progress report i've read yet. that was so much more than i expected. amazing work going on. glad to see it will be a monthly thing too, like for dolphin emu. i don't know if the next ones will be as deep as this one, but it is a very good read, and also a source of interest and entry point into discovery about the inner working of linux, even for less skilled
22:04VinDuv has quit [Quit: Leaving.]
22:44ml_ is now known as ml
23:53choozy has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
…