Hi Lukas,
On Sat, Nov 10, 2018 at 10:11 PM Auer, Lukas
wrote:
>
> Hi Bin,
>
> On Wed, 2018-10-10 at 22:06 -0700, Bin Meng wrote:
> > Currently the comments of several APIs (eg: dm_init_and_scan()) say:
> >
> > @pre_reloc_only: If true, bind only drivers with the
> > DM_FLAG_PRE_RELOC
> > flag.
Do not use the sandbox's virtual address space for the internal structures
of the memory map. This way we can eliminate a whole lot of unnecessary
conversions.
The only conversion remaining is the one when adding known memory.
Signed-off-by: Heinrich Schuchardt
---
lib/efi_loader/efi_memory.c
Add a sandbox DMA driver implementation (provider) and corresponding DM
test.
Reviewed-by: Tom Rini
Signed-off-by: Grygorii Strashko
---
arch/sandbox/dts/test.dts | 8 ++
configs/sandbox_defconfig | 3 +
drivers/dma/Kconfig| 7 +
drivers/dma/Makefile | 1
From: Vignesh R
Add support for K3 AM65x UDMA with only support pktmode MEM_TO_MEM
transfers and DEV_TO_MEM/MEM_TO_DEV through DMA channels.
Signed-off-by: Peter Ujfalusi
Signed-off-by: Grygorii Strashko
---
drivers/dma/Kconfig |2 +
drivers/dma/Makefile |2
Add new driver for the TI AM65x SoC Gigabit Ethernet Switch subsystem (CPSW
NUSS). It has two ports and provides Ethernet packet communication for the
device and can be configured as an Ethernet switch. CPSW NUSS features: the
Reduced Gigabit Media Independent Interface (RGMII), Reduced Media
Hi All,
This series is the next try to add DMA channels support for DMA controllers
which last version was posted by Álvaro Fernández Rojas [1].
i've kept version numbering.
Comparing to the original post I've added few changes:
- added possibility to pass DMA driver/channel's specific data per
From: Álvaro Fernández Rojas
This adds channels support for dma controllers that have multiple channels
which can transfer data to/from different devices (enet, usb...).
DMA channle API:
dma_get_by_index()
dma_get_by_name()
dma_request()
dma_free()
dma_enable()
dma_disable()
From: Álvaro Fernández Rojas
Move dma_ops to a separate header file, following other uclass
implementations. While doing so, this patch also improves dma_ops
documentation.
Reviewed-by: Tom Rini
Reviewed-by: Simon Glass
Signed-off-by: Álvaro Fernández Rojas
Signed-off-by: Grygorii Strashko
Check that the memory area containing the device tree is marked as runtime
data.
Signed-off-by: Heinrich Schuchardt
---
lib/efi_selftest/efi_selftest_memory.c | 24
1 file changed, 24 insertions(+)
diff --git a/lib/efi_selftest/efi_selftest_memory.c
We currently place the flattened device tree 127 MiB from the start of the
first memory bank. This may be in a reserved memory area.
So let's change the sequence: first create memory reservations and then
copy the device tree.
Do not use any magic address.
Signed-off-by: Heinrich Schuchardt
In copy_fdt() we allocate EFI pages for the fdt plus extra 12 KiB as
EFI_RUNTIME_SERVICES_DATA. Afterwards in efi_install_fdt() we overwrite
part of this memory allocation by marking it as EFI_BOOT_SERVICES_DATA.
Remove the code marking the fdt as EFI_BOOT_SERVICES_DATA.
Cf. commit 17ff6f02f5ad
If a memory bank is not EFI_PAGE_SIZE aligned efi_add_known_memory() the
number of memory pages may be incorrectly calculated.
We have to round up the start address and to round down the end address
to determine which complete pages are provided by the memory bank.
Signed-off-by: Heinrich
The "Devicetree Specification 0.2" does not prescribe that memory
reservations must be EFI page aligned. So let's not make such an
assumption in our code.
Do not carve out the pages for the device tree. This memory area is
already marked as EFI_RUNTIME_SERVICES_DATA.
Signed-off-by: Heinrich
When allocating EFI memory pages the size in bytes has to be converted to
pages.
Provide a macro efi_size_in_pages() for this conversion.
Use it in the EFI subsystem and correct related comments.
Signed-off-by: Heinrich Schuchardt
---
cmd/bootefi.c | 15 ++-
The sandbox is using a virtual address space. The addresses used insided
the flattened device tree use the virtual address space. The EFI subsystem
uses the addressable address space and this is where the fdt is stored.
Fix all incorrect addresses for the fdt.
Signed-off-by: Heinrich Schuchardt
This patch series fixes several errors in the handling of addresses on the
sandbox when setting up the flattened device tree.
The memory type used for the fdt is corrected. It is checked by a unit
test.
A macro is supplied to calculate the numbers of pages needed for a buffer.
Heinrich
In efi_find_free_memory() the sandbox uses its virtual address space.
Add the missing mapping.
Signed-off-by: Heinrich Schuchardt
---
lib/efi_loader/efi_memory.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/lib/efi_loader/efi_memory.c b/lib/efi_loader/efi_memory.c
index
On the sandbox the memory addresses in the device tree refer to the virtual
address space of the sandbox. This implies that the memory reservations for
the fdt also have to be converted to this address space.
Signed-off-by: Heinrich Schuchardt
---
common/fdt_support.c | 7 +--
1 file
The terminal escape sequence ESC [ ; H is used to set the cursor
position. According to the ECMA 48 standard the upper left corner in the
escape sequences is [1, 1]. The video uclass uses [0, 0] as upper left
corner.
Signed-off-by: Heinrich Schuchardt
---
v3:
update unit test
v2
Hi Heinrich,
On Sat, Nov 10, 2018 at 4:10 PM Heinrich Schuchardt wrote:
>
> For colibri_vf_defconfig u-boot-nodtb.bin exceeds file size limit.
>
> Disable CONFIG_EFI_UNICODE_CAPITALIZATION for vf610-colibri_vf61 to save a
> few KiB.
>
> Signed-off-by: Heinrich Schuchardt
> ---
> Cf.
For colibri_vf_defconfig u-boot-nodtb.bin exceeds file size limit.
Disable CONFIG_EFI_UNICODE_CAPITALIZATION for vf610-colibri_vf61 to save a
few KiB.
Signed-off-by: Heinrich Schuchardt
---
Cf. https://travis-ci.org/xypron2/u-boot/jobs/453298845
---
configs/colibri_vf_defconfig | 1 +
1 file
On Tue, Nov 06, 2018 at 11:42:11PM +0100, Marek Vasut wrote:
> This patch adds check for command response CRC failure. The driver
> is currently ignoring CRC check failure on command resposes which
> have CRC atteched to it, which can be potentially dangerous. Even
> more grueling problem happens
On Tue, Feb 13, 2018 at 04:07:55PM +0800, Jun Nie wrote:
> Build ymodem only on need to shrink spl image size.
>
> Signed-off-by: Jun Nie
Applied to u-boot/master, thanks!
--
Tom
signature.asc
Description: PGP signature
___
U-Boot mailing list
Intel Tangier SoC has RTC inside. So, enable it in ACPI.
Signed-off-by: Andy Shevchenko
---
arch/x86/include/asm/arch-tangier/acpi/platform.asl | 13 +
1 file changed, 13 insertions(+)
diff --git a/arch/x86/include/asm/arch-tangier/acpi/platform.asl
Make the indentation aligned with what used elsewhere in U-Boot.
No functional change intended.
Signed-off-by: Andy Shevchenko
---
.../include/asm/arch-tangier/acpi/southcluster.asl | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git
On 10.11.18 13:35, Marek Vasut wrote:
On 11/10/2018 09:37 AM, Jan Kiszka wrote:
Hi all,
I'm getting significant speed differences while loading kernel and
initrd from an ext4 rootfs on an SD card via the 'load' command:
## Executing script at 8000
54764 bytes read in 296 ms (180.7 KiB/s)
Hi Bin,
On Wed, 2018-10-10 at 22:06 -0700, Bin Meng wrote:
> Currently the comments of several APIs (eg: dm_init_and_scan()) say:
>
> @pre_reloc_only: If true, bind only drivers with the
> DM_FLAG_PRE_RELOC
> flag. If false bind all drivers.
>
> The 'Pre-Relocation Support' chapter in
On 10.11.2018 09:37, Jan Kiszka wrote:
Hi all,
I'm getting significant speed differences while loading kernel and
initrd from an ext4 rootfs on an SD card via the 'load' command:
## Executing script at 8000
54764 bytes read in 296 ms (180.7 KiB/s)
12359688 bytes read in 42982 ms (280.3
On 11/10/2018 09:37 AM, Jan Kiszka wrote:
> Hi all,
>
> I'm getting significant speed differences while loading kernel and
> initrd from an ext4 rootfs on an SD card via the 'load' command:
>
> ## Executing script at 8000
> 54764 bytes read in 296 ms (180.7 KiB/s)
> 12359688 bytes read in
On Sat, 10 Nov 2018 16:57:07 +0530
Jagan Teki wrote:
> On Sat, Nov 10, 2018 at 4:54 PM Boris Brezillon
> wrote:
> >
> > On Sat, 10 Nov 2018 15:02:05 +0530
> > Jagan Teki wrote:
> >
> > > On Mon, Nov 5, 2018 at 2:07 PM Jagan Teki
> > > wrote:
> > > >
> > > > On Wed, Oct 31, 2018 at 3:38
On Sat, Nov 10, 2018 at 4:54 PM Boris Brezillon
wrote:
>
> On Sat, 10 Nov 2018 15:02:05 +0530
> Jagan Teki wrote:
>
> > On Mon, Nov 5, 2018 at 2:07 PM Jagan Teki
> > wrote:
> > >
> > > On Wed, Oct 31, 2018 at 3:38 PM Boris Brezillon
> > > wrote:
> > > >
> > > > Hello,
> > > >
> > > > Stefan
On Sat, 10 Nov 2018 15:02:05 +0530
Jagan Teki wrote:
> On Mon, Nov 5, 2018 at 2:07 PM Jagan Teki wrote:
> >
> > On Wed, Oct 31, 2018 at 3:38 PM Boris Brezillon
> > wrote:
> > >
> > > Hello,
> > >
> > > Stefan recently reported a bug when using ubi part on a spi-nand
> > > device and proposed
dfu_fill_entity_nand() uses find_dev_and_part() and mtdparts_init()
which are provided by cmd/mtdparts.c.
Add the dependency to avoid build failures when CMD_MTDPARTS is not
selected.
Reported-by: Jagan Teki
Fixes: 6828e602b722d ("dfu: Migrate to Kconfig")
Signed-off-by: Boris Brezillon
---
The gwventana platform was relying on CMD_UBI to select CMD_MTDPARTS,
which was then making {MTDIDS,MTDPARTS}_DEFAULT available.
Now that UBI no longer selects CMD_MTDPARTS, we end up with a build
failure because those defaults are not defined.
Fix that by making adjusting the depends on of these
On Mon, Nov 5, 2018 at 2:07 PM Jagan Teki wrote:
>
> On Wed, Oct 31, 2018 at 3:38 PM Boris Brezillon
> wrote:
> >
> > Hello,
> >
> > Stefan recently reported a bug when using ubi part on a spi-nand
> > device and proposed this fix[1]. While his solution while working
> > I proposed a different
Hi all,
I'm getting significant speed differences while loading kernel and
initrd from an ext4 rootfs on an SD card via the 'load' command:
## Executing script at 8000
54764 bytes read in 296 ms (180.7 KiB/s)
12359688 bytes read in 42982 ms (280.3 KiB/s)
4333462 bytes read in 441 ms (9.4
36 matches
Mail list logo
