* u-boot-flasher fails with current u-boot
@ 2017-06-06 23:36 Peter.Chubb-RgbkMxAV74wUb6iz2VnApA
[not found] ` <84tw3sk7sq.wl-Peter.Chubb-RgbkMxAV74wUb6iz2VnApA@public.gmane.org>
0 siblings, 1 reply; 13+ messages in thread
From: Peter.Chubb-RgbkMxAV74wUb6iz2VnApA @ 2017-06-06 23:36 UTC (permalink / raw)
To: linux-tegra-u79uwXL29TY76Z2rM5mHXA
Cc: swarren-DDmLM1+adcrQT0dZR+AlfA, sjg-F7+t8E8rja9g9hUCZPvPmw
Recent changes to U-Boot have broken u-boot-flasher. I now see,
after
./tegra-uboot-flasher flash jetson-tk1
on the serial port:
>>> Selecting MMC device...
tegra_mmc_send_cmd_bounced: MMC Timeout
Interrupt status 0x00000001
Interrupt status enable 0xffff003b
Interrupt signal enable 0xffff0002
Present status 0x01fb02f6
mmc_init: -1, time 8042
and nothing is flashed to the MMC.
I can do
./tegra-uboot-flasher exec jetson-tk1
and everything works as expected. The running-from-RAM u-boot can
access the MMC.
The patch in U-Boot that causes the problems (found by git-bisect) is
0e513e788f tegra: convert MMC to use driver model for operations
--
Dr Peter Chubb Tel: +61 2 9490 5852 http://ts.data61.csiro.au/
Trustworthy Systems Group Data61 (formerly NICTA)
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: u-boot-flasher fails with current u-boot
2017-06-06 23:36 u-boot-flasher fails with current u-boot Peter.Chubb-RgbkMxAV74wUb6iz2VnApA
@ 2017-06-07 3:13 ` Simon Glass
0 siblings, 0 replies; 13+ messages in thread
From: Simon Glass @ 2017-06-07 3:13 UTC (permalink / raw)
To: Peter Chubb
Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA, Stephen Warren, U-Boot Mailing List
Hi Peter,
On 6 June 2017 at 17:36, <Peter.Chubb-RgbkMxAV74wUb6iz2VnApA@public.gmane.org> wrote:
> Recent changes to U-Boot have broken u-boot-flasher. I now see,
> after
> ./tegra-uboot-flasher flash jetson-tk1
> on the serial port:
> >>> Selecting MMC device...
> tegra_mmc_send_cmd_bounced: MMC Timeout
> Interrupt status 0x00000001
> Interrupt status enable 0xffff003b
> Interrupt signal enable 0xffff0002
> Present status 0x01fb02f6
> mmc_init: -1, time 8042
>
> and nothing is flashed to the MMC.
>
> I can do
> ./tegra-uboot-flasher exec jetson-tk1
> and everything works as expected. The running-from-RAM u-boot can
> access the MMC.
>
> The patch in U-Boot that causes the problems (found by git-bisect) is
> 0e513e788f tegra: convert MMC to use driver model for operations
Oh dear. I cannot find my board but will see if I can repeat this on a beaver.
>
> --
> Dr Peter Chubb Tel: +61 2 9490 5852 http://ts.data61.csiro.au/
> Trustworthy Systems Group Data61 (formerly NICTA)
Regards,
Simon
^ permalink raw reply [flat|nested] 13+ messages in thread
* [U-Boot] u-boot-flasher fails with current u-boot
@ 2017-06-07 3:13 ` Simon Glass
0 siblings, 0 replies; 13+ messages in thread
From: Simon Glass @ 2017-06-07 3:13 UTC (permalink / raw)
To: u-boot
Hi Peter,
On 6 June 2017 at 17:36, <Peter.Chubb@data61.csiro.au> wrote:
> Recent changes to U-Boot have broken u-boot-flasher. I now see,
> after
> ./tegra-uboot-flasher flash jetson-tk1
> on the serial port:
> >>> Selecting MMC device...
> tegra_mmc_send_cmd_bounced: MMC Timeout
> Interrupt status 0x00000001
> Interrupt status enable 0xffff003b
> Interrupt signal enable 0xffff0002
> Present status 0x01fb02f6
> mmc_init: -1, time 8042
>
> and nothing is flashed to the MMC.
>
> I can do
> ./tegra-uboot-flasher exec jetson-tk1
> and everything works as expected. The running-from-RAM u-boot can
> access the MMC.
>
> The patch in U-Boot that causes the problems (found by git-bisect) is
> 0e513e788f tegra: convert MMC to use driver model for operations
Oh dear. I cannot find my board but will see if I can repeat this on a beaver.
>
> --
> Dr Peter Chubb Tel: +61 2 9490 5852 http://ts.data61.csiro.au/
> Trustworthy Systems Group Data61 (formerly NICTA)
Regards,
Simon
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: u-boot-flasher fails with current u-boot
2017-06-07 3:13 ` [U-Boot] " Simon Glass
@ 2017-06-07 4:01 ` Peter.Chubb at data61.csiro.au
-1 siblings, 0 replies; 13+ messages in thread
From: Peter.Chubb @ 2017-06-07 4:01 UTC (permalink / raw)
To: sjg; +Cc: linux-tegra, swarren, u-boot
>>>>> "Simon" == Simon Glass <sjg@chromium.org> writes:
:
Simon> Oh dear. I cannot find my board but will see if I can repeat
Simon> this on a beaver.
Thanks.
If there's any additional logging you'd like me to collect on the
Jetson, let me know.
Peter C
--
Dr Peter Chubb Tel: +61 2 9490 5852 http://ts.data61.csiro.au/
Trustworthy Systems Group Data61 (formerly NICTA)
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
^ permalink raw reply [flat|nested] 13+ messages in thread
* [U-Boot] u-boot-flasher fails with current u-boot
@ 2017-06-07 4:01 ` Peter.Chubb at data61.csiro.au
0 siblings, 0 replies; 13+ messages in thread
From: Peter.Chubb at data61.csiro.au @ 2017-06-07 4:01 UTC (permalink / raw)
To: u-boot
>>>>> "Simon" == Simon Glass <sjg@chromium.org> writes:
:
Simon> Oh dear. I cannot find my board but will see if I can repeat
Simon> this on a beaver.
Thanks.
If there's any additional logging you'd like me to collect on the
Jetson, let me know.
Peter C
--
Dr Peter Chubb Tel: +61 2 9490 5852 http://ts.data61.csiro.au/
Trustworthy Systems Group Data61 (formerly NICTA)
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: u-boot-flasher fails with current u-boot
2017-06-07 4:01 ` [U-Boot] " Peter.Chubb at data61.csiro.au
@ 2017-06-08 1:12 ` Peter.Chubb at data61.csiro.au
-1 siblings, 0 replies; 13+ messages in thread
From: Peter.Chubb @ 2017-06-08 1:12 UTC (permalink / raw)
To: Peter.Chubb; +Cc: linux-tegra, u-boot, swarren
>>>>> "Peter" == Peter Chubb <Peter.Chubb@data61.csiro.au> writes:
>>>>> "Simon" == Simon Glass <sjg@chromium.org> writes:
Simon> Oh dear. I cannot find my board but will see if I can repeat
Simon> this on a beaver.
Peter> If there's any additional logging you'd like me to collect on
Peter> the Jetson, let me know.
I tried to reproduce this this morning. Today, even trying to exec
the U-Boot without flashing fails.
So,
./tegra-uboot-flasher exec jetson-tk1
with a current u-boot gives an inoperative eMMC.
In the boot header I see:
U-Boot 2017.05-00769-g0e513e788f (Jun 08 2017 - 09:26:27 +1000)
TEGRA124
Model: NVIDIA Jetson TK1
Board: NVIDIA Jetson TK1
DRAM: 2 GiB
MMC: sdhci@700b0400: 1, sdhci@700b0600: 0
Then:
Tegra124 (Jetson TK1) # mmc rescan
tegra_mmc_send_cmd_bounced: MMC Timeout
Interrupt status 0x00000001
Interrupt status enable 0xffff003b
Interrupt signal enable 0xffff0002
Present status 0x01fb02f6
mmc_init: -1, time 8042
Peter C
--
Dr Peter Chubb Tel: +61 2 9490 5852 http://ts.data61.csiro.au/
Trustworthy Systems Group Data61 (formerly NICTA)
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
^ permalink raw reply [flat|nested] 13+ messages in thread
* [U-Boot] u-boot-flasher fails with current u-boot
@ 2017-06-08 1:12 ` Peter.Chubb at data61.csiro.au
0 siblings, 0 replies; 13+ messages in thread
From: Peter.Chubb at data61.csiro.au @ 2017-06-08 1:12 UTC (permalink / raw)
To: u-boot
>>>>> "Peter" == Peter Chubb <Peter.Chubb@data61.csiro.au> writes:
>>>>> "Simon" == Simon Glass <sjg@chromium.org> writes:
Simon> Oh dear. I cannot find my board but will see if I can repeat
Simon> this on a beaver.
Peter> If there's any additional logging you'd like me to collect on
Peter> the Jetson, let me know.
I tried to reproduce this this morning. Today, even trying to exec
the U-Boot without flashing fails.
So,
./tegra-uboot-flasher exec jetson-tk1
with a current u-boot gives an inoperative eMMC.
In the boot header I see:
U-Boot 2017.05-00769-g0e513e788f (Jun 08 2017 - 09:26:27 +1000)
TEGRA124
Model: NVIDIA Jetson TK1
Board: NVIDIA Jetson TK1
DRAM: 2 GiB
MMC: sdhci at 700b0400: 1, sdhci at 700b0600: 0
Then:
Tegra124 (Jetson TK1) # mmc rescan
tegra_mmc_send_cmd_bounced: MMC Timeout
Interrupt status 0x00000001
Interrupt status enable 0xffff003b
Interrupt signal enable 0xffff0002
Present status 0x01fb02f6
mmc_init: -1, time 8042
Peter C
--
Dr Peter Chubb Tel: +61 2 9490 5852 http://ts.data61.csiro.au/
Trustworthy Systems Group Data61 (formerly NICTA)
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: u-boot-flasher fails with current u-boot
2017-06-08 1:12 ` [U-Boot] " Peter.Chubb at data61.csiro.au
@ 2017-06-08 3:11 ` Simon Glass
-1 siblings, 0 replies; 13+ messages in thread
From: Simon Glass @ 2017-06-08 3:11 UTC (permalink / raw)
To: Peter Chubb
Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA, Stephen Warren, U-Boot Mailing List
Hi Peter,
On 7 June 2017 at 19:12, <Peter.Chubb-RgbkMxAV74wUb6iz2VnApA@public.gmane.org> wrote:
>>>>>> "Peter" == Peter Chubb <Peter.Chubb-RgbkMxAV74wUb6iz2VnApA@public.gmane.org> writes:
>>>>>> "Simon" == Simon Glass <sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org> writes:
>
> Simon> Oh dear. I cannot find my board but will see if I can repeat
> Simon> this on a beaver.
>
> Peter> If there's any additional logging you'd like me to collect on
> Peter> the Jetson, let me know.
>
> I tried to reproduce this this morning. Today, even trying to exec
> the U-Boot without flashing fails.
The good news is I found my Jetson-TK1 and I can repeat your problem.
>
> So,
> ./tegra-uboot-flasher exec jetson-tk1
> with a current u-boot gives an inoperative eMMC.
>
> In the boot header I see:
>
> U-Boot 2017.05-00769-g0e513e788f (Jun 08 2017 - 09:26:27 +1000)
>
> TEGRA124
> Model: NVIDIA Jetson TK1
> Board: NVIDIA Jetson TK1
> DRAM: 2 GiB
> MMC: sdhci@700b0400: 1, sdhci@700b0600: 0
>
> Then:
>
> Tegra124 (Jetson TK1) # mmc rescan
Why are you running 'mmc rescan'? Is this because the MMC has changed?
This command does not seem to work since it does not re-probe the
driver. It looks like the driver assumes that the controller is reset
each time. I'll send a patch which seems to fix it for me.
> tegra_mmc_send_cmd_bounced: MMC Timeout
> Interrupt status 0x00000001
> Interrupt status enable 0xffff003b
> Interrupt signal enable 0xffff0002
> Present status 0x01fb02f6
> mmc_init: -1, time 8042
>
> Peter C
> --
> Dr Peter Chubb Tel: +61 2 9490 5852 http://ts.data61.csiro.au/
> Trustworthy Systems Group Data61 (formerly NICTA)
Regards,
Simon
^ permalink raw reply [flat|nested] 13+ messages in thread
* [U-Boot] u-boot-flasher fails with current u-boot
@ 2017-06-08 3:11 ` Simon Glass
0 siblings, 0 replies; 13+ messages in thread
From: Simon Glass @ 2017-06-08 3:11 UTC (permalink / raw)
To: u-boot
Hi Peter,
On 7 June 2017 at 19:12, <Peter.Chubb@data61.csiro.au> wrote:
>>>>>> "Peter" == Peter Chubb <Peter.Chubb@data61.csiro.au> writes:
>>>>>> "Simon" == Simon Glass <sjg@chromium.org> writes:
>
> Simon> Oh dear. I cannot find my board but will see if I can repeat
> Simon> this on a beaver.
>
> Peter> If there's any additional logging you'd like me to collect on
> Peter> the Jetson, let me know.
>
> I tried to reproduce this this morning. Today, even trying to exec
> the U-Boot without flashing fails.
The good news is I found my Jetson-TK1 and I can repeat your problem.
>
> So,
> ./tegra-uboot-flasher exec jetson-tk1
> with a current u-boot gives an inoperative eMMC.
>
> In the boot header I see:
>
> U-Boot 2017.05-00769-g0e513e788f (Jun 08 2017 - 09:26:27 +1000)
>
> TEGRA124
> Model: NVIDIA Jetson TK1
> Board: NVIDIA Jetson TK1
> DRAM: 2 GiB
> MMC: sdhci at 700b0400: 1, sdhci at 700b0600: 0
>
> Then:
>
> Tegra124 (Jetson TK1) # mmc rescan
Why are you running 'mmc rescan'? Is this because the MMC has changed?
This command does not seem to work since it does not re-probe the
driver. It looks like the driver assumes that the controller is reset
each time. I'll send a patch which seems to fix it for me.
> tegra_mmc_send_cmd_bounced: MMC Timeout
> Interrupt status 0x00000001
> Interrupt status enable 0xffff003b
> Interrupt signal enable 0xffff0002
> Present status 0x01fb02f6
> mmc_init: -1, time 8042
>
> Peter C
> --
> Dr Peter Chubb Tel: +61 2 9490 5852 http://ts.data61.csiro.au/
> Trustworthy Systems Group Data61 (formerly NICTA)
Regards,
Simon
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: u-boot-flasher fails with current u-boot
2017-06-08 3:11 ` [U-Boot] " Simon Glass
@ 2017-06-08 4:00 ` Peter.Chubb at data61.csiro.au
-1 siblings, 0 replies; 13+ messages in thread
From: Peter.Chubb-RgbkMxAV74wUb6iz2VnApA @ 2017-06-08 4:00 UTC (permalink / raw)
To: sjg-F7+t8E8rja9g9hUCZPvPmw
Cc: Peter.Chubb-RgbkMxAV74wUb6iz2VnApA,
linux-tegra-u79uwXL29TY76Z2rM5mHXA,
swarren-DDmLM1+adcrQT0dZR+AlfA, u-boot-0aAXYlwwYIKGBzrmiIFOJg
>>>>> "Simon" == Simon Glass <sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org> writes:
Simon> The good news is I found my Jetson-TK1 and I can repeat your
Simon> problem.
Cool. So it's not just me (phew)
>>
>> Tegra124 (Jetson TK1) # mmc rescan
Simon> Why are you running 'mmc rescan'? Is this because the MMC has
Simon> changed?
Any mmc command fails except 'mmc part' and 'mmc list'. 'mmc rescan'
was just one example that should work.
Tegra124 (Jetson TK1) # mmc dev
tegra_mmc_send_cmd_bounced: MMC Timeout
Interrupt status 0x00000001
Interrupt status enable 0xffff003b
Interrupt signal enable 0xffff0002
Present status 0x01fb02f6
mmc_init: -1, time 8042
Tegra124 (Jetson TK1) # mmc info
mmc_init: -1, time 4
--
Dr Peter Chubb Tel: +61 2 9490 5852 http://ts.data61.csiro.au/
Trustworthy Systems Group Data61 (formerly NICTA)
^ permalink raw reply [flat|nested] 13+ messages in thread
* [U-Boot] u-boot-flasher fails with current u-boot
@ 2017-06-08 4:00 ` Peter.Chubb at data61.csiro.au
0 siblings, 0 replies; 13+ messages in thread
From: Peter.Chubb at data61.csiro.au @ 2017-06-08 4:00 UTC (permalink / raw)
To: u-boot
>>>>> "Simon" == Simon Glass <sjg@chromium.org> writes:
Simon> The good news is I found my Jetson-TK1 and I can repeat your
Simon> problem.
Cool. So it's not just me (phew)
>>
>> Tegra124 (Jetson TK1) # mmc rescan
Simon> Why are you running 'mmc rescan'? Is this because the MMC has
Simon> changed?
Any mmc command fails except 'mmc part' and 'mmc list'. 'mmc rescan'
was just one example that should work.
Tegra124 (Jetson TK1) # mmc dev
tegra_mmc_send_cmd_bounced: MMC Timeout
Interrupt status 0x00000001
Interrupt status enable 0xffff003b
Interrupt signal enable 0xffff0002
Present status 0x01fb02f6
mmc_init: -1, time 8042
Tegra124 (Jetson TK1) # mmc info
mmc_init: -1, time 4
--
Dr Peter Chubb Tel: +61 2 9490 5852 http://ts.data61.csiro.au/
Trustworthy Systems Group Data61 (formerly NICTA)
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: u-boot-flasher fails with current u-boot
2017-06-08 3:11 ` [U-Boot] " Simon Glass
@ 2017-06-09 12:28 ` Simon Glass
-1 siblings, 0 replies; 13+ messages in thread
From: Simon Glass @ 2017-06-09 12:28 UTC (permalink / raw)
To: Peter Chubb
Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA, Stephen Warren, U-Boot Mailing List
Hi Peter,
On 7 June 2017 at 21:11, Simon Glass <sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org> wrote:
> Hi Peter,
>
> On 7 June 2017 at 19:12, <Peter.Chubb-RgbkMxAV74wUb6iz2VnApA@public.gmane.org> wrote:
>>>>>>> "Peter" == Peter Chubb <Peter.Chubb-RgbkMxAV74wUb6iz2VnApA@public.gmane.org> writes:
>>>>>>> "Simon" == Simon Glass <sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org> writes:
>>
>> Simon> Oh dear. I cannot find my board but will see if I can repeat
>> Simon> this on a beaver.
>>
>> Peter> If there's any additional logging you'd like me to collect on
>> Peter> the Jetson, let me know.
>>
>> I tried to reproduce this this morning. Today, even trying to exec
>> the U-Boot without flashing fails.
>
> The good news is I found my Jetson-TK1 and I can repeat your problem.
>
>>
>> So,
>> ./tegra-uboot-flasher exec jetson-tk1
>> with a current u-boot gives an inoperative eMMC.
>>
>> In the boot header I see:
>>
>> U-Boot 2017.05-00769-g0e513e788f (Jun 08 2017 - 09:26:27 +1000)
>>
>> TEGRA124
>> Model: NVIDIA Jetson TK1
>> Board: NVIDIA Jetson TK1
>> DRAM: 2 GiB
>> MMC: sdhci@700b0400: 1, sdhci@700b0600: 0
>>
>> Then:
>>
>> Tegra124 (Jetson TK1) # mmc rescan
>
> Why are you running 'mmc rescan'? Is this because the MMC has changed?
>
> This command does not seem to work since it does not re-probe the
> driver. It looks like the driver assumes that the controller is reset
> each time. I'll send a patch which seems to fix it for me.
>
>> tegra_mmc_send_cmd_bounced: MMC Timeout
>> Interrupt status 0x00000001
>> Interrupt status enable 0xffff003b
>> Interrupt signal enable 0xffff0002
>> Present status 0x01fb02f6
>> mmc_init: -1, time 8042
OK thanks for that. Just to close the loop I sent a patch to fix it:
http://patchwork.ozlabs.org/patch/772771/
Regards,
Simon
^ permalink raw reply [flat|nested] 13+ messages in thread
* [U-Boot] u-boot-flasher fails with current u-boot
@ 2017-06-09 12:28 ` Simon Glass
0 siblings, 0 replies; 13+ messages in thread
From: Simon Glass @ 2017-06-09 12:28 UTC (permalink / raw)
To: u-boot
Hi Peter,
On 7 June 2017 at 21:11, Simon Glass <sjg@chromium.org> wrote:
> Hi Peter,
>
> On 7 June 2017 at 19:12, <Peter.Chubb@data61.csiro.au> wrote:
>>>>>>> "Peter" == Peter Chubb <Peter.Chubb@data61.csiro.au> writes:
>>>>>>> "Simon" == Simon Glass <sjg@chromium.org> writes:
>>
>> Simon> Oh dear. I cannot find my board but will see if I can repeat
>> Simon> this on a beaver.
>>
>> Peter> If there's any additional logging you'd like me to collect on
>> Peter> the Jetson, let me know.
>>
>> I tried to reproduce this this morning. Today, even trying to exec
>> the U-Boot without flashing fails.
>
> The good news is I found my Jetson-TK1 and I can repeat your problem.
>
>>
>> So,
>> ./tegra-uboot-flasher exec jetson-tk1
>> with a current u-boot gives an inoperative eMMC.
>>
>> In the boot header I see:
>>
>> U-Boot 2017.05-00769-g0e513e788f (Jun 08 2017 - 09:26:27 +1000)
>>
>> TEGRA124
>> Model: NVIDIA Jetson TK1
>> Board: NVIDIA Jetson TK1
>> DRAM: 2 GiB
>> MMC: sdhci at 700b0400: 1, sdhci at 700b0600: 0
>>
>> Then:
>>
>> Tegra124 (Jetson TK1) # mmc rescan
>
> Why are you running 'mmc rescan'? Is this because the MMC has changed?
>
> This command does not seem to work since it does not re-probe the
> driver. It looks like the driver assumes that the controller is reset
> each time. I'll send a patch which seems to fix it for me.
>
>> tegra_mmc_send_cmd_bounced: MMC Timeout
>> Interrupt status 0x00000001
>> Interrupt status enable 0xffff003b
>> Interrupt signal enable 0xffff0002
>> Present status 0x01fb02f6
>> mmc_init: -1, time 8042
OK thanks for that. Just to close the loop I sent a patch to fix it:
http://patchwork.ozlabs.org/patch/772771/
Regards,
Simon
^ permalink raw reply [flat|nested] 13+ messages in thread
end of thread, other threads:[~2017-06-09 12:28 UTC | newest]
Thread overview: 13+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-06-06 23:36 u-boot-flasher fails with current u-boot Peter.Chubb-RgbkMxAV74wUb6iz2VnApA
[not found] ` <84tw3sk7sq.wl-Peter.Chubb-RgbkMxAV74wUb6iz2VnApA@public.gmane.org>
2017-06-07 3:13 ` Simon Glass
2017-06-07 3:13 ` [U-Boot] " Simon Glass
2017-06-07 4:01 ` Peter.Chubb
2017-06-07 4:01 ` [U-Boot] " Peter.Chubb at data61.csiro.au
2017-06-08 1:12 ` Peter.Chubb
2017-06-08 1:12 ` [U-Boot] " Peter.Chubb at data61.csiro.au
[not found] ` <84vao7uvsz.wl-Peter.Chubb-RgbkMxAV74wUb6iz2VnApA@public.gmane.org>
2017-06-08 3:11 ` Simon Glass
2017-06-08 3:11 ` [U-Boot] " Simon Glass
[not found] ` <CAPnjgZ3GhGGq8SrtXNOQyh5V7Xm2X_pfKcrrbHkyVNXcfvWCjA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-06-08 4:00 ` Peter.Chubb-RgbkMxAV74wUb6iz2VnApA
2017-06-08 4:00 ` [U-Boot] " Peter.Chubb at data61.csiro.au
2017-06-09 12:28 ` Simon Glass
2017-06-09 12:28 ` [U-Boot] " Simon Glass
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.