All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Hendrik Farr <kernel@jfarr.cc>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Birger Koblitz <mail@birger-koblitz.de>,
	andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
	hsu.chih.kai@realtek.com, kuba@kernel.org,
	linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
	netdev@vger.kernel.org, olek2@wp.pl, pabeni@redhat.com
Subject: Re: RTL8159 firmware
Date: Wed, 1 Jul 2026 22:13:07 +0200	[thread overview]
Message-ID: <akV008yiRidFHu62@archlinux> (raw)
In-Reply-To: <8f349e00-1710-428d-8c70-5d1b1f4d42f3@lunn.ch>

On 01 21:29:20, Andrew Lunn wrote:
> On Wed, Jul 01, 2026 at 07:24:13PM +0200, Birger Koblitz wrote:
> > Hi Jan,
> > 
> > On 7/1/26 19:13, Jan Hendrik Farr wrote:
> > > Hi Birger,
> > > 
> > > it looks like the firmware file rtl_nic/rtl8159-1.fw isn't in linux-firmware yet.
> > > Could you send it for people to potentially test?
> > > 
> > > Jan
> > > 
> > The code to create the binary firmware file is at:
> > https://gitlab.com/koblitz-rtlnic/rtlnic_fw
> > But I cannot submit the firmware itself to linux-firmware, as the sourcecode from
> > which the binary data is extracted is published by Realtek under the GPL.
> 
> The obvious work around is to not convert it to binary.
> 
> 8152.c has a clear GPL-2.0 header. So you can edit that file, extract
> the two arrays, and it would still be GPL. You can make the firmware
> loader in the driver parse the ASCII array as it is. It also looks
> like you can .xz or .zst compress it, and the kernel
> _request_firmware() will handle the decompression for you.
> 

Not a GPL expert, but aren't those "binary" arrays in 8152.c a GPL violation?
Unless they created them directly. But I "highly suspect" they are
compiled from some source. They have to provide the "preferred form for
modification"

Jan


  reply	other threads:[~2026-07-01 20:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-05 15:56 [PATCH net-next v4 0/3] r8152: Add support for the RTL8159 10Gbit USB Ethernet chip Birger Koblitz
2026-05-05 15:56 ` [PATCH net-next v4 1/3] r8152: Add support for 10Gbit Link Speeds and EEE Birger Koblitz
2026-05-05 15:56 ` [PATCH net-next v4 2/3] r8152: Add support for the RTL8159 chip Birger Koblitz
2026-05-05 15:56 ` [PATCH net-next v4 3/3] r8152: Add firmware upload capability for RTL8157/RTL8159 Birger Koblitz
2026-07-01 17:13   ` RTL8159 firmware Jan Hendrik Farr
2026-07-01 17:24     ` Birger Koblitz
2026-07-01 18:15       ` Jan Hendrik Farr
2026-07-01 18:58         ` Birger Koblitz
2026-07-01 19:29       ` Andrew Lunn
2026-07-01 20:13         ` Jan Hendrik Farr [this message]
2026-07-01 20:32         ` Birger Koblitz
2026-07-01 21:06           ` Aleksander Jan Bajkowski
2026-07-03  4:47             ` Birger Koblitz
2026-05-07  2:00 ` [PATCH net-next v4 0/3] r8152: Add support for the RTL8159 10Gbit USB Ethernet chip patchwork-bot+netdevbpf

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=akV008yiRidFHu62@archlinux \
    --to=kernel@jfarr.cc \
    --cc=andrew+netdev@lunn.ch \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hsu.chih.kai@realtek.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mail@birger-koblitz.de \
    --cc=netdev@vger.kernel.org \
    --cc=olek2@wp.pl \
    --cc=pabeni@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.