When trying to load an image from a non-existent USB key, U-Boot v2017.11
crashes on my x86 platform:
=> load usb 0:1 0300 abc
General Protection
EIP: 0010:[<7b59030d>] EFLAGS: 00010286
Original EIP :[]
...
This used to work in v2017.09. Testing has shown, that this bug was
introduced with
From: Ludovic Desroches
Add a header for SAMA5D2 SMC since it's not compatible with
SAMA5D3 one.
Signed-off-by: Ludovic Desroches
[wenyou: fix the wrong base address of the SMC register]
Signed-off-by: Wenyou Yang
From: Ludovic Desroches
Add the SAMA5D2 PTC EK board and remove the SAMA5D2 PTC ENGI board
which was a prototype.
Signed-off-by: Ludovic Desroches
Signed-off-by: Wenyou Yang
---
Add the new board SAMA5D2 PTC EK and remove the SAMA5D2 PTC ENGI
board which was a prototype.
Ludovic Desroches (2):
ARM: at91: add sama5d2 smc header
board: atmel: add sama5d2_ptc_ek board
arch/arm/dts/Makefile | 3 +
arch/arm/dts/at91-sama5d2_ptc_ek.dts
From: Ludovic Desroches
The capabilities have default values which doesn't reflect the reality
when it concerns the base clock and the mul value. Use a fixe rate
for the gck. 240 MHz is an arbitrary choice, it is a multiple of the
maximum SD clock frequency
From: Ludovic Desroches
To get the same behavior as the Linux driver, instead of selecting
the closest inferior rate, select the closest inferior or superior
rate
Signed-off-by: Ludovic Desroches
Signed-off-by: Wenyou Yang
Differentiate the generic clock source selection value from the parent
clock index to fix the incorrect assignment of the generic clock
source selection.
Signed-off-by: Wenyou Yang
---
drivers/clk/at91/clk-generated.c | 14 --
1 file changed, 8
The purpose of the patch set is to fix the the incorrect assignment
of the generic clock source selection, and to align to the Linux
kernel driver, instead of selecting the closest inferior rate, select
the absolute closest rate.
Ludovic Desroches (1):
clk: at91: clk-generated: select
This reverts commit b63b46313ed29e9b0c36b3d6b9407f6eade40c8f.
This commit changed cadence_qspi_apb to use bouncebuf.c, which invalidates
the data cache after reading. This is meant for dma transfers only and
breaks the cadence_qspi driver which copies via cpu only: data that is
copied by the cpu
What the AT91_UTMI depends on SPL_DM isn't right. AT91_UTMI is not
only used in SPL, also in other place, even if SPL_DM isn't enabled.
Signed-off-by: Wenyou Yang
---
drivers/clk/at91/Kconfig | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git
> Jason Rush wrote:
> Cleanup unused #define values that are read from the DT.
> ---
> Changes for v4:
>- Rebased
Reviewed-by: Simon Goldschmidt
Tested on a socfpga-cyclonev board:
Tested-by: Simon Goldschmidt
Best
> Jason Rush wrote:
> Adopt the Linux DT bindings and clean-up duplicate
> and unused values.
> ---
> Changes for v4:
>- Rebased
Reviewed-by: Simon Goldschmidt
>
> arch/arm/dts/keystone-k2g-evm.dts | 8
>
> Jason Rush wrote:
> Adopt the Linux DT bindings. This also fixes an issue
> with the indaddrtrig register on the Cadence QSPI
> device being programmed with the wrong value for the
> socfpga arch.
> ---
> Changes for v4:
>- Rebased
>
Reviewed-by: Simon Goldschmidt
This patch removes the inclusion of the libgcc math functions and
replaces them by functions coded in C, taken from the coreboot
project. This makes U-Boot building more independent from the toolchain
installed / available on the build system.
The code taken from coreboot is authored from Vadim
On 17.11.2017 02:29, Anatolij Gustschin wrote:
Adjust VGA rom address to 0xfffb so that u-boot.rom image
can be built again.
Signed-off-by: Anatolij Gustschin
---
configs/conga-qeval20-qa3-e3845-internal-uart_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git
On Thu, Nov 16, 2017 at 02:09:40PM +0100, Stefan Roese wrote:
> Hi Tom,
>
> please pull the following pending patches for MVEBU.
>
> Thanks,
> Stefan
>
>
> The following changes since commit c253573f3e269fd9a24ee6684d87dd91106018a5:
>
> Prepare v2017.11 (2017-11-13 20:08:06 -0500)
>
> are
On Wed, Nov 15, 2017 at 10:29:37PM +, York Sun wrote:
> Tom,
>
> Passed compiling on travis,
> https://travis-ci.org/yorksun/u-boot/builds/302640283, the following
> changes since commit c253573f3e269fd9a24ee6684d87dd91106018a5:
>
> Prepare v2017.11 (2017-11-13 20:08:06 -0500)
>
> are
Adjust VGA rom address to 0xfffb so that u-boot.rom image
can be built again.
Signed-off-by: Anatolij Gustschin
---
configs/conga-qeval20-qa3-e3845-internal-uart_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git
Generate u-boot-verified.rom image containing Secure Boot Manifest
when secure boot option is enabled.
Signed-off-by: Anatolij Gustschin
---
NOTE: This patch applies on top of binman changes in binman-working
branch in git://git.denx.de/u-boot-dm.git
Changes in v3:
- New patch.
From: Markus Valentin
Add short summary describing preparations for enabling secure boot
feature on Bay Trail SoC.
Signed-off-by: Markus Valentin
Signed-off-by: Anatolij Gustschin
---
Changes in v3:
- add commit message
- use 'U-Boot' consistently
Prepare binman for adding image signing support after final image
build stage. Custom image signing functionality for SoCs supporting
verified boot can be added, e.g. like in the subsequent patch with
signing functionality for Bay Trail SoC images.
Read 'sign' and 'socname' properties in /binman
From: Markus Valentin
Add board config file for conga-qeval20-qa3-e3845 target with enabled
secure boot option.
Signed-off-by: Markus Valentin
Signed-off-by: Anatolij Gustschin
Reviewed-by: Simon Glass
---
Changes in v3:
- add
From: Markus Valentin
Introduce a new Kconfig variable for secure boot on Bay Trail based
platforms. If this variable is set, the build process tries to use
fsp-sb.bin instead of fsp.bin (-sb is the secure boot enabled FSP).
Also check the two FSP headers against each other and
From: Markus Valentin
Introduce functions that check the integrity of U-Boot by utilising
the hashes stored in the OEM-data block in Secure Boot Manifest.
The verification functions get called in fsp_init()
Signed-off-by: Markus Valentin
Signed-off-by: Anatolij
This patch series makes the hardware mechanisms for verified boot on
Bay Trail based platforms usable in/for U-Boot. The series brings in
binman extension which allows to easily create and assemble a Secure
Boot Manifest in the U-Boot ROM image. The manifest gets utilized by
the Trusted Execution
Hello Ledislav,
While I see no reason U-Boot list was cc'ed on this patch, your attitude
is almost perfect example how _not_ to do opensource development.
As an occasional reader, it seems that this is a rather harsh, I am sure
Marex
and Otavio can handle it themselves..
Regards,
Jeroen
On Thu, Nov 16, 2017 at 04:34:51PM -0200, Otavio Salvador wrote:
> On Thu, Nov 16, 2017 at 4:21 PM, Marek Vasut wrote:
> > On 11/16/2017 01:02 PM, Otavio Salvador wrote:
> >> On Thu, Nov 16, 2017 at 6:12 AM, Marek Vasut wrote:
> >>> On 11/15/2017 05:47 PM, Stefan
On Thu, Nov 16, 2017 at 4:21 PM, Marek Vasut wrote:
> On 11/16/2017 01:02 PM, Otavio Salvador wrote:
>> On Thu, Nov 16, 2017 at 6:12 AM, Marek Vasut wrote:
>>> On 11/15/2017 05:47 PM, Stefan Agner wrote:
On 2017-11-14 19:32, Otavio Salvador wrote:
> This
On 11/16/2017 01:02 PM, Otavio Salvador wrote:
> On Thu, Nov 16, 2017 at 6:12 AM, Marek Vasut wrote:
>> On 11/15/2017 05:47 PM, Stefan Agner wrote:
>>> On 2017-11-14 19:32, Otavio Salvador wrote:
This upgrades the U-Boot from 2017.09 to 2017.11 release.
>>>
>>> You might
looks good,
On 11/15/2017 11:59 PM, patrice.chot...@st.com wrote:
> From: Patrice Chotard
>
> MPU's region setup can be factorized between STM32F4/F7/H7 SoCs family
> and used a common MPU's region config.
>
> Only one exception for STM32H7 which doesn't have device
On Thu, Nov 16, 2017 at 9:59 AM, Otavio Salvador
wrote:
> From: Fabio Berton
>
> Create layout with a boot 16MiB partition and rootfs with remain
> space.
>
> Signed-off-by: Fabio Berton
> Signed-off-by:
On Thu, Nov 16, 2017 at 9:59 AM, Otavio Salvador
wrote:
> From: Fabio Berton
>
> Currently the rootfs location is passed via mmcblk number and using
> the UUID method to specify the rootfs location is a better approach
> working even if
On Thu, Nov 16, 2017 at 11:41:57AM +, Andre Przywara wrote:
> Hi,
>
> On 16/11/17 11:21, Maxime Ripard wrote:
> > On Thu, Nov 16, 2017 at 10:30:38AM +, Andre Przywara wrote:
> >> Hi,
> >>
> >> On 15/11/17 21:03, Alexander Graf wrote:
> >>>
> >>>
> >>> On 15.11.17 11:11, Maxime Ripard
Dear Duncan,
In message <1814106598.1047276.1510787951...@mail.yahoo.com> you wrote:
>
> Many board manufacturers "assign" this unique MAC address by printing it on a
> sticker and sticking that on the board somewhere. It's pretty darn hard to
> read a printed sticker in software, so we have to
Hi Bin,
Sorry for long delay, I finally got to prepare v3 series.
On Tue, 16 May 2017 22:40:29 +0800
Bin Meng bmeng...@gmail.com wrote:
...
> > +#define SB_MANIFEST_BASE 0xFFFE
>
> nits: please use lower case hex and fix this globally in this file
OK, done in v3.
...
> >
On 7.11.2017 03:16, Wilson Lee wrote:
> From: Joe Hershberger
>
> Zynq NAND driver is not support for NAND lock or unlock operation.
> Hence, accidentally write into the critical NAND region might cause
> data corruption to occur.
>
> This commit is to add NAND
On 15.11.2017 10:14, Wilson Lee wrote:
> Putting board_nand_init() function inside NAND driver was not appropriate
> due to it doesn't allow board vendor to customise their NAND
> initialization code such as adding NAND lock/unlock code.
>
> This commit was to move the board_nand_init() function
This reverts commit b63b46313ed29e9b0c36b3d6b9407f6eade40c8f.
This commit changed cadence_qspi_apb to use bouncebuf.c, which invalidates
the data cache after reading. This is meant for dma transfers only and
breaks the cadence_qspi driver which copies via cpu only: data that is
copied by the cpu
Adopt the Linux DT bindings and clean-up duplicate
and unused values.
---
Changes for v4:
- Rebased
arch/arm/dts/keystone-k2g-evm.dts | 8
arch/arm/dts/keystone-k2g.dtsi| 5 +++--
arch/arm/dts/socfpga.dtsi | 5 +++--
Fix indentation of the QSPI node.
---
Changes for v4:
- Rebased
arch/arm/dts/keystone-k2g-evm.dts | 75 +++
1 file changed, 37 insertions(+), 38 deletions(-)
diff --git a/arch/arm/dts/keystone-k2g-evm.dts
b/arch/arm/dts/keystone-k2g-evm.dts
index
Cleanup unused #define values that are read from the DT.
---
Changes for v4:
- Rebased
include/configs/k2g_evm.h| 1 -
include/configs/socfpga_common.h | 1 -
include/configs/stv0991.h| 1 -
3 files changed, 3 deletions(-)
diff --git a/include/configs/k2g_evm.h
Adopt the Linux DT bindings. This also fixes an issue
with the indaddrtrig register on the Cadence QSPI
device being programmed with the wrong value for the
socfpga arch.
---
Changes for v4:
- Rebased
drivers/spi/cadence_qspi.c | 20
drivers/spi/cadence_qspi.h |
Update documentation to reflect adopting the Linux DT bindings.
---
Changes for v4:
- Updated documentation
doc/device-tree-bindings/spi/spi-cadence.txt | 13 -
1 file changed, 8 insertions(+), 5 deletions(-)
diff --git a/doc/device-tree-bindings/spi/spi-cadence.txt
Adopt the Linux DT bindings. This also fixes an issue
with the indaddrtrig register on the Cadence QSPI
device being programmed with the wrong value for the
socfpga arch.
Tested on Terasic SoCKit dev board (Altera Cyclone V)
Jason Rush (5):
spi: cadence_spi: Sync DT bindings with Linux
dts:
On Mon, Nov 13, 2017 at 08:42:34PM +0800, Icenowy Zheng wrote:
> 在 2017-11-13 20:38,Maxime Ripard 写道:
> > Hi,
> >
> > On Mon, Nov 13, 2017 at 07:34:46PM +0800, Icenowy Zheng wrote:
> > > +++ b/configs/orangepi_r1_defconfig
> > > @@ -0,0 +1,19 @@
> > > +CONFIG_ARM=y
> > > +CONFIG_ARCH_SUNXI=y
> >
Hi Tom,
please pull the following pending patches for MVEBU.
Thanks,
Stefan
The following changes since commit c253573f3e269fd9a24ee6684d87dd91106018a5:
Prepare v2017.11 (2017-11-13 20:08:06 -0500)
are available in the Git repository at:
git://www.denx.de/git/u-boot-marvell.git
for
On 13.11.2017 06:04, Baruch Siach wrote:
All current ClearFog SOMs have the SPI flash populated. Enable SPI flash in
the device tree.
Add an alias to the SPI bus so that the 'sf' command can probe the flash on
bus 1.
Add the "spi-flash" compatible string to make the standard SPI flash driver
On 13.11.2017 06:04, Baruch Siach wrote:
From: Jon Nettleton
The production variant of the SPI flash used by the clearfog
devices are based on winbond chips. Additionally enable
SPI_FLASH_BAR since some variants will have 16MB of flash
that requires this to be enabled.
On 06.11.2017 09:33, Baruch Siach wrote:
From: Jon Nettleton
Enable the driver by default for the clearfog boards since the external
port is configured for XHCI.
Signed-off-by: Jon Nettleton
[baruch: split from the SoC setup patch]
Signed-off-by:
On 06.11.2017 09:33, Baruch Siach wrote:
From: Jon Nettleton
This makes the initial changes need to support the
a38x series of SOCs. It adds the device-tree identifier
as well as changing the board_support function to take
the IO address designated by device-tree.
On 06.11.2017 09:33, Baruch Siach wrote:
From: Jon Nettleton
This fixes the USB 3.0 support for the a38x SOC.
Signed-off-by: Jon Nettleton
[baruch: use fdt_addr_t]
Signed-off-by: Baruch Siach
Applied to u-boot-marvell/master.
On 15.10.2017 07:03, Heinrich Schuchardt wrote:
Enable DISTRO_DEFAULTS for
mvebu_db_armada8k_defconfig
mvebu_mcbin-88f8040_defconfig
Signed-off-by: Heinrich Schuchardt
Applied to u-boot-marvell/master (with slightly modified subject).
Thanks,
Stefan
On 06.10.2017 09:11, Stefan Roese wrote:
The setexpr command is useful for scripting, lets enable it for this
platform.
Signed-off-by: Stefan Roese
Applied to u-boot-marvell/master.
Thanks,
Stefan
___
U-Boot mailing list
Applied to u-boot-marvell/master (with some change to the commit message)
Thanks,
Stefan
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
On Thu, 16 Nov 2017 12:54:13 +0100
Alexander Graf wrote:
> On 11/16/2017 12:41 PM, Andre Przywara wrote:
> > Hi,
> >
> > On 16/11/17 11:21, Maxime Ripard wrote:
> >> On Thu, Nov 16, 2017 at 10:30:38AM +, Andre Przywara wrote:
> >>> Hi,
> >>>
> >>> On 15/11/17 21:03, Alexander
Hi Tom,
On 2017년 11월 08일 07:48, Tom Rini wrote:
> On Tue, Nov 07, 2017 at 08:13:02AM +0100, Jorge Ramirez wrote:
>> On 11/07/2017 12:28 AM, Tom Rini wrote:
>>> Hey all,
>>>
>>> It's release day and v2017.11-rc4 is out. It's a week until release
>>> day. Please let me know if you know of any
I found a workaround. If I disable MMC_MODE_HS_52MHz, then it is working fine.
I guess there is a better way to implement the following patch ?
**
diff --git a/drivers/mmc/dw_mmc.c b/drivers/mmc/dw_mmc.c
index
From: Fabio Berton
Create layout with a boot 16MiB partition and rootfs with remain
space.
Signed-off-by: Fabio Berton
Signed-off-by: Otavio Salvador
---
Changes in v2:
- fix typo (s/Mib/MiB/) - Fabio
On Thu, Nov 16, 2017 at 6:12 AM, Marek Vasut wrote:
> On 11/15/2017 05:47 PM, Stefan Agner wrote:
>> On 2017-11-14 19:32, Otavio Salvador wrote:
>>> This upgrades the U-Boot from 2017.09 to 2017.11 release.
>>
>> You might encounter this when building fw_printenv/setenv tools
From: Fabio Berton
Signed-off-by: Fabio Berton
Signed-off-by: Otavio Salvador
---
Changes in v2: None
include/configs/pico-imx6ul.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
From: Fabio Berton
Command run setup_emmc will create gpt partitions for mmc 0 device
based on patitions variable.
Signed-off-by: Fabio Berton
Signed-off-by: Otavio Salvador
---
Changes in v2: None
From: Fabio Berton
Currently the rootfs location is passed via mmcblk number and using
the UUID method to specify the rootfs location is a better approach
working even if mmcblk number for the eMMC changes depending on the
kernel versions.
Signed-off-by: Fabio
From: Fabio Berton
Change dfu_alt_info variable to use the following altsetting:
uboot: To flash raw U-Boot
/zImage: boot: To copy kernel image
/imx6ul-pico-hobbit.dtb: To copy dtb file
rootfs:To copy
From: Fabio Berton
Create CONFIG_DFU_ENV_SETTINGS to set dfu environment settings to
improve human readable code.
Signed-off-by: Fabio Berton
Signed-off-by: Otavio Salvador
---
Changes in v2: None
On 11/16/2017 12:41 PM, Andre Przywara wrote:
Hi,
On 16/11/17 11:21, Maxime Ripard wrote:
On Thu, Nov 16, 2017 at 10:30:38AM +, Andre Przywara wrote:
Hi,
On 15/11/17 21:03, Alexander Graf wrote:
On 15.11.17 11:11, Maxime Ripard wrote:
The partitions variable is especially useful to
Hi,
On 16/11/17 11:21, Maxime Ripard wrote:
> On Thu, Nov 16, 2017 at 10:30:38AM +, Andre Przywara wrote:
>> Hi,
>>
>> On 15/11/17 21:03, Alexander Graf wrote:
>>>
>>>
>>> On 15.11.17 11:11, Maxime Ripard wrote:
The partitions variable is especially useful to create a partition table
On Thu, Nov 16, 2017 at 10:30:38AM +, Andre Przywara wrote:
> Hi,
>
> On 15/11/17 21:03, Alexander Graf wrote:
> >
> >
> > On 15.11.17 11:11, Maxime Ripard wrote:
> >> The partitions variable is especially useful to create a partition table
> >> from U-Boot, either directly from the U-Boot
On Thursday 16 November 2017 04:21 PM, Goldschmidt Simon wrote:
> Hi Vignesh,
>
> Vignesh R wrote:
>> [..]
>> Its not actually unaligned access, cadence QSPI IP on TI platforms do
>> not support non-byte accesses except for the last word. As per the TRM:
>> "The external master is only
Hi Vignesh,
Vignesh R wrote:
> [..]
> Its not actually unaligned access, cadence QSPI IP on TI platforms do
> not support non-byte accesses except for the last word. As per the TRM:
> "The external master is only permitted to issue 32-bit data interface
> writes until the last word of an indirect
Hi Simon,
On Thursday 16 November 2017 03:39 PM, Goldschmidt Simon wrote:
[...]
>
> This 32-bit spi transfer mode does not seem to be used too often, all
> other drivers I looked at are transferring byte by byte and thus can
> not be used as an example.
>
> Additionally, the TI platform Vignesh
Hi,
On 15/11/17 21:03, Alexander Graf wrote:
>
>
> On 15.11.17 11:11, Maxime Ripard wrote:
>> The partitions variable is especially useful to create a partition table
>> from U-Boot, either directly from the U-Boot shell, or through flashing
>> tools like fastboot and its oem format command.
>>
This patch removes the inclusion of the libgcc math functions and
replaces them by functions coded in C, taken from the coreboot
project. This makes U-Boot building more independent from the toolchain
installed / available on the build system.
The code taken from coreboot is authored from Vadim
Simon Goldschmidt wrote:
>Marek Vasut wrote:
>> So what alignment problems do you observe ? If you copy using the CPU
>> only, why do you need the bounce buffer at all ? I don't quite get it.
>
> Sorry for not explaining it good enough:
> I don't observe any alignment problems. mach-socfpga can
Hi Karsten,
On Wed, Nov 15, 2017 at 09:41:34PM +0100, Karsten Merker wrote:
> > We then provide a default partitionning scheme. I'd like feedback on
> > that one. I appreciate that having a good default in such a case, but
> > I'd like to have a reasonably simple layout that works good enough to
Hi Alexander,
On Wed, Nov 15, 2017 at 10:03:32PM +0100, Alexander Graf wrote:
> On 15.11.17 11:11, Maxime Ripard wrote:
> > The partitions variable is especially useful to create a partition table
> > from U-Boot, either directly from the U-Boot shell, or through flashing
> > tools like fastboot
The current environment has been hardcoded to an offset that starts to be
an issue given the current size of our main U-Boot binary.
By implementing a custom environment location routine, we can always favor
the FAT-based environment, and fallback to the MMC if we don't find
something in the FAT
Now that we have everything in place to support multiple environment, let's
make sure the current code can use it.
The priority used between the various environment is the same one that was
used in the code previously.
At read / init times, the highest priority environment is going to be
Now that we have everything in place in the code, let's allow to build
multiple environments backend through Kconfig.
Signed-off-by: Maxime Ripard
---
env/Kconfig | 65 ++---
1 file changed, 32
Allow boards and architectures to override the default environment lookup
code by overriding env_get_location.
Signed-off-by: Maxime Ripard
---
env/env.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/env/env.c b/env/env.c
index
In preparation for the multiple environment support, let's introduce two
new parameters to the environment driver lookup function: the priority and
operation.
The operation parameter is meant to identify, obviously, the operation you
might want to perform on the environment.
The priority is a
The env_driver_lookup_default and env_get_default_location functions are
about to get refactored to support loading from multiple environment.
The name is therefore not really well suited anymore. Drop the default
part to be a bit more relevant.
Signed-off-by: Maxime Ripard
No that there's no users of env_driver_lookup_default outside of env/env.c,
we can mark that function static and remove it from the environment header.
Signed-off-by: Maxime Ripard
---
env/env.c | 2 +-
include/environment.h | 7 ---
2 files
The nvedit command is the only user of env_driver_lookup_default outside of
the environment code itself, and it uses it only to print the environment
it's about to save to during env save.
As we're about to rework the environment to be able to handle multiple
environment sources, we might not
Now that we have everything in place to implement the transition scheme,
let's enable it by default.
Signed-off-by: Maxime Ripard
---
env/Kconfig | 4
1 file changed, 4 insertions(+)
diff --git a/env/Kconfig b/env/Kconfig
index bf6eab6b4ace..19524638e6e1
Hi,
Here is a second attempt at transitioning away from the MMC raw
environment to a FAT-based one.
You'll find the first one here for reference:
https://lists.denx.de/pipermail/u-boot/2017-October/310111.html
The fundamental issue I'm trying to adress is that we've had for a
very long time the
> -Original Message-
> From: York Sun
> Sent: Tuesday, November 14, 2017 10:27 PM
> To: Rajesh Bhagat ; u-boot@lists.denx.de
> Cc: Prabhakar Kushwaha ; Priyanka Jain
> ; Ashish Kumar
>
On 11/15/2017 05:47 PM, Stefan Agner wrote:
> On 2017-11-14 19:32, Otavio Salvador wrote:
>> This upgrades the U-Boot from 2017.09 to 2017.11 release.
>
> You might encounter this when building fw_printenv/setenv tools alone:
>
> https://lists.denx.de/pipermail/u-boot/2017-November/311505.html
On 11/16/2017 09:09 AM, Chee, Tien Fong wrote:
> On Jum, 2017-11-10 at 11:04 +0100, Marek Vasut wrote:
>> On 11/10/2017 10:05 AM, Chee, Tien Fong wrote:
>>>
>>> On Kha, 2017-11-09 at 11:31 +0100, Marek Vasut wrote:
On 11/09/2017 11:00 AM, Lukasz Majewski wrote:
>
>
> On Thu,
On 11/15/2017 11:38 PM, Rush, Jason A wrote:
> Goldschmidt Simon Wrote:
>> Marek Vasut wrote:
> I don't believe the patchset I submitted for DT bindings were merged in.
I can confirm that. I'd strongly vote for them to get in as cadence_qspi
is otherwise not usable on mach
On Jum, 2017-11-10 at 11:04 +0100, Marek Vasut wrote:
> On 11/10/2017 10:05 AM, Chee, Tien Fong wrote:
> >
> > On Kha, 2017-11-09 at 11:31 +0100, Marek Vasut wrote:
> > >
> > > On 11/09/2017 11:00 AM, Lukasz Majewski wrote:
> > > >
> > > >
> > > > On Thu, 9 Nov 2017 08:05:18 +0100
> > > >
From: Patrice Chotard
MPU's region setup can be factorized between STM32F4/F7/H7 SoCs family
and used a common MPU's region config.
Only one exception for STM32H7 which doesn't have device area
located at 0xA000 .
For STM32F4, configure_clocks() need to be moved
91 matches
Mail list logo