From: Gerhard Wiesinger <lists@wiesinger.com>
To: Florian Eckert <fe@dev.tdt.de>,
Eckert.Florian@googlemail.com, info@metux.net,
dvhart@infradead.org, andy@infradead.org
Cc: platform-driver-x86@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: platform/x86/pcengines-apuv2: Missing apu4
Date: Fri, 26 Jul 2019 17:25:34 +0200 [thread overview]
Message-ID: <2f22106f-4d13-f3a7-0862-3a71762d62ab@wiesinger.com> (raw)
In-Reply-To: <02b34d18-27bc-cb48-f698-03df61df7d91@wiesinger.com>
Hello,
I saw that the apu4 board is completly missing (also on 5.3rc1). Can you
please add it. Should be very easy, see below.
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/platform/x86/pcengines-apuv2.c?h=v5.1.20
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/platform/x86/pcengines-apuv2.c?h=v5.3-rc1
For further rference:
https://www.pcengines.ch/apu2.htm
https://www.pcengines.ch/apu4c2.htm
https://www.pcengines.ch/apu4c4.htm
Please backport it also to 5.1.x and 5.2.x.
Thnx.
Ciao,
Gerhard
/* APU4 w/ legacy bios < 4.0.8 */
{
.ident = "apu4",
.matches = {
DMI_MATCH(DMI_SYS_VENDOR, "PC Engines"),
DMI_MATCH(DMI_BOARD_NAME, "APU4")
},
.driver_data = (void *)&board_apu2,
},
/* APU4 w/ legacy bios >= 4.0.8 */
{
.ident = "apu4",
.matches = {
DMI_MATCH(DMI_SYS_VENDOR, "PC Engines"),
DMI_MATCH(DMI_BOARD_NAME, "apu4)
},
.driver_data = (void *)&board_apu2,
},
/* APU4 w/ mainline bios */
{
.ident = "apu4",
.matches = {
DMI_MATCH(DMI_SYS_VENDOR, "PC Engines"),
DMI_MATCH(DMI_BOARD_NAME, "PC Engines apu4")
},
.driver_data = (void *)&board_apu2,
},
|
MODULE_DESCRIPTION("PC Engines APUv2/APUv3/APUv4 board GPIO/LED/keys
driver"); |
next parent reply other threads:[~2019-07-26 15:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <02b34d18-27bc-cb48-f698-03df61df7d91@wiesinger.com>
2019-07-26 15:25 ` Gerhard Wiesinger [this message]
2019-07-29 8:35 ` platform/x86/pcengines-apuv2: Missing apu4 Enrico Weigelt, metux IT consult
2019-07-29 20:51 ` Gerhard Wiesinger
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=2f22106f-4d13-f3a7-0862-3a71762d62ab@wiesinger.com \
--to=lists@wiesinger.com \
--cc=Eckert.Florian@googlemail.com \
--cc=andy@infradead.org \
--cc=dvhart@infradead.org \
--cc=fe@dev.tdt.de \
--cc=info@metux.net \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).