All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernd Kuhls <bernd.kuhls@t-online.de>
To: buildroot@uclibc.org
Subject: Re: [Buildroot] [PATCH 1/1] package/dvb-firmware: new package
Date: Tue, 27 Dec 2022 23:30:45 +0100	[thread overview]
Message-ID: <pan$60b46$ce6281f3$ccde7c98$d5e8f550@ID-313208.user.individual.net> (raw)
In-Reply-To: 20221227224354.3b1d1fdf__40547.9438648158$1672177457$gmane$org@windsurf

Hi Thomas,

Am Tue, 27 Dec 2022 22:43:54 +0100 schrieb Thomas Petazzoni via buildroot:

> Hello,
> 
> On Mon, 26 Dec 2022 19:03:53 +0100 Bernd Kuhls
> <bernd.kuhls@t-online.de> wrote:
> 
>> Signed-off-by: Bernd Kuhls
>> <bernd.kuhls@t-online.de>
> 
> Do we know why these firmware files are not part of the linux-firmware
> project? They are needed in conjunction with which kernel drivers?

The history of this repo is unknown to me, it is used by the LibreELEC 
project in their images. Personally I need only these firmware files:

BR2_PACKAGE_DVB_FIRMWARE_FILES="dvb-demod-m88rs6000.fw dvb-demod-si2168-
d60-01.fw v4l-cx23885-avcore-01.fw"

for the cx23885/m88ds3103/si2168 kernel modules needed by this card:

05:00.0 Multimedia video controller: Conexant Systems, Inc. CX23887/8 
PCIe Broadcast Audio and Video Decoder with 3D Comb (rev 04)

(aka Hauppauge WinTV-HVR-5525HD)

These firmware files are not present in the linux-firmware package.

To pick up Yann's proposal: How about adding a device-specific Config.in 
option for these firmware files like

config BR2_PACKAGE_DVB_FIRMWARE_WINTV_5525HD
    bool "firmware for Hauppauge WinTV-HVR-5525HD"

When other users need specific firmware from this package they can add 
new options when needed, like I did with https://patchwork.ozlabs.org/
project/buildroot/patch/20221218220318.563479-1-bernd.kuhls@t-online.de/

Or, if the license mess gets too complicated, I am happy to keep the 
package in my private repo ;)

Regards, Bernd

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2022-12-27 22:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-26 18:03 [Buildroot] [PATCH 1/1] package/dvb-firmware: new package Bernd Kuhls
2022-12-27 21:43 ` Thomas Petazzoni via buildroot
2022-12-27 21:58   ` Yann E. MORIN
2022-12-28  8:37     ` Thomas Petazzoni via buildroot
     [not found] ` <20221227224354.3b1d1fdf__40547.9438648158$1672177457$gmane$org@windsurf>
2022-12-27 22:30   ` Bernd Kuhls [this message]
2022-12-28 10:00     ` Thomas Petazzoni via buildroot
2022-12-28 22:22       ` Bernd Kuhls

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='pan$60b46$ce6281f3$ccde7c98$d5e8f550@ID-313208.user.individual.net' \
    --to=bernd.kuhls@t-online.de \
    --cc=buildroot@uclibc.org \
    /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.