On 06.02.2014 23:42, Hauke Mehrtens wrote:
On 12/12/2013 07:05 PM, Tim Harvey wrote:
Signed-off-by: Tim Harvey thar...@gateworks.com
---
There is no libqmi-1.8.0.tar.xz on the gnome ftp server.
This url returns 404:
http://ftp.gnome.org/pub/GNOME/sources/libqmi/1.8/libqmi-1.8.0.tar.xz
The symbols are required to build the xhci-pci module.
Probably this applies to kernel 3.13 as well, however, I only had the
chance to test on 3.12.
---
.../generic/patches-3.12/811-pci_disable_usb_common_quirks.patch | 9 -
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git
Hi,
I had a similar problem on the BT Home Hub 2B, which also
has nand flash. The problem as you say seems to be that
mount_root assume that the deadc0de will be at the start
of the block where it would be for nor flash. I expect others
will have a better idea of the right way to solve this
I think I found out the cause. The partition rootfs data gets created
after the squashfs one at 0x73 in my case, but there there's the
sercomm signature and checksum needed for the bootloader there, and
the deadc0de jffs2 magic is instead at 0x74, and that's where the
partition should
On 29/11/13 16:24, Helmut Schaa wrote:
I'd appreciate any testing beside my own :D
Hi, I did some testing on some alix boards. The config
I'm using is the following:
config device
option name br-ovs
option type ovs
list ifname eth0
config interface wan
option
This patch adds factory image building for the DGN3500, all variants,
and fixes sysupgrade images to make them play nice with the sercomm
secondary boot loader.
The factory images can be used directly in the update dialog in the
interface of the stock firmware and via the special Sercomm bootmode
On Fri, Feb 7, 2014 at 12:38 PM, Marco Antonio Mauro marcu...@gmail.com wrote:
I think I found out the cause. The partition rootfs data gets created
after the squashfs one at 0x73 in my case, but there there's the
sercomm signature and checksum needed for the bootloader there, and
the
On Fri, 2014-02-07 at 23:33 +0100, Marco Antonio Mauro wrote:
On Fri, Feb 7, 2014 at 12:38 PM, Marco Antonio Mauro marcu...@gmail.com
wrote:
I think I found out the cause. The partition rootfs data gets created
after the squashfs one at 0x73 in my case, but there there's the
sercomm
I'm using bcm47xx.
On the first boot after installation OpenWrt starts linking my LED and
never stops. It starts around
Press the [f] key and hit [enter] to enter failsafe mode
Press the [1], [2], [3] or [4] key and hit [enter] to select the debug level
Ofc I was waiting for few minutes, even
Hi there,
I am attempting to compile openWRT for the Mikrotik RB951Ui-2HnD router. I
have applied path /patch/4773/ to my development trunk. I can compile and boot
the initramfs image, I have been able to write the image to to flash and boot
off my flash image. I can log into the router and
It turns out that I needed to do the following
opkg update
opkg install kmod-usb2
insmod ehci-hcd
because the kernel did not have it built in. Can't believe I have been at this
for a week, I can finally get the USB to work. Still not certain on the LEDs
Robin
You can toggle the leds in /sys/class/leds or
/sys/devices/platform/leds-gpio/leds,
example: echo 1
/sys/devices/platform/leds-gpio/leds/rb951ui:lan:port2/brightness
I just noticed that patch has a typo for the LED's..
rb951ui:lan:port5 should be GPIO 16 not 21, you will need to update
your
ok, excuse the ignorance, i see the patch, i see the git branch, hows this
branch get integrated to openwrt ?
On Tue, Feb 4, 2014 at 4:31 AM, Helmut Schaa helmut.sc...@googlemail.comwrote:
On Tue, Feb 4, 2014 at 9:16 AM, Roberto Riggio
roberto.rig...@create-net.org wrote:
On 04/02/14 09:09,
13 matches
Mail list logo
