linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: haojian.zhuang@linaro.org (Haojian Zhuang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1 3/3] arm64: dts: add Hi6220 mailbox node
Date: Wed, 26 Aug 2015 10:41:52 +0800	[thread overview]
Message-ID: <1440556912.10987.54.camel@linaro.org> (raw)
In-Reply-To: <20150825153754.GY10728@bivouac.eciton.net>

On Tue, 2015-08-25 at 16:37 +0100, Leif Lindholm wrote:
> On Tue, Aug 25, 2015 at 04:51:22PM +0200, Ard Biesheuvel wrote:
> > >>    Arm kernel should either fetch memory information from
> > >>    efi or DT.
> > >
> > > Absolutely.
> > >
> > >>    Currently arm kernel fetch both efi memory information and
> > >>    reserved buffer from DTB at the same time.
> > >
> > > No, it does not.
> > 
> > It should not, but it does. Due to an oversight, the stub removes
> > /memreserve/ entries but ignores the reserved-memory node completely.
> 
> Urgh.
> 
> > This was reported here in fact
> > 
> > http://thread.gmane.org/gmane.linux.kernel.efi/5736/focus=5742
> > 
> > but there has not been a followup to this series.
> 
> Are all of those patches still relevant, or did some of them go in
> already?
> 
> Haojian: can you give that patch a spin and see if it does what you
> need, combined with adding the reserved areas to the UEFI memory map?
> 
> /
>     Leif

It's so nice. This patch is what I need.

Thanks
Haojian

  parent reply	other threads:[~2015-08-26  2:41 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-19  9:37 [PATCH v1 0/3] mailbox: hisilicon: add Hi6220 mailbox driver Leo Yan
2015-08-19  9:37 ` [PATCH v1 1/3] dt-bindings: mailbox: Document " Leo Yan
2015-08-25 11:17   ` Sudeep Holla
2015-08-25 13:01     ` Leo Yan
2015-08-19  9:37 ` [PATCH v1 2/3] mailbox: Hi6220: add " Leo Yan
2015-08-19  9:37 ` [PATCH v1 3/3] arm64: dts: add Hi6220 mailbox node Leo Yan
2015-08-21 18:40   ` Mark Rutland
2015-08-22 13:30     ` Leo Yan
2015-08-24  3:27       ` Leo Yan
2015-08-24  9:18     ` Leo Yan
2015-08-24  9:51       ` Mark Rutland
2015-08-24 10:19         ` Haojian Zhuang
2015-08-24 11:49           ` Leif Lindholm
2015-08-25  8:13             ` Haojian Zhuang
2015-08-25  9:46               ` Leif Lindholm
2015-08-25 10:15                 ` Haojian Zhuang
2015-08-25 10:40                   ` Leif Lindholm
2015-08-25 10:42                   ` Mark Rutland
2015-08-25 13:43                     ` Haojian Zhuang
2015-08-25 14:24                       ` Leif Lindholm
2015-08-25 14:51                         ` Ard Biesheuvel
2015-08-25 15:37                           ` Leif Lindholm
2015-08-25 15:45                             ` Ard Biesheuvel
2015-08-26  2:41                             ` Haojian Zhuang [this message]
2015-08-25 16:00                       ` Leo Yan
2015-08-26  1:25                         ` Haojian Zhuang
2015-08-26  6:59                           ` Leo Yan
2015-08-27 16:31                             ` Mark Rutland
2015-08-28  6:37                               ` Leo Yan
2015-08-27 15:54                           ` Daniel Thompson
2015-08-27 16:46                           ` Mark Rutland
2015-08-24 12:48           ` Mark Rutland
2015-08-25  8:04             ` Haojian Zhuang
2015-08-25 11:09               ` Mark Rutland
2015-08-25 11:36   ` Sudeep Holla
2015-08-25 14:04     ` Leo Yan
2015-08-25 14:13       ` Sudeep Holla

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=1440556912.10987.54.camel@linaro.org \
    --to=haojian.zhuang@linaro.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 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).