Re: [RFC] Counter-Proposal -- Interpretation of DFSG on Artificial Intelligence (AI) Models

Simon Josefsson <[email protected]>
Newsgroups gmane.linux.debian.devel.vote
Message-ID <[email protected]>
Thorsten Glaser <[email protected]> writes:

> On Thu, 8 May 2025, Simon Josefsson wrote:
>
>>I don't think it is possible to separate firmware into things that are
>>just for enabling of hardware compared to what is running on the main
>>CPU.  Consider a non-free firmware blob for a future SoC CPU that
>>includes camera functionality, it seems possible that would make use of
>>some LLM model to have better face recognition for example.  Without
>>disassembly (which may be illegal) we can't really know if this is part
>>of the blob or not.
>
> I wanted to express that: if the LLM is part of the firmware uploaded
> to the SoC for camera functionality, then it is packaged as firmware
> as a whole and only accessed through normal camera functions when the
> user accesses the camers. It’s not packaged separately (just the model)
> or available to other software on the system (removed from the camera
> functionality).

Okay, I see what you are trying to get at, but I'm not certain things
can be separated that easily.  Can the camera software in the above
scenario be in main, or is it tainted indirectly by the non-free
firmware?  Does it make a difference if the camera software would only
support one proprietary camera that happens to require the
non-free-firmware blob?  I think this situation is comparable to what we
already have today: non-free-firmware blobs enable certain CPU behaviour
that packages in 'main' depends on for functionality.

> But I agree that to make this distinction probably isn’t worth extra
> headache (also my headache’s growing again…) so if nobody has got an
> idea of how to express this well, I’d say let’s just remove all
> mentions of non-free-firmware from the proposal, it can go with its
> usual rules.

Yes, I can't seem to find any policy matters that affect only the
intersection of non-free-firmware and AI models.  It may indeed be
simpler to treat non-free-firmware as part of the !main context.

/Simon
signature.asc (application/pgp-signature, 1.2 KB)
-----BEGIN PGP SIGNATURE-----

iQNoBAEWCAMQFiEEo8ychwudMQq61M8vUXIrCP5HRaIFAmgcbLUUHHNpbW9uQGpv
c2Vmc3Nvbi5vcmfCHCYAmDMEXJLOtBYJKwYBBAHaRw8BAQdACIcrZIvhrxDBkK9f
V+QlTmXxo2naObDuGtw58YaxlOu0JVNpbW9uIEpvc2Vmc3NvbiA8c2ltb25Aam9z
ZWZzc29uLm9yZz6IlgQTFggAPgIbAwULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgBYh
BLHSvRN1vst4TPT4xNc89jjFPAa+BQJn0XQkBQkNZGbwAAoJENc89jjFPAa+BtIA
/iR73CfBurG9y8pASh3cbGOMHpDZfMAtosu6jbpO69GHAP4p7l57d+iVty2VQMsx
+3TCSAvZkpr4P/FuTzZ8JZe8BrgzBFySz4EWCSsGAQQB2kcPAQEHQOxTCIOaeXAx
I2hIX4HK9bQTpNVei708oNr1Klm8qCGKiPUEGBYIACYCGwIWIQSx0r0Tdb7LeEz0
+MTXPPY4xTwGvgUCZ9F0SgUJDWRmSQCBdiAEGRYIAB0WIQSjzJyHC50xCrrUzy9R
cisI/kdFogUCXJLPgQAKCRBRcisI/kdFoqdMAQCgH45aseZgIrwKOvUOA9QfsmeE
8GZHYNuFHmM9FEQS6AD6A4x5aYvoY6lo98pgtw2HPDhmcCXFItjXCrV4A0GmJA4J
ENc89jjFPAa+wUUBAO64fbZek6FPlRK0DrlWsrjCXuLi6PUxyzCAY6lG2nhUAQC6
qobB9mkZlZ0qihy1x4JRtflqFcqqT9n7iUZkCDIiDbg4BFySz2oSCisGAQQBl1UB
BQEBB0AxlRumDW6nZY7A+VCfek9VpEx6PJmdJyYPt3lNHMd6HAMBCAeIfgQYFggA
JgIbDBYhBLHSvRN1vst4TPT4xNc89jjFPAa+BQJn0XTSBQkNZGboAAoJENc89jjF
PAa+0M0BAPPRq73kLnHYNDMniVBOzUdi2XeF32idjEWWfjvyIJUOAP4wZ+ALxIeh
is3Uw2BzGZE6ttXQ2Q+DeCJO3TPpIqaXDAAKCRBRcisI/kdFokgxAQCvS6yCcb3N
dd/ddjkMut/77j4tJ7dOSVzgRBUUBr8zigEAu8nJcG9KXDPtp0IMhWGj052u071E
YTpjDUUM+jteGAc=
=fz1g
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.