Nextor v3 won't include support for Nextor v2 drivers, therefore we need a mechanism to prevent both from being used simultaneously:
Nextor v3 kernels will skip initialization if a Nextor v2 kernel has already initialized.
Otherwise, the "one-time boot keys" mechanism will be used to simulate the user configuring the "N" key as being pressed, this will prevent Nextor v2 kernels from booting.
In other words: only Nextor v2 or Nextor v3 kernels will initialize, depending on which one has the smallest slot number (and thus initializes first).
The last mechanism will cause the non-primary Nextor v3 kernels to skip initialization too, so the disable key for Nextor v3 will need to be changed from "N" to something else at some point. It's also not bullet-proof as older Nextor v2 kernels (which didn't support the "one-time boot keys" mechanism) will initialize anyway, with unpredictable results.
Nextor v3 won't include support for Nextor v2 drivers, therefore we need a mechanism to prevent both from being used simultaneously:
Nextor v3 kernels will skip initialization if a Nextor v2 kernel has already initialized.
Otherwise, the "one-time boot keys" mechanism will be used to simulate the user configuring the "N" key as being pressed, this will prevent Nextor v2 kernels from booting.
In other words: only Nextor v2 or Nextor v3 kernels will initialize, depending on which one has the smallest slot number (and thus initializes first).
The last mechanism will cause the non-primary Nextor v3 kernels to skip initialization too, so the disable key for Nextor v3 will need to be changed from "N" to something else at some point. It's also not bullet-proof as older Nextor v2 kernels (which didn't support the "one-time boot keys" mechanism) will initialize anyway, with unpredictable results.