On 2/9/24 22:15, Niklas Söderlund wrote:
To prepare support for multiple register layouts pointers to register
tables where added to struct cpg_mssr_info. These pointers are suppose
to be filled in at probe time and no intended change in behavior was
intended.
However the new pointers where
On Sun, Feb 11, 2024 at 3:49 AM Jonas Karlman wrote:
>
> Hi Chen-Yu,
>
> On 2024-02-10 07:32, Chen-Yu Tsai wrote:
> > From: Chen-Yu Tsai
> >
> > Regenerate RK3399 defconfigs after adding imply statements.
> >
> > Signed-off-by: Chen-Yu Tsai
> > ---
> > configs/chromebook_bob_defconfig
On Sat, Feb 10, 2024 at 01:07:09PM +0100, Igor Opaniuk wrote:
> From: Igor Opaniuk
>
> Add support for the SHA-512 Secure Hash Algorithm which uses ARMv8 Crypto
> Extensions. The CPU should support ARMv8.2 instruction set and implement
> SHA512H, SHA512H2, SHA512SU0, and SHA512SU1 instructions.
On Sat, Feb 10, 2024 at 07:18:10PM +0100, Dragan Simic wrote:
> As discussed on the U-Boot mailing list, [1][2] only some Rockchip SoCs
> suffer from a bug in their BROMs that requires a specific format for their
> SPI images, which was the reason for the rkspi format to be introduced.
>
>
Sorry, pls ping
Thanks, Arseniy
On 08.01.2024 21:33, Arseniy Krasnov wrote:
> Sorry, pls ping
>
> Thanks, Arseniy
>
> On 20.12.2023 22:36, Arseniy Krasnov wrote:
>> Add access to OTP region. It supports info, dump, write and lock
>> operations.
>>
>> Signed-off-by: Arseniy Krasnov
>> ---
>>
Sorry, pls ping
Thanks, Arseniy
On 08.01.2024 21:33, Arseniy Krasnov wrote:
> Sorry, pls ping
>
> Thanks, Arseniy
[Fixing Ard's email address for something more current.]
On Sat, 10 Feb 2024 12:07:09 +,
Igor Opaniuk wrote:
>
> From: Igor Opaniuk
>
> Add support for the SHA-512 Secure Hash Algorithm which uses ARMv8 Crypto
> Extensions. The CPU should support ARMv8.2 instruction set and implement
>
On 2024-02-10 20:30, Jonas Karlman wrote:
On 2024-02-10 18:18, Dragan Simic wrote:
On 2024-02-08 22:54, Jonas Karlman wrote:
On 2024-02-08 04:53, Dragan Simic wrote:
On 2024-02-07 01:02, Jonas Karlman wrote:
Similar to RK35xx the BootRom in RK3328 can read all data and look
for
idbloader at
Basic support for Amlogic Meson NAND controller on AXG. This version
works at only first EDO mode.
Based on Linux version 6.7.0-rc4.
Signed-off-by: Arseniy Krasnov
---
Changelog:
v1 -> v2:
* Update commit message with 'Based on Linux ...'.
* Add Linux driver author to .c file header.
*
On 2024-02-10 20:38, Jonas Karlman wrote:
On 2024-02-10 19:31, Dragan Simic wrote:
On 2024-02-07 01:02, Jonas Karlman wrote:
Add Kconfig options to enable support for booting from SPI NOR flash
on
Pine64 Rock64.
The generated bootable u-boot-rockchip-spi.bin that can be written to
0x0 of SPI
On 2024-02-10 19:31, Dragan Simic wrote:
> On 2024-02-07 01:02, Jonas Karlman wrote:
>> Add Kconfig options to enable support for booting from SPI NOR flash on
>> Pine64 Rock64.
>>
>> The generated bootable u-boot-rockchip-spi.bin that can be written to
>> 0x0 of SPI NOR flash. The FIT image is
Hi Dragan,
On 2024-02-10 18:18, Dragan Simic wrote:
> Hello Jonas,
>
> On 2024-02-08 22:54, Jonas Karlman wrote:
>> On 2024-02-08 04:53, Dragan Simic wrote:
>>> On 2024-02-07 01:02, Jonas Karlman wrote:
Similar to RK35xx the BootRom in RK3328 can read all data and look
for
Hi Chen-Yu,
On 2024-02-10 07:32, Chen-Yu Tsai wrote:
> From: Chen-Yu Tsai
>
> Regenerate RK3399 defconfigs after adding imply statements.
>
> Signed-off-by: Chen-Yu Tsai
> ---
> configs/chromebook_bob_defconfig | 2 --
> configs/chromebook_kevin_defconfig| 2 --
>
On 2024-02-07 01:02, Jonas Karlman wrote:
Add Kconfig options to enable support for booting from SPI NOR flash on
Pine64 Rock64.
The generated bootable u-boot-rockchip-spi.bin that can be written to
0x0 of SPI NOR flash. The FIT image is loaded from 0x6, same as on
RK35xx boards.
=> sf
As discussed on the U-Boot mailing list, [1][2] only some Rockchip SoCs
suffer from a bug in their BROMs that requires a specific format for their
SPI images, which was the reason for the rkspi format to be introduced.
Improve the description of the rkspi format a bit to mention this, for
future
On Thu, Feb 8, 2024 at 1:59 PM Frieder Schrempf wrote:
>
> From: Frieder Schrempf
>
> The datasheet can be found here:
> https://www.esmt.com.tw/upload/pdf/ESMT/datasheets/EN25Q80B_Ver.E.pdf
>
> Signed-off-by: Frieder Schrempf
Reviewed-by: Fabio Estevam
Hi Frieder,
On Thu, Feb 8, 2024 at 1:59 PM Frieder Schrempf wrote:
> +/ {
> + binman: binman {
> + filename = "flash.bin";
> + pad-byte = <0x00>;
> +
> + spl: blob-ext@1 {
> + offset = <0x0>;
> +
On Mon, 4 Dec 2023 01:09:30 +
Andre Przywara wrote:
Hi Joe, Ramon, Tom,
for some reason patchwork put this on my plate, but it looks like
genuine network code to me, and the problem definitely doesn't affect
sunxi.
As tagged below, I am happy with this change, so if there are no
objections,
Hello Da Xue,
On 2024-02-09 02:57, Da Xue wrote:
On Wed, Feb 7, 2024 at 10:53 PM Dragan Simic
wrote:
On 2024-02-07 01:02, Jonas Karlman wrote:
> Similar to RK35xx the BootRom in RK3328 can read all data and look for
> idbloader at 0x8000, same as on SD and eMMC.
>
> Use the rksd format and
Hello Jonas,
On 2024-02-08 22:54, Jonas Karlman wrote:
On 2024-02-08 04:53, Dragan Simic wrote:
On 2024-02-07 01:02, Jonas Karlman wrote:
Similar to RK35xx the BootRom in RK3328 can read all data and look
for
idbloader at 0x8000, same as on SD and eMMC.
Use the rksd format and modify the
On 2024-02-10 07:32, Chen-Yu Tsai wrote:
From: Chen-Yu Tsai
This series enables ROCKCHIP_EFUSE and MISC_INIT_R by default for
RK3328
and RK3399 so that the cpuid is read from the efuse and used to
generate
a serial number and MAC addresses for all boards.
This stacks on top of the recent
From: Janne Grunau
Draw symbols from code page 437 code points 0x01 - 01f used by UEFI
applications to draw user interfaces using
EFI_SIMPLE_TEXT_OUTPUT_PROTOCOL.
Add a simple test to displaying the Konami code using symbols used by
grub2. The output has to be checked manually on the screen for
From: Andre Przywara
UEFI applications rely on Unicode output capability, and might use that
for drawing pseudo-graphical interfaces using Unicode defined box
drawing characters.
Add a simple test to display the most basic box characters, which would
need to be checked manually on the screen
From: Janne Grunau
Suggested-by: Heinrich Schuchardt
Signed-off-by: Janne Grunau
---
include/charset.h | 14 --
1 file changed, 12 insertions(+), 2 deletions(-)
diff --git a/include/charset.h b/include/charset.h
index 44034c71d3..f1050c903d 100644
--- a/include/charset.h
+++
From: Andre Przywara
UEFI relies entirely on unicode output, which actual fonts displayed on
the screen might not be ready for.
Add a test displaying some international characters, to reveal missing
glyphs, especially in our builtin fonts.
This would be needed to be manually checked on the
From: Janne Grunau
efi_console / UEFI applications (grub2, sd-boot, ...) pass UTF-8
character sequences to vidconsole which results in wrong glyphs for code
points outside of ASCII. The truetype console expects Unicode code
points and bitmap font based consoles expect code page 437 code points.
Andre submitted 2 years ago DM_VIDEO improvements for UEFI applications
using UEFI's EFI_SIMPLE_TEXT_OUTPUT_PROTOCOL but did not follow with
suggested changes. This series takes care of the UTF-8 support which
required to draw symbol and box drawing characters used by UEFI
applications like grub2
From: Janne Grunau
Code page 437 uses code points 1-31 for glyphs instead of control
characters. Map the appropriate Unicode code points to this code points.
Fixes rendering of grub2's menu as EFI application using the
EFI_SIMPLE_TEXT_OUTPUT_PROTOCOL on a console with bitmap fonts.
From: Igor Opaniuk
Add support for the SHA-512 Secure Hash Algorithm which uses ARMv8 Crypto
Extensions. The CPU should support ARMv8.2 instruction set and implement
SHA512H, SHA512H2, SHA512SU0, and SHA512SU1 instructions.
This information can be obtained from ID_AA64ISAR0_EL1 (AArch64
Hej,
On Thu, Jan 18, 2024, at 19:48, Heinrich Schuchardt wrote:
> On 1/17/24 23:24, Janne Grunau via B4 Relay wrote:
>> From: Andre Przywara
>>
>> UEFI relies entirely on unicode output, which actual fonts displayed on
>> the screen might not be ready for.
>>
>> Add a test displaying some
We should not use the reserved value 0x00 for the wake up type but
use 0x02 (Unknown).
Signed-off-by: Heinrich Schuchardt
---
v3:
use an enum for the constants
v2:
use wake-up type 'Unknown' as our default
add more SMBIOS wake-up type constants
---
include/smbios.h | 27
Correct type 1 output
* render wake up time as string
* print family string
* remove duplicate serial number output
Signed-off-by: Heinrich Schuchardt
---
v3:
no change
v2:
no change
---
cmd/smbios.c | 25 +++--
1 file changed, 23 insertions(+), 2
We should not use the reserved value 0x00 for the wake up type but
use 0x06 (Power Switch).
Correctly display wake-up type in smbios command.
Display SMBIOS type 1 field family in smbios command.
v3:
provide an enum for the wake-up type constants
v2:
use wake-up type 0x02 as our
Hi Chen-Yu,
For the entire series:
Reviewed-by: Christopher Obbard
On 10 February 2024 06:32:46 GMT, Chen-Yu Tsai wrote:
>From: Chen-Yu Tsai
>
>Hi folks,
>
>This series enables ROCKCHIP_EFUSE and MISC_INIT_R by default for RK3328
>and RK3399 so that the cpuid is read from the efuse and used
34 matches
Mail list logo
