From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/linux-firmware: add new option for USB TI 3410/5052 firmware
Date: Fri, 25 Dec 2020 19:28:28 +0100 [thread overview]
Message-ID: <20201225182828.GD1680670@scaer> (raw)
In-Reply-To: <2a63d2fb5dc2a51888737af1d3e868b4b8cf74c8.1608718184.git.stefan@agner.ch>
Stefan, All,
On 2020-12-23 11:11 +0100, Stefan Agner spake thusly:
> Signed-off-by: Stefan Agner <stefan@agner.ch>
> ---
> package/linux-firmware/Config.in | 9 +++++++++
> package/linux-firmware/linux-firmware.mk | 6 ++++++
> 2 files changed, 15 insertions(+)
>
> diff --git a/package/linux-firmware/Config.in b/package/linux-firmware/Config.in
> index dbdfdb52b3..6d5e961527 100644
> --- a/package/linux-firmware/Config.in
> +++ b/package/linux-firmware/Config.in
> @@ -490,4 +490,13 @@ config BR2_PACKAGE_LINUX_FIRMWARE_QAT_C62X
>
> endmenu
>
> +menu "USB to Serial Firmware"
> +
> +config BR2_PACKAGE_LINUX_FIRMWARE_USB_SERIAL_TI
> + bool "USB TI 3410/5052 Serial Firmware"
> + help
> + Firmware files for TI 3410/5052
> +
> +endmenu
> +
> endif
> diff --git a/package/linux-firmware/linux-firmware.mk b/package/linux-firmware/linux-firmware.mk
> index f1c84a134d..f00fb2e6ae 100644
> --- a/package/linux-firmware/linux-firmware.mk
> +++ b/package/linux-firmware/linux-firmware.mk
> @@ -620,6 +620,12 @@ LINUX_FIRMWARE_FILES += qat_c62x.bin qat_c62x_mmp.bin
> LINUX_FIRMWARE_ALL_LICENSE_FILES += LICENCE.qat_firmware
> endif
>
> +ifeq ($(BR2_PACKAGE_LINUX_FIRMWARE_USB_SERIAL_TI),y)
> +LINUX_FIRMWARE_FILES += ti_3410.fw ti_5052.fw
That driver lists a lot of other firmware files:
492 MODULE_FIRMWARE("ti_3410.fw");
493 MODULE_FIRMWARE("ti_5052.fw");
494 MODULE_FIRMWARE("mts_cdma.fw");
495 MODULE_FIRMWARE("mts_gsm.fw");
496 MODULE_FIRMWARE("mts_edge.fw");
497 MODULE_FIRMWARE("mts_mt9234mu.fw");
498 MODULE_FIRMWARE("mts_mt9234zba.fw");
499 MODULE_FIRMWARE("moxa/moxa-1110.fw");
500 MODULE_FIRMWARE("moxa/moxa-1130.fw");
501 MODULE_FIRMWARE("moxa/moxa-1131.fw");
502 MODULE_FIRMWARE("moxa/moxa-1150.fw");
503 MODULE_FIRMWARE("moxa/moxa-1151.fw");
which are all available in linux-firmware. I was about to add them to
the list and commit that, but the situation is a bit more complex, as
there is a license file for the moxa firmwares.
Care to respin with the extra firmware added to the list, please?
Regards,
Yann E. MORIN.
> +# No license file; the license is in the file WHENCE
> +# which is installed unconditionally
> +endif
> +
> ifneq ($(LINUX_FIRMWARE_FILES),)
> define LINUX_FIRMWARE_INSTALL_FILES
> cd $(@D) && \
> --
> 2.29.2
>
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2020-12-25 18:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-23 10:11 [Buildroot] [PATCH] package/linux-firmware: add new option for USB TI 3410/5052 firmware Stefan Agner
2020-12-25 18:28 ` Yann E. MORIN [this message]
2020-12-28 13:54 ` Stefan Agner
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=20201225182828.GD1680670@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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.