Re: [OpenWrt-Devel] [PATCH 1/3] IEEE802154 WPAN new files
On 06/25/2012 03:50 PM, Hauke Mehrtens wrote: On 06/22/2012 08:18 AM, xian...@openmobilefree.net wrote: From: Xiangfu --- create mode 100644 target/linux/generic/files/drivers/ieee802154/adf7242.c create mode 100644 target/linux/generic/files/drivers/ieee802154/at86rf230.c create mode 100644 target/linux/generic/files/drivers/ieee802154/at86rf230.h create mode 100644 target/linux/generic/files/drivers/ieee802154/cc2420.c create mode 100644 target/linux/generic/files/drivers/ieee802154/fakelb.c create mode 100644 target/linux/generic/files/drivers/ieee802154/serial.c create mode 100644 target/linux/generic/files/drivers/ieee802154/spi_atben.c create mode 100644 target/linux/generic/files/drivers/ieee802154/spi_atusb.c create mode 100644 target/linux/generic/files/include/linux/if_ieee802154.h create mode 100644 target/linux/generic/files/include/linux/spi/at86rf230.h create mode 100644 target/linux/generic/files/include/net/mac802154.h create mode 100644 target/linux/generic/files/net/mac802154/Kconfig create mode 100644 target/linux/generic/files/net/mac802154/Makefile create mode 100644 target/linux/generic/files/net/mac802154/beacon.c create mode 100644 target/linux/generic/files/net/mac802154/beacon_hash.c create mode 100644 target/linux/generic/files/net/mac802154/beacon_hash.h create mode 100644 target/linux/generic/files/net/mac802154/mac802154.h create mode 100644 target/linux/generic/files/net/mac802154/mac_cmd.c create mode 100644 target/linux/generic/files/net/mac802154/main.c create mode 100644 target/linux/generic/files/net/mac802154/mib.c create mode 100644 target/linux/generic/files/net/mac802154/mib.h create mode 100644 target/linux/generic/files/net/mac802154/monitor.c create mode 100644 target/linux/generic/files/net/mac802154/rx.c create mode 100644 target/linux/generic/files/net/mac802154/scan.c create mode 100644 target/linux/generic/files/net/mac802154/smac.c create mode 100644 target/linux/generic/files/net/mac802154/tx.c create mode 100644 target/linux/generic/files/net/mac802154/wpan.c create mode 100644 target/linux/generic/files/net/zigbee/Kconfig create mode 100644 target/linux/generic/files/net/zigbee/Makefile create mode 100644 target/linux/generic/files/net/zigbee/af_zigbee.c create mode 100644 target/linux/generic/files/net/zigbee/dgram.c The kernel 3.3 already contains most of these files, why do you copy them to target/linux/generic/files ? Hi Hauke I didn't found them under 3.3.8 tar ball. Where are these files exactly from, is this from a more recent kernel than 3.3? Those files are from linux-zigbee: http://linux-zigbee.git.sourceforge.net/git/gitweb.cgi?p=linux-zigbee/kernel;a=tree;f=net/mac802154;h=8f0c8aa0138afc9ee59b8923e48827a4574a2597;hb=9155ba3a1c13ba74478552a096940de9eefc4249 Xiangfu Hauke ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 0/3] IEEE802154 WPAN Support
Hi John Forget to mention. when I test this. I have to insert the atUSB before system boot. Do you have kernel message at serial console? that will help debug. what modules you have include in image? Xiangfu On 06/24/2012 02:06 PM, John Crispin wrote: Hi, i tested on a tplink 3020 which reboots directly after instering these modules and a lantiq unit which segfaults when plugging the dongle John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 0/3] IEEE802154 WPAN Support
On 06/25/2012 05:25 PM, Felix Fietkau wrote: Xiangfu (3): > IEEE802154 WPAN new files > IEEE802154 WPAN patch > IEEE802154 WPAN kernel module makefile Have you considered using compat-wireless to backport 802.15.4 support? It would probably get a lot less messy than patching the whole thing into the kernel tree. Hi Felix Sorry, I don't know this 'compat-wireless', please give me more information on this. Do you mean I need work on 'openwrt/package/mac80211' ? Thanks Xiangfu ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 0/3] IEEE802154 WPAN Support
On 2012-06-29 9:21 AM, Xiangfu Liu wrote: > On 06/25/2012 05:25 PM, Felix Fietkau wrote: >>> Xiangfu (3): >>> > IEEE802154 WPAN new files >>> > IEEE802154 WPAN patch >>> > IEEE802154 WPAN kernel module makefile >> Have you considered using compat-wireless to backport 802.15.4 support? >> It would probably get a lot less messy than patching the whole thing >> into the kernel tree. > > Hi Felix > > Sorry, I don't know this 'compat-wireless', please give me more information > on this. > > Do you mean I need work on 'openwrt/package/mac80211' ? You could make a package that's based on that package and the compat-wireless sources that it uses. Not sure if it's a good idea to fold it into the mac80211 package, but I do think it should at least be something that's built outside of the kernel tree. - Felix ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 2/2] [BRCM63XX] Detect alternative "cfe-" version bootloaders (found in 963281T_TEF board)
Hello, On Wednesday 27 June 2012 10:54:46 Álvaro Fernández Rojas wrote: > Correctly detect CFE bootloaders starting with "cfe-" instead of "cfe-v". > > Signed-off-by: Álvaro Fernández Rojas > > Index: target/linux/brcm63xx/patches-3.3/802-cfe_version_mod.patch > === > --- target/linux/brcm63xx/patches-3.3/802-cfe_version_mod.patch > (revisión: 0) > +++ target/linux/brcm63xx/patches-3.3/802-cfe_version_mod.patch > (revisión: 0) > @@ -0,0 +1,30 @@ > +--- a/arch/mips/bcm63xx/boards/board_bcm963xx.c > b/arch/mips/bcm63xx/boards/board_bcm963xx.c > +@@ -2882,6 +2882,12 @@ void __init board_prom_init(void) > + if (!memcmp(cfe, "cfe-v", 5)) > + snprintf(cfe_version, sizeof(cfe_version), "%u.%u.%u-%u.%u", > + cfe[5], cfe[6], cfe[7], cfe[8], cfe[9]); > ++else if (!memcmp(cfe, "cfe-", 4)) { > ++for(i = 0; i < 0x10; i++) { > ++cfe_version[i] = cfe[4 + i]; > ++} > ++cfe_version[i] = 0; > ++} Cannot we use the following: snprintf(cfe_version, 16), "%s", (char *)&cfe[4]); or maybe there was a reason for this loop? Btw, I'd prefer using 16 instead of 0x10 ;) > + else > + strcpy(cfe_version, "unknown"); > + printk(KERN_INFO PFX "CFE version: %s\n", cfe_version); > +--- a/drivers/mtd/bcm63xxpart.c > b/drivers/mtd/bcm63xxpart.c > +@@ -55,10 +55,10 @@ static int bcm63xx_detect_cfe(struct mtd > + if (ret) > + return ret; > + > +-if (strncmp("cfe-v", buf, 5) == 0) > ++if (strncmp("cfe-", buf, 4) == 0) > + return 0; > + > +-/* very old CFE's do not have the cfe-v string, so check for magic */ > ++/* very old CFE's do not have the cfe- string, so check for magic */ > + ret = mtd_read(master, BCM63XX_CFE_MAGIC_OFFSET, 8, &retlen, > +(void *)buf); > + buf[retlen] = 0; > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [RFC] ar71xx: add support for the TP-Link TL-WDR4310 v1.0
The hardware for TP-Link TL-WDR4300 v1.1 and TL-WDR4310 v1.0 is identical, but requires different firmware headers: TL-WDR4300: 0040 43 00 00 01 00 00 00 01 00 00 00 00 76 fb 83 40 |C...v..@| TL-WDR4310: 0040 43 10 00 01 00 00 00 01 00 00 00 00 38 2b 50 6c |C...8+Pl| Signed-off-by: Stefan Lippers-Hollmann Cc: Gabor Juhos --- UNTESTED, please don't apply until anyone with TL-WDR4310 hardware can confirm this to be functional. Update: According to http://wiki.openwrt.org/toh/tp-link/tl-wdr4310, these changes seem to be sufficient. linux/ar71xx/base-files/lib/ar71xx.sh|2 +- linux/ar71xx/generic/profiles/tp-link.mk |2 +- linux/ar71xx/image/Makefile |1 + 3 files changed, 3 insertions(+), 2 deletions(-) Index: target/linux/ar71xx/base-files/lib/ar71xx.sh === --- target/linux/ar71xx/base-files/lib/ar71xx.sh(revision 32499) +++ target/linux/ar71xx/base-files/lib/ar71xx.sh(working copy) @@ -123,7 +123,7 @@ "342000"*) model="TP-Link TL-MR3420" ;; - "43"*) + "43"*|"431000"*) model="TP-Link TL-WDR4300" ;; *) Index: target/linux/ar71xx/generic/profiles/tp-link.mk === --- target/linux/ar71xx/generic/profiles/tp-link.mk (revision 32499) +++ target/linux/ar71xx/generic/profiles/tp-link.mk (working copy) @@ -95,7 +95,7 @@ define Profile/TLWDR4300 - NAME:=TP-LINK TL-WDR4300 + NAME:=TP-LINK TL-WDR4300/ TL-WDR4310 PACKAGES:=kmod-usb-core kmod-usb2 kmod-ledtrig-usbdev endef Index: target/linux/ar71xx/image/Makefile === --- target/linux/ar71xx/image/Makefile (revision 32499) +++ target/linux/ar71xx/image/Makefile (working copy) @@ -977,6 +977,7 @@ tlwdr4300_cmdline=board=TL-WDR4300 console=ttyS0,115200 define Image/Build/Profile/TLWDR4300 $(call Image/Build/Template/$(fs_64kraw)/$(1),TPLINK-LZMA,tl-wdr4300-v1,$(tlwdr4300_cmdline),0x4301,1,8Mlzma) + $(call Image/Build/Template/$(fs_64kraw)/$(1),TPLINK-LZMA,tl-wdr4310-v1,$(tlwdr4300_cmdline),0x4311,1,8Mlzma) endef wndr3700_cmdline=board=WNDR3700 console=ttyS0,115200 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 2/2] [BRCM63XX] Detect alternative "cfe-" version bootloaders (found in 963281T_TEF board)
Yeah, we can use snprintf ;) Signed-off-by: Álvaro Fernández Rojas Index: target/linux/brcm63xx/patches-3.3/802-cfe_version_mod.patch === --- target/linux/brcm63xx/patches-3.3/802-cfe_version_mod.patch (revisión: 0) +++ target/linux/brcm63xx/patches-3.3/802-cfe_version_mod.patch (revisión: 0) @@ -0,0 +1,26 @@ +--- a/arch/mips/bcm63xx/boards/board_bcm963xx.c b/arch/mips/bcm63xx/boards/board_bcm963xx.c +@@ -2882,6 +2882,8 @@ void __init board_prom_init(void) + if (!memcmp(cfe, "cfe-v", 5)) + snprintf(cfe_version, sizeof(cfe_version), "%u.%u.%u-%u.%u", +cfe[5], cfe[6], cfe[7], cfe[8], cfe[9]); ++ else if (!memcmp(cfe, "cfe-", 4)) ++ snprintf(cfe_version, 16, "%s", (char *) &cfe[4]); + else + strcpy(cfe_version, "unknown"); + printk(KERN_INFO PFX "CFE version: %s\n", cfe_version); +--- a/drivers/mtd/bcm63xxpart.c b/drivers/mtd/bcm63xxpart.c +@@ -55,10 +55,10 @@ static int bcm63xx_detect_cfe(struct mtd + if (ret) + return ret; + +- if (strncmp("cfe-v", buf, 5) == 0) ++ if (strncmp("cfe-", buf, 4) == 0) + return 0; + +- /* very old CFE's do not have the cfe-v string, so check for magic */ ++ /* very old CFE's do not have the cfe- string, so check for magic */ + ret = mtd_read(master, BCM63XX_CFE_MAGIC_OFFSET, 8, &retlen, + (void *)buf); + buf[retlen] = 0; El 29/06/2012 14:59, Florian Fainelli escribió: > Hello, > > On Wednesday 27 June 2012 10:54:46 Álvaro Fernández Rojas wrote: >> Correctly detect CFE bootloaders starting with "cfe-" instead of "cfe-v". >> >> Signed-off-by: Álvaro Fernández Rojas >> >> Index: target/linux/brcm63xx/patches-3.3/802-cfe_version_mod.patch >> === >> --- target/linux/brcm63xx/patches-3.3/802-cfe_version_mod.patch >> (revisión: 0) >> +++ target/linux/brcm63xx/patches-3.3/802-cfe_version_mod.patch >> (revisión: > 0) >> @@ -0,0 +1,30 @@ >> +--- a/arch/mips/bcm63xx/boards/board_bcm963xx.c >> b/arch/mips/bcm63xx/boards/board_bcm963xx.c >> +@@ -2882,6 +2882,12 @@ void __init board_prom_init(void) >> +if (!memcmp(cfe, "cfe-v", 5)) >> +snprintf(cfe_version, sizeof(cfe_version), "%u.%u.%u-%u.%u", >> + cfe[5], cfe[6], cfe[7], cfe[8], cfe[9]); >> ++ else if (!memcmp(cfe, "cfe-", 4)) { >> ++ for(i = 0; i < 0x10; i++) { >> ++ cfe_version[i] = cfe[4 + i]; >> ++ } >> ++ cfe_version[i] = 0; >> ++ } > > Cannot we use the following: > > snprintf(cfe_version, 16), "%s", (char *)&cfe[4]); > > or maybe there was a reason for this loop? Btw, I'd prefer using 16 instead > of > 0x10 ;) > >> +else >> +strcpy(cfe_version, "unknown"); >> +printk(KERN_INFO PFX "CFE version: %s\n", cfe_version); >> +--- a/drivers/mtd/bcm63xxpart.c >> b/drivers/mtd/bcm63xxpart.c >> +@@ -55,10 +55,10 @@ static int bcm63xx_detect_cfe(struct mtd >> +if (ret) >> +return ret; >> + >> +- if (strncmp("cfe-v", buf, 5) == 0) >> ++ if (strncmp("cfe-", buf, 4) == 0) >> +return 0; >> + >> +- /* very old CFE's do not have the cfe-v string, so check for magic */ >> ++ /* very old CFE's do not have the cfe- string, so check for magic */ >> +ret = mtd_read(master, BCM63XX_CFE_MAGIC_OFFSET, 8, &retlen, >> + (void *)buf); >> +buf[retlen] = 0; >> ___ >> openwrt-devel mailing list >> openwrt-devel@lists.openwrt.org >> https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH 1/1, V1] Bump klish version to 1.6.0
Bump klish version to 1.6.0. This version removes its dependency on the C++ library tinyxml as it now implements a new XML backend that support some common C-based XML libraries: libxml2, expat and libroxml. A config option is defined to let the user select the XML backend he wants to use. Since libroxml is not yet in the OpenWRT package tree, it's not yet possible to select this XML backend. Signed-off-by: Emmanuel Deloget Index: packages/utils/klish/Config.in === --- packages/utils/klish/Config.in (révision 0) +++ packages/utils/klish/Config.in (révision 0) @@ -0,0 +1,16 @@ +choice +prompt "XML Backend" +depends on PACKAGE_klish +default KLISH_XML_BACKEND_EXPAT +help + Select the Klish XML backend. Only two backends are currently + supported by both OpenWRT and klish: the expat XML parser and + the well known Gnome libxml2. It's safe to chose either of them. + +config KLISH_XML_BACKEND_LIBEXPAT + bool "Expat XML parser" + +config KLISH_XML_BACKEND_LIBXML2 + bool "Gnome libxml2" + +endchoice Index: packages/utils/klish/Makefile === --- packages/utils/klish/Makefile (révision 32525) +++ packages/utils/klish/Makefile (copie de travail) @@ -8,12 +8,12 @@ include $(TOPDIR)/rules.mk PKG_NAME:=klish -PKG_VERSION:=1.5.4 +PKG_VERSION:=1.6.0 PKG_RELEASE:=1 PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.bz2 PKG_SOURCE_URL:=http://klish.googlecode.com/files -PKG_MD5SUM:=c98a1c65f7538c3f4687c6f8039295df +PKG_MD5SUM:=dad910b6b7d160177317bfe8f145ffd1 PKG_INSTALL:=1 @@ -28,7 +28,9 @@ define Package/klish $(call Package/klish/default,main tool) - DEPENDS:=+libstdcpp + DEPENDS:= \ + +KLISH_XML_BACKEND_LIBEXPAT:libexpat \ + +KLISH_XML_BACKEND_LIBXML2:libxml2 endef define Package/konf @@ -56,6 +58,17 @@ More information about these tools is to be found on the klish web site. endef +define Package/klish/config + source "$(SOURCE)/Config.in" +endef + +ifeq ($(strip $(CONFIG_KLISH_XML_BACKEND_LIBEXPAT)),y) + CONFIGURE_ARGS += --with-libexpat +endif +ifeq ($(strip $(CONFIG_KLISH_XML_BACKEND_LIBXML2)),y) + CONFIGURE_ARGS += --with-libxml2 +endif + define Package/klish/install $(INSTALL_DIR) $(1)/usr/bin $(INSTALL_BIN) $(PKG_INSTALL_DIR)/usr/bin/clish $(1)/usr/bin/ ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Seagate FreeAgent GoFlex Home / SATA not working
today i installed via serial openwrt trunk r32520 on this device, images are from: http://downloads.openwrt.org/snapshots/trunk/kirkwood openwrt-kirkwood-uImage openwrt-kirkwood--jffs2-128k.img picture: http://i32.tinypic.com/2ntiqkj.jpg installing via uboot / nandwrite: https://lists.openwrt.org/pipermail/openwrt-devel/2011-February/009760.html device is working fine, but SATA is not working. Florian suggested to add "sata_mv" to platform_code, but is'nt this already done? see dmesg / lsmod bye, bastian dmesg: [0.00] Booting Linux on physical CPU 0 [0.00] Linux version 3.3.8 (fnord@tschunk) (gcc version 4.6.3 20120201 (prerelease) (Linaro GCC 4.6-2012.02) ) #1 Fri Jun 29 03:26:51 UTC 2012 [0.00] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977 [0.00] CPU: VIVT data cache, VIVT instruction cache [0.00] Memory policy: ECC disabled, Data cache writeback [0.00] On node 0 totalpages: 32768 [0.00] free_area_init_node: node 0, pgdat c0363350, node_mem_map c0372000 [0.00] Normal zone: 256 pages used for memmap [0.00] Normal zone: 0 pages reserved [0.00] Normal zone: 32512 pages, LIFO batch:7 [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: 32512 [0.00] Kernel command line: console=ttyS0,115200 root=/dev/mtdblock2 rw rootfstype=jffs2 [0.00] PID hash table entries: 512 (order: -1, 2048 bytes) [0.00] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) [0.00] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) [0.00] Memory: 128MB = 128MB total [0.00] Memory: 126380k/126380k available, 4692k reserved, 0K highmem [0.00] Virtual kernel memory layout: [0.00] vector : 0x - 0x1000 ( 4 kB) [0.00] fixmap : 0xfff0 - 0xfffe ( 896 kB) [0.00] vmalloc : 0xc880 - 0xff00 ( 872 MB) [0.00] lowmem : 0xc000 - 0xc800 ( 128 MB) [0.00] modules : 0xbf00 - 0xc000 ( 16 MB) [0.00] .text : 0xc0008000 - 0xc0326000 (3192 kB) [0.00] .init : 0xc0326000 - 0xc0345000 ( 124 kB) [0.00] .data : 0xc0346000 - 0xc0363a00 ( 119 kB) [0.00].bss : 0xc0363a24 - 0xc0371970 ( 56 kB) [0.00] NR_IRQS:114 [0.00] gpiochip_add: registered GPIOs 0 to 31 on device: orion_gpio0 [0.00] gpiochip_add: registered GPIOs 32 to 49 on device: orion_gpio1 [0.00] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 21474ms [ 15.267545] Calibrating delay loop... 1191.11 BogoMIPS (lpj=5955584) [ 15.357534] pid_max: default: 32768 minimum: 301 [ 15.357677] Mount-cache hash table entries: 512 [ 15.357990] CPU: Testing write buffer coherency: ok [ 15.358244] Setting up static identity map for 0x278158 - 0x278194 [ 15.359949] NET: Registered protocol family 16 [ 15.362195] Kirkwood: MV88F6281-A1, TCLK=2. [ 15.362211] Feroceon L2: Enabling L2 [ 15.362248] Feroceon L2: Cache support initialised. [ 15.363354] initial MPP regs: 0111 3322 0010 [ 15.363377] final MPP regs: 0111 3322 [ 15.369767] bio: create slab at 0 [ 15.370669] SCSI subsystem initialized [ 15.371230] usbcore: registered new interface driver usbfs [ 15.371369] usbcore: registered new interface driver hub [ 15.371518] usbcore: registered new device driver usb [ 15.372617] Switching to clocksource orion_clocksource [ 15.374171] NET: Registered protocol family 2 [ 15.374309] IP route cache hash table entries: 1024 (order: 0, 4096 bytes) [ 15.374597] TCP established hash table entries: 4096 (order: 3, 32768 bytes) [ 15.374697] TCP bind hash table entries: 4096 (order: 2, 16384 bytes) [ 15.374751] TCP: Hash tables configured (established 4096 bind 4096) [ 15.374760] TCP reno registered [ 15.374770] UDP hash table entries: 256 (order: 0, 4096 bytes) [ 15.374793] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) [ 15.374963] NET: Registered protocol family 1 [ 15.374990] PCI: CLS 0 bytes, default 32 [ 15.376479] squashfs: version 4.0 (2009/01/31) Phillip Lougher [ 15.376494] JFFS2 version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc. [ 15.376828] msgmni has been set to 246 [ 15.376860] io scheduler noop registered [ 15.376868] io scheduler deadline registered (default) [ 15.91] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled [ 15.467243] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A [ 15.799420] console [ttyS0] enabled [ 15.804393] NAND device: Manufacturer ID: 0x98, Chip ID: 0xda (Toshiba NAND 256MiB 3,3V 8-bit) [ 15.813068] Scanning d
Re: [OpenWrt-Devel] [PATCH 1/3] IEEE802154 WPAN new files
On 06/29/2012 09:05 AM, Xiangfu Liu wrote: > On 06/25/2012 03:50 PM, Hauke Mehrtens wrote: >> On 06/22/2012 08:18 AM, xian...@openmobilefree.net wrote: >>> From: Xiangfu >>> >>> --- >>> create mode 100644 >>> target/linux/generic/files/drivers/ieee802154/adf7242.c >>> create mode 100644 >>> target/linux/generic/files/drivers/ieee802154/at86rf230.c >>> create mode 100644 >>> target/linux/generic/files/drivers/ieee802154/at86rf230.h >>> create mode 100644 >>> target/linux/generic/files/drivers/ieee802154/cc2420.c >>> create mode 100644 >>> target/linux/generic/files/drivers/ieee802154/fakelb.c >>> create mode 100644 >>> target/linux/generic/files/drivers/ieee802154/serial.c >>> create mode 100644 >>> target/linux/generic/files/drivers/ieee802154/spi_atben.c >>> create mode 100644 >>> target/linux/generic/files/drivers/ieee802154/spi_atusb.c >>> create mode 100644 >>> target/linux/generic/files/include/linux/if_ieee802154.h >>> create mode 100644 >>> target/linux/generic/files/include/linux/spi/at86rf230.h >>> create mode 100644 target/linux/generic/files/include/net/mac802154.h >>> create mode 100644 target/linux/generic/files/net/mac802154/Kconfig >>> create mode 100644 target/linux/generic/files/net/mac802154/Makefile >>> create mode 100644 target/linux/generic/files/net/mac802154/beacon.c >>> create mode 100644 >>> target/linux/generic/files/net/mac802154/beacon_hash.c >>> create mode 100644 >>> target/linux/generic/files/net/mac802154/beacon_hash.h >>> create mode 100644 >>> target/linux/generic/files/net/mac802154/mac802154.h >>> create mode 100644 target/linux/generic/files/net/mac802154/mac_cmd.c >>> create mode 100644 target/linux/generic/files/net/mac802154/main.c >>> create mode 100644 target/linux/generic/files/net/mac802154/mib.c >>> create mode 100644 target/linux/generic/files/net/mac802154/mib.h >>> create mode 100644 target/linux/generic/files/net/mac802154/monitor.c >>> create mode 100644 target/linux/generic/files/net/mac802154/rx.c >>> create mode 100644 target/linux/generic/files/net/mac802154/scan.c >>> create mode 100644 target/linux/generic/files/net/mac802154/smac.c >>> create mode 100644 target/linux/generic/files/net/mac802154/tx.c >>> create mode 100644 target/linux/generic/files/net/mac802154/wpan.c >>> create mode 100644 target/linux/generic/files/net/zigbee/Kconfig >>> create mode 100644 target/linux/generic/files/net/zigbee/Makefile >>> create mode 100644 target/linux/generic/files/net/zigbee/af_zigbee.c >>> create mode 100644 target/linux/generic/files/net/zigbee/dgram.c >> >> The kernel 3.3 already contains most of these files, why do you copy >> them to target/linux/generic/files ? > > Hi Hauke > > I didn't found them under 3.3.8 tar ball. Yes I haven't check correctly, but drivers/ieee802154/fakehard.c is in that tar ball, but not the rest. As Felx said something like compat-wireless for ieee802154/zigbee or integrating it into compat-wireless would be the best solution also if you want to use a recent version of this stack in some other environments without the need of using the most recent rc kernel. >> Where are these files exactly from, is this from a more recent kernel >> than 3.3? > > Those files are from linux-zigbee: > > http://linux-zigbee.git.sourceforge.net/git/gitweb.cgi?p=linux-zigbee/kernel;a=tree;f=net/mac802154;h=8f0c8aa0138afc9ee59b8923e48827a4574a2597;hb=9155ba3a1c13ba74478552a096940de9eefc4249 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Captive Portal with OAuth support?
> Is there anyone in this mailing list tried with this idea? Which > should > I start from? we have this included since a long time: https://github.com/bittorf/kalua a good starting point is: https://github.com/livibetter/bash-oauth/blob/master/OAuth.sh bye, bastian. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Seagate FreeAgent GoFlex Home / SATA not working / Bootloader
> http://downloads.openwrt.org/snapshots/trunk/kirkwood > openwrt-kirkwood-uImage > openwrt-kirkwood--jffs2-128k.img just for documentation: bootloader is from here: http://www.cyrius.com/debian/kirkwood/sheevaplug/uboot-upgrade.html http://people.debian.org/~tbm/u-boot/2011.12-3/dockstar/u-boot.kwb bye, bastian. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Seagate FreeAgent GoFlex Home / klog-line missing / Dockstart VS GoFlex
> dmesg: > [0.00] Booting Linux on physical CPU 0 > [0.00] Linux version 3.3.8 (fnord@tschunk) (gcc version > 4.6.3 20120201 (prerelease) (Linaro GCC 4.6-2012.02) ) #1 Fri Jun > 29 03:26:51 UTC 2012 > [0.00] CPU: Feroceon 88FR131 [56251311] revision 1 > (ARMv5TE), cr=00053977 > [0.00] CPU: VIVT data cache, VIVT instruction cache by accident one important line was missing: [0.00] Machine: Seagate FreeAgent DockStar > [0.00] Memory policy: ECC disabled, Data cache writeback > [0.00] On node 0 totalpages: 32768 maybe this means, that the device is wrong detected as "Dockstar", but it is a "GoFlex". Or is this not related? bye, bastian. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Seagate FreeAgent GoFlex Home / SATA not working / patch missing?
Is this patch from february still missing? http://patchwork.openwrt.org/patch/734/ bye, bastian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Seagate FreeAgent GoFlex Home / klog-line missing / Dockstart VS GoFlex
Hi Bastian, On Fri, Jun 29, 2012 at 08:12:59PM +0100, Bastian Bittorf wrote: > > dmesg: > > [0.00] Booting Linux on physical CPU 0 > > [0.00] Linux version 3.3.8 (fnord@tschunk) (gcc version > > 4.6.3 20120201 (prerelease) (Linaro GCC 4.6-2012.02) ) #1 Fri Jun > > 29 03:26:51 UTC 2012 > > [0.00] CPU: Feroceon 88FR131 [56251311] revision 1 > > (ARMv5TE), cr=00053977 > > [0.00] CPU: VIVT data cache, VIVT instruction cache > > by accident one important line was missing: > > [0.00] Machine: Seagate FreeAgent DockStar > > > [0.00] Memory policy: ECC disabled, Data cache writeback > > [0.00] On node 0 totalpages: 32768 > > maybe this means, that the device is wrong detected > as "Dockstar", but it is a "GoFlex". Or is this not related? You need to compile with the following patch to get all features ins the goflex to work: http://patchwork.openwrt.org/patch/2247/ If you planning on using encrypted disks I recommend: http://patchwork.openwrt.org/patch/2245/ There is no need to update the bootloader on the goflex, infact if you use a dockstar bootloader on the goflex, SATA won't work. bye MM -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Seagate FreeAgent GoFlex Home / SATA not working / patch missing?
On Fri, Jun 29, 2012 at 08:27:47PM +0100, Bastian Bittorf wrote: > Is this patch from february still missing? > http://patchwork.openwrt.org/patch/734/ Yes. bye MM -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel