2021-10-05
00:06booffo[m] has joined #asahi
00:07dgc[m] has joined #asahi
00:24EdwardAnd[m] has joined #asahi
00:56JuniorJPDJ has joined #asahi
01:08yuyichao has joined #asahi
01:14dpatterbee[m] has joined #asahi
01:14jevinskie[m] has joined #asahi
01:14alexanderwillner[m] has joined #asahi
01:16Nspace has quit [Quit: Nspace]
01:19M31j[m] has joined #asahi
01:26cavoirom[m] has joined #asahi
01:55tylo1 has quit [Remote host closed the connection]
01:55tylo1 has joined #asahi
02:02LeviLynch[m] has joined #asahi
02:03angustrau[m] has joined #asahi
02:04wollymilkcap[m] has joined #asahi
02:06AnushervonTabarov[m] has joined #asahi
02:24M32thSystem[m] has joined #asahi
02:26ilovetrains[m] has joined #asahi
02:27camr0[m] has joined #asahi
02:30peerp[m] has joined #asahi
02:33PhilippvK has joined #asahi
02:36phiologe has quit [Ping timeout: 480 seconds]
02:44Spectrejan[m] has joined #asahi
02:45alyssamaz: I'm still trying to understand how the kernel merge windows work ... when do we expect pci/apple to be merged into linux-next?
02:46alyssaI see linux-next is updated continuously outside the mainline merge window but I'm not sure if there's more to it
02:46alyssa(Is there another hop between "subsystem maintainer merges into a feature branch" and "subsystem maintainer sends it to linux-next"?)
02:47alyssa(At any rate, I rebased on top of pci/apple and everything still works, including the half-baked wifi)
02:50Aaron[m]1 has joined #asahi
02:57PedroArajo[m] has joined #asahi
03:00AndrewLee[m] has joined #asahi
03:21kdrag0n[m] has joined #asahi
03:28thebrinkoftomorrow[m] has joined #asahi
03:35marvin24_ has joined #asahi
03:38marvin24 has quit [Ping timeout: 480 seconds]
03:55kov has quit [Quit: Coyote finally caught me]
03:56kov has joined #asahi
04:02ghantaz[m] has joined #asahi
04:05bastilian[m] has joined #asahi
04:26cgv[m] has joined #asahi
04:30sandornagy[m] has joined #asahi
04:34YichaoYu[m] has joined #asahi
04:37ll3macorn[m] has joined #asahi
04:40Caedus[m] has joined #asahi
04:43SocioProphet[m] has joined #asahi
04:43darkapex has quit [Remote host closed the connection]
04:43darkapex has joined #asahi
04:45Guest1819 is now known as go4godvin
04:45i509vcb[m] has joined #asahi
04:48muscularduckling[m] has joined #asahi
04:59jthom[m] has joined #asahi
05:01facez[m] has joined #asahi
05:07MagMell[m] has joined #asahi
05:09hablerentand[m] has joined #asahi
05:34vasilymilovidov[m] has joined #asahi
05:38happy-dude[m] has joined #asahi
05:42ah-[m] has joined #asahi
05:46shaman_br[m] has joined #asahi
05:51anfernee[m] has joined #asahi
05:52darkapex1 has joined #asahi
05:54darkapex2 has joined #asahi
05:55TypoKign[m] has joined #asahi
05:59darkapex has quit [Ping timeout: 480 seconds]
06:00darkapex1 has quit [Ping timeout: 480 seconds]
06:04PieroDel[m] has joined #asahi
06:04idf00[m] has joined #asahi
06:05TheJollyRoger has joined #asahi
06:17_alice has joined #asahi
07:18tylo1 has quit [Ping timeout: 480 seconds]
07:20Techcable has quit [Quit: ZNC - https://znc.in]
07:21tylo1 has joined #asahi
07:21Techcable has joined #asahi
07:23sveni've seen many of them have different feature branches and then they just merge them for their next branch
07:26arndI think most maintainers have a 'fixes' branch and a 'for-next' branch, whatever they are named
07:27arndboth are merged into linux-next, but the fixes is for the current release, and may occasionally get merged into the for-next branch, which is sent in the following merge window
07:28arndfor the soc tree, we have around five branches that are updated with individual pull requests and then merged into the for-next branch, but then the separate branches are what we send in the merge window
07:29tylo1 has quit [Ping timeout: 480 seconds]
08:03Nspace has joined #asahi
08:04arndmaz: ideally that should go through marcan's tree, but if he has no other changes, I can take it from you with his ack
08:07arndmarcan: the way this should normally work is that you have a tree to collect all M1 specific changes that don't go through a driver subsystem tree. This tree should be part of linux-next, and then you send a pull request to soc@kernel.org for me or ojn to pick it up into the soc tree
08:08arndmost of the changes in that tree would be for arch/arm64/boot/dts, but occasionally there could be something else, like Kconfig, defconfig, or MAINTAINERS updates
08:08marcanalso, we don't exactly have a mailing list for reviews; how are changes by the tree maintainer themselves normally reviewed?
08:09marcanI'm fine with the github flow but I imagine that clashes with what other kernel maintainers expect
08:09arndif you only have a couple of changes for a given merge window, you can also just send individual patches instead of pull requests, the main purpose of the PR is to have a nicer git history with a merge commit that gets your tag description with an overview of the contents
08:10arndmarcan: for dts changes, I expect the review to happen during the review for the corresponding subsystem driver, and/or on the devicetree mailing list, cc linux-arm-kernel and anyone you want to participate in the review
08:11marcanmakes sense too, since my tree would mostly only handle changes that are associated with some driver
08:12marcanthough we probably will have random dts changes not associated with any driver at various points
08:13arndright, so if you add an apple-m2.dtsi file that is not just adding support for another driver, that would probably need separate review, and you should loop in reviewers for that directly.
08:13marcansend the patches out, make changes, then once it's all good just push directly to my tree
08:14marcan(as opposed to another maintainer grabbing patches from the ML and applying them to a different tree)
08:14arndwhen I get a pull request at soc@kernel.org, I usually take a quick look at all the contents to make sure nobody screwed up, but I expect the contents to have been reviewed at that point
08:15marcanthough e.g. for a silly MAINTAINERS change the review would probably only involve the ML and whoever is in that entry
08:16marcanmaz: I'll pick your patches up as soon as I have the progress report out and the other things sent out for review
08:16arndbtw, if you update the email addresses in that file (new reviewer, change of employer etc), please send that directly as a bugfix for the current release so it has the correct information at the time of release, don't wait for the merge window with those
08:17mazmarcan: there's no hurry. it's not like that's the only thing missing in the grand scheme of things!
08:18marcanmaz: fair, but I do need to get into the kernel review/maintainer flow so best not leave it for too late ;)
08:19arndalso, regarding the timing: try to get an initial pull request out to soc@kernel.org early (i.e. before rc4 or rc5) if you have a lot of contents, you can always follow up with fixes or later contents when you have more stuff to add, I just don't want to get a large pull request shortly before the merge window as I'm trying to wrap stuff up for the pull requests I send to torvalds
08:20arndmarcan: yes, same thing there: send bug fixes as soon as you can, batching things up over one or two weeks at most
08:21Glanzmannmarcan: 10:16 < arnd> btw, if you update the email addresses in that file (new reviewer, change of employer etc), please send that directly as a bugfix for the current release so it has the correct information at the time of release, don't wait for the merge window with those
08:22Glanzmannmarcan: You have all day. 10:21 < arnd> I'm a bit behind this release but I plan to pull in all remaining fixes today
08:22arndmost maintainers send pull requests even if it's just one or two bugfixes, but feel free to send the fixes as individual patches if there are only a couple and it's a hassle to set up a git tree for it
08:24arndmarcan: dt patches can be important fixes, this is generally your call to make to weigh the importance of the fix against possible regression risks. Generally I would prefer platform maintainers to categorize more patches as fixes for the current release though
08:25marcansince we're just going to be using some recent release for the m1n1 install, which will be kernel-agnostic
08:26arndAdding a "Cc: stable@vger.kernel.org" tag for stable backports usually makes sense if the current code is definitely wrong and the fix you do would also address the same problem on stable kernels.
08:27arndand in general I would assume that anything you want fixed in the current release cycle should also be fixed in stable trees, and vice versa
08:28arndgregkh often complains about patches marked as cc:stable but not sent as fixes for the current release, so he has to do a ton of backports to the just-released kernel after -rc1 comes out with all those fixes in it
08:29arndhis process for stable kernels is otherwise very automated, so you don't need to worry about creating extra work due to the cc:stable tag
08:29marcan(I've sent a lot of random things marked cc:stable but where they send it is up to them, right?)
08:30arndyes, the cc:stable tag is mostly there to inform gregkh and that the patches are known to apply to older kernels as well
08:31arndSasha also has a set of scripts and AI logic to find patches that have no cc:stable tag but look like they should be backported
08:32Nspace has quit [Quit: Nspace]
08:33arndIt's better to be explicit here. cc:stable is obvious, and you can add the minimum kernel version it applies to (sometimes backporting a fix to an older kernel causes the opposite regression), and if you think a patch looks like a fix but should not be backported, just add a sentence in the description to explain why not
08:35Nspace has joined #asahi
08:36arndregardless of where it goes, you should ask mricon to set up a lore.kernel.org mirror after that, it's super useful as a reference
08:37arndand if you want to pick up patches from that list, you can use 'b4' to interact with it, and it will even add links to the archive in the commit message
08:39arndhttps://youtu.be/mF10hgVIx9o?t=811 is mricon's recent plumbersconf presentation about the latest features and plans
09:03Nspace has quit [Quit: Nspace]
09:23tylo1 has joined #asahi
09:31tylo1 has quit [Ping timeout: 480 seconds]
10:30tomtastic_ has quit [Quit: ZNC - https://znc.in]
10:32tomtastic has joined #asahi
10:50tomtastic has quit [Quit: ZNC - https://znc.in]
10:53tomtastic has joined #asahi
12:19darkapex2 is now known as darkapex
12:48gladiac is now known as Guest1889
12:48gladiac has joined #asahi
12:54Guest1889 has quit [Ping timeout: 480 seconds]
13:03aleasto has joined #asahi
13:26yuyichao has quit [Ping timeout: 480 seconds]
13:40gabuscus_ has joined #asahi
13:41jbowen has joined #asahi
13:44gabuscus has quit [Ping timeout: 480 seconds]
13:47yuyichao has joined #asahi
14:29radex has joined #asahi
14:45tylo1 has joined #asahi
14:47yuyichao_ has joined #asahi
14:51yuyichao has quit [Ping timeout: 480 seconds]
14:54marcanit clockgates them when the UARTs are idle (even if powered themselves; this seems to be about the CPU interface side)
15:02method_ has joined #asahi
15:05Method has quit [Ping timeout: 480 seconds]
15:23yuyichao has joined #asahi
15:27yuyichao_ has quit [Ping timeout: 480 seconds]
15:34marcanit goes from 4 (clockgated) to f (active) if I poke the registers in a loop from another CPU
16:18marcanhttps://asahilinux.org/2021/10/progress-report-september-2021/ <- anyone want to take a look before I send it out on twitter/etc?
16:28mazfunny to read this while I have powered the G5 to check something else... the Mini is a lot quieter!
16:31TheLink"This is effectively a requirement for most SoCs, because hardware tends to vary quite a bit from generation from generation ..."
16:31kettenisI don't think the powerpc macs should hit that codepath as all the pcie devices are represented in the device tree on these machines (even cards plugged into the pci slots)
16:32kettenisbut I'm also not sure the change makes sense as interrupt-map is only supposed to translate interrupts for child nodes
16:43mazI though it'd be quicker to just reinstall Debian, but the install media is missing both ethernet and sata drivers...
17:06tylo1 has quit [Ping timeout: 480 seconds]
17:08tylo1 has joined #asahi
17:17tylo1 has quit [Ping timeout: 480 seconds]
17:24tylo1 has joined #asahi
17:33alyssatext:4:23: leonard.exclamation.30ppm More than 30 ppm of exclamations. Keep them under control.
17:35alyssa(Advice for anyone writing on Linux -- run your text through proselint. It is not nearly as good as Grammarly but it still catches issues.)
17:38psykosea lot of these are really... not worth a lint at all? who minds a difference between ... and …
17:38marcanthough that won't catch transforms that the markdown parser will do for you, like the ... thing
17:40psykoseif anything i prefer the opposite style of all these suggestions, and not because i'm a weird contrarian
17:41alyssaif the adjective/verb you chose is not emphatic enough without the "very", you need a stronger adjective/verb.
17:41marcanalso, it's 2:40AM here and I'm getting solidly into "I couldn't care less, I'm gonna git send on all the announcements" territory :p
17:46frode_0xahey all, just wanted to say that I'm really impressed with the progress you'll made already!
17:56aleasto has quit [Ping timeout: 480 seconds]
17:56aleasto has joined #asahi
18:04MatrixTravelerbot[m] has joined #asahi
18:05nsklausmacbookpro don't have ethernet, unless we use an usb dongle.. and no sound is a bit too sad
18:06nsklausj_ey: i don't think i have one, all i have are bt headset, that may be plugged in usb-c but i think it's just for power delivery
18:06marcanjust needs a big cleanup/rewrite round plus installer scaffolding to put the firmware somewhere useful, and userspace scaffolding to copy/link it to /lib/firmware
18:07j_eynsklaus: sure, just saying that with buying a dongle or other headset, there's a workaround for now!
18:08nsklausmarcan: i'm patient, i can wait more for the dust to settle a bit, and since thing project is moving along quite fast, hopefully it won't be too long for these missing bits materialize in a first public beta
18:09yuyichao_ has joined #asahi
18:09marcanand yeah, the wifi thing is just on the list of things to clean up for the public release... the bigger question is should I jump into GPU first or do a bit of that :p
18:10nsklausnetworking should be first imho, we can survive by using a fast framebuffer, but not without network
18:11marcanit's more like do I spend some time on GPU first or prioritize the "end user testable" thing
18:11chile09[m] has joined #asahi
18:12marcanI guess I should send out cpufreq+mcc for review, work out my DT tree, then at least start poking at GPU while the other kernel drivers go through review
18:12yuyichao has quit [Ping timeout: 480 seconds]
18:13nsklausthat's not to say i'm not eager to see gpu being worked upon, it's of course a very important part and i'm following the progresses made on that front too, but networking ..without networking i cannot do anything
18:14Glanzmannmarcan: GPU, or you use the m1 as your only machine and the rest will sort itself out. :-)
18:20nsklausit's good such project exist to bring vulkan on macos despite apple refusing to make it happen and third party devs having to do it, but it has many limitations and not progressing that fast.. so opengl is outdated, vulkan support is sub-standard and the whole situation is a bit sad
18:24GlanzmannBtw, has someone tried the current state of m1 linux on battery? How it is holding up, I really have to try.
18:34nsklauson x86, running powertop as root, tunning all tables to 'good', unplugging the power cable, it shows the overall power consumption in watts and is accurate, at least on x86. on M1 and asahi current state, i can't say though.
18:37nsklausi can have it run around 6 watts, but that mean i disabled a much stuff as i could, like blutooth and all, and capping cpu frequency to lowest etc ..
21:19tylo1 has quit [Ping timeout: 480 seconds]
21:22tylo1 has joined #asahi
21:30tylo1 has quit [Ping timeout: 480 seconds]
21:43tylo1 has joined #asahi
22:10vulpun has joined #asahi
22:13vulpun has quit []
22:23Nspace has joined #asahi
22:31Nspace has quit [Quit: Nspace]
22:39aleasto has quit [Quit: Konversation terminated!]
22:45doggkruse has joined #asahi
23:00doggkruse has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
23:07yuyichao has joined #asahi
23:10chile09[m]are there a lot of binary blobs on this platform?
23:11yuyichao_ has quit [Ping timeout: 480 seconds]
23:11chile09[m]what parts of the system use binary blobs
23:18yuyichao_ has joined #asahi
23:21yuyichao has quit [Ping timeout: 480 seconds]
23:32yuyichao_ has quit [Ping timeout: 480 seconds]
23:56doggkruse has joined #asahi