2022-08-30
00:03cuolin^ has quit [Ping timeout: 480 seconds]
00:13dmmcf has joined #asahi-dev
00:48e1eph4nt has quit [Ping timeout: 480 seconds]
01:19e1eph4nt has joined #asahi-dev
01:19riker77_ has joined #asahi-dev
01:23riker77 has quit [Ping timeout: 480 seconds]
01:23riker77_ is now known as riker77
01:24cuolin^ has joined #asahi-dev
02:27e1eph4nt has quit [Ping timeout: 480 seconds]
02:43nicolas17 has quit [Remote host closed the connection]
02:49derzahl has quit [Remote host closed the connection]
02:50e1eph4nt has joined #asahi-dev
03:00skipwich_ has quit []
03:01skipwich has joined #asahi-dev
03:07pyropeter3 has joined #asahi-dev
03:09pyropeter2 has quit [Ping timeout: 480 seconds]
04:04e1eph4nt has quit [Ping timeout: 480 seconds]
04:05marcanI use moduleless kernels for my servers (for security/simplicity). It's a lot more practical for a sever where the hardware never changes and there is no hotplugging of random devices.
04:26e1eph4nt has joined #asahi-dev
04:34e1eph4nt has quit [Ping timeout: 480 seconds]
04:41yuyichao_ has quit [Ping timeout: 480 seconds]
04:43e1eph4nt has joined #asahi-dev
04:52pyropeter3 has quit [Quit: WeeChat 3.1]
05:07yuyichao_ has joined #asahi-dev
05:09mxw39 has joined #asahi-dev
05:16mini0n has quit [Read error: Connection reset by peer]
05:34cuolin^ has quit [Remote host closed the connection]
05:58mxw39 has quit [Quit: Konversation terminated!]
06:00DmitrySharshakov[m]Since many usecases include Mac mini or Mac Studio as a server/build machine, this option should be considered a useful one
06:01DmitrySharshakov[m]So CONFIG_APPLE_KTRR could be added which depends on !CONFIG_MODULES
06:03DmitrySharshakov[m]And maybe even ship such sealed kernels, idk. I think many people would be fine with internal hardware + standard USB classes support for some super extended security
06:05e1eph4nt has quit [Ping timeout: 480 seconds]
06:08marcanbut again we're talking about very niche spinoffs that don't really make sense to think about now :)
06:08marcanlet's get the hardware supported first and worry about special-purpose kernels and niche security setups later
06:09marcanright now, I think our priority after the hardware support is decent should be to support reasonable secure boot (i.e. chaining into existing secure boot paradigms), SEP-assisted FDE/unlock, and also Fedora Silverblue as a proof of concept that Linux can also do the macOS SSV thing
06:09DmitrySharshakov[m]marcan: of
06:10DmitrySharshakov[m]> <@_oftc_marcan:matrix.org> let's get the hardware supported first and worry about special-purpose kernels and niche security setups later
06:10DmitrySharshakov[m] * ofc
06:11DmitrySharshakov[m]What's the state of multiarch in Fedora? I haven't investigated it deeply, but looks like you cannot have x86_64 libs on aarch64 system, so emulation will require a separate dir for libs
06:12DmitrySharshakov[m]Sure, thanks
06:14e1eph4nt has joined #asahi-dev
06:17DmitrySharshakov[m]Yes, but a config option could be added for people who have special usecases
06:18DmitrySharshakov[m]E.g. an extra hardened home server. User could build without module support but with KTRR on their own
06:19mpswell, I maintained for some time special kernels for some arm SoCs on alpine linux but stopped few months ago, always someone ask to enable something and someone to disable something
06:21DmitrySharshakov[m]Shipping those is a no-way of course, that'll get crazy as people will try to convince you that all of them use some weird joystick and you should ship the driver builtin xD
06:21DmitrySharshakov[m]So leave that choice to pro users
06:24mpslong ago I used LIDS patches to kernel for servers which allowed load modules on boot and lock it in that state, so later modules can't be loaded
06:43chadmedhas anyone had a look at AVD since R last did? ive been reading the exynos codec v4l2 driver and from what i remember of her initial RE efforts it seems similar to that
06:44skipwich has quit [Ping timeout: 480 seconds]
07:01duban has quit [Quit: I'm out]
07:02duban has joined #asahi-dev
07:14skipwich has joined #asahi-dev
07:21e1eph4nt has quit [Ping timeout: 480 seconds]
07:23marcanchadmed: don't think anyone has looked at it, though some exynos legacy would not be unexpected...
07:29Race has joined #asahi-dev
07:30e1eph4nt has joined #asahi-dev
07:38e1eph4nt has quit [Ping timeout: 480 seconds]
07:47e1eph4nt has joined #asahi-dev
07:55e1eph4nt has quit [Ping timeout: 480 seconds]
07:58WindowPain_ has quit [Remote host closed the connection]
08:04e1eph4nt has joined #asahi-dev
08:09WindowPain has joined #asahi-dev
08:21jakebot602 has joined #asahi-dev
08:26jakebot60 has quit [Ping timeout: 480 seconds]
08:26jakebot602 is now known as jakebot60
08:28benpoulson has joined #asahi-dev
08:31benpoulson has quit [Remote host closed the connection]
08:46Stnby[m] has joined #asahi-dev
08:47_jannau_povik: j493 adt has 'amp-dcblocker-config = 16641' in the speaker node if you can make any sense of it
08:47uniq has joined #asahi-dev
08:48DmitrySharshakov[m]Do other machines have adt props for amp safety settings?
08:48DmitrySharshakov[m]btw which speaker has that prop, where's the whole atd dump?
08:49DmitrySharshakov[m]I guess there should be 2 speakers with this config and 4 with another or the other way around
08:51DmitrySharshakov[m]Probably that's a custom bitmask
08:51_jannau_please look at the ADT. there is a general speaker node holding references to all speakers. the macbook pro 13" has just 4 speakers
08:52DmitrySharshakov[m]Where can I look?
08:53DmitrySharshakov[m]upd it appears that it enables 2 Hz filter on both playback and rec, as well as enabling either IRQZ pullup or edge rate control
08:54DmitrySharshakov[m](derived info from the datasheet, depends on how they order MSB and LSB into registers
08:54leitao has joined #asahi-dev
08:56DmitrySharshakov[m]Appears that it's edge rate control (enabled by default after reset)
08:56DmitrySharshakov[m]Do other models have these node?
08:56DmitrySharshakov[m]Where can ADTs be found online?
08:56DmitrySharshakov[m]povik: yea, decoded it with the datasheet table
08:57DmitrySharshakov[m]Probably on private gists?
08:59leitao has quit [Read error: Connection reset by peer]
09:00leitao has joined #asahi-dev
09:06DmitrySharshakov[m]Yes, ERC is 1 after chip reset by default, so it doesn't change
09:07poviksurprising they have a prop for it on j493, i don't see one on j314, where i would reckon the 'dc blocker' is potentially more interesting to set
09:08DmitrySharshakov[m]they might've invented the idea of saving this in the DT after j314 got released
09:08DmitrySharshakov[m]probably earlier they just set the value hardcoded in the driver
09:09c10l has quit [Quit: Bye o/]
09:09c10l has joined #asahi-dev
09:15e1eph4nt has quit [Ping timeout: 480 seconds]
09:25e1eph4nt has joined #asahi-dev
09:26leitao has quit [Ping timeout: 480 seconds]
09:41Swiftloke has quit [Remote host closed the connection]
09:42Swiftloke has joined #asahi-dev
09:44sven has quit [Quit: ZNC 1.8.2 - https://znc.in]
09:44sven has joined #asahi-dev
10:11jakebot60 has quit [Quit: The Lounge - https://thelounge.chat]
10:17jakebot602 has joined #asahi-dev
10:18marcansven: not really, other than maybe it expects some init we don't do, or it's outright disabled for dcpext?
10:19svenDoesn’t get past the “waiting for hpd” thing, I’m not convinced I have the correct dpphy bringup though
10:24uniq has quit [Quit: Textual IRC Client: www.textualapp.com]
10:27marcanthe thing is, there are DCP EPIC protocols for the DP stuff that may be required for dcpext too
10:34e1eph4nt has quit [Ping timeout: 480 seconds]
10:36marcanand there is an AppleDCPDPTXRemotePort that has DisplayRequest/DisplayRelease/ConnectTo/ValidateConnection
10:38marcanconnectTo references this string: "core%u -> %u,%u (ATC%u::%s) supportsHPD=%u: ret=0x%08x"
10:38marcanso I think the iboot thing is a red herring, you should keep using that (since it's easier) and look into the other EPIC endpoints
10:40marcanit's possible the crossbar is a literal N:M of wiring? and so the dcp side has to choose the route to a given ATC, and the ATC has to choose the route from that DCP, on both ends
10:43e1eph4nt has joined #asahi-dev
10:52e1eph4nt has quit [Ping timeout: 480 seconds]
11:00e1eph4nt has joined #asahi-dev
11:04dmmcf has quit [Quit: dmmcf]
11:09e1eph4nt has quit [Ping timeout: 480 seconds]
11:18e1eph4nt has joined #asahi-dev
11:21yuyichao has joined #asahi-dev
11:22yuyichao_ has quit [Ping timeout: 480 seconds]
11:26nafod has quit [Remote host closed the connection]
11:26nafod has joined #asahi-dev
11:54marcanhooking it up now, I need some refactoring because indeed, there are 2 instances of everything here
11:55sventhere's e.g. some command followed by [cpu5] [DCPTracer@/arm-io/dcpext] [syslog] * [AppleDCPDPTX.cpp:361][AFK]powering nub 0x8553a8
12:02sventhe xnu function which sets up the crossbar is called connect and/or bringConnectionUp iirc
12:04_jannau_see reg in the dcp node https://github.com/jannau/linux/commit/d4ca404169894f84104e5c7838714ad2db76edef#diff-845c07f30f0f94856b22d7b50c0ff3d27a961abeffefcdfab01f2e8cd64569ccR357
12:21DmitrySharshakov[m]povik: Are the I2C buses amps sit on left exposed to userspace via `/dev/i2c-*`? I guess you might have to probe `i2c-dev` to find that out.
12:22DmitrySharshakov[m]Those should be hidden to ensure nobody like lm-sensors detection accidentally taps them
12:22DmitrySharshakov[m]Probably only I2C buses which should remain visible are DCP ones (when supported)
12:24DmitrySharshakov[m]Idk if i2c-dev can be made to avoid some buses in its current condition
12:26DmitrySharshakov[m]Is there any way to use ddc/ci via firmware?
12:26e1eph4nt has quit [Ping timeout: 480 seconds]
12:26DmitrySharshakov[m]Does macOS support DDC/CI on Apple Silicon machines?
12:35e1eph4nt has joined #asahi-dev
12:35AlbertoBasaglia[m] is now known as albertobasaglia[m]
12:40marcanit doesn't do anything for me, but maybe it will for you when you actually set up the xbar
13:42e1eph4nt has quit [Ping timeout: 480 seconds]
13:52e1eph4nt has joined #asahi-dev
14:12gladiac has joined #asahi-dev
14:15Race has quit [Ping timeout: 480 seconds]
14:58e1eph4nt has quit [Ping timeout: 480 seconds]
15:00e1eph4nt has joined #asahi-dev
15:18e1eph4nt has quit [Remote host closed the connection]
15:18e1eph4nt has joined #asahi-dev
15:33e1eph4nt has quit [Ping timeout: 480 seconds]
15:38e1eph4nt has joined #asahi-dev
16:11jannaupovik: amp-dcblocker-config seems to be a m2 thing. now I fear that apple uses not only per SoC kernel/driver binaries but also per SoC source code
16:32DmitrySharshakov[m]Maybe they got tired of hardcoding things and started moving more to DT? I really hope code tries to search for prefs in DT and if not found applies the hardcoded default
16:40shorneHello, I am working on installing my own kernel on the m2 air (I am a kernel developer). In grub I don't get a keyboard to select the appropriate kernel
16:41shorneso I installed the latest u-boot (as I understand), is latest uboot this one? https://github.com/AsahiLinux/u-boot/commits/asahi (0c9bd6e64020c95731caacf787d94d70daec3f16)
16:43j`eyrather https://github.com/AsahiLinux/u-boot/tree/asahi-v2022.07-3 (see: https://github.com/AsahiLinux/PKGBUILDs/blob/main/uboot-asahi/PKGBUILD#L10)
16:47shornej`ey: thanks, I see and the tag and the branch are the same commit, I didnt know of the PKGBUILDs repo yet
16:52e1eph4nt has quit [Ping timeout: 480 seconds]
17:01shornejannau: I am just remembering the error it showed, its not in front of me right now after I rebooted
17:03gladiac is now known as Guest1596
17:03gladiac has joined #asahi-dev
17:03shornej`ey: right, I could do that, at first I didn't think it was packaged yet because the only info I found was a tweet saying its fixed on a dev branch
17:05j`eyshorne: packages like uboot/kernel go into the asahi-dev repo first: https://cdn.asahilinux.org/aarch64/asahi-dev/ and then get moved into the main repo after testing
17:06clararussel[m] has joined #asahi-dev
17:09Guest1596 has quit [Ping timeout: 480 seconds]
17:15marcansven: figured out how to enable a bunch of extra DCP debug, not sure if it's useful though (see latest commits)
17:19e1eph4nt has joined #asahi-dev
17:23pabloscloud[m]So.. How far is the graphic driver? 😃
17:24pabloscloud[m]I‘m super excited about running Linux on my Mac and it already worked pretty well a months ago except videos
17:27e1eph4nt has quit [Ping timeout: 480 seconds]
17:32marcansven: also made displayRequest() not hang, so that triggers that power up message in case that helps
17:33marcanpabloscloud[m]: asking isn't going to make it go any faster, and asking in the channel where developers are trying to work on things *definitely* isn't going to make it go faster ;)
17:36e1eph4nt has joined #asahi-dev
17:49shornej`ey: ok, now I have the asahi-dev arch package repo enabled, I have keyboard and can boot my own kernels
17:56jannaushorne: should be in the asahi pkg repo as well since https://twitter.com/AsahiLinux/status/1560955501831417856
18:09bluetail21 has quit [Read error: Connection reset by peer]
18:09bluetail21 has joined #asahi-dev
18:10jakebot602 has quit [Remote host closed the connection]
18:11jakebot602 has joined #asahi-dev
18:27pabloscloud[m]<marcan> "pabloscloud: asking isn't..." <- So what? Didn’t want to make it faster
18:27jannauis up to 10Gbit/s a valid claim for the usb xhci with "pci 0000:04:00.0: 7.876 Gb/s available PCIe bandwidth, limited by 8.0 GT/s PCIe x1 link at 0000:00:03.0 (capable of 15.752 Gb/s with 8.0 GT/s PCIe x2 link"
18:28bluetail21 has quit [Read error: Connection reset by peer]
18:28bluetail21 has joined #asahi-dev
18:29bpye has quit [Quit: Ping timeout (120 seconds)]
18:29bpye has joined #asahi-dev
18:30opticronpabloscloud[m], he means that bothering the devs for status only slows them down, this is the wrong channel/room for that question anyway and pollutes discussion about development issues
18:31pabloscloud[m]Didn’t know there where other rooms
18:31pabloscloud[m]s/where/were/
18:41bluetail215 has joined #asahi-dev
18:42bluetail21 has quit [Read error: Connection reset by peer]
18:43e1eph4nt has quit [Ping timeout: 480 seconds]
18:44svenmarcan: the debug stuff is nice, still stuck at "waiting for HPD" though. I'll have to look again and see if I missed any dpphy/atcphy init
18:53e1eph4nt has joined #asahi-dev
19:11hays has quit [Remote host closed the connection]
19:25derzahl has joined #asahi-dev
19:44gladiac has quit [Quit: k thx bye]
19:45hays has joined #asahi-dev
19:48povikjannau: i just remembered seeing that one of MCA or ADMAC had surprisingly different driver kexts for t8103 and t6000 (judging on strings), so that furthers the suspicion
20:00e1eph4nt has quit [Ping timeout: 480 seconds]
20:00e1eph4nt has joined #asahi-dev
20:02bluetail215 has quit [Read error: Connection reset by peer]
20:02bluetail215 has joined #asahi-dev
20:05bluetail215 has quit []
20:07bluetail215 has joined #asahi-dev
20:09e1eph4nt has quit [Ping timeout: 480 seconds]
20:18e1eph4nt has joined #asahi-dev
20:27e1eph4nt has quit [Ping timeout: 480 seconds]
20:27bluetail215 has quit []
20:27bluetail215 has joined #asahi-dev
20:34bluetail215 has quit []
20:34bluetail215 has joined #asahi-dev
20:35e1eph4nt has joined #asahi-dev
20:45bluetail215 has quit []
20:45bluetail215 has joined #asahi-dev
20:55bluetail215 has quit [Ping timeout: 480 seconds]
21:04shornehi, as I mentioned before I am looking to help with getting s2idle working. Probably nothing new here, but I compile the kernel with CONFIG_SUSPEND on and played with "mem" suspend.
21:05shornebrcmfmac 0000:01:00.0: brcmf_pcie_pm_enter_D3: Timeout on response for entering D3 substate
21:08jannaushorne: I don't think so. marcan is planning to use the PCI tracer he started yesterday to see what macos is doing
21:12bluetail215 has joined #asahi-dev
21:31StupidYui has joined #asahi-dev
21:42e1eph4nt has quit [Ping timeout: 480 seconds]
21:59Manouchehri_ has quit []
22:26e1eph4nt has joined #asahi-dev
22:28bluetail215 has quit []
22:29bluetail215 has joined #asahi-dev
23:31e1eph4nt has quit [Ping timeout: 480 seconds]
23:40e1eph4nt has joined #asahi-dev
23:49jluthra_ has quit [Remote host closed the connection]
23:49jluthra_ has joined #asahi-dev