Hi,
Le Tue 05 Aug 25, 19:48, Paul Kocialkowski a écrit :
> From: Paul Kocialkowski
>
> Both the V3 and V3s support I2C1 on PB pins, which is often used to
> connect an AXP209 PMIC on V3 boards.
Actually this appears to be wrong. I had this patch around for a while but
I was mistak
Hi,
Thansk for the review!
Le Wed 06 Aug 25, 01:21, Andre Przywara a écrit :
> On Tue, 5 Aug 2025 19:48:23 +0200
> Paul Kocialkowski wrote:
>
> Hi,
>
> > From: Paul Kocialkowski
> >
> > The V3/S3 has extra pins for UART1 on PG pins, which are not presen
Hi,
Le Wed 06 Aug 25, 01:21, Andre Przywara a écrit :
> On Tue, 5 Aug 2025 19:48:18 +0200
> Paul Kocialkowski wrote:
>
> Hi Paul,
>
> > From: Paul Kocialkowski
> >
> > There are a few notable differences that are relevant to U-Boot, including:
> > -
general, which were not
explored at all in the commit. This may break many boards that do rely on that
PHY reset, in various scenarios and for various reasons.
I think it should be reverted as soon as possible to restore previous behavior.
All the best,
Paul
--
Paul Kocialkowski,
Independent contractor - sys-base - https://www.sys-base.io/
Free software developer - https://www.paulk.fr/
Expert in multimedia, graphics and embedded hardware support with Linux.
signature.asc
Description: PGP signature
From: Paul Kocialkowski
A device-tree property is already defined to indicate that the internal
PHY should be used with active-low leds, which corresponds to a
specific bit in the dedicated syscon register.
Add support for setting this bit when the property is present.
Signed-off-by: Paul
From: Paul Kocialkowski
We know about all the relevant fields in the syscon register so there
is no reason to read it first and modify it.
Build the register from scratch instead, with all relevant fields set.
Signed-off-by: Paul Kocialkowski
---
drivers/net/sun8i_emac.c | 32
From: Paul Kocialkowski
This adds a U-Boot config and device-tree build for the Lichee Pi Zero
with Dock. Compared to the Lichee Pi Zero, it has an ethernet port
(with internal PHY) so the EMAC driver and network support are enabled.
Signed-off-by: Paul Kocialkowski
---
configs
From: Paul Kocialkowski
The pinecube has an ethernet connector which uses the EMAC and internal
PHY of the chip. Enable it in the config.
Reviewed-by: Andre Przywara
Signed-off-by: Paul Kocialkowski
---
configs/pinecube_defconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
From: Paul Kocialkowski
The V3/S3 has extra pins for UART1 on PG pins, which are not present
on the V3s. Add support for them and make them the default UART1 pins
on the V3. Note that PE pins are also available for UART1 but almost
never used since they also provide the CSI I2C lines.
Signed
From: Paul Kocialkowski
Both the V3 and V3s support I2C1 on PB pins, which is often used to
connect an AXP209 PMIC on V3 boards.
Signed-off-by: Paul Kocialkowski
---
board/sunxi/board.c | 4
include/sunxi_gpio.h | 1 +
2 files changed, 5 insertions(+)
diff --git a/board/sunxi/board.c b
From: Paul Kocialkowski
There is nothing special for u-boot in the V3/V3s device-tree files,
they are just copies of the upstream ones.
Remove the copies and switch to OF_UPSTREAM for supported boards.
Signed-off-by: Paul Kocialkowski
---
arch/arm/dts/Makefile | 5
From: Paul Kocialkowski
The default voltages used by V3/S3 boards differs from the usual AXP209
default that are used on older chips.
Correct the default voltages based on the Allwinner reference design
schematics, which match boards found in the wild such as the Pinecube.
Update the affected
From: Paul Kocialkowski
While most sun8i platforms have secure SRAM available, some do not.
This is the case for the R40/V40 (based on sun7i) and V3/V3s.
Add the exceptions to the Kconfig default and clean up its align.
Update affected defconfigs to reflect the new default.
Signed-off-by: Paul
From: Paul Kocialkowski
There are a few notable differences that are relevant to U-Boot, including:
- different DRAM configuration due to the co-packaged DRAM chip in V3s;
- use of an external PMIC (typically an AXP209) on V3;
- extra pins available on V3, e.g. for UART1.
Move the exiting V3s
From: Paul Kocialkowski
The V3s (using co-packaged DRAM) runs at 360 MHz, which is specified in
the common platform Kconfig file. However the value for MACH_SUN8I will
be picked up instead due to ordering.
Re-order the defaults to have MACH_SUN8I_V3S before MACH_SUN8I and let
it select the
Changes since v1:
- Added a common MACH_SUN8I_V3_V3S option;
- Disabled secure RAM;
- Switched to OF_UPSTREAM;
- Added some pinmux support.
- Removed internal PHY default value;
Paul Kocialkowski (11):
sunxi: Kconfig: Fix default order for V3s DRAM clock
sunxi: Split V3 and V3s support with a
Hi,
Le Mon 02 Jun 25, 01:40, Andre Przywara a écrit :
> On Sun, 1 Jun 2025 17:39:43 +0200
> Paul Kocialkowski wrote:
>
> Hi,
>
> > A device-tree property is already defined to indicate that the internal
> > PHY should be used with active-low leds, which correspon
Hi Andre,
Le Mon 02 Jun 25, 01:40, Andre Przywara a écrit :
> On Sun, 1 Jun 2025 17:39:39 +0200
> Paul Kocialkowski wrote:
>
> Hi Paul,
>
> > This adds a U-Boot config and device-tree build for the Lichee Pi Zero
> > with Dock. Compared to the Lichee Pi Zero, it has
The pinecube has an ethernet connector which uses the EMAC and internal
PHY of the chip. Enable it in the config.
Signed-off-by: Paul Kocialkowski
---
configs/pinecube_defconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configs/pinecube_defconfig b/configs
A device-tree property is already defined to indicate that the internal
PHY should be used with active-low leds, which corresponds to a
specific bit in the dedicated syscon register.
Add support for setting this bit when the property is present.
Signed-off-by: Paul Kocialkowski
---
drivers/net
The default voltages used by V3/S3 boards differs from the usual AXP209
default that are used on older chips.
Correct the default voltages based on the Allwinner reference design
schematics, which match boards found in the wild such as the Pinecube.
Signed-off-by: Paul Kocialkowski
---
configs
relevant
V3s-specific choices with it.
Also update the pinecube config to reflect the updated config options.
Signed-off-by: Paul Kocialkowski
---
arch/arm/dts/Makefile | 5 ++--
arch/arm/include/asm/arch-sunxi/cpu_sun4i.h | 1 +
arch/arm/mach-sunxi/Kconfig
This adds a U-Boot config and device-tree build for the Lichee Pi Zero
with Dock. Compared to the Lichee Pi Zero, it has an ethernet port
(with internal PHY) so the EMAC driver and network support are enabled.
Signed-off-by: Paul Kocialkowski
---
arch/arm/dts/Makefile| 3
the LicheePi Zero Dock
defconfig to remove the value, which is now correctly selected.
Signed-off-by: Paul Kocialkowski
---
arch/arm/mach-sunxi/Kconfig | 2 +-
configs/LicheePi_Zero_defconfig | 1 -
2 files changed, 1 insertion(+), 2 deletions(-)
diff --git a/arch/arm/mach-sunxi/Kconfig b
Paul Kocialkowski (6):
sunxi: Kconfig: Fix default order for V3s DRAM clock
sunxi: Add support for the Lichee Pi Zero with Dock
sunxi: Split V3/S3 support from V3s
sunxi: pinecube: Enable EMAC and network support
power: axp: Fixup default voltages for V3/S3
net: sun8i-emac: Add support
Hi Chen-Yu,
Le Wed 05 Feb 25, 01:23, Chen-Yu Tsai a écrit :
> From: Chen-Yu Tsai
>
> The IO domain driver controls the I/O voltage for various pins,
> MMC included.
>
> Enable it by default for all supported Rockchip SoCs.
Thanks for the cleanup!
Reviewed-by: Paul Kocialkow
BC_SIN << GRF_GPIO4C3_SEL_SHIFT);
> + GRF_UART2DBGC_SIN << GRF_GPIO4C3_SEL_SHIFT);
> rk_clrsetreg(&grf->gpio4c_iomux,
>GRF_GPIO4C4_SEL_MASK,
>GRF_UART2DBGC_SOUT << GRF_GPIO4C4_SEL_SHIFT);
> --
> 2.39.5
>
--
Paul Kocialkowski,
Independent contractor - sys-base - https://www.sys-base.io/
Free software developer - https://www.paulk.fr/
Expert in multimedia, graphics and embedded hardware support with Linux.
signature.asc
Description: PGP signature
> U-Boot TPL 2025.01-rc1-00165-gd79216ca9878-dirty (Nov 05 2024 - 15:31:45)
> """
>
> possibly hinting at an issue within the SPL when loading the fitImage
> from MMC2 instead of the normal course of events (a system reset).
>
> Signed-off-by: Quentin Schulz
T
n see the TPL banner twice ?
> >
> >
> > PS: We are able to merge to master instead of next before next branch is
> > open, because we still have
> >
> > enough time to debug before next release.
> >
>
> My understanding is that once -rc1 is out, w
Hi,
Le Tue 05 Nov 24, 16:36, Quentin Schulz a écrit :
> From: Quentin Schulz
>
> A later commit will make use of the pinctrl driver in TPL so let's add
> the ability to build the Rockchip pinctrl driver in TPL.
>
> Signed-off-by: Quentin Schulz
Reviewed-by: Paul Ko
Hi,
Le Tue 05 Nov 24, 16:38, Quentin Schulz a écrit :
> Hi Paul,
>
> On 9/26/24 8:31 PM, Paul Kocialkowski wrote:
> > From: Paul Kocialkowski
> >
> > The reset mechanism used by Linux to reset the SoC is known to only
> > partially reset the log
; +# if !defined(CONFIG_TPL_BUILD)
> void __weak led_setup(void)
> {
> }
> @@ -228,4 +229,10 @@ void spl_board_init(void)
>
> rk3399_force_power_on_reset();
> }
> -#endif
> +# else // !defined(CONFIG_TPL_BUILD)
> +void tpl_board_init(void)
> +{
> + rk3399_force_power_on_reset();
> +}
> +# endif // !defined(CONFIG_TPL_BUILD)
> +#endif // defined(CONFIG_XPL_BUILD)
>
> --
> 2.47.0
>
--
Paul Kocialkowski,
Free software developer - https://www.paulk.fr/
Independent contractor - sys-base - https://www.sys-base.io/
Contributor to fully free software support for selected hardware.
signature.asc
Description: PGP signature
fig | 3 ++
> drivers/pinctrl/Kconfig| 8 +
> drivers/pinctrl/rockchip/Kconfig | 7
> 5 files changed, 56 insertions(+), 26 deletions(-)
> ---
> base-commit: 56accc56b9aab87ef4809ccc588e1257969cd271
> change-id: 20241105-rk3399-sysres
ff-by: Quentin Schulz
Reviewed-by: Paul Kocialkowski
Cheers,
Paul
> ---
> arch/arm/mach-rockchip/tpl.c | 6 ++
> 1 file changed, 6 insertions(+)
>
> diff --git a/arch/arm/mach-rockchip/tpl.c b/arch/arm/mach-rockchip/tpl.c
> index
> bbb9329e725af79ea4c4049aa7890a4a143e7df5
pinctrl).
>
> Signed-off-by: Quentin Schulz
Reviewed-by: Paul Kocialkowski
Cheers,
Paul
> ---
> configs/puma-rk3399_defconfig | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/configs/puma-rk3399_defconfig b/configs/puma-rk3399_def
; U-Boot SPL 2025.01-rc1-00165-gd79216ca9878-dirty (Nov 05 2024 - 15:31:45
> +0100)
> Trying to boot from MMC2
>
> U-Boot TPL 2025.01-rc1-00165-gd79216ca9878-dirty (Nov 05 2024 - 15:31:45)
> """
>
> possibly hinting at an issue within the SPL when loading the fitI
he rest of the logic.
>
> Signed-off-by: Quentin Schulz
Reviewed-by: Paul Kocialkowski
Cheers,
Paul
> ---
> arch/arm/mach-rockchip/rk3399/rk3399.c | 43
> +-
> 1 file changed, 21 insertions(+), 22 deletions(-)
>
> diff --git a/arch/arm/mach
Hi,
Le Mon 30 Sep 24, 12:52, Simon Glass a écrit :
> On Mon, 30 Sept 2024 at 03:03, Peter Robinson wrote:
> > On Thu, 26 Sept 2024 at 19:32, Paul Kocialkowski wrote:
> > > The boot timing and reporting (bootstage) infrastructure is useful for
> > > performance
Ah yes I think the Firefly-RK3399 and ROC-RK3399-PC are two distinct designs.
> https://en.t-firefly.com/doc/download/page/id/51.html does route GPIO1_A6 to
> the OTP_OUT_H signal..
> https://en.t-firefly.com/doc/download/page/id/78.html
> https://en.t-firefly.com/doc/download/page/
ouble-checked the schematics (ROC_3399_PC), looking at signal OTP_OUT_H
which is definitely connected to GPIO1_A6 (P26).
Also it clearly resets the board when toggled and solves the MMC reset issue
I was having on this exact board, so I'm rather confident that it's the right
one to use :)
Hi,
Le Thu 26 Sep 24, 23:04, Dragan Simic a écrit :
> On 2024-09-26 22:51, Paul Kocialkowski wrote:
> > Le Thu 26 Sep 24, 22:17, Dragan Simic a écrit :
> > > On 2024-09-26 20:31, Paul Kocialkowski wrote:
> > > > From: Paul Kocialkowski
> > > >
> &
On Thu 26 Sep 24, 23:24, Dragan Simic wrote:
> On 2024-09-26 23:16, Paul Kocialkowski wrote:
> > Le Thu 26 Sep 24, 23:04, Dragan Simic a écrit :
> > > On 2024-09-26 22:51, Paul Kocialkowski wrote:
> > > > Le Thu 26 Sep 24, 22:17, Dragan Simic a écrit :
>
Hi,
Le Thu 26 Sep 24, 22:17, Dragan Simic a écrit :
> On 2024-09-26 20:31, Paul Kocialkowski wrote:
> > From: Paul Kocialkowski
> >
> > Printing debug details about DRAM is not useful in regular use and
> > adds visual pollution to the log. Disable it by default.
&
From: Paul Kocialkowski
The boot timing and reporting (bootstage) infrastructure is useful for
performance analysis and debug but adds overhead and console noise when
using the device normally. Remove it from the device config.
Signed-off-by: Paul Kocialkowski
---
configs/rockpro64
From: Paul Kocialkowski
The reset mechanism used by Linux to reset the SoC is known to only
partially reset the logic. A mechanism is implemented in
rk3399_force_power_on_reset to use a GPIO connected to the PMIC's
over-temperature (OTP) reset pin, which fully resets all logic.
Hoo
From: Paul Kocialkowski
Printing debug details about DRAM is not useful in regular use and
adds visual pollution to the log. Disable it by default.
Signed-off-by: Paul Kocialkowski
---
configs/anbernic-rgxx3-rk3566_defconfig | 1 -
configs/neu2-io-rv1126_defconfig | 1 -
configs
From: Paul Kocialkowski
The reset mechanism used by Linux to reset the SoC is known to only
partially reset the logic. A mechanism is implemented in
rk3399_force_power_on_reset to use a GPIO connected to the PMIC's
over-temperature (OTP) reset pin, which fully resets all logic.
Hoo
patch just
a few days ago, with additional cleanups!
See
https://patchwork.ozlabs.org/project/uboot/patch/20240729204439.429900-3-pa...@sys-base.io/
Cheers,
Paul
> Signed-off-by: Anatolij Gustschin
> ---
> Cc: Paul Kocialkowski
> Cc: Tom Rini
> ---
> arch/arm/mach-omap2/
From: Paul Kocialkowski
This converts the sniper board (LG P970) to device-tree control
and DM I2C, both for SPL and U-Boot.
Note that we lose the call to board_mmc_power_init to enable power
for MMC2. This is now expected to take place through proper
regulators, which are not yet available
rid of
am33xx_spl_board_init.
Rename the function in board files and enable the related config
option for concerned boards.
Signed-off-by: Paul Kocialkowski
---
arch/arm/include/asm/arch-am33xx/sys_proto.h | 1 -
arch/arm/mach-omap2/am33xx/board.c | 8
arch/arm/mach-omap2/boot
Both spl_board_init and spl_soc_init are available as ways to run
specific code in the SPL's board_init_r. Use the former for init
code that is specific to the SoC and leave spl_board_init available
for boards to use.
Signed-off-by: Paul Kocialkowski
---
arch/arm/Kconfig
From: Paul Kocialkowski
Remove custom config options that are not particularly necessary.
Align them with OMAP3 defaults used on other boards (especially for
memory locations).
Also enable Thumb build to reduce the SPL size and remove the custom
prompt text.
This makes the config a lot more
From: Paul Kocialkowski
The common EMIF init code used for DRA7xx does not explicitly fill
the gd->bd->bi_dram entries (like OMAP3 does), so there is no reason
to set an explicit number of DRAM banks which doesn't correspond to
anything in particular.
Remove the CONFIG_NR_DRAM_BANKS
From: Paul Kocialkowski
The number of DRAM banks was defined to the same value in each OMAP3
board defconfig, which is expected and hardcoded in the code. Move the
common definition to the Kconfig option declaration instead.
Signed-off-by: Paul Kocialkowski
---
Kconfig
From: Paul Kocialkowski
The maximum SPL size was defined to the same value in each OMAP3
board defconfig. Move the common definition to the Kconfig option
declaration instead.
Signed-off-by: Paul Kocialkowski
---
common/spl/Kconfig | 1 +
configs/am3517_evm_defconfig
From: Paul Kocialkowski
The maximum U-Boot size was defined to the same value in each OMAP3
board defconfig. Move the common definition to the Kconfig option
declaration instead.
Signed-off-by: Paul Kocialkowski
---
Kconfig | 1 +
configs/am3517_evm_defconfig
From: Paul Kocialkowski
The init stack pointer was defined to the same value in each DRA7xx
board defconfig. Move the common definition to the Kconfig option
declaration instead.
Signed-off-by: Paul Kocialkowski
---
Kconfig | 3 ++-
configs/am57xx_evm_defconfig
From: Paul Kocialkowski
The DRA7xx EVM board use a slightly different init stack pointer
address compared to the AM57xx EVM board, for no particular reason.
Align the address with the AM57xx EVM board (which matches the usual
offset to the end of SRAM used by other OMAP devices) prior to
From: Paul Kocialkowski
The init stack pointer was defined to the same value in each AM43xx
board defconfig. Move the common definition to the Kconfig option
declaration instead.
Signed-off-by: Paul Kocialkowski
---
Kconfig | 3 ++-
configs
From: Paul Kocialkowski
The init stack pointer was defined to the same value in each AM33xx
board defconfig. Move the common definition to the Kconfig option
declaration instead.
Signed-off-by: Paul Kocialkowski
---
Kconfig | 3 ++-
configs
From: Paul Kocialkowski
The AM33xx chiliboard and guardian boards use a slightly different
init stack pointer address compared to other AM33xx boards, for no
particular reason.
Align the address with other AM33xx boards prior to removing it as a
per-board option in a later commit.
Signed-off
From: Paul Kocialkowski
The init stack pointer was defined to the same value in each OMAP3
board defconfig. Move the common definition to the Kconfig option
declaration instead.
Signed-off-by: Paul Kocialkowski
---
Kconfig | 2 ++
configs/am3517_evm_defconfig
From: Paul Kocialkowski
The SPL text base was defined to the same value in each OMAP3 board
defconfig. Move the common definition to the Kconfig option
declaration instead.
Signed-off-by: Paul Kocialkowski
---
common/spl/Kconfig | 1 +
configs/am3517_evm_defconfig
Here is a bunch of configuration cleanups for OMAP boards, mostly
unifying and moving common configuration from board-specific defconfigs
to Kconfig definitions.
There's also a cleanup of the sniper (LG Optimus Black) defconfig,
prior to migrating it to DM/DT in a future follow-up series.
Linux kernel
images.
Signed-off-by: Paul Kocialkowski
---
include/configs/px30_common.h | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/include/configs/px30_common.h b/include/configs/px30_common.h
index 6fbd2679f099..13ed9011764b 100644
--- a/include/configs/px30_common.h
Hi Andre,
Le Wed 26 May 21, 01:57, Andre Przywara a écrit :
> From: Paul Kocialkowski
>
> Recent Allwinner platforms (starting with the H3) only use the MUSB
> controller for peripheral mode and use HCI for host mode. As a result,
> extra steps need to be taken to properly route
Hi Heiko,
On Tue 03 Dec 19, 20:50, Heiko Stuebner wrote:
> Hi Paul,
>
> On 03.12.19 16:46, Paul Kocialkowski wrote:
> > The serial# environment variable is a read-only special variable, that
> > can only be set once. As a result, if the environment was saved to a
> >
whether the variable is already set before.
Signed-off-by: Paul Kocialkowski
---
arch/arm/mach-rockchip/misc.c | 14 +-
1 file changed, 9 insertions(+), 5 deletions(-)
diff --git a/arch/arm/mach-rockchip/misc.c b/arch/arm/mach-rockchip/misc.c
index bed4317f7ece..a0c6a1c0b266 100644
t the boot process.
Return the success return code if the variable is already set instead.
Signed-off-by: Paul Kocialkowski
---
arch/arm/mach-rockchip/misc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/mach-rockchip/misc.c b/arch/arm/mach-rockchip/misc.c
note that the pinmux default in the dts is to use
the M1 pins while the Kconfig option takes M0 as a default.
Signed-off-by: Paul Kocialkowski
Reviewed-by: Kever Yang
Reviewed-by: Heiko Stuebner
---
arch/arm/include/asm/arch-rockchip/cru_px30.h | 19 +
arch/arm/mach-rockchip/px30/px30.c
According to the PX30 TRM, the iomux registers come first, before the pull
and strength control registers.
Signed-off-by: Paul Kocialkowski
Reviewed-by: Kever Yang
Reviewed-by: Heiko Stuebner
---
arch/arm/include/asm/arch-rockchip/grf_px30.h | 16
1 file changed, 8 insertions
UART3 also has two sets of pins that can be selected.
Rename the config option to a common name, to allow it to be used for both
UART2 and UART3.
Signed-off-by: Paul Kocialkowski
---
arch/arm/mach-rockchip/px30/Kconfig | 6 +++---
arch/arm/mach-rockchip/px30/px30.c | 4 ++--
2 files changed
Hi Heiko,
On Thu 28 Nov 19, 10:44, Heiko Stuebner wrote:
> On 27.11.19 11:12, Paul Kocialkowski wrote:
> > Some generic PX30 SoMs found in the wild use UART3 as their debug output
> > instead of UART2 (used for MMC) and UART5.
> >
> > Make it possible to use UART3 as e
between the two is introduced like it's done
for UART2.
Future users should also note that the pinmux default in the dts is to use
the M1 pins while the Kconfig option takes M0 as a default.
Signed-off-by: Paul Kocialkowski
---
arch/arm/include/asm/arch-rockchip/cru_px30.h | 19 +
arc
According to the PX30 TRM, the iomux registers come first, before the pull
and strength control registers.
Signed-off-by: Paul Kocialkowski
---
arch/arm/include/asm/arch-rockchip/grf_px30.h | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/arch/arm/include/asm
Hi,
On Mon 15 Jul 19, 12:55, Jagan Teki wrote:
> On Mon, May 27, 2019 at 5:21 AM André Przywara wrote:
> >
> > On 17/04/2019 12:28, Jagan Teki wrote:
> > > On Mon, Apr 15, 2019 at 1:52 PM Paul Kocialkowski
> > > wrote:
> >
> > Hi,
> >
> >
Hi,
On Mon 27 May 19, 00:50, André Przywara wrote:
> On 17/04/2019 12:28, Jagan Teki wrote:
> > On Mon, Apr 15, 2019 at 1:52 PM Paul Kocialkowski
> > wrote:
>
> Hi,
>
> >> Le vendredi 12 avril 2019 à 14:49 +0530, Jagan Teki a écrit :
> >>> On T
gs and throw shit at us for taking political decisions. That's too
bad, but there is only so much we can do about that. And rest asured
that people (including myself) can also throw shit at the project for
maintaining a weak status-quo and not contribute to mo
Hi,
On Fri, 2019-06-21 at 13:34 +0200, Heiko Stuebner wrote:
> Hi,
>
> Am Donnerstag, 20. Juni 2019, 05:24:32 CEST schrieb Kever Yang:
> > On 06/20/2019 12:54 AM, Paul Kocialkowski wrote:
> > > Le mercredi 19 juin 2019 à 09:42 +0800, Kever Yang a écrit :
> > &g
Hi Kever,
Le mercredi 19 juin 2019 à 09:42 +0800, Kever Yang a écrit :
> Hi Paul,
>
>
> On 06/19/2019 12:12 AM, Mark Kettenis wrote:
> > > From: Paul Kocialkowski
> > > Date: Tue, 18 Jun 2019 14:47:33 +0200
> > >
> > > Hi Kever,
> > >
Hi Kever,
On Tue, 2019-06-18 at 18:08 +0800, Kever Yang wrote:
> Hi Paul,
>
>
> On 06/18/2019 05:03 PM, Paul Kocialkowski wrote:
> > Hi,
> >
> > On Tue, 2019-06-18 at 14:27 +0530, Jagan Teki wrote:
> > > On Tue, Jun 18, 2019 at 1:55 PM Pau
Hi,
On Tue, 2019-06-18 at 14:27 +0530, Jagan Teki wrote:
> On Tue, Jun 18, 2019 at 1:55 PM Paul Kocialkowski
> wrote:
> > Hi,
> >
> > On Mon, 2019-06-17 at 15:24 +0800, xieqin...@gmail.com wrote:
> > > From: Nick Xie
> >
> > Was this tested wit
t; --- /dev/null
> +++ b/configs/khadas-edge-captain-rk3399_defconfig
> @@ -0,0 +1,67 @@
> +CONFIG_ARM=y
> +CONFIG_ARCH_ROCKCHIP=y
> +CONFIG_SYS_TEXT_BASE=0x0020
> +CONFIG_SPL_LIBCOMMON_SUPPORT=y
> +CONFIG_SPL_LIBGENERIC_SUPPORT=y
> +CONFIG_SYS_MALLOC_F_LEN=0x4000
> +CONFIG_ROCK
; + pwrbtn: pwrbtn {
> > > + rockchip,pins = <0 RK_PA5 RK_FUNC_GPIO &pcfg_pull_up>;
> > > + };
> > > + };
> > > +
> > > + fusb302x {
> > > + fusb0_int: fusb0-in
Hi,
On Mon, 2019-05-27 at 00:50 +0100, André Przywara wrote:
> On 17/04/2019 12:28, Jagan Teki wrote:
> > On Mon, Apr 15, 2019 at 1:52 PM Paul Kocialkowski
> > wrote:
>
> Hi,
>
> > > Le vendredi 12 avril 2019 à 14:49 +0530, Jagan Teki a écrit :
> > &
Hi,
On Thu, 2019-05-09 at 14:40 +0200, Philipp Tomsich wrote:
> Jagan,
>
> > On 09.05.2019, at 14:36, Jagan Teki wrote:
> >
> > On Thu, May 9, 2019 at 6:01 PM Paul Kocialkowski
> > wrote:
> > > Hi,
> > >
> > > On Thu, 201
On Thu, 2019-05-09 at 18:06 +0530, Jagan Teki wrote:
> On Thu, May 9, 2019 at 6:01 PM Paul Kocialkowski
> wrote:
> > Hi,
> >
> > On Thu, 2019-05-09 at 16:15 +0530, Jagan Teki wrote:
> > > Hi Paul,
> > >
> > > On Thu, May 9, 2019 at
Hi,
On Thu, 2019-05-09 at 16:15 +0530, Jagan Teki wrote:
> Hi Paul,
>
> On Thu, May 9, 2019 at 12:38 PM Paul Kocialkowski
> wrote:
> > Hi,
> >
> > On Wed, 2019-05-08 at 11:11 +0530, Jagan Teki wrote:
> > > (Sorry for the noice, I have missed to send two p
ch/arm/dts/rk3399-rock-pi-4-u-boot.dtsi
> create mode 100644 arch/arm/dts/rk3399-rock-pi-4.dts
> create mode 100644 arch/arm/dts/rk3399-rockpro64-u-boot.dtsi
> create mode 100644 arch/arm/dts/rk3399-rockpro64.dts
> create mode 100644 configs/nanopc-t4-rk3399_defconfig
> create m
t; +CONFIG_USB_XHCI_DWC3=y
> +CONFIG_USB_EHCI_HCD=y
> +CONFIG_USB_EHCI_GENERIC=y
> +CONFIG_USB_HOST_ETHER=y
> +CONFIG_USB_ETHER_ASIX=y
> +CONFIG_USB_ETHER_ASIX88179=y
> +CONFIG_USB_ETHER_MCS7830=y
> +CONFIG_USB_ETHER_RTL8152=y
> +CONFIG_USB_ETHER_SMSC95XX=y
> +CONFIG_USE_TINY_PRINTF=y
> +CONFIG_ERRNO_STR=y
--
Paul Kocialkowski, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
dtsi
> - sdmmc, u-boot,dm-pre-reloc
> - spi1, u-boot,dm-pre-reloc
For the whole series:
Reviewed-by: Paul Kocialkowski
Cheers,
Paul
> Changes for v6:
> - spilt the existing patch[1] into multiple patches
> and send as a separate series.
>
> [1] https://patchwork.ozlab
Hi,
Le vendredi 26 avril 2019 à 23:12 +0530, Jagan Teki a écrit :
> On Fri, Apr 26, 2019 at 11:07 PM Paul Kocialkowski
> wrote:
> > Hi,
> >
> > Le vendredi 26 avril 2019 à 22:51 +0530, Jagan Teki a écrit :
> > > On Fri, Apr 26, 2019 at 10:38 PM Paul Koci
Hi,
Please split off this two commits to another dedicated series, with the
patch introducing rk3399-u-boot.dtsi. You can then decide to introduce
rk3399 boards support (in a third series) before or after.
Cheers,
Paul
Le vendredi 26 avril 2019 à 19:04 +0530, Jagan Teki a écrit :
> We have a ba
Le vendredi 26 avril 2019 à 23:22 +0530, Jagan Teki a écrit :
> Hi Tom and Simon,
>
> On Fri, Apr 26, 2019 at 7:04 PM Jagan Teki wrote:
> > This series will create single bootable image 'u-boot-rockchip-with-spl.bin'
> > for rk3399 platform with single make command instead of building u-boot
> >
Hi,
Le vendredi 26 avril 2019 à 22:51 +0530, Jagan Teki a écrit :
> On Fri, Apr 26, 2019 at 10:38 PM Paul Kocialkowski
> wrote:
> > Hi,
> >
> > Le vendredi 26 avril 2019 à 22:23 +0530, Jagan Teki a écrit :
> > > > > > > First series, I ge
Hi,
Le vendredi 26 avril 2019 à 22:23 +0530, Jagan Teki a écrit :
> > > > > First series, I get introduced rk3399-u-boot.dtsi, and only the new
> > > > > boards are using this file and next series rest of the boards are
> > > > > using which indeed a valid step. what is inconsistent here, I don't
Hi,
Le vendredi 26 avril 2019 à 21:46 +0530, Jagan Teki a écrit :
> On Fri, Apr 26, 2019 at 9:38 PM Paul Kocialkowski
> wrote:
> > Hi,
> >
> > Le vendredi 26 avril 2019 à 21:18 +0530, Jagan Teki a écrit :
> > > On Fri, Apr 26, 2019 at 9:08 PM Paul Koci
Hi,
Le vendredi 26 avril 2019 à 21:18 +0530, Jagan Teki a écrit :
> On Fri, Apr 26, 2019 at 9:08 PM Paul Kocialkowski
> wrote:
> > Hi,
> >
> > Le vendredi 26 avril 2019 à 20:48 +0530, Jagan Teki a écrit :
> > > On Fri, Apr 26, 2019 at 8:42 PM Paul Koci
Hi,
Le vendredi 26 avril 2019 à 20:48 +0530, Jagan Teki a écrit :
> On Fri, Apr 26, 2019 at 8:42 PM Paul Kocialkowski
> wrote:
> > Hi,
> >
> > On Fri, 2019-04-26 at 20:31 +0530, Jagan Teki wrote:
> > > On Fri, Apr 26, 2019 at 8:24 PM Paul Koci
Hi,
On Fri, 2019-04-26 at 20:31 +0530, Jagan Teki wrote:
> On Fri, Apr 26, 2019 at 8:24 PM Paul Kocialkowski
> wrote:
> > Hi,
> >
> > On Fri, 2019-04-26 at 20:15 +0530, Jagan Teki wrote:
> > > On Fri, Apr 26, 2019 at 8:04 PM Paul Kocialkowski
> > >
1 - 100 of 639 matches
Mail list logo
