Klez

Hi Igor and everyone else.
 
Id'like to suggest the following:
 
/etc/fstab
It´s not necesary to use both noatime and nodiratime, because noatime already implies nodiratime, so you can use only the option "noatime" instead of both.
 
When creating the ext4 filesystem with mkfs.ext4 you can type a label for it with the parameter " -L " so when the users mount their cards on a computer, the desktop will show some name instead "NO NAME".
For example:
 # mkfs.ext4 -O ^has_journal -L Armbian /dev/mmcblk0p1
or...
# mkfs.ext4 -O ^has_journal -L Cubox-i /dev/mmcblk0p1
 
Cheers
- Klez

i think you are refering to the firmware file, a .BIN file, (wich is part of linux-firmware). But i am refering to the specific nvram file, wich is a text .TXT file, wich is supposed to be specific to the device wich mounts the chip. Yes, for sure the most up-to-date firmware file must be from linux-firmware at: http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/tree/brcm
As you can see in the GIT repository, there are only BIN firmware files, but not Nvram .txt files...
 
Differences between the two files are quite important and my fear is that one could be better or have less wifi bugs.
I´m hoping that Jon Nettleton answers my question and tell me where in the earth the "upgraded" file come from.
 
Maybe depending solid-runs answer you could take the decission of upgrading (or keeping) the nvram file shipped in Armbian.
 
Will post replies as i find more info about
- Klez