From: Henning Schild <henning.schild@siemens.com>
To: "Moessbauer, Felix (T CED SES-DE)" <felix.moessbauer@siemens.com>
Cc: "isar-users@googlegroups.com" <isar-users@googlegroups.com>,
"amikan@ilbers.de" <amikan@ilbers.de>,
"Kiszka, Jan (T CED)" <jan.kiszka@siemens.com>,
"Schmidt, Adriaan (T CED SES-DE)" <adriaan.schmidt@siemens.com>
Subject: Re: [PATCH v3 2/7] Add ISAR version of biosplusefi WIC plugin
Date: Mon, 28 Mar 2022 11:20:13 +0200 [thread overview]
Message-ID: <20220328112013.1eb5baa8@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <AM9PR10MB48692B745D4DBCBDDCDD0D9B891D9@AM9PR10MB4869.EURPRD10.PROD.OUTLOOK.COM>
Am Mon, 28 Mar 2022 11:11:40 +0200
schrieb "Moessbauer, Felix (T CED SES-DE)"
<felix.moessbauer@siemens.com>:
> > > 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.
Good. We should keep that in mind, and i agree that we should not slow
down any more.
Henning
> 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:20 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
2022-03-28 9:20 ` Henning Schild [this message]
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=20220328112013.1eb5baa8@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=adriaan.schmidt@siemens.com \
--cc=amikan@ilbers.de \
--cc=felix.moessbauer@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