Re: [OpenWrt-Devel] [OpenWrt-Commits] r14628 - trunk/target/linux/ar71xx/files/drivers/net/phy
Michael Buesch írta: > On Sunday 22 February 2009 21:52:13 openwrt-comm...@openwrt.org wrote: >> Author: juhosg >> Date: 2009-02-22 21:52:12 +0100 (Sun, 22 Feb 2009) >> New Revision: 14628 >> >> Modified: >>trunk/target/linux/ar71xx/files/drivers/net/phy/micrel.c >> Log: >> [ar71xx] micrel phy driver: change initcall level if compiled into the kernel > > ... > >> +#ifdef MODULE >> module_init(micrel_phy_init); >> module_exit(micrel_phy_exit); >> +#else >> +subsys_initcall(micrel_phy_init); >> +#endif > > This ifdef-ing is not needed. Simply do this: Yes, i know this is ugly. > > -module_init(micrel_phy_init); > +subsys_initcall(micrel_phy_init); > module_exit(micrel_phy_exit); > > It will do the correct thing for you in the built-in and module case.. > You are right, although 'include/linux/init.h' should be changed then: /* Don't use these in modules, but some people do... */ ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] monit: update to version 5.0_beta6
This set of patches can be used to compile monit version 5.0_beta6. It updates the existing Makefile used for version 4.10.1, and includes a fixed version of the patch to disable SSL support (line numbers changed). I wanted to upgrade to 5.0_beta6 in order to get monit working as part of inittab. For reference, here is the line I added to /etc/inittab: ::respawn:/usr/sbin/monit -Ic /etc/monitrc hope these patches came out correctly. Signed-off-by: Dan Brown Index: package/feeds/packages/monit/update_Makefile === --- Makefile.original 2009-02-21 21:25:46.0 -0800 +++ Makefile2009-02-22 19:05:58.0 -0800 @@ -9,12 +9,12 @@ include $(TOPDIR)/rules.mk PKG_NAME:=monit -PKG_VERSION:=4.10.1 +PKG_VERSION:=5.0_beta6 PKG_RELEASE:=1 PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.gz -PKG_SOURCE_URL:=http://www.tildeslash.com/monit/dist/ -PKG_MD5SUM:=d3143b0bbd79b53f1b019d2fc1dae656 +PKG_SOURCE_URL:=http://www.tildeslash.com/monit/dist/beta/ +PKG_MD5SUM:=a4d9224d08f885b46b418ede0fad592e include $(INCLUDE_DIR)/package.mk Index: package/feeds/packages/monit/patches/001-no_sslv2.patch === --- a/ssl.c +++ b/ssl.c @@ -675,9 +675,11 @@ ssl->method = SSLv23_client_method(); break; +#ifndef OPENSSL_NO_SSLV2 case SSL_VERSION_SSLV2: ssl->method = SSLv2_client_method(); break; +#endif case SSL_VERSION_SSLV3: ssl->method = SSLv3_client_method(); ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [OpenWrt-Commits] r14628 - trunk/target/linux/ar71xx/files/drivers/net/phy
On Sunday 22 February 2009 21:52:13 openwrt-comm...@openwrt.org wrote: > Author: juhosg > Date: 2009-02-22 21:52:12 +0100 (Sun, 22 Feb 2009) > New Revision: 14628 > > Modified: >trunk/target/linux/ar71xx/files/drivers/net/phy/micrel.c > Log: > [ar71xx] micrel phy driver: change initcall level if compiled into the kernel ... > +#ifdef MODULE > module_init(micrel_phy_init); > module_exit(micrel_phy_exit); > +#else > +subsys_initcall(micrel_phy_init); > +#endif This ifdef-ing is not needed. Simply do this: -module_init(micrel_phy_init); +subsys_initcall(micrel_phy_init); module_exit(micrel_phy_exit); It will do the correct thing for you in the built-in and module case.. -- Greetings, Michael. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Asus WL-330gE Support
Hi,
Here is support for the compact Asus WL-330gE. It uses that all-in-one
5354 Broadcom chip that's also in the WL-520gU, so I assume USB
support can be soldered on. I've yet to open up the device, though.
Initial flashing is done through the CFE failsafe mode like on other
Asus devices, where you boot holding the reset button, the power LED
flashes, and you tftp an image.
I'm recommending for inclusion in 8.09.
Thanks,
Dave Cooper
Signed-off-by: David Cooper
---
Index: package/broadcom-diag/src/diag.c
===
--- package/broadcom-diag/src/diag.c(revision 14622)
+++ package/broadcom-diag/src/diag.c(working copy)
@@ -68,6 +68,7 @@
WLHDD,
WL300G,
WL320GE,
+ WL330GE,
WL500G,
WL500GD,
WL500GP,
@@ -307,6 +308,15 @@
{ .name = "link", .gpio = 1 << 11, .polarity =
REVERSE },
},
},
+ [WL330GE] = {
+ .name = "ASUS WL-330gE",
+ .buttons= {
+ { .name = "reset", .gpio = 1 << 2 },
+ },
+ .leds = {
+ { .name = "power", .gpio = 1 << 0, .polarity =
REVERSE },
+ },
+ },
[WL500G] = {
.name = "ASUS WL-500g",
.buttons= {
@@ -764,6 +774,8 @@
return &platforms[WL520GC];
if (startswith(buf,"WL520GU-")) /* WL520GU-* */
return &platforms[WL520GU];
+ if (startswith(buf,"WL330GE-")) /* WL330GE-* */
+ return &platforms[WL330GE];
}
/* Based on "ModelId" */
Index: target/linux/brcm-2.4/base-files/etc/init.d/netconfig
===
--- target/linux/brcm-2.4/base-files/etc/init.d/netconfig (revision 14622)
+++ target/linux/brcm-2.4/base-files/etc/init.d/netconfig (working copy)
@@ -57,6 +57,12 @@
c["wan_ifname"] = ""
c["lan_ifname"] = "eth1"
}
+ if (model == "ASUS WL-330gE") {
+ c["wan_ifname"] = ""
+ c["lan_ifname"] = "eth0"
+ c["vlan0ports"] = ""
+ c["vlan1ports"] = ""
+ }
if (model == "ASUS WL-500g") {
c["wan_ifname"] = "eth1"
c["lan_ifname"] = "eth0"
@@ -149,12 +155,14 @@
c["vlan1ports"] = ""
}
- print " VLAN configuration "
- print "config switch eth0"
- p("vlan0", "vlan0ports")
- p("vlan1", "vlan1ports")
- print ""
- print ""
+ if (c["vlan0ports"] || c["vlan1ports"]) {
+ print " VLAN configuration "
+ print "config switch eth0"
+ p("vlan0", "vlan0ports")
+ p("vlan1", "vlan1ports")
+ print ""
+ print ""
+ }
print " Loopback configuration"
print "config interface loopback"
print " option ifname \"lo\""
@@ -173,10 +181,16 @@
print " option netmask 255.255.255.0"
print ""
print ""
- print " WAN configuration"
- print "config interface wan"
- p("ifname", "wan_ifname")
- p("macaddr", "wan_macaddr")
- print " option protodhcp"
+ if (c["wan_ifname"]) {
+ print " WAN configuration"
+ print "config interface wan"
+ p("ifname", "wan_ifname")
+ p("macaddr", "wan_macaddr")
+ print " option protodhcp"
+ } else {
+ print " WAN configuration (disabled)"
+ print "#config interface wan"
+ print "#option protodhcp"
+ }
}' > /etc/config/network
}
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] kexec failure on mips
On Sun, 2009-02-22 at 17:17 +0100, Holger Gross wrote: > i use the serial console, no other output is given. Oh, so the kernel doesn't even begin to boot? > now i m trying something of > http://www.nabble.com/kexec-on-mips---anyone-has-it-working--tt17485898.html#a17485898 Maybe I didn't quite follow the thread well enough but I didn't really see any solutions in there. It does seem clear that there are all sorts of avenues for failure to kexec. :-( If you do manage to make any headway, please, do post here. b. signature.asc Description: This is a digitally signed message part ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] kexec failure on mips
i use the serial console, no other output is given. now i m trying something of http://www.nabble.com/kexec-on-mips---anyone-has-it-working--tt17485898.html#a17485898 Am 22.02.2009 17:14, schrieb Brian J. Murrell: > On Sun, 2009-02-22 at 14:56 +0100, Holger Gross wrote: > >> now the kernel loads, but does not boot: >> >> br-lan: port 1(eth0.0) entering disabled state >> Starting new kernel >> Will call new kernel at 0029d000 >> Bye ... >> > > Do you have a serial console on your device? I don't yet. My > TTL-to-RS232 level converter arrived the other day, although I'd really > rather find one of those nokia usb cables with the level adjuster built > in. > > Anyway, sounds like you and I are having the same problems and likely > seeing the kernel boot on a serial console will reveal the problem. I > just need to find the time to get to it. > > b. > > > > > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel > ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] kexec failure on mips
On Sun, 2009-02-22 at 14:56 +0100, Holger Gross wrote: > now the kernel loads, but does not boot: > > br-lan: port 1(eth0.0) entering disabled state > Starting new kernel > Will call new kernel at 0029d000 > Bye ... Do you have a serial console on your device? I don't yet. My TTL-to-RS232 level converter arrived the other day, although I'd really rather find one of those nokia usb cables with the level adjuster built in. Anyway, sounds like you and I are having the same problems and likely seeing the kernel boot on a serial console will reveal the problem. I just need to find the time to get to it. b. signature.asc Description: This is a digitally signed message part ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] kexec failure on mips
now the kernel loads, but does not boot: br-lan: port 1(eth0.0) entering disabled state Starting new kernel Will call new kernel at 0029d000 Bye ... Am 17.02.2009 19:14, schrieb Brian J. Murrell: > On Tue, 2009-02-17 at 18:36 +0100, Holger Gross wrote: > >> Hi, >> >> i have the same problem using kexec with buffalo whr g54s openwrt rc2 >> kernel 2.4: >> >> kexec_load failed: Success >> entry = 0x298000 flags = 0 >> nr_segments = 2 >> segment[0].buf = 0x2ac37008 >> segment[0].bufsz = 27307b >> segment[0].mem = 0x1000 >> segment[0].memsz = 297000 >> segment[1].buf = 0x456338 >> segment[1].bufsz = 1a4 >> segment[1].mem = 0x298000 >> segment[1].memsz = 1000 >> >> is there any solution for this? >> > > The solution for me, on 2.6.25 was to actually enable KEXEC in the > kernel. > > Now the kernel loads and boots but doesn't complete booting. I'm > waiting for my TTL/RS-232 conversion cable to arrive so I can see why. > > b. > > > > > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel > ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] option overlay_root /jffs
Hi, I have OpenWrt (Kamikaze 8.09), and 'opkg install xx' says: * Only have 0 available blocks on filesystem /, pkg xx needs nnn I had this error some time ago, and found that the option option overlay_root /jffs resolves this problem. But this version does not accept this option. I tried this: dest root /jffs and install/upgrade seems working, but I don't know if it is a correct solution or not. Or is there any better solution? Thanx in advance K. Gy. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
