When the underlying /etc/config/wireless got changed since the last "wifi up"
has been performed, the uci vap ifname state vars become inconsistent on a
subsequent "wifi up" and multiple vaps get mapped to the same ifnames which
confuses the gui and other processes relying on them.
For now call an explicit "wifi down" prior to each "wifi up" which will clear
up the state accordingly.
SVN-Revision: 33076
Give nas interface time to setup them selves before configuring them.
Should fix#11826.
Contributed by T-Labs, Deutsche Telekom Innovation Laboratories
Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
SVN-Revision: 33074
The structs defined in these header files should be the same as the
structes used by the platform code otherwise it will cause strange
runtime errors. By removing them from compat-wireless we will get a
compile error instead of a runtime error if they are out of sync.
SVN-Revision: 33006
* remove use_et, all supported drivers are using mii ioctls
* remove robo.phy_addr, phy_addr was always set to ROBO_PHY_ADDR.
* remove support for old kernel versions
* do_ioctl is allways called with buff == NULL
* use if_mii
SVN-Revision: 33002
When standalone ldd is selected in config the binary is installed in /usr/bin/ldd.
Signed-off-by: Michael Heimpold <mhei@heimpold.de>
SVN-Revision: 32891
I did not add the last patch, because it add some stubs for the flash drivers and our patches have to be changed for that, if the flash support in bcma is able to do something I will integrate it.
This also contains 3 additional patches fixing some bugs in bcma.
SVN-Revision: 32880
With the BRCM47xx image I have built (Linksys E3000), there are additional
writes following the completion of "mtd_replace_jffs2" which invalidate the
'trx_fixup' performed by 'mtd_replace_jffs2'. Moving the 'trx_fixup' to somewhere
after all writes have completed fixes the problem. I also noticed that 'erasesize'
used to compute 'block_offset' in 'mtd_fixtrx' is used before it is computed by
'mtd_check_open'; moving the call to 'mtd_check_open' up a few lines fixes this.
Unlike 'mtd_fixtrx', 'trx_fixup' appears to assume that the TRX header is always at
offset 0; which may be the cause of the problem described in Ticket #8960.
Signed-off-by: Nathan Hintz <nlhintz@hotmail.com>
SVN-Revision: 32866
Jo-Philipp Wich
Florian Fainelli
Jonas Gorski
Felix Fietkau
John Crispin
Hauke Mehrtens