So we can use imagetool_get_source_date() from callers who do not have
the image tool params struct, just pass in the command name for the error
message.
Signed-off-by: Alex Kiernan
---
tools/default_image.c | 2 +-
tools/fit_image.c | 3 ++-
tools/imagetool.c | 4 ++--
When generating timestamps in signatures, use imagetool_get_source_date()
so we can be overridden by SOURCE_DATE_EPOCH to generate reproducible
images.
Signed-off-by: Alex Kiernan
---
include/image.h| 3 ++-
tools/fit_image.c | 3 ++-
tools/image-host.c | 34
On Wed, Jun 20, 2018 at 5:51 PM, Michael Trimarchi
wrote:
> drivers/spi/mxc_spi.c:507: undefined reference to `dev_get_addr'
> linux-ld.bfd: BFD (GNU Binutils) 2.29.1 assertion fail elf32-arm.c:9509
>
> Signed-off-by: Michael Trimarchi
Yes, this has been reported before. Thanks for fixing it:
During spi initialization logic creates a glitch on the clock and
if this is followed by the chip select this can be interpretated
as clock. Add a delay let the glitch out of chip select
Signed-off-by: Michael Trimarchi
---
drivers/spi/mxc_spi.c | 1 +
1 file changed, 1 insertion(+)
diff --git
CS GPIO activation low/high is determinated by the device tree
so we don't need to take in accoung in cs_activate and cs_deactivate
Signed-off-by: Michael Trimarchi
---
drivers/spi/mxc_spi.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/spi/mxc_spi.c
U-Boot needs to link ps7_init_gpl.c on Zynq or psu_init_gpl.c on
ZynqMP (PS init for short). The current logic to locate this file for
both platforms is:
1. if a board-specific file exists in
board/xilinx/zynq[mp]/$(CONFIG_DEFAULT_DEVICE_TREE)/ps?_init_gpl.c
then use it
2. otherwise use
Add extra feature to support data-enable and clock-polarity
Signed-off-by: Michael Trimarchi
---
drivers/video/mxsfb.c | 21 ++---
1 file changed, 18 insertions(+), 3 deletions(-)
diff --git a/drivers/video/mxsfb.c b/drivers/video/mxsfb.c
index 02fde05..4e3e3d7 100644
---
lcdif_power_down should not be included in spl build to avoid build
failure introduced by commit eb111bb31d882877e75e6b8083808dcaf6493b92
Signed-off-by: Michael Trimarchi
---
arch/arm/mach-imx/mx6/soc.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/mach-imx/mx6/soc.c
Hi,
On 20/06/18 16:24, Paul Kocialkowski wrote:
> Hi and thanks for your anwers!
>
> On Wed, 2018-06-20 at 11:56 +, Peng Fan wrote:
>> Hi Paul
>>
>>> -Original Message-
>>> From: Paul Kocialkowski [mailto:cont...@paulk.fr]
>>> Sent: 2018年6月20日 16:58
>>> To: Peng Fan ; sba...@denx.de;
On 17 June 2018 at 06:57, Bin Meng wrote:
> With driver model philosophy, we should avoid explicitly calling
> driver initialization routine during boot. This updates the ram
> init sequence table to exclude the IDE initialization for DM BLK.
>
> Signed-off-by: Bin Meng
> ---
>
>
drivers/spi/mxc_spi.c:507: undefined reference to `dev_get_addr'
linux-ld.bfd: BFD (GNU Binutils) 2.29.1 assertion fail elf32-arm.c:9509
Signed-off-by: Michael Trimarchi
---
drivers/spi/mxc_spi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/spi/mxc_spi.c
Hi,
Le mercredi 20 juin 2018 à 17:12 +0100, Andre Przywara a écrit :
> On 20/06/18 16:24, Paul Kocialkowski wrote:
> > Regarding the DDR firmware: I would like to start a discussion with NXP
> > and Synopsys about making the firmware free software/open source.
>
> Don't want to temper your
Hi Trent,
On Wed, Jun 20, 2018 at 05:51:28PM +, Trent Piepho wrote:
> On Mon, 2018-06-18 at 06:57 +0300, Baruch Siach wrote:
> > Since commit f916757300 (imx: Create distinct pre-processed mkimage
> > config files), *.cfgtmp files are no longer generated. There is no need
> > to remove them
Hi Alex,
On 14 June 2018 at 13:32, Alexander Graf wrote:
>
>
> On 14.06.18 21:02, Simon Glass wrote:
>> Hi Alex,
>>
>> On 14 June 2018 at 12:05, Alexander Graf wrote:
>>>
>>>
>>>
>>> On 14.06.18 19:15, Simon Glass wrote:
Hi Alex,
On 14 June 2018 at 11:08, Alexander Graf wrote:
Hi Bin,
On 17 June 2018 at 06:57, Bin Meng wrote:
> The generic efi payload currently does not enumerate the PCI bus,
> which means peripherals on the PCI bus are not discovered by their
> drivers. This uses board_early_init_r() to do the PCI enumeration.
>
> Signed-off-by: Bin Meng
> ---
>
>
On 17 June 2018 at 06:57, Bin Meng wrote:
> The default vesa mode was changed since commit 55b4e1b7d999
> ("x86: Change default FRAMEBUFFER_VESA_MODE of some boards") for
> better VxWorks compatibility but with the changes QEMU video console
> no longer works. This is because QEMU's vgabios
Hi Heinrich,
On 20 June 2018 at 00:03, Heinrich Schuchardt wrote:
> On 06/18/2018 04:08 PM, Simon Glass wrote:
>> This does not work at present and gives the following error:
>>
>> output: 'ld.bfd: read in flex scanner failed
>> scripts/Makefile.lib:390: recipe for target
>>
On Mon, 2018-06-18 at 06:57 +0300, Baruch Siach wrote:
> Since commit f916757300 (imx: Create distinct pre-processed mkimage
> config files), *.cfgtmp files are no longer generated. There is no need
> to remove them on the 'clean' target anymore.
>
> Remove also the .gitignore glob.
I didn't
Hi Heinrich,
On 15 June 2018 at 14:05, Heinrich Schuchardt wrote:
> Provide sandbox.dtb as default device tree for sandbox_defconfig.
>
> We can use the dtb with
>
> ./u-boot -d u-boot.dtb
There is a -D flag for that. Also I think your commit message should
distinguish between the
On 06/18/2018 04:08 PM, Simon Glass wrote:
> We plan to run more than one EFI test. In order to avoid duplicating code,
> create functions which handle preparing for running the test and cleaning
> up afterwards.
>
> Also shorten the awfully long variable names here.
>
> Signed-off-by: Simon
Hi Simon and other,
do we have a way to remove device and probe it again via u-boot prompt?
I was grepping u-boot and I didn't find any command for that. I see
functionality in the code and several tests but nothing what it is
available via command.
Thanks,
Michal
From: Tien Fong Chee
In ARM 64-bits, memory size can be supported is more than 4GB,
hence increasing save array is needed to cope with testing larger memory.
Signed-off-by: Tien Fong Chee
---
Changes in v2:
- Change save array size to save[BITS_PER_LONG - 1]
---
common/memsize.c | 2 +-
1
On 19.6.2018 20:40, Tom Rini wrote:
> On Wed, Jun 13, 2018 at 03:06:49PM +0200, Michal Simek wrote:
>
>> gpio input/set/clear and toggle commands are already cover that's why
>> there is no any other case which should be handled.
>>
>> Signed-off-by: Michal Simek
>> ---
>>
>> Reported by:
On 06/18/2018 04:08 PM, Simon Glass wrote:
> With sandbox the U-Boot code is not mapped into the sandbox memory range
> so does not need to be excluded when allocating EFI memory. Update the EFI
> memory init code to take account of that.
>
> Also use mapmem instead of a cast to convert a memory
Hi Marek,
2018-06-20 13:43 GMT+09:00 Marek Vasut :
> On 06/19/2018 08:39 AM, Masahiro Yamada wrote:
>> Hi Marek,
>
> Hi,
>
>> 2018-06-08 5:17 GMT+09:00 Marek Vasut :
>>> Replace the ad-hoc DMA cache management functions with common bouncebuf,
>>> since those functions are not handling cases where
On Tue, 2018-06-19 at 23:57 -0400, Tom Rini wrote:
>
>
> With the move to using at least gcc-6 for many targets we now have C
> code that requires the GNU11 C standard to be used in all cases.
Requiring gcc-6 is a bit much I think, there are lots of cross gcc's out there
that is older. I don't
On 06/20/2018 06:16 PM, Paul Kocialkowski wrote:
> Hi,
>
> Le mercredi 20 juin 2018 à 17:12 +0100, Andre Przywara a écrit :
>> On 20/06/18 16:24, Paul Kocialkowski wrote:
>>> Regarding the DDR firmware: I would like to start a discussion with NXP
>>> and Synopsys about making the firmware free
Hi Alex,
On 18 June 2018 at 08:51, Alexander Graf wrote:
> On 06/18/2018 04:08 PM, Simon Glass wrote:
>>
>> The test should exit like any other EFI application, by calling exit()
>> in the boot services API. But this crashes at present on sandbox. For now,
>> add in the placeholder code.
>>
>>
Hi Alex,
On 18 June 2018 at 08:52, Alexander Graf wrote:
> On 06/18/2018 04:08 PM, Simon Glass wrote:
>>
>> Sandbox only has 128MB of memory so we cannot relocate the device tree up
>> to start at 128MB. Use 127MB instead, which should be safe.
>>
>> Signed-off-by: Simon Glass
>
>
> We should
Hi Alex,
On 18 June 2018 at 09:03, Alexander Graf wrote:
> On 06/18/2018 04:08 PM, Simon Glass wrote:
>>
>> Sandbox does not support direct casts between addresses and pointers,
>> since it uses an emulated RAM buffer rather than directly using host
>> RAM.
>>
>> The current EFI code uses an
Hi Alex,
On 18 June 2018 at 09:23, Alexander Graf wrote:
> In sandbox, longjmp returns to itself in an endless loop. Cut this through
> by calling the real OS function.
>
> Setjmp on the other hand must not return. So here we have to call the OS
> setjmp function straight from the code where the
Hi Alex,
On 18 June 2018 at 09:08, Alexander Graf wrote:
> On 06/18/2018 04:08 PM, Simon Glass wrote:
>>
>> From: Alexander Graf
>>
>> The fs_read() function wants to get an address rather than the
>> pointer to a buffer.
>>
>> So let's convert the passed buffer from pointer back a the address
Hi Alex,
On 18 June 2018 at 09:23, Alexander Graf wrote:
> With efi_loader we do not control payload applications, so we can not
> teach them about the difference between virtual and physical addresses.
>
> Instead, let's just always map host virtual addresses in the efi memory
> map. That way
kOn 18 June 2018 at 09:23, Alexander Graf wrote:
> The fs_read() and fs_write() functions are internal interfaces that
> naturally want to get pointers as arguments. Most users so far even
> have pointers and explicitly cast them into integers just to be able
> to pass them into the function.
>
>
There is typo in the Subject: "implementation"
On Wed, Jun 20, 2018 at 6:27 PM, Michael Trimarchi
wrote:
> lcdif_power_down should not be included in spl build to avoid build
> failure introduced by commit eb111bb31d882877e75e6b8083808dcaf6493b92
What is the build failure exactly?
Please
On 06/20/2018 07:51 PM, Simon Glass wrote:
> Hi Alex,
>
> On 14 June 2018 at 17:13, Alexander Graf wrote:
>> So far we've always had a split address space situation with
>> "U-Boot addresses" (a number space starting from 0) and "host
>> virtual addresses" (128MB mapped randomly in address
Hi Alex,
On 18 June 2018 at 09:23, Alexander Graf wrote:
> Varargs differ between sysv and ms abi. On x86_64 we have to follow the ms
> abi though, so we also need to make sure we use x86_64 varargs helpers.
>
> This patch introduces generic efi vararg helpers that adhere to the
> respective EFI
Hi Heinrich,
On 20 June 2018 at 00:10, Heinrich Schuchardt wrote:
> On 06/18/2018 04:08 PM, Simon Glass wrote:
>> With sandbox the U-Boot code is not mapped into the sandbox memory range
>> so does not need to be excluded when allocating EFI memory. Update the EFI
>> memory init code to take
Hi Heinrich,
On 20 June 2018 at 00:26, Heinrich Schuchardt wrote:
> On 06/18/2018 04:08 PM, Simon Glass wrote:
>> We plan to run more than one EFI test. In order to avoid duplicating code,
>> create functions which handle preparing for running the test and cleaning
>> up afterwards.
>>
>> Also
Hi Alex,
On 18 June 2018 at 09:00, Alexander Graf wrote:
> On 06/18/2018 04:08 PM, Simon Glass wrote:
>>
>> At present this function takes a pointer as its argument, then passes this
>> to efi_allocate_pages(), which actually takes an address. It uses casts,
>> which are not supported on
Hi Alex,
On 18 June 2018 at 08:50, Alexander Graf wrote:
> On 06/18/2018 04:08 PM, Simon Glass wrote:
>>
>> At present map_sysmem() maps an address into the sandbox RAM buffer,
>> return a pointer, while map_to_sysmem() goes the other way.
>>
>> The mapping is currently just 1:1 since a case was
Hi Alex,
On 20 June 2018 at 03:31, Alexander Graf wrote:
> On 06/20/2018 12:03 AM, Simon Glass wrote:
>>
>> Hi Alex,
>>
>> On 14 June 2018 at 15:55, Alexander Graf wrote:
>>>
>>>
>>> On 14.06.18 23:35, Simon Glass wrote:
Hi Alex,
On 14 June 2018 at 13:51, Alexander Graf
Hi Alex,
On 20 June 2018 at 02:54, Alexander Graf wrote:
> On 06/20/2018 08:10 AM, Heinrich Schuchardt wrote:
>>
>> On 06/18/2018 04:08 PM, Simon Glass wrote:
>>>
>>> With sandbox the U-Boot code is not mapped into the sandbox memory range
>>> so does not need to be excluded when allocating EFI
Hi Alex,
On 20 June 2018 at 02:51, Alexander Graf wrote:
> On 06/20/2018 12:02 AM, Simon Glass wrote:
>>
>> Hi Alex,
>>
>> On 18 June 2018 at 08:45, Alexander Graf wrote:
>>>
>>> On 06/18/2018 04:08 PM, Simon Glass wrote:
Use a starting address of 256MB which should be available. This
Hi Heinrich,
On 20 June 2018 at 19:23, Heinrich Schuchardt wrote:
> On 06/20/2018 07:51 PM, Simon Glass wrote:
>> Hi Alex,
>>
>> On 14 June 2018 at 17:13, Alexander Graf wrote:
>>> So far we've always had a split address space situation with
>>> "U-Boot addresses" (a number space starting from
Hi Michal,
On 20 June 2018 at 00:31, Michal Simek wrote:
> Hi Simon and other,
>
> do we have a way to remove device and probe it again via u-boot prompt?
> I was grepping u-boot and I didn't find any command for that. I see
> functionality in the code and several tests but nothing what it is
>
Hi Alex,
On 18 June 2018 at 09:23, Alexander Graf wrote:
> We try hard to make sure that SMBIOS tables live in the lower 32bit.
> However, when we can not find any space at all there, we should not
> error out but instead just fall back to map them in the full address
> space instead.
Does this
Hi Alex,
On 18 June 2018 at 09:23, Alexander Graf wrote:
> From: Simon Glass
>
> With sandbox the U-Boot code is not mapped into the sandbox memory range
> so does not need to be excluded when allocating EFI memory. Update the EFI
> memory init code to take account of that.
>
> Signed-off-by:
Hi,
On 20 June 2018 at 10:44, York Sun wrote:
> Guys,
>
> I want to know if anyone is actively working on adding FIT support for
> SPL NOR. I have made some improvement (pending upstreaming) for
> LS1046ARDB QSPI boot. My target is to have falcon mode enabled for QSPI.
> This will give one
Hi Alex,
On 18 June 2018 at 09:23, Alexander Graf wrote:
> With efi_loader, we may want to execute payloads from RAM. By default,
> permissions on the RAM region don't allow us to execute from there though.
>
> So whenever we get into the efi_loader case, let's mark RAM as executable.
> That way
Hi Alex,
On 20 June 2018 at 02:56, Alexander Graf wrote:
> On 06/20/2018 12:02 AM, Simon Glass wrote:
>>
>> Hi Alex,
>>
>> On 18 June 2018 at 08:46, Alexander Graf wrote:
>>>
>>> On 06/18/2018 04:08 PM, Simon Glass wrote:
There appears to be a bug [1] in gcc when using varargs with
Hi Alex,
On 18 June 2018 at 09:53, Alexander Graf wrote:
> On 06/18/2018 05:22 PM, Alexander Graf wrote:
>>
>> This patch set augments Simon's patch set for efi_loader support
>> in sandbox[1], but cuts off the memory allocation scheme at a different
>> point.
>>
>> According to the UEFI spec,
On Wed, Jun 20, 2018 at 1:12 AM, Heinrich Schuchardt wrote:
> car.o can only be used with start.o, not with start64.o.
>
> Signed-off-by: Heinrich Schuchardt
> ---
> v2
> rebase to current master
> shorten commit message
> ---
> arch/x86/cpu/qemu/Makefile | 5 -
> 1 file
On Wed, Jun 20, 2018 at 2:40 AM, Ivan Gorinov wrote:
> Add setjmp/longjmp functions for x86_64.
>
> Signed-off-by: Ivan Gorinov
> ---
> arch/x86/cpu/x86_64/setjmp.S | 49
> +++
> arch/x86/cpu/x86_64/setjmp.c | 19 -
>
Hi Heinrich,
On 20 June 2018 at 20:01, Simon Glass wrote:
> Hi Heinrich,
>
> On 20 June 2018 at 19:23, Heinrich Schuchardt wrote:
>> On 06/20/2018 07:51 PM, Simon Glass wrote:
>>> Hi Alex,
>>>
>>> On 14 June 2018 at 17:13, Alexander Graf wrote:
So far we've always had a split address
On 06/20/2018 09:06 AM, tien.fong.c...@intel.com wrote:
> From: Tien Fong Chee
>
> In ARM 64-bits, memory size can be supported is more than 4GB,
> hence increasing save array is needed to cope with testing larger memory.
>
> Signed-off-by: Tien Fong Chee
> ---
>
> Changes in v2:
> - Change
On Thu, Jun 21, 2018 at 12:30 PM, Bin Meng wrote:
> On Wed, Jun 20, 2018 at 2:40 AM, Ivan Gorinov wrote:
>> Add setjmp/longjmp functions for x86_64.
>>
>> Signed-off-by: Ivan Gorinov
>> ---
>> arch/x86/cpu/x86_64/setjmp.S | 49
>> +++
>>
On Wed, Jun 20, 2018 at 6:02 AM, Simon Glass wrote:
> On 18 June 2018 at 19:43, Bin Meng wrote:
>> Previous rename of efi-x86 target missed the MAINTAINERS update,
>> which caused the buildman warnings:
>>
>> WARNING: no status info for 'efi-x86_app'
>> WARNING: no maintainers for
Hi Ivan,
On Tue, Jun 19, 2018 at 9:19 AM, Bin Meng wrote:
> On Mon, Jun 18, 2018 at 8:58 PM, Bin Meng wrote:
>> On Sat, Jun 16, 2018 at 2:01 AM, Ivan Gorinov wrote:
>>> Built without a ROM image with FSP (u-boot.rom), the U-Boot loader applies
>>> the microcode update data block encoded in
On Thu, Jun 21, 2018 at 12:30 PM, Bin Meng wrote:
> On Wed, Jun 20, 2018 at 1:12 AM, Heinrich Schuchardt
> wrote:
>> car.o can only be used with start.o, not with start64.o.
>>
>> Signed-off-by: Heinrich Schuchardt
>> ---
>> v2
>> rebase to current master
>> shorten commit
On 06/20/2018 09:14 AM, Masahiro Yamada wrote:
> Hi Marek,
>
> 2018-06-20 13:43 GMT+09:00 Marek Vasut :
>> On 06/19/2018 08:39 AM, Masahiro Yamada wrote:
>>> Hi Marek,
>>
>> Hi,
>>
>>> 2018-06-08 5:17 GMT+09:00 Marek Vasut :
Replace the ad-hoc DMA cache management functions with common
Hi Miquel, Simon,
> Hi,
>
> On 18 June 2018 at 03:47, Miquel Raynal
> wrote:
> >
> > Hi Martin,
> >
> > > > > Nevertheless one question: Why did you define another dts binding
> > > > > instead of using that one what is already available on the Linux
> > > > > kernel? There is
On 06/20/2018 12:02 AM, Simon Glass wrote:
Hi Alex,
On 18 June 2018 at 08:46, Alexander Graf wrote:
On 06/18/2018 04:08 PM, Simon Glass wrote:
There appears to be a bug [1] in gcc when using varargs with this
attribute. Disable it for sandbox so that functions which use that can
work
On 06/20/2018 08:10 AM, Heinrich Schuchardt wrote:
On 06/18/2018 04:08 PM, Simon Glass wrote:
With sandbox the U-Boot code is not mapped into the sandbox memory range
so does not need to be excluded when allocating EFI memory. Update the EFI
memory init code to take account of that.
Also use
On 06/20/2018 12:03 AM, Simon Glass wrote:
Hi Alex,
On 14 June 2018 at 15:55, Alexander Graf wrote:
On 14.06.18 23:35, Simon Glass wrote:
Hi Alex,
On 14 June 2018 at 13:51, Alexander Graf wrote:
On 14.06.18 21:01, Simon Glass wrote:
On 14 June 2018 at 12:22, Alexander Graf wrote:
The
On 06/20/2018 12:02 AM, Simon Glass wrote:
Hi Alex,
On 18 June 2018 at 08:45, Alexander Graf wrote:
On 06/18/2018 04:08 PM, Simon Glass wrote:
Use a starting address of 256MB which should be available. This helps to
make sandbox RAM buffers pointers more recognisable.
Signed-off-by: Simon
Hi there,
On Wed, 2018-01-10 at 13:20 +0800, Peng Fan wrote:
> Add i.MX8MQ EVK support. SPL will initialize ddr and load ddr phy
> firmware. Then loading FIT image, ATF to OCRAM, U-Boot and DTB to
> DRAM.
First off, I'd like to express my gratitude for this port: the i.MX8
looks like a great
On 06/18/2018 04:08 PM, Simon Glass wrote:
> This does not work at present and gives the following error:
>
> output: 'ld.bfd: read in flex scanner failed
> scripts/Makefile.lib:390: recipe for target
> 'lib/efi_selftest/efi_selftest_miniapp_return_efi.so' failed
>
> It may be possible to
Guys,
I want to know if anyone is actively working on adding FIT support for
SPL NOR. I have made some improvement (pending upstreaming) for
LS1046ARDB QSPI boot. My target is to have falcon mode enabled for QSPI.
This will give one dedicated example to use falcon mode with QSPI
(SD/eMMC is
On 18 June 2018 at 07:56, Jean-Jacques Hiblot wrote:
> Command "dm tree" dumps the devices with class, driver, name information.
> Add the index of the device in the class too, because the information is
> useful for the bind/unbind commands.
>
> Signed-off-by: Jean-Jacques Hiblot
>
> ---
>
>
On 17 June 2018 at 06:57, Bin Meng wrote:
> For boards that don't route serial port pins out, it's quite common
> to attach a USB keyboard as the input device, along with a monitor.
> However USB is not automatically started in the generic efi payload
> codes. This uses a payload specific
Hi Alex,
On 14 June 2018 at 17:13, Alexander Graf wrote:
> So far we've always had a split address space situation with
> "U-Boot addresses" (a number space starting from 0) and "host
> virtual addresses" (128MB mapped randomly in address space).
>
> This meant that we had to make sure all code
Hi Jean-Jacques,
On 18 June 2018 at 07:56, Jean-Jacques Hiblot wrote:
> In some cases it can be useful to be able to bind a device to a driver from
> the command line.
> The obvious example is for versatile devices such as USB gadget.
> Another use case is when the devices are not yet ready at
Hi Jean-Jacques,
On 18 June 2018 at 07:56, Jean-Jacques Hiblot wrote:
> Signed-off-by: Jean-Jacques Hiblot
> ---
Please add a commit message with motivation and purpose.
Also please add a test for this (e.g. in test/dm/core.c
>
> Changes in v2: New
>
> drivers/core/uclass.c| 21
On 19 June 2018 at 11:12, Heinrich Schuchardt wrote:
> car.o can only be used with start.o, not with start64.o.
>
> Signed-off-by: Heinrich Schuchardt
> ---
> v2
> rebase to current master
> shorten commit message
> ---
> arch/x86/cpu/qemu/Makefile | 5 -
> 1 file changed, 4
From: Fabio Estevam
On a 4.18-rc1 kernel the following warning is seen on i.MX51 and
i.MX53:
CPU0: Spectre v2: firmware did not set auxiliary control register IBE bit,
system vulnerable
Select the ARM_CORTEX_A8_CVE_2017_5715 workaround for i.MX51/i.MX53
to fix the problem.
With this patch
Change address of DPL header in SD
Signed-off-by: Vinitha V Pillai
---
include/configs/ls1088ardb.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/configs/ls1088ardb.h b/include/configs/ls1088ardb.h
index e629814..40b1716 100644
--- a/include/configs/ls1088ardb.h
On Tue, Jun 12, 2018 at 5:24 PM, Nishanth Menon wrote:
> As recommended by Arm in [1], ACTLR[0] (Enable invalidates of BTB)
> needs to be set[2] for BTB to be invalidated on ICIALLU. This needs to
> be done unconditionally for Cortex-A15 processors. Provide a config
> option for platforms to
Hi and thanks for your anwers!
On Wed, 2018-06-20 at 11:56 +, Peng Fan wrote:
> Hi Paul
>
> > -Original Message-
> > From: Paul Kocialkowski [mailto:cont...@paulk.fr]
> > Sent: 2018年6月20日 16:58
> > To: Peng Fan ; sba...@denx.de; Fabio Estevam
> >
> > Cc: u-boot@lists.denx.de;
On Tue, Jun 12, 2018 at 5:24 PM, Nishanth Menon wrote:
> As recommended by Arm in [1], IBE[2] has to be enabled unconditionally
> for BPIALL to be functional on Cortex-A8 processors. Provide a config
> option for platforms to enable this option based on impact analysis
> for products.
>
> NOTE:
On Wed, Jun 20, 2018 at 07:28:15AM +, Joakim Tjernlund wrote:
> On Tue, 2018-06-19 at 23:57 -0400, Tom Rini wrote:
> >
> >
> > With the move to using at least gcc-6 for many targets we now have C
> > code that requires the GNU11 C standard to be used in all cases.
>
> Requiring gcc-6 is a
Hi all,
Some system really need ext4 journal_data option to avoid any
inconsistency on his filesystem in case of unexpected power failure.
While journal_data greatly improved the reliability of the system from
the Linux kernel point of view, to my surprise this has increase the
failure rate of
(resending trimmed version to pass the U-Boot size limit filter ...)
Hi,
On 20/06/18 09:57, Paul Kocialkowski wrote:
> Hi there,
>
> On Wed, 2018-01-10 at 13:20 +0800, Peng Fan wrote:
>> Add i.MX8MQ EVK support. SPL will initialize ddr and load ddr phy
>> firmware. Then loading FIT image, ATF
On Tue, Jun 19, 2018 at 8:33 PM, Vasily Khoruzhick wrote:
> On Mon, Jun 18, 2018 at 11:56 PM, Jagan Teki wrote:
>>
>> This what[1] I changed on top of your changes, same issue.
>>
>> [1] https://paste.ubuntu.com/p/NjYyMk68P6/
>
> It should be tested separately.
Works for me, with md 0x01c11144
Hi,
On Wed, 2018-06-20 at 12:37 +0100, Andre Przywara wrote:
> (resending trimmed version to pass the U-Boot size limit filter ...)
>
> Hi,
>
> On 20/06/18 09:57, Paul Kocialkowski wrote:
> > Hi there,
> >
> > On Wed, 2018-01-10 at 13:20 +0800, Peng Fan wrote:
> > > Add i.MX8MQ EVK support.
Hi Paul
> -Original Message-
> From: Paul Kocialkowski [mailto:cont...@paulk.fr]
> Sent: 2018年6月20日 16:58
> To: Peng Fan ; sba...@denx.de; Fabio Estevam
>
> Cc: u-boot@lists.denx.de; andre.przyw...@arm.com; Todd Weaver
> ; Nicole Faerber
> Subject: Re: [U-Boot] [PATCH V5 31/31] imx: add
On Wed, 2018-06-20 at 13:54 +0200, Paul Kocialkowski wrote:
> Hi,
>
> On Wed, 2018-06-20 at 12:37 +0100, Andre Przywara wrote:
> > (resending trimmed version to pass the U-Boot size limit filter ...)
> >
> > Hi,
> >
> > On 20/06/18 09:57, Paul Kocialkowski wrote:
> > > Hi there,
> > >
> > > On
87 matches
Mail list logo
