Comment by dmix
15 hours ago
> Instead of continuing with the code, I spawned a fresh Pi session, and asked the agent to write a detailed specification of how the brcmfmac driver works
Planning markdown files are critical for any large LLM task.
15 hours ago
> Instead of continuing with the code, I spawned a fresh Pi session, and asked the agent to write a detailed specification of how the brcmfmac driver works
Planning markdown files are critical for any large LLM task.
The line between AI-assisted clean-room reverse-engineeing and open-source-license-laundering is a thin one, and I think the one described in the article crosses over to laundering. In classic clean-room design, one team documents the interfaces - not the code.
In this case though, the new driver has the same license as the project it was based on and explicitly credits the original project
This surprised me - but sure enough, they're right. The linux brcmfmac driver is ISC licensed:
https://github.com/torvalds/linux/blob/master/drivers/net/wi...
// SPDX-License-Identifier: ISC
It heavily depends on what you mean by "not the code", if all the code does is implement the necessary steps for the interface, then it's part of the interface. It's an interpretation of an interpretation of a datasheet.
i mean clean room was always license laundering and an AI agent cannot hold any copyright and it is largely not the same code