#
…

2021-02-14

00:01TheJollyRoger has quit [Read error: Connection reset by peer]
00:01DarthCloud has quit [Remote host closed the connection]
00:04TheJollyRoger has joined #asahi
00:05DarthCloud has joined #asahi
00:16choozy has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
00:20amw has joined #asahi
00:24amw has quit [Ping timeout: 240 seconds]
00:58amw has joined #asahi
01:03amw has quit [Ping timeout: 272 seconds]
01:19amw has joined #asahi
01:25thestr4ng3r has quit [Read error: Connection reset by peer]
01:26thestr4ng3r has joined #asahi
01:39thestr4ng3r has quit [Read error: Connection reset by peer]
01:39thestr4ng3r has joined #asahi
02:01hypergenesis[m]7.1 quake in Japan, hope marcan is okay
02:01opticronhe was posting about it on twitter earlier, seems to be fine
03:00el1x has joined #asahi
03:06ys0seri0us has joined #asahi
03:15phiologe has quit [Ping timeout: 264 seconds]
03:15phiologe has joined #asahi
03:17brosenz[m] has joined #asahi
03:46ys0seri0us has quit [Ping timeout: 240 seconds]
03:50ransom has joined #asahi
04:00_whitelogger has joined #asahi
04:30cshbicos has joined #asahi
04:43cshbicos has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
04:49ransom has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
04:56marvin24 has quit [Ping timeout: 260 seconds]
04:57marvin24 has joined #asahi
05:12_whitelogger has joined #asahi
06:43ransom has joined #asahi
07:30ransom_ has joined #asahi
07:31ransom has quit [Ping timeout: 240 seconds]
07:57_whitelogger has joined #asahi
08:07ransom_ has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
08:12maor26 has joined #asahi
08:17marcanyeah, all good here, thanks for checking :)
08:36amw has quit [Ping timeout: 256 seconds]
08:37Tokamak has quit [Ping timeout: 240 seconds]
08:40hir0 has joined #asahi
08:44Tokamak has joined #asahi
08:51amw has joined #asahi
09:00TellowKrinkle[m] has quit [Quit: Idle for 30+ days]
09:13raster has joined #asahi
09:25amw has quit [Ping timeout: 240 seconds]
09:30Tokamak has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
09:33hir0 has quit [Quit: hir0]
09:53mps has quit [Ping timeout: 256 seconds]
10:05mps has joined #asahi
10:09VinDuv has joined #asahi
10:16maor26 has quit [Remote host closed the connection]
10:17amw has joined #asahi
10:17maor26 has joined #asahi
10:37leah2 has quit [Ping timeout: 272 seconds]
10:49leah2 has joined #asahi
11:14marcanrobher: I'm not sure where the [non]posted-mmio property should be documented in the DT bindings. the simple-bus definition is part of the spec, not the bindings in the kernel tree... the property is really part of the common address resolution code
11:34amw has quit [Ping timeout: 256 seconds]
12:00vimal has quit [Ping timeout: 240 seconds]
12:42DarthCloud has quit [Remote host closed the connection]
12:42DarthCloud has joined #asahi
12:44kettenismaybe a separate file in bindings/bus/ is the way to go?
12:44kettenisthe idea is that it is a proprty of the bus isn't it? not of the devices themselves
12:51arndmarcan, robher: if we assume the new property could show up in any node, it makes sense to document it there, OTOH it's likely that no other platform will need it any time soon
12:52raster has quit [Quit: Gettin' stinky!]
12:53marcankettenis, arnd: yeah, it's a property of the bus, though potentially any bus
12:54marcanI need to check that I didn't miss any review comments, but this should be pretty close to v2: https://github.com/AsahiLinux/linux/tree/upstream-bringup-v2 (cc maz too)
12:57marcanrunning the dt bindings check now and going to grab some dinner :) I'll probably send it a bit later today and defer the nonposted-mmio binding for v3
13:02grumble has quit [Quit: ACCORDING TO ALL KNOWN LAWS OF AVIATION THERE IS NO WAY A BEE SHOULD BE ABLE TO FLY ITS WINGS ARE TOO SMALL TO GET ITS FAT LITTLE BODY OFF THE GROUND THE BEE OF COURSE FLIES ANYWAY BECAUSE BEES DON'T CARE WHAT HUMANS THINK IS IMPOSSIBLE]
13:07Tokamak has joined #asahi
13:10grumble has joined #asahi
13:15Tokamak has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
13:16inglor has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
13:17inglor has joined #asahi
13:31VinDuv has quit [Quit: Leaving.]
13:41Tokamak has joined #asahi
13:48Tokamak has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
13:52jeffb has joined #asahi
14:29Necrosporus has quit [Read error: Connection reset by peer]
14:30Necrosporus has joined #asahi
14:36riker77 has quit [Ping timeout: 264 seconds]
14:57plainbits has joined #asahi
15:02riker77 has joined #asahi
15:10plainbits has quit [Ping timeout: 264 seconds]
15:12arndmarcan: just to clarify the timeline: I expect linux-5.11 to be released later today, which means it's too late for 5.12 now. I won't queue anything up until v5.12-rc1 is out, but I'm happy to take anything that has been reviewed at that point into soc.git for v5.13, which means it can be part of linux-next two to three weeks from now
15:12marcanyup, no problem; I wasn't really expecting to make 5.12
15:13arndthere are generally two options for merging a new platform: either everything goes into the soc tree, with an ack from the other subsystem maintainers, or everything goes into separate trees, and only the dts+Kconfig+MAINTAINERS file updates go through soc.git
15:13plainbits has joined #asahi
15:14arndafter the initial merge, the second method is normally used for everything
15:15marcangiven there are some dependencies involved, the first method might make more sense here? though it could be broken up into at least a few semi-independent pieces
15:17marcanthe samsung_tty stuff basically stands alone, other than the Kconfig test; but the AIC driver depends on sysreg_apple.h at least
15:19marcanI don't really expect any major dependencies after this; I think the vast majority of drivers that will go in after this point will communicate through existing kernel abstractions
15:25arndmarcan: yes, we specifically allow this for the initial merge to avoid having platform maintainers go through multiple release cycles to get everything merged in the right order
15:26arndthe main problem later on is when you have a .dts file in the kernel and intentionally break compatibility with older versions. Which is something that we try to avoid as soon as there are users anyway, but it might happen with the iommu or something unexpected
15:29marcanI need to look into how the iommu stuff works for socs... that's going to be coming up pretty soon anyway
15:33marcanhm, looks like it's mostly just referencing the iommu from peripherals
15:33marcanarnd: do you have an example of how this can end up breaking compat?
15:35arndmarcan: I think if the dtb lists an iommu, the kernel will not try to use devices until a driver for the iommu has been loaded, but older kernels would then fail because they don't have a driver for it
15:35arndit's possible that is no longer the case, it's been a while since I looked at iommus
15:36arndthere are lots of other things that could go wrong though
15:36marcanah, but that'd be for using older kernels with newer devicetrees
15:36marcanso as long as the iommu support goes in first, then the dts update in the kernel, the kernel itself would be consistent
15:37arndeven if only one way is broken, it can still be a pain for users to upgrade when they want to use a newer dtb to use new features that a later kernel enables, but after updating the dtb they can no longer go back to a known working kernel
15:37marcanyeah, of course, especially in the longer term
15:38marcanbut I don't think we can really avoid breaking compat with older kernels and newer devicetrees until all those core drivers have stabilized for a bit anyway
15:38marcanclocks/power/iommu especially
15:38marcane.g. obviously current kernels *have* to break with future devicetrees once I introduce real clock/power drivers and make the UART use those
15:39kettenisnot necessarily
15:39arndright. For the opposite case (new kernel, old dtb), there is usually an easier way to avoid breaking things, but it may require doing the update over multiple merge windows, to first change the driver and then dte dts files
15:40marcanI'm not *that* worried about that case, because once we have a solid footing I expect all the early adopters to be using my tree anyway, and as long as I keep the upstreaming pipeline flowing we won't fall behind while also not being blocked on that too much
15:41marcanfor the same reason only the initial merge has all those dependency issues
15:42marcanit's just going to require getting used to the planning :)
15:42marcanI'm going to have to come up with some kind of system
15:46marcankettenis: what are you thinking of?
15:46marcan(re: compat)
15:54kettenisif fimrware (e.g. m1n1) sets up clocks and power a kernel without proper clock/power support might still work
15:56kettenisand a uart drive could be implemented in a way such that it simply skips setting the baudrate if it can't determine the clock frequency of the clock feeding it
15:57marcanyeah, the problem is the samsung uart driver refuses to work without clocks defined
15:58marcanand, well... I'm not sure I'd call not being able to change baud rates a "working device" :-)
15:58kettenisgood enough for a serial console ;)
16:00hwatwasthat[m] has quit [Quit: Idle for 30+ days]
16:02marcanyeah but... if you're the kind of person with a serial console, you probably won't mind dt compat breakage at this stage :-)
16:28plainbits has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
16:40Necrosporus has quit [Ping timeout: 256 seconds]
16:44VinDuv has joined #asahi
16:49raster has joined #asahi
16:55marcananyway, I should get some sleep; I'll fire off v2 for review tomorrow
16:56marcanI'll split off `arm64: samsung: Add missing Kconfig dependencies` too and send that separately, that has nothing to do with this series anyway, I just happened to stumble upon it during testing
17:03arndmarcan: right, I actually had found the same Kconfig bugs independently but never got around to sending out the fixes (I had two patches instead of one, but it makes sense to combine them as you did)
17:03Tokamak has joined #asahi
17:04marcanright :)
17:04marcanalso I should fire off the DT things which we don't care about anyway but I think are clearly broken; I just need to find a PPC tester... or dig up that old G4 Mac Mini I have lying around...
17:05arndmarcan: before you send out v2, can you add a patch to 'defconfig' to enable the platform and any driver you need?
17:05marcanah yes, defconfig!
17:05marcanthanks for reminding me about tha
17:05marcanI'll do it tomorrow then *makes a note*
17:20djb has joined #asahi
17:32Necrosporus has joined #asahi
18:04davidrysk[m]so I see that never_released_ commented on SSD wear
18:05davidrysk[m]I'm looking at mine (2TB SSD) and I see 149 TBW and 3% "Percentage Used"
18:05davidrysk[m]those are... not great stats
18:06davidrysk[m]"Percentage Used" is defined to be a vendor specified estimate though
18:29KindOne has quit [Ping timeout: 272 seconds]
18:37KindOne has joined #asahi
18:43Glanzmanndavidrysk[m]: HOw to get these numbers?
18:45plainbits has joined #asahi
18:55leah2 has quit [Ping timeout: 272 seconds]
18:55davidrysk[m]Glanzmann: smartctl from smartmontools
18:55arndor "nvme smart-log /dev/nvme0n1"
18:55davidrysk[m]I meant from macOS
18:56ransom has joined #asahi
18:57ransom has quit [Client Quit]
18:57davidrysk[m]arnd: I think it's more a complaint about macOS being too swap-happy
18:57davidrysk[m]149 TBW * (100/3)% is roughly 5PBW
18:57arnddavidrysk[m]: it's also really RAM-limited
18:58arndI wonder if they used MLC flash then, most drives today use either TLC or QLC, which ends up with a much shorter life
18:59arndMy four year old Samsung 960 Pro using MLC is at 23% with 295529554 "data units written"
18:59davidrysk[m]does it say the size of a "data unit"?
19:00davidrysk[m]I have "291,819,868 [149 TB]"
19:01arndIIRC it's vendor specific, I should check the datasheet
19:01tpw_rulesdavidrysk[m]: how old is this drive?
19:02davidrysk[m]2TB in an M1 MBP that was received about 2 months ago
19:03tpw_rulesweird. my 2016 touch bar MBP has a 1TB that reports 1% used and 55.4TBW. but i'm still on 10.14
19:04tpw_rulesbut it's been my daily driver for that whole time
19:04davidrysk[m]I've been "up 4 days, 20:22" and kernel_task has written 15.68 TB in that time
19:04arndsmartctl says "Data Units Written: 295,530,779 [151 TB]"
19:05never_releasedarnd: on which machine?
19:05tpw_rulesmine has written 837GB over 47 days
19:05tpw_rulesis there a bug in the newer OSes?
19:05never_releasedhad macOS write 1.8TB in a day
19:05arndnever_released: this my threadripper workstation that has pretty much been building kernels for the past 3.5 years
19:06davidrysk[m]never_released: have you filed a feedback about this?
19:06davidrysk[m]I'm wondering if I should
19:06never_releasedThreadripper is so expensive nowadays that Epyc is a better choice
19:07davidrysk[m]never_released: what's the best way to ask you offtopic stuff (since you're not in #asahi-offtopic)?
19:07never_releasedTwitter maybe? I don't know
19:11plainbits has quit [Ping timeout: 264 seconds]
19:12davidrysk[m]so yeah -- worth filing a feedback?
19:14plainbits has joined #asahi
19:31leah2 has joined #asahi
19:33VinDuv has quit [Read error: Connection reset by peer]
19:33VinDuv has joined #asahi
19:50zkrx has quit [Ping timeout: 240 seconds]
19:54zkrx has joined #asahi
20:28plainbits has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
20:35plainbits has joined #asahi
20:36plainbits has quit [Client Quit]
20:40vup has quit [Ping timeout: 246 seconds]
20:41anuejn has quit [Ping timeout: 272 seconds]
20:48leah2 has quit [Ping timeout: 264 seconds]
20:55anuejn has joined #asahi
20:55vup has joined #asahi
21:32raster has quit [Quit: Gettin' stinky!]
21:40VinDuv has quit [Quit: Leaving.]
21:55eta has quit [Quit: we're here, we're queer, connection reset by peer]
21:56eta has joined #asahi
22:14TheJollyRoger has quit [Remote host closed the connection]
22:15TheJollyRoger has joined #asahi
22:31leah2 has joined #asahi
23:00yrlf has quit [Quit: The Lounge - https://thelounge.chat]
23:01yrlf has joined #asahi
23:02amw has joined #asahi
23:15saintdev has joined #asahi
…