public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Dalon Westergreen <dwesterg@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v7 0/7] arm: socfpga: update default u-boot environment
Date: Thu, 26 Jan 2017 14:33:52 -0800	[thread overview]
Message-ID: <1485470032.8012.74.camel@gmail.com> (raw)
In-Reply-To: <12ad365e-bb38-5d4b-d65e-eec8b666be13@denx.de>

On Thu, 2017-01-26 at 22:41 +0100, Marek Vasut wrote:
> On 01/26/2017 10:05 PM, Dalon Westergreen wrote:
> > 
> > On Thu, 2017-01-26 at 21:54 +0100, Marek Vasut wrote:
> > > 
> > > On 01/26/2017 09:31 PM, Dalon Westergreen wrote:
> > > > 
> > > > 
> > > > From: Dalon Westergreen <dalon.westergreen@intel.com>
> > > > 
> > > > These patches update the boot and os partition numbers in
> > > > the???????????????????
> > > > default uboot environment for a number of socfpga
> > > > boards.??Per??????????????????
> > > > request, common environment configurations have been moved to
> > > > a?????????????????
> > > > shared
> > > > header.?????????????????????????????????????????????????????????????????
> > > > ?
> > > > 
> > > > Changed in v7:
> > > > ? Changed the bootloader partition to 3 to match the default layout for
> > > > ? socfpga.??commit 61520ac4d5545cc8d2e1792092e46ab8043d5f36 changed this
> > > > to
> > > > 1
> > > > ? which broke a number of socfpga kits.
> > > 
> > > And this commit will break another bulk of kits, great ...
> > I think the only kit that MAY be affected is the DE1 kit and I
> > actually dont even think that is true b/c they are probably
> > using the method described in the former thread where they just?
> > write the u-boot-with-spl.sfp to +64KB.??
> > CONFIG_SPL_ABORT_ON_RAW_IMAGE is defined for the board.
> 
> And all the kits which used the environment in mainline U-Boot.
> 
> > 
> > If i had a board I would test it.??But that said, this is currently?
> > how all of the altera kits, and the de0 kit work.
> 
> I'd be happy to take the previous patchset without this new "windows
> compatibility"/"ancient u-boot compatibility" crap and then proceed
> with a discussion on this new topic.
> 
> But now that it came up, well, I guess I'll wait for Dinh to make the
> decision, since we clearly have totally different opinions.
> 
Thanks. ?I am open to any suggestions, i could just wrap the?
boot partition number in socfpga_common with an ifndef? and define?
it as partition 3 in the altera boards which currently use that setup?

another option would be to re-implement the method used in the older
2013.01.01 uboot used by socfpga which, rather than using a partition
number specifically looked for a partition of type 0xa2 making the
partition number irrelevant?

--dalon

  reply	other threads:[~2017-01-26 22:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-26 20:31 [U-Boot] [PATCH v7 0/7] arm: socfpga: update default u-boot environment Dalon Westergreen
2017-01-26 20:31 ` [U-Boot] [PATCH v7 1/7] arm: socfpga: add env settings to common header Dalon Westergreen
2017-01-26 20:31 ` [U-Boot] [PATCH v7 2/7] arm: socfpga: update de0 nano default environment Dalon Westergreen
2017-01-26 20:31 ` [U-Boot] [PATCH v7 3/7] arm: socfpga: update cyclone5 socdk " Dalon Westergreen
2017-01-26 20:31 ` [U-Boot] [PATCH v7 4/7] arm: socfpga: update arria5 " Dalon Westergreen
2017-01-26 20:31 ` [U-Boot] [PATCH v7 5/7] arm: socfpga: Update DE1 environment Dalon Westergreen
2017-01-26 20:31 ` [U-Boot] [PATCH v7 6/7] arm: socfpga: Update SoCKit environment Dalon Westergreen
2017-01-26 20:31 ` [U-Boot] [PATCH v7 7/7] arm: socfpga: Update sr1500 environment Dalon Westergreen
2017-01-26 20:54 ` [U-Boot] [PATCH v7 0/7] arm: socfpga: update default u-boot environment Marek Vasut
2017-01-26 21:05   ` Dalon Westergreen
2017-01-26 21:41     ` Marek Vasut
2017-01-26 22:33       ` Dalon Westergreen [this message]
2017-01-27  2:11         ` Marek Vasut
2017-01-27  2:30           ` Dalon Westergreen
2017-01-27  4:24             ` 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=1485470032.8012.74.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