From: Yang Li <yang.li@amlogic.com>
To: yann.morin@orange.com, Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: Bernd Kuhls <bernd@kuhls.net>,
"Yann E. MORIN" <yann.morin.1998@free.fr>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/linux-firmware: add scripts for Amlogic
Date: Mon, 22 Jan 2024 10:12:16 +0800 [thread overview]
Message-ID: <4b9cd30d-bb10-4db4-b285-c3c4e3155a63@amlogic.com> (raw)
In-Reply-To: <ZapsMGs7sk3V0SMo@tl-lnx-nyma7486-2>
Hi all
On 1/19/24 20:33, yann.morin@orange.com wrote:
> [你通常不会收到来自 yann.morin@orange.com 的电子邮件。请访问 https://aka.ms/LearnAboutSenderIdentification,以了解这一点为什么很重要]
>
> Thomas, All,
>
> On 2024-01-19 12:23 +0100, Thomas Petazzoni via buildroot spake thusly:
>> On Fri, 19 Jan 2024 11:15:02 +0800
>> Yang Li <yang.li@amlogic.com> wrote:
>>> Add scripts for installing Amlogic firmware.
>>> +ifeq ($(BR2_PACKAGE_LINUX_FIRMWARE_AMLOGIC),y)
>> This option does not exist. Probably you forgot to add some changes in
>> package/linux-firmware/Config.in?
> In fact, this has already been applied by Yann@home as of commit:
> https://gitlab.com/buildroot.org/buildroot/-/commit/104b0fee839d3e4885329e77d1b8d553d552fb8e
>
> I thought the review comment was explicit enough, though:
>
> https://lore.kernel.org/buildroot/ZaOiZNVvO7OuK3sC@landeda/
>
> Applied to master with the above fixes, thanks.
>
>> Also, usually, our options are not per vendor, but more per device or
>> class of devices. Which devices are supported by those 2 bluetooth
>> firmware files?
> I also changed the Config.in entry for the same reason you noticed.
>
> I however assumed that they were Amlogic Bluettoth chipsets, as per the
> path of the binary blob in linux-firmware:
> amlogic/bluetooth/*.bin
>
> The path is 'amlogic', so it made sense to name the Config.oin entry
> BR2_PACKAGE_LINUX_FIRMWARE_AMLOGIC and to have the prompt list it as
> "Amlogic SOC Bluetooth".
>
> If that was not correct, we can change it, though...
Sorry, it's my fault.
^_^
>
> Regards,
> Yann E. MORIN.
>
> --
> ____________
> .-----------------.--------------------: _ :------------------.
> | Yann E. MORIN | Real-Time Embedded | __/ ) | /"\ ASCII RIBBON |
> | | Software Designer | _/ - /' | \ / CAMPAIGN |
> | +33 638.411.245 '--------------------: (_ `--, | X AGAINST |
> | yann.morin (at) orange.com |_=" ,--' | / \ HTML MAIL |
> '--------------------------------------:______/_____:------------------'
>
> ____________________________________________________________________________________________________________
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-01-22 2:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 3:15 [Buildroot] [PATCH] package/linux-firmware: add scripts for Amlogic Yang Li
2024-01-19 11:23 ` Thomas Petazzoni via buildroot
2024-01-19 12:33 ` yann.morin
2024-01-22 2:12 ` Yang Li [this message]
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=4b9cd30d-bb10-4db4-b285-c3c4e3155a63@amlogic.com \
--to=yang.li@amlogic.com \
--cc=bernd@kuhls.net \
--cc=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
--cc=yann.morin@orange.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox