Add target NBD_INFINITYAIO255

[mywinchester]

firmware already verify and been tested in hardware.

[sugaarK]

https://betaflight.com/docs/development/manufacturer/config-target-guidance
please read this @mywinchester

[mywinchester]

https://betaflight.com/docs/development/manufacturer/config-target-guidance please read this @mywinchester

I had read this document, we will follow policy in next step.

[sugaarK]

@mywinchester did you get NBD to email me or the target team?
there is a new review process.

[sugaarK]

opps sorry wrong button

[mywinchester]

@mywinchester did you get NBD to email me or the target team? there is a new review process.

Not yet, but I will send ASAP

[mywinchester]

I already send an email to [email protected], can you receive it? My email address is: [email protected]

[sugaarK]

@mywinchester talking to Lexi from NBD you don't need this now as far as I know. ?

[nerdCopter]

@sugaarK , Discord had a couple people ask where the target was. So the hardware is in the wild -- no clue how many.

[sugaarK]

@sugaarK , Discord had a couple people ask where the target was. So the hardware is in the wild -- no clue how many.

They have their own fork. They use a special osd that they don’t want to burden our project with

[mywinchester]

@sugaarK , Discord had a couple people ask where the target was. So the hardware is in the wild -- no clue how many.

They have their own fork. They use a special osd that they don’t want to burden our project with

In fact this board osd is max7456 compatible, and this target NBD_INFINITYAIO255 is already available in unified target repo, but somehow it can shows 4.5 version in configurator, that make people confuse. This pull request just wanna fix that problem.
And as I know the PR open in one month ago, but guide said it should start at july. If this PR really bothers your team, please remove the target form configurator, and I will close PR.

[sugaarK]

There is no problem with it but every one has to pay the fee and pass the review process NBD can afford it and given no one else has a problem contributing to the project it shouldn’t be an issue.

[sugaarK]

@mywinchester NDB have joined the full partner program so we can proceed with this now

[mywinchester]

@sugaarK config file had been check and ready for release.