From: Dalon Westergreen <dwesterg@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/8] arm: socfpga: Add distro boot to socfpga common header
Date: Sun, 19 Feb 2017 11:59:51 -0800 [thread overview]
Message-ID: <1487534391.13957.3.camel@gmail.com> (raw)
In-Reply-To: <20170219194555.GA16718@amd>
On Sun, 2017-02-19 at 20:45 +0100, Pavel Machek wrote:
> Hi!
>
> >
> > >
> > > >
> > > > >
> > > > > >
> > > > > > ?/* Environment for SDMMC boot */
> > > > > > ?#if defined(CONFIG_ENV_IS_IN_MMC) && !defined(CONFIG_ENV_OFFSET)
> > > > > > -#define CONFIG_SYS_MMC_ENV_DEV 0 /* device 0
> > > > > > */
> > > > > > -#define CONFIG_ENV_OFFSET 512 /* just after
> > > > > > the
> > > > > > MBR
> > > > > > */
> > > > > > +#define CONFIG_SYS_MMC_ENV_DEV 0 /*
> > > > > > device 0
> > > > > > */
> > > > > > +#define CONFIG_ENV_OFFSET (34*512)/* just after the
> > > > > > GPT
> > > > > > */
> ...
> >
> > I actually dont believe this will cause much of an issue. the env is placed
> > immediately after the partition table. ?I know this size fits between the
> > table and the typical location of the first partition without issue.
>
> Hmm. It is not immediately after partition table (==MBR), it is at
> sector 34. Now, by changing size you already break the setups, so
> moving it back to sector 1 does not help much, but can you explain?
Sorry, you are right. Frank had moved it after the GPT in his patchset and i
had just copied that. ?i will update this to be immediately after the mbr as
it was before.
--dalon
>
> Pavel
next prev parent reply other threads:[~2017-02-19 19:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-18 20:51 [U-Boot] [PATCH 0/8] arm: socfpga: Move to using distro boot Dalon Westergreen
2017-02-18 20:51 ` [U-Boot] [PATCH 1/8] arm: socfpga: Add distro boot to socfpga common header Dalon Westergreen
2017-02-18 21:01 ` Marek Vasut
2017-02-18 23:29 ` Dalon Westergreen
2017-02-19 0:37 ` Marek Vasut
2017-02-19 1:10 ` Dalon Westergreen
2017-02-19 2:26 ` Marek Vasut
2017-02-19 19:45 ` Pavel Machek
2017-02-19 19:59 ` Dalon Westergreen [this message]
2017-02-18 20:51 ` [U-Boot] [PATCH 2/8] arm: socfpga: DE0 use environment in " Dalon Westergreen
2017-02-18 20:51 ` [U-Boot] [PATCH 3/8] arm: socfpga: A5 SoCDK " Dalon Westergreen
2017-02-18 20:58 ` Marek Vasut
2017-02-18 20:51 ` [U-Boot] [PATCH 4/8] arm: socfpga: C5 " Dalon Westergreen
2017-02-18 20:51 ` [U-Boot] [PATCH 5/8] arm: socfpga: DE1 " Dalon Westergreen
2017-02-18 20:51 ` [U-Boot] [PATCH 6/8] arm: socfpga: SoCKit " Dalon Westergreen
2017-02-18 20:51 ` [U-Boot] [PATCH 7/8] arm: socfpga: Socrates " Dalon Westergreen
2017-02-18 20:51 ` [U-Boot] [PATCH 8/8] arm: socfpga: sr1500 " Dalon Westergreen
2017-02-18 20:56 ` Marek Vasut
2017-02-18 23:31 ` Dalon Westergreen
2017-02-19 0:33 ` Marek Vasut
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=1487534391.13957.3.camel@gmail.com \
--to=dwesterg@gmail.com \
--cc=u-boot@lists.denx.de \
/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