Request for new definition to support Ebyte E22 modules[Board]: about firmware HOT 1 OPEN

Ok so ebyte got back to me, they don't know meshtastic and can't offer any support,
I've done a hell of alot of reading on this issue and the more I read up on the ebyte E22 full power output issue the more it seems to now be a meshtastic issue,
Other projects that have had this issue have overcome the problem now buy changing things in the code,

I have managed to find the bits in the code I was looking for regarding power limits and regions and max tx power and pa ramp time etc, and I've spent about 40 hours now trying different things with no luck,

Me being into hardware and not doing much code I really wanted the team here to have another look into this issue and maybe write a profile specifically for the E23 modules, I say modules plural as we now have the E22-900M33S which has different setup requirements than the E22-900M30S ( 33 only needs 9db drive) ( this need to be at radio_begin otherwise we are potentially going to damage modules during channel changes as I've noted this also updates output power as part of the ch settings)

I have noted EBYTE_E22 in the code but I don't know just how much work has been done to fully support it let alone the issue I mentioned with the latest module so that would need it's own definition

I don't feel moving this from and issue as I reported it to a discussion helps, there has been endless discussion and there is obviously an issue here

Anyway I'm hoping we can resolve this issue and get on with using these modules to their full potential

from firmware.