Some devices like Netgear WNR1000v3 or WGR614v10 have partitions aligned
to 0x1000. Using bigger blocksize stopped us from detecting some parts.
Signed-off-by: Rafał Miłecki zaj...@gmail.com
---
Most of supported devices use flashes with erasesize 0x1 (64Ki), so
this change shouldn't affect
Hi,
I'm trying to start/stop our Wi-Fi sharing daemons [1] in tandem with wifi
up/down. On AA we used to patch /sbin/wifi, but on BB it seems this logic
has moved into netifd and that it may be possible to do it patchless,
perhaps by monitoring ubus for some event?
I tried just doing ubus listen
* Johan Almbladh j...@anyfi.net [12.11.2014 10:45]:
I tried just doing ubus listen in one shell and then running wifi from
another, but that doesn't give much to go on:
which events do you need?
a joining or leaving station?
use 'iw event'
an upcoming (or going down) interface?
use
Thanks, Bastian. If I add a script /etc/hotplug.d/net/ I get up/down events
for WLAN interfaces when /sbin/wifi is run.
The hotplug scripts receive events for interface names, but they know
nothing about the underlying configuration. Is there any way to map a WLAN
interface name, e.g. wlan0, to
Hey openwrt devs!
I'm observing 100% reproducible kernel oopses with a recent openwrt
(tested with trunk and barrier breaker) on a Mikrotik Routerboard RB435
which is equipped with 5 minipci cards. The board boots up fine if all
wifi devices are disabled in /etc/config/wireless and yields the
On 9 November 2014 10:16, Alexey N. Vinogradov a.n.vinogra...@gmail.com wrote:
Where is squashfs ever necessary for initramfs?
bcm53xx/image. The ubinize is invoked for any fs (initramfs, squashfs).
And, in turn, in ubinize.conf the root.squashfs is reffered.
So, if just ask to build
Thanks for that pointer, Aaron, but it looks like swconfig won't be of use to
me, because it's for configuring specific switches (my usage is not a switch -
it's the Intel ethernet port directly from the Rangeley SoC).
Anyway, for now, I'm planning to write a small helper script that is
Tells Python not to compile the source files.
The default behaviour is for the sources to be compiled
when the sources are run.
On small disks this can fill them up.
Although the performance of Python will suffer (it's not fast
to begin with) it's better to for it to be slow than to fill up
the
On 2014-11-12 21:08, Alexandru Ardelean wrote:
Tells Python not to compile the source files.
The default behaviour is for the sources to be compiled
when the sources are run.
On small disks this can fill them up.
Although the performance of Python will suffer (it's not fast
to begin
2014-11-11 23:51 GMT-07:00 Rafał Miłecki zaj...@gmail.com:
On 11 November 2014 23:26, Alex Henrie alexhenri...@gmail.com wrote:
Is no one interested? Come on, I'm offering free hardware to play with ;-)
I already have about 10-20 Broadcom based boars in my drawer ;) Not
that excited with
Will do it that way.
Thanks
On Wed, Nov 12, 2014 at 11:01 PM, Felix Fietkau n...@openwrt.org wrote:
On 2014-11-12 21:08, Alexandru Ardelean wrote:
Tells Python not to compile the source files.
The default behaviour is for the sources to be compiled
when the sources are run.
On
Signed-off-by: Richard Kunze richard.ku...@web.de
---
target/linux/kirkwood/image/Makefile | 3 +++
target/linux/kirkwood/profiles/110-nas.mk | 17 +
2 files changed, 20 insertions(+)
diff --git a/target/linux/kirkwood/image/Makefile
b/target/linux/kirkwood/image/Makefile
On Nov 11, 2014 6:09 PM, Shankar Unni shankaru...@netscape.net wrote:
Our box has to deal with a few broken external switches that don't
auto-negotiate properly. (Our box is based on an Intel Rangeley Atom, with
the IGB driver for eth0/1, and we're running BB, more or less - tip of the
13 matches
Mail list logo
