On 10/02/2018 09:54 AM, Patrick DELAUNAY wrote:
> Hi Marek,
Hi,
>> From: Marek Vasut
>> Sent: dimanche 30 septembre 2018 10:09
>>
>> On 09/28/2018 11:30 AM, Patrick DELAUNAY wrote:
>>> Hi,
>>
>> Hi,
>>
From: Marek Vasut
On 09/26/2018 01:04 PM, Patrick Delaunay wrote:
> solve
Hi Marek,
> From: Marek Vasut
> Sent: dimanche 30 septembre 2018 10:09
>
> On 09/28/2018 11:30 AM, Patrick DELAUNAY wrote:
> > Hi,
>
> Hi,
>
> >> From: Marek Vasut
> >>
> >> On 09/26/2018 01:04 PM, Patrick Delaunay wrote:
> >>> solve data abort for the command "ums 0 ubi 0"
> >>> because resu
On 09/28/2018 11:30 AM, Patrick DELAUNAY wrote:
> Hi,
Hi,
>> From: Marek Vasut
>>
>> On 09/26/2018 01:04 PM, Patrick Delaunay wrote:
>>> solve data abort for the command "ums 0 ubi 0"
>>> because result of case blk_get_device_part_str() result is OK but with
>>> block_dev = 0 when CONFIG_CMD_UBI
Hi,
> From: Marek Vasut
>
> On 09/26/2018 01:04 PM, Patrick Delaunay wrote:
> > solve data abort for the command "ums 0 ubi 0"
> > because result of case blk_get_device_part_str() result is OK but with
> > block_dev = 0 when CONFIG_CMD_UBIFS is activate and ubi volume is
> > mounted
>
> I don't
On 09/26/2018 01:04 PM, Patrick Delaunay wrote:
> solve data abort for the command "ums 0 ubi 0"
> because result of case blk_get_device_part_str() result is OK
> but with block_dev = 0 when CONFIG_CMD_UBIFS is activate and
> ubi volume is mounted
I don't quite understand the commit message, can y
solve data abort for the command "ums 0 ubi 0"
because result of case blk_get_device_part_str() result is OK
but with block_dev = 0 when CONFIG_CMD_UBIFS is activate and
ubi volume is mounted
Signed-off-by: Patrick Delaunay
---
I check and the issue is still present on U-Boot v2018.09,
on my boar
6 matches
Mail list logo