2021-09-24
00:20quarkyalice_ has joined #asahi
00:21quarkyalice has quit [Ping timeout: 480 seconds]
00:44aralyssa: i only remember that there's a, i think, 2 week window after a release of a given version where subsystem maintainers and other people can send pull requests to linus and hope that their stuff lands in the -rc1, or that the problems are small enough to get fixed before rc2
00:45arbut i only ever look at it from the outside, to see if there are interesting changes to drivers that affect me
01:09hspak has quit [Quit: bye]
01:12hspak has joined #asahi
01:16yuyichao has joined #asahi
02:29phiologe has quit [Ping timeout: 480 seconds]
03:13marvin24 has joined #asahi
03:16marvin24_ has quit [Ping timeout: 480 seconds]
05:03linearcannon_ is now known as linearcannon
05:51svenalyssa: three or so patches for tipd should be in linux-next starting today. they are the boring ones though and only ~5 lines
05:51svenit's meant for maintainers who send pull requests directly to linus to make sure everything works and iron out conflicts as soon as possible
06:05marcansven: so AFAICT the downstream/upstream idle (no device) states are the same as the reset state for the eUSB2 phy
06:06marcanI'm guessing that works because if you reset the eUSB2 repeater while gadget mode is connected, it detects that as a disconnect, and as part of that sequence issues an eUSB2 reset/reconfigure
06:07marcan(and that's why it works sometimes, depends on who detects the reset first, tipd or the phy, and how fast you unplug the connector...)
06:08marcanso the question is, can we poke some phy regs to force an eUSB2 reset without using a big hammer on the controller
06:09sven(but then sometimes makes dwc3 fail because I didn't do a complete reset I guess and broke some internal state machine :D)
06:32aleasto has joined #asahi
07:31nbnm has joined #asahi
08:02coolshaurya[m] has joined #asahi
08:18X-Scale has joined #asahi
08:23X-Scale` has quit [Ping timeout: 480 seconds]
08:38nbnm has quit [Ping timeout: 480 seconds]
09:11FireFox317 has joined #asahi
09:13FireFox317Finally decided to buy my first apple hardware with the M1 chip, the MacBook Air. Cannot wait to put m1n1 on this thing and try to boot Linux xd
09:24robinp_ is now known as robinp
09:30chadmed has joined #asahi
09:55FireFox317 has quit [Remote host closed the connection]
10:08tophevich[m]marcan: what do you reckon, next progress report ~ v5.15 or v5.16?
10:10marcanI cover things whatever their progress is, which version they land in doesn't really matter
10:13tophevich[m]ah, cool, earlyier than expected, thought releases of stable kernel versions would give you the best "kick" in the buttocks to cover the progress, as you mentioned that it's hard to get the motiviation to write those.
10:15* tophevich[m]is always reminded of this sketch: https://www.youtube.com/watch?v=OQnd5ilKx2Y when using "reckon" :D
10:30marcantophevich[m]: I said I'd do less crazy updates monthly from now on, I hope I can keep to that :)
10:34tophevich[m]aye, also if you do it more frequently it is easier to digest. I guess summarizing also helps you yourself to get a better overview on the current state, and gives ideas on how to best proceed.
11:23chadmedlikewise yeah but i find asahi to be remarkably undrinkable warm, moreso than other beers
12:17nbnm has joined #asahi
12:27nsklaus_i wonder why they've choosen such kanji keys for the macintosh apple. 旭 features two keys: 九and 日 (nine and day). maybe something related to mcintosh apples takes 9 days to happen ?
12:35marcanthe "morning sun" meaning is from the original chinese, phonetic-semantic composition (九 is the phonetic component, 日 is the semantic component)
12:38nsklaus_marcan: if i follow you correctly, then 旭 is a more traditional/closer to primitive japanese derived from chinese, way of saying 朝日 ?
12:39nsklaus_i never saw it spelled 旭 before, but i know only current japanese, and i may have overlooked that spelling too
12:41alyssaand now I can drop the "clk_ignore_unused" hack in my cmdline which was pretty awful, so that's nice 👍
12:42marcanalyssa: 2bed6110 won't work as is "on purpose" because I hadn't decide if m1n1 should fix that borkage or we should just re-define it
12:43marcanyou want to remove ps_ans2 from ps_apcie_st and instead have the ans device node depend on both ps_ans2 and ps_apcie_st
12:43j_eymarcan: yeah but it's not a useful commit if youre trying to merge that branch into yours :P
12:45marcananyway, I'll rebase and add a bunch of register defines just for documentation's sake, maaybe implement auto-pm just to see how that goes, and throw it upstream soon
12:47marcanI really don't know what the perfstate regs do; xnu just initializes them all from ADT data and then ~never touches them afaict
12:52marcanif linux has to manage some we can take care of that later, but at least that way it doesn't have to init everything
14:22svenah yes. i love how rebasing on the latest linux-next essentially triggers a full kernel rebuild. and ccache doesn't seem to help :(
14:22nbnm has quit [Read error: Connection reset by peer]
14:34nsr has joined #asahi
14:36yuyichao has quit [Ping timeout: 480 seconds]
14:36nsrHoy! Started around playing with asahi/m1n1, great&impressive stuff! One question though: I'm trying to access the ARMv8 PMU registers, but getting a SYNC exception upon trying. Couldn't find any solution yet, any insights? Is apple silicon locking those away?
14:49maznsr: there's an IMPDEF PMU, but there is absolutely no documentation (or at least none I'm aware of) for the programming model or the characterisation of the events. that'd certainly be an interesting project for someone to RE! ;-)
14:52_jannau_nsr: at least parts of apple's pmu code is the in open source part of xnu. Apple also made more performance counters available in mac os recently
14:52yuyichao has joined #asahi
14:53jbowen has quit [Quit: leaving]
14:53maz_jannau_: do you happen to know if they have described the nature of the events in any sort of detail?
14:56_jannau_not sure if apple has documentation about the semantics of the counters in Instruments (part of xcode)
15:03brinly_ has joined #asahi
15:08brinly has quit [Ping timeout: 480 seconds]
15:08brinly_ is now known as brinly
15:25nctcf^ has joined #asahi
15:43marcannsr: we have some documented here too: https://github.com/AsahiLinux/docs/wiki/HW:ARM-System-Registers
16:42phiologe has joined #asahi
16:48svenhuh... looks like i also just somehow managed to get one of the usb-c port into a broken state on my macbook air running macOS
16:52alyssai will not nerdsnipe myself into writing a jpeg driver i will not nerdsnipe myself into writing a jpeg driver i will not nerdsnipe myself into writing a jpeg driver i will not nerdsnipe myself into writing a jpeg driver i will not nerdsnipe myself into writing a jpeg driver
16:52svenand it looks like that got *both* m1 machines into a state where that port just refuses to work :D
16:55alyssaand conveniently noticing the ADT for the JPEG block makes it seem especially simple to the extent it might be possible to just ... guess my way through
16:55svenif even doing _that_ makes it unstable i feel like trying to be clever and getting away with partial resets or PHY only resets might just make it worse
16:56marcanand I can confirm idevicerestore fails with in, for multiple reasons only one of which I've fixed so far :)
16:57marcansee https://github.com/libimobiledevice/usbmuxd/pull/177 https://github.com/libimobiledevice/idevicerestore/issues/442 https://github.com/libimobiledevice/idevicerestore/issues/441
17:10roxfan has joined #asahi
18:07svenyup. and this works semi-reliably: connect both usb ports (maybe one is also enough), wait until the linux tells you that the serial gadget is attached and then unplug the cable.
18:44yuyichao has quit [Ping timeout: 480 seconds]
18:53tomtastic_ has quit [Quit: ZNC - https://znc.in]
18:54tomtastic has joined #asahi
19:14fdsdcv has joined #asahi
19:33Orsira has joined #asahi
20:02aleasto has quit [Ping timeout: 480 seconds]
20:28d4ve has quit [Ping timeout: 480 seconds]
20:28d4ve has joined #asahi