Hi Rick and Sebastian,
On Thu, Feb 15, 2018 at 2:15 PM, Sebastian Reichel
wrote:
> From: Rick Bronson
>
> Allow higher UART baud rates for communications to ACHC at 13.5 MBaud
What does ACHC mean?
> Done in u-boot since it changes a divider common to all UARTs, including
> the console. If it w
On Thu, Feb 15, 2018 at 2:15 PM, Sebastian Reichel
wrote:
> From: Rick Bronson
>
> Allow higher UART baud rates for communications to ACHC at 13.5 MBaud
> Done in u-boot since it changes a divider common to all UARTs, including
> the console. If it were done in Linux we would get garbled characte
It's been ages since I've worked on this, let me refresh my memory and get back
to you.
Cheers,
Rick
From: "Fabio Estevam"
To: "Sebastian Reichel"
Cc: "Stefano Babic" , "Fabio Estevam" ,
"U-Boot-Denx" , "Rick Bronson"
Sent: Saturday, February 17, 2018 9:42:47 AM
Subject: Re: [U-Boot
On Thu, Feb 15, 2018 at 04:47:42PM +0530, Faiz Abbas wrote:
> In SPL, DFU only has RAM support. Therefore, only build RAM for DFU
> in SPL.
>
> Signed-off-by: Faiz Abbas
Reviewed-by: Tom Rini
--
Tom
signature.asc
Description: PGP signature
___
U-
On Fri, Feb 16, 2018 at 01:41:23PM +0530, Faiz Abbas wrote:
> Add CONFIG_SPL_NET_VCI_STRING to enable USB-Ethernet boot mode
> support.
>
> Signed-off-by: Faiz Abbas
Reviewed-by: Tom Rini
--
Tom
signature.asc
Description: PGP signature
___
U-Boot
On Wed, Feb 07, 2018 at 02:17:11PM -0800, York Sun wrote:
> Commit 7d714a24d725 ("env: Support multiple environments") added
> static variable env_load_location. When saving environmental
> variables, this variable is presumed to have the value set before.
> In case the value was set before reloca
On Fri, Feb 09, 2018 at 08:23:17PM +, Goldschmidt Simon wrote:
> With multiple environments, the 'get_char' callback for env
> drivers does not really make sense any more because it is
> only supported by two drivers (eeprom and nvram).
>
> To restore single character loading for these driver
On Fri, Feb 16, 2018 at 05:00:52PM +0100, Marek Vasut wrote:
> The following changes since commit 32fe36574ea5e6ea55313e16547b98a984af7767:
>
> Merge git://git.denx.de/u-boot-arc (2018-02-15 14:07:04 -0500)
>
> are available in the Git repository at:
>
> git://git.denx.de/u-boot-sh.git mast
On Fri, Feb 16, 2018 at 04:59:08PM +0100, Marek Vasut wrote:
> The following changes since commit 0c502b6c176281a096a23803e517b19e964485f1:
>
> configs: Resync with savedefconfig (2018-02-14 21:34:50 -0500)
>
> are available in the Git repository at:
>
> git://git.denx.de/u-boot-usb.git mas
On Fri, Feb 16, 2018 at 04:59:36PM +0100, Marek Vasut wrote:
> The following changes since commit 0c502b6c176281a096a23803e517b19e964485f1:
>
> configs: Resync with savedefconfig (2018-02-14 21:34:50 -0500)
>
> are available in the Git repository at:
>
> git://git.denx.de/u-boot-socfpga.git
Remove this config option as it's useless and causes a warning.
Signed-off-by: Marek Vasut
Cc: Nobuhiro Iwamatsu
---
configs/porter_defconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/configs/porter_defconfig b/configs/porter_defconfig
index 09776db003..ada106feb1 100644
--- a/configs/
The following changes since commit bd650cd404b6dc870b6cc220025f35da4b31d0f4:
Merge git://git.denx.de/u-boot-sh (2018-02-16 13:56:02 -0500)
are available in the Git repository at:
git://git.denx.de/u-boot-sh.git master
for you to fetch changes up to 25f6dc8955bdf97bfb16ef19de7ce4abe76aaee4:
On Sat, Feb 17, 2018 at 10:02:09PM +0100, Marek Vasut wrote:
> The following changes since commit bd650cd404b6dc870b6cc220025f35da4b31d0f4:
>
> Merge git://git.denx.de/u-boot-sh (2018-02-16 13:56:02 -0500)
>
> are available in the Git repository at:
>
> git://git.denx.de/u-boot-sh.git maste
From: Fabio Estevam
With fastboot support enabled, it is useful to be able to list
the eMMC EFI partitions, so select the CONFIG_EFI_PARTITION option.
Signed-off-by: Fabio Estevam
---
Hi Stefano,
It seems you picked the v1 of my fastboot patch instead of v2.
Hence I am sending a new patch tha
With the switch to newer toolchains from kernel.org we can now fetch an
sh2 toolchain that will build for sh2/3/4, so switch to that.
Signed-off-by: Tom Rini
---
.travis.yml | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/.travis.yml b/.travis.yml
index 7b53b3dddc1b..
Based on reading over the GCC manual, passing both -m2a and -m2a-nofpu
are redundant, as -m2a-nofpu will provide functional code for both. As
-m2a-nofpu functions with more toolchains and does what is expected,
switch.
Cc: Nobuhiro Iwamatsu
Signed-off-by: Tom Rini
---
arch/sh/cpu/sh2/config.mk
With a newer toolchain we can see that in both sh_eth_phy_config_legacy
and sh_eth_recv_common the variable port is never referenced as
eth->port is always used instead.
Cc: Joe Hershberger
Signed-off-by: Tom Rini
---
drivers/net/sh_eth.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-
With modern GCC, we get warnings such as:
cmd/jffs2.c: In function 'mtdparts_init':
arch/sh/include/asm/string.h:110:38:
warning: array subscript is above array bounds [-Warray-bounds]
: "0" (__cs), "1" (__ct), "r" (__cs+__n)
^~~~
This results in a small si
Based on v4.15, add MTDIDS / MTDPARTS that match the in-kernel defaults.
Cc: Nobuhiro Iwamatsu
Signed-off-by: Tom Rini
---
configs/sh7763rdp_defconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git a/configs/sh7763rdp_defconfig b/configs/sh7763rdp_defconfig
index 9683c7a6cabf..ff8011793016
Check that parameter guid is not NULL. This avoids a possible NULL
pointer exception.
Signed-off-by: Heinrich Schuchardt
---
lib/efi_loader/efi_boottime.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/lib/efi_loader/efi_boottime.c b/lib/efi_loader/efi_boottime.c
index 6eea2395c7..c03965
Hi Fabio,
First a disclaimer. I no longer work for the client that had me
make this change. I also no longer have any iMX53 hardware to do any
kind of tests. But I'm happy to help out with this email.
> Hi Rick and Sebastian,
>
> On Thu, Feb 15, 2018 at 2:15 PM, Sebastian Reichel
> wrote:
>
Hi Rick,
On Sat, Feb 17, 2018 at 9:24 PM, Rick Bronson wrote:
>> It would be nice to explain a bit how you achieve the higher baud rates.
>
> Background: PLL2 runs at 400 MHz, PLL3 runs at 216 MHz. One of
> these PLL's are fed to a UART divider, the output of which sets the
> maximum UART bau
22 matches
Mail list logo
