在 2018-02-08 08:37,André Przywara 写道:
On 07/02/18 19:35, Icenowy Zheng wrote:
Hi,
Some Allwinner SoCs can use 3GiB DRAM (part of 4GiB or larger module).
As the common get_ram_size function cannot detect non-pow-of-2 memory,
add special detect code into the DRAM size code in main U-Boot.
On Thu, Feb 8, 2018 at 11:54 AM, Stefan Mavrodiev
wrote:
> On 02/07/2018 07:19 PM, Maxime Ripard wrote:
>>
>> On Wed, Feb 07, 2018 at 12:55:54PM +0530, Jagan Teki wrote:
+ {
+ pinctrl-names = "default";
+ pinctrl-0 =
在 2018-02-08 08:37,André Przywara 写道:
On 07/02/18 19:35, Icenowy Zheng wrote:
Hi,
As 4GiB capacity is above the range of 32-bit unsigned integer, raise
the return type of sunxi_dram_init() to unsigned long long, thus it
can
hold 4GiB capacity (or maybe more on A80).
Some controllers that
在 2018-02-08 10:14,Chen-Yu Tsai 写道:
On Thu, Feb 8, 2018 at 8:35 AM, André Przywara
wrote:
On 07/02/18 19:35, Icenowy Zheng wrote:
Allwinner 64-bit SoCs can use 4GiB DRAM chip, however their memory
map
has only allocated 3GiB for DRAM, so only 3GiB of the DRAM is
From: Richard Weinberger
Fixes a bug found on thuban boards, which were for 2 years in
a long-term test with varying temperatures. They showed
problems in u-boot when attaching the ubi partition:
U-Boot# run flash_self_test
Booting from nand
set A...
UBI: attaching mtd1 to ubi0
Hi Michal,
On Wednesday 07 February 2018 01:14 PM, Michal Simek wrote:
> Hi Lokesh,
>
> On 6.2.2018 13:28, Michal Simek wrote:
>> There is no reason to unconditially select network commands as distro
>> defaults without networking enable.
>>
>> Signed-off-by: Michal Simek
On Thursday 08 February 2018 12:11 AM, Sam Protsenko wrote:
> From DFU_ALT_INFO_EMMC (include/environment/ti/dfu.h) we can see that
> rootfs will be flashed to second partition on eMMC. But at the moment we
> have only one partition in $partitions environment variable. Let's add
> "bootloader"
On Mon, Feb 05, 2018 at 11:31:42AM +0100, Mark Kettenis wrote:
> > Date: Mon, 5 Feb 2018 21:06:59 +1100
> > From: Jonathan Gray
> >
> > > > booting sd0a:/bsd: open sd0a:/bsd: Device not configured
> > > > failed(6). will try /bsd
> > >
> > > How do you find out that it's sd0a
On 07.02.2018 22:18, York Sun wrote:
On 02/07/2018 12:45 PM, Goldschmidt Simon wrote:
On 02/07/2018 21:18, York Sun wrote:
On 02/07/2018 12:43 AM, Maxime Ripard wrote:
Hi,
On Tue, Jan 30, 2018 at 11:02:49PM +, York Sun wrote:
On 01/30/2018 12:16 PM, York Sun wrote:
On 01/30/2018 11:40
I'm gettin overrun on the raspberry pi.
Which ethernet drived does it use? I need to determine if it
uses CONFIG_SYS_RX_ETH_BUFFER" from net.h and the "net_rx_packets"
buffer pool defined in net/net.c
grep suggests it is not using net_rx_packets.
Here's a list of a grep of the u-boot source
On Thu, Feb 8, 2018 at 8:35 AM, André Przywara wrote:
> On 07/02/18 19:35, Icenowy Zheng wrote:
>> Allwinner 64-bit SoCs can use 4GiB DRAM chip, however their memory map
>> has only allocated 3GiB for DRAM, so only 3GiB of the DRAM is
>> accessible.
>>
>> Add a Kconfig
2018-02-02 16:20 GMT+08:00 陳建志 :
>> Actually I have checked with checkpatch.pl and cleaned most before
>> sending patchs.
>> But it seem still left some, I will keep fixing them.
>>
>> Thanks for Tom and Wolfgang's help.
>>
>> Rick
>>
>> 2018-01-15 21:52 GMT+08:00 Tom Rini
On 07/02/18 19:35, Icenowy Zheng wrote:
Hi,
> As 4GiB capacity is above the range of 32-bit unsigned integer, raise
> the return type of sunxi_dram_init() to unsigned long long, thus it can
> hold 4GiB capacity (or maybe more on A80).
> Some controllers that are possible to use 4GiB+ memory
On 07/02/18 19:35, Icenowy Zheng wrote:
Hi,
> Some Allwinner SoCs can use 3GiB DRAM (part of 4GiB or larger module).
>
> As the common get_ram_size function cannot detect non-pow-of-2 memory,
> add special detect code into the DRAM size code in main U-Boot.
The original get_ram_size() function
On 07/02/18 19:35, Icenowy Zheng wrote:
> Allwinner 64-bit SoCs can use 4GiB DRAM chip, however their memory map
> has only allocated 3GiB for DRAM, so only 3GiB of the DRAM is
> accessible.
>
> Add a Kconfig option for the maximum accessible DRAM.
That looks fine to me, but have you checked
On 07/02/18 19:35, Icenowy Zheng wrote:
Hi,
> All Allwinner 64-bit SoCs now are known to be able to access 3GiB of
> external DRAM, however the size of DRAM part in the MMU translation
> table is still 2GiB.
>
> Change the size of DRAM part in MMU table to 3GiB.
This is needed for the (new)
xtensa toolchains are core-specific, so give full toolchain name and
download corresponding prebuilt toolchain from the github release.
Signed-off-by: Max Filippov
---
.travis.yml | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/.travis.yml
This allows running tests on emulated KC705 board with DC233C xtensa
core. It expects to find conf.xtfpga_qemu in the uboot-test-hooks.
Signed-off-by: Max Filippov
---
.travis.yml | 7 +++
1 file changed, 7 insertions(+)
diff --git a/.travis.yml b/.travis.yml
index
Remove CONFIG_BOOT_RETRY_TIME as it doesn't do much good and enable
CONFIG_HUSH_PARSER in xtfpga_defconfig.
Signed-off-by: Max Filippov
---
Changes v1->v2:
- new patch
configs/xtfpga_defconfig | 1 +
include/configs/xtfpga.h | 2 --
2 files changed, 1 insertion(+), 2
Hi Tom,
the following patches allow building and running U-Boot for xtensa in
Travis CI.
The test results are the following:
73 passed, 31 skipped, 1 deselected
Changes v1->v2:
- add patch that enables hush parser for xtfpga_defconfig. The size
increase is tolerable and now there are no
On 02/04/2018 05:40 AM, Simon Glass wrote:
> Hi York,
>
> On 24 January 2018 at 12:04, York Sun wrote:
>> For DDR4, command/address delay in mode registers and parity latency
>> in timing config register are only needed for UDIMMs, but not RDIMMs.
>> Add additional register
Commit 8a3a7e2270b3 ("env: Pass additional parameters to the env
lookup function") dropped the default action if driver doesn't have
get_char() defined. This causes failure to get environmental
variables from NOR flash. Add back this default action for now.
Signed-off-by: York Sun
Commit 7d714a24d725 ("env: Support multiple environments") added
static variable env_load_location. When saving environmental
variables, this variable is presumed to have the value set before.
In case the value was set before relocation and U-Boot runs from a
NOR flash, this variable wasn't
xtensa toolchains are core-specific, so give full toolchain name and
download corresponding prebuilt toolchain from the github release.
Signed-off-by: Max Filippov
---
.travis.yml | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/.travis.yml
This allows running tests on emulated KC705 board with DC233C xtensa
core. It expects to find conf.xtfpga_qemu in the uboot-test-hooks.
Signed-off-by: Max Filippov
---
.travis.yml | 7 +++
1 file changed, 7 insertions(+)
diff --git a/.travis.yml b/.travis.yml
index
Hi Tom,
the following two patches allow building and running U-Boot for xtensa in
Travis CI.
The test results are the following:
4 failed, 14 passed, 86 skipped, 1 deselected
Failures are in the environment manipulation tests and skipped tests are
mostly the hush ones. I guess that's because
On 02/07/2018 12:45 PM, Goldschmidt Simon wrote:
> On 02/07/2018 21:18, York Sun wrote:
>> On 02/07/2018 12:43 AM, Maxime Ripard wrote:
>>> Hi,
>>>
>>> On Tue, Jan 30, 2018 at 11:02:49PM +, York Sun wrote:
On 01/30/2018 12:16 PM, York Sun wrote:
> On 01/30/2018 11:40 AM, York Sun
The test checks all block image transfer operations of the graphical output
protocol. An animated submarine is shown.
To run the test:
setenv efi_selftest bock image transfer
bootefi selftest
Signed-off-by: Heinrich Schuchardt
---
v2
correct commit message
---
With the patch all block image transfer operations of the
EFI_GRAPHICS_OUTPUT_PROTOCOL are supported.
Signed-off-by: Heinrich Schuchardt
---
v2
no change
---
include/efi_api.h| 10 ++-
lib/efi_loader/efi_gop.c | 158
The patch series implements the missing block image transfer operations of
the graphical output protocol
A unit test is provided.
---
v2
correct commit message
---
Heinrich Schuchardt (2):
efi_loader: implement missing bit blit operations in gop
efi_selftest: test gop bitblt
The test dr
Signed-off-by: Heinrich Schuchardt
---
lib/efi_selftest/Makefile | 1 +
lib/efi_selftest/efi_selftest_bitblt.c | 311 +
2 files changed, 312 insertions(+)
create mode 100644 lib/efi_selftest/efi_selftest_bitblt.c
With the patch all block image transfer operations of the
EFI_GRAPHICS_OUTPUT_PROTOCOL are supported.
Signed-off-by: Heinrich Schuchardt
---
include/efi_api.h| 10 ++-
lib/efi_loader/efi_gop.c | 158 ---
2 files changed,
The patch series implements the missing block image transfer operations of
the graphical output protocol
A unit test is provided.
Heinrich Schuchardt (2):
efi_loader: implement missing bit blit operations in gop
efi_selftest: test gop bitblt
include/efi_api.h | 10 +-
On 02/07/2018 21:18, York Sun wrote:
> On 02/07/2018 12:43 AM, Maxime Ripard wrote:
>> Hi,
>>
>> On Tue, Jan 30, 2018 at 11:02:49PM +, York Sun wrote:
>>> On 01/30/2018 12:16 PM, York Sun wrote:
On 01/30/2018 11:40 AM, York Sun wrote:
> On 01/30/2018 12:19 AM, Simon Goldschmidt wrote:
On 02/07/2018 12:43 AM, Maxime Ripard wrote:
> Hi,
>
> On Tue, Jan 30, 2018 at 11:02:49PM +, York Sun wrote:
>> On 01/30/2018 12:16 PM, York Sun wrote:
>>> On 01/30/2018 11:40 AM, York Sun wrote:
On 01/30/2018 12:19 AM, Simon Goldschmidt wrote:
> On 23.01.2018 21:16, Maxime Ripard
When saving the environment on a platform which has DMA alignment
larger than the natural alignment, env_fat_save triggers a debug
message in file_fat_write:
Saving Environment to FAT... writing uboot.env
FAT: Misaligned buffer address (9df1c8e0)
OK
Signed-off-by: Alex Kiernan
Hi,
On 02/07/2018 07:50 AM, patrice.chot...@st.com wrote:
> From: Patrice Chotard
>
> For STM32F4 and F7 SoCx family, a specific stm32.h file exists.
> Some common defines are duplicated or even unused in each of
> these stm32.h.
>
> Factorize all common definition in
Hi Patrice,
On 02/07/2018 07:50 AM, patrice.chot...@st.com wrote:
> From: Patrice Chotard
>
> Instead to have 3 identical gpio.h for all STM32 SoCs,
> migrate them in one file in include/asm.
good move to consolidate these headers.
One comment below.
>
>
To make this driver easier to be reused, dual-license DDR driver.
Signed-off-by: York Sun
CC: Simon Glass
CC: Tom Rini
CC: Heinrich Schuchardt
CC: Thomas Schaefer
CC: Masahiro Yamada
Some Allwinner SoCs can use 3GiB DRAM (part of 4GiB or larger module).
As the common get_ram_size function cannot detect non-pow-of-2 memory,
add special detect code into the DRAM size code in main U-Boot.
Signed-off-by: Icenowy Zheng
---
board/sunxi/board.c| 23
On newer Allwinner SoCs with the BROM start at 0x0 and the DRAM space at
<0x4000 0xc000>, some parts of DRAM will be inaccessible when
4GiB module is used.
Restrict the ram_size written to global_data in SPL.
Signed-off-by: Icenowy Zheng
---
board/sunxi/board.c | 13
As 4GiB capacity is above the range of 32-bit unsigned integer, raise
the return type of sunxi_dram_init() to unsigned long long, thus it can
hold 4GiB capacity (or maybe more on A80).
Some controllers that are possible to use 4GiB+ memory module are
also changed to calculate its memory capacity
All Allwinner 64-bit SoCs now are known to be able to access 3GiB of
external DRAM, however the size of DRAM part in the MMU translation
table is still 2GiB.
Change the size of DRAM part in MMU table to 3GiB.
Signed-off-by: Icenowy Zheng
---
arch/arm/mach-sunxi/board.c | 2 +-
Allwinner 64-bit SoCs can use 4GiB DRAM chip, however their memory map
has only allocated 3GiB for DRAM, so only 3GiB of the DRAM is
accessible.
Add a Kconfig option for the maximum accessible DRAM.
For A80 it should be a much higher value (8GiB), but as I have no A80
device to test and
Allwinner 64-bit SoCs have allocated 3GiB space in the memory map for
DRAM. If memory bigger than 3GiB is installed (as memory usually come as
pow of 2 and they are not known to support 3GiB LPDDR3 modules, it means
4GiB memory is installed), the whole 3GiB space can be all used.
However, in many
1;5002;0c
On Wed, Feb 07, 2018 at 09:25:55AM +0100, Simon Goldschmidt wrote:
> On 07.02.2018 09:19, Maxime Ripard wrote:
> > On Tue, Feb 06, 2018 at 09:09:07AM +0100, Simon Goldschmidt wrote:
> > > On 23.01.2018 21:16, Maxime Ripard wrote:
> > > > Now that we have everything in place to support
From DFU_ALT_INFO_EMMC (include/environment/ti/dfu.h) we can see that
rootfs will be flashed to second partition on eMMC. But at the moment we
have only one partition in $partitions environment variable. Let's add
"bootloader" partition prior to "rootfs", so that DFU works correctly.
This also
On Wed, Feb 07, 2018 at 08:45:46AM +, Joakim Tjernlund wrote:
> On Thu, 1970-01-01 at 00:00 +, Simon Goldschmidt wrote:
> > CAUTION: This email originated from outside of the organization. Do not
> > click links or open attachments unless you recognize the sender and know
> > the content
On Wed, Feb 07, 2018 at 12:55:54PM +0530, Jagan Teki wrote:
> > + {
> > + pinctrl-names = "default";
> > + pinctrl-0 = <_pins_b>, <_cs0_pins_b>;
> > + status = "okay";
> > +
> > + flash: w25q128@0 {
>
> Was it sync from Linux?
> >>>
> >>>
Hi Jagan,
On 07.02.2018 17:03, Jagan Teki wrote:
> Writing/updating boot image in nand device is not
> straight forward in i.MX6 platform and it requires
> boot control block(BCB) to be configured.
>
> It becomes difficult to use uboot 'nand' command to
> write BCB since it requires platform
From: Patrick Delaunay
This patch adds "st,pin-ckin" support to activate sdmmc_ckin feature.
When using an external driver (a voltage switch transceiver),
it's advised to select SDMMC_CKIN feedback clock input to sample
the received data.
Signed-off-by: Patrick Delaunay
From: Patrice Chotard
This series adds the following stm32_sdmmc2 driver update :
_ Enable hardware flow control
_ Add support for st,pin-ckinsdmmc_ckin to select "ckin" clock input
to sample received data.
Patrick Delaunay (2):
mmc: stm32: sdmmc2: add hardware flow
From: Patrick Delaunay
The hardware flow control functionality is used to avoid
FIFO underrun (TX mode) and overrun (RX mode) errors.
The behavior is to stop SDMMC_CK during data transfer and
freeze the SDMMC state machines.
Signed-off-by: Patrick Delaunay
Add Kconfig entry for CMD_NANDBCB, and default y on i.MX6
platform with NAND_MXS defined.
Signed-off-by: Jagan Teki
---
Changes for v3:
- Fixed Typo 'seprate'
Changes for v2:
- New patch
arch/arm/mach-imx/Kconfig | 11 +++
1 file changed, 11 insertions(+)
Writing/updating boot image in nand device is not
straight forward in i.MX6 platform and it requires
boot control block(BCB) to be configured.
It becomes difficult to use uboot 'nand' command to
write BCB since it requires platform specific attributes
need to be taken care of.
It is even
From: Patrice Chotard
Removes unused .h files in arch/arm/include/asm/arch-stm32xx
Factorize and clean some .h files to avoid to duplicate defines in
separate .h files
Patrice Chotard (5):
arch-stm32f4: Remove fmc.h file
arch-stm32: Move gpio.h for STM32 SoCs in
From: Patrice Chotard
fmc.h file is no more used, remove it.
All FMC related defines are declared in drivers/ram/stm32_sdram.c
which is common to all STM32 SoCs.
Signed-off-by: Patrice Chotard
---
arch/arm/include/asm/arch-stm32f4/fmc.h | 75
From: Patrice Chotard
Remove arch/arm/include/asm/arch-stm32fx/stm32_periph.h
as all defines or enums are no more used.
Signed-off-by: Patrice Chotard
---
arch/arm/include/asm/arch-stm32f4/stm32_periph.h | 38
From: Patrice Chotard
Remove all unused defines
Signed-off-by: Patrice Chotard
---
arch/arm/include/asm/arch-stm32f7/syscfg.h | 9 -
1 file changed, 9 deletions(-)
diff --git a/arch/arm/include/asm/arch-stm32f7/syscfg.h
From: Patrice Chotard
For STM32F4 and F7 SoCx family, a specific stm32.h file exists.
Some common defines are duplicated or even unused in each of
these stm32.h.
Factorize all common definition in arch/arm/include/asm/stm32f.h and keep
specific definitions in each
From: Patrice Chotard
Instead to have 3 identical gpio.h for all STM32 SoCs,
migrate them in one file in include/asm.
Signed-off-by: Patrice Chotard
---
arch/arm/include/asm/arch-stm32f4/gpio.h | 146 +--
Hi Jagan,
On Tue, Feb 6, 2018 at 5:41 PM, Jagan Teki wrote:
> ---
> Changes for v2:
> - Fixed commit message notes
> - Updated proper commit message
> - Update doc/README.imx6 with NAND boot details
> - Fixed long length variable names.
> - Fixed Gigantic variable
On 02/07/2018 09:25 AM, Jagan Teki wrote:
On Wed, Feb 7, 2018 at 12:35 PM, Stefan Mavrodiev
wrote:
On 02/07/2018 08:39 AM, Jagan Teki wrote:
On Wed, Feb 7, 2018 at 12:00 PM, Stefan Mavrodiev
wrote:
On 02/06/2018 06:48 PM, Jagan Teki
This commit broke the command setexpr.
http://git.denx.de/?p=u-boot.git;a=commit;h=6f62d7c4f7a2242a76e19b09dccca6f68776e788
setexpr uses cmd_get_data_size(). If none of I2C, ITEST or PCI is
chosen, setexpr will fail to be built.
--- include/command.h
+++ include/command.h
@@ -80,13 +80,14 @@
*
On 02/07/2018 08:39 AM, Jagan Teki wrote:
On Wed, Feb 7, 2018 at 12:00 PM, Stefan Mavrodiev
wrote:
On 02/06/2018 06:48 PM, Jagan Teki wrote:
On Tue, Feb 6, 2018 at 6:44 PM, Stefan Mavrodiev
wrote:
Driver testing is done with
On 02/06/2018 06:48 PM, Jagan Teki wrote:
On Tue, Feb 6, 2018 at 6:44 PM, Stefan Mavrodiev wrote:
Driver testing is done with A20-OLinuXino-Lime2. Testing
requirements are:
- Exposing spi0 alternative pins in the dts file
- Add alias node, enabling driver probing
-
Hi Jagan,
> -Original Message-
> From: Jagan Teki [mailto:ja...@amarulasolutions.com]
> Sent: Tuesday, January 23, 2018 10:41 PM
> To: Siva Durga Prasad Paladugu
> Cc: U-Boot-Denx ; Siva Durga Prasad Paladugu
>
> Subject:
On Wed, Feb 7, 2018 at 2:54 PM, Stefan Mavrodiev
wrote:
> On 02/07/2018 09:25 AM, Jagan Teki wrote:
>>
>> On Wed, Feb 7, 2018 at 12:35 PM, Stefan Mavrodiev
>> wrote:
>>>
>>> On 02/07/2018 08:39 AM, Jagan Teki wrote:
On Wed, Feb 7,
From: Patrice Chotard
Use available DM stm32_timer driver instead of dedicated
mach-stm32/stm32fx/timer.c.
Remove all defines or files previously used for timer usage in
arch/arm/include/asm/arch-stm32fx and in arch/arm/mach-stm32/stm32fx
Enable DM STM32_TIMER for
From: Patrice Chotard
d1cfgr register was used to calculate the domain 3
prescaler value instead of d3cfgr.
Signed-off-by: Patrice Chotard
---
drivers/clk/clk_stm32h7.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git
From: Patrice Chotard
Add missing timer node to enable timer5 for STM32F7 SoCs family
Signed-off-by: Patrice Chotard
---
arch/arm/dts/stm32f7-u-boot.dtsi | 8
arch/arm/dts/stm32f746.dtsi | 7 +++
2 files changed, 15
From: Patrice Chotard
For timer clock, an additional prescaler is used which
was not taken into account previously.
Signed-off-by: Patrice Chotard
---
drivers/clk/clk_stm32h7.c | 102 --
1 file
From: Patrice Chotard
For timer clock, an additionnal prescaler is used which was
not taken into account previously.
Signed-off-by: Patrice Chotard
---
drivers/clk/clk_stm32f.c | 116 ---
From: Patrice Chotard
Add DM timer support for all STM32F7/F4/H7 SoCs family.
Clock driver for STM32F4/F7 and H7 need to updated to get timer clock rate.
Remove all defines or files previously used for timer usage in
arch/arm/include/asm/arch-stm32fx and in
From: Patrice Chotard
This timer driver is using GPT Timer (General Purpose Timer)
available on all STM32 SOCs family.
This driver can be used on STM32F4/F7 and H7 SoCs family
Signed-off-by: Patrice Chotard
---
drivers/timer/Kconfig | 7
> -Original Message-
> From: York Sun
> Sent: Tuesday, February 06, 2018 10:38 PM
> To: Rajat Srivastava ; u-boot@lists.denx.de
> Subject: Re: [PATCH] ls1088a: qspi: Enable XIP mode above 16 MB addresses
>
> On 02/06/2018 02:59 AM, Rajat Srivastava wrote:
> >
>
Dear Faiz Abbas,
In message <1517564875-10237-1-git-send-email-faiz_ab...@ti.com> you wrote:
> When booting from a non-MMC device, the MMC sub-system may not be
> initialized when the environment is first accessed.
> We need to make sure that the MMC sub-system is ready in even a non-MMC
> boot
On Thu, 1970-01-01 at 00:00 +, Simon Goldschmidt wrote:
> CAUTION: This email originated from outside of the organization. Do not click
> links or open attachments unless you recognize the sender and know the
> content is safe.
>
>
> On 06.02.2018 09:20, Joakim Tjernlund wrote:
> > On Thu,
Hi,
On Tue, Jan 30, 2018 at 11:02:49PM +, York Sun wrote:
> On 01/30/2018 12:16 PM, York Sun wrote:
> > On 01/30/2018 11:40 AM, York Sun wrote:
> >> On 01/30/2018 12:19 AM, Simon Goldschmidt wrote:
> >>> On 23.01.2018 21:16, Maxime Ripard wrote:
> Now that we have everything in place to
On Thu, 1970-01-01 at 00:00 +, Maxime Ripard wrote:
> Hi,
>
> On Tue, Feb 06, 2018 at 08:20:49AM +, Joakim Tjernlund wrote:
> > On Thu, 1970-01-01 at 00:00 +, Simon Goldschmidt wrote:
> >
> > .
> > > > Reviewed-by: Andre Przywara
> > > > Reviewed-by:
On 06.02.2018 09:20, Joakim Tjernlund wrote:
On Thu, 1970-01-01 at 00:00 +, Simon Goldschmidt wrote:
.
Reviewed-by: Andre Przywara
Reviewed-by: Simon Glass
Signed-off-by: Maxime Ripard
---
env/env.c | 80
On Mon, Feb 05, 2018 at 04:30:50PM +, York Sun wrote:
> On 02/05/2018 05:44 AM, Maxime Ripard wrote:
> > Hi York,
> >
> > On Fri, Feb 02, 2018 at 08:04:12PM +, York Sun wrote:
> >> On 02/02/2018 10:51 AM, Maxime Ripard wrote:
> > This patch looks correct. But it doesn't fix NOR flash.
On 07.02.2018 09:19, Maxime Ripard wrote:
On Tue, Feb 06, 2018 at 09:09:07AM +0100, Simon Goldschmidt wrote:
On 23.01.2018 21:16, Maxime Ripard wrote:
Now that we have everything in place to support multiple environment, let's
make sure the current code can use it.
I get more build errors
On Tue, Feb 06, 2018 at 09:09:07AM +0100, Simon Goldschmidt wrote:
> On 23.01.2018 21:16, Maxime Ripard wrote:
> > Now that we have everything in place to support multiple environment, let's
> > make sure the current code can use it.
>
> I get more build errors testing this feature: there's a
Hi,
On Tue, Feb 06, 2018 at 08:20:49AM +, Joakim Tjernlund wrote:
> On Thu, 1970-01-01 at 00:00 +, Simon Goldschmidt wrote:
>
> .
> > > Reviewed-by: Andre Przywara
> > > Reviewed-by: Simon Glass
> > > Signed-off-by: Maxime Ripard
85 matches
Mail list logo