Hi Masahiro,
On 21.06.2016 07:32, Masahiro Yamada wrote:
As the help message of CONFIG_BOOTDELAY says, CONFIG_BOOTDELAY=-2
means the autoboot with no delay, with no abort check even if
CONFIG_ZERO_BOOTDELAY_CHECK is defined.
To sum up, the autoboot behaves as follows:
[1] CONFIG_BOOTDELAY=0
Hi Masahiro,
On 21.06.2016 07:32, Masahiro Yamada wrote:
Move the bootdelay >= 0 check to the caller, which simplifies
the callees.
Signed-off-by: Masahiro Yamada
Reviewed-by: Stefan Roese
Thanks,
Stefan
Hi Masahiro,
On 21.06.2016 07:32, Masahiro Yamada wrote:
Factor out the same code from the callees to the caller.
Signed-off-by: Masahiro Yamada
Reviewed-by: Stefan Roese
Thanks,
Stefan
___
U-Boot
Hi Masahiro,
On 21.06.2016 07:32, Masahiro Yamada wrote:
Because abortboot_keyed() and abortboot_normal() are not compiled
at the same time, we can rename both of them to __abortboot().
This allows to drop #ifdef from the caller.
Signed-off-by: Masahiro Yamada
As the help message of CONFIG_BOOTDELAY says, CONFIG_BOOTDELAY=-2
means the autoboot with no delay, with no abort check even if
CONFIG_ZERO_BOOTDELAY_CHECK is defined.
To sum up, the autoboot behaves as follows:
[1] CONFIG_BOOTDELAY=0 && CONFIG_ZERO_BOOTDELAY_CHECK=y
autoboot with no delay,
1/6 moves CONFIG_BOOTDELAY for a new SOCFPGA board.
The rest of this series are clean-ups of autoboot code.
Masahiro Yamada (6):
ARM: socfpga: move CONFIG_BOOTDELAY to Kconfig for IS1 board
doc: bootdelay: drop explanation about CONFIG_BOOTDELAY from README
autoboot: remove
Move the bootdelay >= 0 check to the caller, which simplifies
the callees.
Signed-off-by: Masahiro Yamada
---
common/autoboot.c | 22 --
1 file changed, 8 insertions(+), 14 deletions(-)
diff --git a/common/autoboot.c b/common/autoboot.c
index
The same information now exists in common/Kconfig. Do not duplicate
documentation from the point of view of maintainability.
Signed-off-by: Masahiro Yamada
---
README | 17 -
common/Kconfig | 2 ++
2 files changed, 2 insertions(+), 17
Factor out the same code from the callees to the caller.
Signed-off-by: Masahiro Yamada
---
common/autoboot.c | 21 ++---
1 file changed, 10 insertions(+), 11 deletions(-)
diff --git a/common/autoboot.c b/common/autoboot.c
index eb31c88..2d19104
Because abortboot_keyed() and abortboot_normal() are not compiled
at the same time, we can rename both of them to __abortboot().
This allows to drop #ifdef from the caller.
Signed-off-by: Masahiro Yamada
---
common/autoboot.c | 10 +++---
1 file changed, 3
This recently added board missed the tree-wide migration of
CONFIG_BOOTDELAY.
Signed-off-by: Masahiro Yamada
---
configs/socfpga_is1_defconfig | 4 +---
include/configs/socfpga_is1.h | 1 -
2 files changed, 1 insertion(+), 4 deletions(-)
diff --git
On Tuesday 21 June 2016 10:32 AM, Andreas Dannenberg wrote:
> Hi Lokesh--- comment inlined...
>
> On Tue, Jun 21, 2016 at 10:01:54AM +0530, Lokesh Vutla wrote:
>>
>>
>> On Tuesday 21 June 2016 09:04 AM, Andreas Dannenberg wrote:
>>> Adds an API that verifies a signature attached to an image
Hi Aaron,
On 21.06.2016 00:15, Aaron Williams wrote:
I have just been handed the task of cleaning up our U-Boot port to our
ThunderX armv8 chip and am wondering where I should put the files
specific to our chip.
The people who previously worked on the chip created a subdirectory
under u-boot
Hi Lokesh--- comment inlined...
On Tue, Jun 21, 2016 at 10:01:54AM +0530, Lokesh Vutla wrote:
>
>
> On Tuesday 21 June 2016 09:04 AM, Andreas Dannenberg wrote:
> > Adds an API that verifies a signature attached to an image (binary
> > blob). This API is basically a entry to a secure ROM service
On Mon, Jun 20, 2016 at 11:16:28PM +0200, Hans de Goede wrote:
> DISTRO_DEFAULTS is intended to mirror / replace
> include/config_distro_defaults.h.
>
> The intend is for boards which include this file to select this from
> their Kconfig files and when moving setting to Kconfig which are
On Mon, Jun 20, 2016 at 11:03:17PM +0200, Hans de Goede wrote:
> Hi Tom,
>
> Here is the third sunxi pull-req for v2016.07, it
> contains a few misc. fixes, 2 new boards and
> the conversion of the PSCI code to C-code.
>
> The following changes since commit
On Tuesday 21 June 2016 09:04 AM, Andreas Dannenberg wrote:
> Adds an API that verifies a signature attached to an image (binary
> blob). This API is basically a entry to a secure ROM service provided by
> the device and accessed via an SMC call, using a particular calling
> convention.
>
>
From: Daniel Allred
Adds information regarding SPL handling the loading
and processing of secured u-boot images as part of
the second stage boot the SPL does. Introduces the
description of a new interface script in the TI
SECDEV Package which handles the creation and prep
of
Adds an API that verifies a signature attached to an image (binary
blob). This API is basically a entry to a secure ROM service provided by
the device and accessed via an SMC call, using a particular calling
convention.
Signed-off-by: Daniel Allred
Signed-off-by: Andreas
From: Daniel Allred
Add an interface for calling secure ROM APIs across a range of OMAP and
OMAP compatible high-security (HS) device variants. While at it, also
perform minor cleanup/alignment without any change in functionality.
Signed-off-by: Daniel Allred
Adds commands so that when a secure device is in use and the SPL is
built to load a FIT image (with combined U-Boot binary and various
DTBs), these components that get fed into the FIT are all processed to
be signed/encrypted/etc. as per the operations performed by the
secure-binary-image.sh
This patch series is derived from an earlier RFC [1] with (most of the)
feedback implemented that was provided by Simon, Tom, and Lokesh (see change
log at the end). There are still some loose ends namely affecting the make
process (see discussion here [2], maybe Yamada-san has some inputs?) as
From: Daniel Allred
Adds missing flush_dcache_range and invalidate_dcache_range dummy
(empty) placeholder functions to the #else portion of the #ifndef
CONFIG_SYS_DCACHE_OFF, where full implementations of these functions
are defined.
Signed-off-by: Daniel Allred
From: Madan Srinivas
Modify the SPL build procedure for AM437x high-security (HS) device
variants to create a secure u-boot_HS.img FIT blob that contains U-Boot
and DTB artifacts signed (and optionally encrypted) with a TI-specific
process based on the CONFIG_TI_SECURE_DEVICE
Modify the SPL build procedure for AM57xx and DRA7xx high-security (HS)
device variants to create a secure u-boot_HS.img FIT blob that contains
U-Boot and DTB artifacts signed with a TI-specific process based on the
CONFIG_TI_SECURE_DEVICE config option and the externally-provided image
signing
Adds a generic C-callable API for making secure ROM calls on OMAP and
OMAP-compatible devices. This API provides the important function of
flushing the ROM call arguments to memory from the cache, so that the
secure world will have a coherent view of those arguments. Then is
simply calls the
From: Daniel Allred
The next stage boot loader image and the selected FDT can be
post-processed by board/platform/device-specific code, which can include
modifying the size and altering the starting source address before
copying these binary blobs to their final desitination.
Hi Simon,
thanks for the continued feedback. Comments below...
On Mon, Jun 20, 2016 at 04:40:10PM -0600, Simon Glass wrote:
> +Masahiro for the Makefile question
>
> Hi Andreas,
>
> On 17 June 2016 at 10:13, Andreas Dannenberg wrote:
> > Hi Simon,
> > many thanks for your
On 06/20/2016 06:04 PM, Christian Didriksson wrote:
> Hi,
Hi,
>> On 06/20/2016 03:22 PM, Christian Didriksson wrote:
>>> Hi Marek,
>>
>> Hi,
>>
On 06/17/2016 04:39 PM, Christian Didriksson wrote:
> Hi Marek,
Hi
> I applied the two patches you suggested, but got no
2016-06-21 6:16 GMT+09:00 Hans de Goede :
> DISTRO_DEFAULTS is intended to mirror / replace
> include/config_distro_defaults.h.
>
> The intend is for boards which include this file to select this from
> their Kconfig files and when moving setting to Kconfig which are
2016-06-21 6:33 GMT+09:00 Joe Hershberger :
> On Wed, Jun 15, 2016 at 12:33 AM, Masahiro Yamada
> wrote:
>> The subprocess.Popen() does not change the child process's working
>> directory if cwd=None is given. Let's exploit this fact to
On Mon, Jun 20, 2016 at 07:49:30PM +0100, Peter Robinson wrote:
> > It's release day and v2016.07-rc2 is out and on time. I expect to do
> > -rc3 in another two weeks. I've updated git and the tarballs are also
> > up now.
>
> I might be blind but I don't see a tarball here :)
>
On ls2080 we have a separate network fabric component which we need to
shut down before we enter Linux (or any other OS). Along with that also
comes configuration of the fabric using a description file.
Today we always stop and configure the fabric in the boot script and
(again) exit it on device
So far bounce buffers were only used for disk I/O, but network I/O
may suffer from the same problem.
On platforms that have problems doing DMA on high addresses, let's
also bounce outgoing network packets. Incoming ones always already
get bounced.
Signed-off-by: Alexander Graf
Some boards decided not to run ATF or other secure firmware in EL3, so
they instead run U-Boot there. The uEFI spec doesn't know what EL3 is
though - it only knows about EL2 and EL1. So if we see that we're running
in EL3, let's get into EL2 to make payloads happy.
Signed-off-by: Alexander Graf
EFI allows an OS to leverage firmware drivers while the OS is running. In the
generic code we so far had to stub those implementations out, because we would
need board specific knowledge about MMIO setups for it.
However, boards can easily implement those themselves. This patch provides the
We now have EFI support in U-Boot which worked out of the box on all systems
that I tried it on so far. Except for the LS2080ARDB. With this patch set
I can successfully boot grub2 and Linux from there on such a system - even
using PXE.
v3 -> v4:
- Add CONFIG_CMD_FS_GENERIC to defconfig
-
Most new systems in U-Boot these days make use of the generic "distro"
framework which allows a user to have U-Boot scan for a bootable OS
on all available media types.
This patch extends the LS2080ARDB board to use that framework if the
hard coded NOR flash location does not contain a bootable
Some systems may implemente TrustZone (EL3) in U-Boot. Those systems
reserve some memory that U-Boot is aware of as secure.
For those systems, mask out that secure memory in the EFI memory map,
as it's not usable from EL2 or EL1.
Signed-off-by: Alexander Graf
---
When implementing efi loader support, we can expose runtime services
for payloads. One such service is CPU reset.
This patch implements RTS CPU reset support for layerscape systems.
Signed-off-by: Alexander Graf
---
arch/arm/cpu/armv8/fsl-layerscape/cpu.c | 33
The efi loader code has its own memory map, so it needs to be aware where
the spin tables are located, to ensure that no code writes into those
regions.
Signed-off-by: Alexander Graf
---
arch/arm/cpu/armv8/fsl-layerscape/fdt.c | 6 ++
1 file changed, 6 insertions(+)
diff
The DP-DDR shouldn't be exposed as conventional memory to an OS, so let's
rather claim it's a reserved region in the EFI memory map
Signed-off-by: Alexander Graf
---
board/freescale/ls2080ardb/ls2080ardb.c | 9 +
1 file changed, 9 insertions(+)
diff --git
I have just been handed the task of cleaning up our U-Boot port to our
ThunderX armv8 chip and am wondering where I should put the files
specific to our chip.
The people who previously worked on the chip created a subdirectory
under u-boot and have things scattered about.
Should I create a
+Masahiro for the Makefile question
Hi Andreas,
On 17 June 2016 at 10:13, Andreas Dannenberg wrote:
> Hi Simon,
> many thanks for your feedback on the series... I know it takes a lot of
> effort to digest all that stuff. We'll see how we can tackle the
> feedback one by one
On Mon, Jun 20, 2016 at 2:31 PM, Guillaume Gardet
wrote:
> Please note that, this patch applies on top of this one:
> NFS: Add error message when U-Boot NFS version (V2) is not supported by
> NFS server
> https://patchwork.ozlabs.org/patch/630898/
Please make
On Wed, Jun 15, 2016 at 12:33 AM, Masahiro Yamada
wrote:
> There are some cases where config options are moved, but they are
> ripped off at the final savedefconfig stage:
>
> - The moved option is not user-configurable, for example, due to
> a missing prompt
On Wed, Jun 15, 2016 at 12:33 AM, Masahiro Yamada
wrote:
> Since commit 1d085568b3de ("tools: moveconfig: display log atomically
> in more readable format"), the function color_text() is clever enough
> to exclude LF from escape sequences. Exploit it for removing
On Wed, Jun 15, 2016 at 12:33 AM, Masahiro Yamada
wrote:
> The subprocess.Popen() does not change the child process's working
> directory if cwd=None is given. Let's exploit this fact to refactor
> the source directory handling.
>
> We no longer have to pass "-C "
On Wed, Jun 15, 2016 at 12:33 AM, Masahiro Yamada
wrote:
> The class WorkDir can be used in a very generic way, but currently
> it is only used for containing a reference source directory.
>
> This commit changes it for a more dedicated use. The move_config
>
On Wed, Jun 15, 2016 at 12:33 AM, Masahiro Yamada
wrote:
> When moving an integer type option with default value 1, the tool
> moves configs with the same value as the default (, and then removed
> by the later savedefconfig). This is a needless operation.
>
> The
DISTRO_DEFAULTS is intended to mirror / replace
include/config_distro_defaults.h.
The intend is for boards which include this file to select this from
their Kconfig files and when moving setting to Kconfig which are #define-ed
in config_distro_defaults.h to select this from DISTRO_DEFAULTS so
Hi Tom,
Here is the third sunxi pull-req for v2016.07, it
contains a few misc. fixes, 2 new boards and
the conversion of the PSCI code to C-code.
The following changes since commit 46fd625dfee9ef69cd183f0cd11e09309a71a4e2:
Prepare v2016.07-rc2 (2016-06-20 11:14:12 -0400)
are available in
Please note that, this patch applies on top of this one:
NFS: Add error message when U-Boot NFS version (V2) is not supported by NFS
server
https://patchwork.ozlabs.org/patch/630898/
It would be nice if people could test it on other boards and with other NFS
servers.
Guillaume
Le
This patch enables NFSv3 support.
If NFSv2 is available use it as usual.
If NFSv2 is not available, but NFSv3 is available, use NFSv3.
If NFSv2 and NFSv3 are not available, print an error message since NFSv4 is not
supported.
Tested on iMX6 sabrelite with 4 Linux NFS servers:
* NFSv2 + NFSv3 +
Hi Rob,
> On Jun 20, 2016, at 21:20 , Rob Herring wrote:
>
> On Mon, Jun 20, 2016 at 04:08:47PM +0300, Pantelis Antoniou wrote:
>> Hi Hans,
>>
>>> On Jun 20, 2016, at 16:02 , Hans de Goede wrote:
>>>
>>> Hi,
>>>
>>> On 20-06-16 14:22, Pantelis Antoniou
Hello,
in my device-tree (for stm32f429 - as found in the linux kernel) exist
two branches /soc and /clocks. While /soc contains all embedded
functionality of the SOC, /clocks contain the external crystal, like in
the following snippet.
/ {
clocks {
clk_hse: clk-hse {
> It's release day and v2016.07-rc2 is out and on time. I expect to do
> -rc3 in another two weeks. I've updated git and the tarballs are also
> up now.
I might be blind but I don't see a tarball here :) ftp://ftp.denx.de/pub/u-boot/
> We've gotten a number of PRs in with the sort of changes
From: Benjamin Tietz
If the device-tree gpio selection is selected, the hardcoded board-specific
led-initialization will fail.
This will disable that code, if CONFIG_DM_GPIO is enabled.
---
board/st/stm32f429-discovery/Makefile |3 +++
From: Benjamin Tietz
Extend the LED API to support toggling an LED. If the device provides a
direct way for this, it can implement the corresponding op.
If not supported directly by the driver, the led will be toggled by calling
led_set_on(!led_get_on()), transparently.
From: Benjamin Tietz
Support toggling of LEDs in the led command for device-tree configured LEDs.
---
cmd/led.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/cmd/led.c b/cmd/led.c
index 7632074..217ec5a 100644
--- a/cmd/led.c
+++ b/cmd/led.c
@@
From: Benjamin Tietz
This extends the LED-API for retrieving the current state a LED is in.
This needs corresponding support by the underlying device, but provides a way
to check, wether an LED is on or off.
---
drivers/led/led-uclass.c | 10 ++
include/led.h
From: Benjamin Tietz
Add the code needed for retrieving the led-status to the generic led-gpio
driver.
---
drivers/led/led_gpio.c | 11 +++
1 file changed, 11 insertions(+)
diff --git a/drivers/led/led_gpio.c b/drivers/led/led_gpio.c
index cb6e996..80e0f72
From: Benjamin Tietz
Make the LED command aware of device-tree configured LEDs, using the new
LED API calls.
---
cmd/led.c | 53 -
1 file changed, 52 insertions(+), 1 deletion(-)
diff --git a/cmd/led.c b/cmd/led.c
From: Benjamin Tietz
Previously, all knwon LED were hold in a single array and computed at
compile-time.
With the new variant, if all LEDs are known, these will also be computed at
compile-time.
Using functions will allow additional dynamic (eg. DM-based) LED
From: Benjamin Tietz
This extends the API of the LED-driver to count the number
of configured LEDs and retrieving an array of them.
---
drivers/led/led-uclass.c | 53 ++
include/led.h| 18
2
From: Benjamin Tietz
This extends the API of the led-driver to retrieve the label of and led-device.
---
drivers/led/led-uclass.c |6 ++
include/led.h|8
2 files changed, 14 insertions(+)
diff --git a/drivers/led/led-uclass.c
From: Benjamin Tietz
The following adds the configuration of the user-leds to the device tree for
STM32F429 discovery board.
---
arch/arm/dts/stm32f429-disco.dts | 22 ++
1 file changed, 22 insertions(+)
diff --git
From: Benjamin Tietz
If STATUS_LED isn't selected, neither led_id_t is selected, nor STATUS_LED_ON.
The following will set led_id_t to a reasonable default and define
STATUS_LED_ON for that case.
---
drivers/misc/gpio_led.c |4
drivers/misc/status_led.c |
From: Benjamin Tietz
This adds all GPIO-banks known by the STM32F4 MCU to the corresponding
.dts-file. Those not available in the the TQFP-package are currently
disabled.
---
arch/arm/dts/stm32f429.dtsi | 92 +++
1 file changed,
From: Benjamin Tietz
In the STM32 gpio driver, multiple family-dependent sections existed.
All but one just statically filled a datastructure. The following patch
creates these structure const-static within a single family-dependent
section.
This seperation improves the
From: Benjamin Tietz
If CONFIG_DM_GPIO is enabled, the STM32 SOC GPIO driver will switch it's
behaviour
from implementing the gpio_*() interface directly to provide a gpio-device.
---
drivers/gpio/stm32_gpio.c | 133 +
1 file
From: Benjamin Tietz
This patch adds the DTS configuration files needed for the
STM32F429-Discovery board, as they can be found in a current
Linux Kernel.
---
arch/arm/dts/Makefile|2
arch/arm/dts/armv7-m.dtsi| 24 +
From: Benjamin Tietz
This implements an basic clock driver for the RCC-part of STM32 MCUs.
Currently, only enabling and disabling of peripheral clocks and retrieving main
frequency is implemented.
---
drivers/clk/Kconfig |4 ++
drivers/clk/Makefile|1
From: Benjamin Tietz
Currently, clocks can be enabled, only. To be feature-complete - and allow
a bit of power-saving in applications - disabling a clock should be
possible, too.
This extend the API of the DM clock driver to allow a clock to be disabled.
The
From: Benjamin Tietz
This enables and adds configuration for status-leds on the
STM32F429 discovery board.
---
include/configs/stm32f429-discovery.h |8
1 file changed, 8 insertions(+)
diff --git a/include/configs/stm32f429-discovery.h
From: Benjamin Tietz
This patch creates an entry for selecting the led command from
kconfig configuration.
---
cmd/Kconfig |4
1 file changed, 4 insertions(+)
diff --git a/cmd/Kconfig b/cmd/Kconfig
index d51645c..f49ff47 100644
--- a/cmd/Kconfig
+++
Since the GPIOx_OTYPER register has only one bit for every pin, the width and
shift has to be corrected.
---
drivers/gpio/stm32_gpio.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpio/stm32_gpio.c b/drivers/gpio/stm32_gpio.c
index 50f86d3..2457211 100644
---
Previously the bit for settting the pin-behaviour was left undefined, which may
result in an open-drain behaviour for the affected pin.
Now it is correctly initialized, always.
---
drivers/gpio/stm32_gpio.c |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/gpio/stm32_gpio.c
Some functions using the GPIO-interface depend on gpio_get_value to
return 0 or 1, while the stm32 driver returned 0 or "something not zero".
This patch corrects this behaviour.
---
drivers/gpio/stm32_gpio.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
This series begins to provide device-tree support on stm32 devices,
starting with a the stack of a simple clock-driver (at least
enabling/disabling peripheral clocks), the gpio driver and leds.
As the current led command-line interface isn't aware of any device-tree
configured led, the command
On Mon, Jun 20, 2016 at 04:08:47PM +0300, Pantelis Antoniou wrote:
> Hi Hans,
>
> > On Jun 20, 2016, at 16:02 , Hans de Goede wrote:
> >
> > Hi,
> >
> > On 20-06-16 14:22, Pantelis Antoniou wrote:
> >> Hi Hans,
> >>
> >>> On Jun 20, 2016, at 14:03 , Hans de Goede
There is no more define of CONFIG_SYS_HUSH_PARSER. Rename some
remaining references and drop the backward compatible Kconfig entry.
Signed-off-by: Masahiro Yamada
---
board/work-microwave/work_92105/work_92105_display.c | 4 ++--
cmd/Kconfig
I still see some defines of this config in board headers. Move them
to defconfigs (+ renaming to CONFIG_HUSH_PARSER) to complete this
migration.
Signed-off-by: Masahiro Yamada
---
configs/gurnard_defconfig| 1 +
configs/odroid-c2_defconfig | 1 +
On 06/19/2016 03:34 AM, André Przywara wrote:
> Hi,
>
> On 19/06/16 09:57, Masahiro Yamada wrote:
>> 2016-06-18 18:40 GMT+09:00 Linus Walleij :
>>> On Fri, Jun 17, 2016 at 2:51 PM, Masahiro Yamada
>>> wrote:
>>>
There are two enable
Hi Stefano,
On Mon, Jun 20, 2016 at 05:46:52PM +0200, Stefano Babic wrote:
> Hallo Andrej,
>
> On 20/06/2016 17:21, and...@inversepath.com wrote:
> > From: Andrej Rosano
> >
> > Define a default board_run_command() function. This function contains
> > the commands
Hi,
> On 06/20/2016 03:22 PM, Christian Didriksson wrote:
> > Hi Marek,
>
> Hi,
>
> >> On 06/17/2016 04:39 PM, Christian Didriksson wrote:
> >>> Hi Marek,
> >>
> >> Hi
> >>
> >>> I applied the two patches you suggested, but got no change in behavior:
> >>>
> >>> U-Boot SPL
Hallo Andrej,
On 20/06/2016 17:21, and...@inversepath.com wrote:
> From: Andrej Rosano
>
> Define a default board_run_command() function. This function contains
> the commands needed to boot the board when CLI is disabled (CONFIG_CMDLINE=n).
>
> Signed-off-by: Andrej
Simon,
> -Original Message-
> From: s...@google.com [mailto:s...@google.com] On Behalf Of Simon Glass
> Sent: Friday, June 17, 2016 4:05 PM
> To: Stephen Warren
> Cc: U-Boot Mailing List ; Stephen Warren
> ; Tom Warren
On Mon, Jun 20, 2016 at 05:34:05PM +0200, Hans de Goede wrote:
> Hi,
>
> On 20-06-16 17:26, Tom Rini wrote:
> >Hey all,
> >
> >It's release day and v2016.07-rc2 is out and on time. I expect to do
> >-rc3 in another two weeks. I've updated git and the tarballs are also
> >up now.
> >
> >We've
Hi,
On 20-06-16 17:26, Tom Rini wrote:
Hey all,
It's release day and v2016.07-rc2 is out and on time. I expect to do
-rc3 in another two weeks. I've updated git and the tarballs are also
up now.
We've gotten a number of PRs in with the sort of changes that should go
in, in. Going forward
From: Andrej Rosano
Switch to using zImage instead of uImage.
Signed-off-by: Andrej Rosano
---
include/configs/usbarmory.h | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/include/configs/usbarmory.h
From: Andrej Rosano
Define a default board_run_command() function. This function contains
the commands needed to boot the board when CLI is disabled (CONFIG_CMDLINE=n).
Signed-off-by: Andrej Rosano
---
board/inversepath/usbarmory/usbarmory.c |
Hey all,
It's release day and v2016.07-rc2 is out and on time. I expect to do
-rc3 in another two weeks. I've updated git and the tarballs are also
up now.
We've gotten a number of PRs in with the sort of changes that should go
in, in. Going forward now changes really should be of the bug fix
On 06/20/2016 03:43 AM, Peng Fan wrote:
> The USBNC_PHYCFG2_ACAENB bit should be cleared to enable the
> OTG ID detection, not set it. When the bit is set, the ACA
> Resistance Detection is enabled, which disables the OTG ID
> detection, because the internal pull up is off.
>
> Signed-off-by: Ye
On 06/20/2016 06:15 AM, Sriram Dash wrote:
> Currently, U-boot doesn't allow to compile more than one type of USB protocol
> simultaneously. Hence, EHCI and XHCI controllers cannot co-exist and
> CONFIG_USB_MAX_CONTROLLER_COUNT macro represents count of only one type of
> controller.
This does
i.MX6UL defines speed grading in OCOTP register 0x440[17:16]
as follows:
00 reserved
01 528MHz
10 700MHz
11 reserved
This commit removes the constants (which had the speed hardcoded
in their names) and uses values instead.
Signed-off-by: Hector Palacios
On 06/20/2016 03:43 AM, Peng Fan wrote:
> There is a 4 bytes hole between phy_cfg2 and phy_status, fix the
> usbnc_regs structure to include the hole.
>
> Signed-off-by: Ye Li
> Signed-off-by: Peng Fan
> ---
Applied, thanks
> V2:
> Split from V1 to a single
On 06/20/2016 03:22 PM, Christian Didriksson wrote:
> Hi Marek,
Hi,
>> On 06/17/2016 04:39 PM, Christian Didriksson wrote:
>>> Hi Marek,
>>
>> Hi
>>
>>> I applied the two patches you suggested, but got no change in behavior:
>>>
>>> U-Boot SPL 2016.05-ga0bd0e7-dirty (Jun 17 2016 - 16:32:35)
>>>
Hi Marek,
> On 06/17/2016 04:39 PM, Christian Didriksson wrote:
> > Hi Marek,
>
> Hi
>
> > I applied the two patches you suggested, but got no change in behavior:
> >
> > U-Boot SPL 2016.05-ga0bd0e7-dirty (Jun 17 2016 - 16:32:35)
> > drivers/ddr/altera/sequencer.c: Preparing to start memory
Hi Andrew,
> Hi Lukasz,
>
> I hope you may be able to offer me some advice.
>
> I have a small project to update a tbs2900, tbs moi. which is a DVB-S2
> network/iptv device.
>
> The device is based on smdkv210, with the s5pv210 soc. I understand
> that in terms of the kernel this is well
1 - 100 of 132 matches
Mail list logo