Dear Andre,
In message <552c6e47-c700-829f-c03b-a8576f616...@arm.com> you 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 enthusiasm, but I believe this has be
On 18.6.2018 15:56, Jean-Jacques Hiblot wrote:
> Signed-off-by: Jean-Jacques Hiblot
> ---
>
> Changes in v2: New
>
> drivers/core/uclass.c| 21 +
> include/dm/uclass-internal.h | 11 +++
> 2 files changed, 32 insertions(+)
>
> diff --git a/drivers/core/uclas
Hi Michael,
On Wed, 20 Jun 2018 22:55:55 +0200
Michael Trimarchi mich...@amarulasolutions.com wrote:
> 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(+),
Hi
On Thu, Jun 21, 2018 at 9:17 AM, Anatolij Gustschin wrote:
> Hi Michael,
>
> On Wed, 20 Jun 2018 22:55:55 +0200
> Michael Trimarchi mich...@amarulasolutions.com wrote:
>
>> Add extra feature to support data-enable and clock-polarity
>>
>> Signed-off-by: Michael Trimarchi
>> ---
>> drivers/vi
On 18.6.2018 15: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 startup and
> require some
Use live-tree function.
Signed-off-by: Michal Simek
---
drivers/gpio/zynq_gpio.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpio/zynq_gpio.c b/drivers/gpio/zynq_gpio.c
index 8d84e3fc1313..afba4580f570 100644
--- a/drivers/gpio/zynq_gpio.c
+++ b/drivers/gpio/zynq
Hi Heinrich,
On Tue, 19 Jun 2018 19:01:06 +0200
Heinrich Schuchardt xypron.g...@gmx.de wrote:
...
> @Anatolij:
> Do you have an overview if we have blue in the low bits of the pixels in
> all low endian U-Boot supported devices?
No, I don't have such overview.
--
Anatolij
___
On Mon, Jun 18, 2018 at 7:56 PM, Andrew Thomas wrote:
> This bug is the combination of dwc2 USB controller and lan78xx
> USB ethernet controller, which is the combination in use on
> the Raspberry Pi Model 3 B+.
>
> When the host attempts to receive a packet, but a packet has not
> arrived, the la
From: Jon Nettleton
This is required so SPL and u-boot can boot from spi
flash devices that use the dm drivers.
Signed-off-by: Jon Nettleton
Signed-off-by: Baruch Siach
---
arch/arm/dts/armada-388-clearfog.dts | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/dts/armada-388-clear
Hi Baruch,
On 21.06.2018 11:03, Baruch Siach wrote:
> From: Jon Nettleton
>
> This is required so SPL and u-boot can boot from spi
> flash devices that use the dm drivers.
>
> Signed-off-by: Jon Nettleton
> Signed-off-by: Baruch Siach
> ---
> arch/arm/dts/armada-388-clearfog.dts | 2 ++
>
From: Michal Simek
This patch added support to read register base address
from DTS file.
Signed-off-by: Michal Simek
Signed-off-by: Vipul Kumar
---
Changes in v3:
- Read reg in probe function
- Removed xilinx_spi_ofdata_to_platdata function
- Removed reading of fifo_depth
---
drivers/spi/xili
This series of patches do the following:
- This patch added support to get reg base address from DTS file
- Added rxfifo() and txfifo() functions to add the modularity
- Added support to read JEDEC-id twice at the boot time
Changes in v2:
- Split single patch into the series of patches
Changes in
This patch is for the startup block issue in the spi controller.
SPI clock is passing through STARTUP block to FLASH. STARTUP block
don't provide clock as soon as QSPI provides command. So, first
command fails.
This patch added support to read JEDEC id in xilinx_spi_xfer ().
Signed-off-by: Vipul
This patch modify xilinx_spi_xfer() function and add rxfifo() and
txfifo() functions to add the modularity so that these functions
can be used by other functions within the same file.
This patch also added support to read fifo_size from dts.
Signed-off-by: Vipul Kumar
Signed-off-by: Siva Durga P
From: Jon Nettleton
This is required so SPL and u-boot can boot from spi
flash devices that use the dm drivers.
Signed-off-by: Jon Nettleton
[baruch: use -u-boot.dtsi]
Signed-off-by: Baruch Siach
---
v2: Add u-boot,dm-spl in .dtsi (Stefan Roese)
---
arch/arm/dts/armada-388-clearfog-u-boot.dts
On 21.06.2018 11:35, Baruch Siach wrote:
From: Jon Nettleton
This is required so SPL and u-boot can boot from spi
flash devices that use the dm drivers.
Signed-off-by: Jon Nettleton
[baruch: use -u-boot.dtsi]
Signed-off-by: Baruch Siach
---
v2: Add u-boot,dm-spl in .dtsi (Stefan Roese)
---
On 06/21/2018 04:01 AM, Simon Glass wrote:
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 f
On 06/21/2018 04:02 AM, Simon Glass wrote:
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 helpe
On 06/21/2018 04:02 AM, Simon Glass wrote:
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 funct
On 06/21/2018 04:02 AM, Simon Glass wrote:
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, le
On 06/21/2018 04:44 AM, Simon Glass wrote:
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.
Ac
On 06/21/2018 04:02 AM, Simon Glass wrote:
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 ex
On 06/21/2018 04:02 AM, Simon Glass wrote:
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 b
On 06/21/2018 04:02 AM, Simon Glass wrote:
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 usin
On 06/21/2018 04:01 AM, Simon Glass wrote:
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 curre
On 06/21/2018 04:01 AM, Simon Glass wrote:
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:
Hi Simon,
On 21.6.2018 04:02, Simon Glass wrote:
> 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
>> functiona
On 06/21/2018 04:01 AM, Simon Glass wrote:
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 curre
On 06/21/2018 04:01 AM, Simon Glass wrote:
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,
wh
On 06/21/2018 04:01 AM, Simon Glass wrote:
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 c
Hello,
I came across this commit on the github repo titled: "fdtdec: allow board to
provide fdt for CONFIG_OF_SEPARATE" dated 10th Jan in lib/fdtdec.c
The commit changes the following lines:
>elif defined CONFIG_OF_SEPARATE
>ifdef CONFIG_SPL_BUILD
>if (IS_ENABLED(CONFIG_SPL_SEPAR
Hi Simon,
On Thu, Jun 21, 2018 at 1:51 AM, Simon Glass 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_
Tom, Stefano,
Scott Wood seems not to be very active this days in the U-Boot
community.
This patchsets seem all to be blocked due to that:
https://patchwork.ozlabs.org/cover/897263/
https://patchwork.ozlabs.org/cover/901995/
https://patchwork.ozlabs.org/patch/922907/
Those patches have been arou
Signed-off-by: Alexey Brodkin
---
board/synopsys/emdk/README | 82 ++
1 file changed, 82 insertions(+)
create mode 100644 board/synopsys/emdk/README
diff --git a/board/synopsys/emdk/README b/board/synopsys/emdk/README
new file mode 100644
index ..
Hi Tom,
The following changes since commit a5742efa20384a27d51ee6c43d02c2025536c65d:
Prepare v2018.07-rc2 (2018-06-19 19:39:44 -0400)
are available in the Git repository at:
git://git.denx.de/u-boot-arc.git tags/arc-updates-for-2018.07-rc3
for you to fetch changes up to 0921f9294bd10b6639c
Enable ums command for zcu100 to enable mass storage gadget.
Tested with ums 0 mmc 0 (for SD) and ums 0 usb 0 (for USB flashdisk).
Signed-off-by: Michal Simek
---
configs/xilinx_zynqmp_zcu100_revC_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/configs/xilinx_zynqmp_zcu100_revC_de
Use enum command_ret_t types in cmd_process_error().
Signed-off-by: Michal Simek
---
Changes in v2:
- Move adding RET_USAGE to separate patch.
common/command.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/common/command.c b/common/command.c
index 52d47c133c3c..a4a8dc
command_ret_t enum contains 3 return values but only two are handled
now. Extend cmd_process_error() and handle CMD_RET_USAGE separately.
These commands are affected by this change.
cmd/demo.c
cmd/efi.c
cmd/gpio.c
cmd/qfw.c
cmd/x86/fsp.c
test/dm/cmd_dm.c
And scripts shouldn't be affected because
On 21/06/2018 12:04, Michal Simek wrote:
Hi Simon,
On 21.6.2018 04:02, Simon Glass wrote:
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 comman
On 06/19/2018 08:41 PM, Tom Rini wrote:
On Fri, Jun 08, 2018 at 08:53:26PM +0300, Ramon Fried wrote:
Add dump trace command which dump all trace
buffer content in a much more readable fashion
than md.
Signed-off-by: Ramon Fried
Reviewed-by: Simon Glass
Applied to u-boot/master, thanks!
Th
> In the sandbox environment we can not easily build efi stub binaries
> right now, so let's disable the respective test cases for the efi
> selftest suite.
>
> Signed-off-by: Alexander Graf
> Reviewed-by: Simon Glass
Thanks, applied to efi-next
Alex
__
> We need to know about x86 relocation definitions even in cases where
> we don't officially build against the x86 target, such as with sandbox.
>
> So let's move the x86 definitions into the common elf header, where all
> other architectures already have them.
>
> Signed-off-by: Alexander Graf
> The bootefi command gets a few addresses as values passed in. In sandbox,
> these values are in U-Boot address space, so we need to make sure we
> explicitly call map_sysmem() on them to be able to access them.
>
> Signed-off-by: Alexander Graf
> Reviewed-by: Simon Glass
Thanks, applied to ef
> We currently expose host addresses in the EFI memory map. That can be
> bad if we ever want to use sandbox to boot strap a real kernel, because
> then the kernel would fetch its memory table from our host virtual address
> map. But to make that use case work, we would need to have full control
>
> Thanks to CONFIG_SANDBOX, we can not rely on config options to tell us
> what CPU architecture we're running on.
>
> The compiler however does know that, so let's just move the ifdefs over
> to compiler based defines rather than kconfig based options.
>
> Signed-off-by: Alexander Graf
Thanks,
> 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: Simon Glass
> [agraf: Remove map_sysmem() call]
> Signed-o
> Now that elf.h contains relocation defines for all architectures
> we care about, let's just include it unconditionally and refer to
> the defines.
>
> Signed-off-by: Alexander Graf
Thanks, applied to efi-next
Alex
___
U-Boot mailing list
U-Boot@li
> 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.
>
> Signed-off-by: Alexander Graf
Thanks, applied to efi-next
Alex
> The EFI image loader tries to determine which target architecture we're
> working with to only load PE binaries that match.
>
> So far this has worked based on CONFIG defines, because the target CPU
> was always indicated by a config define. With sandbox however, this is
> not longer true as all
> 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 ABI. That way we can deal with them properly from efi
> lo
> From: Heinrich Schuchardt
>
> When running on the sandbox the stack is not necessarily at a higher memory
> address than the highest free memory.
>
> There is no reason why the checking of the highest memory address should be
> more restrictive for EFI_ALLOCATE_ANY_PAGES than for
> EFI_ALLOCAT
On Thu, Jun 21, 2018 at 05:11:27PM +0200, Alexander Graf wrote:
> On 06/19/2018 08:41 PM, Tom Rini wrote:
> >On Fri, Jun 08, 2018 at 08:53:26PM +0300, Ramon Fried wrote:
> >
> >>Add dump trace command which dump all trace
> >>buffer content in a much more readable fashion
> >>than md.
> >>
> >>Sig
On Thu, Jun 21, 2018 at 01:46:10PM +0200, Stefan Agner wrote:
> Tom, Stefano,
>
> Scott Wood seems not to be very active this days in the U-Boot
> community.
>
> This patchsets seem all to be blocked due to that:
> https://patchwork.ozlabs.org/cover/897263/
> https://patchwork.ozlabs.org/cover/9
Hi Tom,
This is my current patch queue for efi on 2018.07. Please pull.
Alex
The following changes since commit a5742efa20384a27d51ee6c43d02c2025536c65d:
Prepare v2018.07-rc2 (2018-06-19 19:39:44 -0400)
are available in the git repository at:
git://github.com/agraf/u-boot.git tags/signe
On 06/21/2018 05:20 PM, Tom Rini wrote:
On Thu, Jun 21, 2018 at 05:11:27PM +0200, Alexander Graf wrote:
On 06/19/2018 08:41 PM, Tom Rini wrote:
On Fri, Jun 08, 2018 at 08:53:26PM +0300, Ramon Fried wrote:
Add dump trace command which dump all trace
buffer content in a much more readable fash
On Wed, Jun 20, 2018 at 08:02:09PM -0600, Simon Glass wrote:
> 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
> At present a NULL pointer passed to printf for a %pU argument will cause
> U-Boot to access memory at 0. Fix this by adding a check, and print
> "(null)" instead.
>
> Signed-off-by: Simon Glass
> Reviewed-by: Alexander Graf
Thanks, applied to efi-next
Alex
__
Hi Stefan,
On 21/06/2018 17:22, Tom Rini wrote:
> On Thu, Jun 21, 2018 at 01:46:10PM +0200, Stefan Agner wrote:
>
>> Tom, Stefano,
>>
>> Scott Wood seems not to be very active this days in the U-Boot
>> community.
>>
>> This patchsets seem all to be blocked due to that:
>> https://patchwork.ozlab
On 06/18/2018 04:08 PM, Simon Glass wrote:
Add some more verbose debugging when doing memory allocations. This might
help to find bugs later.
Signed-off-by: Simon Glass
---
Changes in v8: None
Changes in v7: None
Changes in v6: None
Changes in v5: None
Changes in v4: None
Changes in v3: None
C
> This is a bit confusing at present since it adds 4KB to the pointer, then
> rounds it up. It looks like a bug, but is not.
>
> Move the 4KB addition into a separate statement and expand the comment.
>
> Signed-off-by: Simon Glass
Thanks, applied to efi-next
Alex
> Fix the 'amp' typo, expand on what 'steps' is and fix a few other minor
> things.
>
> Signed-off-by: Simon Glass
Thanks, applied to efi-next
Alex
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
> This function currently returns an error code, but never uses it. There is
> no function comment so it is not obvious why. Presuambly the error is not
> important.
>
> Update the function to explain its purpose and why it ignores the error.
> Drop the useful error return value.
>
> Signed-off-b
Commit 2407183f98cf130b008125ef1718ccf89a192998 breaks
the qemu-x86 and edison builds.
Move ucode_base and ucode_size into common startup code,
except for configs with FSP.
Signed-off-by: Ivan Gorinov
---
arch/x86/cpu/intel_common/car.S | 10 --
arch/x86/cpu/start.S| 10
On Thu, Jun 21, 2018 at 11:59:55AM +, Alexey Brodkin wrote:
> Hi Tom,
>
> The following changes since commit a5742efa20384a27d51ee6c43d02c2025536c65d:
>
> Prepare v2018.07-rc2 (2018-06-19 19:39:44 -0400)
>
> are available in the Git repository at:
>
> git://git.denx.de/u-boot-arc.git t
On Tue, Jun 19, 2018 at 11:57:31PM -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.
>
> Signed-off-by: Tom Rini
With a much re-worded to be clearer than gcc-6 is not required but that
On Wed, Jun 20, 2018 at 06:40:42AM +0200, Marek Vasut wrote:
> he following changes since commit 378b29cbc6607ad8246b1381bc74ec62bdb19105:
>
> Merge git://git.denx.de/u-boot-x86 (2018-06-18 12:59:46 -0400)
>
> are available in the Git repository at:
>
> git://git.denx.de/u-boot-sh.git maste
+Angus into the thread...
On Thu, 2018-06-21 at 02:07 +0100, André Przywara wrote:
> 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 firmwa
During manufacturing it is useful to be able to verify integrity of
secondary fit image by just running
`./fit_check_sign -f /dev/mtdblock? -k ...`
This was unfortunately failing as fstat(fd, sbuf) was setting
sbuf->st_size to zero, which caused mmap to fail later on.
Signed-off-by: Radek Dostál
Hi Alex,
On 21 June 2018 at 03:59, Alexander Graf wrote:
> On 06/21/2018 04:02 AM, Simon Glass wrote:
>>
>> 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 wro
Hi Alex,
On 21 June 2018 at 03:38, Alexander Graf wrote:
>
> On 06/21/2018 04:01 AM, Simon Glass wrote:
>>
>> 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
Hi Alex,
On 21 June 2018 at 03:52, Alexander Graf wrote:
> On 06/21/2018 04:02 AM, Simon Glass wrote:
>>
>> 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:
>
> W
Hi Alex,
On 21 June 2018 at 03:44, Alexander Graf wrote:
> On 06/21/2018 04:02 AM, Simon Glass wrote:
>>
>> 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
Hi Alex,
On 21 June 2018 at 04:10, Alexander Graf wrote:
> On 06/21/2018 04:01 AM, Simon Glass wrote:
>>
>> 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 buf
Hi Alex,
On 21 June 2018 at 04:14, Alexander Graf wrote:
> On 06/21/2018 04:01 AM, Simon Glass wrote:
>>
>> 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 poin
Hi Alex,
On 21 June 2018 at 04:01, Alexander Graf wrote:
> On 06/21/2018 04:01 AM, Simon Glass wrote:
>>
>> 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 devic
Hi Bin,
On 21 June 2018 at 05:19, Bin Meng wrote:
> Hi Simon,
>
> On Thu, Jun 21, 2018 at 1:51 AM, Simon Glass 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 n
On 20 June 2018 at 14:10, Alex Kiernan wrote:
> 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.
Hi Alex,
On 21 June 2018 at 03:41, Alexander Graf wrote:
>
> On 06/21/2018 04:02 AM, Simon Glass wrote:
>>
>> 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.
>>>
Hi Alex,
On 21 June 2018 at 03:58, Alexander Graf wrote:
> On 06/21/2018 04:02 AM, Simon Glass wrote:
>>
>> 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 wro
Hi Alex,
On 21 June 2018 at 04:13, Alexander Graf wrote:
> On 06/21/2018 04:01 AM, Simon Glass wrote:
>>
>> 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 p
Hi Alex,
On 21 June 2018 at 03:47, Alexander Graf wrote:
> On 06/21/2018 04:44 AM, Simon Glass wrote:
>>
>> 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 supp
Hi Alex,
On 21 June 2018 at 04:00, Alexander Graf wrote:
> On 06/21/2018 04:01 AM, Simon Glass wrote:
>>
>> 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 buf
On 20 June 2018 at 14:10, Alex Kiernan wrote:
> 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
On 21 June 2018 at 06:58, Michal Simek wrote:
> Use enum command_ret_t types in cmd_process_error().
>
> Signed-off-by: Michal Simek
> ---
>
> Changes in v2:
> - Move adding RET_USAGE to separate patch.
>
> common/command.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
Reviewed-
On 21 June 2018 at 06:58, Michal Simek wrote:
> command_ret_t enum contains 3 return values but only two are handled
> now. Extend cmd_process_error() and handle CMD_RET_USAGE separately.
>
> These commands are affected by this change.
> cmd/demo.c
> cmd/efi.c
> cmd/gpio.c
> cmd/qfw.c
> cmd/x86/fs
Add ut_assertnull macro to include/test/ut.h
For testing of functions that returns NULL on errors.
Signed-off-by: Ramon Fried
---
include/test/ut.h | 12
1 file changed, 12 insertions(+)
diff --git a/include/test/ut.h b/include/test/ut.h
index 59b23a25a4..fce75fd12a 100644
--- a/in
>From: Karsten Merker
>To: Duncan Hare
>Cc: U-Boot Mailing List
>Sent: Wednesday, June 20, 2018 2:16 PM
>Subject: Re: Make Menuconfig Error
>
>On Wed, Jun 20, 2018 at 12:33:45AM +, Duncan Hare wrote:
>
>> Makefile:491: recipe for target 'menuconfig' failed
>> make: *** [menuconfig]
On 06/21/2018 01:37 AM, Peter Robinson wrote:
On Mon, Jun 18, 2018 at 7:56 PM, Andrew Thomas wrote:
This bug is the combination of dwc2 USB controller and lan78xx
USB ethernet controller, which is the combination in use on
the Raspberry Pi Model 3 B+.
When the host attempts to receive a packet
A minor fix to efi networking.
When if_type is not set, it leads grub2's efi code to send a bogus
arp request. This will then stall the progress of grub.
This was tested with grubaa64.efi from Redhat/Oracle linux 7u5.
The patch was tested against: 890e79f2b1c26c5ba1a86d179706348aec7feef7
(aka v2
if_type is not correctly initialized
Failure to initialize if_type means that grub2/efinet sends
a bogus arp request. It therefore gets no response. On Raspberry Pi 3B+
this leads to a pause at:
lan78xx_eth Waiting for PHY auto negotiation to complete... done
lan78xx_eth Waiting for PHY auto
Hi Ivan,
On Wed, Jun 13, 2018 at 9:36 AM, Bin Meng wrote:
> Hi Ivan,
>
> On Wed, Jun 13, 2018 at 1:52 AM, Ivan Gorinov wrote:
>> UEFI specifies the calling convention used in Microsoft compilers;
>> first arguments of a function are passed in (%rcx, %rdx, %r8, %r9).
>>
>> All other compilers use
Hi Ivan,
On Fri, Jun 22, 2018 at 2:07 AM, Ivan Gorinov wrote:
> Commit 2407183f98cf130b008125ef1718ccf89a192998 breaks
> the qemu-x86 and edison builds.
>
> Move ucode_base and ucode_size into common startup code,
> except for configs with FSP.
>
> Signed-off-by: Ivan Gorinov
> ---
> arch/x86/c
From: Ivan Gorinov
Built without a ROM image with FSP (u-boot.rom), the U-Boot loader applies
the microcode update data block encoded in Device Tree to the bootstrap
processor but not passed to the other CPUs when multiprocessing is enabled.
If the bootstrap processor successfully performs a mic
Hi Ivan,
On Fri, Jun 22, 2018 at 12:16 PM, Bin Meng wrote:
> From: Ivan Gorinov
>
> Built without a ROM image with FSP (u-boot.rom), the U-Boot loader applies
> the microcode update data block encoded in Device Tree to the bootstrap
> processor but not passed to the other CPUs when multiprocessi
On Fri, Jun 22, 2018 at 10:59 AM, Bin Meng wrote:
> Hi Ivan,
>
> On Fri, Jun 22, 2018 at 2:07 AM, Ivan Gorinov wrote:
>> Commit 2407183f98cf130b008125ef1718ccf89a192998 breaks
>> the qemu-x86 and edison builds.
>>
>> Move ucode_base and ucode_size into common startup code,
>> except for configs w
On Thu, Jun 21, 2018 at 1:51 AM, Simon Glass wrote:
> 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 consol
On Thu, Jun 21, 2018 at 1:51 AM, Simon Glass wrote:
> 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 BL
On Fri, Jun 22, 2018 at 3:45 AM, Simon Glass wrote:
> Hi Bin,
>
> On 21 June 2018 at 05:19, Bin Meng wrote:
>> Hi Simon,
>>
>> On Thu, Jun 21, 2018 at 1:51 AM, Simon Glass wrote:
>>> Hi Bin,
>>>
>>> On 17 June 2018 at 06:57, Bin Meng wrote:
The generic efi payload currently does not enumer
On Thu, Jun 21, 2018 at 1:51 AM, Simon Glass wrote:
> 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
From: Jay Carlson
This patch adds support for booting blank i.MX6 devices in SD/MMC Manufacture
Mode: a fallback mode which the boot ROM enters when no fuses or boot mode
pins have been set, the USB serial downloader connection is inactive, and there
is an SD card inserted into uSDHC1. The i.MX7
1 - 100 of 105 matches
Mail list logo
