On Fri, Jan 5, 2018 at 9:45 PM, Jun Nie wrote:
> Enable OTG clock and deassert reset
>
> Signed-off-by: Jun Nie
> ---
> arch/arm/include/asm/arch-sunxi/clock_sun6i.h | 1 +
> drivers/usb/musb-new/sunxi.c | 6 +-
> 2 files changed, 6
On 26.01.18 20:52, Heinrich Schuchardt wrote:
> The appended README explains how U-Boot and iPXE can be used
> to boot a diskless system from an iSCSI SAN.
>
> The maintainer for README.efi and README.iscsi is set.
>
> Signed-off-by: Heinrich Schuchardt
> ---
> v2
>
The previous code tried to update the PHY parameters without waiting for
autonegotiation to complete. This caused wrong values to be written to
the EMAC in sun8i_adjust_link(). As a result, any commands that called
eth_start() before autonegotiation completed would find the network
nonfunctional.
On Sat, Jan 27, 2018 at 08:40:49PM +0100, Marek Vasut wrote:
> The following changes since commit 16121280188d3daa57b18ad623d08455a90a:
>
> Merge git://git.denx.de/u-boot-fsl-qoriq (2018-01-23 21:48:53 -0500)
>
> are available in the Git repository at:
>
>
On Sun, Jan 28, 2018 at 06:40:34AM +0900, Masahiro Yamada wrote:
> Hi Tom,
>
> Please pull one more patch for -rc1.
> Thanks!
>
>
> The following changes since commit 0163c9186b161682a46bd7ae3c2e6ffe275bb1f8:
>
> env: sunxi: Enable FAT-based environment support by default
> (2018-01-27
On Sat, Jan 27, 2018 at 08:38:19PM +0100, Marek Vasut wrote:
> The following changes since commit fb4413295c765aa8c013650984dc2d908964c81d:
>
> Merge git://git.denx.de/u-boot-mmc (2018-01-24 11:28:44 -0500)
>
> are available in the Git repository at:
>
> git://git.denx.de/u-boot-usb.git
On Sat, Jan 27, 2018 at 08:37:48PM +0100, Marek Vasut wrote:
> The following changes since commit fb4413295c765aa8c013650984dc2d908964c81d:
>
> Merge git://git.denx.de/u-boot-mmc (2018-01-24 11:28:44 -0500)
>
> are available in the Git repository at:
>
>
On 01/27/2018 09:22 PM, Tom Rini wrote:
> The variable hcd_name is unsued, drop.
>
> Cc: Marek Vasut
> Cc: Chris Brandt
> Signed-off-by: Tom Rini
Applied, thanks
--
Best regards,
Marek Vasut
On 01/27/2018 09:21 PM, Tom Rini wrote:
> The isp116x-hcd driver is extremely long unused, so just remove it.
>
> Cc: Marek Vasut
> Signed-off-by: Tom Rini
Applied, thanks
--
Best regards,
Marek Vasut
___
U-Boot
Reviewed-by: Marek Behun
On Sat, 27 Jan 2018 17:23:21 -0500
Tom Rini wrote:
> When printing a size_t value we need to use %zu for portability
> between 32bit and 64bit targets.
>
> Cc: Marek Behún
> Signed-off-by: Tom Rini
When printing a size_t value we need to use %zu for portability between
32bit and 64bit targets.
Cc: Marek Behún
Signed-off-by: Tom Rini
---
Changes in v2:
- Drop u32 cast, per Marek.
---
fs/btrfs/super.c | 4 ++--
1 file changed, 2 insertions(+), 2
shouldn't in that case the (u32) cast be removed?
On Sat, 27 Jan 2018 14:48:10 -0500
Tom Rini wrote:
> When printing a size_t value we need to use %zu for portability
> between 32bit and 64bit targets.
>
> Cc: Marek Behún
> Signed-off-by: Tom Rini
Hi,
When trying to build a kernel uIimage for PowerPC, on a PoewrPC host,
mkimage generates a header that appears to be in Little-endian, rather
than Big-endian, resulting in an unbootable uImage.
From a correct build (NetBSD's mkubootimage):
: 2705 1956 ae84 7a0b 5a55 38e5 010e d6f8
Hi Marek,
> On 01/27/2018 10:55 PM, Lukasz Majewski wrote:
> > The goal of this patch is to clean up the code related to choosing
> > spl MMC boot mode.
> >
> > The spl_boot_mode() now is called only in spl_mmc_load_image()
> > function, which is only compiled in if CONFIG_SPL_MMC_SUPPORT is
> >
On 01/27/2018 10:55 PM, Lukasz Majewski wrote:
> The goal of this patch is to clean up the code related to choosing spl
> MMC boot mode.
>
> The spl_boot_mode() now is called only in spl_mmc_load_image() function,
> which is only compiled in if CONFIG_SPL_MMC_SUPPORT is enabled.
It always was
The goal of this patch is to clean up the code related to choosing spl
MMC boot mode.
The spl_boot_mode() now is called only in spl_mmc_load_image() function,
which is only compiled in if CONFIG_SPL_MMC_SUPPORT is enabled.
To achieve the goal, all per mach/arch implementations eligible for
2018-01-25 14:10 GMT+09:00 Jaehoon Chung :
> On 01/25/2018 01:43 PM, Masahiro Yamada wrote:
>> Signed-off-by: Masahiro Yamada
>
> Reviewed-by: Jaehoon Chung
>
>> ---
Applied to u-boot-uniphier.
--
Best Regards
Hi Tom,
Please pull one more patch for -rc1.
Thanks!
The following changes since commit 0163c9186b161682a46bd7ae3c2e6ffe275bb1f8:
env: sunxi: Enable FAT-based environment support by default
(2018-01-27 09:23:32 -0500)
are available in the git repository at:
Hi Simon,
2018-01-27 0:27 GMT+09:00 Simon Glass :
> Hi Masahiro,
>
> On 21 January 2018 at 02:34, Masahiro Yamada
> wrote:
>> All of these host tools are apparently written for Python2,
>> not Python3.
>>
>> Use 'python2' in the shebang line
On 01/27/2018 09:17 PM, Dr. Philipp Tomsich wrote:
>
>> On 27 Jan 2018, at 20:56, Tom Rini wrote:
>>
>> On Sat, Jan 27, 2018 at 08:52:43PM +0100, Marek Vasut wrote:
>>> On 01/27/2018 08:48 PM, Tom Rini wrote:
When we have a driver that is used on both 32bit and 64bit
On 26.01.18 21:03, Heinrich Schuchardt wrote:
> README.efi describes two different concepts:
> * U-Boot exposing the UEFI API
> * U-Boot running on top of UEFI.
>
> This patch splits the document in two.
> Religious references are removed.
>
> The separation of the concepts makes sense before
The variable hcd_name is unsued, drop.
Cc: Marek Vasut
Cc: Chris Brandt
Signed-off-by: Tom Rini
---
drivers/usb/host/r8a66597-hcd.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/usb/host/r8a66597-hcd.c
The isp116x-hcd driver is extremely long unused, so just remove it.
Cc: Marek Vasut
Signed-off-by: Tom Rini
---
drivers/usb/host/Makefile |1 -
drivers/usb/host/isp116x-hcd.c | 1323
drivers/usb/host/isp116x.h
> On 27 Jan 2018, at 20:56, Tom Rini wrote:
>
> On Sat, Jan 27, 2018 at 08:52:43PM +0100, Marek Vasut wrote:
>> On 01/27/2018 08:48 PM, Tom Rini wrote:
>>> When we have a driver that is used on both 32bit and 64bit targets and
>>> we are talking about address space we cannot
The variable t_rfc is never used, so drop it. The variables ddr_wctl
and ddr_wcmd are only used in certain manual instances, so guard their
declaration by the same check as their use.
Cc: Bin Meng
Signed-off-by: Tom Rini
---
arch/x86/cpu/quark/smc.c |
On 01/27/2018 08:57 PM, Tom Rini wrote:
> Both the isp116x-hcd and r8a66597-hcd drivers have an unused hcd_name
> variable, drop. isp116x-hcd also defines an unused DRIVER_VERSION, so
> drop that while in here.
>
> Cc: Marek Vasut (maintainer:USB)
> Signed-off-by: Tom Rini
On 01/27/2018 08:56 PM, Tom Rini wrote:
> On Sat, Jan 27, 2018 at 08:52:43PM +0100, Marek Vasut wrote:
>> On 01/27/2018 08:48 PM, Tom Rini wrote:
>>> When we have a driver that is used on both 32bit and 64bit targets and
>>> we are talking about address space we cannot use u64 nor u32 and instead
When a UEFI payload just returns instead of calling the Exit() callback,
we handle that in efi_do_enter() and call Exit on its behalf, so that
the loaded_image->exit_status value is correct.
We were missing that logic in StartImage(). Call it there too.
Reported-by: Heinrich Schuchardt
Dear Nathan,
In message
you wrote:
>
> Anyone know where a guide to hush shell in u-boot would be?
There is none. The hush shell was copied from the busybox project
(and I have to admit that I don't know
Both the isp116x-hcd and r8a66597-hcd drivers have an unused hcd_name
variable, drop. isp116x-hcd also defines an unused DRIVER_VERSION, so
drop that while in here.
Cc: Marek Vasut (maintainer:USB)
Signed-off-by: Tom Rini
---
drivers/usb/host/isp116x-hcd.c
Dear Nathan,
In message
you wrote:
> This manual http://www.denx.de/wiki/DULG/Manual
> is out of date and missing a lot of info.
> I have been using it thinking it was the official manual.
It is. And it is
On Sat, Jan 27, 2018 at 08:53:34PM +0100, Marek Vasut wrote:
> On 01/27/2018 08:48 PM, Tom Rini wrote:
> > The order of arguments for ehci_writel() is 'dest', 'value' and not
> > 'value', 'dest'.
> >
> > Cc: Stefano Babic
> > Cc: Marek Vasut
> > Signed-off-by: Tom
On 01/27/2018 08:48 PM, Tom Rini wrote:
> When we have a driver that is used on both 32bit and 64bit targets and
> we are talking about address space we cannot use u64 nor u32 and instead
> need to use phys_addr_t.
Can someoneone pass in a pointer above 32bit address range ? That might
cause some
The order of arguments for ehci_writel() is 'dest', 'value' and not
'value', 'dest'.
Cc: Stefano Babic
Cc: Marek Vasut
Signed-off-by: Tom Rini
---
drivers/usb/host/ehci-mxs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
When printing a size_t value we need to use %zu for portability between
32bit and 64bit targets.
Cc: Marek Behún
Signed-off-by: Tom Rini
---
fs/btrfs/super.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/btrfs/super.c
When we have a driver that is used on both 32bit and 64bit targets and
we are talking about address space we cannot use u64 nor u32 and instead
need to use phys_addr_t.
Cc: Lukasz Majewski
Cc: Marek Vasut
Signed-off-by: Tom Rini
---
When we have a driver that is used on both 32bit and 64bit targets and
we are talking about address space we cannot use u64 nor u32 and instead
need to use phys_addr_t.
Fixes: 377883f16d36 ("net: mvpp2x: fix phy connected to wrong mdio issue")
Cc: Stefan Chulski
Cc: Stefan
The following changes since commit fb4413295c765aa8c013650984dc2d908964c81d:
Merge git://git.denx.de/u-boot-mmc (2018-01-24 11:28:44 -0500)
are available in the Git repository at:
git://git.denx.de/u-boot-usb.git master
for you to fetch changes up to
The following changes since commit 16121280188d3daa57b18ad623d08455a90a:
Merge git://git.denx.de/u-boot-fsl-qoriq (2018-01-23 21:48:53 -0500)
are available in the Git repository at:
git://git.denx.de/u-boot-sh.git rmobile-mx
for you to fetch changes up to
The following changes since commit fb4413295c765aa8c013650984dc2d908964c81d:
Merge git://git.denx.de/u-boot-mmc (2018-01-24 11:28:44 -0500)
are available in the Git repository at:
git://git.denx.de/u-boot-socfpga.git master
for you to fetch changes up to
On Tue, Jan 23, 2018 at 09:17:04PM +0100, Maxime Ripard wrote:
> Now that we have everything in place to implement the transition scheme,
> let's enable it by default.
>
> Reviewed-by: Andre Przywara
> Reviewed-by: Lukasz Majewski
> Signed-off-by: Maxime
On Tue, Jan 23, 2018 at 09:16:53PM +0100, Maxime Ripard wrote:
> Since we'll soon have support for multiple environments, the environment
> saving message might end up being printed multiple times if the higher
> priority environment cannot be used.
>
> That might confuse the user, so let's make
On Tue, Jan 23, 2018 at 09:17:00PM +0100, Maxime Ripard wrote:
> The raw MMC environment directly calls into the MMC framework. Make sure
> it's enabled before we can select it.
>
> Reviewed-by: Simon Glass
> Signed-off-by: Maxime Ripard
>
On Tue, Jan 23, 2018 at 09:17:01PM +0100, Maxime Ripard wrote:
> Now that we have everything in place in the code, let's allow to build
> multiple environments backend through Kconfig.
>
> Reviewed-by: Andre Przywara
> Reviewed-by: Lukasz Majewski
>
On Tue, Jan 23, 2018 at 09:16:57PM +0100, Maxime Ripard wrote:
> Since we have global messages to indicate what's going on, the custom
> messages in the environment drivers only make the output less readable.
>
> Make the common code play a little nicer by removing all the extra output
> in the
On Tue, Jan 23, 2018 at 09:16:59PM +0100, Maxime Ripard wrote:
> Since we want to have multiple environments, we will need to initialise
> all the environments since we don't know at init time what drivers might
> fail when calling load.
>
> Let's init all of them, and only consider for further
On Tue, Jan 23, 2018 at 09:17:02PM +0100, Maxime Ripard wrote:
> Allow boards and architectures to override the default environment lookup
> code by overriding env_get_location.
>
> Reviewed-by: Andre Przywara
> Reviewed-by: Lukasz Majewski
> Reviewed-by:
On Tue, Jan 23, 2018 at 09:17:03PM +0100, Maxime Ripard wrote:
> The current environment has been hardcoded to an offset that starts to be
> an issue given the current size of our main U-Boot binary.
>
> By implementing a custom environment location routine, we can always favor
> the FAT-based
On Tue, Jan 23, 2018 at 09:16:58PM +0100, Maxime Ripard wrote:
> Now that we have everything in place to support multiple environment, let's
> make sure the current code can use it.
>
> The priority used between the various environment is the same one that was
> used in the code previously.
>
>
On Tue, Jan 23, 2018 at 09:16:55PM +0100, Maxime Ripard wrote:
> Since we have global messages to indicate what's going on, the custom
> messages in the environment drivers only make the output less readable.
>
> Make FAT play a little nicer by removing all the extra \n and formatting
> that is
On Tue, Jan 23, 2018 at 09:16:54PM +0100, Maxime Ripard wrote:
> Since we can have multiple environments now, it's better to provide a
> decent indication on what environments were tried and which were the one to
> fail and succeed.
>
> Reviewed-by: Simon Glass
>
On Tue, Jan 23, 2018 at 09:16:51PM +0100, Maxime Ripard wrote:
> The env_driver_lookup_default and env_get_default_location functions are
> about to get refactored to support loading from multiple environment.
>
> The name is therefore not really well suited anymore. Drop the default
> part to
On Tue, Jan 23, 2018 at 09:16:52PM +0100, Maxime Ripard wrote:
> In preparation for the multiple environment support, let's introduce two
> new parameters to the environment driver lookup function: the priority and
> operation.
>
> The operation parameter is meant to identify, obviously, the
On Tue, Jan 23, 2018 at 09:16:50PM +0100, Maxime Ripard wrote:
> The nvedit command is the only user of env_driver_lookup_default outside of
> the environment code itself, and it uses it only to print the environment
> it's about to save to during env save.
>
> As we're about to rework the
These are declared in Kconfig, but some #defines have crept in.
CONFIG_FPGA
CONFIG_FPGA_ALTERA
CONFIG_FPGA_CYCLON2
CONFIG_FPGA_SOCFPGA
CONFIG_FPGA_XILINX
CONFIG_FPGA_ZYNQMPPL
Signed-off-by: Tuomas Tynkkynen
---
configs/apf27_defconfig | 1 +
On 27/01/18 15:20, Jun Nie wrote:
> Support fuse cmd to read/write fuse. Power supply for fuse
> should be ready, name is VDD_EFUSE in some schematic.
Mmh, in general I am not sure it is a good idea to expose this so easily
to the user. I guess a clueless user can easily brick his board by
typing
For devices running I2C over 400KHz, this needs to be in HS mode.
Currently, the code is only running in HS mode when the speed is
equal or greater than 3.4MHz. At least on the OMAP3630/3730, this
fails when trying to configure at 2.6MHz
Using the Linux kernel setup as a reference, I used much
HI,
i'm trying the standalone hello_world.bin example on a
mips/ath79/QCA9558/Tp-Link Archer-c7
it just hangs for me:
ap135> tftpboot 0x8020
dup 1 speed 1000
*** Warning: no boot file name; using '6F01A8C0.img'
Using eth1 device
TFTP from server 192.168.1.100; our IP address is
Hello
I'm trying to run u-boot (sandbox) with a spi emulation, but the start
fails with an error (err=-19).
What I did
# clone and compile u-boot
cd ~/
git clone git://git.denx.de/u-boot.git
cd u-boot
git checkout v2017.11
make sandbox_defconfig menuconfig
"Sandbox architecture" -> "Run
Several inline functions in this file reference undefined functions in
U-Boot. For example:
atomic-long.h:73:9: warning: implicit declaration of function
'atomic64_sub_and_test'
atomic-long.h:80:9: warning: implicit declaration of function
'atomic64_dec_and_test'
atomic-long.h:87:9: warning:
Support fuse cmd to read/write fuse. Power supply for fuse
should be ready, name is VDD_EFUSE in some schematic.
Signed-off-by: Jun Nie
---
arch/arm/mach-sunxi/cpu_info.c | 60 ++
1 file changed, 60 insertions(+)
diff --git
61 matches
Mail list logo