From: Eric Anholt <eric@anholt.net>
To: Stefan Wahren <stefan.wahren@i2se.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>
Cc: Stefan Wahren <stefan.wahren@i2se.com>,
devicetree@vger.kernel.org, Phil Elwell <phil@raspberrypi.org>,
bcm-kernel-feedback-list@broadcom.com,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V4 2/3] ARM: dts: add Raspberry Pi 3 A+
Date: Thu, 27 Dec 2018 16:51:54 -0800 [thread overview]
Message-ID: <87wonulbh1.fsf@anholt.net> (raw)
In-Reply-To: <1545780008-22271-3-git-send-email-stefan.wahren@i2se.com>
[-- Attachment #1.1: Type: text/plain, Size: 294 bytes --]
Stefan Wahren <stefan.wahren@i2se.com> writes:
> The Raspberry Pi 3 A+ is similar to the Pi 3 B+ but has only 512 MB RAM,
> 1 USB 2.0 port and no Ethernet.
>
> Compared to the Raspberry Pi 3 B it isn't possible to control BT_ON and
> WL_ON separately.
Acked-by: Eric Anholt <eric@anholt.net>
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2018-12-28 0:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-25 23:20 [PATCH V4 0/3] ARM: dts: add Raspberry Pi 3 A+ Stefan Wahren
2018-12-25 23:20 ` [PATCH V4 1/3] dt-bindings: bcm: Add " Stefan Wahren
2018-12-25 23:20 ` [PATCH V4 2/3] ARM: dts: add " Stefan Wahren
2018-12-28 0:51 ` Eric Anholt [this message]
2019-01-12 18:11 ` Sergey Suloev
2019-01-12 19:34 ` Stefan Wahren
2019-01-14 12:16 ` Sergey Suloev
2018-12-25 23:20 ` [PATCH V4 3/3] arm64: dts: broadcom: Add reference to RPi " Stefan Wahren
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=87wonulbh1.fsf@anholt.net \
--to=eric@anholt.net \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=phil@raspberrypi.org \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=sbranden@broadcom.com \
--cc=stefan.wahren@i2se.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;
as well as URLs for NNTP newsgroup(s).