Rename SPL06 to SPx06

[peterbarker]

I've built this branch for every target, blimp-only.

Binary output is identical except where the hwdefs have been modifed.

Extracted from https://github.com/ArduPilot/ardupilot/pull/27905/files

pbarker@threads:~$ ~/rc/ardupilot/Tools/scripts/filter_size_compare_branches_csv.py /tmp/some.csv  --hide-bin
------------------------  -----  ----------
Board                     blimp  bootloader
AtomRCF405NAVI            0      *
FlyingMoonF427            0      *
FlyingMoonH743            0      *
FlywooF745                0      *
FlywooF745Nano            0      *
IFLIGHT_2RAW_H7           0      *
MambaF405-2022            0      *
MambaH743v4               0      *
MatekF405-TE              0      *
MatekF405-TE-bdshot       0      *
MicoAir405v2              0      *
R9Pilot                   0      *
SITL_arm_linux_gnueabihf  0
SITL_x86_64_linux_gnu     0
SpeedyBeeF405WING         0      *
bbbmini                   0
blue                      0
canzero                   0
edge                      0
erlebrain2                0
navigator                 0
navio                     0
navio2                    0
obal                      0
pxf                       0
pxfmini                   0
speedybeef4v3             0      *
speedybeef4v4             0      *
------------------------  -----  ----------
pbarker@threads:~$ 

[tridge]

I'd prefer just a comment in the top of the SPL06 driver saying it supports SPA06 as well

[radiolinkW]

I'd prefer just a comment in the top of the SPL06 driver saying it supports SPA06 as well

What if there is still SPB06? And SPA06 was not originally part of SPL06.

How was the discussion at your DevCallEU going?

[peterbarker]

I'd prefer just a comment in the top of the SPL06 driver saying it supports SPA06 as well

What if there is still SPB06? And SPA06 was not originally part of SPL06.

How was the discussion at your DevCallEU going?

I've commented on your PR explaining what happened.

Hopefully into the future we can do something like we do for the Invensense drivers - so if the protocol changes we add "v2" or "v3" on the end. And to know which driver supports what you check the comments at the top of the file.

Again, apologies for the run-around with the rename - you suggested it, I thought it was a good idea - it wasn't :-)