On Mon, Oct 29, 2018 at 8:05 PM Tom Rini wrote:
>
> Hey all,
>
> It's two weeks until v2018.11 release and today I've put out rc3. The
> delta is pretty reasonable and at this point I can really hold things to
> either obviously correct fixes or bugfixes/regression fixes/Kconfig
> migrations that
Tom or Tom,
Any chance we could get these reviewed and merged, mostly generic
cleanups so I don't think most of them are controversial.
Peter
On Sun, Sep 16, 2018 at 6:23 PM Peter Robinson wrote:
>
> The following patches are a few cleanups to dangling comments from Kconfig
>
On Fri, Nov 16, 2018 at 1:06 AM Ricardo Salveti wrote:
>
> Hi Baruch,
>
> On Wed, Nov 14, 2018 at 5:07 AM Baruch Siach wrote:
> >
> > Hi Ricardo,
> >
> > On Tue, Nov 13, 2018 at 11:42:44AM -0200, Ricardo Salveti wrote:
> > > On Thu, Sep 6, 2018 at 12:52 PM Fabio Estevam wrote:
> > > > On Thu, Se
ich may happen when no eMMC is populated on
> board.
>
> Reported-by: Ricardo Salveti
> Signed-off-by: Fabio Estevam
Tested-by: Peter Robinson
Boots fine on my i.MX6 Quad hummingboard2 with SOM rev 1.5 which
previously has the problem I reported back in 2018.09 series.
Peter
> ---
On Mon, Nov 19, 2018 at 11:17 AM Fabio Estevam wrote:
>
> Ricardo/Peter,
>
> On Mon, Nov 19, 2018 at 5:44 AM Baruch Siach wrote:
>
> > I guess Fabio's patch would fix the issue for you. Indefinite loops are not
> > a
> > good idea in general, I think.
>
> I have just sent a patch that avoids the
On Tue, Nov 20, 2018 at 12:32 PM Stefano Babic wrote:
>
> Hi,
>
> On 19/11/18 23:06, Marek Vasut wrote:
> > On 11/19/2018 11:02 PM, Adam Ford wrote:
> >> On Mon, Nov 19, 2018 at 3:54 PM Tom Rini wrote:
> >>>
> >>> On Mon, Nov 19, 2018 at 10:32:01PM +0100, Marek Vasut wrote:
> On 11/19/2018 0
The following patches are a few cleanups to dangling comments from Kconfig
cleanups and migrations of SYS_I2C_TEGRA, USB_EHCI_TEGRA and TEGRA_KEYBOARD.
There's also a couple of other minors fixes and cleanups as well.
___
U-Boot mailing list
U-Boot@lists.
There's a number of dangling comments in various tegra configs post migrations
of various configs so lets clean them up.
Signed-off-by: Peter Robinson
Cc: Tom Warren
Cc: Stephen Warren
Cc: Marcel Ziswiler
Cc: Tom Warren
Cc: Stephen Warren
Cc: peter.ch...@data61.csiro.au
Cc: Lucas Stac
Migrate TEGRA_KEYBOARD from headers to Kconfig, only the seaboard uses it but we
drop CONFIG_KEYBOARD as the driver doesn't use the legacy drv_keyboard_init.
Signed-off-by: Peter Robinson
Cc: Tom Warren
Cc: Stephen Warren
---
configs/seaboard_defconfig | 1 +
drivers/input/Kc
The CONFIG_KEYBOARD does nothing as it's legacy and unused
so just drop it from the config.
Signed-off-by: Peter Robinson
Cc: Tom Warren
Cc: Stephen Warren
Cc: Allen Martin
---
include/configs/nyan-big.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/include/configs/nyan-bi
All other Tegra devices that define USB_EHCI_TXFIFO_THRESH use hex
representation, fix tegra20 to be the same format.
Signed-off-by: Peter Robinson
Cc: Tom Warren
Cc: Stephen Warren
---
include/configs/tegra20-common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a
Migrate USB_EHCI_TEGRA from headers to Kconfig
Signed-off-by: Peter Robinson
Cc: Tom Warren
Cc: Stephen Warren
Cc: Marek Vasut
Cc: Marcel Ziswiler
Cc: peter.ch...@data61.csiro.au
Cc: Lucas Stach
Cc: Stefan Agner
Cc: Alban Bedel
Cc: Allen Martin
---
configs/apalis-tk1_defconfig | 1
Migrate SYS_I2C_TEGRA from headers to Kconfig
Signed-off-by: Peter Robinson
Cc: Tom Warren
Cc: Stephen Warren
Cc: Heiko Schocher
Cc: Marcel Ziswiler
Cc: peter.ch...@data61.csiro.au
Cc: Lucas Stach
Cc: Stefan Agner
Cc: Alban Bedel
Cc: Allen Martin
---
configs/apalis-tk1_defconfig | 1
This should go into a -u-boot.dtsi file so that the
dragonboard410c.dts can be synced from the linux kernel without
change.
Peter
On Wed, Sep 19, 2018 at 7:31 PM Ramon Fried wrote:
>
> Alias is required so req-seq will be filled.
>
> Signed-off-by: Ramon Fried
> ---
>
> arch/arm/dts/dragonboar
> > This should go into a -u-boot.dtsi file so that the
> > dragonboard410c.dts can be synced from the linux kernel without
> > change.
> >
> Hi Peter.
> I thought that -u-boot.dtsi is only for u-boot specific stuff,
> The alias is not specific to u-boot AFAIK.
Yes, I did wonder if some of these c
s_reg): Node /images/fdt@1 has
> a unit name, but no reg property
> u-boot.itb.tmp: Warning (unit_address_vs_reg): Node
> /configurations/config@1 has a unit name, but no reg property
> make[1]: Leaving directory
> '/builddir/BUILD/u-boot-2018.05-rc2/builds/firefly-rk3399'
&
Philipp,
Can we get get a decision on this one, it fixes issues for me on
Rockchips devices. While I'm sure a rewrite in C to reduce
dependenciees is an option, this fix doesn't add any extra
dependencies and I think is still a candidate for 2018.11
Peter
On Fri, Jun 8, 2018 at 11:34 AM Mian Yous
the properties which
> differ between both boards are placed in the board specific dts and
> the reset of the nodes are placed in common dtsi file.
>
> Signed-off-by: Manivannan Sadhasivam
> [Added instructions for SD card boot]
> Signed-off-by: Ezequiel Garcia
Tested-by: Peter Rob
by: Heiko Stuebner
> Signed-off-by: Ezequiel Garcia
Tested-by: Peter Robinson
Tested on both a Rock960 and a Firefly3399
> ---
>
> Changes in v3: None
>
> Changes in v2: None
>
> arch/arm/dts/rk3399.dtsi | 55 +++-
> 1 file changed,
adds DDR configuration for LPDDR3-2GiB-1600MHz which
> is being used on the board.
>
> Signed-off-by: Manivannan Sadhasivam
Tested-by: Peter Robinson
Tested on a Rock960
> ---
>
> Changes in v3:
>
> * Add config options for USB to Ethernet and USB2 PHY
>
> Chan
> 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 th
It seems we've regressed with the Orange Pi PC for 2016.07 but I'm
wondering with the PCSI bits whether the process has changed and I've
missed the details of what's needed to flash u-boot.
With rc3 I see the follwing:
U-Boot SPL 2016.07-rc3 (Jul 07 2016 - 10:36:40)
DRAM: u MiB
Could not determin
>> It seems we've regressed with the Orange Pi PC for 2016.07 but I'm
>> wondering with the PCSI bits whether the process has changed and I've
>> missed the details of what's needed to flash u-boot.
>
>
> I just tried on my own Orange Pi PC with current master (which will
> become the final 2016.07
On Mon, Jul 11, 2016 at 4:57 AM, Andreas Färber wrote:
> Hi,
>
> Am 08.05.2016 um 08:30 schrieb Beniamino Galvani:
>> this series adds a very basic support for Amlogic S905 SoC (GXBaby)
>> and for the ODROID-C2 board [1], and is based on u-boot sources
>> available from the board vendor [2]. At th
On Tue, Jul 12, 2016 at 11:12 PM, Fabio Estevam wrote:
> Hi Breno,
>
> On Tue, Jul 12, 2016 at 12:55 PM, Breno Lima wrote:
>> Increase the boot delay to 3 seconds, because it's more convenient
>> to load u-boot from imx_usb_loader tool.
>>
>> Signed-off-by: Breno Lima
>
> Yes, this is a better v
On Thu, Apr 21, 2016 at 2:38 PM, Tom Rini wrote:
> Hey all,
>
> As promised, and only slightly late, here's -rc2. I've picked up a
> bunch of things that were outstanding and I had grabbed in patchwork and
> I felt should come in now rather than wait for the next window. There's
> some good work
Hi All,
I didn't look closely when it happened with rc1 because I saw a pull
req from Stefano shortly afterwards and I decided to try again after
that landed. With rc3 I'm still seeing the same issue.
Basically all the i.MX6 devices
(cm_fx6,mx6cuboxi,novena,riotboard,udoo,wandboard,warp) we curre
Hi Stefano,
>> I didn't look closely when it happened with rc1 because I saw a pull
>> req from Stefano shortly afterwards and I decided to try again after
>> that landed. With rc3 I'm still seeing the same issue.
>>
>> Basically all the i.MX6 devices
>> (cm_fx6,mx6cuboxi,novena,riotboard,udoo,wan
; clk->rate = parent_rate;
> "
>
> Reported-by: Peter Robinson
> Signed-off-by: Peng Fan
> Cc: Stefano Babic
> Cc: Fabio Estevam
> Cc: Tom Rini
> Cc: Anatolij Gustschin
> Cc: Peter Robinson
Tested-by: Peter Robinson
> ---
>
> Hi Peter,
>
>
Fix the device tree name for the Pine64+ for the naming that's going
into the upstream kernel.
Signed-off-by: Peter Robinson
---
configs/pine64_plus_defconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configs/pine64_plus_defconfig b/configs/pine64_plus_defconfig
On Mon, May 2, 2016 at 10:43 PM, Alexander Graf wrote:
> We can now successfully boot EFI applications from disk, but users
> may want to also run them from a PXE setup.
>
> This patch implements rudimentary network support, allowing a payload
> to send and receive network packets.
>
> With this p
On Wed, May 4, 2016 at 10:15 PM, Andre Przywara wrote:
> Rename the defconfig file for the Pine64 from pine64_plus_defconfig to
> pine64_defconfig.
> The differences between the two versions (more RAM and a different
> Ethernet PHY) don't justify two board versions, so lets stick with the
> generi
On Wed, May 4, 2016 at 10:15 PM, Andre Przywara wrote:
> This series improves the Pine64 support.
> The first patch fixes a build break, see details in the commit message.
> Patch 2/6 reverts a no longer needed memory reservation, as the firmware
> bits that used to live in DRAM now can reside in
On Wed, May 4, 2016 at 11:05 PM, André Przywara wrote:
> On 04/05/16 22:53, Peter Robinson wrote:
>> On Wed, May 4, 2016 at 10:15 PM, Andre Przywara
>> wrote:
>>> This series improves the Pine64 support.
>>> The first patch fixes a build break, see details in
Hi All,
Not sure if this has been addressed since RC3 but thought I'd
highlight it just in case. I've not had time to test 2016.05 as much
as I'd like so playing a bit of catch up here.
I'm seeing two different errors:
On a BBBlack booting off the emmc (2Gb variety) I see:
U-Boot SPL 2016.05-rc
Hi Lokesh,
>> Not sure if this has been addressed since RC3 but thought I'd
>> highlight it just in case. I've not had time to test 2016.05 as much
>> as I'd like so playing a bit of catch up here.
>
> Which defconfig are you using? Recently MMC is converted to DM, may be
> that could have caused
On 10 May 2016 20:29, "Tom Rini" wrote:
>
> On Tue, May 10, 2016 at 03:03:07PM +0100, Peter Robinson wrote:
> > Hi Lokesh,
> >
> > >> Not sure if this has been addressed since RC3 but thought I'd
> > >> highlight it just in case. I'
Add initial support for gcc6 by taking a copy of compiler-gcc5.h
Signed-off-by: Peter Robinson
---
include/linux/compiler-gcc6.h | 65 +++
1 file changed, 65 insertions(+)
create mode 100644 include/linux/compiler-gcc6.h
diff --git a/include/linux
Hi All,
Here's a couple of patches to help building on gcc-6. We're rebasing Fedora to
gcc-6 for Fedora 24 so this was the first build I've attempted with it. It
doesn't fix all problems as I also see an issue that the
generated/generic-asm-offsets.h isn't generated early enough in the build
When compiling with gcc 6 we get the following error due to ARRAY_SIZE being
defined elsewhere.
common/env_flags.c:155: undefined reference to `ARRAY_SIZE'
Signed-off-by: Peter Robinson
---
common/env_flags.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/c
>> Here's a couple of patches to help building on gcc-6. We're rebasing Fedora
>> to gcc-6 for Fedora 24 so this was the first build I've attempted with it.
>> It doesn't fix all problems as I also see an issue that the
>> generated/generic-asm-offsets.h isn't generated early enough in the build
Hi Albert,
On Wed, Feb 3, 2016 at 1:41 PM, Albert ARIBAUD
wrote:
> Hello Peter,
>
> On Wed, 3 Feb 2016 12:42:51 +0000, Peter Robinson
> wrote:
>> When compiling with gcc 6 we get the following error due to ARRAY_SIZE being
>> defined elsewhere.
>>
>> common/
>> When compiling with gcc 6 we get the following error due to ARRAY_SIZE being
>> defined elsewhere.
>>
>> common/env_flags.c:155: undefined reference to `ARRAY_SIZE'
>>
>> Signed-off-by: Peter Robinson
>
> I'm going to take http://patchwork
In the big move of CONFIG_HUSH_PARSER to config files the clearfog
somehow missed out.
Signed-off-by: Peter Robinson
---
configs/clearfog_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/configs/clearfog_defconfig b/configs/clearfog_defconfig
index 0fde640..75ea200 100644
--- a
Hi Peter,
Looking at u-boot on the hikey and when trying to work out what's
needed in terms of ATF and flashing of it the only information I can
find is a dead link to a readme [1] in your original post [2]. Any
chance you could add a README.hikey outlining what's required, where
it can be found,
On Fri, May 27, 2016 at 2:36 PM, Tom Rini wrote:
> Hey all,
>
> So, when I said a few months back that we would try doing a 2 month
> release cycle, I planned things out until the v2016.07 release, since
> that coincided with the old schedule. As I was looking at the
> ReleaseCycle page today I d
Hi Tom,
> It's release day and v2016.11-rc2 is out. I've tried to clean up my
> queue a bit, but I think there's still a few things I have outstanding.
> And I know I need to get some changes from Alexander for EFI stuff that
> I've already promised can come in. But we should also be moving towa
Hi,
> This series adds initial support for RK3368 SoC and GeekBox.
> For more details see the commit message.
>
> Will need to be rebased onto Heiko's cleanups and Kever's RK3399 series.
Did you ever get a chance to rebase these? Wouldn't mind playing with
my geekbox with an upstream u-boot.
Reg
The Cubox-i and Hummingboard series of devices have an option of
SATA on board, and depending on how the fuses are blown even the
option to boot SPL from SATA. So enable support for it so it can
be used to boot the OS from if people desire.
Signed-off-by: Peter Robinson
---
board/solidrun
On Sat, Mar 4, 2017 at 6:41 PM, Fabio Estevam wrote:
> On Sat, Mar 4, 2017 at 3:36 PM, Peter Robinson wrote:
>
>> +#ifdef CONFIG_CMD_SATA
>> + /* Only mx6q/mx6q has SATA */
>> + if (is_cpu_type(MXC_CPU_MX6Q) || is_cpu_type(MXC_CPU_MX6D))
>
> Could
On Tue, Mar 7, 2017 at 6:10 PM, Tom Rini wrote:
> On Wed, Mar 08, 2017 at 02:09:46AM +0900, Masahiro Yamada wrote:
>> 2017-02-27 15:24 GMT+09:00 Masahiro Yamada :
>> > DTC 1.4.2 or later checks DT unit-address without reg property and
>> > vice-versa, and generates lots of warnings. Fixing DT fil
On Wed, Mar 8, 2017 at 8:22 AM, Trevor Woerner wrote:
> On Wed 2017-03-08 @ 02:39:00 AM, Trevor Woerner wrote:
>> It appears as though linking u-boot with binutils-2.28 fails:
>>
>> arm-oe-linux-gnueabi-ld.bfd: u-boot: Not enough room for program
>> headers, try linking with -N
>
> ...and a
On Wed, Mar 8, 2017 at 4:43 PM, Trevor Woerner wrote:
> On Wed 2017-03-08 @ 08:43:33 AM, Peter Robinson wrote:
>> On Wed, Mar 8, 2017 at 8:22 AM, Trevor Woerner wrote:
>> > On Wed 2017-03-08 @ 02:39:00 AM, Trevor Woerner wrote:
>> >> It appears as though linking u
On Sat, Mar 11, 2017 at 3:34 PM, Tom Rini wrote:
> Borrowing from omap3_logic, switch to SPL_SYS_MALLOC_SIMPLE and moving
> the stack to DDR as soon as we're able.
Should we do that for all the omap3 devices?
> Signed-off-by: Tom Rini
> ---
> configs/omap3_overo_defconfig | 4
> 1 file ch
"On Thu, Mar 30, 2017 at 8:29 PM, Robert Nelson wrote:
> BeagleBone Black Wireless is clone of the BeagleBone Black (BBB) with
> the Ethernet replaced by a TI wl1835 wireless module.
>
> This board can be indentified by the BWAx value after A335BNLT (BBB)
> in the at24 eeprom:
> BWAx [aa 55 33 ee
On Mon, Feb 13, 2017 at 9:00 AM, Jelle van der Waa wrote:
> The rsa_st struct has been made opaque in 1.1.x, add forward compatible
> code to access the n, e, d members of rsa_struct.
>
> EVP_MD_CTX_cleanup has been removed in 1.1.x and EVP_MD_CTX_reset should be
> called to reinitialise an alread
Hi Breno and Stefano,
I finally got around to testing my udoo neo full with upstream u-boot
and with 2017.03rc1 (building rc2 now) I'm seeing a reset when it
tries to load data (I think). Details below, I'll test 2017.01 and
03rc2 shortly.
U-Boot 2017.03-rc1 (Feb 11 2017 - 23:55:08 +)
CPU:
On Tue, Feb 14, 2017 at 9:19 AM, Peter Robinson wrote:
> Hi Breno and Stefano,
>
> I finally got around to testing my udoo neo full with upstream u-boot
> and with 2017.03rc1 (building rc2 now) I'm seeing a reset when it
> tries to load data (I think). Details below, I'll
On Mon, Feb 13, 2017 at 9:57 AM, Peter Robinson wrote:
> On Mon, Feb 13, 2017 at 9:00 AM, Jelle van der Waa wrote:
>> The rsa_st struct has been made opaque in 1.1.x, add forward compatible
>> code to access the n, e, d members of rsa_struct.
>>
>> EVP_MD_CTX_cleanu
Hi Breno, Francesco and Stefano,
The following three patches fix the generic distro boot support for me on the
udoo Neo (Full edition tested).
I think all three patches are pretty straight forward and self explanatory.
Would be good to get them into 2017.03 GA.
Thanks,
Peter
__
Standard boot processes including distro boot generally expect the
default console to be defined.
Signed-off-by: Peter Robinson
---
include/configs/udoo_neo.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/configs/udoo_neo.h b/include/configs/udoo_neo.h
index 23a3685..5b46272e
The fdt_addr and ramdisk_addr_r are currently both defined to
0x8300 and that's not going to work well for anyone. Move
the ramdisk_addr_r to 0x8400.
Signed-off-by: Peter Robinson
---
include/configs/udoo_neo.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/in
The include/configs/udoo_neo.h already includes the distro defaults
include files so it seems the board was missed in the move to the
config file, whether that in initial commit or conversion, so
enable the option now and remove duplicated settings.
Signed-off-by: Peter Robinson
---
configs
On Thu, Feb 16, 2017 at 6:20 PM, Nicolas Chauvet wrote:
> Having sata first will makes preference to sata boot if
> both sata0 and mmc0 have a boot partition
>
> This change was not tested against wanboard solo/dual,
> but it does operate correctly when there is no sata disk
> connected on quad.
>
On Mon, Feb 27, 2017 at 1:29 PM, Stefano Babic wrote:
> On 27/02/2017 14:22, Tom Rini wrote:
>> On Mon, Feb 27, 2017 at 10:12:59AM +0100, Stefano Babic wrote:
>>> Hi Tom,
>>>
>>> please pull from u-boot-imx, thanks !
>>>
>>> The following changes since commit b24cf8540a85a9bf97975aadd6a7542f166c78
The CONFIG_DEFAULT_FDT_FILE expects just the file not a full path
as that might vary depending on the variant of Linux distro you
might be using.
Cc: Martin Donnelly
Signed-off-by: Peter Robinson
---
configs/ge_b650v3_defconfig | 2 +-
configs/ge_b850v3_defconfig | 2 +-
2 files changed, 2
On Thu, Jun 29, 2017 at 12:51 PM, Fabio Estevam wrote:
> Hi Peter,
>
> On Thu, Jun 29, 2017 at 8:44 AM, Peter Robinson wrote:
>> The CONFIG_DEFAULT_FDT_FILE expects just the file not a full path
>> as that might vary depending on the variant of Linux distro you
>&g
The CONFIG_DEFAULT_FDT_FILE expects just the file not a full path
as that might vary depending on the variant of Linux distro you
might be using.
Cc: Martin Donnelly
Cc: Fabio Estevam
Signed-off-by: Peter Robinson
---
configs/ge_b450v3_defconfig | 2 +-
configs/ge_b650v3_defconfig | 2
The Cubox-i and Hummingboard series of devices have an option of
SATA on board, and depending on how the fuses are blown even the
option to boot SPL from SATA. So enable support for it so it can
be used to boot the OS from if people desire.
Cc: Fabio Estevam
Signed-off-by: Peter Robinson
> On 21 June 2017 at 01:07, Peter Robinson wrote:
>>>>>> Simon, do you have some suggestions on what to do here? Thanks!
>>>>>>
>>>>>> --
>>>>>> Tom
>>>>>
>>>>> My guess is that there is alr
On Fri, Jul 7, 2017 at 4:50 PM, Stephen Warren wrote:
> On 07/06/2017 09:57 PM, Simon Glass wrote:
>>
>> Hi Stephen,
>>
>> On 6 July 2017 at 12:55, Stephen Warren wrote:
>>>
>>>
>>> On 07/06/2017 11:36 AM, s...@google.com wrote:
Update the tegra pci driver to support a live device
On Wed, Jul 5, 2017 at 8:37 AM, Peter Robinson wrote:
>> On 21 June 2017 at 01:07, Peter Robinson wrote:
>>>>>>> Simon, do you have some suggestions on what to do here? Thanks!
>>>>>>>
>>>>>>> --
>>>>>>&
On Sat, Jul 8, 2017 at 1:21 PM, Tom Rini wrote:
> On Sat, Jul 08, 2017 at 09:27:59AM +0100, Peter Robinson wrote:
>> On Wed, Jul 5, 2017 at 8:37 AM, Peter Robinson wrote:
>> >> On 21 June 2017 at 01:07, Peter Robinson wrote:
>> >>>>>>> Simon,
On Mon, Jul 10, 2017 at 4:31 AM, Simon Glass wrote:
> Hi Tom,
>
> On 9 July 2017 at 16:36, Tom Rini wrote:
>> On Sun, Jul 09, 2017 at 12:38:19PM -0600, Simon Glass wrote:
>>> Hi,
>>>
>>> On 9 July 2017 at 06:49, Tom Rini wrote:
>>> > On
On Mon, Jul 10, 2017 at 4:30 AM, Simon Glass wrote:
> This error code has not been upstreamed and is not really needed since it
> is unlikely to be triggered. Drop it to maintain compatability with
> upstream.
>
> Reported-by: Peter Robinson
Tested-by: Peter Robinson
> Si
On Mon, Jul 10, 2017 at 2:54 PM, Oliver Westermann
wrote:
> Hello,
>
> I've got multiple ARM boards with similar but not quite the same
> configurations.
> For example different IO configurations for peripheral reset lines of
> hardware used in the u-boot phase.
>
> Currently I have multiple u-Boo
On Wed, Jul 12, 2017 at 10:00 AM, Stefano Babic wrote:
> Hi Peter,
>
> your :
>
> commit ff1815632563a826cfe49fc9496a36d00febb6e3
> Author: Peter Robinson
> Date: Sat Jul 1 18:44:03 2017 +0100
>
> mx6cuboxi: Add support for sata
>
>
> breaks (indirect
On Thu, Jul 13, 2017 at 11:11 AM, Måns Rullgård wrote:
> Siarhei Siamashka writes:
>
>> On Thu, 13 Jul 2017 01:43:37 +0100
>> Måns Rullgård wrote:
>>
>>> Maxime Ripard writes:
>>>
>>> > Hi,
>>> >
>>> > I recently got a gcc 7.1 based toolchain, and it seems like it
>>> > generates unaligned code
On Fri, Jul 14, 2017 at 12:07 AM, Fabio Estevam wrote:
> Hi Stefano,
>
> On Wed, Jul 12, 2017 at 6:00 AM, Stefano Babic wrote:
>> Hi Peter,
>>
>> your :
>>
>> commit ff1815632563a826cfe49fc9496a36d00febb6e3
>> Author: Peter Robinson
>> Date:
It would be useful to have a changelog between revisions.
Peter
On Tue, Jul 25, 2017 at 12:00 PM, Leo Wen wrote:
> These three patches enable usbkeyboard drivers(usb_kbd.c) and set some
> environment
> variables to auto-start USB device. You can use the usbkeyboard instead of the
> serial input
On Mon, Apr 17, 2017 at 3:38 AM, Chen-Yu Tsai wrote:
> Hi,
>
> (Resent from my main email address.)
>
> What's the current status of u-boot-sunxi? There are still some
> patch series floating around. Some of them have been around for
> a while now, listed here in no particular order:
>
> - sunxi
On Wed, Apr 5, 2017 at 10:49 AM, Mario Six wrote:
> Hi Jelle,
>
> On Tue, Apr 4, 2017 at 11:59 PM, Jelle van der Waa wrote:
>> @@ -20,6 +20,19 @@
>> #define HAVE_ERR_REMOVE_THREAD_STATE
>> #endif
>>
>> +#if OPENSSL_VERSION_NUMBER < 0x1010L || defined(LIBRESSL_VERSION_NUMBER)
>> +void RSA_ge
o throw a look at the result instead).
>
> Signed-off-by: Andre Przywara
> Reviewed-by: Lokesh Vutla
Tested-by: Peter Robinson
Tested entire patch series on a 2Gb Pine64+ with Fedora 26. Looks good
> ---
> common/spl/spl_fit.c | 88
> ++
On Wed, May 24, 2017 at 5:35 AM, Jernej Škrabec wrote:
> Hi,
>
> Dne sreda, 24. maj 2017 ob 03:00:16 CEST je Tom Rini napisal(a):
>> On Tue, May 23, 2017 at 11:05:30PM +0200, Jernej Skrabec wrote:
>> > This commit fixes the warning produced by gcc 7.1.
>> >
>> > Signed-off-by: Jernej Skrabec
>>
>
On Mon, May 22, 2017 at 12:17 PM, Simon Glass wrote:
> Most Chromebooks support chain-loading U-Boot but instructions are
> somewhat scattered. Add a README to hold this information within the
> U-Boot tree. Also add the standard developer keys to simplify the
> instructions, since they are small
On Sat, Jun 17, 2017 at 6:45 PM, Jean-Marc Beaune wrote:
> Hello,
>
> I am new to U-Boot and trying to compile source code in order to get U-Boot
> working on a BananaPi.
>
> I get the following error while compiling the latest version of master
> branch:
>
> ImportError: No module named _libfdt
>
On Tue, Jun 20, 2017 at 1:47 AM, Tom Rini wrote:
> Hey all,
>
> It's release day and v2017.07-rc2 is out. I'm mostly happy with the
> size of the changes here and I did remember to sync the defconfigs prior
> to tagging.
>
> If anyone has critical fixes I've missed or some Kconfig migrations
> (t
> On 20 June 2017 at 05:19, Tom Rini wrote:
>> On Tue, Jun 20, 2017 at 11:15:19AM +0100, Peter Robinson wrote:
>>> On Tue, Jun 20, 2017 at 1:47 AM, Tom Rini wrote:
>>> > Hey all,
>>> >
>>> > It's release day and v2017.07-rc2 is out. I&#
Simon, do you have some suggestions on what to do here? Thanks!
--
Tom
>>>
>>> My guess is that there is already a libfdt.py in the system. Someone
>>> else reported this too.
>>>
>>> We could perhaps change the ordering in PYTHONPATH so that our one is first.
>>
>> No, I'm not
On Tue, Jun 20, 2017 at 10:49 PM, Rob Clark wrote:
> efi_disk_register() would try to iterate all the blk devices. But if
> the first one in the list failed to probe, uclass_first_device() would
> return NULL and no attempt would be made to register the remaining
> devices. Also uclass_next_devi
Enable Device Tree Overlays for a number of boards with widely available
expanion options such as HATs/Capes/DIPs/mezzanine.
Signed-off-by: Peter Robinson
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
Raspberry Pi has numerous HAT and other HW expansion options such as screens and
cameras some of which need overlays from the beginning so it makes sense to
enable evice tree overlays.
Signed-off-by: Peter Robinson
---
configs/rpi_2_defconfig | 2 ++
configs/rpi_3_32b_defconfig | 2
TI am33xx devices such as the BeagleBone devices have numerous cape options such
as screens some of which need overlays from the beginning so it makes sense to
enable evice tree overlays.
Signed-off-by: Peter Robinson
---
configs/am335x_boneblack_defconfig | 1 +
configs/am335x_evm_defconfig
96boards CE devices such as the DragonBoard and Hikey devices have numerous
mezzanine options some of which need overlays from the beginning so it makes
sense to enable device tree overlays.
Signed-off-by: Peter Robinson
---
configs/dragonboard410c_defconfig | 2 ++
configs/hikey_defconfig
CHIP and CHIP Pro devices have options of DIP addon boards some of which need
overlays from the beginning so it makes sense to enable device tree overlays.
Signed-off-by: Peter Robinson
---
configs/CHIP_defconfig | 2 ++
configs/CHIP_pro_defconfig | 2 ++
2 files changed, 4 insertions
SSL 1.1.x
> tools: kwbimage fix build with OpenSSL 1.1.x
Series tested on Fedora 27 with openssl 1.1.0e and gcc7
Tested-by: Peter Robinson
> lib/rsa/rsa-sign.c | 44 ++--
> tools/kwbimage.c | 36 ++
Drop include of netdev.h as it's a SATA driver not a network driver.
Signed-off-by: Peter Robinson
---
drivers/block/sata_ceva.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/block/sata_ceva.c b/drivers/block/sata_ceva.c
index 9b5466483a..9ac195bac2 100644
--- a/drivers/
On Sat, May 13, 2017 at 1:07 AM, Ruchika Gupta wrote:
> kASLR support in kernel requires a random number to be passed via
> chosen/kaslr-seed propert. sec_firmware generates this random seed
> which can then be passed in the device tree node
Is that functionality generic that it can be consumed b
On Sat, Mar 4, 2017 at 7:05 PM, Tom Rini wrote:
> On Sat, Mar 04, 2017 at 06:36:28PM +0000, Peter Robinson wrote:
>> The Cubox-i and Hummingboard series of devices have an option of
>> SATA on board, and depending on how the fuses are blown even the
>> option to boot SPL
Hi Tom and Fabio,
First patch converts CMD_SATA over to Kconfig, plus a few generic cleanups for
a few of the configs there. The second of the patches is basically the same one
as befoe with the associated changes for CMD_SATA move.
Peter
___
U-Boot
601 - 700 of 991 matches
Mail list logo
