I think the layout of the x86 filesystem needs to change in order to
support sysupgrade properly. Personally I'm using an alix2 board with
the ext4 filesystem (trunk image). I've not had much luck getting
reliable sysupgrades when using a pure ext4 filesystem. It works only
sporadically. More o
This patch makes several changes with uboot-envtools package:
* bumps to version 2011.12
* adds md5sum
* creates a menu so it will look better in "make menuconfig"
* adds /etc/fw_env.config to conffile
* adds /etc/config/ubootenv to conffile
* refresh patches
* removes init script because w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Applied in r31270, thanks.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk+HbmsACgkQdputYINPTPMR2ACgkx7DPQ1Fl2z7NjyOCyc3Vm6G
j+kAoIR17bALDooABY793sg
The alix2 target has the VGA console for grub enabled by default. This
prevents the grub menu from appearing on bootup. It is disabled by
default for the other embedded x86 platforms. This patch corrects that
behavior for the alix2 target.
Signed-off-by: Adam Gensler
Index: target/linux/x86/
Hi John,
Then perhaps gpioctl and gpio-dev should be marked as ¨obsolete¨ in the
config or removed entirely? As is, it´s broken - better to have old but
working code?
Regards,
Jeroen
On 04/12/2012 01:03 AM, John Crispin wrote:
On 12/04/12 08:59, Jeroen van Bemmel wrote:
Hello,
I needed to
From: Karl Palsson
Use the service helper scripts to build a simple init script for the
mosquitto broker. To make sure that the standard shipped config file
works, add a mosquitto user if not found.
Signed-off-by: Karl Palsson
---
net/mosquitto/Makefile | 24
On 04/02/2012 05:16 PM, Florian Fainelli wrote:
The configure scripts fails complaining it could not find neither glib
2.0 nor libxml-2.0. Can you please start from a fresh build and test
again if that works for you?
This is what I just did:
1) make distclean
2) svn up
3) enable xorg feed and
On 12/04/12 08:59, Jeroen van Bemmel wrote:
> Hello,
>
> I needed to determine which GPIO pin was connected to the reset button,
> so I figured I´d use gpioctl to pull the status. However, /dev/gpio did
> not exist; I traced this and found that the probe function was not being
> called. Adding a p
Hello,
I needed to determine which GPIO pin was connected to the reset button,
so I figured I´d use gpioctl to pull the status. However, /dev/gpio did
not exist; I traced this and found that the probe function was not being
called. Adding a platform_device called "GPIODEV" fixes this:
static
