SabreLite board.
Signed-off-by: Denis Pynkin
---
configs/mx6qsabrelite_defconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configs/mx6qsabrelite_defconfig b/configs/mx6qsabrelite_defconfig
index 008fcfe04c..6e7193e411 100644
--- a/configs/mx6qsabrelite_defconfig
+++ b
shed onto SPI it overlaps with the stored environment.
>>> This leads to U-Boot corruption in case of saving environment onto
>>> SPI and non-bootable SabreLite board.
>>>
>>> Signed-off-by: Denis Pynkin
>>
>> Reviewed-by: Fabio Estevam
>>
&
14.09.2020 17:11, Tom Rini wrote:
> On Mon, Sep 14, 2020 at 09:29:18AM -0400, Tom Rini wrote:
>> On Mon, Sep 14, 2020 at 04:20:20PM +0300, Denis Pynkin wrote:
>>> 14.09.2020 15:33, Tom Rini wroteт:
>>>> On Mon, Sep 14, 2020 at 08:03:33AM -0300, Fabio Estevam wro
14.09.2020 21:50, Tom Rini wrote:
> On Mon, Sep 14, 2020 at 08:08:48PM +0300, Denis Pynkin wrote:
>> 14.09.2020 17:11, Tom Rini wrote:
>>> On Mon, Sep 14, 2020 at 09:29:18AM -0400, Tom Rini wrote:
>>>> On Mon, Sep 14, 2020 at 04:20:20PM +0300, Denis Pynkin wrote:
&g
(with enabled option `CONFIG_ENV_IS_IN_SPI_FLASH`). In that case the
U-Boot binary flashed on SPI NOR is also corrupted after environment
saving with the original 0x6 offset.
Signed-off-by: Denis Pynkin
---
configs/mx6qsabrelite_defconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion
hout packed
attribute.
Reviewed-by: Yauheni Kaliuta
Signed-off-by: Denis Pynkin
---
include/net.h | 14 +++---
net/bootp.h | 2 +-
net/dns.h | 2 +-
net/nfs.h | 2 +-
net/sntp.h| 2 +-
5 files changed, 11 insertions(+), 11 deletions(-)
diff --git a/include/net.h b/inclu
28.07.2017 00:26, Joe Hershberger wrote:
PXE boot is broken with GCC 7.1 due option '-fstore-merging' enabled
by default for '-O2':
So, what I've been wondering, and others have poked me about (who can
chime in if they like), how is the kernel not also tripping over this?
Great question.
28.07.2017 00:26, Joe Hershberger wrote:
PXE boot is broken with GCC 7.1 due option '-fstore-merging' enabled
by default for '-O2':
So, what I've been wondering, and others have poked me about (who can
chime in if they like), how is the kernel not also tripping over this?
Great question.
insertions(+), 136 deletions(-)
Tested-by: Denis Pynkin
Tested with SabreLite board:
mmc0 is current device
Scanning mmc 0:1...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
318 bytes read in 47 ms (5.9 KiB/s)
1: Linux 4.14.0-0.bpo.2-armmp
Retrieving file: /initrd.img
9 matches
Mail list logo