x86: expo: Add support for editing coreboot CMOS RAM settings
Subsystems (2)
v3 cover x86: expo: Add support for editing coreboot CMOS RAM settings
U-Boot provides support for editing settings with an 'expo', as well as reading and writing settings to CMOS RAM.
This series integrates expo functionality with coreboot, using the sysinfo table to get a list of settings, creating an expo with them and allowing them to be edited.
A new CI test provides coverage for some coreboot-related commands. For this to work, a number of minor tweaks are made to existing tests, so that they pass on coreboot (x86) or at least are skipped when they cannot pass. Likely most of these fixes will apply to other boards too.
It includes several other fixes and improvements:
- new -m flag for 'bootflow scan' so it can display a menu automatically
- Fix for video-scrolling crash with Truetype
- menu items can now have individual integer values
- menu items are lined up according to the width of all menu labels
Changes in v3:
- Update Dockerfile instead
Changes in v2:
- Avoid using common.h
- Avoid using common.h
- Rebase to -next
Simon Glass (20):
video: Add a dark-grey console colour
video: Avoid starting a new line to close to the bottom
expo: Place menu items to the right of all labels
expo: Set the initial next_id to 1
expo: Use standard numbering for save and discard
expo: Allow menu items to have values
expo: Add a little more cedit CMOS logging
expo: Support menu-item values in cedit
expo: Drop unneceesary calls to expo_str()
expo: Drop scene_title_set()
expo: Add forward declaration for udevice to cedit
x86: coreboot: Enable unit tests
docker: Update coreboot
doc: Update coreboot's CI information
x86: coreboot: Add a test for cbsysinfo command
x86: coreboot: Show the option table
x86: coreboot: Enable support for the configuration editor
x86: coreboot: Add a command to check and update CMOS RAM
x86: coreboot: Allow building an expo for editing CMOS config
x86: Enable RTC command by default
arch/sandbox/dts/cedit.dtsi | 3 + arch/x86/dts/coreboot.dts | 7 + boot/Makefile | 3 + boot/cedit.c | 191 +++++++++++++++-------- boot/expo.c | 3 + boot/expo_build.c | 36 ++--- boot/expo_build_cb.c | 245 ++++++++++++++++++++++++++++++ boot/scene.c | 61 ++++++-- boot/scene_internal.h | 30 +++- boot/scene_menu.c | 26 +++- boot/scene_textline.c | 3 +- cmd/Kconfig | 12 ++ cmd/cedit.c | 28 ++++ cmd/x86/Makefile | 1 + cmd/x86/cbcmos.c | 139 +++++++++++++++++ cmd/x86/cbsysinfo.c | 73 ++++++++- configs/coreboot64_defconfig | 2 + configs/coreboot_defconfig | 6 + doc/board/coreboot/coreboot.rst | 16 +- doc/develop/cedit.rst | 9 +- doc/develop/expo.rst | 26 +++- doc/usage/cmd/cbcmos.rst | 45 ++++++ doc/usage/cmd/cbsysinfo.rst | 99 ++++++++++++ doc/usage/cmd/cedit.rst | 91 ++++++++++- doc/usage/index.rst | 1 + drivers/video/vidconsole-uclass.c | 4 +- drivers/video/video-uclass.c | 3 + include/cedit.h | 1 + include/expo.h | 51 +++++-- include/test/cedit-test.h | 30 ++-- include/video.h | 4 +- include/video_console.h | 8 + test/boot/cedit.c | 22 ++- test/boot/expo.c | 26 +++- test/boot/files/expo_ids.h | 3 +- test/boot/files/expo_layout.dts | 5 +- test/cmd/Makefile | 1 + test/cmd/coreboot.c | 119 +++++++++++++++ tools/docker/Dockerfile | 7 +- tools/expo.py | 33 +++- 40 files changed, 1309 insertions(+), 164 deletions(-) create mode 100644 boot/expo_build_cb.c create mode 100644 cmd/x86/cbcmos.c create mode 100644 doc/usage/cmd/cbcmos.rst create mode 100644 test/cmd/coreboot.c
Signature · 1 line
2.34.1
PATCH v3 1/20 video: Add a dark-grey console colour
This is useful for highlighting something with a black background, as is needed with cedit when using a white-on-black console. Add this as a new colour.
---
(no changes since v1)
boot/scene.c | 2 +- drivers/video/video-uclass.c | 3 +++ include/video.h | 1 + 3 files changed, 5 insertions(+), 1 deletion(-)
boot/scene.c +1 -1
@@ -339,7 +339,7 @@ static void scene_render_background(struct scene_obj *obj, bool box_only)/* draw a background for the object */ if (CONFIG_IS_ENABLED (SYS_WHITE_ON_BLACK )) { - fore =VID_BLACK ; + fore =VID_DARK_GREY ; back =VID_WHITE ; }else { fore =VID_LIGHT_GRAY ;
drivers/video/video-uclass.c +3 -0
@@ -294,6 +294,9 @@ static const struct vid_rgb colours[VID_COLOUR_COUNT] = { { 0xff, 0x00, 0xff }, /* bright magenta */ { 0x00, 0xff, 0xff }, /* bright cyan */ { 0xff, 0xff, 0xff }, /* white */ + +/* an extra one for menus */ + { 0x40, 0x40, 0x40 }, /* dark gray */ };u32 video_index_to_colour (struct video_priv *priv,enum colour_idx idx)
include/video.h +1 -0
@@ -181,6 +181,7 @@ enum colour_idx {VID_LIGHT_MAGENTA ,VID_LIGHT_CYAN ,VID_WHITE , +VID_DARK_GREY , VID_COLOUR_COUNT };
Signature · 1 line
2.34.1
Re: [PATCH v3 01/20] video: Add a dark-grey console colour
This is useful for highlighting something with a black background, as is needed with cedit when using a white-on-black console. Add this as a new colour.
---
(no changes since v1)
boot/scene.c | 2 +- drivers/video/video-uclass.c | 3 +++ include/video.h | 1 + 3 files changed, 5 insertions(+), 1 deletion(-)
Applied to u-boot-dm, thanks!
PATCH v3 2/20 video: Avoid starting a new line to close to the bottom
In reply to Simon GlassWhen starting a new text line, an assumption is made that the current vertical position is a multiple of the character height. When this is not true, characters can be written after the end of the framebuffer.
This can causes crashes and strange errors from QEMU.
Adjust the scrolling check when processing a newline character, to avoid any problems.
Add some comments to make things a little clearer.
---
(no changes since v1)
drivers/video/vidconsole-uclass.c | 4 +++- include/video.h | 3 ++- include/video_console.h | 8 ++++++++ 3 files changed, 13 insertions(+), 2 deletions(-)
drivers/video/vidconsole-uclass.c +3 -1
@@ -94,7 +94,9 @@ static void vidconsole_newline(struct udevice *dev) priv->ycur += priv->y_charsize;/* Check if we need to scroll the terminal */ -if ((priv->ycur + priv->y_charsize) / priv->y_charsize > priv->rows) { +if (vid_priv->rot %2 ? + priv->ycur + priv->x_charsize > vid_priv->xsize : + priv->ycur + priv->y_charsize > vid_priv->ysize) {vidconsole_move_rows (dev,0 , rows, priv->rows - rows);for (i =0 ; i < rows; i++) vidconsole_set_row(dev, priv->rows - i - 1,
include/video.h +2 -1
@@ -78,7 +78,8 @@ enum video_format {* * @xsize: Number of pixel columns (e.g. 1366) * @ysize: Number of pixels rows (e.g.. 768) -* @rot: Display rotation (0=none, 1=90 degrees clockwise, etc.) +* @rot: Display rotation (0=none, 1=90 degrees clockwise, etc.). THis +* does not affect @xsize and @ysize * @bpix: Encoded bits per pixel (enum video_log2_bpp) * @format: Pixel format (enum video_format) * @vidconsole_drv_name: Driver to use for the text console, NULL to
include/video_console.h +8 -0
@@ -27,6 +27,14 @@ enum {* Drivers must set up @rows, @cols, @x_charsize, @y_charsize in their probe() * method. Drivers may set up @xstart_frac if desired. * +* Note that these values relate to the rotated console, so that an 80x25 +* console which is rotated 90 degrees will have rows=80 and cols=25 +* +* The xcur_frac and ycur values refer to the unrotated coordinates, that is +* xcur_frac always advances with each character, even if its limit might be +* vid_priv->ysize instead of vid_priv->xsize if the console is rotated 90 or +* 270 degrees. +* * @sdev: stdio device, acting as an output sink * @xcur_frac: Current X position, in fractional units (VID_TO_POS(x)) * @ycur: Current Y position in pixels (0=top)
Signature · 1 line
2.34.1
Re: [PATCH v3 02/20] video: Avoid starting a new line to close to the bottom
When starting a new text line, an assumption is made that the current vertical position is a multiple of the character height. When this is not true, characters can be written after the end of the framebuffer.
This can causes crashes and strange errors from QEMU.
Adjust the scrolling check when processing a newline character, to avoid any problems.
Add some comments to make things a little clearer.
---
(no changes since v1)
drivers/video/vidconsole-uclass.c | 4 +++- include/video.h | 3 ++- include/video_console.h | 8 ++++++++ 3 files changed, 13 insertions(+), 2 deletions(-)
Applied to u-boot-dm, thanks!
PATCH v3 3/20 expo: Place menu items to the right of all labels
In reply to Simon GlassAt present a fixed position is used for menu items, 200 pixels to the right of the left side of the labels. This means that a menu item with a very long label may overlap the items.
It seems better to calculate the maximum label width and then place the items to the right of all of them.
To implement this, add a new struct to containing arrangement information. Calculate it before doing the actual arrangement. Add a new style item which sets the amount of space from the right side of the labels to left side of the items.
---
(no changes since v1)
boot/cedit.c | 13 ++++++++--- boot/expo.c | 2 ++ boot/scene.c | 52 +++++++++++++++++++++++++++++++++++++++++-- boot/scene_internal.h | 20 +++++++++++++++-- boot/scene_menu.c | 9 +++++--- boot/scene_textline.c | 3 ++- doc/develop/expo.rst | 4 ++++ include/expo.h | 12 ++++++++++ 8 files changed, 104 insertions(+), 11 deletions(-)
boot/cedit.c +10 -3
@@ -51,10 +51,11 @@ struct cedit_iter_priv {int cedit_arange (struct expo *exp,struct video_priv *vpriv,uint scene_id) { +struct expo_arrange_info arr;struct scene_obj_txt *txt;struct scene_obj *obj;struct scene *scn; -int y; +int y, ret; scn =expo_lookup_scene_id (exp, scene_id);if (!scn)
@@ -68,6 +69,11 @@ int cedit_arange(struct expo *exp, struct video_priv *vpriv, uint scene_id)if (txt)scene_obj_set_pos (scn, txt->obj.id,200 ,10 ); +memset (&arr,'\0' ,sizeof (arr)); + ret =scene_calc_arrange (scn, &arr); +if (ret <0 ) +return log_msg_ret ("arr" , ret); + y =100 ;list_for_each_entry (obj, &scn->obj_head, sibling) {switch (obj->type) {
@@ -77,12 +83,13 @@ int cedit_arange(struct expo *exp, struct video_priv *vpriv, uint scene_id)break ;case SCENEOBJT_MENU :scene_obj_set_pos (scn, obj->id,50 , y); -scene_menu_arrange (scn, (struct scene_obj_menu *)obj); +scene_menu_arrange (scn, &arr, + (struct scene_obj_menu *)obj); y +=50 ;break ;case SCENEOBJT_TEXTLINE :scene_obj_set_pos (scn, obj->id,50 , y); -scene_textline_arrange (scn, +scene_textline_arrange (scn, &arr, (struct scene_obj_textline *)obj); y +=50 ;break ;
boot/expo.c +2 -0
@@ -258,6 +258,8 @@ int expo_apply_theme(struct expo *exp, ofnode node)ofnode_read_u32 (node,"font-size" , &theme->font_size);ofnode_read_u32 (node,"menu-inset" , &theme->menu_inset);ofnode_read_u32 (node,"menuitem-gap-y" , &theme->menuitem_gap_y); +ofnode_read_u32 (node,"menu-title-margin-x" , + &theme->menu_title_margin_x);list_for_each_entry (scn, &exp->scene_head, sibling) { ret =scene_apply_theme (scn, theme);
boot/scene.c +50 -2
75 lines not on this page · raw message
boot/scene_internal.h +18 -2
@@ -96,10 +96,12 @@ int scene_calc_dims(struct scene *scn, bool do_menus);* if not already done * * @scn: Scene to update +* @arr: Arrangement information * @menu: Menu to process * Returns: 0 if OK, -ve on error */ -int scene_menu_arrange (struct scene *scn,struct scene_obj_menu *menu); +int scene_menu_arrange (struct scene *scn,struct expo_arrange_info *arr, +struct scene_obj_menu *menu);/** * scene_textline_arrange() - Set the position of things in a textline
@@ -108,10 +110,12 @@ int scene_menu_arrange(struct scene *scn, struct scene_obj_menu *menu);* positioned correctly relative to the textline. * * @scn: Scene to update +* @arr: Arrangement information * @tline: textline to process * Returns: 0 if OK, -ve on error */ -int scene_textline_arrange (struct scene *scn,struct scene_obj_textline *tline); +int scene_textline_arrange (struct scene *scn,struct expo_arrange_info *arr, +struct scene_obj_textline *tline);/** * scene_apply_theme() - Apply a theme to a scene
@@ -358,4 +362,16 @@ int scene_textline_open(struct scene *scn, struct scene_obj_textline *tline);*/ int scene_textline_close (struct scene *scn,struct scene_obj_textline *tline); +/** +* scene_calc_arrange() - Calculate sizes needed to arrange a scene +* +* Checks the size of some objects and stores this info to help with a later +* scene arrangement +* +* @scn: Scene to check +* @arr: Place to put scene-arrangement info +* Returns: 0 if OK, -ve on error +*/ +int scene_calc_arrange (struct scene *scn,struct expo_arrange_info *arr); +#endif /* __SCENE_INTERNAL_H */
boot/scene_menu.c +6 -3
@@ -168,7 +168,8 @@ int scene_menu_calc_dims(struct scene_obj_menu *menu)return 0 ; } -int scene_menu_arrange (struct scene *scn,struct scene_obj_menu *menu) +int scene_menu_arrange (struct scene *scn,struct expo_arrange_info *arr, +struct scene_obj_menu *menu) {const bool open = menu->obj.flags &SCENEOF_OPEN ;struct expo *exp = scn->expo;
@@ -182,16 +183,18 @@ int scene_menu_arrange(struct scene *scn, struct scene_obj_menu *menu) x = menu->obj.dim.x; y = menu->obj.dim.y;if (menu->title_id) { +int width; + ret =scene_obj_set_pos (scn, menu->title_id, menu->obj.dim.x, y);if (ret <0 )return log_msg_ret ("tit" , ret); - ret =scene_obj_get_hw (scn, menu->title_id,NULL ); + ret =scene_obj_get_hw (scn, menu->title_id, &width);if (ret <0 )return log_msg_ret ("hei" , ret);if (stack) - x +=200 ; + x += arr->label_width + theme->menu_title_margin_x;else y += ret *2 ; }
boot/scene_textline.c +2 -1
@@ -87,7 +87,8 @@ int scene_textline_calc_dims(struct scene_obj_textline *tline)return 0 ; } -int scene_textline_arrange (struct scene *scn,struct scene_obj_textline *tline) +int scene_textline_arrange (struct scene *scn,struct expo_arrange_info *arr, +struct scene_obj_textline *tline) {const bool open = tline->obj.flags &SCENEOF_OPEN ;bool point;
doc/develop/expo.rst +4 -0
@@ -176,6 +176,10 @@ menu-inset menuitem-gap-y Number of pixels between menu items +menu-title-margin-x + Number of pixels between right side of menu title to the left size of the + menu labels + Pop-up mode -----------
include/expo.h +12 -0
@@ -59,11 +59,14 @@ struct expo_action {* @font_size: Default font size for all text * @menu_inset: Inset width (on each side and top/bottom) for menu items * @menuitem_gap_y: Gap between menu items in pixels +* @menu_title_margin_x: Gap between right side of menu title and left size of +* menu label */ struct expo_theme {u32 font_size;u32 menu_inset;u32 menuitem_gap_y; +u32 menu_title_margin_x; };/**
@@ -341,6 +344,15 @@ struct scene_obj_textline {uint pos; }; +/** +* struct expo_arrange_info - Information used when arranging a scene +* +* @label_width: Maximum width of labels in scene +*/ +struct expo_arrange_info { +int label_width; +}; +/** * expo_new() - create a new expo *
Signature · 1 line
2.34.1
Re: [PATCH v3 03/20] expo: Place menu items to the right of all labels
At present a fixed position is used for menu items, 200 pixels to the right of the left side of the labels. This means that a menu item with a very long label may overlap the items.
It seems better to calculate the maximum label width and then place the items to the right of all of them.
To implement this, add a new struct to containing arrangement information. Calculate it before doing the actual arrangement. Add a new style item which sets the amount of space from the right side of the labels to left side of the items.
---
(no changes since v1)
boot/cedit.c | 13 ++++++++--- boot/expo.c | 2 ++ boot/scene.c | 52 +++++++++++++++++++++++++++++++++++++++++-- boot/scene_internal.h | 20 +++++++++++++++-- boot/scene_menu.c | 9 +++++--- boot/scene_textline.c | 3 ++- doc/develop/expo.rst | 4 ++++ include/expo.h | 12 ++++++++++ 8 files changed, 104 insertions(+), 11 deletions(-)
Applied to u-boot-dm, thanks!
PATCH v3 4/20 expo: Set the initial next_id to 1
In reply to Simon GlassIf expo_set_dynamic_start() is never called, the first scene created will have an ID of 0, which is invalid. Correct this by setting a default value.
Add a test to check this.
---
(no changes since v1)
boot/expo.c | 1 + test/boot/expo.c | 23 +++++++++++++++++++++-- 2 files changed, 22 insertions(+), 2 deletions(-)
boot/expo.c +1 -0
@@ -29,6 +29,7 @@ int expo_new(const char *name, void *priv, struct expo **expp) exp->priv = priv;INIT_LIST_HEAD (&exp->scene_head);INIT_LIST_HEAD (&exp->str_head); + exp->next_id =1 ; *expp = exp;
test/boot/expo.c +21 -2
@@ -91,7 +91,7 @@ static int expo_base(struct unit_test_state *uts) *name ='\0' ;ut_assertnonnull (exp);ut_asserteq (0 , exp->scene_id); -ut_asserteq (0 , exp->next_id); +ut_asserteq (1 , exp->next_id);/* Make sure the name was allocated */ ut_assertnonnull (exp->name);
@@ -130,7 +130,7 @@ static int expo_scene(struct unit_test_state *uts)ut_assertok (expo_new (EXPO_NAME ,NULL , &exp)); scn =NULL ; -ut_asserteq (0 , exp->next_id); +ut_asserteq (1 , exp->next_id);strcpy (name,SCENE_NAME1 ); id =scene_new (exp, name,SCENE1 , &scn); *name ='\0' ;
@@ -167,6 +167,25 @@ static int expo_scene(struct unit_test_state *uts) }BOOTSTD_TEST (expo_scene,UTF_DM |UTF_SCAN_FDT ); +/* Check creating a scene with no ID */ +static int expo_scene_no_id (struct unit_test_state *uts) +{ +struct scene *scn; +struct expo *exp; +char name[100 ]; +int id; + +ut_assertok (expo_new (EXPO_NAME ,NULL , &exp)); +ut_asserteq (1 , exp->next_id); + +strcpy (name,SCENE_NAME1 ); + id =scene_new (exp,SCENE_NAME1 ,0 , &scn); +ut_asserteq (1 , scn->id); + +return 0 ; +} +BOOTSTD_TEST (expo_scene_no_id,UTF_DM |UTF_SCAN_FDT ); +/* Check creating a scene with objects */ static int expo_object (struct unit_test_state *uts) {
Signature · 1 line
2.34.1
Re: [PATCH v3 04/20] expo: Set the initial next_id to 1
If expo_set_dynamic_start() is never called, the first scene created will have an ID of 0, which is invalid. Correct this by setting a default value.
Add a test to check this.
---
(no changes since v1)
boot/expo.c | 1 + test/boot/expo.c | 23 +++++++++++++++++++++-- 2 files changed, 22 insertions(+), 2 deletions(-)
Applied to u-boot-dm, thanks!
PATCH v3 5/20 expo: Use standard numbering for save and discard
In reply to Simon GlassSet aside some expo IDs for 'save' and 'discard' buttons. This avoids needing to store the IDs for these. Adjust the documentation and expo tool for the new EXPOID_BASE_ID value.
Ignore these objects when saving and loading the cedit, since they do not contain real data.
Adjust 'cedit run' to return failure when the user exits the expo without saving. Update the test for this change as well.
---
(no changes since v1)
boot/cedit.c | 24 +++++++++++++++++++++--- boot/expo.c | 2 +- doc/develop/cedit.rst | 7 ++++++- doc/develop/expo.rst | 12 ++++++++---- include/expo.h | 20 ++++++++++++++++++++ include/test/cedit-test.h | 30 +++++++++++++++--------------- test/boot/cedit.c | 14 ++++++++------ test/boot/expo.c | 8 ++++---- test/boot/files/expo_ids.h | 3 +-- tools/expo.py | 33 ++++++++++++++++++++++++++++----- 10 files changed, 112 insertions(+), 41 deletions(-)
boot/cedit.c +21 -3
@@ -154,7 +154,7 @@ int cedit_run(struct expo *exp)struct video_priv *vid_priv;uint scene_id;struct scene *scn; -bool done; +bool done, save;int ret;cli_ch_init (cch);
@@ -164,6 +164,7 @@ int cedit_run(struct expo *exp) scene_id = ret; done = false; + save = false; do { struct expo_action act; int ichar, key;
@@ -208,6 +209,15 @@ int cedit_run(struct expo *exp)case EXPOACT_OPEN :scene_set_open (scn, act.select.id, true);cedit_arange (exp, vid_priv, scene_id); +switch (scn->highlight_id) { +case EXPOID_SAVE : + done = true; + save = true; +break ; +case EXPOID_DISCARD : + done = true; +break ; + }break ;case EXPOACT_CLOSE :scene_set_open (scn, act.select.id, false);
@@ -229,6 +239,8 @@ int cedit_run(struct expo *exp)if (ret)return log_msg_ret ("end" , ret); +if (!save) +return -EACCES ;return 0 ; }
@@ -477,6 +489,9 @@ static int h_write_settings_env(struct scene_obj *obj, void *vpriv)const char *str;int val, ret; +if (obj->id <EXPOID_BASE_ID ) +return 0 ; +snprintf (var,sizeof (var),"c.%s" , obj->name);switch (obj->type) {
@@ -549,6 +564,9 @@ static int h_read_settings_env(struct scene_obj *obj, void *vpriv)char var[60 ];int val; +if (obj->id <EXPOID_BASE_ID ) +return 0 ; +snprintf (var,sizeof (var),"c.%s" , obj->name);switch (obj->type) {
@@ -644,7 +662,7 @@ static int h_write_settings_cmos(struct scene_obj *obj, void *vpriv)int val, ret;uint i, seq; -if (obj->type !=SCENEOBJT_MENU ) +if (obj->type !=SCENEOBJT_MENU || obj->id <EXPOID_BASE_ID )return 0 ; menu = (struct scene_obj_menu *)obj;
@@ -734,7 +752,7 @@ static int h_read_settings_cmos(struct scene_obj *obj, void *vpriv)int val, ret;uint i; -if (obj->type !=SCENEOBJT_MENU ) +if (obj->type !=SCENEOBJT_MENU || obj->id <EXPOID_BASE_ID )return 0 ; menu = (struct scene_obj_menu *)obj;
boot/expo.c +1 -1
@@ -29,7 +29,7 @@ int expo_new(const char *name, void *priv, struct expo **expp) exp->priv = priv;INIT_LIST_HEAD (&exp->scene_head);INIT_LIST_HEAD (&exp->str_head); - exp->next_id =1 ; + exp->next_id =EXPOID_BASE_ID ; *expp = exp;
doc/develop/cedit.rst +6 -1
@@ -94,7 +94,7 @@ them. Expo supports doing this with an enum, where every ID is listed in the enum:: enum { - ZERO, + ID_PROMPT = EXPOID_BASE_ID, ID_PROMPT,
@@ -130,6 +130,11 @@ that means that something is wrong with your syntax, or perhaps you have an ID in the `.dts` file that is not mentioned in your enum. Check both files and try again. +Note that the first ID in your file must be no less that `EXPOID_BASE_ID` since +IDs before that are reserved. The `expo.py` tool automatically obtains this +value from the `expo.h` header file, but you must set the first ID to this +enum value. + Use the command interface -------------------------
doc/develop/expo.rst +8 -4
@@ -88,8 +88,13 @@ or even the IDs of objects. Programmatic creation of many items in a loop can be handled by allocating space in the enum for a maximum number of items, then adding the loop count to the enum values to obtain unique IDs. -Where dynamic IDs are need, use expo_set_dynamic_start() to set the start value, -so that they are allocated above the starting (enum) IDs. +Some standard IDs are reserved for certain purposes. These are defined by +`enum expo_id_t` and start at 1. `EXPOID_BASE_ID` defines the first ID which +can be used for an expo. + +An ID of 0 is invalid. If this is specified in an expo call then a valid +'dynamic IDs is allocated. Use expo_set_dynamic_start() to set the start +value, so that they are allocated above the starting (enum) IDs. All text strings are stored in a structure attached to the expo, referenced by a text ID. This makes it easier at some point to implement multiple languages or
@@ -417,8 +422,7 @@ strings are provided inline in the nodes where they are used. /* this comment is parsed by the expo.py tool to insert the values below enum { - ZERO, - ID_PROMPT, + ID_PROMPT = EXPOID_BASE_ID, ID_SCENE1, ID_SCENE1_TITLE,
include/expo.h +20 -0
@@ -15,6 +15,26 @@ struct udevice;#include <cli.h> +/** +* enum expo_id_t - standard expo IDs +* +* These are assumed to be in use at all times. Expos should use IDs starting +* from EXPOID_BASE_ID, +* +* @EXPOID_NONE: Not used, invalid ID 0 +* @EXPOID_SAVE: User has requested that the expo data be saved +* @EXPOID_DISCARD: User has requested that the expo data be discarded +* @EXPOID_BASE_ID: First ID which can be used for expo objects +*/ +enum expo_id_t { +EXPOID_NONE , + +EXPOID_SAVE , +EXPOID_DISCARD , + +EXPOID_BASE_ID =5 , +}; +/** * enum expoact_type - types of actions reported by the expo *
include/test/cedit-test.h +15 -15
@@ -9,24 +9,24 @@#ifndef __cedit_test_h#define __cedit_test_h -#define ID_PROMPT 1 -#define ID_SCENE1 2 -#define ID_SCENE1_TITLE 3 +#define ID_PROMPT 5 +#define ID_SCENE1 6 +#define ID_SCENE1_TITLE 7 -#define ID_CPU_SPEED 4 -#define ID_CPU_SPEED_TITLE 5 -#define ID_CPU_SPEED_1 6 -#define ID_CPU_SPEED_2 7 -#define ID_CPU_SPEED_3 8 +#define ID_CPU_SPEED 8 +#define ID_CPU_SPEED_TITLE 9 +#define ID_CPU_SPEED_1 10 +#define ID_CPU_SPEED_2 11 +#define ID_CPU_SPEED_3 12 -#define ID_POWER_LOSS 9 -#define ID_AC_OFF 10 -#define ID_AC_ON 11 -#define ID_AC_MEMORY 12 +#define ID_POWER_LOSS 13 +#define ID_AC_OFF 14 +#define ID_AC_ON 15 +#define ID_AC_MEMORY 16 -#define ID_MACHINE_NAME 13 -#define ID_MACHINE_NAME_EDIT 14 +#define ID_MACHINE_NAME 17 +#define ID_MACHINE_NAME_EDIT 18 -#define ID_DYNAMIC_START 15 +#define ID_DYNAMIC_START 19#endif
test/boot/cedit.c +8 -6
@@ -31,9 +31,11 @@ static int cedit_base(struct unit_test_state *uts)* ^N Move down to second item * ^M Select item * \e Quit +* +* cedit_run() returns -EACCESS so this command returns CMD_RET_FAILURE */ console_in_puts ("\x0e\x0d\x0e\x0d\e" ); -ut_assertok (run_command ("cedit run" ,0 )); +ut_asserteq (1 ,run_command ("cedit run" ,0 )); exp = cur_exp; scn =expo_lookup_scene_id (exp, exp->scene_id);
@@ -147,14 +149,14 @@ static int cedit_env(struct unit_test_state *uts)strcpy (str,"my-machine" );ut_assertok (run_command ("cedit write_env -v" ,0 )); -ut_assert_nextlinen ("c.cpu-speed=7" ); +ut_assert_nextlinen ("c.cpu-speed=11" );ut_assert_nextlinen ("c.cpu-speed-str=2.5 GHz" ); -ut_assert_nextlinen ("c.power-loss=10" ); +ut_assert_nextlinen ("c.power-loss=14" );ut_assert_nextlinen ("c.power-loss-str=Always Off" );ut_assert_nextlinen ("c.machine-name=my-machine" );ut_assert_console_end (); -ut_asserteq (7 ,env_get_ulong ("c.cpu-speed" ,10 ,0 )); +ut_asserteq (11 ,env_get_ulong ("c.cpu-speed" ,10 ,0 ));ut_asserteq_str ("2.5 GHz" ,env_get ("c.cpu-speed-str" ));ut_asserteq_str ("my-machine" ,env_get ("c.machine-name" ));
@@ -163,8 +165,8 @@ static int cedit_env(struct unit_test_state *uts) *str ='\0' ;ut_assertok (run_command ("cedit read_env -v" ,0 )); -ut_assert_nextlinen ("c.cpu-speed=7" ); -ut_assert_nextlinen ("c.power-loss=10" ); +ut_assert_nextlinen ("c.cpu-speed=11" ); +ut_assert_nextlinen ("c.power-loss=14" );ut_assert_nextlinen ("c.machine-name=my-machine" );ut_assert_console_end ();
test/boot/expo.c +4 -4
@@ -91,7 +91,7 @@ static int expo_base(struct unit_test_state *uts) *name ='\0' ;ut_assertnonnull (exp);ut_asserteq (0 , exp->scene_id); -ut_asserteq (1 , exp->next_id); +ut_asserteq (EXPOID_BASE_ID , exp->next_id);/* Make sure the name was allocated */ ut_assertnonnull (exp->name);
@@ -130,7 +130,7 @@ static int expo_scene(struct unit_test_state *uts)ut_assertok (expo_new (EXPO_NAME ,NULL , &exp)); scn =NULL ; -ut_asserteq (1 , exp->next_id); +ut_asserteq (EXPOID_BASE_ID , exp->next_id);strcpy (name,SCENE_NAME1 ); id =scene_new (exp, name,SCENE1 , &scn); *name ='\0' ;
@@ -176,11 +176,11 @@ static int expo_scene_no_id(struct unit_test_state *uts)int id;ut_assertok (expo_new (EXPO_NAME ,NULL , &exp)); -ut_asserteq (1 , exp->next_id); +ut_asserteq (EXPOID_BASE_ID , exp->next_id);strcpy (name,SCENE_NAME1 ); id =scene_new (exp,SCENE_NAME1 ,0 , &scn); -ut_asserteq (1 , scn->id); +ut_asserteq (EXPOID_BASE_ID , scn->id);return 0 ; }
test/boot/files/expo_ids.h +1 -2
@@ -4,8 +4,7 @@*/ enum { -ZERO , -ID_PROMPT , +ID_PROMPT =EXPOID_BASE_ID ,ID_SCENE1 ,ID_SCENE1_TITLE ,
tools/expo.py +28 -5
@@ -20,17 +20,22 @@ from u_boot_pylib import tools # Parse: # SCENE1 = 7, +# or SCENE1 = EXPOID_BASE_ID, # or SCENE2, -RE_ENUM = re.compile(r'(\S*)(\s*= (\d))?,') +RE_ENUM = re.compile(r'(\S*)(\s*= ([0-9A-Z_]+))?,') # Parse #define <name> "string" RE_DEF = re.compile(r'#define (\S*)\s*"(.*)"') -def calc_ids(fname): +# Parse EXPOID_BASE_ID = 5, +RE_BASE_ID = re.compile(r'\s*EXPOID_BASE_ID\s*= (\d+),') + +def calc_ids(fname, base_id): """Figure out the value of the enums in a C file Args: fname (str): Filename to parse + base_id (int): Base ID (value of EXPOID_BASE_ID) Returns: OrderedDict():
@@ -55,8 +60,12 @@ def calc_ids(fname): if not line or line.startswith('/*'): continue m_enum = RE_ENUM.match(line) - if m_enum.group(3): - cur_id = int(m_enum.group(3)) + enum_name = m_enum.group(3) + if enum_name: + if enum_name == 'EXPOID_BASE_ID': + cur_id = base_id + else: + cur_id = int(enum_name) vals[m_enum.group(1)] = cur_id cur_id += 1 else:
@@ -67,10 +76,24 @@ def calc_ids(fname): return vals +def find_base_id(): + fname = 'include/expo.h' + base_id = None + with open(fname, 'r', encoding='utf-8') as inf: + for line in inf.readlines(): + m_base_id = RE_BASE_ID.match(line) + if m_base_id: + base_id = int(m_base_id.group(1)) + if base_id is None: + raise ValueError('EXPOID_BASE_ID not found in expo.h') + #print(f'EXPOID_BASE_ID={base_id}') + return base_id + def run_expo(args): """Run the expo program""" + base_id = find_base_id() fname = args.enum_fname or args.layout - ids = calc_ids(fname) + ids = calc_ids(fname, base_id) if not ids: print(f"Warning: No enum ID values found in file '{fname}'")
Signature · 1 line
2.34.1
Re: [PATCH v3 05/20] expo: Use standard numbering for save and discard
Set aside some expo IDs for 'save' and 'discard' buttons. This avoids needing to store the IDs for these. Adjust the documentation and expo tool for the new EXPOID_BASE_ID value.
Ignore these objects when saving and loading the cedit, since they do not contain real data.
Adjust 'cedit run' to return failure when the user exits the expo without saving. Update the test for this change as well.
---
(no changes since v1)
boot/cedit.c | 24 +++++++++++++++++++++--- boot/expo.c | 2 +- doc/develop/cedit.rst | 7 ++++++- doc/develop/expo.rst | 12 ++++++++---- include/expo.h | 20 ++++++++++++++++++++ include/test/cedit-test.h | 30 +++++++++++++++--------------- test/boot/cedit.c | 14 ++++++++------ test/boot/expo.c | 8 ++++---- test/boot/files/expo_ids.h | 3 +-- tools/expo.py | 33 ++++++++++++++++++++++++++++----- 10 files changed, 112 insertions(+), 41 deletions(-)
Applied to u-boot-dm, thanks!
PATCH v3 6/20 expo: Allow menu items to have values
In reply to Simon GlassAt present menu items are stored according to their sequence number in the menu. In some cases we may want to have holes in that sequence, or not use a sequence at all.
Add a new 'value' property for menu items. This will be used for reading and writing, if present. If there is no 'value' property, then the normal sequence number will be used instead.
---
(no changes since v1)
arch/sandbox/dts/cedit.dtsi | 3 +++ boot/expo_build.c | 16 ++++++++++++---- boot/scene_internal.h | 10 ++++++++++ boot/scene_menu.c | 17 +++++++++++++++++ doc/develop/expo.rst | 10 ++++++++++ include/expo.h | 2 ++ test/boot/expo.c | 1 + test/boot/files/expo_layout.dts | 3 +++ 8 files changed, 58 insertions(+), 4 deletions(-)
arch/sandbox/dts/cedit.dtsi +3 -0
@@ -39,6 +39,9 @@ /* IDs for the menu items */ item-id = <ID_CPU_SPEED_1 ID_CPU_SPEED_2 ID_CPU_SPEED_3>; + + /* values for the menu items */ + item-value = <0 3 6>; }; power-loss {
boot/expo_build.c +12 -4
@@ -227,10 +227,10 @@ static void list_strings(struct build_info *info)static int menu_build (struct build_info *info,ofnode node,struct scene *scn,uint id,struct scene_obj **objp) { +const u32 *item_ids, *item_values;struct scene_obj_menu *menu; +int ret, size, i, num_items;uint title_id, menu_id; -const u32 *item_ids; -int ret, size, i;const char *name; name =ofnode_get_name (node);
@@ -254,9 +254,15 @@ static int menu_build(struct build_info *info, ofnode node, struct scene *scn,return log_msg_ret ("itm" , -EINVAL );if (!size || size %sizeof (u32))return log_msg_ret ("isz" , -EINVAL ); - size /=sizeof (u32); + num_items = size /sizeof (u32); -for (i =0 ; i < size; i++) { + item_values =ofnode_read_prop (node,"item-value" , &size); +if (item_values) { +if (size != num_items *sizeof (u32)) +return log_msg_ret ("vsz" , -EINVAL ); + } + +for (i =0 ; i < num_items; i++) {struct scene_menitem *item;uint label, key, desc;
@@ -280,6 +286,8 @@ static int menu_build(struct build_info *info, ofnode node, struct scene *scn, desc, 0, 0, &item);if (ret <0 )return log_msg_ret ("mi" , ret); +if (item_values) + item->value =fdt32_to_cpu (item_values[i]); } *objp = &menu->obj;
boot/scene_internal.h +10 -0
@@ -281,6 +281,16 @@ struct scene_menitem *scene_menuitem_find(const struct scene_obj_menu *menu,struct scene_menitem *scene_menuitem_find_seq (const struct scene_obj_menu *menu,uint seq); +/** +* scene_menuitem_find_val() - Find the menu item with a given value +* +* @menu: Menu to check +* @find_val: Value to look for +* Return: menu item if found, else NULL +*/ +struct scene_menitem *scene_menuitem_find_val (const struct scene_obj_menu *menu, +int val); +/** * scene_bbox_union() - update bouding box with the demensions of an object *
boot/scene_menu.c +17 -0
@@ -61,6 +61,22 @@ struct scene_menitem *scene_menuitem_find_seq(const struct scene_obj_menu *menu,return NULL ; } +struct scene_menitem *scene_menuitem_find_val (const struct scene_obj_menu *menu, +int val) +{ +struct scene_menitem *item; +uint i; + + i =0 ; +list_for_each_entry (item, &menu->item_head, sibling) { +if (item->value == val) +return item; + i++; + } + +return NULL ; +} +/** * update_pointers() - Update the pointer object and handle highlights *
@@ -416,6 +432,7 @@ int scene_menuitem(struct scene *scn, uint menu_id, const char *name, uint id, item->desc_id = desc_id; item->preview_id = preview_id; item->flags = flags; + item->value =INT_MAX ;list_add_tail (&item->sibling, &menu->item_head);if (itemp)
doc/develop/expo.rst +10 -0
@@ -361,6 +361,13 @@ item-id Specifies the ID for each menu item. These are used for checking which item has been selected. +item-value + type: u32 list, optional + + Specifies the value for each menu item. These are used for saving and + loading. If this is omitted the value is its position in the menu (0..n-1). + Valid values are positive and negative integers INT_MIN...(INT_MAX - 1). + item-label / item-label-id type: string list / u32 list, required
@@ -474,6 +481,9 @@ strings are provided inline in the nodes where they are used. /* IDs for the menu items */ item-id = <ID_CPU_SPEED_1 ID_CPU_SPEED_2 ID_CPU_SPEED_3>; + + /* values for the menu items */ + item-value = <(-1) 3 6>; }; power-loss {
include/expo.h +2 -0
@@ -330,6 +330,7 @@ enum scene_menuitem_flags_t {* @desc_id: ID of text object to use as the description text * @preview_id: ID of the preview object, or 0 if none * @flags: Flags for this item +* @value: Value for this item, or INT_MAX to use sequence * @sibling: Node to link this item to its siblings */ struct scene_menitem {
@@ -340,6 +341,7 @@ struct scene_menitem {uint desc_id;uint preview_id;uint flags; +int value;struct list_head sibling; };
test/boot/expo.c +1 -0
@@ -717,6 +717,7 @@ static int expo_test_build(struct unit_test_state *uts)ut_asserteq (0 , item->desc_id);ut_asserteq (0 , item->preview_id);ut_asserteq (0 , item->flags); +ut_asserteq (0 , item->value); txt =scene_obj_find (scn, item->label_id,SCENEOBJT_NONE );ut_asserteq_str ("2 GHz" ,expo_get_str (exp, txt->str_id));
test/boot/files/expo_layout.dts +3 -0
@@ -39,6 +39,9 @@ item-id = <ID_CPU_SPEED_1 ID_CPU_SPEED_2 ID_CPU_SPEED_3>; + /* values for the menu items */ + item-value = <(-1) 3 6>; + start-bit = <0x400>; bit-length = <2>; };
Signature · 1 line
2.34.1
Re: [PATCH v3 06/20] expo: Allow menu items to have values
At present menu items are stored according to their sequence number in the menu. In some cases we may want to have holes in that sequence, or not use a sequence at all.
Add a new 'value' property for menu items. This will be used for reading and writing, if present. If there is no 'value' property, then the normal sequence number will be used instead.
---
(no changes since v1)
arch/sandbox/dts/cedit.dtsi | 3 +++ boot/expo_build.c | 16 ++++++++++++---- boot/scene_internal.h | 10 ++++++++++ boot/scene_menu.c | 17 +++++++++++++++++ doc/develop/expo.rst | 10 ++++++++++ include/expo.h | 2 ++ test/boot/expo.c | 1 + test/boot/files/expo_layout.dts | 3 +++ 8 files changed, 58 insertions(+), 4 deletions(-)
Applied to u-boot-dm, thanks!
PATCH v3 7/20 expo: Add a little more cedit CMOS logging
In reply to Simon GlassAdd some more logging in the CMOS read/write code. Tidy up a few comments while we are here.
---
(no changes since v1)
boot/cedit.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)
boot/cedit.c +4 -2
@@ -584,7 +584,7 @@ static int h_read_settings_env(struct scene_obj *obj, void *vpriv)/* * note that no validation is done here, to make sure the ID is -* valid * and actually points to a menu item +* valid and actually points to a menu item */ menu->cur_item_id = val;break ;
@@ -718,6 +718,7 @@ int cedit_write_settings_cmos(struct expo *exp, struct udevice *dev, }/* write the data to the RTC */ +log_debug ("Writing CMOS\n" ); first =CMOS_MAX_BYTES ; last =-1 ;for (i =0 , count =0 ; i <CMOS_MAX_BYTES ; i++) {
@@ -785,6 +786,7 @@ static int h_read_settings_cmos(struct scene_obj *obj, void *vpriv) }/* update the current item */ +log_debug ("look for menuitem value %d in menu %d\n" , val, menu->obj.id); mi =scene_menuitem_find_seq (menu, val);if (!mi)return log_msg_ret ("seq" , -ENOENT );
@@ -819,7 +821,7 @@ int cedit_read_settings_cmos(struct expo *exp, struct udevice *dev, goto done; } -/* read the data to the RTC */ +/* indicate what bytes were read from the RTC */ first =CMOS_MAX_BYTES ; last =-1 ;for (i =0 , count =0 ; i <CMOS_MAX_BYTES ; i++) {
Signature · 1 line
2.34.1
Re: [PATCH v3 07/20] expo: Add a little more cedit CMOS logging
Add some more logging in the CMOS read/write code. Tidy up a few comments while we are here.
---
(no changes since v1)
boot/cedit.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)
Applied to u-boot-dm, thanks!
PATCH v3 8/20 expo: Support menu-item values in cedit
In reply to Simon GlassUpdate the cedit read/write functions to support menu items with values.
---
(no changes since v1)
boot/cedit.c | 148 +++++++++++++++++++++----------- boot/scene_menu.c | 2 +- doc/usage/cmd/cedit.rst | 15 +++- test/boot/cedit.c | 8 +- test/boot/files/expo_layout.dts | 4 +- 5 files changed, 117 insertions(+), 60 deletions(-)
boot/cedit.c +96 -52
@@ -293,11 +293,49 @@ static int get_cur_menuitem_text(const struct scene_obj_menu *menu,return 0 ; } +/** +* get_cur_menuitem_val() - Get the value of a menu's current item +* +* Obtains the value of the current item in the menu. If no value, then +* enumerates the items of a menu (0, 1, 2) and returns the sequence number of +* the currently selected item. If the first item is selected, this returns 0; +* if the second, 1; etc. +* +* @menu: Menu to check +* @valp: Returns current-item value / sequence number +* Return: 0 on success, else -ve error value +*/ +static int get_cur_menuitem_val (const struct scene_obj_menu *menu,int *valp) +{ +const struct scene_menitem *mi; +int seq; + + seq =0 ; +list_for_each_entry (mi, &menu->item_head, sibling) { +if (mi->id == menu->cur_item_id) { + *valp = mi->value ==INT_MAX ? seq : mi->value; +return 0 ; + } + seq++; + } + +return log_msg_ret ("nf" , -ENOENT ); +} + +/** +* write_dt_string() - Write a string to the devicetree, expanding if needed +* +* If this fails, it tries again after expanding the devicetree a little +* +* @buf: Buffer containing the devicetree +* @name: Property name to use +* @str: String value +* Return: 0 if OK, -EFAULT if something went horribly wrong +*/ static int write_dt_string (struct abuf *buf,const char *name,const char *str) {int ret, i; -/* write the text of the current item */ ret = -EAGAIN ;for (i =0 ; ret && i <2 ; i++) { ret =fdt_property_string (abuf_data (buf), name, str);
@@ -315,6 +353,38 @@ static int write_dt_string(struct abuf *buf, const char *name, const char *str)return 0 ; } +/** +* write_dt_u32() - Write an int to the devicetree, expanding if needed +* +* If this fails, it tries again after expanding the devicetree a little +* +* @buf: Buffer containing the devicetree +* @name: Property name to use +* @lva: Integer value +* Return: 0 if OK, -EFAULT if something went horribly wrong +*/ +static int write_dt_u32 (struct abuf *buf,const char *name,uint val) +{ +int ret, i; + +/* write the text of the current item */ + ret = -EAGAIN ; +for (i =0 ; ret && i <2 ; i++) { + ret =fdt_property_u32 (abuf_data (buf), name, val); +if (!i) { + ret =check_space (ret, buf); +if (ret) +return log_msg_ret ("rs2" , -ENOMEM ); + } + } + +/* this should not happen */ +if (ret) +return log_msg_ret ("str" , -EFAULT ); + +return 0 ; +} +static int h_write_settings (struct scene_obj *obj,void *vpriv) {struct cedit_iter_priv *priv = vpriv;
@@ -339,23 +409,21 @@ static int h_write_settings(struct scene_obj *obj, void *vpriv)const struct scene_obj_menu *menu;const char *str;char name[80 ]; -int i; +int val;/* write the ID of the current item */ menu = (struct scene_obj_menu *)obj; - ret = -EAGAIN ; -for (i =0 ; ret && i <2 ; i++) { - ret =fdt_property_u32 (abuf_data (buf), obj->name, - menu->cur_item_id); -if (!i) { - ret =check_space (ret, buf); -if (ret) -return log_msg_ret ("res" , -ENOMEM ); - } - } -/* this should not happen */ + ret =write_dt_u32 (buf, obj->name, menu->cur_item_id);if (ret) -return log_msg_ret ("wrt" , -EFAULT ); +return log_msg_ret ("wrt" , ret); + +snprintf (name,sizeof (name),"%s-value" , obj->name); + ret =get_cur_menuitem_val (menu, &val); +if (ret <0 ) +return log_msg_ret ("cur" , ret); + ret =write_dt_u32 (buf, name, val); +if (ret) +return log_msg_ret ("wr2" , ret); ret =get_cur_menuitem_text (menu, &str);if (ret)
@@ -521,6 +589,14 @@ static int h_write_settings_env(struct scene_obj *obj, void *vpriv) ret =env_set (name, str);if (ret)return log_msg_ret ("st2" , ret); + + ret =get_cur_menuitem_val (menu, &val); +if (ret <0 ) +return log_msg_ret ("cur" , ret); +snprintf (name,sizeof (name),"c.%s-value" , obj->name); +if (priv->verbose) +printf ("%s=%d\n" , name, val); +break ;case SCENEOBJT_TEXTLINE : {const struct scene_obj_textline *tline;
@@ -624,43 +700,12 @@ int cedit_read_settings_env(struct expo *exp, bool verbose)return 0 ; } -/** -* get_cur_menuitem_seq() - Get the sequence number of a menu's current item -* -* Enumerates the items of a menu (0, 1, 2) and returns the sequence number of -* the currently selected item. If the first item is selected, this returns 0; -* if the second, 1; etc. -* -* @menu: Menu to check -* Return: Sequence number on success, else -ve error value -*/ -static int get_cur_menuitem_seq (const struct scene_obj_menu *menu) -{ -const struct scene_menitem *mi; -int seq, found; - - seq =0 ; - found =-1 ; -list_for_each_entry (mi, &menu->item_head, sibling) { -if (mi->id == menu->cur_item_id) { - found = seq; -break ; - } - seq++; - } - -if (found ==-1 ) -return log_msg_ret ("nf" , -ENOENT ); - -return found; -} -static int h_write_settings_cmos (struct scene_obj *obj,void *vpriv) {const struct scene_obj_menu *menu;struct cedit_iter_priv *priv = vpriv;int val, ret; -uint i, seq; +uint i;if (obj->type !=SCENEOBJT_MENU || obj->id <EXPOID_BASE_ID )return 0 ;
@@ -668,11 +713,10 @@ static int h_write_settings_cmos(struct scene_obj *obj, void *vpriv) menu = (struct scene_obj_menu *)obj; val = menu->cur_item_id; - ret =get_cur_menuitem_seq (menu); + ret =get_cur_menuitem_val (menu, &val);if (ret <0 )return log_msg_ret ("cur" , ret); - seq = ret; -log_debug ("%s: seq=%d\n" , menu->obj.name, seq); +log_debug ("%s: val=%d\n" , menu->obj.name, val);/* figure out where to place this item */ if (!obj->bit_length)
@@ -680,11 +724,11 @@ static int h_write_settings_cmos(struct scene_obj *obj, void *vpriv)if (obj->start_bit + obj->bit_length >CMOS_MAX_BITS )return log_msg_ret ("bit" , -E2BIG ); -for (i =0 ; i < obj->bit_length; i++, seq >>=1 ) { +for (i =0 ; i < obj->bit_length; i++, val >>=1 ) {uint bitnum = obj->start_bit + i; priv->mask[CMOS_BYTE (bitnum)] |=1 <<CMOS_BIT (bitnum); -if (seq &1 ) +if (val &1 ) priv->value[CMOS_BYTE (bitnum)] |=BIT (CMOS_BIT (bitnum)); log_debug("bit %x %x %x\n", bitnum, priv->mask[CMOS_BYTE(bitnum)],
@@ -787,7 +831,7 @@ static int h_read_settings_cmos(struct scene_obj *obj, void *vpriv)/* update the current item */ log_debug ("look for menuitem value %d in menu %d\n" , val, menu->obj.id); - mi =scene_menuitem_find_seq (menu, val); + mi =scene_menuitem_find_val (menu, val);if (!mi)return log_msg_ret ("seq" , -ENOENT );
boot/scene_menu.c +1 -1
@@ -69,7 +69,7 @@ struct scene_menitem *scene_menuitem_find_val(const struct scene_obj_menu *menu, i =0 ;list_for_each_entry (item, &menu->item_head, sibling) { -if (item->value == val) +if (item->value ==INT_MAX ? val == i : item->value == val)return item; i++; }
doc/usage/cmd/cedit.rst +12 -3
@@ -107,8 +107,10 @@ That results in:: / { cedit-values { cpu-speed = <0x00000006>; + cpu-speed-value = <0x00000003>; cpu-speed-str = "2 GHz"; power-loss = <0x0000000a>; + power-loss-value = <0x00000000>; power-loss-str = "Always Off"; }; }
@@ -118,16 +120,23 @@ That results in:: This shows settings being stored in the environment:: => cedit write_env -v - c.cpu-speed=7 + c.cpu-speed=11 c.cpu-speed-str=2.5 GHz - c.power-loss=12 - c.power-loss-str=Memory + c.cpu-speed-value=3 + c.power-loss=14 + c.power-loss-str=Always Off + c.power-loss-value=0 + c.machine-name=my-machine + c.cpu-speed=11 + c.power-loss=14 + c.machine-name=my-machine => print ... c.cpu-speed=6 c.cpu-speed-str=2 GHz c.power-loss=10 c.power-loss-str=Always Off + c.machine-name=my-machine ... => cedit read_env -v
test/boot/cedit.c +6 -2
@@ -96,14 +96,16 @@ static int cedit_fdt(struct unit_test_state *uts)ut_asserteq (ID_CPU_SPEED_2 ,ofnode_read_u32_default (node,"cpu-speed" ,0 )); +ut_asserteq (3 , +ofnode_read_u32_default (node,"cpu-speed-value" ,0 ));ut_asserteq_str ("2.5 GHz" ,ofnode_read_string (node,"cpu-speed-str" ));ut_asserteq_str ("my-machine" ,ofnode_read_string (node,"machine-name" )); -/* There should only be 5 properties */ +/* There should only be 7 properties */ for (i =0 ,ofnode_first_property (node, &prop);ofprop_valid (&prop); i++,ofnode_next_property (&prop)) ; -ut_asserteq (5 , i); +ut_asserteq (7 , i);ut_assert_console_end ();
@@ -151,8 +153,10 @@ static int cedit_env(struct unit_test_state *uts)ut_assertok (run_command ("cedit write_env -v" ,0 ));ut_assert_nextlinen ("c.cpu-speed=11" );ut_assert_nextlinen ("c.cpu-speed-str=2.5 GHz" ); +ut_assert_nextlinen ("c.cpu-speed-value=3" );ut_assert_nextlinen ("c.power-loss=14" );ut_assert_nextlinen ("c.power-loss-str=Always Off" ); +ut_assert_nextlinen ("c.power-loss-value=0" );ut_assert_nextlinen ("c.machine-name=my-machine" );ut_assert_console_end ();
test/boot/files/expo_layout.dts +2 -2
@@ -40,10 +40,10 @@ ID_CPU_SPEED_3>; /* values for the menu items */ - item-value = <(-1) 3 6>; + item-value = <0 3 6>; start-bit = <0x400>; - bit-length = <2>; + bit-length = <3>; }; power-loss {
Signature · 1 line
2.34.1
Re: [PATCH v3 08/20] expo: Support menu-item values in cedit
Update the cedit read/write functions to support menu items with values.
---
(no changes since v1)
boot/cedit.c | 148 +++++++++++++++++++++----------- boot/scene_menu.c | 2 +- doc/usage/cmd/cedit.rst | 15 +++- test/boot/cedit.c | 8 +- test/boot/files/expo_layout.dts | 4 +- 5 files changed, 117 insertions(+), 60 deletions(-)
Applied to u-boot-dm, thanks!
PATCH v3 9/20 expo: Drop unneceesary calls to expo_str()
In reply to Simon GlassThe scene_txt_str() function calls expo_str() so there is no need to call it beforehand. Drop this unnecessary code.
---
(no changes since v1)
boot/expo_build.c | 16 ++-------------- 1 file changed, 2 insertions(+), 14 deletions(-)
boot/expo_build.c +2 -14
@@ -46,7 +46,6 @@ int add_txt_str(struct build_info *info, ofnode node, struct scene *scn, const char *find_name, uint obj_id) {const char *text; -uint str_id;int ret; info->err_prop = find_name;
@@ -67,12 +66,7 @@ int add_txt_str(struct build_info *info, ofnode node, struct scene *scn,return log_msg_ret ("id" , -EINVAL ); } - ret =expo_str (scn->expo, find_name,0 , text); -if (ret <0 ) -return log_msg_ret ("add" , ret); - str_id = ret; - - ret =scene_txt_str (scn, find_name, obj_id, str_id, text,NULL ); + ret =scene_txt_str (scn, find_name, obj_id,0 , text,NULL );if (ret <0 )return log_msg_ret ("add" , ret);
@@ -94,7 +88,6 @@ int add_txt_str_list(struct build_info *info, ofnode node, struct scene *scn, const char *find_name, int index, uint obj_id) { const char *text; -uint str_id;int ret; ret =ofnode_read_string_index (node, find_name, index, &text);
@@ -114,12 +107,7 @@ int add_txt_str_list(struct build_info *info, ofnode node, struct scene *scn,return log_msg_ret ("id" , -EINVAL ); } - ret =expo_str (scn->expo, find_name,0 , text); -if (ret <0 ) -return log_msg_ret ("add" , ret); - str_id = ret; - - ret =scene_txt_str (scn, find_name, obj_id, str_id, text,NULL ); + ret =scene_txt_str (scn, find_name, obj_id,0 , text,NULL );if (ret <0 )return log_msg_ret ("add" , ret);
Signature · 1 line
2.34.1
Re: [PATCH v3 09/20] expo: Drop unneceesary calls to expo_str()
The scene_txt_str() function calls expo_str() so there is no need to call it beforehand. Drop this unnecessary code.
---
(no changes since v1)
boot/expo_build.c | 16 ++-------------- 1 file changed, 2 insertions(+), 14 deletions(-)
Applied to u-boot-dm, thanks!
PATCH v3 10/20 expo: Drop scene_title_set()
In reply to Simon GlassThis function is really just an assignment, so serves no useful purpose. Drop it.
---
(no changes since v1)
boot/expo_build.c | 4 ++-- boot/scene.c | 7 ------- include/expo.h | 9 --------- test/boot/expo.c | 2 +- 4 files changed, 3 insertions(+), 19 deletions(-)
boot/expo_build.c +2 -2
@@ -404,7 +404,7 @@ static int scene_build(struct build_info *info, ofnode scn_node,if (ret <0 )return log_msg_ret ("tit" , ret); title_id = ret; -scene_title_set (scn, title_id); + scn->title_id = title_id; ret =add_txt_str (info, scn_node, scn,"prompt" ,0 );if (ret <0 )
@@ -420,7 +420,7 @@ static int scene_build(struct build_info *info, ofnode scn_node,return 0 ; } -int build_it (struct build_info *info,ofnode root,struct expo **expp) +static int build_it (struct build_info *info,ofnode root,struct expo **expp) {ofnode scenes, node;struct expo *exp;
boot/scene.c +0 -7
@@ -70,13 +70,6 @@ void scene_destroy(struct scene *scn)free (scn); } -int scene_title_set (struct scene *scn,uint id) -{ - scn->title_id = id; - -return 0 ; -} -int scene_obj_count (struct scene *scn) {return list_count_nodes (&scn->obj_head);
include/expo.h +0 -9
@@ -540,15 +540,6 @@ void scene_set_highlight_id(struct scene *scn, uint id);*/ int scene_set_open (struct scene *scn,uint id,bool open); -/** -* scene_title_set() - set the scene title -* -* @scn: Scene to update -* @title_id: Title ID to set -* Returns: 0 if OK -*/ -int scene_title_set (struct scene *scn,uint title_id); -/** * scene_obj_count() - Count the number of objects in a scene *
test/boot/expo.c +1 -1
@@ -151,7 +151,7 @@ static int expo_scene(struct unit_test_state *uts) scn =NULL ; id =scene_new (exp,SCENE_NAME2 ,0 , &scn);ut_assertnonnull (scn); -ut_assertok (scene_title_set (scn, title_id)); + scn->title_id = title_id;ut_asserteq (STR_SCENE_TITLE +1 , id);ut_asserteq (STR_SCENE_TITLE +2 , exp->next_id);ut_asserteq_ptr (exp, scn->expo);
Signature · 1 line
2.34.1
Re: [PATCH v3 10/20] expo: Drop scene_title_set()
This function is really just an assignment, so serves no useful purpose. Drop it.
---
(no changes since v1)
boot/expo_build.c | 4 ++-- boot/scene.c | 7 ------- include/expo.h | 9 --------- test/boot/expo.c | 2 +- 4 files changed, 3 insertions(+), 19 deletions(-)
Applied to u-boot-dm, thanks!
PATCH v3 11/20 expo: Add forward declaration for udevice to cedit
In reply to Simon GlassSome files may include this header file without first including dm.h so add a forward declaration.
---
(no changes since v1)
include/cedit.h | 1 + 1 file changed, 1 insertion(+)
include/cedit.h +1 -0
@@ -14,6 +14,7 @@struct abuf ;struct expo ;struct scene ; +struct udevice ;struct video_priv ;struct udevice ;
Signature · 1 line
2.34.1
Re: [PATCH v3 11/20] expo: Add forward declaration for udevice to cedit
Some files may include this header file without first including dm.h so add a forward declaration.
---
(no changes since v1)
include/cedit.h | 1 + 1 file changed, 1 insertion(+)
Applied to u-boot-dm, thanks!
PATCH v3 12/20 x86: coreboot: Enable unit tests
In reply to Simon GlassEnable unit tests so we can run command-line tests in coreboot. Enable console recording, with enough space for the 'cbsysinfo' command. Add to the pre-relocation malloc() space to make room for this.
---
(no changes since v1)
configs/coreboot_defconfig | 4 ++++ 1 file changed, 4 insertions(+)
configs/coreboot_defconfig +4 -0
@@ -1,6 +1,7 @@ CONFIG_X86=y CONFIG_TEXT_BASE=0x1110000 CONFIG_SYS_MALLOC_LEN=0x2000000 +CONFIG_SYS_MALLOC_F_LEN=0x1000 CONFIG_NR_DRAM_BANKS=8 CONFIG_ENV_SIZE=0x1000 CONFIG_DEFAULT_DEVICE_TREE="coreboot"
@@ -15,6 +16,8 @@ CONFIG_SHOW_BOOT_PROGRESS=y CONFIG_USE_BOOTARGS=y CONFIG_BOOTARGS="root=/dev/sdb3 init=/sbin/init rootwait ro" CONFIG_BOOTCOMMAND="bootflow scan -l; if bootflow menu; then cls; bootflow boot; fi" +CONFIG_CONSOLE_RECORD=y +CONFIG_CONSOLE_RECORD_OUT_SIZE=0x1000 CONFIG_PRE_CONSOLE_BUFFER=y CONFIG_SYS_CONSOLE_INFO_QUIET=y CONFIG_LOG=y
@@ -59,3 +62,4 @@ CONFIG_CONSOLE_SCROLL_LINES=5 CONFIG_CMD_DHRYSTONE=y # CONFIG_GZIP is not set CONFIG_SMBIOS_PARSER=y +CONFIG_UNIT_TEST=y
Signature · 1 line
2.34.1
PATCH v3 13/20 docker: Update coreboot
In reply to Simon GlassUpdate to a newer version which supports settings in CMOS RAM and linear framebuffer.
---
Changes in v3:
- Update Dockerfile instead
tools/docker/Dockerfile | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-)
tools/docker/Dockerfile +5 -2
@@ -244,12 +244,15 @@ RUN mkdir /tmp/trace && \ rm -rf /tmp/trace # Build coreboot -RUN wget -O - https://coreboot.org/releases/coreboot-4.22.01.tar.xz | tar -C /tmp -xJ && \ - cd /tmp/coreboot-4.22.01 && \ +RUN wget -O - https://coreboot.org/releases/coreboot-24.08.tar.xz | tar -C /tmp -xJ && \ + cd /tmp/coreboot-24.08 && \ make crossgcc-i386 CPUS=$(nproc) && \ make -C payloads/coreinfo olddefconfig && \ make -C payloads/coreinfo && \ make olddefconfig && \ + echo CONFIG_GENERIC_LINEAR_FRAMEBUFFER=y | tee -a .config && \ + echo CONFIG_USE_OPTION_TABLE=y | tee -a .config && \ + make olddefconfig && \ make -j $(nproc) && \ sudo mkdir /opt/coreboot && \ sudo cp build/coreboot.rom build/cbfstool /opt/coreboot/
Signature · 1 line
2.34.1
Re: [PATCH v3 13/20] docker: Update coreboot
Quoted 4 lines · Simon Glass
Update to a newer version which supports settings in CMOS RAM and linear framebuffer.
Signed-off-by Simon Glass <[email protected]>
Signature · 1 line
Tom
Simon Glass
Reviewed-by Tom RiniRe: [PATCH v3 13/20] docker: Update coreboot
Quoted 4 lines · Simon Glass
Update to a newer version which supports settings in CMOS RAM and linear framebuffer.
Signed-off-by Simon Glass <[email protected]>
Signature · 3 lines
Tom Applied to u-boot-dm, thanks!
PATCH v3 14/20 doc: Update coreboot's CI information
In reply to Simon GlassThis is in the Dockerfile now, so update this section of the docs.
---
(no changes since v1)
doc/board/coreboot/coreboot.rst | 14 +------------- 1 file changed, 1 insertion(+), 13 deletions(-)
doc/board/coreboot/coreboot.rst +1 -13
@@ -181,16 +181,4 @@ coreboot in CI CI runs tests using a pre-built coreboot image. This ensures that U-Boot can boot as a coreboot payload, based on a known-good build of coreboot. -To update the `coreboot.rom` file which is used: - -#. Build coreboot with `CONFIG_GENERIC_LINEAR_FRAMEBUFFER=y`. If using - `make menuconfig`, this is under - `Devices->Display->Framebuffer mode->Linear "high resolution" framebuffer`. - -#. Compress the resulting `coreboot.rom`:: - - xz -c /path/to/coreboot/build/coreboot.rom > coreboot.rom.xz - -#. Upload the file to Google drive - -#. Send a patch to change the file ID used by wget in the CI yaml files. +To update the `coreboot.rom` file which is used, see ``tools/Dockerfile``
Signature · 1 line
2.34.1
Re: [PATCH v3 14/20] doc: Update coreboot's CI information
This is in the Dockerfile now, so update this section of the docs.
---
(no changes since v1)
doc/board/coreboot/coreboot.rst | 14 +------------- 1 file changed, 1 insertion(+), 13 deletions(-)
Applied to u-boot-dm, thanks!
PATCH v3 15/20 x86: coreboot: Add a test for cbsysinfo command
In reply to Simon GlassAdd a simple test for this command, checking that coreboot has the required features.
---
(no changes since v1)
test/cmd/Makefile | 1 + test/cmd/coreboot.c | 36 ++++++++++++++++++++++++++++++++++++ 2 files changed, 37 insertions(+) create mode 100644 test/cmd/coreboot.c
test/cmd/Makefile +1 -0
@@ -14,6 +14,7 @@ endif obj-y += exit.o mem.o obj-$(CONFIG_CMD_ADDRMAP) += addrmap.o obj-$(CONFIG_CMD_BDI) += bdinfo.o +obj-$(CONFIG_COREBOOT_SYSINFO) += coreboot.o obj-$(CONFIG_CMD_FDT) += fdt.o obj-$(CONFIG_CONSOLE_TRUETYPE) += font.o obj-$(CONFIG_CMD_HISTORY) += history.o
test/cmd/coreboot.c new file +36 -0
@@ -0,0 +1,36 @@ +// SPDX-License-Identifier: GPL-2.0+ +/* +* Test for coreboot commands +* +* Copyright 2023 Google LLC +* Written by Simon Glass <[email protected]> +*/ + +#include <command.h> +#include <test/cmd.h> +#include <test/test.h> +#include <test/ut.h> + +/** +* test_cmd_cbsysinfo() - test the cbsysinfo command produces expected output +* +* This includes ensuring that the coreboot build has the expected options +* enabled +*/ +static int test_cmd_cbsysinfo (struct unit_test_state *uts) +{ +ut_assertok (run_command ("cbsysinfo" ,0 )); +ut_assert_nextlinen ("Coreboot table at" ); + +/* Make sure the linear frame buffer is enabled */ +ut_assert_skip_to_linen ("Framebuffer" ); +ut_assert_nextlinen (" Phys addr" ); + +ut_assert_skip_to_line ("Chrome OS VPD: 00000000" ); +ut_assert_nextlinen ("RSDP" ); +ut_assert_nextlinen ("Unimpl." ); +ut_assert_console_end (); + +return 0 ; +} +CMD_TEST (test_cmd_cbsysinfo,UTF_CONSOLE );
Signature · 1 line
2.34.1
PATCH v3 16/20 x86: coreboot: Show the option table
In reply to Simon GlassUpdate the cbsysinfo command to show the contents of the CMOS option table.
While we are here, add some example output for this command, along with mention of what the unimplemented tags are.
---
(no changes since v1)
cmd/x86/cbsysinfo.c | 73 ++++++++++++++++++++++++++- doc/usage/cmd/cbsysinfo.rst | 99 +++++++++++++++++++++++++++++++++++++ test/cmd/coreboot.c | 7 +++ 3 files changed, 178 insertions(+), 1 deletion(-)
cmd/x86/cbsysinfo.c +72 -1
@@ -184,6 +184,77 @@ static const char *timestamp_name(uint32_t id)return "<unknown>" ; } +static void show_option_vals (const struct cb_cmos_option_table *tab, +uint id) +{ +const void *ptr, *end; +bool found = false; + + end = (void *)tab + tab->size; +for (ptr = (void *)tab + tab->header_length; ptr < end;) { +const struct cb_record *rec = ptr; + +switch (rec->tag) { +case CB_TAG_OPTION_ENUM : { +const struct cb_cmos_enums *enums = ptr; + +if (enums->config_id == id) { +if (!found) +printf (" " ); +printf (" %d:%s" , enums->value, enums->text); + found = true; + } +break ; + } +break ; +case CB_TAG_OPTION_DEFAULTS : +case CB_TAG_OPTION_CHECKSUM : +case CB_TAG_OPTION : +break ; +default : +printf ("tag %x\n" , rec->tag); +break ; + } + ptr += rec->size; + } +} + +static void show_option_table (const struct cb_cmos_option_table *tab) +{ +const void *ptr, *end; + +print_ptr ("option_table" , tab); +if (!tab->size) +return ; + +printf (" Bit Len Cfg ID Name\n" ); + end = (void *)tab + tab->size; +for (ptr = (void *)tab + tab->header_length; ptr < end;) { +const struct cb_record *rec = ptr; + +switch (rec->tag) { +case CB_TAG_OPTION : { +const struct cb_cmos_entries *entry = ptr; + +printf ("%4x %4x %3c %3x %-20s" , entry->bit, + entry->length, entry->config, entry->config_id, + entry->name); +show_option_vals (tab, entry->config_id); +printf ("\n" ); +break ; + } +case CB_TAG_OPTION_ENUM : +case CB_TAG_OPTION_DEFAULTS : +case CB_TAG_OPTION_CHECKSUM : +break ; +default : +printf ("tag %x\n" , rec->tag); +break ; + } + ptr += rec->size; + } +} +static void show_table (struct sysinfo_t *info,bool verbose) {struct cb_serial *ser = info->serial;
@@ -218,7 +289,7 @@ static void show_table(struct sysinfo_t *info, bool verbose)printf ("%12d: %02x:%-8s %016llx %016llx\n" , i, mr->type,get_mem_name (mr->type), mr->base, mr->size); } -print_ptr ("option_table" , info->option_table); +show_option_table (info->option_table);print_hex ("CMOS start" , info->cmos_range_start);if (info->cmos_range_start) {
doc/usage/cmd/cbsysinfo.rst +99 -0
102 lines not on this page · raw message
test/cmd/coreboot.c +7 -0
@@ -22,6 +22,13 @@ static int test_cmd_cbsysinfo(struct unit_test_state *uts)ut_assertok (run_command ("cbsysinfo" ,0 ));ut_assert_nextlinen ("Coreboot table at" ); +/* Make sure CMOS options are enabled */ +ut_assert_skip_to_line ( +" 1c0 1 e 1 power_on_after_fail 0:Disable 1:Enable" ); +ut_assert_skip_to_line ("CMOS start : 1c0" ); +ut_assert_nextline (" CMOS end : 1cf" ); +ut_assert_nextline (" CMOS csum loc: 3f0" ); +/* Make sure the linear frame buffer is enabled */ ut_assert_skip_to_linen ("Framebuffer" );ut_assert_nextlinen (" Phys addr" );
Signature · 1 line
2.34.1
PATCH v3 17/20 x86: coreboot: Enable support for the configuration editor
In reply to Simon GlassEnable cedit support along with required options and a simple style.
---
(no changes since v1)
arch/x86/dts/coreboot.dts | 7 +++++++ configs/coreboot64_defconfig | 2 ++ configs/coreboot_defconfig | 2 ++ 3 files changed, 11 insertions(+)
arch/x86/dts/coreboot.dts +7 -0
@@ -54,6 +54,13 @@ menu-inset = <3>; menuitem-gap-y = <1>; }; + + cedit-theme { + font-size = <30>; + menu-inset = <3>; + menuitem-gap-y = <1>; + menu-title-margin-x = <30>; + }; }; sysinfo {
configs/coreboot64_defconfig +2 -0
@@ -17,6 +17,7 @@ CONFIG_SHOW_BOOT_PROGRESS=y CONFIG_USE_BOOTARGS=y CONFIG_BOOTARGS="root=/dev/sdb3 init=/sbin/init rootwait ro" CONFIG_BOOTCOMMAND="bootflow scan -l; if bootflow menu; then cls; bootflow boot; fi" +CONFIG_CEDIT=y CONFIG_SYS_PBSIZE=532 CONFIG_PRE_CONSOLE_BUFFER=y CONFIG_SYS_CONSOLE_INFO_QUIET=y
@@ -46,6 +47,7 @@ CONFIG_TFTP_TSIZE=y CONFIG_USE_ROOTPATH=y CONFIG_REGMAP=y CONFIG_SYSCON=y +CONFIG_OFNODE_MULTI_TREE=y # CONFIG_ACPIGEN is not set CONFIG_SYS_IDE_MAXDEVICE=4 CONFIG_SYS_ATA_DATA_OFFSET=0
configs/coreboot_defconfig +2 -0
@@ -16,6 +16,7 @@ CONFIG_SHOW_BOOT_PROGRESS=y CONFIG_USE_BOOTARGS=y CONFIG_BOOTARGS="root=/dev/sdb3 init=/sbin/init rootwait ro" CONFIG_BOOTCOMMAND="bootflow scan -l; if bootflow menu; then cls; bootflow boot; fi" +CONFIG_CEDIT=y CONFIG_CONSOLE_RECORD=y CONFIG_CONSOLE_RECORD_OUT_SIZE=0x1000 CONFIG_PRE_CONSOLE_BUFFER=y
@@ -43,6 +44,7 @@ CONFIG_TFTP_TSIZE=y CONFIG_USE_ROOTPATH=y CONFIG_REGMAP=y CONFIG_SYSCON=y +CONFIG_OFNODE_MULTI_TREE=y # CONFIG_ACPIGEN is not set CONFIG_SYS_IDE_MAXDEVICE=4 CONFIG_SYS_ATA_DATA_OFFSET=0
Signature · 1 line
2.34.1
PATCH v3 18/20 x86: coreboot: Add a command to check and update CMOS RAM
In reply to Simon GlassCoreboot tables provide information about the CMOS-RAM checksum. Add a command which can check and update this.
With this it is possible to adjust CMOS-RAM settings and tidy up the checksum afterwards.
---
(no changes since v2)
Changes in v2:
- Avoid using common.h
cmd/Kconfig | 11 ++++ cmd/x86/Makefile | 1 + cmd/x86/cbcmos.c | 139 +++++++++++++++++++++++++++++++++++++++ doc/usage/cmd/cbcmos.rst | 42 ++++++++++++ doc/usage/index.rst | 1 + test/cmd/coreboot.c | 41 ++++++++++++ 6 files changed, 235 insertions(+) create mode 100644 cmd/x86/cbcmos.c create mode 100644 doc/usage/cmd/cbcmos.rst
cmd/Kconfig +11 -0
@@ -2846,6 +2846,17 @@ config CMD_CBSYSINFO memory by coreboot before jumping to U-Boot. It can be useful for debugging the beaaviour of coreboot or U-Boot. +config CMD_CBCMOS + bool "cbcmos" + depends on X86 + default y if SYS_COREBOOT + help + This provides information options to check the CMOS RAM checksum, + if present, as well as to update it. + + It is useful when coreboot CMOS-RAM settings must be examined or + updated. + config CMD_CYCLIC bool "cyclic - Show information about cyclic functions" depends on CYCLIC
cmd/x86/Makefile +1 -0
@@ -1,6 +1,7 @@ # SPDX-License-Identifier: GPL-2.0+ obj-$(CONFIG_CMD_CBSYSINFO) += cbsysinfo.o +obj-$(CONFIG_CMD_CBCMOS) += cbcmos.o obj-y += mtrr.o obj-$(CONFIG_CMD_EXCEPTION) += exception.o obj-$(CONFIG_USE_HOB) += hob.o
cmd/x86/cbcmos.c new file +139 -0
139 lines not on this page · raw message
doc/usage/cmd/cbcmos.rst new file +42 -0
42 lines not on this page · raw message
doc/usage/index.rst +1 -0
@@ -43,6 +43,7 @@ Shell commands cmd/bootz cmd/button cmd/cat + cmd/cbcmos cmd/cbsysinfo cmd/cedit cmd/cli
test/cmd/coreboot.c +41 -0
54 lines not on this page · raw message
Signature · 1 line
2.34.1
PATCH v3 19/20 x86: coreboot: Allow building an expo for editing CMOS config
In reply to Simon GlassCoreboot provides the CMOS layout in the tables it passes to U-Boot. Use that to build an editor for the CMOS settings.
---
(no changes since v2)
Changes in v2:
- Avoid using common.h
boot/Makefile | 3 + boot/expo_build_cb.c | 245 ++++++++++++++++++++++++++++++++ cmd/cedit.c | 28 ++++ doc/board/coreboot/coreboot.rst | 6 + doc/develop/cedit.rst | 2 +- doc/usage/cmd/cbcmos.rst | 3 + doc/usage/cmd/cedit.rst | 76 ++++++++++ include/expo.h | 8 ++ test/cmd/coreboot.c | 35 +++++ 9 files changed, 405 insertions(+), 1 deletion(-) create mode 100644 boot/expo_build_cb.c
boot/Makefile +3 -0
@@ -62,6 +62,9 @@ obj-$(CONFIG_$(PHASE_)LOAD_FIT) += common_fit.o obj-$(CONFIG_$(PHASE_)EXPO) += expo.o scene.o expo_build.o obj-$(CONFIG_$(PHASE_)EXPO) += scene_menu.o scene_textline.o +ifdef CONFIG_COREBOOT_SYSINFO +obj-$(CONFIG_$(SPL_TPL_)EXPO) += expo_build_cb.o +endif obj-$(CONFIG_$(PHASE_)BOOTMETH_VBE) += vbe.o obj-$(CONFIG_$(PHASE_)BOOTMETH_VBE_REQUEST) += vbe_request.o
boot/expo_build_cb.c new file +245 -0
245 lines not on this page · raw message
cmd/cedit.c +28 -0
@@ -67,6 +67,28 @@ static int do_cedit_load(struct cmd_tbl *cmdtp, int flag, int argc,return 0 ; } +#ifdef CONFIG_COREBOOT_SYSINFO +static int do_cedit_cb_load (struct cmd_tbl *cmdtp,int flag,int argc, +char *const argv[]) +{ +struct expo *exp; +int ret; + +if (argc >1 ) +return CMD_RET_USAGE ; + + ret =cb_expo_build (&exp); +if (ret) { +printf ("Failed to build expo: %dE\n" , ret); +return CMD_RET_FAILURE ; + } + + cur_exp = exp; + +return 0 ; +} +#endif /* CONFIG_COREBOOT_SYSINFO */ +static int do_cedit_write_fdt (struct cmd_tbl *cmdtp,int flag,int argc,char *const argv[]) {
@@ -271,6 +293,9 @@ static int do_cedit_run(struct cmd_tbl *cmdtp, int flag, int argc,U_BOOT_LONGHELP (cedit, "load <interface> <dev[:part]> <filename> - load config editor\n" +#ifdef CONFIG_COREBOOT_SYSINFO + "cb_load - load coreboot CMOS editor\n" +#endif"cedit read_fdt <i/f> <dev[:part]> <filename> - read settings\n" "cedit write_fdt <i/f> <dev[:part]> <filename> - write settings\n" "cedit read_env [-v] - read settings from env vars\n"
@@ -281,6 +306,9 @@ U_BOOT_LONGHELP(cedit, U_BOOT_CMD_WITH_SUBCMDS(cedit, "Configuration editor", cedit_help_text, U_BOOT_SUBCMD_MKENT(load, 5, 1, do_cedit_load), +#ifdef CONFIG_COREBOOT_SYSINFO + U_BOOT_SUBCMD_MKENT(cb_load, 5, 1, do_cedit_cb_load), +#endif U_BOOT_SUBCMD_MKENT(read_fdt, 5, 1, do_cedit_read_fdt), U_BOOT_SUBCMD_MKENT(write_fdt, 5, 1, do_cedit_write_fdt), U_BOOT_SUBCMD_MKENT(read_env, 2, 1, do_cedit_read_env),
doc/board/coreboot/coreboot.rst +6 -0
@@ -182,3 +182,9 @@ CI runs tests using a pre-built coreboot image. This ensures that U-Boot can boot as a coreboot payload, based on a known-good build of coreboot. To update the `coreboot.rom` file which is used, see ``tools/Dockerfile`` + +Editing CMOS RAM settings +------------------------- + +U-Boot supports creating a configuration editor to edit coreboot CMOS-RAM +settings. See :ref:`cedit_cb_load`.
doc/develop/cedit.rst +1 -1
@@ -172,4 +172,4 @@ Cedit provides several options for persistent settings: For now, reading and writing settings is not automatic. See the :doc:`../usage/cmd/cedit` for how to do this on the command line or in a -script. +script. For x86 devices, see :ref:`cedit_cb_load`.
doc/usage/cmd/cbcmos.rst +3 -0
@@ -40,3 +40,6 @@ CMOS RAM:: Checksum 6600 written => cbc check => + +See also :ref:`cedit_cb_load` which shows an example that includes the +configuration editor.
doc/usage/cmd/cedit.rst +76 -0
91 lines not on this page · raw message
include/expo.h +8 -0
@@ -762,4 +762,12 @@ int expo_apply_theme(struct expo *exp, ofnode node);*/ int expo_build (ofnode root,struct expo **expp); +/** +* cb_expo_build() - Build an expo for coreboot CMOS RAM +* +* @expp: Returns the expo created +* Return: 0 if OK, -ve on error +*/ +int cb_expo_build (struct expo **expp); +#endif /*__EXPO_H */
test/cmd/coreboot.c +35 -0
@@ -6,12 +6,16 @@* Written by Simon Glass <[email protected]> */ +#include <cedit.h> #include <command.h> #include <dm.h> +#include <expo.h> #include <rtc.h> +#include <test/cedit-test.h> #include <test/cmd.h> #include <test/test.h> #include <test/ut.h> +#include "../../boot/scene_internal.h" enum {CSUM_LOC =0x3f0 /8 ,
@@ -82,3 +86,34 @@ static int test_cmd_cbcmos(struct unit_test_state *uts)return 0 ; }CMD_TEST (test_cmd_cbcmos,UTF_CONSOLE ); + +/* test 'cedit cb_load' command */ +static int test_cmd_cedit_cb_load (struct unit_test_state *uts) +{ +struct scene_obj_menu *menu; +struct video_priv *vid_priv; +struct scene_obj_txt *txt; +struct scene *scn; +struct expo *exp; +int scn_id; + +ut_assertok (run_command ("cedit cb_load" ,0 )); +ut_assertok (run_command ("cedit read_cmos" ,0 )); +ut_assert_console_end (); + + exp = cur_exp; + scn_id =cedit_prepare (exp, &vid_priv, &scn); +ut_assert (scn_id >0 ); +ut_assertnonnull (scn); + +/* just do a very basic test that the first menu is present */ + menu =scene_obj_find (scn, scn->highlight_id,SCENEOBJT_NONE ); +ut_assertnonnull (menu); + + txt =scene_obj_find (scn, menu->title_id,SCENEOBJT_NONE ); +ut_assertnonnull (txt); +ut_asserteq_str ("Boot option" ,expo_get_str (exp, txt->str_id)); + +return 0 ; +} +CMD_TEST (test_cmd_cedit_cb_load,UTF_CONSOLE );
Signature · 1 line
2.34.1
PATCH v3 20/20 x86: Enable RTC command by default
In reply to Simon GlassThe real-time clock is needed for most X86 systems and it is useful to be able to read from it. Enable the rtc command by default.
---
(no changes since v2)
Changes in v2:
- Rebase to -next
cmd/Kconfig | 1 + 1 file changed, 1 insertion(+)
cmd/Kconfig +1 -0
@@ -2266,6 +2266,7 @@ config CMD_DATE config CMD_RTC bool "rtc" depends on DM_RTC + default y if X86 help Enable the 'rtc' command for low-level access to RTC devices.
Signature · 1 line
2.34.1
Re: [PATCH v3 20/20] x86: Enable RTC command by default
The real-time clock is needed for most X86 systems and it is useful to be able to read from it. Enable the rtc command by default.
---
(no changes since v2)
Changes in v2:
- Rebase to -next
cmd/Kconfig | 1 + 1 file changed, 1 insertion(+)
Applied to u-boot-dm, thanks!