Am 05.03.2015 um 16:32 schrieb Tom Rini:
On Sun, Mar 01, 2015 at 12:44:39PM +0100, Kamil Lulko wrote:
Signed-off-by: Kamil Lulko re...@wp.pl
[snip]
diff --git a/arch/arm/lib/crt0.S b/arch/arm/lib/crt0.S
[snip]
@@ -66,15 +69,30 @@ ENTRY(_main)
#else
ldr sp,
Hi,
Am 28.05.2015 um 23:49 schrieb Naitik Amin:
I am using Altera SOC, under my includes, I have a file called
/include/configs/socfpga_common.h
In this file, I have #define as below.
#define PHYS_SDRAM_1_SIZE 0x2000
If this #define is set to 0x2000, and uboot is
Am 23.07.2015 um 13:46 schrieb Andreas Färber:
Am 09.07.2015 um 09:32 schrieb Alexandre Courbot:
Tegra124 requires the bootloader to perform VPR initialization, otherwise the
GPU cannot be used by the system. Since using the GPU without that
initialization results in a hang, the GPU DT node
Hi,
Am 23.07.2015 um 16:10 schrieb Ruchika Gupta:
Signed-off-by: Ruchika Gupta ruchika.gu...@freescale.com
[...]
diff --git a/drivers/crypto/fsl/Makefile b/drivers/crypto/fsl/Makefile
index 4aa91e4..fd736cf 100644
--- a/drivers/crypto/fsl/Makefile
+++ b/drivers/crypto/fsl/Makefile
@@ -1,9
chips.
Tested-by: Andreas Färber afaer...@suse.de
I've tested this patchset on v2015.07 with 4.2.0-rc3-00115-gc5dfd65 -
with these two patches I get a console login on HDMI again.
However, I'm still having trouble with X11... Should that be working
with linux.git? (haven't tried linux-next.git yet
Am 23.07.2015 um 13:46 schrieb Andreas Färber:
Salut Alexandre,
Am 09.07.2015 um 09:32 schrieb Alexandre Courbot:
Tegra124 requires the bootloader to perform VPR initialization, otherwise the
GPU cannot be used by the system. Since using the GPU without that
initialization results in a hang
Dear Wolfgang,
Am 15.07.2015 um 14:51 schrieb Wolfgang Denk:
In message 593aef6c47f46446852b067021a273d6fbc78...@mucse037.lantiq.com you
wrote:
I tried to find a way to download a file with wget or a similar tool, which
would be used by a distribution builder (like Yocto, Buildroot,
Hi Tom,
Am 12.10.2015 um 17:18 schrieb Tom Rini:
> If you have a regression, speak up.
For -rc4 I had reported that CONFIG_API is broken for sunxi among
others. I was told this was fallout of the new Driver Model. Has anyone
thought about how to fix this? Is that already a lost cause for
Am 15.10.2015 um 02:40 schrieb Tom Rini:
> On Thu, Oct 15, 2015 at 02:28:34AM +0200, Andreas Färber wrote:
>> Am 12.10.2015 um 17:18 schrieb Tom Rini:
>>> If you have a regression, speak up.
>>
>> For -rc4 I had reported that CONFIG_API is broken for sun
Hi Marcin,
Am 07.10.2015 um 15:58 schrieb Marcin Krzemiński:
> Since I use qemu it
> is very hard to debug with gdb u-boot after relocation( or I do not know
> how to do it), so I am almost blind.
QEMU has a built-in gdb stub that you can just connect to as gdb remote
target, similar to how you
for the first MMC device in group 3.
Fix this by properly setting the "more" argument also in the case of the
first storage device of a group.
Signed-off-by: Andreas Färber <afaer...@suse.de>
---
api/api_storage.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/api/api
Hi,
For at least Bananapi, Cubieboard, Cubieboard2, Cubietruck, Mele_A1000,
A10-OLinuXino-Lime, A13-OLinuXino, A20-OLinuXino-Lime2 and probably
other sunxi boards, enabling CONFIG_API in the distro defaults header
leads to build failures like this one:
[ 105s] CC api/api_net.o
[ 105s]
Am 04.01.2016 um 19:03 schrieb Andreas Färber:
> Am 04.01.2016 um 17:56 schrieb Tom Rini:
>> Please note that with the generic distro framework U-Boot will grok
>> https://wiki.freedesktop.org/www/Specifications/BootLoaderSpec/ and
>> things Just Work. I setup a bunch of
Am 04.01.2016 um 17:56 schrieb Tom Rini:
> Please note that with the generic distro framework U-Boot will grok
> https://wiki.freedesktop.org/www/Specifications/BootLoaderSpec/ and
> things Just Work. I setup a bunch of SD cards with Debian and Fedora
> over holiday so I can drop them in whatever
Am 25.12.2015 um 10:02 schrieb Alexander Graf:
[snip]
> The reason I implemented "bootefi" was really because it's the natural
> fit into how U-Boot handles all other formats today. I don't think this
> is going to be the last patch set around EFI support.
I think what Matwey was suggesting is
Am 22.12.2015 um 14:57 schrieb Alexander Graf:
> diff --git a/lib/efi_loader/efi_boottime.c b/lib/efi_loader/efi_boottime.c
> new file mode 100644
> index 000..ed95962
> --- /dev/null
> +++ b/lib/efi_loader/efi_boottime.c
[...]
> +/*
> + * The "gd" pointer lives in a register on ARM and
settings.
>
> Cc: Wolfgang Denk <w...@denx.de>
> Cc: Heiko Schocher <h...@denx.de>
> Cc: Tom Rini <tr...@ti.com>
> Cc: Daniel Schwierzeck <daniel.schwierz...@gmail.com>
> Cc: Andreas Färber <afaer...@suse.de>
Actually I have no clue about Travis...
Cheers
Hi Mateusz,
Am 20.01.2016 um 23:00 schrieb Mateusz Kulikowski:
> On 20.01.2016 05:35, Simon Glass wrote:
>> Tested-by: Simon Glass
>
> Great!
Which Git branch can we use to test this? I spotted no final v1 branch
matching this series. Among others, I tried your
It has been superseded in kwbimage.cfg in favor of an SPL in commit
9e30b31d20f0b793465d07f056b3d9885f578c0d (arm: mvebu: db-88f6820: Add
SPL support with DDR init code). Found via code review.
Cc: Stefan Roese <s...@denx.de>
Signed-off-by: Andreas Färber <afaer...@suse.de>
---
boar
Am 15.03.2016 um 18:21 schrieb Alexander Graf:
> The bcm2835 frame buffer is in RAM, so we can easily map it as cached and gain
> all the glorious performance boost that brings with it.
>
> Signed-off-by: Alexander Graf
> ---
> drivers/video/bcm2835.c | 6 ++
> 1 file
Am 15.03.2016 um 18:21 schrieb Alexander Graf:
> We want to be able to reuse device drivers from 32bit code, so let's add
> definitions for all the dcache options that 32bit code has.
>
> While at it, fix up the DCACHE_OFF configuration. That was setting the bits
> to declare a PTE a PTE and left
Tracing the arguments has been helpful for pinpointing overflows.
Cc: Alexander Graf <ag...@suse.de>
Signed-off-by: Andreas Färber <afaer...@suse.de>
---
lib/efi_loader/efi_memory.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/lib/efi_loader/efi_memory.c b/lib/efi_loader/
jetson-tk1 has 2 GB of RAM at 0x8000, causing gd->ram_top to be zero.
Handle this by replacing it with 0x1 in that case.
Cc: Alexander Graf <ag...@suse.de>
Signed-off-by: Andreas Färber <afaer...@suse.de>
---
lib/efi_loader/efi_memory.c | 4 ++--
1 file changed, 2 i
Am 13.04.2016 um 07:50 schrieb Alexander Graf:
>> Am 13.04.2016 um 05:24 schrieb Andreas Färber <afaer...@suse.de>:
>>
>> jetson-tk1 has 2 GB of RAM at 0x8000, causing gd->ram_top to be zero.
>> Handle this by replacing it with 0x1 in that case.
>
Some variables for the distro boot commands were missing, using some
custom name instead. Rename them.
Cc: Mateusz Kulikowski <mateusz.kulikow...@gmail.com>
Signed-off-by: Andreas Färber <afaer...@suse.de>
---
include/configs/dragonboard410c.h | 8
1 file changed, 4 inse
Hi Daniel,
Am 13.04.2016 um 14:16 schrieb Andreas Färber:
> Some variables for the distro boot commands were missing, using some
> custom name instead. Rename them.
>
> Cc: Mateusz Kulikowski <mateusz.kulikow...@gmail.com>
> Signed-off-by: Andreas Färber <afaer...@s
jetson-tk1 has 2 GB of RAM at 0x8000, causing gd->ram_top to be zero.
Handle this by either avoiding ram_top or by using the same type as
ram_top to reverse the overflow effect.
Cc: Alexander Graf <ag...@suse.de>
Signed-off-by: Andreas Färber <afaer...@suse.de>
---
com>
Cc: Alexander Graf <ag...@suse.de>
Signed-off-by: Andreas Färber <afaer...@suse.de>
---
include/configs/jetson-tk1.h | 4
1 file changed, 4 insertions(+)
diff --git a/include/configs/jetson-tk1.h b/include/configs/jetson-tk1.h
index 59dbb20..82a4be4 100644
--- a/include/co
inux that comes after would happily find
> it - around the recommended 128MB line.
>
> Signed-off-by: Alexander Graf <ag...@suse.de>
Tested-by: Andreas Färber <afaer...@suse.de>
It definitely avoids a warning message. However, it does not always
allow Linux to actually
escending order, so let's just
> reverse it when we pass it to a payload.
>
> Signed-off-by: Alexander Graf <ag...@suse.de>
Tested-by: Andreas Färber <afaer...@suse.de>
This fixed clearfog for me.
Thanks,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
e attributes.
>
> Reported-by: Marek Vasut <ma...@denx.de>
> Signed-off-by: Alexander Graf <ag...@suse.de>
Reviewed-by: Andreas Färber <afaer...@suse.de>
Tested-by: Andreas Färber <afaer...@suse.de>
Thanks,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg,
Am 13.04.2016 um 14:48 schrieb Andreas Färber:
> The 4.5.0 kernel cannot cope with U-Boot's internal device tree, and the
> distro boot commands are looking for $fdtfile, so provide it to avoid
> having users supply a dumb boot.scr doing a setenv fdtfile ...; boot,
> defeating
Am 13.04.2016 um 14:51 schrieb Andreas Färber:
> Am 11.04.2016 um 23:51 schrieb Alexander Graf:
>> The uEFI spec doesn't dictate where the device tree should live at, but
>> legacy 32bit ARM grub2 has some assumptions that it may stay at its place
>> when it's already l
ame device tree for U-Boot
> and Linux we can just share it and there's no need to manually provide
> a device tree in the target image.
>
> While at it, also copy and pad the device tree by 64kb to give us
> space for modifications.
>
> Signed-off-by: Alexander Graf <ag...@sus
oader: Pass file path to payload
> efi_loader: Increase path string to 32 characters
> distro: Enable iso partition code
Tested-by: Andreas Färber <afaer...@suse.de>
Doesn't break the regular EFI boot path for me.
Regards,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnbe
NFIG_BAUDRATE 115200
I had tested a similar patch, so
Reviewed-by: Andreas Färber <afaer...@suse.de>
Thanks,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
Am 04.04.2016 um 09:32 schrieb Alexander Graf:
> The cache line flush helpers only work properly when they get aligned
> start and end addresses. Round our flush range to cache line size. It's
> safe because we're guaranteed to flush within a single page which has the
> same cache attributes.
>
>
Hello,
v2016.01 is the last release to boot Linux on the Firefly-RK3288 for me.
On v2016.03 or master there is no output from the kernel.
This coincides with the DRAM getting misdetected as 512 MiB:
U-Boot SPL 2016.03-00634-g563d8d9 (Apr 03 2016 - 16:29:17)
Trying to boot from MMC1
U-Boot
Am 03.04.2016 um 05:56 schrieb Stephen Warren:
> Now that rpi_*defconfig and Kconfig rather than the config header file,
"rpi*_defconfig"?
Also the sentence seems to be missing a verb - "Now that we use ..."?
> provide the identify of the build, we don't need to separate config
"identity"?
>
Am 03.04.2016 um 21:59 schrieb Alexander Graf:
>> Am 03.04.2016 um 21:32 schrieb Andreas Färber <afaer...@suse.de>:
>>> Am 03.04.2016 um 18:05 schrieb Andreas Färber:
>>> v2016.01 is the last release to boot Linux on the Firefly-RK3288 for me.
>>> On v20
Am 03.04.2016 um 18:05 schrieb Andreas Färber:
> v2016.01 is the last release to boot Linux on the Firefly-RK3288 for me.
> On v2016.03 or master there is no output from the kernel.
Correction: Plain v2016.03 does work but not openSUSE's package.
> This coincides with the DRA
Am 05.04.2016 um 01:54 schrieb Daniel Glöckner:
> On Tue, Apr 05, 2016 at 01:13:38AM +0200, Andreas Färber wrote:
>> Am 31.03.2016 um 23:12 schrieb Mateusz Kulikowski:
>>> +/* Environment */
>>> +#define CONFIG_EXTRA_ENV_SETTINGS \
>>> + "reflash=&
Am 04.04.2016 um 17:36 schrieb Stephen Warren:
> On 04/03/2016 09:41 AM, Andreas Färber wrote:
>> Am 03.04.2016 um 05:56 schrieb Stephen Warren:
>>> Now that rpi_*defconfig and Kconfig rather than the config header file,
>>
>> "rpi*_defconfig"?
>
Am 31.03.2016 um 23:12 schrieb Mateusz Kulikowski:
> diff --git a/include/configs/dragonboard410c.h
> b/include/configs/dragonboard410c.h
> new file mode 100644
> index 000..a63440f
> --- /dev/null
> +++ b/include/configs/dragonboard410c.h
[...]
> +#include
> +
> +/* BOOTP options */
>
Am 13.04.2016 um 15:15 schrieb Alexander Graf:
> On 04/13/2016 02:58 PM, Andreas Färber wrote:
>> Am 11.04.2016 um 16:55 schrieb Alexander Graf:
>>> When the user did not pass any device tree or the boot script
>>> didn't find any, let's use the system device tre
Am 13.04.2016 um 17:31 schrieb Stephen Warren:
> On 04/13/2016 06:55 AM, Andreas Färber wrote:
>> Am 13.04.2016 um 14:48 schrieb Andreas Färber:
>>> The 4.5.0 kernel cannot cope with U-Boot's internal device tree, and the
>>> distro boot commands are looking for $fdtf
Am 13.04.2016 um 20:47 schrieb Alexander Graf:
> load mmc 0 $fdt_addr_r my_awesome.dtb ;\
> load mmc 0 $kernel_addr_r some/random/path/grub2.efi ;\
> bootefi $kernel_addr_r
If we're going in that direction, I would rather pass $fdt_addr_r as
second optional argument to bootefi. That would
Am 13.04.2016 um 19:58 schrieb Stephen Warren:
> On 04/13/2016 11:42 AM, Andreas Färber wrote:
>> Am 13.04.2016 um 19:00 schrieb Stephen Warren:
>>> Anyway, nothing in your benefits-of-EFI statement implies that relying
>>> on $fdtfile being set is correct. That's a
Hi,
Am 13.04.2016 um 19:08 schrieb Angelo Dureghello:
> This patch allows to read back the EXT_CSD[179] partition_config
> register, just specifiing the dev param:
"specifying"
>
> linkmotion> mmc partconf 0
> EXT_CSD[179], PARTITION_CONFIG register:
> BOOT_ACK: 0
> BOOT_PARTITION_ENABLE: 0
>
Am 13.04.2016 um 19:00 schrieb Stephen Warren:
> On 04/13/2016 09:51 AM, Alexander Graf wrote:
>> On 04/13/2016 05:31 PM, Stephen Warren wrote:
>>> On 04/13/2016 06:55 AM, Andreas Färber wrote:
>>>> Am 13.04.2016 um 14:48 schrieb Andreas Färber:
>>>>&g
Am 13.04.2016 um 19:40 schrieb Stephen Warren:
> On 04/13/2016 11:22 AM, Andreas Färber wrote:
>> Am 13.04.2016 um 17:31 schrieb Stephen Warren:
>>> On 04/13/2016 06:55 AM, Andreas Färber wrote:
>>>> Am 13.04.2016 um 14:48 schrieb Andreas Färber:
>>>>&g
Am 15.04.2016 um 12:59 schrieb Heiko Schocher:
> Fix following warnings for all mips based boards:
> mips: + pic32mzdask
> +Warning (unit_address_vs_reg): Node /memory has a reg or ranges property,
> but no unit name
> +Warning (unit_address_vs_reg): Node /cpus/cpu@0 has a unit name, but
Am 18.04.2016 um 09:55 schrieb Yoshinori Sato:
> Signed-off-by: Yoshinori Sato
> ---
> common/env_ext4.c | 20 +++-
> 1 file changed, 11 insertions(+), 9 deletions(-)
>
> diff --git a/common/env_ext4.c b/common/env_ext4.c
> index ce748ed..5683890
$subject: "standard"
Regards,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
___
U-Boot mailing list
U-Boot@lists.denx.de
Am 17.04.2016 um 09:48 schrieb Beniamino Galvani:
> All members of the DMA descriptor must be 32-bit, even on 64-bit
> architectures: change the type to u32 to ensure this. Also, fix
> other warnings.
>
> Signed-off-by: Beniamino Galvani
> ---
> drivers/net/designware.c |
;\
> "load ${devtype} ${devnum}:${distro_bootpart} " \
> "${kernel_addr_r} efi/boot/"BOOTEFI_NAME"; " \
>
VARS_UBOOT_CONFIG instead of runtime config
> - s/efifdtfile/efi_fdtfile/g
Otherwise
Reviewed-by: Andreas Färber <afaer...@suse.de>
ARM64 can be handled as follow-up.
Thanks,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham
Am 13.04.2016 um 23:22 schrieb Alexander Graf:
> When there is no $fdtfile variable set, we still have a good chance
> that on 32bit arm the fdtfile really is just called $soc-$board.dtb.
>
> Enable the exports for $soc and $board in our distr defaults and make
> use of them in the efi boot
Am 13.04.2016 um 20:51 schrieb Stephen Warren:
> On 04/13/2016 12:17 PM, Andreas Färber wrote:
>> Am 13.04.2016 um 19:58 schrieb Stephen Warren:
>>> On 04/13/2016 11:42 AM, Andreas Färber wrote:
>>>> Am 13.04.2016 um 19:00 schrieb Stephen Warren:
>>>>
Am 14.04.2016 um 18:56 schrieb Angelo Dureghello:
> On 14/04/2016 01:16, Marek Vasut wrote:
>> On 04/14/2016 01:11 AM, Angelo Dureghello wrote:
>>> diff --git a/include/mmc.h b/include/mmc.h
>>> index cdb56e7..4b34b31 100644
>>> --- a/include/mmc.h
>>> +++ b/include/mmc.h
>>> @@ -222,6 +222,10 @@
Am 14.04.2016 um 00:05 schrieb Tom Rini:
> On Wed, Apr 13, 2016 at 08:02:24PM +0200, Andreas Färber wrote:
>> my point was that U-Boot != Linux filename in some cases. For
>> example, the dragonboard410c is using dragonboard410c.dts but in Linux
>> it's qcom/apq8016-sbc.dts.
Am 13.04.2016 um 23:22 schrieb Alexander Graf:
> The bootefi cmd today fetches its device tree pointer from either the
> location appointed by "fdt addr" with a fallback to the U-Boot control
> fdt.
>
> This integration is unusual for U-Boot and diverges from the way we
> usually handle
by: Kever Yang <kever.y...@rock-chips.com>
> Acked-by: Simon Glass <s...@chromium.org>
> ---
>
> Changes in v5:
> - add file source and detail changes for U-Boot
>
> Changes in v4: None
> Changes in v3: None
> Changes in v2: None
Reviewed-by: Andreas Färber
Hi Simon,
Am 23.07.2016 um 04:31 schrieb Simon Glass:
> On 18 July 2016 at 06:13, Heiko Stübner <he...@sntech.de> wrote:
>> Am Montag, 18. Juli 2016, 03:06:07 schrieb Andreas Färber:
>>> diff --git a/arch/arm/mach-rockchip/Kconfig b/arch/arm/mach-rockchip/Kconfig
>>&
Hi Keerthy,
Am 01.08.2016 um 12:07 schrieb Keerthy:
> I am trying to enable hypervisor in u-boot for DRA7(A15 based) family of
> SoCs which does not have LPAE support yet.
>
> Is it mandatory for LPAE to be enabled before enabling hypervisor for A15?
On the Linux kernel side you can't enable
Am 12.07.2016 um 09:29 schrieb Alexander Graf:
> On 12.07.16 06:21, Andreas Färber wrote:
>> On arm64 Linux device trees are organized by SoC vendor. Therefore we
>> need to search the vendor subdirectory as well.
>>
>> Since the SoC vendor may be different from
Am 12.07.2016 um 09:30 schrieb Alexander Graf:
> On 12.07.16 06:21, Andreas Färber wrote:
>> We do so for the EFI binary already and it aids debugging.
>>
>> Cc: Alexander Graf <ag...@suse.de>
>> Signed-off-by: Andreas Färber <afaer...@suse.de>
>>
Am 12.07.2016 um 09:25 schrieb Alexander Graf:
>
>
> On 12.07.16 06:21, Andreas Färber wrote:
>> A UEFI setup will typically have an EFI FAT partition, but device trees
>> are more likely to be located on, e.g., Linux volumes. By convention the
>> EFI partition will
It conflicts with the generic_timer.
Cc: Kever Yang <kever.y...@rock-chips.com>
Signed-off-by: Andreas Färber <afaer...@suse.de>
---
arch/arm/mach-rockchip/Makefile | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/mach-rockchip/Makefile b/arch/arm/mach-rockchip/Ma
Am 14.07.2016 um 05:51 schrieb Kever Yang:
> Add support for rockchip rk33 series Soc like rk3368 and rk3399
>
> Signed-off-by: Kever Yang
> ---
>
> tools/rkcommon.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/tools/rkcommon.c b/tools/rkcommon.c
> index
In preparation for RK3368 and RK3399, which need to select ARM64, don't
select CPU_V7 at the ARCH_ROCKCHIP level but at the SoC level instead.
Cc: Kever Yang <kever.y...@rock-chips.com>
Signed-off-by: Andreas Färber <afaer...@suse.de>
---
arch/arm/Kconfig | 1 -
a
Hi Alex,
Am 05.06.2016 um 23:17 schrieb Alexander Graf:
> If Linux finds an EFI implementation it always uses the EFI reset handler to
> reboot or power down the system.
Hm, I thought my powerdown issues on the Jetson TK1 were for lack of
CONFIG_AS3277_RESET - sounds like it could be due to EFI
Am 17.07.2016 um 06:57 schrieb Andreas Färber:
> Tracing the arguments has been helpful for pinpointing overflows.
>
> Cc: Alexander Graf <ag...@suse.de>
> Signed-off-by: Andreas Färber <afaer...@suse.de>
> ---
> lib/efi_loader/efi_memory.c | 3 +++
> 1 file
Am 15.07.2016 um 10:42 schrieb Kever Yang:
> diff --git a/arch/arm/mach-rockchip/Kconfig b/arch/arm/mach-rockchip/Kconfig
> index d3f5ffd..8499692 100644
> --- a/arch/arm/mach-rockchip/Kconfig
> +++ b/arch/arm/mach-rockchip/Kconfig
> @@ -9,6 +9,10 @@ config ROCKCHIP_RK3288
> video
Am 15.07.2016 um 10:42 schrieb Kever Yang:
> diff --git a/board/rockchip/evb_rk3399/evb-rk3399.c
> b/board/rockchip/evb_rk3399/evb-rk3399.c
> new file mode 100644
> index 000..357b08b
> --- /dev/null
> +++ b/board/rockchip/evb_rk3399/evb-rk3399.c
> @@ -0,0 +1,41 @@
> +/*
> + * (C) Copyright
Am 18.07.2016 um 10:46 schrieb Kever Yang:
> RK3399 is a SoC from Rockchip with dual-core Cortex-A72
> and quad-core Cortex-A53 CPU. It supports two USB3.0
> type-C ports and two USB2.0 EHCI ports. Other interfaces
> are very much like RK3288, the DRAM are 32bit width address
> and support address
Am 18.07.2016 um 10:46 schrieb Kever Yang:
> These files are from kernel upstream with some modification
> need by U-Boot:
> - chosen with stdout-path to uart2.
>
> Signed-off-by: Kever Yang
> Acked-by: Simon Glass
> ---
>
> Changes in v4: None
Hi Kever,
Am 18.07.2016 um 06:54 schrieb Kever Yang:
> Hi Andreas,
>
> Thanks for you comments, I will apply them one by one except some
> confuse below.
>
> On 07/18/2016 07:26 AM, Andreas Färber wrote:
>> Hi,
>>
>> Isn't evb short for eval
Am 15.07.2016 um 10:42 schrieb Kever Yang:
> These files are from kernel upstream with some modification
> need by uboot:
> - chosen with stdout-path to uart2.
Please also mention:
- clock-frequency for uart2
Cost me quite some time to figure out this was necessary...
Regards,
Andreas
>
>
Hi,
Isn't evb short for evaluation board? That makes board board then. ;)
Am 15.07.2016 um 10:42 schrieb Kever Yang:
> RK3399 is a SoC from Rockchip with dual-core Cortex-A72
> and qual-core Cortex-A53 CPU. It supports two USB3.0
quad-core
> type-C ports and two USB2.0 EHCI ports. Other
Unmodified from Linux kernel v4.7-rc6.
Signed-off-by: Andreas Färber <afaer...@suse.de>
---
arch/arm/dts/Makefile |3 +-
arch/arm/dts/rk3368-geekbox.dts| 319 ++
arch/arm/dts/rk3368.dtsi | 1081
incl
will need to
short two pins on the bottom of the module to enter MaskRom mode and
re-flash the loader:
# ./utils/upgrade_tool ul ./lollipop_u-boot/RK3368MiniLoaderAll_V2.40.bin
# ./utils/upgrade_tool di uboot u-boot.img
Signed-off-by: Andreas Färber <afaer...@suse.de>
---
eiko Stübner <he...@sntech.de>
Andreas Färber (2):
dts: Import rk3368-geekbox.dts
ARM64: rockchip: Add initial support for RK3368 based GeekBox
arch/arm/Kconfig |4 -
arch/arm/dts/Makefile |3 +-
arch/arm/dts/rk3368-geekbox.dts| 31
Am 15.07.2016 um 10:42 schrieb Kever Yang:
> diff --git a/include/configs/rk3399_common.h b/include/configs/rk3399_common.h
> new file mode 100644
> index 000..1c13e2e
> --- /dev/null
> +++ b/include/configs/rk3399_common.h
[...]
> +#ifndef CONFIG_SPL_BUILD
> +#include
> +
> +#define
Am 18.07.2016 um 03:06 schrieb Andreas Färber:
> The RK3368 is an octa-core Cortex-A53 SoC from Rockchip.
>
> The GeekBox is a TV box from GeekBuying, based on an MXM3 module.
> The module can be used with base boards such as the GeekBox Landingship.
>
> This adds basic suppo
Tracing the arguments has been helpful for pinpointing overflows.
Cc: Alexander Graf <ag...@suse.de>
Signed-off-by: Andreas Färber <afaer...@suse.de>
---
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/
Hi,
When I boot my Jetson TK1, by default I get this from lspci:
00:02.0 PCI bridge: NVIDIA Corporation TegraK1 PCIe x1 Bridge (rev a1)
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)
If however I plug some mini
Am 20.07.2016 um 10:56 schrieb Robert P. J. Day:
> On Tue, 19 Jul 2016, Tom Rini wrote:
>
>> On Tue, Jul 19, 2016 at 04:15:47AM -0400, Robert P. J. Day wrote:
>>
>>>
>>> kind of a style question but what is the preferred way to define a
>>> board in the sense of what belongs in the defconfig
Am 16.07.2016 um 15:52 schrieb Tom Rini:
> +(pine64_plus)himport_r(_htab, (char *)spl->fel_script_address,
> +(pine64_plus) ^
> w+(pine64_plus) ../board/sunxi/board.c: In function ‘parse_spl_header’:
> w+(pine64_plus) ../board/sunxi/board.c:601:24: warning: cast to
21 insertions(+), 21 deletions(-)
Makes perfect sense to me,
Reviewed-by: Andreas Färber <afaer...@suse.de>
Thanks,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
___
Am 16.07.2016 um 00:21 schrieb Jeremy Hunt:
> As part of the startup process for boards using the SPL, the
> meaning of board_init_f changed such that it should return normally
> rather than calling board_init_r directly. (see
> db910353a126d84fe8dff7a694ea792f50fcfb6a )
> This was fixed in 32-bit
Am 11.07.2016 um 21:48 schrieb Beniamino Galvani:
> On Mon, Jul 11, 2016 at 05:23:15AM +0100, Peter Robinson wrote:
>> On Mon, Jul 11, 2016 at 4:57 AM, Andreas Färber <afaer...@suse.de> wrote:
>>> Last output:
>>>
>>> NOTICE: BL3-1: v1.0(debug):4d2e34d
&g
Am 12.07.2016 um 16:25 schrieb Alexander Graf:
> On 12.07.16 14:45, Andreas Färber wrote:
>> Am 12.07.2016 um 09:30 schrieb Alexander Graf:
>>> On 12.07.16 06:21, Andreas Färber wrote:
>>>> We do so for the EFI binary already and it aids debugging.
>>>&
Am 12.07.2016 um 14:38 schrieb Andreas Färber:
> Am 12.07.2016 um 09:29 schrieb Alexander Graf:
>> On 12.07.16 06:21, Andreas Färber wrote:
>>> On arm64 Linux device trees are organized by SoC vendor. Therefore we
>>> need to search the vendor subdirectory as well.
>&
Am 12.07.2016 um 16:50 schrieb Tom Rini:
> On Tue, Jul 12, 2016 at 06:21:45AM +0200, Andreas Färber wrote:
>
>> On arm64 Linux device trees are organized by SoC vendor. Therefore we
>> need to search the vendor subdirectory as well.
>>
>> Since the SoC vendor
Hi Kever,
Am 20.06.2016 um 04:59 schrieb Kever Yang:
> I want to upstream a new SoC named RK3399 from Rockchip which is
> AARCH64/ARMv8, we need to support Arm Trust Firmware base on U-boot.
>
> Right now we are using a miniloader(just like SPL in U-boot) to load
> ATF/U-boot,
> and PC
Hi,
Am 13.07.2016 um 14:45 schrieb Andre Przywara:
> On 13/07/16 13:27, Andreas Färber wrote:
>> Am 20.06.2016 um 04:59 schrieb Kever Yang:
>>> I want to upstream a new SoC named RK3399 from Rockchip which is
>>> AARCH64/ARMv8, we need to support Arm Tr
Am 11.07.2016 um 22:36 schrieb Carlo Caione:
> On Mon, Jul 11, 2016 at 10:15 PM, Andreas Färber <afaer...@suse.de> wrote:
>> [...]
>> NOTICE: BL3-1: v1.0(debug):4d2e34d
>> NOTICE: BL3-1: Built : 17:08:35, Oct 29 2015
>> INFO:BL3-1: Initializing runtime serv
Am 12.07.2016 um 00:52 schrieb Carlo Caione:
> On Mon, Jul 11, 2016 at 11:38 PM, Andreas Färber <afaer...@suse.de> wrote:
>> Am 11.07.2016 um 22:36 schrieb Carlo Caione:
>>> On Mon, Jul 11, 2016 at 10:15 PM, Andreas Färber <afaer...@suse.de> wrote:
>
eusz Kulikowski <mateusz.kulikow...@gmail.com>
> Signed-off-by: Ricardo Salveti <rsalv...@rsalveti.net>
Reviewed-by: Andreas Färber <afaer...@suse.de>
Tested-by: Andreas Färber <afaer...@suse.de>
Thanks,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF
1 - 100 of 316 matches
Mail list logo