From: Kalle Valo <kvalo@codeaurora.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Arend van Spriel <arend.vanspriel@broadcom.com>,
Franky Lin <franky.lin@broadcom.com>,
Hante Meuleman <hante.meuleman@broadcom.com>,
Chi-Hsien Lin <chi-hsien.lin@infineon.com>,
Chung-hsien Hsu <chung-hsien.hsu@infineon.com>,
Wright Feng <wright.feng@infineon.com>,
Hans de Goede <hdegoede@redhat.com>,
linux-wireless@vger.kernel.org,
brcm80211-dev-list.pdl@broadcom.com,
SHA-cyfmac-dev-list@infineon.com
Subject: Re: [PATCH 1/2] brcmfmac: Add DMI nvram filename quirk for Predia Basic tablet
Date: Mon, 8 Feb 2021 11:03:14 +0000 (UTC) [thread overview]
Message-ID: <20210208110314.0CB9FC43462@smtp.codeaurora.org> (raw)
In-Reply-To: <20210129171413.139880-1-hdegoede@redhat.com>
Hans de Goede <hdegoede@redhat.com> wrote:
> The Predia Basic tablet contains quite generic names in the sys_vendor and
> product_name DMI strings, without this patch brcmfmac will try to load:
> brcmfmac43340-sdio.Insyde-CherryTrail.txt as nvram file which is a bit
> too generic.
>
> Add a DMI quirk so that a unique and clearly identifiable nvram file name
> is used on the Predia Basic tablet.
>
> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
2 patches applied to wireless-drivers-next.git, thanks.
af4b3a6f36d6 brcmfmac: Add DMI nvram filename quirk for Predia Basic tablet
a338c874d3d9 brcmfmac: Add DMI nvram filename quirk for Voyo winpad A15 tablet
--
https://patchwork.kernel.org/project/linux-wireless/patch/20210129171413.139880-1-hdegoede@redhat.com/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2021-02-08 11:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-29 17:14 [PATCH 1/2] brcmfmac: Add DMI nvram filename quirk for Predia Basic tablet Hans de Goede
2021-01-29 17:14 ` [PATCH 2/2] brcmfmac: Add DMI nvram filename quirk for Voyo winpad A15 tablet Hans de Goede
2021-02-08 11:03 ` Kalle Valo [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=20210208110314.0CB9FC43462@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=SHA-cyfmac-dev-list@infineon.com \
--cc=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=chi-hsien.lin@infineon.com \
--cc=chung-hsien.hsu@infineon.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=hdegoede@redhat.com \
--cc=linux-wireless@vger.kernel.org \
--cc=wright.feng@infineon.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.