[PATCH] sh: Implemented syscall_{get|set}_arguments for i != 0

2014-04-14 Thread Konstantin Tokarev
>From 5cd11ca62acfcde2757fbcc9bbb55e9449d2d50b Mon Sep 17 00:00:00 2001 From: Konstantin Tokarev Date: Mon, 14 Apr 2014 20:38:00 +0400 Subject: [PATCH] sh: Implemented syscall_{get|set}_arguments for i != 0. syscall_get_arguments and syscall_set_arguments implementations for SH will not call

Re: lz4hc compression in UBIFS?

2013-10-28 Thread Konstantin Tokarev
24.10.2013, 19:15, "Konstantin Tokarev" : > Attached patch to crypto API wrapper for lz4hc seems to fix the issue. I can > save > and read files on LZ4HC-compressed volume, and I'm running on > LZ4HC-compressed rootfs, > flashed from mkfs.ubifs generated image

Re: lz4hc compression in UBIFS?

2013-10-24 Thread Konstantin Tokarev
24.10.2013, 18:20, "Konstantin Tokarev" : > 23.10.2013, 22:26, "Yann Collet" : > >>  UBIFS error (pid 4288): ubifs_decompress: cannot decompress 12 bytes, >>  (...) >>  data size  12 >>  data: >>  : 1

Re: lz4hc compression in UBIFS?

2013-10-23 Thread Konstantin Tokarev
23.10.2013, 16:49, "Brent Taylor" : > On Wed, Oct 23, 2013 at 2:40 AM, Konstantin Tokarev wrote: > >>  23.10.2013, 09:26, "Brent Taylor" : >>>  Konstantin, >>> I did my testing with data from /dev/urandom (which I now realize >>>

Re: lz4hc compression in UBIFS?

2013-10-23 Thread Konstantin Tokarev
23.10.2013, 09:26, "Brent Taylor" : > Konstantin, >    I did my testing with data from /dev/urandom (which I now realize > wasn't the best choice of data source), but if I use /dev/zero (which > actually causes data compression to occur), the decompressor fails.  I > don't know the internal worki