[Bug]: Ambiguous naming for Core3566

[ssinyagin]

What happened?

There are two board configs with confusing names: luckfox-core3566.csc and core3566.csc. As far as I could find out, there is no other board named core3566 apart from the Luckfox one.

Also, bookworm built with core3566.csc does not boot on Luckfox Core3566.

Also, bookworm built with luckfox-core3566.csc does not see any USB devices.

How to reproduce?

compile, dd to an SD card, boot from it

Branch

main (main development branch)

On which host OS are you running the build script and observing this problem?

Debian 12 Bookworm

Are you building on Windows WSL2?

• Yes, my Ubuntu/Debian/OtherOS is running on WSL2

Relevant log URL

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[github-actions]

Jira ticket: AR-2691

[EvilOlaf]

Also, bookworm built with core3566.csc does not boot on Luckfox Core3566.

Not a framework bug. How to debug boot issues: https://debug.armbian.de

Also, bookworm built with luckfox-core3566.csc does not see any USB devices.

Not a framwork bug. Issues running Armbian shall be reported in forums. Also this is a community supported board. Its status is unknown to the Armbian team.

[EvilOlaf]

There are two board configs with confusing names: luckfox-core3566.csc and core3566.csc

Agreed. No clue if they are related to each other or are meant for different boards.
These are the PRs where those were added. I suggest to reach out to the authors and try to clear things up.
#7018
#7354

[ssinyagin]

These are the PRs where those were added.

probably a stricter policy needs to be introduced for PRs? Like, a more detailed board description. Also, testing before merging.

[igorpecovnik]

testing before merging.

For CSC, that is not possible. We don't have time nor hardware.

The only way to allow "anything" is establishing "community supported section". Which switches this responsibility to contributor of PR. In most cases its tested, but this is not requirement for merge as its impossible to verify. Only rule here is - does it build - yes?, merge. Already dealing with merging and often breaking after awhile, exceeds our time and budget. When .CSC community target stops compiling, its EOL-ed without questions asked.

[ssinyagin]

@igorpecovnik I'm not proposing for the team to test. But the PR acceptance criteria could be tightened, like:

1. Detailed description of the board: manufacturer, model name, link to the vendor site
2. A list of standard test results (this needs to be worked on, but roughly it's UART, Ethernet, USB, GPIO, PCIe, HDMI, Wifi/BT if present).
3. At least one test result (or maybe two?) from an independent tester.

[igorpecovnik]

PR acceptance criteria could be tightened

True, some additional guidance can help a bit on a long run.

Feel free to improve the text:
https://docs.armbian.com/User-Guide_Board-Support-Rules/
https://github.com/armbian/build/blob/main/.github/PULL_REQUEST_TEMPLATE.md (perhaps some parts are pointless here)