Me too.
> On May 5, 2018, at 7:36 AM, Paul Spooren wrote:
>
> Are there any updates on this issue? I'd really like to see squasfs 5.0 used
> in OpenWrt!
>
> On Sat, May 27, 2017 at 8:51 PM, Hauke Mehrtens wrote:
>> On 05/26/2017 06:13 PM, Alexander Couzens wrote:
>>> squashfs is quite long u
From: Rafał Miłecki
The biggest (and the only?) disadventage of this is obviously an
increased image size.
For mips74k the size of vmlinux goes up from 4186684 B to 4701436 B.
Most devices use LZMA compressed kernel so probably more important is
vmlinux.lzma size which goes up from 1342945 B to
They already had jow or someone else sent messages to call for kernel
updates and sending patches before the release, and got stuff done by now.
As per the last answer of John Crispin to this mail thread, they will
release at the beginning of next week.
Developers choose freely what they pref
On 05.05.2018 15:56, Kristian Evensen wrote:
Hello,
When restarting the firewall on routers running latest nightly, I
frequently get the following warning:
[ 74.952854] [ cut here ]
[ 74.952874] WARNING: CPU: 2 PID: 0 at
net/netfilter/nf_conntrack_rtcache.c:197 0x8f6
I didn't mention forcing people at any point. Just having someone to be
in charge in order to organize certain things, get people's availability
and make more thing happen.
With regards schedule the lack of one seems not doing much good, so
having one has the potential to improve things. And a
> One characteristic from OpenWrt, different from other projects is the
> lack of a leader or a person who can gather others together, make some
> decisions or push for them to happen. If one doesn't like this title it
> can also be "Project Manager" or "Project Coordinator". This, in my
> view, ma
This isn't a job where you can force people to do anything.
Also, I'm not a fan of half-assing or leaving out things for the sake of
a schedule.
-Alberto
On 05/05/2018 20:41, Fernando Frediani wrote:
One characteristic from OpenWrt, different from other projects is the
lack of a leader or a
Hello,
On Friday, May 4, 2018 4:12:16 PM CEST Roman Yeryomin wrote:
> I'm seeing this
>
> [1.275858] cpufreq: cpufreq_online: CPU0: Running at unlisted freq:
> 632000 KHz
> [1.276620] cpufreq: cpufreq_online: CPU0: Unlisted initial frequency
> changed to: 716000 KHz
Sorry, but I'm havi
One characteristic from OpenWrt, different from other projects is the
lack of a leader or a person who can gather others together, make some
decisions or push for them to happen. If one doesn't like this title it
can also be "Project Manager" or "Project Coordinator". This, in my
view, makes a
On 05/05/18 12:27, Jaap Buurman wrote:
Hi all,
I feel like everybody is just waiting for everybody to agree what
features we want in before coming up with the next step of picking a
date. Obviously this isn't working out very well. Why not turn things
around? Pick a date in a few weeks time on
* Refreshed patches
Compile-tested: ar71xx
Run-tested: ar71xx
Signed-off-by: Etienne Haarsma
---
include/kernel-version.mk| 4 ++--
...03-mtd_fix_cfi_cmdset_0002_status_check.patch | 14 +++---
...11-mtd-cfi_cmdset_0002-force-word-write.patch | 6 +++---
.../pa
On 2018-05-05 16:35, Linus Walleij wrote:
On Sat, May 5, 2018 at 11:25 AM, Linus Walleij
wrote:
On Fri, May 4, 2018 at 11:49 PM, Linus Walleij
wrote:
On Fri, May 4, 2018 at 11:37 PM, Roman Yeryomin
wrote:
The GPIO LEDs does not come up though?
CONFIG_LEDS_GPIO is not in config, and
/sys/c
On 2018-05-05 17:32, Linus Walleij wrote:
On Tue, May 1, 2018 at 8:44 PM, Roman Yeryomin wrote:
Linus, if you have time, could you check if this helps to bring
network up
on dir-685?
https://github.com/yeryomin/openwrt/commit/b0296b1f71bd3d677c931addd6de341203fbf18f
Sadly not. At least not
On Tue, May 1, 2018 at 8:44 PM, Roman Yeryomin wrote:
> Linus, if you have time, could you check if this helps to bring network up
> on dir-685?
> https://github.com/yeryomin/openwrt/commit/b0296b1f71bd3d677c931addd6de341203fbf18f
Sadly not. At least not outofthebox. I do not know what other
dev
Are there any updates on this issue? I'd really like to see squasfs 5.0
used in OpenWrt!
On Sat, May 27, 2017 at 8:51 PM, Hauke Mehrtens
wrote:
On 05/26/2017 06:13 PM, Alexander Couzens wrote:
squashfs is quite long unmaintained. All patches from major
distributions are integrated.
Fixed
On Thu, Mar 29, 2018 at 9:22 AM, Daniel Golle
wrote:
On Tue, Mar 27, 2018 at 07:42:18PM +0200, Christian Lamparter wrote:
This patch adds a image with squashfs as the root filesystem.
A rootfs_data partition will be generated on the first boot
and placed inside the rootfs partition (just
On Sat, May 5, 2018 at 11:25 AM, Linus Walleij wrote:
> On Fri, May 4, 2018 at 11:49 PM, Linus Walleij
> wrote:
>> On Fri, May 4, 2018 at 11:37 PM, Roman Yeryomin wrote:
>>
The GPIO LEDs does not come up though?
CONFIG_LEDS_GPIO is not in config, and
/sys/class/leds is empty.
>>>
Hello,
When restarting the firewall on routers running latest nightly, I
frequently get the following warning:
[ 74.952854] [ cut here ]
[ 74.952874] WARNING: CPU: 2 PID: 0 at
net/netfilter/nf_conntrack_rtcache.c:197 0x8f6293f0
[ 74.952876] Modules linked in: rt2800p
On 05/04/2018 07:27 PM, Sandeep Sheriker Mallikarjun wrote:
> resending all patches again due with rebase.
>
> Sandeep Sheriker Mallikarjun (10):
> at91bootstrap:update to v3.8.10
> at91: fix sdcard create image
> uboot-at91: fetch uboot src from u-boot-at91 github
> kernel: fix build erro
Hi all,
I feel like everybody is just waiting for everybody to agree what
features we want in before coming up with the next step of picking a
date. Obviously this isn't working out very well. Why not turn things
around? Pick a date in a few weeks time on which the Master branch
will be split to a
On 05/05/2018 11:25 AM, Linus Walleij wrote:
> On Fri, May 4, 2018 at 11:49 PM, Linus Walleij
> wrote:
>> On Fri, May 4, 2018 at 11:37 PM, Roman Yeryomin wrote:
>>
The GPIO LEDs does not come up though?
CONFIG_LEDS_GPIO is not in config, and
/sys/class/leds is empty.
Doe
On Fri, May 4, 2018 at 11:49 PM, Linus Walleij wrote:
> On Fri, May 4, 2018 at 11:37 PM, Roman Yeryomin wrote:
>
>>> The GPIO LEDs does not come up though?
>>> CONFIG_LEDS_GPIO is not in config, and
>>> /sys/class/leds is empty.
>>>
>>> Does it need a separate kmod?
>>
>> kmod-leds-gpio is part
22 matches
Mail list logo