Add exfat filesystem support for fstools so that the block can detect and show
the information
of stroage in exfat format.
Signed-off-by: Rosy Song
---
CMakeLists.txt | 1 +
libblkid-tiny/blkidP.h | 12
libblkid-tiny/exfat.c | 155 +
Fix potential memory leak in fstools
Signed-off-by: Rosy Song
---
libblkid-tiny/libblkid-tiny.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libblkid-tiny/libblkid-tiny.c b/libblkid-tiny/libblkid-tiny.c
index ccfaf63..12cab6f 100644
--- a/libblkid-tiny/libblkid-tiny.c
+++
When firmware is new flashed and reboot with a storage device plug in its usb
interface. Though the filesystem is not ready (FS_STATE_UNKNOWN), the
/dev/sda1 still mount on /mnt/sda1 by block-mount, then the system switching
jffs...
root@OpenWrt:~# dmesg
..
[ 32.224522] jffs2_scan_eraseblo
On 29/03/18 10:23, rosys...@rosinson.com wrote:
Add exfat filesystem support for fstools so that the block can detect and show
the information
of stroage in exfat format.
(...)
Can an exfat implementation be legally distributed?
--
Bas.
___
Lede
Hi,
fstools will use the full libblkid if it is installed on the system,
this should also enable support for all filesystems supported by the
full libblkid.
Adding more and more exotic stuff to libblkid-tiny will bloat the
default fstools install for all users, so we should avoid that - imho.
Re
Hi Felix,
Regarding your commit ("build: include kmod-ipt-offload in default
images") [1]
By default, this package is only supported (and selectable) when the
target device uses kernel 4.14.
I've just tried this:
- Checkout OpenWrt master
- Select a target using kernel 4.9 (ar71xx)
- Buil
On 2018-03-29 13:42, Koen Vandeputte wrote:
> Hi Felix,
>
> Regarding your commit ("build: include kmod-ipt-offload in default
> images") [1]
>
> By default, this package is only supported (and selectable) when the
> target device uses kernel 4.14.
>
>
> I've just tried this:
>
> - Checkout
Hello,
Trying to add support of drivers/net/wireless/rsi/rsi91x driver in mac80211 we
faced with problem,
that the version of backports is quite old(2017-11-01), and at least one
significant commit for rsi91x was later than this version:
https://git.kernel.org/pub/scm/linux/kernel/git/wireless/w
After building coreboot myself, I discovered that the board names
changed again - they now seem to be the same as before.
https://github.com/pcengines/coreboot/commit/3578e9fb6dac753ec9365c88a8556ca1b90a8deb
I guess the "PC Engines apuX" strings can be considered to be a bug on
the PCEngines si
