[U-Boot] [PATCH] configs: Remove CONFIG_SPL_FS_EXT4 for all MX6 platforms

[Marek Vasut]

On 5/31/19 3:08 PM, Tom Rini wrote:
> On Fri, May 31, 2019 at 02:57:08PM +0200, Marek Vasut wrote:
>> On 5/31/19 2:51 PM, Tom Rini wrote:
>>> On Fri, May 31, 2019 at 02:46:45PM +0200, Marek Vasut wrote:
>>>> On 5/31/19 2:42 PM, Tom Rini wrote:
>>>>> On Fri, May 31, 2019 at 02:20:15PM +0200, Marek Vasut wrote:
>>>>>> On 5/31/19 2:18 PM, Fabio Estevam wrote:
>>>>>>> On Fri, May 31, 2019 at 9:17 AM Marek Vasut <marex at denx.de> wrote:
>>>>>>>
>>>>>>>> So I will have to track a downstream patch for wandboard now ?
>>>>>>>
>>>>>>> I didn't mention we want to remove CONFIG_SPL_FS_EXT4 from Wandboard.
>>>>>>
>>>>>> Ah OK, good, thanks.
>>>>>>
>>>>>>> I do want to remove it from mx6sabresd for sure.
>>>>>>
>>>>>> How does the sabresd boot ?
>>>>>
>>>>> How does your wandboard/novena boot?  I'd have sworn most distros do
>>>>> VFAT /boot not ext4 /boot.  Of course I'm still surprised anyone is
>>>>> loading u-boot from fs on iMX since I always see that as raw offsets.
>>>>
>>>> Novena is ext4 for sure, for two reasons -- VFAT has patent problems and
>>>> putting it at raw offset is just an accident waiting to happen (silent
>>>> FT corruption if the image gets too large)
>>>
>>> So you've setup your own one-off.  That's fine and something to support.
>>> But it's irregular and uncommon.
>>
>> I would say this is the recommended approach over just writing U-Boot
>> binary to random offset on the card at hoping that your data will be
>> safe the next time you update it ?
> 
> No, it's generally not.

That's not the point, the point is that writing data to random offset is
likely to end up with silent FS corruption eventually.

-- 
Best regards,
Marek Vasut