From: Sascha Hauer <s.hauer@pengutronix.de>
To: Alexander Aring <alex.aring@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 1/5] ARM: phyCORE-AM335x: Updated SPI NOR dts entries
Date: Fri, 5 Sep 2014 08:51:22 +0200 [thread overview]
Message-ID: <20140905065122.GB5352@pengutronix.de> (raw)
In-Reply-To: <20140905063158.GA23258@omega>
On Fri, Sep 05, 2014 at 08:32:00AM +0200, Alexander Aring wrote:
> Hi Sascha,
>
> On Fri, Sep 05, 2014 at 07:37:33AM +0200, Sascha Hauer wrote:
> > Hi Teresa,
> >
> > On Thu, Sep 04, 2014 at 08:50:36AM +0200, Teresa Gámez wrote:
> > > Updated the SPI NOR flash entries. NOR flash got
> > > detected but did not work.
> > >
> > > - Updated muxing
> > > - Fixed frequency
> > > - Fixed CS
> > > - Removed first compatible entry (the flashes used is changing frequently)
> > >
> > > Signed-off-by: Teresa Gámez <t.gamez@phytec.de>
> >
> > Applied up to 4/5. The Root partition start seems indeed wrong.
> >
>
> yea. But sometimes you also do a "fixed while applying". Why not now?
> Okay, maybe on the "good" days.
Maybe because you didn't write the correct start offset and I didn't
feel like doing maths before the first coffee ;)
>
> Nevertheless, isn't there any mechanism to check on conflicts while
> creating partitions like request memory mapped regions?
No. Right now creating multiple conflicting partitions is a feature, see
for example /dev/env0 and /dev/nor0.bareboxenv. Those are two
partitions which both conflict but must both exist.
I must admit it's a misfeature though and I wish we could do without it
as it really can hide problems.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2014-09-05 6:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-04 6:50 Teresa Gámez
2014-09-04 6:50 ` [PATCH 2/5] ARM: phyCORE-AM335x: Update RAM Timings Teresa Gámez
2014-09-04 6:50 ` [PATCH 3/5] ARM: phyCORE-AM335x: Fixup RAM setting naming Teresa Gámez
2014-09-04 6:50 ` [PATCH 4/5] ARM: phyCORE-AM335x: Add support for 2x512MB RAM Teresa Gámez
2014-09-04 6:50 ` [PATCH 5/5] ARM: phyCORE-AM335x: Update partition table Teresa Gámez
2014-09-04 7:13 ` Alexander Aring
2014-09-04 7:15 ` Alexander Aring
2014-09-05 5:37 ` [PATCH 1/5] ARM: phyCORE-AM335x: Updated SPI NOR dts entries Sascha Hauer
2014-09-05 6:32 ` Alexander Aring
2014-09-05 6:51 ` Sascha Hauer [this message]
2014-09-05 7:18 ` Alexander Aring
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=20140905065122.GB5352@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=alex.aring@gmail.com \
--cc=barebox@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