Add a simple function to simplify the task of accepting both full path
in "/dev" and just device name as a parameter.
Signed-off-by: Andrey Smirnov
---
include/fs.h | 9 +
1 file changed, 9 insertions(+)
diff --git a/include/fs.h b/include/fs.h
index d7fa7714b..79ae404bb 100644
--- a/in
Convert the code to use shared function from fs.h
Signed-off-by: Andrey Smirnov
---
arch/arm/mach-imx/imx-bbu-internal.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/arch/arm/mach-imx/imx-bbu-internal.c
b/arch/arm/mach-imx/imx-bbu-internal.c
index 51ec8b827..a139331a6 1
Make -s option to be a bit more consistent with how it is used in
other commands by allowing PHY device to be specified by either its
name of full path in /dev. This change also allows us to leverage
autocompletion since it will work as expected for paths in /dev.
Signed-off-by: Andrey Smirnov
--
It seems like mdiobus_show() doesn't need more than read-only to
'phydevname', so constify it to allow passing const stings in.
Signed-off-by: Andrey Smirnov
---
commands/miitool.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/commands/miitool.c b/commands/miitool.c
index
Hi everyone,
This patchset is intended to make miitools's -s option a bit more
consistnet with the rest of Barebox commands. It is inspired mostly by
users's feedback and personal frustration with inability to use
autocomplete in that command.
It's nice to have, IMHO, but if we decide not to have
Select MDIO bus GPIO multiplexer to support hardware present on the
board.
Signed-off-by: Andrey Smirnov
---
arch/arm/configs/zii_vf610_dev_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/zii_vf610_dev_defconfig
b/arch/arm/configs/zii_vf610_dev_defconfig
index e2c
Calling mdiobus_detect() for a bus that serves as a parent for a MDIO
bus multiplexer would result in parent bus being populated with
devices that are present on downstream bus that multiplexer happens to
be "pointing" at that moment. To avoid that introduce 'is_multiplexed'
flag to struct mii_bus
Port Linux version driver to Barebox, to support such device found in
various revisions of ZII's VF610 development board.
Signed-off-by: Andrey Smirnov
---
drivers/net/phy/Kconfig | 10 +++
drivers/net/phy/Makefile| 1 +
drivers/net/phy/mdio-mux-gpio.c | 147 ++
Port mdio-mux.c from Linux kernel to Barebox, to support adding
dirvers that rely on that infrastructure/API.
Signed-off-by: Andrey Smirnov
---
drivers/net/phy/Kconfig| 8 +++
drivers/net/phy/Makefile | 2 +
drivers/net/phy/mdio-mux.c | 142 +
Now that vf610-zii-dev.dts, vf610-zii-dev-rev-b.dts and
vf610-zii-dev-rev-c.dts made their way from Linux to Barebox, convert
all relevant code to make use of them.
Signed-off-by: Andrey Smirnov
---
arch/arm/dts/vf610-zii-cfu1-rev-a.dts | 3 +-
arch/arm/dts/vf610-zii-dev-rev-b.dts | 3
Hi everyone,
This is the second version of my original, with few modifications and
fixes.
Changes since [v1]:
- Addressed smalle issues pointed out by Sascha (leftover comment,
bad identation)
- Added patch enabling MDIO GPIO mux driver for ZII VF610 boards
since the are the HW this pat
Port of_mdio_find_bus() from Linux kernel. This function is used in
MDIO multiplexor infrastructure added in following commit.
Signed-off-by: Andrey Smirnov
---
drivers/net/phy/mdio_bus.c | 27 +++
include/linux/phy.h| 2 ++
2 files changed, 29 insertions(+)
dif
On Fri, Dec 1, 2017 at 3:12 AM, Sascha Hauer wrote:
> On Tue, Nov 28, 2017 at 08:55:04PM -0800, Andrey Smirnov wrote:
>> Port mdio-mux.c from Linux kernel to Barebox, to support adding
>> dirvers that rely on that infrastructure/API.
>>
>> Signed-off-by: Andrey Smirnov
>> ---
>> drivers/net/phy/
Hi Robert
Did lookup the Boot ROM error codes:
0x8050100B Load command payload CRC failed.
0x8050800F ECC failed - data is not valid.
So, I assume in our case that it is stored a CRC of bootstream in the BCB image
(with command bcb nand0.bootstream)
The MXS Bootrom code CRC check fails since im
14 matches
Mail list logo