After kernel 2.6.39, usbip kernel and userspace are in kernel tree
The new kernel modules names have already been updated in openwrt for
kernel > 2.6.39
This patch, allow to build the new corresponding usbip userspace tool
when of the device use a kernel > 2.6.39
And continue to build version
A grep for LINUX_VERSION in target/linux/*/Makefile shows that OpenWRT
current uses a large number of different kernel versions for the various
platforms. While there may be reasons for using a particular version, it
would be nice if newer kernels were available for those platforms that
support
Not entirely. If you do sysupgrade -n, even with a squashfs image, the
image isn't actually upgraded. The upgrade process skips writing the
image file and proceeds with a reboot without having done anything.
On 4/13/12 8:03 AM, Kaspar Schleiser wrote:
Hey,
well, and it only affects those ins
Hey,
well, and it only affects those installations that use ext4.
Using sqashfs and jffs2 is perfectly possibly on block devices.
Sysupgrade works fine with them on x86.
Regards
Kaspar
On 04/13/2012 11:24 AM, David Woodhouse wrote:
For a start, this isn't really about "x86", is it? It's abou
More device info at: http://wiki.openwrt.org/toh/tenda/w306r
Index: target/linux/ramips/files/arch/mips/ralink/rt305x/Kconfig
===
--- target/linux/ramips/files/arch/mips/ralink/rt305x/Kconfig (revision 31231)
+++ target/linux/ramips
On Fri, 2012-04-13 at 10:24 +0100, David Woodhouse wrote:
> Sounds like you'd be a lot better off using btrfs snapshots for that.
Note that btrfs-progs from the git tree now has a '-r' option to create
an image from a given directly, much like genext2fs does.
--
dwmw2
smime.p7s
Description: S/
For a start, this isn't really about "x86", is it? It's about systems
which use block-based storage instead of flash?
This is for anything which makes the mistake of using CompactFlash or SD
instead of letting the OS have real access to the flash.
There are x86 systems (like OLPCv1, anything with
