From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/4] board: orangepi: lite2: Add WiFi support
Date: Sun, 16 Dec 2018 16:00:37 +0100 [thread overview]
Message-ID: <20181216160037.1150c27e@windsurf.home> (raw)
In-Reply-To: <20181103125608.2255-4-jagan@amarulasolutions.com>
Hello,
On Sat, 3 Nov 2018 18:26:08 +0530, Jagan Teki wrote:
> Orangepi lite2 board has AP6356S WiFi/BT combo, but does
> not have ethernet port. So it makes sense to enable wireless
> networking by default:
> - add broadcom wireless firmware package to image
> - add basic wireless tools to image
> - add rootfs overlay with proper NVRAM file for on-board AP6356S chip
> - add mdev to image to enable module autoloading
> - update readme.txt to test wifi
>
> Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
> ---
> board/orangepi/orangepi-lite2/readme.txt | 9 ++
> .../lib/firmware/brcm/brcmfmac43455-sdio.txt | 82 +++++++++++++++++++
> configs/orangepi_lite2_defconfig | 13 +++
> 3 files changed, 104 insertions(+)
> create mode 100755 board/orangepi/orangepi-lite2/rootfs_overlay/lib/firmware/brcm/brcmfmac43455-sdio.txt
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-12-16 15:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-03 12:56 [Buildroot] [PATCH 1/4] uboot: bump to version 2018.09 Jagan Teki
2018-11-03 12:56 ` [Buildroot] [PATCH v2 2/4] board: orangepi: Add Orangepi One Plus support Jagan Teki
2018-11-03 19:27 ` Baruch Siach
2018-12-16 15:00 ` Thomas Petazzoni
2018-11-03 12:56 ` [Buildroot] [PATCH 3/4] board: orangepi: Add Orangepi Lite2 support Jagan Teki
2018-12-16 15:00 ` Thomas Petazzoni
2018-11-03 12:56 ` [Buildroot] [PATCH 4/4] board: orangepi: lite2: Add WiFi support Jagan Teki
2018-12-16 15:00 ` Thomas Petazzoni [this message]
2018-11-03 14:56 ` [Buildroot] [PATCH 1/4] uboot: bump to version 2018.09 Thomas Petazzoni
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=20181216160037.1150c27e@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox