mripard has quit [Remote host closed the connection]
mripard has joined #linux-msm
marvin24 has joined #linux-msm
marvin24_ has quit [Ping timeout: 480 seconds]
Caterpillar has joined #linux-msm
pespin has quit []
<phh>
where do signed firmwares go to? dts mention qcom/msm8996/oneplus3t/mba.mbn, but I don't see it in linux-firmware
<konradybcio>
the license doesn't allow us to redistribute, so the only legal path is to add a script that moves them from /vendor to the desired location
<konradybcio>
some people do upload the binaries somewhere though, you'll likely find it somewhere in gitlab/postmarketos/pmaports/device/*/firmware-vendor-device
<phh>
ok, thanks. If I have to happen to have the rights to publish some signed firmwares, then linux-firmware will be ok with it? I'm asking since that would be a lot of copy/paste-d firmwares just for changing the firmware
<konradybcio>
if you have an ack from the author of these files, which are usually made by qualcomm and modified by vendors, yes
<konradybcio>
otherwise, it's between you and their legal team, as nobody can really assess whether you do in fact have such rights
<phh>
yeah license is definitely an issue I'll look into, I was first worried about linux-firmware not wanting a huge inflation in size. Thanks
<konradybcio>
linux-firmware was made to be fat :)
<phh>
on non-mainline I do Android Generic System Images, so I see hundreds of models, surely linux-firmware would look different if all those devices in linux-firmware -_-'. but ok thanks