OpenWrt/LEDE Project

  • Status Closed
  • Percent Complete
  • Task Type Bug Report
  • Category Base system
  • Assigned To No-one
  • Operating System All
  • Severity Low
  • Priority Very Low
  • Reported Version lede-17.01
  • Due in Version Undecided
  • Due Date Undecided
  • Private
Attached to Project: OpenWrt/LEDE Project
Opened by guifipedro - 17.01.2019
Last edited by Ted Hess - 20.02.2019

FS#2061 - Different names for the same targets, let's decide: ALFA-NX, ALFANX or alfa-nx ?

I’m doing a tool that helps for compilation (I’m working based on lede 17.01.4). With these targets I had no problems, the name is the same everywhere. yay!, but with alfa-nx yes, this name is not clear, depends where you find it the name is different

here is ALFA-NX

# dmesg | grep -i board
[    0.000000] MyLoader: sysp=b9c9f1a8, boardp=9b949905, parts=b9c9f188
[    0.000000] Kernel command line:  board=ALFA-NX console=ttyS0,115200 mtdparts=spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,6144k(rootfs),1600k(kernel),64k(nvram),64k(art)ro,7744k@0x50000(firmware) rootfstype=squashfs,jffs2 noinitrd

here is ALFANX

make info | grep 'ALFANX' -A2

    ALFA Network N2/N5 board

here is alfa-nx (the output target in compilation)


Do you agree that the same name should be everywhere? I think it should be alfa-nx (as the other profiles are 100% lowercase)

I can solve this locally putting an if statement (doing an exception), but I think it is better to have good universal names everywhere.

Closed by  Ted Hess
20.02.2019 13:38
Reason for closing:  Invalid report
guifipedro commented on 17.01.2019 16:57

(The board name to be different is not important)

I find that all these names are very similar here, and they are uppercase:


looks like you want the legacy devices to be uppercase, no problem, I will find a way to process this


Available keyboard shortcuts


Task Details

Task Editing