#asahi-dev · 2025-09-14 14:33
svenjust use b4 to add the commits, then merge branch into asahi-soc/for-next or however that’s called #asahi-dev · 2025-09-14 14:31
svenbut sending PRs from github is also fine. also happy if you want to do that as well, I just figured i'd take care of upstream while you take care of the downstream kernel :-)#asahi-dev · 2025-09-14 14:30
sveni just send the PRs from kernel.org, if you also get an account there we could also move the primary repo to kernel.org#asahi-dev · 2025-09-14 14:30
svensure#asahi-dev · 2025-09-14 14:29
jannauI can do the commits if the asahi github is still the primary repo#asahi-dev · 2025-09-14 14:28
jannauI'll send a v2 for the dt changes and driver changes without ack separately#asahi-dev · 2025-09-14 14:28
svenat least the driver changes probably needs ack though i guess?#asahi-dev · 2025-09-14 14:28
svensure, works for me#asahi-dev · 2025-09-14 14:27
jannausven: what shall we do about the t6020 series? I would propose to take every acked dt-bindings and driver change that hasn't been taken up elsewhere in apple-soc/drivers-6.18#asahi-dev · 2025-09-14 14:22
svenhuh, looks like it's already been merged into usb-testing#asahi-dev · 2025-09-14 13:27
svennext up dwc3 once that's been reviewed and then finally atcphy#asahi-dev · 2025-09-14 13:27
svenhttps://lore.kernel.org/asahi/20250914-apple-usb3-tipd-v1-0-4e99c8649024@kernel.org/ tipd changes#asahi-dev · 2025-09-14 12:38
svenjust different tunable names, but we're already changing those and merging some of them inside m1n1 anyway#asahi-dev · 2025-09-14 12:38
svenyeah, m3 looks similar enough i think#asahi-dev · 2025-09-14 12:32
jannaum4 pro might be differentr due to tb5 but I guess that would justify dt-binding as well#asahi-dev · 2025-09-14 12:31
fl0_idsven sure. just in general I mean :)#asahi-dev · 2025-09-14 12:30
svenshould be fine, jannau's dump is enough#asahi-dev · 2025-09-14 12:29
fl0_idusually I like to use pastery, but was also having issues#asahi-dev · 2025-09-14 12:28
fl0_idbut ok. if you need more let me know #asahi-dev · 2025-09-14 12:28
fl0_idsven weird#asahi-dev · 2025-09-14 12:27
svenbut that can be handled inside m1n1 anyway#asahi-dev · 2025-09-14 12:27
svenalright.. so they at least re-named some tunables it seems#asahi-dev · 2025-09-14 12:27
svenbut jannau's dump should be fine#asahi-dev · 2025-09-14 12:27
sven"This page is no longer available. It has either expired, been removed by its creator, or removed by one of the Pastebin staff."#asahi-dev · 2025-09-14 12:26
fl0_idoops too late#asahi-dev · 2025-09-14 12:26
fl0_idsven https://pastebin.com/uc6tbrbT#asahi-dev · 2025-09-14 12:26
sventhanks!#asahi-dev · 2025-09-14 12:26
jannausven: https://paste.debian.net/1396568/#asahi-dev · 2025-09-14 12:20
svenjust one node is enough, just want to see if anything significant changed#asahi-dev · 2025-09-14 12:20
svenyeah#asahi-dev · 2025-09-14 12:20
fl0_idsven I can offer m3 max, or copy the atcphy for you. you mean the adt from macos right?#asahi-dev · 2025-09-14 12:16
svensomething extracted from the ipsw should be enough fwiw#asahi-dev · 2025-09-14 12:16
sven(same warning as usual: if you upload the entire adt taken from your device it will contain stuff like wifi or bt keys)#asahi-dev · 2025-09-14 12:15
svenanyone got some M3 or M4 adts for me? only interested in the atcphy nodes#asahi-dev · 2025-09-14 11:18
svenmaybe this entire mess is actually stable now with the glue approach#asahi-dev · 2025-09-14 11:18
sventhis is.. suspicious. i just worked in janne's comments into the tipd driver and I didn't break usb3 on the first try#asahi-dev · 2025-09-13 14:32
chadmedokay we'll keep the shell script around then#asahi-dev · 2025-09-13 14:31
chadmed:D #asahi-dev · 2025-09-13 14:31
jannauI'm going to forget that the build needs to be tested before a tag can be pushed#asahi-dev · 2025-09-13 14:29
chadmedor even just update /dev#asahi-dev · 2025-09-13 14:29
chadmedthen when we push a tag on that commit that updates the links etc#asahi-dev · 2025-09-13 14:29
chadmedyeah but we can test the artefact built on the commit manually#asahi-dev · 2025-09-13 14:28
jannaustill needs to be manually tested#asahi-dev · 2025-09-13 14:27
chadmedyeah, i was thinking to automate the updating of the links on tag/release push anyway, not on every commit#asahi-dev · 2025-09-13 14:24
jannauI was mostly concerned about the one in the main installer which should be updated manually anyway#asahi-dev · 2025-09-13 14:22
chadmedbut rigging up the pipeline to actually build it is trivial #asahi-dev · 2025-09-13 14:21
chadmedjannau: lgtm. the installer package will need an extra step to push it to bunny and update the 'latest' pointer#asahi-dev · 2025-09-13 13:36
jannauchadmed: https://github.com/AsahiLinux/m1n1/pull/495 builds the boot.bin for uefi-only, creating a full installer package shouldn't be much more effort#asahi-dev · 2025-09-13 12:26
truitafl0_id: hmm that's fair. as i won't have my desktop until next week i'll do some osdev in the meantime and then i'll try to get m1n1#asahi-dev · 2025-09-13 12:23
fl0_idtruita that's fine, I'm only working on this off an on (more off). I'm not mainly an embedded developer, so I'm not sure I can give good advice on how to learn. For just getting m1n1 updated, I don't think writing a whole OS is necessary. Ofc it's necessary to have at least some systems/embedded understanding, which I cannot judge. For learning that, may get an arm sbc and write an OS for that. (but I never did that and don't have the time for it)