mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Sascha Hauer <s.hauer@pengutronix.de>, Ahmad Fatoum <ahmad@a3f.at>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 1/2] ARM: at91: dts: sama5d27-som1: adapt to upstream partition layout
Date: Tue, 14 Jul 2020 20:45:19 +0200	[thread overview]
Message-ID: <47d0f439-8451-4b8e-83b6-acbd16d680e4@pengutronix.de> (raw)
In-Reply-To: <20200714183713.GW15485@pengutronix.de>



On 7/14/20 8:37 PM, Sascha Hauer wrote:
> On Sat, Jul 11, 2020 at 11:02:02AM +0200, Ahmad Fatoum wrote:
>> Linux v5.8-rc1 adds partitions to the flash@0 node, which now overlap
>> with the partitions we define and resulting in errors:
>>
>>   ERROR: m25p0.barebox: New partition m25p0.barebox conflicts
>> 	with m25p0.at91bootstrap
>>   ERROR: m25p0.barebox-environment: New partition
>>   	m25p0.barebox-environment conflicts with m25p0.bootloader
>>
>> We don't want to reuse those partitions as their name may and probably
>> will change (they have leading zeroes in the unit address).
>> We could use the &{/path/to/partition} syntax, but that might be broken
>> soon as well, as the nodes aren't inside a partitions node with a
>> "fixed-partitions" compatible.
>> The busses also don't align with the yaml schema and might be renamed.
>>
>> Nuke the full flash@0 node and supply ours and avoid these problems.
>> The offsets of the partitions have been adjusted to coincide with the
>> upstream offsets for second stage bootloader and environment.
>>
>> Signed-off-by: Ahmad Fatoum <ahmad@a3f.at>
>> ---
>> Hello Sascha,
>>
>> The brekage doesn't seem to end..
>> if possible please reorder before v5.8-rc1 dts/ sync.
>> ---
> 
> I haven't reordered it, please see if you are happy with the result
> anyway. It looks like I would have to put the whole at91 stack before
> the dts updates, I rather don't do that.

Ah, I missed that they don't apply cleanly.
Well, I think it's ok. Only environment will be broken between these
two comments.

> 
> Regards,
>  Sascha
> 

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
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

      reply	other threads:[~2020-07-14 18:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-11  9:02 Ahmad Fatoum
2020-07-11  9:02 ` [PATCH 2/2] fixup! ARM: at91: sama5d2: read back memory size from DDRAM controller Ahmad Fatoum
2020-07-14 18:37 ` [PATCH 1/2] ARM: at91: dts: sama5d27-som1: adapt to upstream partition layout Sascha Hauer
2020-07-14 18:45   ` Ahmad Fatoum [this message]

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=47d0f439-8451-4b8e-83b6-acbd16d680e4@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=ahmad@a3f.at \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.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