(yes, more nitpickery for which i apologize ahead of time ...)

another oddity that was asked of me yesterday ... was explaining to a couple colleagues how the Kconfig system worked for u-boot, especially this part from doc/README.kconfig:

Define CONFIG_SYS_VENDOR="vendor" to compile board/<vendor>/common/* and board/<vendor>/<board>/* Define CONFIG_SYS_BOARD="board" to compile board/<board>/* (or board/<vendor>/<board>/* if CONFIG_SYS_VENDOR is defined)

at which point one of those colleagues asked, "how many boards don't specify a vendor? wouldn't that be kind of weird? a board without a vendor?"

i'd never thought about it so, as a quick check, i just tried this to see how many board files actually lived directly under board/<board>/ and got:

$ ls board/*/board.c board/sunxi/board.c $

i thought that was interesting -- all of one board (unless i'm misreading something). a quick "git log" shows that that sunxi content was added back in may 2014, before the Kbuild system was incorporated.

is that really the only supported board that does not identify a vendor? and if it is, why not just refactor that content to add its vendor (allwinner??), at which point is there any need to support vendorless boards?

or perhaps i am just misreading what i'm looking at. it's just a curiosity i had no answer for when asked about.

rday