From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-6.3 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id BADEEC433DB for ; Tue, 30 Mar 2021 03:17:33 +0000 (UTC) Received: by mail.kernel.org (Postfix) id 91D0460C3E; Tue, 30 Mar 2021 03:17:33 +0000 (UTC) Received: from mail-qt1-f195.google.com (mail-qt1-f195.google.com [209.85.160.195]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 490AF6195D for ; Tue, 30 Mar 2021 03:17:33 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 490AF6195D Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=schmorgal.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=doug@schmorgal.com Received: by mail-qt1-f195.google.com with SMTP id 1so10315661qtb.0 for ; Mon, 29 Mar 2021 20:17:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=schmorgal.com; s=google; h=from:to:cc:subject:message-id:date:user-agent:mime-version :content-transfer-encoding:content-language; bh=rjPExMtYs1kqjt/CTaWBz7aoN1AIX0rSeL0R8pOiRiw=; b=TItwIoirGK+SHdG+Qx6NohvyLbkhBnPOZpneXQ08I2OL3Vfr1u9Iy2ZXnZZrAQbNVg yWQ+l9p3k+Y2i2rC+h6Y7EigVKUZAt4erNo9SEInYGrVhS9wYik7zxvT+wI7XKUupSoG DIjkdM/MSfKTZiZwJiodZjIVXCUTUAH9Q+ffE= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:message-id:date:user-agent :mime-version:content-transfer-encoding:content-language; bh=rjPExMtYs1kqjt/CTaWBz7aoN1AIX0rSeL0R8pOiRiw=; b=AENcV3UNb6uFCnopHlpx+GY+yNjOZbkMe9WkX6lnmXVmg1CNQsM0j5U93ls49iU/Ql 1M1x0YFiXifa3DSDcvY+wQSNjwsqS9BJHgSyho3mQJ3UF47XSQ7B3G/MZ5AZxeI1BeE8 Wf/qq7HWPK4HDv3K7Czhx1USUJmN9l5jIQQKwBz+NN7mP63aYopulKK7qoOXgc7oVeE1 GkyuK8ccqJ11hCBG+mqWqEGcpNEmXAOjBNXE9BPG3jlLqRveBTkj3pYioBPJWd/+lGEL MohWeWkN/byws+q/i6qlYTNfwRXxCRPCqqFjeDW71MVct1sUDhm8L4j6xjlbIORcC8wH cTnQ== X-Gm-Message-State: AOAM530GT5TBGPZpe9KzuxfxgV1xDu+DX7tdNKCW5JghR7QCO7De6qzm lotH7rK2fRU2FEYcrM9ucPB0hg== X-Google-Smtp-Source: ABdhPJxxs7X6dCxb/vDWXMkOiyCanb6zOud7chyYZv+Kv+2yb3yktKcWguLLi8/qPM7uKa7eoG7yDA== X-Received: by 2002:ac8:6f25:: with SMTP id i5mr26221392qtv.202.1617074252368; Mon, 29 Mar 2021 20:17:32 -0700 (PDT) Received: from [192.168.1.33] (047-028-046-055.res.spectrum.com. [47.28.46.55]) by smtp.googlemail.com with ESMTPSA id y1sm15015318qki.9.2021.03.29.20.17.31 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 29 Mar 2021 20:17:32 -0700 (PDT) From: Doug Brown List-Id: To: linux-firmware@kernel.org, netdev@vger.kernel.org Cc: "David S. Miller" , Jakub Kicinski Subject: [RFC] (re)moving drivers/net/appletalk/cops_*.h firmware blobs Message-ID: <6c62d7d5-5171-98a3-5287-ecb1df20f574@schmorgal.com> Date: Mon, 29 Mar 2021 20:17:30 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.8.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Content-Language: en-US Hi there, I've been recently looking at the (ancient) AppleTalk/LocalTalk drivers=20 because I've been working on a modern LocalTalk network adapter for=20 crazy vintage computer enthusiasts like myself. ;-) In the process, I=20 discovered the existence of cops_ffdrv.h and cops_ltdrv.h in the kernel=20 source tree (drivers/net/appletalk), which contain proprietary binary=20 blobs for old COPS LocalTalk ISA cards with pretty vague licensing in=20 terms of ability to redistribute: > This material is licensed to you strictly for use in conjunction with > the use of COPS LocalTalk adapters. > There is no charge for this SDK. And no waranty express or implied > about its fitness for any purpose. However, we will cheerefully > refund every penny you paid for this SDK... > Regards, > > Thomas F. Divine > Chief Scientist I was surprised that these blobs were still in the kernel source. I=20 think it would be nice to remove another set of nonfree blobs from the=20 kernel source tree. Sadly, Mr. Divine passed away in 2015, so we can't=20 get any further input from him. Is this license acceptable enough to=20 migrate these two firmware binaries to linux-firmware and change the=20 driver to use request_firmware? Following the process in the=20 linux-firmware README to a T is likely not 100% possible because there's = nothing about permission to redistribute, and I won't be able to get a=20 Signed-off-by line. I've been experimenting in QEMU to convert the=20 driver to use request_firmware and have something working, but I wanted=20 to check before submitting a firmware pull request to start going=20 forward with this. Alternatively, if that's not acceptable, would it=20 make more sense to follow the route of other drivers like the iSight=20 camera driver (drivers/usb/misc/isight_firmware.c), and use=20 request_firmware, but supply instructions for extracting the firmware=20 binaries from the original source instead of including them in=20 linux-firmware? They are still available through archive.org's old=20 capture of the (now defunct) company's website, so instructions could be = provided for downloading and extracting it yourself. To be honest though -- the whole thing is probably a moot point given=20 that the driver in question is for an ISA card. Is there really someone=20 out there still using this driver? With that in mind, I suppose another=20 option would be to remove the driver altogether. I was hoping somebody=20 could provide some input on the correct way to handle this situation. I=20 would be happy to take care of it, but I'm unsure of the correct=20 approach. Any direction would be much appreciated! Thanks, Doug