Attention is currently required from: Balázs Vinarz, Keith Hui, Nico Huber.
2 comments:
Patchset:
have the user specify the protocol via programmer options
If this is fine for the user, this is a good option. Would the user know which protocol they need? For example, if you were the user?
dummyflasher.c can initialise more than one bus, and the desired option is set via programmer param. dummyflasher is an emulator-programmer, but it will do as an example how to init one bus or the other depending on the param.
Also, this can be done step-by-step, doesn't have to be in one commit. First commit adds programmer and support for spi. Second commit can add programmer param, and more options (parallel). If default option stays the same (default what happens without param provided), this should be fine.
Adding new programmer will be a large commit already, and lots of work, I think planning multiple commits will help.
File meson.build:
we might need to use the ezo here as well to maintain consistency, but that wouldn't mention that th […]
yes, let's use `ezo`
it seems it can be made to work with not only SPI
To view, visit change 23053. To unsubscribe, or for help writing mail filters, visit settings.