From: Cyril Bur <cyrilbur@gmail.com>
To: Joel Stanley <joel@jms.id.au>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: [PATCH linux 1/3] ARM: dts: aspeed: Update palmetto device tree
Date: Tue, 13 Dec 2016 14:48:45 +1100 [thread overview]
Message-ID: <1481600925.10426.5.camel@gmail.com> (raw)
In-Reply-To: <CACPK8XfoPV51WMHiXgFJ6gCyZDr5s+FGP3uDgKxvF6phimafyg@mail.gmail.com>
On Tue, 2016-12-13 at 14:29 +1100, Joel Stanley wrote:
> On Tue, Dec 13, 2016 at 2:11 PM, Cyril Bur <cyrilbur@gmail.com>
> wrote:
> > > > --- a/arch/arm/boot/dts/aspeed-bmc-opp-palmetto.dts
> > > > +++ b/arch/arm/boot/dts/aspeed-bmc-opp-palmetto.dts
> > > > @@ -17,7 +17,30 @@
> > > > };
> > > >
> > > > memory {
> > > > - reg = <0x40000000 0x10000000>;
> > > > + reg = <0x40000000 0x20000000>;
> > > > + };
> > >
> > > Can you send this in a separate patch? It should go into the tree
> > > now.
> > >
> >
> > Yep, should I send just for palmetto?
> >
> > Do you have a list of other platforms? I figure all the ast2400
> > based
> > aspeed-bmc-opp-* should get this change, should I include them all
> > in
> > one patch or all individually?
>
> One patch will do. I checked all of the machines and they all have
> 512MB (minus bits that I assume are reserved for framebuffers, etc.):
>
> Barreleye: 499020 kB
> Palmetto: 424204 kB
> Firestone: 416020 kB
> Garrison: 416012 kB
>
>
Ok great thanks!
Final question, I assume the same thing in a separate patch is good for
the framebuffer, I'd forgotten that the size of VGA memory can be
altered by a hardware strapping reg '0x1E6E2070 Hardware Strapping
Table' bits 3:2 define it. The default is for 16MB, is it safe assume
the platforms will come up with strapping reg in default state?
> Cheers,
>
> Joel
next prev parent reply other threads:[~2016-12-13 3:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-09 5:43 [PATCH linux 0/3] LPC/MBOX work Cyril Bur
2016-12-09 5:43 ` [PATCH linux 1/3] ARM: dts: aspeed: Update palmetto device tree Cyril Bur
2016-12-13 0:44 ` Joel Stanley
2016-12-13 3:11 ` Cyril Bur
2016-12-13 3:29 ` Joel Stanley
2016-12-13 3:48 ` Cyril Bur [this message]
2016-12-13 4:34 ` Joel Stanley
2016-12-09 5:43 ` [PATCH linux 2/3] drivers/misc: Add aspeed mbox driver Cyril Bur
2016-12-13 1:26 ` Joel Stanley
2016-12-13 8:03 ` Cédric Le Goater
2016-12-15 7:59 ` Cyril Bur
2016-12-15 22:50 ` Andrew Jeffery
2016-12-13 8:14 ` Cédric Le Goater
2016-12-15 8:01 ` Cyril Bur
2016-12-14 23:14 ` Andrew Jeffery
2016-12-14 23:14 ` Andrew Jeffery
2016-12-09 5:43 ` [PATCH linux 3/3] drivers/misc: Add aspeed lpc controlling driver Cyril Bur
2016-12-13 0:51 ` Joel Stanley
2016-12-15 0:58 ` Andrew Jeffery
2016-12-15 8:01 ` Cyril Bur
2016-12-13 10:24 ` [PATCH linux 0/3] LPC/MBOX work Cédric Le Goater
2016-12-14 0:13 ` Cyril Bur
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=1481600925.10426.5.camel@gmail.com \
--to=cyrilbur@gmail.com \
--cc=joel@jms.id.au \
--cc=openbmc@lists.ozlabs.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.