From: "Moessbauer, Felix" <felix.moessbauer@siemens.com>
To: "Schild, Henning" <henning.schild@siemens.com>
Cc: "isar-users@googlegroups.com" <isar-users@googlegroups.com>,
"amikan@ilbers.de" <amikan@ilbers.de>,
"jan.kiszka@siemens.com" <jan.kiszka@siemens.com>,
"Schmidt, Adriaan" <adriaan.schmidt@siemens.com>
Subject: RE: [PATCH v3 2/7] Add ISAR version of biosplusefi WIC plugin
Date: Mon, 28 Mar 2022 09:11:40 +0000 [thread overview]
Message-ID: <AM9PR10MB48692B745D4DBCBDDCDD0D9B891D9@AM9PR10MB4869.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20220328105133.5c20634a@md1za8fc.ad001.siemens.net>
> > a/meta/scripts/lib/wic/plugins/source/bootimg-biosplusefi-isar.py +++
> > b/meta/scripts/lib/wic/plugins/source/bootimg-biosplusefi-isar.py @@
> > -75,10 +75,10 @@ class BootimgBiosPlusEFIPlugin(SourcePlugin):
> > --ondisk sda --label os_boot --active --align 1024 --use-uuid """
> > - name = 'bootimg-biosplusefi'
> > + name = 'bootimg-biosplusefi-isar'
> >
> > - __PCBIOS_MODULE_NAME = "bootimg-pcbios"
> > - __EFI_MODULE_NAME = "bootimg-efi"
> > + __PCBIOS_MODULE_NAME = "bootimg-pcbios-isar"
> > + __EFI_MODULE_NAME = "bootimg-efi-isar"
> >
> > __imgEFIObj = None
> > __imgBiosObj = None
> > @@ -106,7 +106,7 @@ class BootimgBiosPlusEFIPlugin(SourcePlugin):
> > loader = SourceFileLoader(cls.__PCBIOS_MODULE_NAME,
> > modulePath) mod = types.ModuleType(loader.name)
> > loader.exec_module(mod)
> > - cls.__imgBiosObj = mod.BootimgPcbiosPlugin()
> > + cls.__imgBiosObj = mod.BootimgPcbiosIsarPlugin()
>
> Mhh, for some reason we did rename the class in that fork but not in the EFI
> one.
That is indeed not consistent. However, I don't know about the side effects when renaming this.
Looks like the class name is not part of our API as the WIC script just takes the name of the python file (e.g. --source bootimg-efi-isar).
By that, a rename should be safe.
>
> Maybe something to get sorted out in this series, or later. Not sure which option
> would be best ... i guess the consistent rename would be the conservative
> option, meaning the EFI class would have to go
I vote for not refactoring this as part of the series.
It is technically unrelated (we just call the existing plugins) and just delays the integration.
Felix
>
> -class BootimgEFIPlugin(SourcePlugin)
> +class BootimgEFIIsarPlugin(SourcePlugin)
>
> Henning
>
> > # Import bootimg-efi (class name "BootimgEFIPlugin")
> > modulePath =
> > os.path.join(os.path.dirname(os.path.realpath(__file__)),
next prev parent reply other threads:[~2022-03-28 9:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 16:45 [PATCH v3 0/7] Add support for dual bios + efi disk generation Felix Moessbauer
2022-03-22 16:45 ` [PATCH v3 1/7] Copy efi-plus-pcbios script from OE Felix Moessbauer
2022-03-22 16:45 ` [PATCH v3 2/7] Add ISAR version of biosplusefi WIC plugin Felix Moessbauer
2022-03-28 8:51 ` Henning Schild
2022-03-28 9:11 ` Moessbauer, Felix [this message]
2022-03-28 9:20 ` Henning Schild
2022-03-22 16:45 ` [PATCH v3 3/7] wic: make import isarpluginbase work when plugins use each other Felix Moessbauer
2022-03-22 16:45 ` [PATCH v3 4/7] test: add target for efi-plus-pcbios image type Felix Moessbauer
2022-03-22 16:45 ` [PATCH v3 5/7] add support for current debian distros in start_vm.py Felix Moessbauer
2022-03-22 16:45 ` [PATCH v3 6/7] Add pcbios option to start_vm Felix Moessbauer
2022-03-22 16:45 ` [PATCH v3 7/7] run vm_boot_test against EFI and PC BIOS Felix Moessbauer
2022-04-12 12:56 ` [PATCH v3 0/7] Add support for dual bios + efi disk generation Moessbauer, Felix
2022-04-13 8:34 ` Anton Mikanovich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AM9PR10MB48692B745D4DBCBDDCDD0D9B891D9@AM9PR10MB4869.EURPRD10.PROD.OUTLOOK.COM \
--to=felix.moessbauer@siemens.com \
--cc=adriaan.schmidt@siemens.com \
--cc=amikan@ilbers.de \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox