This series of patches add the needed bits for booting the FreeBSD
loader.
FreeBSD loader needs the U-Boot API and dache disabled for it to run so
add kconfig options for them.
Also add some some boot command that locate and run the FreeBSD loader
if found.
Emmanuel Vadot (4):
kconfig: Add API k
Add a kconfig option to disable the data cache.
Signed-off-by: Emmanuel Vadot
---
arch/arm/Kconfig | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
index d7a9b11..59b91a0 100644
--- a/arch/arm/Kconfig
+++ b/arch/arm/Kconfig
@@ -118,6 +118,12 @@ config
Add kconfig file to enable API support
Signed-off-by: Emmanuel Vadot
---
Kconfig | 2 ++
api/Kconfig | 9 +
2 files changed, 11 insertions(+)
create mode 100644 api/Kconfig
diff --git a/Kconfig b/Kconfig
index 1263d0b..6e7c9b0 100644
--- a/Kconfig
+++ b/Kconfig
@@ -335,6 +335,8 @@
Add commands that scans for the FreeBSD loader and run it if found.
FreeBSD has two loader: ubldr which is an ELF binary and ubldr.bin which
is a PIE binary.
Signed-off-by: Emmanuel Vadot
---
include/config_distro_bootcmd.h | 32
1 file changed, 32 insertions(+)
Add a FreeBSD option that enable the API and disable the data cache as
it is needed to boot the FreeBSD loader.
Signed-off-by: Emmanuel Vadot
---
common/Kconfig | 9 +
1 file changed, 9 insertions(+)
diff --git a/common/Kconfig b/common/Kconfig
index 913d21a..73cd205 100644
--- a/common
1;4600;0c
On Mon, Nov 07, 2016 at 09:53:00AM +0800, Chen-Yu Tsai wrote:
> On Mon, Nov 7, 2016 at 1:15 AM, Maxime Ripard
> wrote:
> > On Sat, Nov 05, 2016 at 09:34:25AM +0800, Chen-Yu Tsai wrote:
> >> On Fri, Nov 4, 2016 at 11:18 PM, Maxime Ripard
> >> wrote:
> >> > The sun8i SoCs also have a 8 bi
On Mon, Nov 7, 2016 at 4:39 PM, Maxime Ripard
wrote:
> 1;4600;0c
> On Mon, Nov 07, 2016 at 09:53:00AM +0800, Chen-Yu Tsai wrote:
>> On Mon, Nov 7, 2016 at 1:15 AM, Maxime Ripard
>> wrote:
>> > On Sat, Nov 05, 2016 at 09:34:25AM +0800, Chen-Yu Tsai wrote:
>> >> On Fri, Nov 4, 2016 at 11:18 PM, Max
PWM_ROCKCHIP need to enable for PWM regulator, this config
is missing during rebase and new patch set in previous submission.
Signed-off-by: Kever Yang
---
configs/evb-rk3399_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/configs/evb-rk3399_defconfig b/configs/evb-rk3399_defconfi
Am 07.11.2016 um 09:30 schrieb Kever Yang:
> The size dram node need to be deduced by the same amount of reserved space.
>
>
Reported-by: Andreas Färber
> Signed-off-by: Kever Yang
Reviewed-by: Andreas Färber
Thanks,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF:
Hi Alison,
On 7 November 2016 at 02:21, Alison Wang wrote:
>> On 11/04/2016 10:12 AM, Alexander Graf wrote:
>> >
>> >
>> > On 04/11/2016 17:08, york sun wrote:
>> >> On 11/04/2016 09:53 AM, Alexander Graf wrote:
>> >>>
>> >>>
>> >>> On 04/11/2016 16:43, york sun wrote:
>> On 11/04/2016 09:32
On 05.11.2016 18:41, Masahiro Yamada wrote:
> Hi.
Hi!
>
> 2016-10-31 22:15 GMT+09:00 Stefan Müller-Klieser
> :
>> When building the cross_tools target, HOSTCFLAGS and HOSTLDFLAGS will
>> propagate to the target build. This should not happen and is easy to
>> prevent.
>>
>> Signed-off-by: Stefan
The size dram node need to be deduced by the same amount of reserved space.
Signed-off-by: Kever Yang
---
board/rockchip/evb_rk3399/evb-rk3399.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/board/rockchip/evb_rk3399/evb-rk3399.c
b/board/rockchip/evb_rk3399/evb-rk3399.c
Drop CONFIG_CUSTOM_BOARDINFO as it is not Kconfig compliant and anyway
not really used anywhere plus the upcoming weak show_board_info()
approach seems much superior.
This reverts commit a9ad18c9d5fe2554753b0f9a52adfd5ebce61147.
Signed-off-by: Marcel Ziswiler
Reviewed-by: Tom Rini
Acked-by: Max
Make show_board_info() a weak function which allows for custom board
specific implementations thereof.
Signed-off-by: Marcel Ziswiler
Reviewed-by: Tom Rini
Acked-by: Max Krummenacher
---
Changes in v4: None
Changes in v3:
- introduce new patch making show_board_info() a weak function which
Now with the config block handling in place move the U-Boot environment
location before the config block at the end of 1st "boot sector" as
deployed during production using our downstream BSP.
Signed-off-by: Marcel Ziswiler
Acked-by: Max Krummenacher
---
Changes in v4:
- add various peoples ac
Deactivate CONFIG_DISPLAY_BOARDINFO in favour of
CONFIG_DISPLAY_BOARDINFO_LATE which also displays on the LCD.
Signed-off-by: Marcel Ziswiler
Acked-by: Max Krummenacher
---
Changes in v4: None
Changes in v3:
- fixup deactivation of CONFIG_DISPLAY_BOARDINFO in favour of
CONFIG_DISPLAY_BOARDIN
With our common code in place actually make use of it across all our
modules.
Signed-off-by: Marcel Ziswiler
Acked-by: Max Krummenacher
---
Changes in v4: None
Changes in v3:
- use checkboard() rather than checkboard_fallback()
- drop CUSTOM_BOARDINFO
Changes in v2: None
board/toradex/apali
This series integrates Toradex factory configuration block handling. The
config block is a data structure which gets stored to flash during
production testing. The structure holds such information as board resp.
hardware revision, product ID and serial number which is used as the NIC
part of the E
From: Max Krummenacher
remove now unused CONFIG_TRDX_PID_XXX
Signed-off-by: Marcel Ziswiler
Acked-by: Stefan Agner
Acked-by: Max Krummenacher
---
Changes in v4: None
Changes in v3: None
Changes in v2: None
board/toradex/colibri_vf/colibri_vf.c | 16
include/configs/colibri
Add Toradex factory configuration block handling. The config block is a
data structure which gets stored to flash during production testing. The
structure holds such information as board resp. hardware revision,
product ID and serial number which is used as the NIC part of the
Ethernet MAC address
On Fri, Oct 28, 2016 at 12:32:36PM -0600, Stephen Warren wrote:
> Related, consider the following from the Linux kernel's
> Documentation/arm64/booting.txt:
>
> >- Caches, MMUs
> > The MMU must be off.
> > Instruction cache may be on or off.
> > The address range corresponding to the loaded ker
On Fri, Oct 28, 2016 at 09:35:37PM +, york sun wrote:
> I am struggling on the dcache_disable() which implies all dcache is
> flushed. I don't have a reasonable way to flush all if I want to skip
> L3. I tried to benchmark flushing by VA to cover my entire 16GB memory.
> It took 30+ seconds.
Raspberry firmware used to pass a FDT blob at a fixed address (0x100),
but this is not true anymore. The address now depends on both the
memory size and the blob size [1].
If one wants to passthrough this FDT blob to the kernel, the most
reliable way is to save its address from the r2/x0 register
Hi Fabio.
On 11/06/2016 02:16 PM, Fabio Estevam wrote:
> Hi Sebastien,
>
> On Thu, Nov 3, 2016 at 5:20 PM, Sebastien Bourdelin
> wrote:
>
>> +/* Extra Environment */
>> +#define CONFIG_EXTRA_ENV_SETTINGS \
>> + "fdt_addr=0x4100\0" \
>> + "loadkernel=load mmc ${mmcdev}:${mmcpart}
Hi Sebastien,
On Mon, Nov 7, 2016 at 1:36 PM, Sebastien Bourdelin
wrote:
>
> It's in my todo list yes, but nothing really planned currently, do you
> think i should keep the mx28evk dtb instead?
I am not familar with this board. Do you mean that you use
imx28-evk.dtb to boot it?
IMHO it would b
Hi Alex,
On 19 October 2016 at 01:11, Alexander Graf wrote:
>
>
> On 18/10/2016 22:37, Simon Glass wrote:
>> Hi Alex,
>>
>> On 18 October 2016 at 01:12, Alexander Graf wrote:
>>> On 10/18/2016 04:29 AM, Simon Glass wrote:
This is required for x86 and is also correct for ARM (since it i
Hi Alex,
On 19 October 2016 at 01:07, Alexander Graf wrote:
>
>
> On 18/10/2016 22:37, Simon Glass wrote:
>> Hi Alex,
>>
>> On 4 October 2016 at 09:50, Alexander Graf wrote:
>>>
>>>
>>> Am 04.10.2016 um 17:37 schrieb Simon Glass :
>>>
>>> Hi Alex,
>>>
>>> On 3 October 2016 at 21:15, Alexander Gr
Hi Alex,
On 19 October 2016 at 01:09, Alexander Graf wrote:
>
>
> On 18/10/2016 22:37, Simon Glass wrote:
>> Hi Alex,
>>
>> On 18 October 2016 at 01:14, Alexander Graf wrote:
>>> On 10/18/2016 04:29 AM, Simon Glass wrote:
It is useful to have a basic sanity check for EFI loader support
Hi Leif,
On 20 October 2016 at 02:19, Leif Lindholm wrote:
> On 19 October 2016 at 21:22, Leif Lindholm wrote:
>> On Mon, Oct 17, 2016 at 07:55:02PM -0600, Simon Glass wrote:
>>> Hi Leif,
>>>
>>> On 26 September 2016 at 19:53, Leif Lindholm
>>> wrote:
>>> >> Thanks for the pointer. Unfortunate
Hi Alex,
On 25 October 2016 at 15:33, Alexander Graf wrote:
>
>
> On 10/08/2016 14:56, Simon Glass wrote:
>> Hi Alex,
>>
[...]
#endif
struct efi_device_path;
diff --git a/lib/efi_loader/efi_boottime.c b/lib/efi_loader/efi_boottime.c
index 798b566..e027bd3 100644
--
This series adds EFI loader support for x86. Since U-Boot already supports
running as an EFI app (and as a payload) this is relatively
straightforward, requiring just moving files into place and updating a few
compiler flags.
One problem with the EFI loader is that it lacks even rudimentary test
s
There is a build warning for three x86 boards since
write_smbios_table_wrapper() is not used. Fix it.
Fixes: e824cf3f (smbios: Allow compilation on 64bit systems)
Signed-off-by: Simon Glass
---
Changes in v4: None
Changes in v3: None
Changes in v2: None
arch/x86/lib/tables.c | 2 ++
1 file cha
Make sure that the cache flushes correctly by ensuring that the end
address is correctly aligned.
Signed-off-by: Simon Glass
---
Changes in v4: None
Changes in v3: None
Changes in v2: None
lib/efi_loader/efi_image_loader.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/l
At present we use a CONFIG option in efi.h to determine whether we are
building the EFI stub or not. This means that the same header cannot be
used for EFI_LOADER support. The CONFIG option will be enabled for the
whole build, even when not building the stub.
Use a different define instead, set up
This should use U-Boot's standard format for hex address. Fix it.
Signed-off-by: Simon Glass
---
Changes in v4: None
Changes in v3: None
Changes in v2: None
cmd/bootefi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/cmd/bootefi.c b/cmd/bootefi.c
index c8079c4..3ab256e 10
It is useful to have a basic sanity check for EFI loader support. Add a
'bootefi hello' command which loads HelloWord.efi and runs it under U-Boot.
Signed-off-by: Simon Glass
---
Changes in v4:
- Move hello world test program into new patch
Changes in v3: None
Changes in v2: None
cmd/Kconfig
When building an EFI app we need three things:
- start-up code
- relocation code
- link script
These are all different for each architecture. We also need special
compiler flags in some cases.
Add top-level Makefile variables for these along with documentation.
Signed-off-by: Simon Gla
Rather than hard-coding the relocation type, add it to the ELF header file
and use it from there.
Signed-off-by: Simon Glass
---
Changes in v4: None
Changes in v3: None
Changes in v2: None
arch/arm/lib/relocate.S| 3 ++-
arch/arm/lib/relocate_64.S | 3 ++-
include/elf.h | 13
Add support for EFI apps on aarch64. This includes start-up and relocation
code plus a link script.
Signed-off-by: Simon Glass
---
Changes in v4:
- Add new patch to add EFI app support on aarch64
Changes in v3: None
Changes in v2: None
arch/arm/cpu/armv8/config.mk | 4 ++
arch/arm/lib/c
Add support for EFI apps on ARM. This includes start-up and relocation
code, plus a link script and some compiler setting changes.
Signed-off-by: Simon Glass
---
Changes in v4:
- Add new patch to add EFI app support
Changes in v3: None
Changes in v2: None
arch/arm/config.mk | 7 ++
These files now need to be in a standard place so that they can be located
by generic Makefile rules. Move them to the 'lib' directory.
Signed-off-by: Simon Glass
---
Changes in v4: None
Changes in v3: None
Changes in v2: None
arch/x86/config.mk | 2 +-
arch/x86/{cpu/
It is useful to have a basic sanity check for EFI loader support. Enable
this for ARM.
Signed-off-by: Simon Glass
---
Changes in v4:
- Use the build-generated 'hello world' program instead of a binary blob
Changes in v3:
- Include a link to the program instead of adding it to the tree
- Fix sev
Add compiler flags and make a few minor adjustments to support the efi
loader.
Signed-off-by: Simon Glass
---
Changes in v4:
- Add new patch to adjust EFI files support efi_loader
Changes in v3: None
Changes in v2: None
arch/x86/config.mk | 16
arch/x86/lib/Makef
These files now need to be in a standard place so that they can be located
by generic Makefile rules. Move them to the 'lib' directory.
Signed-off-by: Simon Glass
---
Changes in v4: None
Changes in v3: None
Changes in v2: None
Makefile | 2 +-
arc
Enable this so that EFI applications (notably grub) can be run under U-Boot
on x86 platforms.
At present the 'hello world' EFI application is not supported for the
qemu-x86_efi_payload64 board. That board builds a payload consisting of a
64-bit header and a 32-bit U-Boot, which is incompatible wit
Hi Fabio.
On 11/07/2016 10:43 AM, Fabio Estevam wrote:
> Hi Sebastien,
>
> On Mon, Nov 7, 2016 at 1:36 PM, Sebastien Bourdelin
> wrote:
>>
>> It's in my todo list yes, but nothing really planned currently, do you
>> think i should keep the mx28evk dtb instead?
>
> I am not familar with this boa
On 07/11/2016 10:46, Simon Glass wrote:
Hi Alex,
On 19 October 2016 at 01:09, Alexander Graf wrote:
On 18/10/2016 22:37, Simon Glass wrote:
Hi Alex,
On 18 October 2016 at 01:14, Alexander Graf wrote:
On 10/18/2016 04:29 AM, Simon Glass wrote:
It is useful to have a basic sanity check
Hi Sebastien,
On Mon, Nov 7, 2016 at 2:24 PM, Sebastien Bourdelin
wrote:
> Yes currently i'm using the mainstream Linux kernel using the mx28evk
> defconfig and its Device Tree.
> Obviously not all peripherals are working.
Ok, got it. So that means that having a dedicated ts4600.dts file in
mai
Hi Fabio
On 11/07/2016 11:49 AM, Fabio Estevam wrote:
> Hi Sebastien,
>
> On Mon, Nov 7, 2016 at 2:24 PM, Sebastien Bourdelin
> wrote:
>
>> Yes currently i'm using the mainstream Linux kernel using the mx28evk
>> defconfig and its Device Tree.
>> Obviously not all peripherals are working.
>
>
On 11/06/2016 06:42 PM, Shengzhou Liu wrote:
>
>> -Original Message-
>> From: york sun
>> Sent: Friday, November 04, 2016 11:20 PM
>> To: Shengzhou Liu ; u-boot@lists.denx.de
>> Subject: Re: [PATCH 1/3] fsl/ddr: Revise erratum a009942 and clean related
>> erratum
>>
>> On 11/04/2016 04:18 A
Hi Tom,
The following changes since commit 4b6035da482cccda06aeb419634f99937c9fc783:
mx6sabresd: Make Ethernet functional again (2016-11-06 06:59:27 -0500)
are available in the git repository at:
git://git.denx.de/u-boot-net.git master
for you to fetch changes up to aa555fe9f07a21b3bbdab15
Hi Stephen,
https://patchwork.ozlabs.org/patch/685272/ was applied to u-boot-net.git.
Thanks!
-Joe
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Hi Stephen,
https://patchwork.ozlabs.org/patch/685273/ was applied to u-boot-net.git.
Thanks!
-Joe
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Hi Stephen,
https://patchwork.ozlabs.org/patch/668910/ was applied to u-boot-net.git.
Thanks!
-Joe
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Hi Stephen,
https://patchwork.ozlabs.org/patch/668912/ was applied to u-boot-net.git.
Thanks!
-Joe
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Hi Stephen,
https://patchwork.ozlabs.org/patch/668911/ was applied to u-boot-net.git.
Thanks!
-Joe
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Hi Chris,
https://patchwork.ozlabs.org/patch/689658/ was applied to u-boot-net.git.
Thanks!
-Joe
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Hi Stephen,
https://patchwork.ozlabs.org/patch/668913/ was applied to u-boot-net.git.
Thanks!
-Joe
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Hi Michal,
https://patchwork.ozlabs.org/patch/690374/ was applied to u-boot-net.git.
Thanks!
-Joe
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Hi Ash,
https://patchwork.ozlabs.org/patch/685298/ was applied to u-boot-net.git.
Thanks!
-Joe
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Hi Jim,
On Wed, Nov 2, 2016 at 8:21 AM, James Chargin wrote:
> Hi,
>
> Regarding "invalid" Ethernet address.
>
> Is there a reliable way to set the default environment that will prevent
> Ethernet communications from being attempted.
>
> That is, when an Ethernet capable system is brand new and b
On 10/16/2016 08:58 PM, Yao Yuan wrote:
> Hi York,
>
> It seems arch/arm/cpu/armv8/fsl-layerscape/doc/README.* is better.
> I will update my patch and resend soon.
>
Did you send the update? BTW, I think you meant "deploy QSPI image" in
the subject.
York
On 10/10/2016 11:09 PM, Yuan Yao wrote:
> From: Yuan Yao
>
> Add the address value and size value name for QSPI dts node.
This message doesn't match the change. Do you call "QuadSPI" the address
value name?
>
> Signed-off-by: Yuan Yao
> ---
> arch/arm/dts/ls1021a.dtsi | 1 +
> 1 file changed,
On 10/27/2016 02:47 AM, Calvin Johnson wrote:
> Hi York,
>
>> -Original Message-
>> From: york sun
>> Sent: Wednesday, October 26, 2016 10:09 PM
>> To: Calvin Johnson ; Prabhakar Kushwaha
>> ; Pratiyush
>> Srivastava ; u-boot@lists.denx.de; Mingkai Hu
>>
>> Cc: Hou Zhiqiang
>> Subject:
On 11/07/2016 06:12 AM, Mark Rutland wrote:
> On Fri, Oct 28, 2016 at 09:35:37PM +, york sun wrote:
>> I am struggling on the dcache_disable() which implies all dcache is
>> flushed. I don't have a reasonable way to flush all if I want to skip
>> L3. I tried to benchmark flushing by VA to cover
On 10/25/2016 12:03 AM, Suresh Gupta wrote:
> USB High Speed (HS) EYE Height Adjustment
> USB HS speed eye diagram fails with the default value at
> many corners, particularly at a high temperature
>
> Optimal eye at TXVREFTUNE value to 1001 is observed, change
> set the same vale.
>
> Signed-off-b
On 10/24/2016 01:05 AM, Priyanka Jain wrote:
> Firmware of Management Complex (MC) should be loaded at 512MB aligned
> address.
> So use aligned address for firmware load.
>
> Signed-off-by: Priyanka Jain
> Signed-off-by: Prabhakar Kushwaha
> Signed-off-by: Ashish Kumar
> ---
> drivers/net/fsl-
On 10/17/2016 01:33 AM, shh@gmail.com wrote:
> From: Shaohui Xie
>
> The current value to check whether the PHY was configured has dependency
> on MC, it expects MC to start PCS AN, this is not true during boot up,
> so it should be changed to remove the dependency.
>
> The PHY's register spac
On 10/25/2016 07:10 PM, Yuan Yao wrote:
> From: Yuan Yao
>
> The default configuration for QSPI AHB bus can't support 16MB+.
> But some flash on NXP layerscape board are more than 16MB.
So what do you do?
Is this an erratum workaround? If yes, please refer the erratum number.
>
> Signed-off-by:
On 11/06/2016 06:21 PM, Alison Wang wrote:
>>
> [Alison Wang] Thanks for all your comments.
>
> For the issue about the tree would not be bisect-able, I have
> a solution. Actually it is the root cause that 64-bit kernel could not boot
> up when U-Boot is running in EL2. I will move these codes fro
This commit adds basic support including:
MMC, Serial console
Signed-off-by: Sebastien Bourdelin
---
Changes v1 -> v2:
- remove useless define
- remove eMMC muxing and init which doesn't exist on the TS4600 board
- disable SSP1 and SSP2 clocks settings which are not currently used
Signed-
On 10/11/2016 07:11 AM, M.H. Lian wrote:
>>
>> I got it. But this does not look that good to me. There are two controllers,
>> and
>> bus number should be relative to the controller itself, not system wide. It's
>> definitely right to assign bus number 0 to both PCIe host controllers, as
>> they
On 10/24/2016 12:40 AM, Priyanka Jain wrote:
>
>
>> -Original Message-
>> From: U-Boot [mailto:u-boot-boun...@lists.denx.de] On Behalf Of Zhiqiang
>> Hou
>> Sent: Wednesday, October 12, 2016 2:56 PM
>> To: u-boot@lists.denx.de; albert.u.b...@aribaud.net; york sun
>> ; s...@chromium.org; bme
Hi Joe,
Thanks for your reply.
On 11/07/2016 10:20 AM, Joe Hershberger wrote:
Hi Jim,
On Wed, Nov 2, 2016 at 8:21 AM, James Chargin wrote:
Hi,
Regarding "invalid" Ethernet address.
Is there a reliable way to set the default environment that will prevent
Ethernet communications from being a
Hi,
I found an problem with this patch on the last rev B of the TS4600
due to a DRAM timing issue.
Please do not consider this patch until i post an other one.
Sorry for the noise,
Regards.
On 11/07/2016 02:30 PM, Sebastien Bourdelin wrote:
> This commit adds basic support including:
> MMC, S
The following series moves the contents of arch/arm/cpu/armv7/omap-common to
arch/arm/mach-omap2/ and arch/arm/cpu/armv7{omap[345],am33xx} over to
sub-directories ofarch/arm/mach-omap2/. I thought about moving them all to the
top level but I don't think that will add clarity to the situation. I'v
To start consolidating various TI-related code, introduce the ARCH_OMAP2
symbol. While we have removed omap2-specific boards some time ago,
matching up with the kernel naming here will help overall.
Signed-off-by: Tom Rini
---
arch/arm/Kconfig | 50 --
This moves what was in arch/arm/cpu/armv7/omap-common in to
arch/arm/mach-omap2 and moves
arch/arm/cpu/armv7/{am33xx,omap3,omap4,omap5} in to arch/arm/mach-omap2
as subdirectories. All refernces to the former locations are updated to
the current locations. For the logic to decide what our outputs
With the move to arch/arm/mach-omap2 there are now very few uses of
CONFIG_OMAP_COMMON and further they can all be replaced with
CONFIG_ARCH_OMAP2, so do so.
Signed-off-by: Tom Rini
---
arch/arm/config.mk | 2 +-
arch/arm/include/asm/global_data.h | 2 +-
arch/arm
On 11/07/2016 07:44 AM, Cédric Schieli wrote:
Raspberry firmware used to pass a FDT blob at a fixed address (0x100),
but this is not true anymore. The address now depends on both the
memory size and the blob size [1].
If one wants to passthrough this FDT blob to the kernel, the most
reliable way
On 11/06/2016 03:24 AM, Alexander Graf wrote:
On 05/11/2016 23:01, Stephen Warren wrote:
On 11/02/2016 03:36 AM, Alexander Graf wrote:
The rpi has a pretty simple way of resetting the whole system. All it
takes
is to poke a few registers at a well defined location in MMIO space.
This patch a
On 11/06/2016 10:33 AM, Stefan Brüns wrote:
Support was already implemented, but not hooked up. This fixes several
fails in the test cases.
diff --git a/fs/ext4/ext4fs.c b/fs/ext4/ext4fs.c
/* Adjust len so it we can't read past the end of the file. */
- if (len > filesize)
-
Hi York,
Thanks for your comments!
> -Original Message-
> From: york sun
> Sent: 2016年11月8日 2:33
> To: Priyanka Jain ; Z.Q. Hou
> ; u-boot@lists.denx.de; albert.u.b...@aribaud.net;
> s...@chromium.org; bmeng...@gmail.com; h...@denx.de;
> yamada.masah...@socionext.com; Ruchika Gupta ;
> ed
On 11/07/2016 07:58 PM, Yao Yuan wrote:
> On 11/08/2016 02:27 AM, York Sun wrote:
>> On 10/10/2016 11:09 PM, Yuan Yao wrote:
>>> From: Yuan Yao
>>>
>>> Add the address value and size value name for QSPI dts node.
>>
>> This message doesn't match the change. Do you call "QuadSPI" the address
>> val
On 11/07/2016 07:52 PM, Yuan Yao wrote:
> From: Yuan Yao
>
> Signed-off-by: Yuan Yao
> ---
> Changed in v2:
> Move the readme for QSPI deploy out of only for ls2080aqds.
> ---
> .../arm/cpu/armv8/fsl-layerscape/doc/README.deploy | 44
> ++
> 1 file changed, 44 insertio
Add support for EFI console modes.
Mode 0 is always 80x25 and present by EFI specification.
Mode 1 is always 80x50 and not mandatory.
Mode 2 and above is freely usable.
If the terminal can handle mode 1, we mark it as supported.
If the terminal size is greater than mode 0 and different than mode 1
On 11/08/2016 12:46 PM, York Sun wrote:
> On 11/07/2016 07:58 PM, Yao Yuan wrote:
> > On 11/08/2016 02:27 AM, York Sun wrote:
> >> On 10/10/2016 11:09 PM, Yuan Yao wrote:
> >>> From: Yuan Yao
> >>>
> >>> Add the address value and size value name for QSPI dts node.
> >>
> >> This message doesn't ma
On 11/08/2016 02:27 AM, York Sun wrote:
> On 10/25/2016 07:10 PM, Yuan Yao wrote:
> > From: Yuan Yao
> >
> > The default configuration for QSPI AHB bus can't support 16MB+.
> > But some flash on NXP layerscape board are more than 16MB.
>
> So what do you do?
>
> Is this an erratum workaround? If
From: Yuan Yao
Signed-off-by: Yuan Yao
---
Changed in v2:
Move the readme for QSPI deploy out of only for ls2080aqds.
---
.../arm/cpu/armv8/fsl-layerscape/doc/README.deploy | 44 ++
1 file changed, 44 insertions(+)
create mode 100644 arch/arm/cpu/armv8/fsl-layerscap
On 11/08/2016 02:17 PM, York Sun wrote:
> On 10/16/2016 08:58 PM, Yao Yuan wrote:
> > Hi York,
> >
> > It seems arch/arm/cpu/armv8/fsl-layerscape/doc/README.* is better.
> > I will update my patch and resend soon.
> >
>
> Did you send the update? BTW, I think you meant "deploy QSPI image" in the
>
On 10/30/2016 10:47 AM, Jagan Teki wrote:
> INFO macro make flash table entries more adjustable like
> adding new flash_info attributes, update ID length bytes
> and so on and more over it will sync to Linux way of defining
> flash_info attributes.
>
> - Add JEDEC_ID
> - Add JEDEC_EXT macro
> - Add
On 11/08/2016 02:27 AM, York Sun wrote:
> On 10/10/2016 11:09 PM, Yuan Yao wrote:
> > From: Yuan Yao
> >
> > Add the address value and size value name for QSPI dts node.
>
> This message doesn't match the change. Do you call "QuadSPI" the address
> value name?
>
Yes, I always call QuadSPI as QS
92 matches
Mail list logo
