The function dev_read_addr calls ofnode_get_addr_index in the live tree
case, which does not apply bus translations to the address read from the
device tree. This results in illegal addresses on boards that rely on
bus translations being applied.
Fix this situation by applying bus translations in
On 23.11.2017 18:59, Anatolij Gustschin wrote:
This reverts commit 13c531e52a09b4e6ffa8b5a1457199b0a574cb27.
The error message with FIT style image mentioned in the above commit
only happens when booting using FIT image containing bzImage kernel
and without setup node (setup.bin). The current do
On 11/23/2017 11:55 PM, Marek Vasut wrote:
> On 11/23/2017 03:52 PM, Jean-Jacques Hiblot wrote:
>>
>>
>> On 22/11/2017 15:00, Marek Vasut wrote:
>>> On 11/22/2017 01:09 PM, Jaehoon Chung wrote:
On 11/22/2017 12:13 AM, Jean-Jacques Hiblot wrote:
> This series applies on top of "[PATCH v2 00
Hello Ladislav,
Sorry for digging into it so late...
Am 22.11.2017 um 09:25 schrieb Ladislav Michl:
On Wed, Nov 22, 2017 at 09:09:36AM +0100, Wolfgang Denk wrote:
Dear Ladislav,
In message <2017112121.ryicwv6tyh5rye2e@lenoch> you wrote:
diff --git a/fs/ubifs/ubifs.c b/fs/ubifs/ubifs.c
i
Hello Calvin
Please find few comments inline.
Regards
Poonam
> -Original Message-
> From: U-Boot [mailto:u-boot-boun...@lists.denx.de] On Behalf Of Calvin
> Johnson
> Sent: Monday, October 09, 2017 2:42 PM
> To: u-boot@lists.denx.de
> Cc: joe.hershber...@ni.com; Anji Jagarlmudi
> Subjec
Hello Calvin,
Minor comments below.
Regards
Poonam
> -Original Message-
> From: U-Boot [mailto:u-boot-boun...@lists.denx.de] On Behalf Of Calvin
> Johnson
> Sent: Monday, October 09, 2017 2:42 PM
> To: u-boot@lists.denx.de
> Cc: joe.hershber...@ni.com; Anji Jagarlmudi
> Subject: [U-Boot]
On 11/24/2017 04:29 AM, Bin Meng wrote:
> Hi Marek,
>
> On Mon, Nov 6, 2017 at 11:39 PM, Marek Vasut wrote:
>> On 11/06/2017 04:39 PM, Bin Meng wrote:
>>> As discussed with Marek, this adds myself as the maintainer to
>>> offload the USB xHCI part.
>>>
>>> Signed-off-by: Bin Meng
>>
>> Acked-by:
On Wed, Nov 22, 2017 at 02:18:59PM +1100, Jonathan Gray wrote:
> Zero partition_signature in the efi_device_path_hard_drive_path
> structure when signature_type is 0 (no signature) as required by the
> UEFI specification.
>
> This is required so that efi_dp_match() will work as expected
> when doi
Hi Marek,
On Mon, Nov 6, 2017 at 11:39 PM, Marek Vasut wrote:
> On 11/06/2017 04:39 PM, Bin Meng wrote:
>> As discussed with Marek, this adds myself as the maintainer to
>> offload the USB xHCI part.
>>
>> Signed-off-by: Bin Meng
>
> Acked-by: Marek Vasut
>
I thought this was picked up by Tom
Hi Tom,
Happy Thanksgiving. Herewith some test fix-ups.
After this I have some patches to enable these tests with 'make
tests'. But I'm a little nervous about it. One of them needs Python
code coverage tools which not everyone will have. So I'll take those
separately after I've tried with travis-
Hi Lukasz,
On 21 November 2017 at 02:55, Lukasz Majewski wrote:
>
> On Mon, 20 Nov 2017 15:33:28 -0700
> Simon Glass wrote:
>
> > Add the logging header file and implementation with some configuration
> > options to control it.
>
> Despite one question -
>
> Reviewed-by: Lukasz Majewski
Thanks
These warnings are not useful for binman tests. Disable them.
Signed-off-by: Simon Glass
---
tools/dtoc/fdt_util.py | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
Applied to u-boot-dm thanks!
___
U-Boot mailing list
U-Boot@lists.denx.de
http
At present these tests use the same filename as patman. This adds
confusion when running all tests, since error messages look very similar.
In fact binman tries to run the wrong tests at present.
Rename the tests.
Signed-off-by: Simon Glass
---
tools/binman/binman.py | 4 ++--
The tests were broken by two separate commits which adjusted the output
when boards are listed. Fix this by adding back a PowerPC board and
putting the name of each board in the test.
Fixes: b9f7d881 (powerpc, 5xx: remove some "5xx" remains)
Fixes: 8d7523c5 (buildman: Allow showing the list of boa
This script runs the tests but does not report failure. Also it always
returns an exit code of 0 even on failure.
Fix these problems by checking the result of each test.
Signed-off-by: Simon Glass
---
test/run | 20 +---
1 file changed, 17 insertions(+), 3 deletions(-)
Applied
Accessing the network slows down the test and limits the environment in
which it can be run. Add an option to disable network tests.
Signed-off-by: Simon Glass
---
tools/buildman/buildman.py | 6 --
tools/buildman/cmdline.py | 2 ++
tools/buildman/test.py | 7 +--
3 files changed,
There is a debugging option in the Makefile to allow people to figure out
which u-boot.dtsi files are used in the build. But is it not easy to use
since it only shows files it finds, not those it is looking for. Update it
and update the mention of it to the docs.
Signed-off-by: Simon Glass
---
Rather that overwrite this, append to it, in case the caller has already
set up the path correctly.
Signed-off-by: Simon Glass
---
tools/binman/binman.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Applied to u-boot-dm thanks!
___
U-Boot ma
Add a test for this feature. It allows SPL to hold a pointer to the
microcode block. This is used for 64-bit U-Boot on x86.
Signed-off-by: Simon Glass
---
tools/binman/etype/u_boot_spl_with_ucode_ptr.py | 2 +-
tools/binman/ftest.py | 84 -
too
The tool has changed slightly since it was originally written. Update the
tests to suit.
Signed-off-by: Simon Glass
---
tools/dtoc/test_dtoc.py | 82 ++---
1 file changed, 37 insertions(+), 45 deletions(-)
Applied to u-boot-dm thanks!
___
There is a little check at the top of entry.py which decides if importlib
is available. At present this has no test coverage. To add this we will
need to import the module twice, once with importlib and once without.
In preparation for allowing a test to control the importing of this
module, remove
Add a main program so that the tests can be executed directly, without
going through the main binman program.
Signed-off-by: Simon Glass
---
tools/binman/entry_test.py | 4
tools/binman/ftest.py | 4
2 files changed, 8 insertions(+)
Applied to u-boot-dm thanks!
_
Files that are never imported are not shown in the test-coverage report.
Detect these and show an error.
Signed-off-by: Simon Glass
---
tools/binman/binman.py | 22 +++---
1 file changed, 19 insertions(+), 3 deletions(-)
Applied to u-boot-dm thanks!
This allows us to put the 16-bit x86 start-up code in SPL. Add a test for
it.
Signed-off-by: Simon Glass
---
tools/binman/ftest.py| 10 +-
tools/binman/test/48_x86-start16-spl.dts | 13 +
2 files changed, 22 insertions(+), 1 deletion(-)
create mode 10064
The checkpatch tool was updated but the patman tests were not. Fix this.
Signed-off-by: Simon Glass
---
tools/patman/test.py | 41 ++---
1 file changed, 26 insertions(+), 15 deletions(-)
Applied to u-boot-dm thanks!
__
Add a test that we can pad the BSS with zero bytes.
Signed-off-by: Simon Glass
---
tools/binman/ftest.py| 9 +
tools/binman/test/47_spl_bss_pad.dts | 17 +
tools/binman/test/Makefile | 5 -
tools/binman/test/bss_data | Bin 0 -
The process is not obvious. Add a little section to explain how to move a
board to use binman.
Signed-off-by: Simon Glass
---
tools/binman/README | 21 +
1 file changed, 21 insertions(+)
Applied to u-boot-dm thanks!
___
U-Boot mai
Add a test that the 'entry' module works with or without importlib.
The tests are numbered so that they are executed in the correct order.
Signed-off-by: Simon Glass
---
tools/binman/binman.py | 8 ++--
tools/binman/entry_test.py | 30 ++
2 files changed, 36
These test programs are includedd as binary files in U-Boot to avoid
having to build them (and associated toolchain differences). Instructions
on building are in the files themselves, but it seems better to provide
a Makefile which can be manually run when desired.
Add a Makefile, separate from th
Make a minor tweak to fix test coverage.
Signed-off-by: Simon Glass
---
tools/binman/etype/u_boot_ucode.py | 11 ---
1 file changed, 4 insertions(+), 7 deletions(-)
Applied to u-boot-dm thanks!
___
U-Boot mailing list
U-Boot@lists.denx.de
htt
Return exit code 1 when test fail so that callers can detect this.
Signed-off-by: Simon Glass
---
tools/binman/binman.py | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
Applied to u-boot-dm thanks!
___
U-Boot mailing list
U-Boot@lists.d
MRC (Memory Reference Code) is a binary blob used to set up the SDRAM
controller on some Intel boards. Add a test for this feature.
With this test coverage on binman is back up to 100%.
Signed-off-by: Simon Glass
---
tools/binman/ftest.py | 7 +++
tools/binman/test/50_intel_m
For debugging efi_loader we need the capability to print EFI
device paths. With this patch we can write:
debug("device path: %pD", dp);
A possible output would be
device path: /MemoryMapped(0x0,0x3ff93a82,0x3ff93a82)
Cc: Wolfgang Denk
Suggested-by: Rob Clark
Signed-off-by: Heinrich Sc
The changes in u-boot to implement this were sent Nov 8, and
I've see no mention of it, in the mailing list.
What's the next step?
Thanks
Duncan Hare d...@synoia.com
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
On 11/21/2017 03:16 PM, Wolfgang Denk wrote:
> Dear Heinrich Schuchardt,
>
> In message you wrote:
>>
>> +u16 *str = efi_dp_str((struct efi_device_path *)dp);
>> +
>> +buf = string16(buf, end, str, field_width, precision, flags);
>> +efi_free_pool(str);
>>>
Provide comments for efi_convert_device_node_to_text()
and efi_convert_device_path_to_text().
Signed-off-by: Heinrich Schuchardt
---
lib/efi_loader/efi_device_path_to_text.c | 24
1 file changed, 24 insertions(+)
diff --git a/lib/efi_loader/efi_device_path_to_text.c
b/
According to the UEFI spec we have to return NULL if the device
path argument is NULL.
Signed-off-by: Heinrich Schuchardt
---
lib/efi_loader/efi_device_path_to_text.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/lib/efi_loader/efi_device_path_to_text.c
b/lib/efi_loade
Hi Neil,
> Hi,
>
> I'm having a strange issue while porting the DART-MX6 and it's
> carrier board to mainline U-Boot.
>
> Everything works as expected except "fatls" where I get the following
> output :
Please look into:
http://patchwork.ozlabs.org/patch/831183/
IN short:
You may need to fix
This reverts commit 13c531e52a09b4e6ffa8b5a1457199b0a574cb27.
The error message with FIT style image mentioned in the above commit
only happens when booting using FIT image containing bzImage kernel
and without setup node (setup.bin). The current documentation for
x86 FIT support in doc/uImage.FIT
On Thu, 23 Nov 2017 08:53:10 +
"Amartya Shreyank (RBEI/ESD2)" wrote:
> Hi,
>
> I am trying to configure uboot for xip from eim nor for a custom
> imx6solo board. Can someone suggest what modifications are needed for
> this in uboot. I have borrowed configurations from imx6 based boards
> and
> On 23 Nov 2017, at 15:51, Philipp Tomsich
> wrote:
>
>> With the ATF capable of accessing the FDT passed to the next stage,
>> we can specify configuration items for the ATF in the /config path.
>>
>> This adds the arm-trusted-firmware,reset-gpio that conveys the number
>> of the GPIO used to
On 22.11.2017 11:39, Felix Brack wrote:
> Hello Simon,
>
> Many thanks for taking the time to review my patch.
>
> On 20.11.2017 16:38, Simon Glass wrote:
>> Hi Felix,
>>
>>> +
>>> +/* platform data */
>>> +struct tps65910_pdata {
>>> + u32 supply[TPS65910_NUM_SUPPLIES]; /* regulator supp
Hi,
I'm having a strange issue while porting the DART-MX6 and it's carrier board to
mainline U-Boot.
Everything works as expected except "fatls" where I get the following output :
=> fatls mmc 0:1
CACHE: Misaligned operation at range [4f59dfc8, 4f59e7c8]
CACHE: Misaligned operation at range [4f
> This commit updates the .its file for the RK3399-Q7 to use the new
> features and demonstrates how to use those:
> * it marks the ATF as the 'firmware'
> * it tracks the OS-type for U-Boot and ATF
> * it loads the PMU (M0) firmware to DRAM and records the location
>to /fit-images (where ou
> This tracks the SPL changes for ATF for the RK3368-uQ7:
> * renames ATF_SUPPORT to ATF
> * drops CONFIG_SPL_ATF_TEXT_BASE (now dynamically retrieved from
>the .itb file)
>
> Signed-off-by: Philipp Tomsich
> Reviewed-by: Simon Glass
> ---
>
> configs/lion-rk3368_defconfig | 3 +--
> 1 f
> This defconfig update makes use of the new features:
> * CONFIG_ROCKCHIP_SPL_RESERVE_IRAM is now set to 0, as there is no
>overlap between the M0 firmware and the ATF (we load this to DRAM
>and relocate it to its final location within the ATF)
> * tracks the ATF_SUPPORT -> ATF renaming
> This tracks the SPL changes for ATF for the Firefly:
> * renames ATF_SUPPORT to ATF
> * drops CONFIG_SPL_ATF_TEXT_BASE
>
> Signed-off-by: Philipp Tomsich
> Reviewed-by: Simon Glass
> ---
>
> configs/firefly-rk3399_defconfig | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
Appl
> For the RK3368-uQ7, we can now update the .its file to mark the
> Trusted Firmware as out 'firmware' bootable and annotate both ATF and
> U-Boot with an OS-type.
>
> Signed-off-by: Philipp Tomsich
> Reviewed-by: Simon Glass
> ---
>
> board/theobroma-systems/lion_rk3368/fit_spl_atf.its | 6 ++
On 11/23/2017 03:52 PM, Jean-Jacques Hiblot wrote:
>
>
> On 22/11/2017 15:00, Marek Vasut wrote:
>> On 11/22/2017 01:09 PM, Jaehoon Chung wrote:
>>> On 11/22/2017 12:13 AM, Jean-Jacques Hiblot wrote:
This series applies on top of "[PATCH v2 00/26] mmc: Add support for
HS200
and UHS
> If a FDT was loaded (e.g. to append it to U-Boot image), we store it's
> address and record information for all loadables into this FDT. This
> allows us to easily keep track of images for multiple privilege levels
> (e.g. with ATF) or of firmware images preloaded into temporary
> locations (e.g
On 22/11/2017 15:00, Marek Vasut wrote:
On 11/22/2017 01:09 PM, Jaehoon Chung wrote:
On 11/22/2017 12:13 AM, Jean-Jacques Hiblot wrote:
This series applies on top of "[PATCH v2 00/26] mmc: Add support for HS200
and UHS modes"
It fixes a bug with old SD and MMC cards that support only the leg
> Having CONFIG_SPL_ATF seems more natural.
> Rename it, while it it is easy and there's few boards that use it
> (only RK3399 and RK3368 boards).
>
> Signed-off-by: Philipp Tomsich
> Reviewed-by: Simon Glass
> ---
>
> common/spl/Kconfig | 2 +-
> common/spl/Makefile | 2 +-
> 2 files changed
> To better support bootin through an ATF or OPTEE, we need to
> streamline some of the logic for when the FDT is appended to an image:
> depending on the image type, we'd like to append the FDT not at all
> (the case for the OS boot), to the 'firmware' image (if it is a
> U-Boot) or to one of the
> With the ATF capable of accessing the FDT passed to the next stage,
> we can specify configuration items for the ATF in the /config path.
>
> This adds the arm-trusted-firmware,reset-gpio that conveys the number
> of the GPIO used to reset the board (used, when a reboot is requested
> from ATF v
> This adds a new interface spl_invoke_atf() that takes a spl_image_info
> argument and then derives the necessary parameters for the ATF entry.
> Based on the additional information recorded (into /fit-images) from
> the FIT loadables, we can now easily locate the next boot stage.
>
> We now pass
> The SPL_ATF_TEXT_BASE configuration item has become obsolete.
> Remove it from Kconfig.
>
> Signed-off-by: Philipp Tomsich
> Reviewed-by: Simon Glass
> ---
>
> common/spl/Kconfig | 6 --
> 1 file changed, 6 deletions(-)
>
Applied to u-boot-rockchip, thanks!
> During the loading of more complex FIT images (e.g. when the invoked
> next stage needs to find additional firmware for a power-management
> core... or if there are multiple images for different privilege levels
> started in parallel), it is helpful to create a record of what images
> are loaded
> To boot on ARMv8 systems with ARM Trusted Firmware, we need to
> assemble an ATF-specific parameter structure and also provide the
> address of the images started by ATF (e.g. BL3-3, which may be the
> full U-Boot).
>
> To allow us to identify an ARM Trusted Firmware contained in a FIT
> image,
> Mainly a stylistic change: convert the load_addr and entry_point
> fields of struct spl_image_info to uintptr_t (from ulong).
>
> Signed-off-by: Philipp Tomsich
> Reviewed-by: Simon Glass
> ---
>
> include/spl.h | 9 ++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
>
Applied to
> When loading a full U-Boot with detached device-tree using the SPL FIT
> backend, we should store the address of the FDT loaded as part of the
> SPL image info: this allows us to fixup the FDT with additional info
> we may want to propagate onward.
>
> Signed-off-by: Philipp Tomsich
> Reviewed-
On Wed, 27 Sep 2017, Kever Yang wrote:
evb-rk3128 is an evb from Rockchip based on rk3128 SoC:
- 2 USB2.0 Host port;
- 1 HDMI port;
- 2 10/100M eth port;
- 2GB ddr;
- 16GB eMMC;
- UART to USB debug port;
Signed-off-by: Kever Yang
Acked-by: Philipp Tomsich
Reviewed-by: Philipp Tomsich
Se
On Wed, 27 Sep 2017, Kever Yang wrote:
Add rk3128 sysreset driver.
Signed-off-by: Kever Yang
Acked-by: Philipp Tomsich
Reviewed-by: Philipp Tomsich
See below for requested changes.
---
drivers/sysreset/Makefile | 1 +
drivers/sysreset/sysreset_rk3128.c | 45 +
On Wed, 27 Sep 2017, Kever Yang wrote:
Add rk3128 clock driver and cru structure definition.
Signed-off-by: Kever Yang
Acked-by: Philipp Tomsich
Reviewed-by: Philipp Tomsich
See below for requested changes.
---
arch/arm/include/asm/arch-rockchip/cru_rk3128.h | 173
arch/a
From: Ben Whitten
This board is based on the Atmel sama5d3 eval boards.
Supporting the following features:
- Boot from NAND Flash
- Ethernet
- FIT
- SPL
Signed-off-by: Ben Whitten
Signed-off-by: Dan Kephart
---
Changes for v2:
- Updated to current master
- Moved some configs to kconf
From: Ben Whitten
This board is based on the Atmel 9x5 eval board.
Supporting the following features:
- Boot from NAND Flash
- Ethernet
- FIT
- SPL
Signed-off-by: Ben Whitten
Signed-off-by: Dan Kephart
---
Changes for v2:
- Updated to current master
- Moved some configs to kconfig
Hi,
Resubmitting the board patches based off current master branch at
16fa2eb with updates to configs.
Ben Whitten (2):
board: laird: add WB45N CPU module
board: laird: add WB50N CPU module
arch/arm/mach-at91/Kconfig | 14 +++
arch/arm/mach-at91/include/mach/gpio.h | 2 +
boa
Hi,
I am trying to configure uboot for xip from eim nor for a custom imx6solo board.
Can someone suggest what modifications are needed for this in uboot.
I have borrowed configurations from imx6 based boards and stripped them down to
bare minimum.
Also, if anyone can explain how do we select the
Heiko,
I test with Rockchip op-tee from rkbin and it works fine, let me
test with
upstream op-tee again and get back to you.
Thanks,
- Kever
On 11/22/2017 06:00 PM, Heiko Stuebner wrote:
Am Dienstag, 21. November 2017, 09:43:57 CET schrieb Andrew F. Davis:
On 11/20/2017 03:25 PM, Heiko
The kernel gets the ethernet MAC from the ethaddr variable, the omap boards for
devices with USB based eth adapters just set the usbethaddr which doesn't appear
to get passed to the kernel. The same Raspberry Pi code sets both ethaddr and
usbethaddr so lets do that so linux (tested 4.13 and 4.14) g
imx_set_wdog_powerdown() is always used to disable the power down
enable bit, so remove the boolean parameter of the function.
It is also a bit strange to write a boolean value into registers,
so this new version makes explicit that we are writing 0.
While at it, rename it to imx_wdog_disable_pow
On 11/23/2017 12:31 PM, Lukasz Majewski wrote:
> Dear Marek,
>
> Please find pull request for dfu repository:
>
> The following changes since commit
> 786d0faa19c1a2e9b7a98cc4e23bd8669f4c6870:
>
> usb: ehci: do not invalidate a NULL buffer (2017-11-21 12:27:38 +0100)
>
> are available in the
On 11/22/2017 05:31 PM, Dr. Philipp Tomsich wrote:
>
>> On 22 Nov 2017, at 17:23, Marek Vasut wrote:
>>
>> On 11/22/2017 05:15 PM, Philipp Tomsich wrote:
>>> When usb_hub_reset_devices is called, it should be passed both an
>>> indicator which hub it should operate on and what port number (local
On 23/11/2017 12:18, Fabio Estevam wrote:
> From: Fabio Estevam
>
> Clear powerdown enable bit for WDOG3 on i.MX6ULL to avoid unwanted
> kernel reboots.
>
> Suggested-by: Ye Li
> Signed-off-by: Fabio Estevam
> ---
> arch/arm/mach-imx/init.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion
On 23/11/2017 12:18, Fabio Estevam wrote:
> From: Fabio Estevam
>
> i.MX6ULL has the same WDOG3 base address as i.MX6UL, so take this
> into account in the base address definition.
>
> Signed-off-by: Fabio Estevam
> ---
> arch/arm/include/asm/arch-mx6/imx-regs.h | 2 +-
> 1 file changed, 1 ins
Dear Marek,
Please find pull request for dfu repository:
The following changes since commit
786d0faa19c1a2e9b7a98cc4e23bd8669f4c6870:
usb: ehci: do not invalidate a NULL buffer (2017-11-21 12:27:38 +0100)
are available in the git repository at:
git://git.denx.de/u-boot-dfu.git
for you to
> -Original Message-
> From: Fabio Estevam [mailto:feste...@gmail.com]
> Sent: Thursday, November 23, 2017 7:19 PM
> To: sba...@denx.de
> Cc: u-boot@lists.denx.de; Ye Li ; Peng Fan
> ; Fabio Estevam
> Subject: [PATCH 1/2] mx6ull: Fix WDOG3 base address
>
> From: Fabio Estevam
>
> i.MX
> -Original Message-
> From: Fabio Estevam [mailto:feste...@gmail.com]
> Sent: Thursday, November 23, 2017 7:19 PM
> To: sba...@denx.de
> Cc: u-boot@lists.denx.de; Ye Li ; Peng Fan
> ; Fabio Estevam
> Subject: [PATCH 2/2] imx: Also clear powerdown enable bit for WDOG3 on
> i.MX6ULL
>
>
Linux device tree contains "ethernet" node for all possible
interface supported by SoC i.e. LS1046A.
It is not necessary for a SerDes protocol to support all possible
interface. So disable unavailable "ethernet" node in device tree.
Also, enable FDT_SEQ_MACADDR_FROM_ENV to fetch MAC address
seque
The MAC addresses get fixed in the device tree for "ethernet" nodes
is by using trailing number behind "ethernet" found in "/aliases".
It may not be necessary for the "ethernet" nodes to be sequential.
There can be gaps in between or any node disabled
So provide a support to fetch MAC addr sequent
"ethernet" node fix-up for device tree happens before Linux boot.
There can be requirement of updating "ethernet" node even before
fix-up. So, add support of updating "ethernet" node.
Signed-off-by: Prabhakar Kushwaha
---
Changes for v2: Sending as it is
Changes for v2: Sending as it is
arch/a
The MAC addresses get fixed in the device tree for "ethernet" nodes
is by using trailing number behind "ethernet" found in "/aliases".
It may not be necessary for the "ethernet" nodes to be sequential.
There can be gaps in between or any ethenet node disabled.
Reason for gaps is because the availa
Hi Ye Li,
On Thu, Nov 23, 2017 at 12:52 AM, Fabio Estevam wrote:
> Hi Ye Li,
>
> On Thu, Nov 23, 2017 at 12:05 AM, Ye Li wrote:
>
>> The wdog3 is not disabled for i.mx6ull on mainline U-boot. Please fix it in
>> imx_set_wdog_powerdown.
>>
>>if (is_mx6sx() || is_mx6ul() || is_mx6ull() || is
From: Fabio Estevam
Clear powerdown enable bit for WDOG3 on i.MX6ULL to avoid unwanted
kernel reboots.
Suggested-by: Ye Li
Signed-off-by: Fabio Estevam
---
arch/arm/mach-imx/init.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/mach-imx/init.c b/arch/arm/mach-imx
From: Fabio Estevam
i.MX6ULL has the same WDOG3 base address as i.MX6UL, so take this
into account in the base address definition.
Signed-off-by: Fabio Estevam
---
arch/arm/include/asm/arch-mx6/imx-regs.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/include/asm/
Hi Philipp,
> This adds a driver for the FAN53555 family of regulators.
>
> While these devices support a 'normal' and 'suspend' mode (controlled
> via an external pin) to switch between two programmable voltages, this
> incarnation of the driver assumes that the device is always operating
> in '
On 11/23/2017 10:46 AM, Siva Durga Prasad Paladugu wrote:
> Hi Jaehoon,
>
>> -Original Message-
>> From: U-Boot [mailto:u-boot-boun...@lists.denx.de] On Behalf Of Jaehoon
>> Chung
>> Sent: Friday, October 20, 2017 5:02 PM
>> To: Jean-Jacques Hiblot ; tr...@konsulko.com;
>> kis...@ti.com; s
Hi Jaehoon,
> -Original Message-
> From: U-Boot [mailto:u-boot-boun...@lists.denx.de] On Behalf Of Jaehoon
> Chung
> Sent: Friday, October 20, 2017 5:02 PM
> To: Jean-Jacques Hiblot ; tr...@konsulko.com;
> kis...@ti.com; s...@chromium.org
> Cc: u-boot@lists.denx.de
> Subject: Re: [U-Boot]
On Wed, 22 Nov 2017 11:15:26 -0200
Fabio Estevam wrote:
> From: Fabio Estevam
>
> NXP development boards based on i.MX6/i.MX7 contain the board
> revision information stored in the fuses.
>
> Introduce a common function that can be shared by different boards and
> convert mx6sabreauto to use t
On Wed, 22 Nov 2017 11:15:27 -0200
Fabio Estevam wrote:
> From: Fabio Estevam
>
> Currently only imx6sx-sdb.dtb is loaded, but if revA board is used the
> correct dtb is imx6sx-sdb-reva.dtb, so make this possible.
>
> While at it, remove an extra 'mmc dev'.
>
> Signed-off-by: Fabio Estevam
>
Hi Fabio,
> From: Fabio Estevam
>
> mx6sxsabresd can run different kernel versions, such as NXP 4.1 or
> mainline.
> Currently the rootfs location is passed via mmcblk number and the
> problem with this approach is that the mmcblk number for the SD
> card changes depending on the kernel version
Unset USE_BOOTCOMMAND for all ls1088 defconfig files to fix
redefinition error
USE_BOOTCOMMAND was introduced in commit-id b6251db8c3f
("Kconfig: Introduce USE_BOOTCOMMAND and migrate BOOTCOMMAND").
Signed-off-by: Ashish Kumar
---
configs/ls1088aqds_qspi_defconfig| 1 +
configs/ls1088aq
"ethernet" node fix-up for device tree happens before Linux boot.
There can be requirement of updating "ethernet" node even before
fix-up. So, add support of updating "ethernet" node.
Signed-off-by: Prabhakar Kushwaha
---
Changes for v2: Sending as it is
arch/arm/lib/bootm-fdt.c | 12 +
Linux device tree contains "ethernet" node for all possible
interface supported by SoC i.e. LS1046A.
It is not necessary for a SerDes protocol to support all possible
interface. So disable unavailable "ethernet" node in device tree.
Also, enable FDT_SEQ_MACADDR_FROM_ENV to fetch MAC address
seque
The MAC addresses get fixed in the device tree for "ethernet" nodes
is by using trailing number behind "ethernet" found in "/aliases".
It may not be necessary for the "ethernet" nodes to be sequential.
There can be gaps in between or any node disabled
So provide a support to fetch MAC addr sequent
The MAC addresses get fixed in the device tree for "ethernet" nodes
is by using trailing number behind "ethernet" found in "/aliases".
It may not be necessary for the "ethernet" nodes to be sequential.
There can be gaps in between or any ethenet node disabled.
Reason for gaps is because the availa
Hi Simon,
On Mon, 2017-11-20 at 08:38 -0700, Simon Glass wrote:
> Hi Wilson,
>
> On 7 November 2017 at 19:30, Wilson Lee wrote:
> >
> > uint8_t used in sha1_der_prefix array was not able to recognize by
> > compiler when try to build the tools using 'HOSTCC'. That is
> > because,
> > uint8_t is
96 matches
Mail list logo
