#
…

2021-10-13

00:31* alyssawaves her wand to make the magic numbers go away
00:31yuyichao_ has joined #asahi-dev
00:35yuyichao has quit [Ping timeout: 480 seconds]
00:41alyssa 2633 total
00:41alyssastill much too large a driver :'(
00:42alyssaand too much... sketchy
00:49robinp_ has quit [Read error: Connection reset by peer]
01:14yuyichao_ has quit [Ping timeout: 480 seconds]
01:36alyssabeen investigating the Xorg hotplug thing
01:37alyssacorrect hotplugging depends on atomic_flush() getting called on hotplug, but I guess Xorg doesn't do that
01:37brentr123[m]When next stream?
01:45alyssayou really don't want a kernel stream
01:45alyssa^from me
01:46brentr123[m]I meant Marcus
01:50alyssadrm_client_modeset "looks" like it does what you want, but it seems to be a fbdev thing...?
02:20alyssaoh. it's a wontfix. xorg doesn't support displayport hotplugging without a DE.
02:22chadmedfriendship ended with Xorg now wayland is my best friend
02:25phiologe has joined #asahi-dev
02:27PhilippvK has quit [Ping timeout: 480 seconds]
03:03yuyichao_ has joined #asahi-dev
03:52kov has quit [Quit: Coyote finally caught me]
03:52kov has joined #asahi-dev
06:03dottedmagalyssa: X and atomic modesetting... Not a love at first sight. Have you seen https://github.com/torvalds/linux/commit/26b1d3b527e7bf3e24b814d617866ac5199ce68d ? (also that's why never name your DRM client binary Xtreme)
06:06svenor just set req->value > 1 if your binary starts with X i guess
06:06svenbut that's quite a hack. X must've screwed up pretty badly :D
06:29ardottedmag: wait, so xf86-video-modesetting has broken idea of atomic, and they decide to break atomic for everyone?
06:40dottedmagar: For every binary with name starting with capital X
06:40svennah, not everyone. only every process that starts with X! :-P
06:41svenbut seriously, enabling a workaround depending on the process name kinda sounds like X messed up in truly horrible ways
07:09j_eyis that actually in the kernel?
07:09j_eyor is it april fools or something
07:09svenpretty sure it's in the kernel
07:11svenyeah. that's why I assume that X must've messed up pretty badly
07:22kode54 has quit [Quit: Ping timeout (120 seconds)]
07:23grange_c has quit [Quit: Ping timeout (120 seconds)]
07:23kenzie has quit [Quit: Ping timeout (120 seconds)]
07:24vx^ has quit [Quit: :)~]
07:26blasty has quit [Remote host closed the connection]
07:26nico_32 has quit [Remote host closed the connection]
07:28akemin_dayo has quit [Ping timeout: 480 seconds]
07:29Ziemas has quit [Remote host closed the connection]
07:41nico_32 has joined #asahi-dev
07:42blasty has joined #asahi-dev
08:20vx^ has joined #asahi-dev
08:20Ziemas has joined #asahi-dev
08:21kode54 has joined #asahi-dev
08:23grange_c has joined #asahi-dev
08:25kenzie has joined #asahi-dev
08:27akemin_dayo has joined #asahi-dev
09:08marcanthis is windows driver process name hacks level
09:12mjg59Kind of amazed that got in, yeah
09:13j_eylinus must have missed it :P
09:13mjg59Not sure there's an actually better solution, though
09:13chadmedyeah doesnt linus have a thing about userspace stuff imposing itself on kernel decisions? seems like a pretty big thing for him to miss given that
09:15archadmed: "don't break userspace, ever"?
09:16chadmedwell that but also the obverse. i remember him kicking up a massive stink about lennart trying to get kernel maintainers to change stuff to accommodate systemd's design decisions. maybe i am misremembering
09:18aryeah, lennart tried to hijack "debug" kernel commandline argument
09:19JTLchadmed: I seem to remember that too?
09:19svenit sounds like this was just a terrible situation with no good solution. and i guess that hack was just the least bad solution in the end
09:20chadmedwell i mean we could just all move to wayland and have cute puppies and no more war and hunger :P
09:20chadmedbut the green gpus wont let us have those nice things
10:38JTL1 has joined #asahi-dev
10:39JTL is now known as Guest2710
10:39JTL1 is now known as JTL
10:39Guest2710 has quit [Ping timeout: 480 seconds]
10:39JTL has quit []
10:40JTL has joined #asahi-dev
10:44bps has quit [Remote host closed the connection]
10:45bps has joined #asahi-dev
10:49JTL is now known as JTL1
10:50JTL1 has quit []
10:50JTL has joined #asahi-dev
10:59kettenisah, I had forgotten all about that gem
11:04dhewgI already like it at the "Fixes:" line
11:05aleasto has joined #asahi-dev
11:08kettenisoff-topic, but boy it is amazing how Intel keeps pushing out broken hardware
11:08chadmeddhewg: thats filthy lmao. october 18 baby i say goodbye to amd64 forever
11:09chadmed(hopefully)
11:09kettenisthere literally isn't any single clock that you can use on x86 systems that isn't broken on some systems
11:10kettenisI think ARM got it spot on with have the architecturally defined timer that includes a register that tells you the frequency it runs at
11:10kettenis(admittedly only with armv7 and later)
11:10chadmedthe solution is simple. intel needs to add yet another clock source that is a tiny bit broken in some use cases but fixes the use cases in which the other clocks are broken. its all about "flexibility" after all!
11:37ari'm reasonably happy with all my private x86 systems, but the only intel chips in them are NICs (wifi or wired) or thunderbolt controllers
11:50chadmed yeah ive been having this discussion with my mates. in the grand scheme of things this stuff doesnt _really_ affect the platform's usability. i type "emerge libreoffice" on both and get a working office suite. its not a matter of being unhappy with the performance of my x86 box, (for me) its more a growing dissatisfaction with the platform's design philosophy.
11:51ketteniswell, AMD CPUs and chipsets have similar issues
11:52chadmedyeah wasnt too happy when i found out about the platform "security" processor...
12:40arndkettenis: The hardware timer is supposed to be there on ARMV7VE (Cortex-A7/A15) or later, but there are enough examples of it being broken in certain SoCs, I don't think there is any hope of ARM being less of a trainwreck in this area than Intel
12:44kettenisarnd: well, so far, in my experience it is less of a trainwreck
12:45kettenisyes, there are hardware bugs, but in most cases they can be worked around
12:46kettenisalthough I suppose that when I'd try to do more aggressive power management, more bugs will pop up
12:47arndDocumentation/devicetree/bindings/timer/arm,arch_timer.yaml in Linux lists a number of errata for the timer. In most cases this ends up meaning that we can't use it from user space because it's unreliable
12:49arndalso, timer bugs are notoriously hard to find, because you can't rely on the timer to tell you when it goes wrong. One example is the Samsung Exynos, which has a timer that almost always has the correct values, but once in a blue moon produces nonsense
12:49arnd(I assume newer versions fixed it, this was exynos5 IIRC)
12:51arndI'd also include the way that Apple hooks up the timer to the FIQ in this, regardless of whether this is technically compliant or not
12:57psykosetimers must just be very hard for almost every vendor to have a bunch of broken timers
12:57psykosei don't think they intentionally want to consistently have a bunch of broken things every release
13:13dottedmagpsydroid: I might be talking out of my ass here, because I really have no clue... But isn't it due to grafting new timer-changing features onto existing ISA? E.g. virtualization and power management change everything related to timers.
13:41jbowen has joined #asahi-dev
14:05krbtgtit's all about implementation
14:07yuyichao_ has quit [Ping timeout: 480 seconds]
14:14el0y has joined #asahi-dev
14:24yuyichao_ has joined #asahi-dev
15:20bps has quit [Ping timeout: 480 seconds]
15:56bps has joined #asahi-dev
16:15bps has quit [Ping timeout: 480 seconds]
16:28yuyichao has joined #asahi-dev
16:32yuyichao_ has quit [Ping timeout: 480 seconds]
17:09yuyichao_ has joined #asahi-dev
17:13yuyichao has quit [Ping timeout: 480 seconds]
17:15jbowen has quit [Ping timeout: 480 seconds]
17:16jbowen has joined #asahi-dev
17:20___nick___ has joined #asahi-dev
17:20___nick___ has quit []
17:22___nick___ has joined #asahi-dev
17:54yuyichao has joined #asahi-dev
17:58yuyichao_ has quit [Ping timeout: 480 seconds]
17:58yuyichao_ has joined #asahi-dev
18:03yuyichao has quit [Ping timeout: 480 seconds]
18:18bps has joined #asahi-dev
18:21rgort10[m] has joined #asahi-dev
18:33yuyichao has joined #asahi-dev
18:36yuyichao_ has quit [Ping timeout: 480 seconds]
18:42bps has quit [Ping timeout: 480 seconds]
18:58yuyichao_ has joined #asahi-dev
19:01erincandescent has quit [Remote host closed the connection]
19:02erincandescent has joined #asahi-dev
19:02yuyichao has quit [Ping timeout: 480 seconds]
19:18jacoxon has joined #asahi-dev
19:30gabuscus_ has joined #asahi-dev
19:32jacoxon has quit []
19:34gabuscus has quit [Ping timeout: 480 seconds]
19:45jacoxon has joined #asahi-dev
19:45jacoxon has quit []
19:47___nick___ has quit [Ping timeout: 480 seconds]
19:47nsklaus_ has joined #asahi-dev
19:53nsklaus has quit [Ping timeout: 480 seconds]
20:58jbowen has quit [Quit: leaving]
22:07aleasto has quit [Quit: Konversation terminated!]
23:11yuyichao_ has quit [Ping timeout: 480 seconds]
23:14bps has joined #asahi-dev
23:15chadmed has quit [Ping timeout: 480 seconds]
23:49yuyichao_ has joined #asahi-dev
…