On 04/23/2017 04:10 AM, Simon Glass wrote:
> Hi Heinrick,
>
> On 19 April 2017 at 05:26, Heinrich Schuchardt wrote:
>> When iterating over the devices of an uclass the iteration stops
>> at the first device that cannot be probed.
>> When calling booefi this will result in no block device being
>>
Hi Heinrick,
On 19 April 2017 at 05:26, Heinrich Schuchardt wrote:
> When iterating over the devices of an uclass the iteration stops
> at the first device that cannot be probed.
> When calling booefi this will result in no block device being
> passed to the EFI executable if the first device can
Hi Andy,
On 19 April 2017 at 05:50, Andy Shevchenko
wrote:
> On Tue, 2017-04-18 at 18:12 -0600, Simon Glass wrote:
>> Hi Andy,
>>
>> On 18 April 2017 at 08:45, Andy Shevchenko
>> wrote:
>> > On Tue, 2017-04-18 at 08:33 -0600, Simon Glass wrote:
>> > > Hi Andy,
>> > >
>> > > On 18 April 2017 at 0
We should not call out to board code from drivers. With driver model,
mmc_power_init() already has code to use a named regulator, but the
legacy code path remains. Update the code to make this clear.
Signed-off-by: Simon Glass
---
drivers/mmc/mmc.c | 15 +++
1 file changed, 11 inser
Hi Kever,
On 13 April 2017 at 04:11, Kever Yang wrote:
> Hi Simon,
>
> When I try to update
> rk3399.dtsi(https://patchwork.ozlabs.org/patch/749901/), I get error report
> like this:
>
> spl/dts/dt-platdata.c:10:17: error: ‘dtv_clock_controller_at_ff76’
> undeclared here (not in a function)
>
At present dtoc assumes that nodes which are phandles do not themselves
reference other phandle nodes. Unfortunately this is not necessarilly
true. As a result we can currently output C code which does not compile
because a node declaration can be referenced before it is declared.
Adjust the code
The code to generate the tables is quite long. Move the node-output code
into its own function.
Signed-off-by: Simon Glass
---
tools/dtoc/dtoc.py | 96 +-
1 file changed, 52 insertions(+), 44 deletions(-)
diff --git a/tools/dtoc/dtoc.py b/too
Hi,
On 19 April 2017 at 15:34, Simon Glass wrote:
> On 19 April 2017 at 15:06, Andreas Färber wrote:
>> Am 19.04.2017 um 13:26 schrieb Heinrich Schuchardt:
>>> When iterating over the devices of an uclass the iteration stops
>>> at the first device that cannot be probed.
>>> When calling booefi
+Tom
On 19 April 2017 at 07:24, Philipp Tomsich
wrote:
>
> This change encodes the CC list to UTF-8 to avoid failures on
> maintainer-addresses that include non-ASCII characters (observed on
> Debian 7.11 with Python 2.7.3).
>
> Without this, I get the following failure:
> Traceback (most recen
On 04/22/2017 05:47 PM, Andreas Färber wrote:
> Am 22.04.2017 um 16:19 schrieb Heinrich Schuchardt:
>> On 04/22/2017 03:10 PM, Andreas Färber wrote:
>>> Am 22.04.2017 um 14:59 schrieb Heinrich Schuchardt:
On 01/15/2017 07:52 PM, Andreas Färber wrote:
> Use the generic "distro" boot framewo
Am 22.04.2017 um 16:19 schrieb Heinrich Schuchardt:
> On 04/22/2017 03:10 PM, Andreas Färber wrote:
>> Am 22.04.2017 um 14:59 schrieb Heinrich Schuchardt:
>>> On 01/15/2017 07:52 PM, Andreas Färber wrote:
Use the generic "distro" boot framework to enable automatic DHCP boot.
The fdt
On 04/22/2017 03:10 PM, Andreas Färber wrote:
> Hi,
>
> Am 22.04.2017 um 14:59 schrieb Heinrich Schuchardt:
>> On 01/15/2017 07:52 PM, Andreas Färber wrote:
>>> Use the generic "distro" boot framework to enable automatic DHCP boot.
>>>
>>> The fdt and kernel addresses are adopted from downstream;
On 04/22/2017 03:10 PM, Andreas Färber wrote:
> Hi,
>
> Am 22.04.2017 um 14:59 schrieb Heinrich Schuchardt:
>> On 01/15/2017 07:52 PM, Andreas Färber wrote:
>>> Use the generic "distro" boot framework to enable automatic DHCP boot.
>>>
>>> The fdt and kernel addresses are adopted from downstream;
Hi,
Am 22.04.2017 um 14:59 schrieb Heinrich Schuchardt:
> On 01/15/2017 07:52 PM, Andreas Färber wrote:
>> Use the generic "distro" boot framework to enable automatic DHCP boot.
>>
>> The fdt and kernel addresses are adopted from downstream; ramdisk and
>> scriptaddr addresses were chosen arbitrar
Add debug UART functions to permit omap specific ns16550 to
provide an early debug UART. This is mostly in common with
DEBUG_UART_NS16550 except for Mode definition register which
is required for selecting UART mode(16x auto-baud or 13x mode).
Signed-off-by: Lokesh Vutla
---
- I understand it is
As per board documentation, default sysclk is 100MHz
So, update the default value in ls0280ardb board file
to return 100MHz
Signed-off-by: Priyanka Jain
---
board/freescale/ls2080ardb/ls2080ardb.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/board/freescale/ls2080ard
LS2081ARDB board is similar to LS2080ARDB board
with few differences like
It hosts LS2081A SoC
Default boot source is QSPI-boot
It does not have IFC interface
RTC and QSPI flash device are different
It provides QIXIS access via I2C
Signed-off-by: Priyanka Jain
Signed-off-by: Santan Kumar
--
The QorIQ LS2081A SoC has eight 64-bit ARM v8 Cortex A-72 CPUs and
is built on layerscape architecture.
It is 40-pin derivative of LS2084A (non-AIOP personality of LS2088A).
So feature-wise it is same as LS2084A.
LS2081A has one more similar personality which
has four CPUs: LS2041A
Signed-off-by
Set ethernet mac address in late init for Tinker Board,
prevents getting a random mac address each boot.
Read mac address from eeprom, first 6 bytes from m24c08@50.
Same as /etc/init.d/rockchip.sh on Tinker OS.
Signed-off-by: Jonas Karlman
---
Changes in v3:
- Use uclass_first_device_err() to f
Signed-off-by: Jonas Karlman
---
Changes in v3:
- Add i2c_eeprom_{read,write} functions
Changes in v2: None
drivers/misc/i2c_eeprom.c | 32 ++--
include/i2c_eeprom.h | 24
2 files changed, 50 insertions(+), 6 deletions(-)
diff --git a/
Set ethernet mac address in late init for Tinker Board,
prevents getting a random mac address each boot.
Read mac address from eeprom, first 6 bytes from m24c08@50.
Same as /etc/init.d/rockchip.sh on Tinker OS.
Changes in v3:
- Add i2c_eeprom_{read,write} functions
- Use uclass_first_device_err()
21 matches
Mail list logo
