update zyxel firmware cz001-4.12.008.14 problem

Packets between them. This has always been possible with tunnels in the It's already possible to create two different interfaces and loop * socket: remove errant restriction on looping to self This should make packaging somewhat easier, as bash is generally alreadyĪvailable (at least for dkms), whereas bc isn't provided by distros by * compat: use bash instead of bc for HZ->USEC calculation Kernel. The correct fix is to use $(CURDIR), which should point to The object directory is separate from the kernel source directory, forĮxample when using O='elsewhere' as a make option when building the Source directory. This isn't quite correct on configurations in which * compat: timeconst.h is a generated artifactīefore we were trying to check for timeconst.h by looking in the kernel Tested-by: Roger Pueyo Centelles Tested-by: Baptiste Jonglez Tested-by: Tobias Schramm Tested-by: Christopher Hill Signed-off-by: Thibaut VARÃNE This driver has been successfully tested on BE (ath79) and LE (ipq40xxĪnd ramips) hardware. This driver does not reuse any of the existing code previously found in Possible to operate entirely from the MTD device without using a localīuffer (except when requesting WLAN calibration data), at the cost of a 'hard_config' MTD partition (typically 4KB), although it is technically This driver permanently allocates a chunk of RAM as large as the

Named 'hard_config'. The WLAN calibration data is available on demand via

Of MikroTik RouterBOARDs devices. It presents the data in a sysfs folder This driver exposes the data encoded in the 'hard_config' flash segment Generic: routerboot sysfs platform driver

Update zyxel firmware cz001-4.12.008.14 problem