From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: bcm2835: Add devicetree for the Raspberry Pi 3.
Date: Mon, 7 Mar 2016 22:54:30 -0700 [thread overview]
Message-ID: <56DE6916.9080608@wwwdotorg.org> (raw)
In-Reply-To: <1457116769-8567-2-git-send-email-eric@anholt.net>
On 03/04/2016 11:39 AM, Eric Anholt wrote:
> For now this doesn't support the new hardware present on the Pi 3 (BT,
> wifi, GPIO expander). Since the GPIO expander isn't supported, we
> also don't have the LEDs like the other board files do.
The series,
Acked-by: Stephen Warren <swarren@wwwdotorg.org>
... although I'd be slightly surprised if this was accepted; when
AArch64 was first announced, I thought the mainline ARM kernel community
decided that only 64-bit kernels would be supported on 64-bit HW? Still,
I don't immediately see that in any commit log or in the kernel doc
directory, so perhaps I'm misremembering. Hopefully; life is simpler
that way:-)
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Warren <swarren@wwwdotorg.org>
To: Eric Anholt <eric@anholt.net>
Cc: linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Lee Jones <lee@kernel.org>,
Florian Fainelli <f.fainelli@gmail.com>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH 2/2] ARM: bcm2835: Add devicetree for the Raspberry Pi 3.
Date: Mon, 7 Mar 2016 22:54:30 -0700 [thread overview]
Message-ID: <56DE6916.9080608@wwwdotorg.org> (raw)
In-Reply-To: <1457116769-8567-2-git-send-email-eric@anholt.net>
On 03/04/2016 11:39 AM, Eric Anholt wrote:
> For now this doesn't support the new hardware present on the Pi 3 (BT,
> wifi, GPIO expander). Since the GPIO expander isn't supported, we
> also don't have the LEDs like the other board files do.
The series,
Acked-by: Stephen Warren <swarren@wwwdotorg.org>
... although I'd be slightly surprised if this was accepted; when
AArch64 was first announced, I thought the mainline ARM kernel community
decided that only 64-bit kernels would be supported on 64-bit HW? Still,
I don't immediately see that in any commit log or in the kernel doc
directory, so perhaps I'm misremembering. Hopefully; life is simpler
that way:-)
next prev parent reply other threads:[~2016-03-08 5:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 18:39 [PATCH 1/2] dt-bindings: Add root properties for Raspberry Pi 3 Eric Anholt
2016-03-04 18:39 ` Eric Anholt
2016-03-04 18:39 ` Eric Anholt
2016-03-04 18:39 ` [PATCH 2/2] ARM: bcm2835: Add devicetree for the " Eric Anholt
2016-03-04 18:39 ` Eric Anholt
2016-03-04 18:39 ` Eric Anholt
2016-03-04 18:41 ` Mark Rutland
2016-03-04 18:41 ` Mark Rutland
2016-03-04 18:55 ` Eric Anholt
2016-03-04 18:55 ` Eric Anholt
2016-03-04 18:55 ` Eric Anholt
2016-03-04 18:59 ` Mark Rutland
2016-03-04 18:59 ` Mark Rutland
2016-03-04 18:59 ` Mark Rutland
2016-03-04 19:39 ` Eric Anholt
2016-03-04 19:39 ` Eric Anholt
2016-03-08 5:54 ` Stephen Warren [this message]
2016-03-08 5:54 ` Stephen Warren
2016-03-17 11:53 ` [PATCH 1/2] dt-bindings: Add root properties for " Rob Herring
2016-03-17 11:53 ` Rob Herring
2016-03-17 11:53 ` Rob Herring
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=56DE6916.9080608@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=linux-arm-kernel@lists.infradead.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 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.