#asahi-dev · 2026-06-30 09:04
chaos_princessbsds can copy it then#asahi-dev · 2026-06-30 09:04
chadmeddual licence allows the bsds to look at the driver and copy parts of it for their own use#asahi-dev · 2026-06-30 09:04
jannauit can't be -or-MIT when it is based on the GPL only driver. specific parts which are not based on GPL source could be -or-MIT#asahi-dev · 2026-06-30 09:04
sofuschadmed: any reason to use -or-MIT? I dont know a lot about licensing#asahi-dev · 2026-06-30 09:03
StanfordAppliedCyber[m]gracias chaos princess#asahi-dev · 2026-06-30 09:03
StanfordAppliedCyber[m]oh that does look useful#asahi-dev · 2026-06-30 09:02
chadmedbut it cannot _not_ be gpl #asahi-dev · 2026-06-30 09:02
chadmeddriver also must be gpl and optionally -or-MIT#asahi-dev · 2026-06-30 09:01
chaos_princessdriver you use gpl#asahi-dev · 2026-06-30 09:01
chadmedif so yes, you will need to add Copyright (c) xxxx Rockchip or whatever#asahi-dev · 2026-06-30 09:01
sofusdriver#asahi-dev · 2026-06-30 09:01
chaos_princessdriver or fw#asahi-dev · 2026-06-30 09:01
sofusyes#asahi-dev · 2026-06-30 09:01
chadmedwhen you say "based on" do you mean "copied" #asahi-dev · 2026-06-30 09:01
sofusmuch of the avd driver code is based on rockchip's driver that has an GPL-2.0 license, does that change anything?#asahi-dev · 2026-06-30 08:59
chaos_princessStanfordAppliedCyber[m]: may or may not be useful https://gist.github.com/hoshinolina/1a70f1f26b9cd3c52d61d2b8e8b27673#asahi-dev · 2026-06-30 08:58
StanfordAppliedCyber[m]and the clipboard is messed up#asahi-dev · 2026-06-30 08:58
chadmedso pick whichever licence you actually want to use, and take my S-o-b for my commits #asahi-dev · 2026-06-30 08:58
StanfordAppliedCyber[m]i'd copy paste to you the errors but i'm actually working over an RDP session#asahi-dev · 2026-06-30 08:58
chaos_princessmost of our stuff is mit#asahi-dev · 2026-06-30 08:58
chadmedi only said that for the benefit of the bsds but then i realised they dont need to actually incorporate the code at all and can just take the blobs because its firmware#asahi-dev · 2026-06-30 08:57
StanfordAppliedCyber[m]one is some UNEXP_RT_ something#asahi-dev · 2026-06-30 08:57
chaos_princessmit/apache/gpl/bsd, your choice#asahi-dev · 2026-06-30 08:57
sofusmit was prefered right?#asahi-dev · 2026-06-30 08:57
StanfordAppliedCyber[m]like, one is some dart disp0 thin#asahi-dev · 2026-06-30 08:57
chaos_princessthat assumes you do mit or apache#asahi-dev · 2026-06-30 08:57
chadmedsofus: yea pretty much. probably also add a LICENCE file to the fw repo#asahi-dev · 2026-06-30 08:57
chaos_princesssofus: spdx headers + LICENSE file in root#asahi-dev · 2026-06-30 08:56
StanfordAppliedCyber[m]like i have three issues all around memory mappings#asahi-dev · 2026-06-30 08:56
chaos_princessspecifically, agx and dcp are usually the things that die from that#asahi-dev · 2026-06-30 08:56
StanfordAppliedCyber[m]the agx issue is a memory cashing thing#asahi-dev · 2026-06-30 08:56
sofuschadmed: i should add the SPDX-License-Identifier header to all source files in both my avd driver and fw right?#asahi-dev · 2026-06-30 08:56
StanfordAppliedCyber[m]i can literally get a trace#asahi-dev · 2026-06-30 08:56
StanfordAppliedCyber[m]dcp works#asahi-dev · 2026-06-30 08:56
StanfordAppliedCyber[m]but i'm very, very late into boot#asahi-dev · 2026-06-30 08:56
chaos_princessiboot loads agx firmware, since you are confused whether this is a 26.5 or a 26.6, it could be loading the wrong one#asahi-dev · 2026-06-30 08:56
StanfordAppliedCyber[m]i'm admittedly very confused what's happenning because iboot thinks that this is a 26.5 install#asahi-dev · 2026-06-30 08:55
StanfordAppliedCyber[m]wdym?#asahi-dev · 2026-06-30 08:54
chaos_princessdcp and agx will say no#asahi-dev · 2026-06-30 08:54
chaos_princessare you by any chance trying to boot mismatched firmware#asahi-dev · 2026-06-30 08:54
StanfordAppliedCyber[m]i'm not looking forward to upstreaming this hypervisor#asahi-dev · 2026-06-30 08:54
StanfordAppliedCyber[m]the windowserver progress bar is 50% full crashing on some agx thingy#asahi-dev · 2026-06-30 08:53
StanfordAppliedCyber[m]i still need to create a new volume, but that can wait#asahi-dev · 2026-06-30 08:53
StanfordAppliedCyber[m]i managed to get past the sep regression usig some mega cursed adt hacks#asahi-dev · 2026-06-30 08:50
chadmedthat would be a nice goal eventually but i dont think its realistic until it is some semblance of complete with the release cadence of linux-firmware#asahi-dev · 2026-06-30 08:49
chaos_princesswe are getting it into linux-firmware, right?#asahi-dev · 2026-06-30 08:48
chadmedalso please actually assign copyright and such to the firmware, we cant really ship it until you do#asahi-dev · 2026-06-30 08:47
chadmedfor the driver itself one commit is typically acceptable for a new driver but making it atomic at the "add hevc support" level or support for various soc quirks might also make sense #asahi-dev · 2026-06-30 08:47
chadmedimportant thing to make everyones lives easier: make sure your dt binding is its own commit, your dts changes are their own commits for each soc (or soc series)#asahi-dev · 2026-06-30 08:45
chaos_princessyou can look at past prs to see what needs splitting out