Hi Jonas,
On Sun, 7 Jan 2024 at 17:35, Jonas Karlman wrote:
>
> Hi Hugh,
>
> On 2023-12-26 17:43, Hugh Cole-Baker wrote:
> > An uncompressed 6.7.0-rc1 Linux kernel Image built with the arm64
> > defconfig is about 40MB. This does not fit in to the space betwee
and its decompression buffer, then devicetree,
overlay and ramdisk at the end.
Signed-off-by: Hugh Cole-Baker
---
Changes from v1:
Reorder things to have to have 128MiB for kernel and decompression space,
then devicetree, overlays and ramdisk.
Update kernel_comp_size to 128MiB.
include/configs
to allow 96MB for uncompressing kernels.
Signed-off-by: Hugh Cole-Baker
Cc: Simon Glass
Cc: Philipp Tomsich
Cc: Kever Yang
Cc: Jonas Karlman
---
include/configs/rk3568_common.h | 4 ++--
include/configs/rk3588_common.h | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git
SPI flash on this machine is located on bus 1, default to using bus 1
for SPI flash and stop aliasing it to bus 0. Formerly the alias spi1
pointed to , use an alias spi5 for this instead.
Signed-off-by: Hugh Cole-Baker
Suggested-by: Kever Yang
---
Changes in v2:
New patch.
arch/arm/dts
SPI flash on this board is located on bus 1, default to using bus 1 for
SPI flash on both rk3399-roc-pc and -mezzanine, and stop aliasing it to
bus 0.
Signed-off-by: Hugh Cole-Baker
Suggested-by: Simon Glass
Fixes: c4cea2bb ("rockchip: Enable building a SPI ROM image on bob")
---
(
SPI flash on this machine is located on bus 1, default to using bus 1
for SPI flash and stop aliasing it to bus 0.
Signed-off-by: Hugh Cole-Baker
Suggested-by: Simon Glass
Fixes: c4cea2bb ("rockchip: Enable building a SPI ROM image on bob")
---
(no changes since v1)
arch/arm/
s who have the
affected boards would be welcome.
Changes in v2:
Also make this change to the Puma-Haikou board as suggested by Kever.
Hugh Cole-Baker (3):
rockchip: pinebook-pro: default to SPI bus 1 for SPI-flash
rockchip: rk3399-roc-pc: default to SPI bus 1 for SPI-flash
rockchip: puma-haiko
SPI flash on this machine is located on bus 1, default to using bus 1
for SPI flash and stop aliasing it to bus 0.
Signed-off-by: Hugh Cole-Baker
Suggested-by: Simon Glass
Fixes: c4cea2bb ("rockchip: Enable building a SPI ROM image on bob")
---
arch/arm/dts/rk3399-pinebook-pro-u-boo
SPI flash on this board is located on bus 1, default to using bus 1 for
SPI flash on both rk3399-roc-pc and -mezzanine, and stop aliasing it to
bus 0.
Signed-off-by: Hugh Cole-Baker
Suggested-by: Simon Glass
Fixes: c4cea2bb ("rockchip: Enable building a SPI ROM image on bob")
---
I
haven't touched its configuration as it seems to have a more complex
setup where spi1 is already an alias that points to I don't
have one of these boards to test with, but I suspect it wasn't affected
by the addition of the spi1 alias in rk3399-u-boot.dtsi.
Hugh Cole-Baker (2):
rockchip: pi
Hi,
> On 10 Nov 2020, at 07:34, Kever Yang wrote:
>
> Hi Peter,
>
> On 2020/11/9 上午7:02, Peter Robinson wrote:
>> Move the bits that are device specific to the -u-boot.dtsi as the
>> bits may be different on other devices and hence breaks SPI on
>> those devices such as the Pinebook Pro.
>>
Hi Simon,
> On 3 Nov 2020, at 15:11, Simon Glass wrote:
>
> Hi Hugh,
>
> On Wed, 14 Oct 2020 at 12:37, Hugh Cole-Baker wrote:
>>
>> Hello,
>>> On 11 Oct 2020, at 16:39, Emmanuel Vadot wrote:
>>>
>>>
>>> Hi Simon,
>
this board.
Remove the spi0 alias, set the default bus for SPI flash to 1, and
enable support for numbered aliases in SPL so that it uses the same bus
numbering as U-Boot proper. This fixes booting from U-Boot in SPI flash
on the rockpro64 board.
Signed-off-by: Hugh Cole-Baker
Suggested-by: Simon Gl
Hello,
> On 11 Oct 2020, at 16:39, Emmanuel Vadot wrote:
>
>
> Hi Simon,
>
> On Sun, 19 Jul 2020 13:55:58 -0600
> Simon Glass wrote:
>
>> Add a simple binman config and enable CONFIG_HAS_ROM so that U-Boot
>> produces a ROM for bob.
>>
>> Signed-off-by: Simon Glass
>> ---
>>
>> Changes in
they
know they will be using a compatible version of TF-A.
Signed-off-by: Hugh Cole-Baker
---
For some background, see this thread on the TF-A list [1].
Since the corresponding required change isn't in a tagged version of
TF-A yet, and I don't know how many RK3399 boards are normally used with
older TF-A vers
> On 24 May 2020, at 20:00, Suniel Mahesh wrote:
>
>
>
> On Sun, May 24, 2020 at 3:52 PM Hugh Cole-Baker wrote:
>
> > On 20 May 2020, at 13:08, Jagan Teki wrote:
> >
> > It seems like SPI boot on rk3399 with TPL based is unable to return
> >
> On 20 May 2020, at 13:08, Jagan Teki wrote:
>
> It seems like SPI boot on rk3399 with TPL based is unable to return
> from ROM or switching to from TPL to SPL is unsuccessful.
>
> I have verified board_init_f on spl.c and the control is not even
> reached here. On the other hand the
adc_channel_single_shot() requires the full device name e.g.
"saradc@ff10", which differs between Rockchip SoC's, but they all
share the prefix "saradc"; find the ADC device with this name prefix and
use its full name.
Signed-off-by: Hugh Cole-Baker
---
I previously
adc_channel_single_shot() requires the full device name e.g.
"saradc@ff10", which differs between Rockchip SoC's, but they all
share the prefix "saradc"; find the ADC device with this name prefix and
use its full name.
Signed-off-by: Hugh Cole-Ba
Hi Bin,
> On 1 Jan 2020, at 13:25, Bin Meng wrote:
>
> On Wed, Jan 1, 2020 at 7:15 PM Hugh Cole-Baker wrote:
>>
>> Otherwise, uninitialised memory from the upper 32 bits can end up in
>> find_id.class, and this causes bugs later when looking for a driver for
>
Otherwise, uninitialised memory from the upper 32 bits can end up in
find_id.class, and this causes bugs later when looking for a driver for
the class.
Signed-off-by: Hugh Cole-Baker
---
drivers/pci/pci-uclass.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/pci/pci
Hi Vasily,
> On 29 Nov 2019, at 01:06, Vasily Khoruzhick wrote:
>
> On Thu, Nov 28, 2019 at 4:59 PM Kever Yang wrote:
>>
>> Hi Vasily,
>>
>> On 2019/11/28 下午11:51, Vasily Khoruzhick wrote:
>>> On Thu, Nov 28, 2019 at 1:23 AM Kever Yang
>>> wrote:
Hi Vasily,
I think
This enables reading the cpuid from e-fuse, and deriving a static
MAC address from it. Without this, the ethernet interface on the
rockpro64 can't be used to boot.
Signed-off-by: Hugh Cole-Baker
Cc: Philipp Tomsich
---
configs/rockpro64-rk3399_defconfig | 3 +++
1 file changed, 3 insertions
23 matches
Mail list logo
