#
…

2022-09-05

00:11e1eph4nt has quit [Ping timeout: 480 seconds]
00:28e1eph4nt has joined #asahi-dev
00:32AdryzzOLEDEdition[m]11 is now known as Lena
00:46yuyichao has quit [Remote host closed the connection]
00:54yuyichao has joined #asahi-dev
01:28jakebot602 has quit [Quit: The Lounge - https://thelounge.chat]
01:28yuyichao has quit [Ping timeout: 480 seconds]
01:31sam_folks, does anyone have an idea about https://bugs.gentoo.org/858431?
01:31sam_I'm sorry to intrude here, I'm just out of ideas -- the only person who can hit it is an apple silicon user using a gentoo vm
01:31sam_he seems to hit it on various packages with no common theme
01:32sam_cc chadmed_
01:33jakebot602 has joined #asahi-dev
01:36e1eph4nt has quit [Ping timeout: 480 seconds]
01:37yuyichao has joined #asahi-dev
01:45e1eph4nt has joined #asahi-dev
01:46rkjnsn#asahi-alt is probably the right channel for that.
01:47CatDentures has quit [Quit: leaving]
01:53e1eph4nt has quit [Ping timeout: 480 seconds]
02:01e1eph4nt has joined #asahi-dev
02:03phireI'm assuming these packages are fine on other arm64 systems?
02:10e1eph4nt has quit [Ping timeout: 480 seconds]
02:10phiremight be more of a compiler bug? assembler and codegen seem to disagree about what instructions are supported on the processor
02:12phireyes, seems the udot/sdot instructions are supported on the M1, so the assemeber is wrong?
02:18e1eph4nt has joined #asahi-dev
02:24sam_thanks rkjnsn
02:25sam_phire: yeah, completely fine on other systems
02:26e1eph4nt has quit [Ping timeout: 480 seconds]
02:27sam_the weird thing is I don't think asahi (or anyone else?) is using a patched binutils at least
02:29phireis it possible that gentoo's (or this person's) binutils is older than the gcc version?
02:34phirethough, it was added to binutils 5 years ago... I supsect compiler bug with -mnative doing diffrent things in diffrent places.
02:36e1eph4nt has joined #asahi-dev
03:27chadmed_i can try build later today on bare metal but id say its either something parallels/hv.framework does or the person has borked their compiler
03:31chadmed_ is now known as chadmed
03:43e1eph4nt has quit [Ping timeout: 480 seconds]
04:06e1eph4nt has joined #asahi-dev
04:15e1eph4nt has quit [Ping timeout: 480 seconds]
04:24e1eph4nt has joined #asahi-dev
04:56jluthra_ is now known as jluthra
05:12the_lanetly_052__ has joined #asahi-dev
05:31e1eph4nt has quit [Ping timeout: 480 seconds]
05:40e1eph4nt has joined #asahi-dev
05:54conradev8 has quit [Quit: -]
05:55conradev8 has joined #asahi-dev
06:11the_lanetly_052__ has quit [Ping timeout: 480 seconds]
06:46e1eph4nt has quit [Ping timeout: 480 seconds]
06:47jannauproblem is that gcc doesn't pass '-march=...' to the assembler for -march=native. probably because the assembler doesn't support native on aarch64
06:48jannauthis only becomes a problem when gcc codegen uses instructions from a extension
06:49jannauthis is not a problem for other distros since they don't use -march=native to build packages
06:51jannaubuilding the same software with -march=native will be a problem everywhere
06:55e1eph4nt has joined #asahi-dev
07:03e1eph4nt has quit [Ping timeout: 480 seconds]
07:04e1eph4nt has joined #asahi-dev
07:13e1eph4nt has quit [Ping timeout: 480 seconds]
07:21e1eph4nt has joined #asahi-dev
07:22fossdd has quit [Read error: Connection reset by peer]
07:22fossdd has joined #asahi-dev
07:22dingodoppelt has quit [Read error: Connection reset by peer]
07:22dingodoppelt has joined #asahi-dev
07:29e1eph4nt has quit [Ping timeout: 480 seconds]
07:55e1eph4nt has joined #asahi-dev
08:03e1eph4nt has quit [Ping timeout: 480 seconds]
08:12e1eph4nt has joined #asahi-dev
08:33leitao has joined #asahi-dev
08:35leitao has quit []
08:40maz-march=native doesn't mean much, really, as most of the features cannot be discovered from userspace.
08:40leitao has joined #asahi-dev
08:48_jannau_I think it uses HWCAP and detects "armv8-a+crypto+crc+lse+rcpc+rdma+dotprod+fp16fml+sb+ssbs+flagm+pauth"
09:11jluthra has quit [Remote host closed the connection]
09:12jluthra has joined #asahi-dev
09:19e1eph4nt has quit [Ping timeout: 480 seconds]
09:27e1eph4nt has joined #asahi-dev
09:32leitao has quit [Ping timeout: 480 seconds]
09:35M4t64[m]does it need simd stuff? try removing -march=armv8.2-a+sha3 or remove the flag
09:35M4t64[m] * does it need simd stuff? try -march=armv8.2-a+sha3 or remove the march flag
09:35e1eph4nt has quit [Ping timeout: 480 seconds]
09:43e1eph4nt has joined #asahi-dev
09:52e1eph4nt has quit [Ping timeout: 480 seconds]
09:58rmkdo we have any documentation on the SMC keys? Andy was suggesting that we should be using the endian conversion macros with the keys - does that sound correct?
10:00e1eph4nt has joined #asahi-dev
10:08e1eph4nt has quit [Ping timeout: 480 seconds]
10:17_jannau_sven: I can't get dual displays to work connected to a HP G4 thunderbolt 4 dock (M1 Max), no verification on an intel laptop yet
10:17e1eph4nt has joined #asahi-dev
10:17svenhuh, weird
10:18sventhe HW should support that
10:19_jannau_it works partially but the 2nd display has no stable output
10:20_jannau_display settings show just the unstable and internal display
10:43svenstrange
10:44svenI have one screen that is very unstable when I connect it directly to my m1 but works fine when connected through my thunderbolt dock and a DP->hdmi converter
10:46jannautried a different monitor and the instability might be caused by mirroring the same mode to both display
10:48jannauHP claims "... a dock that supports up to four 4K displays" I guess that requires DP MST support
10:51minidoes it use displaylink USB displays?
10:52minisome of the HP docks do :(
10:56leitao has joined #asahi-dev
11:01jannaunot as far as I can tell
11:02jannauthunderbolt + DP works as dual display
11:04leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
11:06svennice, looks like it’s usingn dpin0/1
11:07svenout_unk_en seems to have an additional bit set
11:08svenhrm, or maybe that’s just dispext bits instead of atc as well
11:20jannauI'll test tonight with additional displays connected through hdmi/2nd usb-c port
11:24svenunk_en is something strange, dunno what it represents yet
11:24e1eph4nt has quit [Ping timeout: 480 seconds]
11:24svenfifo_rd_unk as well
11:26dmmcf has joined #asahi-dev
11:33e1eph4nt has joined #asahi-dev
11:41e1eph4nt has quit [Ping timeout: 480 seconds]
11:45dmmcf has quit [Ping timeout: 480 seconds]
11:45dmmcf has joined #asahi-dev
11:53gladiac has joined #asahi-dev
12:01dmmcf has quit [Read error: Connection reset by peer]
12:04e1eph4nt has joined #asahi-dev
12:09leitao has joined #asahi-dev
12:36Glanzmann has joined #asahi-dev
12:41Race has quit [Ping timeout: 480 seconds]
12:57ajbio[m] has joined #asahi-dev
13:11e1eph4nt has quit [Ping timeout: 480 seconds]
13:20e1eph4nt has joined #asahi-dev
13:28e1eph4nt has quit [Ping timeout: 480 seconds]
13:29mazgah, pinhead travelling to Dublin with his M2 only. no pressure... :-/
13:30svenuh oh
13:31_jannau_he did announce that he was planning that when he got the M2
13:32svenI think the “only” part creates a bit more pressure
13:32mazwell, he's true to his earlier plan.
13:33svenis there some linux conference in dublin?
13:33j`eylinux plumbers
13:33Nspace has quit []
13:34mazplumbers, kvm forum, maintainer summit, security summit...
13:34Nspace has joined #asahi-dev
13:34_jannau_I guess the main pain point will be merging commits which are in conflicting form in linux-asahi
13:35svenj`ey: ah, nice. at least this time I don't have to regret not getting a ticket since i'll be on vacation then anyway :)
13:35mazyeah. maybe I'll convince him to run arm64 guests, just to reduce the potential pain.
13:35Glanzmannmaz: axboe already tried and failed. Good luck.
13:36mazGlanzmann: hey, it's not my laptop, and I could do *without* having him on my back when KVM breaks.
13:38e1eph4nt has joined #asahi-dev
13:40raytracer has joined #asahi-dev
13:41raytracer has quit []
13:43rmkwell, Andy Shevchenko is doubting that any of you exist...
13:43rmkWhile I agree on technical aspects, this mythical "they" is
13:43rmkfrustrating me. They haven't participated in this discussion (yet?) so
13:43rmkthey do not care, why should we (as a community of upstream)?
13:44rmkUnless you speak up, I'm going to give up with trying to upstream this gpio driver
13:44rmkI'm getting pissed off with saying "that's for the Asahi people to decide" and similar
13:45kettenisI fear the hard reality is that marcan needs to stop doing new stuff for a while and spend some serious time on upstreaming what we already have
13:45kettenis(and I still do appreciate your effort)
13:47e1eph4nt has quit [Ping timeout: 480 seconds]
13:48mazkettenis: yeah, the current trend has been worrying me for some time. the more we wait to submit this upstream, the more difficult it becomes.
13:48svenspeaking of which, i should prepare bluetooth v2
13:51wsx[m] has joined #asahi-dev
13:51kettenisupstreaming someone else's work is hard since it is harder to defend design choices you didn't make yourself
13:51wsx[m]do M2 supports nested virt? if yes, does m1n1 needs some changes to make it work in KVM?
13:51j`eywsx[m]: normal KVM should work on the m2, but nested virt is different, linux doesnt support that
13:51svenwsx[m]: yes, m1n1 needs no changes but linux itself doesn't support nested virt yet
13:52* mazlooks somewhere else.
13:52svenkettenis: yeah, especially with something as complex as SMC
13:53j`eymaz: borrow linus laptop this week to test nv :P
13:53mazj`ey: I need to rebase it and address the pending comments, which will likely take me another couple of weeks, at which point I'll be on holiday...
13:54marcankettenis: I'll have good motivation to upstream stuff when DART t6k is finally merged :p
13:54mazj`ey: also, debugging NV on a laptop without serial console isn't my idea of fun!
13:55wsx[m]sven: xen or vmware do?
13:55j`eymaz: it'll just work :P
13:55svenwsx[m]: hmm?
13:55wsx[m]nested virt on arm64
13:55j`ey(also re: andy saying asahi people dont care, it's only been a few days.. 2 of which were the weekend..)
13:55svenwsx[m]: can you try to rephrase that as a full question? i'm not sure what you're trying to ask there
13:56mazwsx[m]: xen definitely doesn't support NV on arm64. as for VMware, ask them.
13:56e1eph4nt has joined #asahi-dev
14:04e1eph4nt has quit [Ping timeout: 480 seconds]
14:12e1eph4nt has joined #asahi-dev
14:17marcanj`ey: where did he say that?
14:18j`eymarcan: look at what rmk said ^, Im assuming it was a quote from a private email..
14:18marcan(conversely, I'm not sure what andy cares about - he seems to want to review as much code as possible, as sloppily as possibly. I often wonder if he has nothing better to do.)
14:18kettenis"Re: [PATCH 5/6] gpio: Add new gpio-macsmc driver for Apple Macs"
14:18marcan(over half his review comments are completely useless, consistently - he doesn't seem to actually read the code he reviews beyond a 4-line context window)
14:19rmkj`ey: no, it's all on the mailing lists
14:20rmkmarcan: I agree, that thing about "%.4s" &cpu_to_be32(foo) was utterly idiotic
14:20j`eyrmk: sorry, I didnt see it there
14:20marcanfound it
14:21e1eph4nt has quit [Ping timeout: 480 seconds]
14:21marcanbut yeah, as far as I'm concerned Andy has been on every upstreaming thread I've had, and half his comments have been purely wasting my time explaining to him why he didn't actually read the code
14:21marcanand the other half are just nitpicks
14:22marcansome fraction of those actually taught me about some kernel functions I didn't know about, but let's just say the SNR on his reviews is abysmal
14:22marcanand he just drive-bys everything I do it seems
14:23* rmkrushes to either end of the boat to close the cratch cover and the stern hatch... it's raining! :D
14:23* marcanis replying to Andy right now in case you didn't notice
14:23rmkthanks.
14:25rmkI've made quite a few changes to the gpio driver... I'm going to boot test them soon.
14:29e1eph4nt has joined #asahi-dev
14:32chadmed has quit [Ping timeout: 480 seconds]
14:32chadmed has joined #asahi-dev
14:32rmkmarcan: seems you're right - I just read another response of his on a different thread about someone using PTR_ERR_OR_ZERO(). His comment is utter trash, designed to waste the time of the patch submitter.
14:35rmkHe could have looked up the definition himself which would've answered his question.
14:45* povikis trying to come up with a conspiracy theory :p
14:50mazpovik: don't attribute to malice...
14:53marcanhe used to comment from an Intel email, and I was convinced Intel had him in some department twiddling his thumbs and he just decided to kill time reviewing random Linux patches
14:54marcanbut now he's coming from gmail, so I don't know
14:54mazstill with Intel AFAIK. overall, I tend to ignore his comments for the stuff I care about, due to the very poor signal/noise ratio.
14:56svenmaybe Intel has some bonus or whatever tied to “number of patches reviewed” :p
14:56mazsven: I rest my case! :D
14:57leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
15:01chadmed has quit [Read error: Connection reset by peer]
15:01chadmed has joined #asahi-dev
15:06marcanrmk: sorry you had to deal with him
15:22Jamie[m]heh i thought i remembered his name, ironically he was super helpful in my first ever interaction with LKML
15:22Jamie[m]but that did concern intel gpio specifically lol
15:25rmkwell, looking at the macsmc-gpio list on my mainline kernel, the only thing I have using it is the PWREN gpio, so no interrupts...
15:33kettenistouchpad on M2 uses macsmc-gpio as well, but no interrupts there either
15:35j`eythe power button?
15:35kettenishandled as an SMC event
15:36kettenisthere is a GPIO SMC event IIRC, which could be used to implement interrupts from GPIO pins
15:36leitao has joined #asahi-dev
15:36leitao has quit [Remote host closed the connection]
15:36kettenisnot sure if that functionality has been fully worked out and whether it is actually needed anywhere
15:37e1eph4nt has quit [Ping timeout: 480 seconds]
15:40rmkdoes that mean that the patch adding IRQ support to macsmc-gpio hasn't been tested?
15:45leitao has joined #asahi-dev
15:45leitao has quit [Remote host closed the connection]
15:47kettenisnot by anybody else than marcan I think
15:47leitao has joined #asahi-dev
15:49e1eph4nt has joined #asahi-dev
15:49rmkok, booted a kernel without, wifi still works so I'll drop that patch for now as it doesn't seem to be needed yet.
15:55kettenisthe DT binding for the GPIO block doesn't include an interrupt-controller property, which I think would be required to support actual GPIO interrupts
16:11marcanrmk: fwiw everything I didn't comment on re:style and such is fine to do what Andy says, though I find it all *extremely* nitpicky and much of it a waste of time, but shrug
16:16marcanrmk: IIRC I added the GPIO IRQ stuff so that sdmmc could use them for card detect (instead of the internal one) and therefore power down the entire controller when no SD card is inserted, as part of the WIP PCIe power management stuff, but that didn't go into asahi yet since it's not done.
16:16marcanI did test it though.
16:17marcanand I pushed that patch through since it was "done" even though it doesn't have a consumer in the asahi DTs yet
16:17rmkokay, my v2 series will be:
16:17rmkdt-bindings: mfd: add binding for Apple Mac System Management Controller
16:17rmkdt-bindings: gpio: add binding for the GPIO block for Apple Mac SMC
16:17rmksoc: apple: rtkit: Add apple_rtkit_poll
16:17rmklib/vsprintf: Add support for generic FOURCCs by extending %p4cc
16:17rmkplatform/apple: Add new Apple Mac SMC driver
16:17rmkgpio: Add new gpio-macsmc driver for Apple Macs
16:18rmkarm64: dts: apple: Add SMC node to t8103/t6001 devicetrees
16:18marcanI think you also need the mailbox patch? withotu that, apple_rtkit_poll won't work (and therefore shutdown/reboot won't work properly)
16:18rmkthose six.
16:18rmkoh, let me dig that out.
16:19marcansee bits/010-mailbox
16:19marcanthe first 2 patches, but then I discovered some horribleness (that entire subsystem is a pet peeve of mine...)
16:19marcanso you might want to review the commits yourself and see if you agree
16:20marcanthat last patch in particular, I swear the original code is backwards but I just find the design of that thing so confusing
16:21marcanand I'm this close to ripping out that entire driver and embedding the mailbox support into rtkit, since it's a massive impedance mismatch and has only caused us pain (abstractions/subsystems are only useful when they actually increase the useful combinatronics - this doesn't, it just causes pain between two sides that will only ever talk to each other)
16:21marcanbut if you just want to make SMC work, the first two patches are probably all you need, even if there is lingering brokenness in the driver
16:22marcanIIRC I started running into that during an attempt to make the SMC IRQ stuff work in atomic context, before I discovered the trick to writing non-atomic irqchips
16:22marcanso chances are the atomic stuff will only ever be used for the final shutdown/reboot messages, and honestly that's never going to hit any race conditions
16:24rmkah, so that's why shutdown doesn't work very well :D
16:25atipls has joined #asahi-dev
16:27sven<3 mailbox
16:27svenI’m half expecting that we’ll have to rip that out to get reasonable agx performance anyway
16:27marcanyup, I'm waiting for that
16:27marcan"increases glxgears FPS by 30%", and out the window it goes
16:27svenit’s like what… three context switches for a single message even when the fifo is empty?
16:28marcanyes, for a GPU which seems to be explicitly designed with multiple queues just to avoid CPU lock contention
16:28marcanand then we put a pile of nonsense in the final bottleneck for what should be a single MMIO write if there is FIFO space available? lol.
16:28svenyeah…
16:29marcan(and that FIFO isn't even used right now, because mailbox)
16:29svenyeah, the maintainer didn’t like my original series which would’ve used the fifo and not done any context switche iirc
16:30marcanthat said, Apple also have some really funny overengineered stuff in their IOKit drivers, so I wouldn't be surprised if we get better FPS than them at some microbenchmarks in the end
16:31marcanbut right now we don't have to care, nothing so far cares about RTKit performance
16:31marcanlet's just wait for Lina ;)
16:32svenyeah, the only bottlenecks are DCP and agx and DCP seems to be fine
16:32marcanDCP will never be a real bottleneck, modesetting/page flipping doesn't care about a few extra context switches
16:33marcan(at least not until you're an Apple Watch or something)
16:34marcanbut AGX, yeah, that needs a doorbell that goes via mailbox for every command submission, unless the driver does some kind of batching/elision, and given how fast the hardware is apparently... I'm expecting it to matter.
16:34marcanespecially in the fully synchronous case, which I think glxgears is
16:34M4t64[m]iokit is oop hell
16:35marcanwhen the whole cycle is fractions of a millisecond and the benchmark is naive and does not queue anything, all that time wasted is FPS you lose
16:40rmkmarcan: I think the first three mailbox patches are reasonable
16:43leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
16:44rmkprobably best to send the first two only at the moment though.
16:45leitao has joined #asahi-dev
16:50rmkmarcan: yes, some companies do have a policy of tracking their involvement in the mainline kernel by monitoring mailing lists and counting messages.
16:51rmkI guess we'll see Andy pop up for those mailbox patches
16:56marcanrmk: I'll punt on the IRQ support comments since you're dropping that for now (and it could use more testing), so I think I covered everything else but DT
16:57marcanre DT, fine with compatibles, not terribly clear on how that works myself, so if you want to try it, go for it. it could be useful in the future to have per-SoC compatibles anyway so we can quirk things when inevitably my idea of "SMC can just autoprobe funniness" breaks down...
16:58marcan(as I said I'm new to mfd so feel free to screw around with how that all hooks together at that level, if it makes things better)
16:58marcanI should get some sleep, it's 2AM here :)
16:58rmkthe only issue that was brought up with changing the way that stuff works is that it's also being used in openbsd
16:58rmkyea, and I should make my supper!
16:59rmkit's 6pm here.
16:59marcanyeah; adding compatibles would be backwards-compatible though, so that much is no issue if we keep the same node names
16:59svenat least for mailbox stuff my reviewed-by should be enough to get jassi to pick them up ;)
16:59marcanalso, I can keep transitional DTs in our tree
17:00marcanpersonally, I don't want to lock us into bad bindings due to openbsd being faster than us, but I'd rather avoid flag-day hell for kettenis, so ideally feel free to make any changes where a single (non-schema-compliant is fine) DT can work both the old and the new way, and if needed we can go that route
17:01e1eph4nt has quit [Ping timeout: 480 seconds]
17:03marcanwe can also e.g. duplicate node names if we end up changing them
17:03marcanas long as it would work out for existing drivers, I don't mind keeping around an ugly DT for a while if it means the end resultis better
17:03marcan(and I don't want to come across as pushing unreviewed DTs on robher because OpenBSD picked them up either :) )
17:04rmkI think if we add compatibles, that should avoid any back-compat issues
17:04rmkas long as we keep the device node initialisation, old DT will continue to work
17:04rmkmainline can drop the device node initialisation as there's no prior history there
17:05rmkthe only thing will be that mainline won't work with old asahi dt
17:05marcanthat's fine, and I might drop the init in asahi anyway
17:05svengah, everytime i look at mailbox it manages to confuse me again *sigh*
17:05marcanfor our reference distro, we sync kernel and DTs 1:1 on update
17:05marcanso nobody will break
17:06marcanand for alt distros, well, they know they're still in playing with fire territory right? ;)
17:06marcanbut really, the sooner we get through all these growing pains the better, so thank you again for upstreaming this
17:07rmkbtw, this is home for me this week... it's the ultimate UPS - if the shore power fails, everything switches over to the boat's batteries: http://zeniv.linux.org.uk/~rmk/canals/IMG_20220529_131236.jpg
17:07svenlooks fun!
17:07marcanniiiice!
17:07rmkand then I have the option of running the diesel engine to recharge the batteries
17:08marcanreminds me I still need to redo my entire server setup... now that the Mac Studio has usable USB, I really can start the process
17:08marcanand I have a new UPS upstairs on the Threadripper temporarily, that needs to go in my studio (and the studio UPS in the server closet, probably - I think once it's all Macs that will have the lower power consumption ;))
17:08marcanright now my UPS cries every now and then due to overload, it's serving both my studio *and* server closet
17:09marcan(intel machines don't help :D)
17:10marcan(mind you, this is somewhat academic, since... I've had zero power outages and two split-second brownouts in 8 years in japan)
17:10marcan(but hey)
17:10marcananyway, I should sleep :)
17:10rmkmarcan: the supply from the marina is 16A at 240V... not that I use anything close to that. When on battery power, the inverter will support 2.5kW, but the DC wiring isn't up to that (its a job I need to sort out). 35mm² cable over about 3m... it's supposed to be about 90mm² for that distance !
17:11marcantomorrow I'll try to go through all the kernel merging stuff, especially audio, and push a 6.0 rebase to -dev
17:11marcanrmk: oof, make sure you don't accidentally overload it :D
17:12marcanmy UPSes are 300VA / 600VA IIRC, this is small scale stuff :)
17:12rmkyea, previous owners look like they did, I've already replaced the dead isolator switch, redone a load of crimp terminals, and made other changes to improve the whole thing.
17:12marcan*ouch*, but nice work on the rework!
17:13rmkthe cables in the sleeving are for the inverter.
17:14rmkthe furthest battery is for the engine start, the other two (there's actually three) are for the domestics
17:14marcanthat little dinky brown wire on the + terminal running next to sheet metal is... scaring me a bit
17:14rmkthat's via a 3A fuse for the automatic bilge pump
17:14marcanmight want to have the fuse closer to the battery :D
17:15marcanjust a cable physical integrity thing, not about the diameter
17:15marcanI imagine if something pinched that thing you'd get a nice little smoke fest
17:16rmkI suspect the wire would immitate a fuse at the current the batteries could supply
17:16marcanyup, though not before smoke and melting :)
17:16marcananyway, good night!
17:17rmknight!
17:29e1eph4nt has joined #asahi-dev
17:31leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
17:49jannausven: with 4 external displays: https://gist.github.com/jannau/80a8330219920295d534b76c2b4cabec connected and disconnected displays so a little messy
17:49jannauI can redo a more rigorous test after dinner
17:50svenhrm... looks like I have all the _UNK_EN bits slightly wrong (not very surprising :D)
17:51jannauthe dock's display outputs are probably behind a DP MST hub which would explain why only one output works
17:53svenmakes sense
18:07off^ has quit [Ping timeout: 480 seconds]
18:12off^ has joined #asahi-dev
18:25mps has quit [Quit: leaving]
18:29mps has joined #asahi-dev
18:37e1eph4nt has quit [Ping timeout: 480 seconds]
18:39atipls has quit [Remote host closed the connection]
18:39atipls has joined #asahi-dev
18:43atipls has quit [Remote host closed the connection]
18:48e1eph4nt has joined #asahi-dev
18:57gladiac has quit [Quit: k thx bye]
19:05off^ has quit [Ping timeout: 480 seconds]
19:46off^ has joined #asahi-dev
19:55e1eph4nt has quit [Ping timeout: 480 seconds]
20:02e1eph4nt has joined #asahi-dev
20:18jannaupovik: did you forgot to run dtbs_check on "arm64: dts: apple: t8103: Add MCA and its support"? the nco_clkref can not be inside 'soc {}'
20:26jannaualso it looks lite the nodes are not ordered by address
21:16e1eph4nt has quit [Ping timeout: 480 seconds]
21:24ntrung03[m] has joined #asahi-dev
21:25e1eph4nt has joined #asahi-dev
21:35derzahl has quit [Quit: auf wiedersehen]
21:37off^ has quit [Ping timeout: 480 seconds]
21:38derzahl has joined #asahi-dev
21:40off^ has joined #asahi-dev
21:43* rmkrolls his eyes.
21:44rmkAndy sent a reply privately to me... he just tried to forward the missing email to the lists etc, and instead of forwarding his private email, he forwarded one of my replies to LinusW that was already on the list with "(Replied privately to Russell by a mistake)" being the only comment.
21:57jonmasters has joined #asahi-dev
22:31e1eph4nt has quit [Ping timeout: 480 seconds]
22:40e1eph4nt has joined #asahi-dev
22:42jannauI plan to send the t600x devicetree out tomorrow based on this https://github.com/jannau/linux/tree/apple-t600x-dts-for-v6.1 (based on sound/for-next for the admac dt-bindings)
22:48e1eph4nt has quit [Ping timeout: 480 seconds]
22:51povikjannau: it's worse. i haven't yet learned to run dtbs_check at all
22:51poviki have a script to check schemas, i shall now graduate to checking the dts'es themselves
22:51povikanyway, thanks for the comments on the list
22:52poviki thought power-domains and iommus are special-cased and need not be included in schemas
22:52poviknot sure where i got that impression from
22:53jannauiirc marcan was under the same impression
22:55povikmaybe that's how it should be then!
22:56jannauI've also pushed a refreshed bits/000-devicetree, the non sorted nodes avoided conflicts there so it's not all bad
22:56povikfeel free to squash the fixups from my bits-update branch
22:56poviki have done it as fixups only so that it may be examined
22:58e1eph4nt has joined #asahi-dev
22:59jannautoo late, machine with the tree is already powered down
22:59nepeat_ has quit []
22:59jannaugood night
23:06e1eph4nt has quit [Ping timeout: 480 seconds]
23:10e1eph4nt has joined #asahi-dev
23:26nepeat has joined #asahi-dev
23:30off^ has quit [Ping timeout: 480 seconds]
23:36e1eph4nt_ has joined #asahi-dev
23:36e1eph4nt has quit [Remote host closed the connection]
23:58e1eph4nt_ has quit [Remote host closed the connection]
23:58e1eph4nt has joined #asahi-dev
…