[OpenWrt-Devel] [PATCH V2] [packages] libqmi: update to 1.8.0
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 Hauke ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel v1: update to libqmi 1.8.0 v2: fix packet source URL libqmi is now hosted on Freedesktop Signed-off-by: Tim Harvey thar...@gateworks.com Signed-off-by: Dirk Neukirchen dirkneukirc...@web.de --- libs/libqmi/Makefile | 7 --- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/libs/libqmi/Makefile b/libs/libqmi/Makefile index a9db3c0..14e6569 100644 --- a/libs/libqmi/Makefile +++ b/libs/libqmi/Makefile @@ -1,12 +1,12 @@ include $(TOPDIR)/rules.mk PKG_NAME:=libqmi -PKG_VERSION:=1.0 +PKG_VERSION:=1.8.0 PKG_RELEASE:=1 PKG_SOURCE:=libqmi-$(PKG_VERSION).tar.xz -PKG_SOURCE_URL:=@GNOME/libqmi/1.0/ -PKG_MD5SUM:=1e00d300616efc1bf8d3e8e541a69f73 +PKG_SOURCE_URL:=http://www.freedesktop.org/software/libqmi +PKG_MD5SUM:=1c4c64c0894f691632727363abec32b8 PKG_FIXUP:=autoreconf PKG_INSTALL:=1 @@ -19,6 +19,7 @@ define Package/libqmi CATEGORY:=Libraries DEPENDS:=+glib2 +zlib +kmod-usb-net-qmi-wwan TITLE:=Helper library and utils to talk to QMI enabled modems + URL:=http://www.freedesktop.org/wiki/Software/libqmi endef define Package/libqmi/description -- 1.9.rc1 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] kernel/generic-3.12: don't remove Intel-specific XHCI quirks
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
a/target/linux/generic/patches-3.12/811-pci_disable_usb_common_quirks.patch
b/target/linux/generic/patches-3.12/811-pci_disable_usb_common_quirks.patch
index ca0cc46..11c1d60 100644
--- a/target/linux/generic/patches-3.12/811-pci_disable_usb_common_quirks.patch
+++ b/target/linux/generic/patches-3.12/811-pci_disable_usb_common_quirks.patch
@@ -46,7 +46,7 @@
+#endif
--- a/drivers/usb/host/pci-quirks.h
+++ b/drivers/usb/host/pci-quirks.h
-@@ -4,20 +4,29 @@
+@@ -4,6 +4,14 @@
#ifdef CONFIG_PCI
void uhci_reset_hc(struct pci_dev *pdev, unsigned long base);
int uhci_check_and_reset_hc(struct pci_dev *pdev, unsigned long base);
@@ -61,9 +61,7 @@
int usb_amd_find_chipset_info(void);
void usb_amd_dev_put(void);
void usb_amd_quirk_pll_disable(void);
- void usb_amd_quirk_pll_enable(void);
--void usb_enable_intel_xhci_ports(struct pci_dev *xhci_pdev);
--void usb_disable_xhci_ports(struct pci_dev *xhci_pdev);
+@@ -13,11 +21,16 @@ void usb_disable_xhci_ports(struct pci_d
void sb800_prefetch(struct device *dev, int on);
#else
struct pci_dev;
@@ -74,7 +72,8 @@
static inline void usb_amd_quirk_pll_disable(void) {}
static inline void usb_amd_quirk_pll_enable(void) {}
static inline void usb_amd_dev_put(void) {}
--static inline void usb_disable_xhci_ports(struct pci_dev *xhci_pdev) {}
++static inline void usb_enable_intel_xhci_ports(struct pci_dev *xhci_pdev) {}
+ static inline void usb_disable_xhci_ports(struct pci_dev *xhci_pdev) {}
static inline void sb800_prefetch(struct device *dev, int on) {}
-#endif /* CONFIG_PCI */
+#endif
--
1.8.5.3
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Firstboot problems
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 (perhaps
avoiding using squashfs on nand completely) but for the moment
I have I got round the problem by patching ubox mount_root.c
as follows.
I have also had to add to modify include/image.mk, adding 16K
(which is the erase block size on the HH2B) to the call to padjffs2.
Ben
--- a/mount_root.c 2014-01-18 10:19:12.319136947 +0100
+++ b/mount_root.c 2014-01-18 10:18:21.149945597 +0100
@@ -381,6 +381,13 @@
return FS_JFFS2;
}
+ if (type == MTD_TYPE_NAND
+ deadc0de == 0x) {
+
+ LOG(jffs2 is ready\n);
+ return FS_JFFS2;
+ }
+
ERROR(No jffs2 marker was found\n);
return FS_NONE;
On Fri, 2014-02-07 at 03:00 +0100, Marco Antonio Mauro wrote:
Hi,
the router I'm working on at the moment, the DGN3500 lantiq platform,
has a strange issue: it won't create or save the configuration. I see
this in the logs:
[0.00] Linux version 3.10.26 (marcus905@experiment) (gcc
version 4.6.4 (OpenWrt/Linaro GCC 4.6-2013.05 r39286) ) #39 Thu Feb 6
19:19:14 CET 2014
[0.00] SoC: AR9 rev 1.1
[0.00] bootconsole [early0] enabled
[0.00] CPU revision is: 0001954c (MIPS 34Kc)
[0.00] MIPS: machine is DGN3500 - Netgear DGN3500
[0.00] Determined physical RAM map:
[0.00] memory: 0400 @ (usable)
[0.00] Initrd not found or empty - disabling initrd
[0.00] Zone ranges:
[0.00] Normal [mem 0x-0x03ff]
[0.00] Movable zone start for each node
[0.00] Early memory node ranges
[0.00] node 0: [mem 0x-0x03ff]
[0.00] On node 0 totalpages: 16384
[0.00] free_area_init_node: node 0, pgdat 8034e9d0,
node_mem_map 81002a80
[0.00] Normal zone: 128 pages used for memmap
[0.00] Normal zone: 0 pages reserved
[0.00] Normal zone: 16384 pages, LIFO batch:3
[0.00] Primary instruction cache 32kB, VIPT, 4-way, linesize 32 bytes.
[0.00] Primary data cache 16kB, 4-way, VIPT, no aliases,
linesize 32 bytes
[0.00] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[0.00] pcpu-alloc: [0] 0
[0.00] Built 1 zonelists in Zone order, mobility grouping on.
Total pages: 16256
[0.00] Kernel command line: console=ttyLTQ0,115200 init=/etc/preinit
...
[0.248000] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[0.256000] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME)
(CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
...
[0.304000] spi_gpio spi.4: master is unqueued, this is deprecated
[0.312000] m25p80 spi32766.0: found mx25l12805d, expected s25fl129p0
[0.316000] m25p80 spi32766.0: mx25l12805d (16384 Kbytes)
[0.32] 4 ofpart partitions found on MTD device spi32766.0
[0.328000] Creating 4 MTD partitions on spi32766.0:
[0.332000] 0x-0x0001 : uboot
[0.34] 0x0001-0x0002 : uboot-env
[0.348000] 0x0002-0x0003 : calibration
[0.352000] 0x0005-0x00ff : firmware
[0.36] 0x0017c7c8-0x00ff : rootfs
[0.364000] mtd: partition rootfs must either start or end on
erase block boundary or be smaller than an erase block -- forcing
read-only
[0.38] mtd: device 4 (rootfs) set to be root filesystem
[0.384000] mtd: partition rootfs_data created automatically,
ofs=0x73, len=0x8c
[0.392000] 0x0073-0x00ff : rootfs_data
...
[ 160.68] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985
not found at 0x: 0x7345 instead
[ 160.696000] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985
not found at 0x0004: 0x6f4d instead
[ 160.712000] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985
not found at 0x000c: 0x5035 instead
[ 160.728000] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985
not found at 0x0010: 0x3600 instead
[ 160.744000] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985
not found at 0x002c: 0x0041 instead
[ 160.76] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985
not found at 0x0030: 0x3200 instead
[ 160.776000] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985
not found at 0x0038: 0x0011 instead
[ 160.792000] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985
not found at 0x0040: 0x4572 instead
[ 160.808000] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985
not found at 0x0044: 0x4d6d instead
[ 160.824000] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985
not found at 0x0048: 0x3845 instead
[ 160.832000] jffs2: Further such events for
Re: [OpenWrt-Devel] Firstboot problems
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 start actually. Any suggestion? -- Marcus905 GPG pubkey: http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0x1FC0ECC932FE5FAC ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [RFC/RFT] netifd: Initial OpenVSwitch support
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 ifname br-ovs option proto dhcp Everything seems to work fine, the bridge is created and the interface is added to it. The only problem I;ve found is that if I change the device name from br-ovs to (for example) ovs at the next reboot the change is not applied. Also, the device section could benefit from an ovs-controller option to specify the controller for the switch. Tested with OpenVSwitch 2.0. R. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] DGN3500 (all known variants) factory and sysupgrade image building support
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 and a special windows flashing utility (allegedly present in the CD that came with the device -- but it's also compatible with the NSLU2 Upgrade_207_XP utility.) The special bootmode can be activated by turning the device on while holding the reset button pressed, then releasing it when the power led starts blinking red and green. Please notice that if using the 207 utility, it will always report that the flashing failed even though it completed successfully. Just power cycle the router manually after the utility reports the failure and OpenWRT will boot. This same utility (despite reporting failure in this case too) can revert a DGN3500 (any variant) to the appropriate stock Netgear firmware. This patch is a heavily modified version of a package I found on the OpenWRT forum with a couple fixes and features added -- mainly the generation of all the different image variants to support all known models directly, atm known variants are AnnexA-WW, AnnexA-NA and AnnexB-DE/GR. I tested the patch successfully on my device. Signed-off-by: Marco Antonio Mauro marcu...@gmail.com dgn3500-factory-sysupgrade-final.patch Description: Binary data ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Firstboot problems
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 deadc0de jffs2 magic is instead at 0x74, and that's where the partition should start actually. Any suggestion? I managed to fool the sercomm SBL by putting it slightly before the eraseblock start. I submitted the patch to the list, it works perfect now! Obviously the same checksum, signature and workaround have to be done for the sysupgrade images too -- I took care of that in the same patch. Now only the ath9k wifi needs to be fixed and then we have another (the absolute second maybe) fully working OpenWRT DSL router! -- Marcus905 GPG pubkey: http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0x1FC0ECC932FE5FAC ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Firstboot problems
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 signature and checksum needed for the bootloader there, and the deadc0de jffs2 magic is instead at 0x74, and that's where the partition should start actually. Any suggestion? I managed to fool the sercomm SBL by putting it slightly before the eraseblock start. I submitted the patch to the list, it works perfect now! Obviously the same checksum, signature and workaround have to be done for the sysupgrade images too -- I took care of that in the same patch. Now only the ath9k wifi needs to be fixed and then we have another (the absolute second maybe) fully working OpenWRT DSL router! My earlier reply was completely off. I misread nand flash for some reason. Sorry! Glad you fixed it. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] OpenWrt signaling early boot cycle (blinking LED) all the time on 1st boot
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 after preparing JFFS2 partition LED keeps blinking. On another boot this problem doesn't occur. My guess is that set_state (/etc/diag.sh) is never called with done argument on the first boot. -- Rafał ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Mikrotik RB951Ui-2HnD
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 most things seem to be working. I'm uncertain how to enable or toggle the LED's from user space so some pointers there would be appreciated. The thing that is worrying me the most is the USB does not appear to work. I can toggle the power via the GPIO pin, but no devices seem to be detected. dmesg shows 0.09] MIPS: machine is MikroTik RouterBOARD 951Ui-2HnD so I know that the board is been detected correctly. and [5.86] usbcore: registered new interface driver usbfs [5.97] usbcore: registered new interface driver hub [6.05] usbcore: registered new device driver usb [6.13] leds-gpio: probe of leds-gpio failed with error -16 [8.21] eth0: link up (100Mbps/Full duplex) [9.04] eth0: link down [ 10.29] NET: Registered protocol family 10 [ 10.35] NET: Registered protocol family 8 [ 10.40] NET: Registered protocol family 20 [ 10.46] nf_conntrack version 0.5.0 (1976 buckets, 7904 max) [ 10.54] ip6_tables: (C) 2000-2006 Netfilter Core Team [ 10.63] usbcore: registered new interface driver cdc_wdm [ 10.70] Loading modules backported from Linux version master-2014-01-23-0-g62c147d [ 10.79] Backport generated by backports.git backports-20140124-0- g1256d3e [ 10.88] ip_tables: (C) 2000-2006 Netfilter Core Team [ 10.97] usbcore: registered new interface driver usbserial [ 11.04] usbcore: registered new interface driver usbserial_generic [ 11.12] usbserial: USB Serial support registered for generic seems to indicate that the usb core is running but lsusb displays and error and no ttyUSB0 devices appear in /dev/ nor can I find them in the /sys tree Am I missing anything as I can't seem to talk to my PL2303 usb to serial converter ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Mikrotik RB951Ui-2HnD - further results
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 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Mikrotik RB951Ui-2HnD - further results
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 mach-rb95x.c and make that change. -- Davey On Fri, Feb 7, 2014 at 4:01 PM, Robin Gilham robin.gil...@gmail.com wrote: 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 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [RFC/RFT] netifd: Initial OpenVSwitch support
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, Helmut Schaa wrote: What if you write the config file after boot and run /etc/init.d/network reload? Does it also end up in a loop? Just tried, no, it does not loop. Ok, this helps a lot I guess. Maybe OVS is not up and running yet during boot or not yet initialized? Forgot to point out that it does not loop but it also does not work as expected. basically the bridge is not created. But it works if you create it manually with ovs-vsctl? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
