On 4. Apr 2025, at 18:21, neil.armstr...@linaro.org wrote:
>
> Hi Christian
>
...
>
> could you test:
>
> ==><==
> diff --git a/drivers/net/dwmac_meson8b.c b/drivers/net/dwmac_meson8b.c
> index fde4aabbace..bf9c5e8f349 100644
> --- a/drivers/net/dwmac_meson8b.c
>
eth_halt() in EXIT_BOOT_SERVICES explicitly.
>
> Thanks Heinrich
>
> Reviewed-by: Ilias Apalodimas
>
> [1]
> https://lore.kernel.org/all/c101b675-eee6-44cb-8a44-83f72182f...@kohlschutter.com/
>
> Cc: Michael Brown
> Reported-by: Christian Kohlschütter
> Si
Hi Simon,
> On 1. Apr 2025, at 17:51, Simon Glass wrote:
>>
>> but I don't know precisely what these various functions are supposed to
>> do, and I can't find any path that leads from any of these to eth_halt().
>>
>> Is it possible that U-Boot is failing to call eth_halt() in response to
>> Ex
+Tom Rini (actually adding Tom to the conversation)
> On 3. Apr 2025, at 19:54, Simon Glass wrote:
>
> +Tom Rini in case this affects the release
>
> Hi Christian,
>
> On Fri, 4 Apr 2025 at 01:46, Christian Kohlschütter
> wrote:
>>
>> Hi Simon,
>>
On 31. Mar 2025, at 19:15, Michael Brown wrote:
>
> On 31/03/2025 17:49, Christian Kohlschütter wrote:
>> # hexdump /.argh
>> 000
>> *
>> 0044100 15dc f9c8 6f16 e188
>> 0044110 00a0 52b0 a01c
Hi all,
After upgrading some rather old U-Boot/IPXE setup on two aarch64 boards
(Amlogic S922X-based ODROID N2+ and RK3399-based NanoPi R4S), I noticed strange
errors in the initrd phase of my Linux kernel — usually something like "Illegal
instruction" coming from "udhcpc", etc.
The setup I ha
Provide human-readable manufacturer and product names for the
FriendlyELEC NanoPi R4S.
Enable CONFIG_SYSINFO and CONFIG_SYSINFO_SMBIOS by default.
Signed-off-by: Christian Kohlschütter
---
arch/arm/dts/rk3399-nanopi-r4s-u-boot.dtsi | 22 ++
configs/nanopi-r4s
> On 1. Oct 2022, at 00:58, Christian Kohlschütter
> wrote:
>
> On 1. Oct 2022, at 00:21, Christian Kohlschütter
> wrote:
>>
>>>> See
>>>> https://github.com/hathach/tinyusb/blob/master/examples/device/cdc_msc/src/usb_descriptors.c
>>&
On 1. Oct 2022, at 00:21, Christian Kohlschütter
wrote:
>
>>> See
>>> https://github.com/hathach/tinyusb/blob/master/examples/device/cdc_msc/src/usb_descriptors.c
>>> for an example of such a device. It has one mass storage device and one
>>> CDC.
>&
>> See
>> https://github.com/hathach/tinyusb/blob/master/examples/device/cdc_msc/src/usb_descriptors.c
>> for an example of such a device. It has one mass storage device and one CDC.
>> Changing the device class to 0x00 breaks support on Linux and macOS (I
>> didn't try Windows).
>
> The questi
On 30. Sep 2022, at 01:55, Simon Glass wrote:
...
>> Is there a tool to sort these values in a certain order?
>
> $ echo nanopi-r4s-rk3399_defconfig >asc
> $ ./tools/moveconfig.py -s -d asc
>
> (it could use a new flag to just specific the board, if you want to
> send a patch)
>
> Should these
> On 30. Sep 2022, at 04:42, Marek Vasut wrote:
>
> On 9/26/22 23:55, Christian Kohlschütter wrote:
>> On 26. Sep 2022, at 01:45, Marek Vasut wrote:
>>>
>>> On 9/25/22 16:46, Christian Kohlschütter wrote:
>>>> When detecting USB storage devices,
> On 29. Sep 2022, at 04:36, Simon Glass wrote:
>
> On Wed, 28 Sept 2022 at 18:15, Christian Kohlschütter
> wrote:
>>
>> Provide human-readable manufacturer and product names for the
>> FriendlyELEC NanoPi R4S.
>>
>> Enable CONFIG_SYSINFO and CONFI
> On 29. Sep 2022, at 04:36, Simon Glass wrote:
>
> Hi Christian,
>
> On Wed, 28 Sept 2022 at 18:20, Christian Kohlschütter
> wrote:
>>
>> With CONFIG_DISPLAY_CPUINFO=y and CONFIG_CPU=y, the initcall sequence
>> may fail (and therefore hang the boot process
to the non-Driver Model
implementation of print_cpuinfo.
Signed-off-by: Christian Kohlschütter
---
common/board_f.c | 14 +-
include/init.h | 3 +--
2 files changed, 10 insertions(+), 7 deletions(-)
diff --git a/common/board_f.c b/common/board_f.c
index 18e2246733..0656845e24
Provide human-readable manufacturer and product names for the
FriendlyELEC NanoPi R4S.
Enable CONFIG_SYSINFO and CONFIG_SYSINFO_SMBIOS by default.
Signed-off-by: Christian Kohlschütter
---
arch/arm/dts/rk3399-nanopi-r4s-u-boot.dtsi | 22 ++
configs/nanopi-r4s
Currently, device trees can only specify an asset tag for the
"baseboard" type, not for the "chassis" (system enclosure) type, which
usually carries the more user-visible asset tag.
Add support for the chassis asset-tag, and update the documentation.
Signed-off-by: Ch
Please disregard (duplicate patch)
Following up with "[PATCH] rk3399: r4s: Derive local MAC address if EEPROM is
missing".
Cheers,
Christian
> Following up with "[PATCH] rockchip: rk3399: add ethaddr and serial# init,
> enable for R4S", which enables these settings in
> configs/nanopi-r4s-rk3399_defconfig.
>
> This doesn't look any different from what you already sent.
>
> ChenYu
Following up with "[PATCH] rk3399: r4s: Derive local
On 26. Sep 2022, at 01:45, Marek Vasut wrote:
>
> On 9/25/22 16:46, Christian Kohlschütter wrote:
>> When detecting USB storage devices, we currently skip everything that is
>> not marked as "undefined device class".
>> Composite devices such as tinyusb's CDC+MSC identify as "miscellaneous"
>> (
> On 26. Sep 2022, at 13:59, Chen-Yu Tsai wrote:
>
> On Mon, Sep 26, 2022 at 7:53 PM Christian Kohlschütter
> wrote:
>>
>> Some RK3399 boards, such as newer revisions of NanoPi R4S, do not
>> provide an EEPROM chip containing a globally unique MAC address.
>>
>> Currently, this means that a r
21 matches
Mail list logo
