Re: [OpenWrt-Devel] menuconfig vs kernel_menuconfig
Hi Felix and All, Thanks so much for your note. Very insightful :). So I am trying to enable MMC on Kamikaze 8.0.9 [actually the village telco version]. I need to wind up with 3 kernel modules related to gpio and mmc. I gather I start with kernel_menuconfig at the main level and then do menuconfig? It is still confusing to me which boxes in the two menuconfigs I check to get the various kernel modules whose names I know compiled in. i.e.- the names on the selection boxes don't make it clear which modules are going to be compiled? I feel like I must be missing some simple step? That said I am pretty sure I am close to having it working :). Again thank you for your insightful response. warm regards to all, Wiz On Tue, 20 Apr 2010, Felix Fietkau wrote: > On 2010-04-19 11:40 PM, RHS Linux User wrote: > > Hi All, > > > > > > > >This whole config business IMHO is a real mess! > I disagree, it just takes a bit of getting used to. > > >Can someone clarify what happens with target config, and whatever other > > .configs that happen to be around somewhere? > It works like this: > you have target/linux/generic-2.6/config-, which contains > the baseline settings for all targets. Each target can override and add > any config option relative to that. The delta is stored in > target/linux//config-. > The reason for that is that maintaining one individual .config for each > target would create a much bigger mess, as it makes common config > changes that affect all targets much harder to implement. > > >Also it seems to me HI TIME that .config became a VERY visible file. So > > much depends on the "main" .config and the .config in the kernel > > directory. > For reasons stated above, we can't just stick the plain .config files > from the kernel directories in the target dir, as this would mess up > other things. > > >Is running make kernel_menuconfig the same as going into the kernel > > directory and doing menuconfig there? (I hope so.) > No, it's not. Make kernel_menuconfig does these things (simplified): > > - Generate the kernel's .config by merging the following files: >- target/linux/generic-2.6/config- >- target/linux//config- > - run make menuconfig in the kernel tree > - subtract generic stuff from the kernel's .config and rebuild >target/linux//config- from that > > The idea is that you only need to hand-edit stuff if you want to make > changes to the generic config template, which most of the time you don't > have to. > > A bit more tricky is the interaction with the build system .config for > selecting modules. The idea behind that is to not let the kernel build > all modules all the time, but allow the user to select which modules to > throw in binary packages. For this to work, the build system needs to > make further modifications to the kernel's .config before launching the > kernel module build, as having making these changes ahead of time for > platform kernel configs would launch you into an unmanageable Dependency > Tree From Hell. > > For all of the .config merges, scripts/kconfig.pl is used, which can do > some very simple config merging/splitting operation. > For the module selection it has a special operation that allows the > merged-in config to only *upgrade* config selections. That means if you > selected something as =y in kernel_menuconfig, the build system will not > change that. It will however select stuff as =m or =y depending on the > KCONFIG settings for kmod-* packages that you selected. > > Normally you don't have to be concerned with this process at all, > however occasionally you may encounter undefined config symbols which > make kernel_menuconfig or kernel_oldconfig won't show you. In this case, > you need to add defaults for the missing symbols either to the KCONFIG > line of the package that triggered them, or simply stick them into > target/linux/generic-2.6/config-* > > I hope this clears things up a bit > > - Felix > ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Option modem GTM382 and HSO
Well, hit the wall at this point: https://forum.openwrt.org/viewtopic.php?id=22301 There IS no kmod-usb-net module in the section allthou it's suppose to be in kernel. <*> kmod-usb-core Support for USB │ │ │ │ < > kmod-usb-acm. Support for modems/isdn controllers │ │ │ │ < > kmod-usb-atm.. Support for ATM on USB bus │ │ │ │ < > kmod-usb-audio. Support for USB audio devices │ │ │ │ < > kmod-usb-cm109.. Support for CM109 device │ │ │ │ < > kmod-usb-hid. Support for USB Human Input Devices │ │ │ │ kmod-usb-net... Kernel modules for USB-to-Ethernet convertors │ │ │ │ < > kmod-usb-net-asix.. Kernel module for USB-to-Ethernet Asix convertors (NEW) │ │ │ │ < > kmod-usb-net-cdc-ether.. Support for cdc ethernet connections (NEW) │ │ │ │ < > kmod-usb-net-dm9601-ether Support for DM9601 ethernet connections (NEW) │ │ │ │ < > kmod-usb-net-kaweth.. Kernel module for USB-to-Ethernet Kaweth convertors (NEW) │ │ │ │ < > kmod-usb-net-mcs7830 (NEW) │ │ │ │ < > kmod-usb-net-pegasus (NEW) │ │ │ │ < > kmod-usb-net-rndis. Support for RNDIS connections (NEW) │ │ │ │ < > kmod-usb-ohci... Support for OHCI controllers │ │ │ │ < > kmod-usb-phidget.. USB Phidget Driver │ │ │ │ < > kmod-usb-printer Support for printers │ │ │ │ < > kmod-usb-serial. Support for USB-to-Serial converters │ │ │ │ kmod-usb-storage. USB Storage support │ │ │ │ < > kmod-usb-storage-extras Extra drivers for usb-storage │ │ │ │ < > kmod-usb-uhci... Support for UHCI controllers │ │ │ │ < > kmod-usb-video. Support for USB video devices │ │ │ │ < > kmod-usb-yealink.. USB Yealink VOIP phone │ │ │ │ <*> kmod-usb2... Support for USB2 controllers │ │ │ │ < > kmod-usbip.. USB-over-IP (kernel support) │ │ │ │ < > kmod-usbip-client. USB-over-IP (kernel client driver) │ │ │ │ < > kmod-usbip-server... USB-over-IP (kernel host driver) │ │ │ │ On 20.04.2010 22:18, Bernhard Loos wrote: 2010/4/20 Janno Sannik: I'm kinda new to openwrt dependency and bulding. I have set the required modules (RFKILL, CONFIG_USB_HSO) in kernel_menuconfig as described in ticket: https://dev.openwrt.org/ticket/6998 . make kernel_menuconfig shows it, but after exiting looking at build_dir/linux-gemini/linux-2.6.32.10/.config it still is unset. That's because of the way openwrt handles modules. Don't touch kernel_menuconfig unless you know, what you are doing. Enable instead the packages in normal openwrt menuconfig. It will still build kernel modules. Procedure is as follows: get latest svn make symlinks/packages make menuconfig (configure for gemini and kmod-usb2) make (for some reason if make kernel_menuconfig was called before building kernel first time, it gives error. Sorry, didn't note it down, but probably can be reproduced) That's normal, because the tools (quilt is needed) are not yet build. make kernel_menuconfig make ___ 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 mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Configuring 3G connection to come up on boot
Nuno, >I have the following config: > >config interface wan > option device /dev/ttyUSB0 > option proto3g > [...] > >According to the wiki this connection should come on-line on boot. But don't. >Wiki also says that the ifname option is mandatory. What would I >choose for this? I use "ppp0" for my ifname. As for the boot problem, I posted about a seemingly-identical issue with 3G modem bringup in February: https://lists.openwrt.org/pipermail/openwrt-devel/2010-February/005818.html The patch I attached previously cured it for me (although the line numbers may have changed a bit since then): https://lists.openwrt.org/pipermail/openwrt-devel/attachments/20100204/5f3170c3/attachment.txt I am unsure if my solution was correct since my change did not get incorporated into trunk. But I didn't get a NACK either and I forgot to follow up, so I'm not sure if my patch was the wrong approach or if it was simply overlooked. Regardless, it got things working for me. Scott _ The New Busy is not the too busy. Combine all your e-mail accounts with Hotmail. http://www.windowslive.com/campaign/thenewbusy?tile=multiaccount&ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_4___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Re Re AR7 Linksys WRTP54G 3.1.27-ETSI
Well, then. I should not fool around writing to nvram if I wish to set/proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_established to a sane value. Instead of this I should edit /etc/sysctl.conf cd etc # ls TZ host.conf securetty ca_crt.pem hosts services config.xml igd shadow dhcp-fwd.cfginit.d shells dproxy.conf inittab strings.xml dropbearkillp sysdef.xml firewall_start language.datudhcpc firewall_stop lsca_crt.pemudhcpd.conf flush_conntrack passwd versions flush_firewall ppp voice_defaults.txt fpar_check progdefs.xmlvoice_dly fstab protocols voice_reboot gatewaysresolv.conf voice_start group rootca_crt.pem voice_stop Which one is it?Thanks, Gabor___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Re Re AR7 Linksys WRTP54G 3.1.27-ETSI
Well, then. I should not fool around writing to nvram if I wish to set/proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_established to a sane value. Instead of this I should edit /etc/sysctl.conf cd etc # ls TZ host.conf securetty ca_crt.pem hosts services config.xml igd shadow dhcp-fwd.cfginit.d shells dproxy.conf inittab strings.xml dropbearkillp sysdef.xml firewall_start language.datudhcpc firewall_stop lsca_crt.pemudhcpd.conf flush_conntrack passwd versions flush_firewall ppp voice_defaults.txt fpar_check progdefs.xmlvoice_dly fstab protocols voice_reboot gatewaysresolv.conf voice_start group rootca_crt.pem voice_stop Which one is it?Thanks, Gabor___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Re Re AR7 Linksys WRTP54G 3.1.27-ETSI
Well, then. I should not fool around writing to nvram if I wish to set/proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_established to a sane value. Instead of this I should edit /etc/sysctl.conf cd etc # ls TZ host.conf securetty ca_crt.pem hosts services config.xml igd shadow dhcp-fwd.cfginit.d shells dproxy.conf inittab strings.xml dropbearkillp sysdef.xml firewall_start language.datudhcpc firewall_stop lsca_crt.pemudhcpd.conf flush_conntrack passwd versions flush_firewall ppp voice_defaults.txt fpar_check progdefs.xmlvoice_dly fstab protocols voice_reboot gatewaysresolv.conf voice_start group rootca_crt.pem voice_stop Which one is it?Thanks, Gabor___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Re Re AR7 Linksys WRTP54G 3.1.27-ETSI
Well, then. I should not fool around writing to nvram if I wish to set/proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_established to a sane value. Instead of this I should edit /etc/sysctl.conf cd etc # ls TZ host.conf securetty ca_crt.pem hosts services config.xml igd shadow dhcp-fwd.cfginit.d shells dproxy.conf inittab strings.xml dropbearkillp sysdef.xml firewall_start language.datudhcpc firewall_stop lsca_crt.pemudhcpd.conf flush_conntrack passwd versions flush_firewall ppp voice_defaults.txt fpar_check progdefs.xmlvoice_dly fstab protocols voice_reboot gatewaysresolv.conf voice_start group rootca_crt.pem voice_stop Which one is it?Thanks, Gabor___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Re Re AR7 Linksys WRTP54G 3.1.27-ETSI
Well, then. I should not fool around writing to nvram if I wish to set/proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_established to a sane value. Instead of this I should edit /etc/sysctl.conf cd etc # ls TZ host.conf securetty ca_crt.pem hosts services config.xml igd shadow dhcp-fwd.cfginit.d shells dproxy.conf inittab strings.xml dropbearkillp sysdef.xml firewall_start language.datudhcpc firewall_stop lsca_crt.pemudhcpd.conf flush_conntrack passwd versions flush_firewall ppp voice_defaults.txt fpar_check progdefs.xmlvoice_dly fstab protocols voice_reboot gatewaysresolv.conf voice_start group rootca_crt.pem voice_stop Which one is it?Thanks, Gabor___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Re Re AR7 Linksys WRTP54G 3.1.27-ETSI
Well, then. I should not fool around writing to nvram if I wish to set/proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_established to a sane value. Instead of this I should edit /etc/sysctl.conf cd etc # ls TZ host.conf securetty ca_crt.pem hosts services config.xml igd shadow dhcp-fwd.cfginit.d shells dproxy.conf inittab strings.xml dropbearkillp sysdef.xml firewall_start language.datudhcpc firewall_stop lsca_crt.pemudhcpd.conf flush_conntrack passwd versions flush_firewall ppp voice_defaults.txt fpar_check progdefs.xmlvoice_dly fstab protocols voice_reboot gatewaysresolv.conf voice_start group rootca_crt.pem voice_stop Which one is it?Thanks, Gabor___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Re Re AR7 Linksys WRTP54G 3.1.27-ETSI
Well, then. I should not fool around writing to nvram if I wish to set/proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_established to a sane value. Instead of this I should edit /etc/sysctl.conf cd etc # ls TZ host.conf securetty ca_crt.pem hosts services config.xml igd shadow dhcp-fwd.cfginit.d shells dproxy.conf inittab strings.xml dropbearkillp sysdef.xml firewall_start language.datudhcpc firewall_stop lsca_crt.pemudhcpd.conf flush_conntrack passwd versions flush_firewall ppp voice_defaults.txt fpar_check progdefs.xmlvoice_dly fstab protocols voice_reboot gatewaysresolv.conf voice_start group rootca_crt.pem voice_stop Which one is it?Thanks, Gabor___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Option modem GTM382 and HSO
2010/4/20 Janno Sannik : > I'm kinda new to openwrt dependency and bulding. I have set the required > modules (RFKILL, CONFIG_USB_HSO) in kernel_menuconfig as described in > ticket: https://dev.openwrt.org/ticket/6998 . make kernel_menuconfig shows > it, but after exiting looking at > build_dir/linux-gemini/linux-2.6.32.10/.config it still is unset. That's because of the way openwrt handles modules. Don't touch kernel_menuconfig unless you know, what you are doing. Enable instead the packages in normal openwrt menuconfig. It will still build kernel modules. > > Procedure is as follows: > get latest svn > make symlinks/packages > make menuconfig (configure for gemini and kmod-usb2) > make > (for some reason if make kernel_menuconfig was called before building kernel > first time, it gives error. Sorry, didn't note it down, but probably can be > reproduced) That's normal, because the tools (quilt is needed) are not yet build. > make kernel_menuconfig > make > ___ > 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] wl0 - impossible to use STA simultaneously with AP
Current trunk on WL500GP v1(2.4), can not set a STA and AP simultaneously. STA works OK, LAN clients can connect but any wireless client timeout when connecting. config wifi-device wl0 option type broadcom option channel 5 config wifi-iface option device wl0 option network wan option mode sta option ssid NrSrFatima option encryption psk2 option key "yesterday" config wifi-iface option device wl0 option network lan option mode ap option ssid Openwrt option encryption none -- config interfacewan option type bridge option ifname "wl0" option protodhcp -- r...@openwrt:/# ifconfig br-lanLink encap:Ethernet HWaddr 00:1D:60:15:5F:A3 inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:504 errors:0 dropped:0 overruns:0 frame:0 TX packets:375 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:108266 (105.7 KiB) TX bytes:61883 (60.4 KiB) br-wanLink encap:Ethernet HWaddr 00:1D:60:15:5F:A3 inet addr:192.168.137.54 Bcast:192.168.137.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:182 errors:0 dropped:0 overruns:0 frame:0 TX packets:209 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:42555 (41.5 KiB) TX bytes:97387 (95.1 KiB) eth0 Link encap:Ethernet HWaddr 00:1D:60:15:5F:A3 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:867 errors:0 dropped:0 overruns:0 frame:0 TX packets:375 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:242953 (237.2 KiB) TX bytes:65081 (63.5 KiB) Interrupt:4 eth0.0Link encap:Ethernet HWaddr 00:1D:60:15:5F:A3 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:504 errors:0 dropped:0 overruns:0 frame:0 TX packets:375 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:110282 (107.6 KiB) TX bytes:63383 (61.8 KiB) loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:9 errors:0 dropped:0 overruns:0 frame:0 TX packets:9 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:587 (587.0 B) TX bytes:587 (587.0 B) wl0 Link encap:Ethernet HWaddr 00:1D:60:15:5F:A3 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:182 errors:0 dropped:0 overruns:0 frame:8635 TX packets:212 errors:39 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:45103 (44.0 KiB) TX bytes:99082 (96.7 KiB) Interrupt:2 Base address:0x2000 wl0.1 Link encap:Ethernet HWaddr 02:1D:60:15:5F:A0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) r...@openwrt:/# iwconfig lono wireless extensions. eth0 no wireless extensions. eth1 no wireless extensions. eth0.0no wireless extensions. br-lanno wireless extensions. wl0 IEEE 802.11-DS ESSID:"NrSrFatima" Mode:Master Frequency:2.462 GHz Access Point: 00:22:6B:86:DF:5E Bit Rate=54 Mb/s Tx-Power:32 dBm RTS thr:off Fragment thr:off Link Quality:5 Signal level:0 Noise level:180 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 br-wanno wireless extensions. wl0.1 IEEE 802.11-DS ESSID:"Openwrt" Mode:Master Channel:11 Access Point: 02:1D:60:15:5F:A0 Bit Rate=54 Mb/s RTS thr:off Fragment thr:off -- + Nuno Gonçalves + nuno...@gmail.com + http://nunoassimassim.blogspot.com/ + PORTUGAL E-mail sent directly from Google Mail webmail using HTTPS on behalf of Nuno João Pinto Gonçalves, birth date 1986-11-16. E-mail headers provide good assurance that this message was not tampered and originates from nuno...@gmail.com. If you require additional security, I may provide on request X509 electronic signature under Portuguese government chain. Se precisar de assinatura digital do Cartão de Cidadão, de uma apitadela. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Option modem GTM382 and HSO
I'm kinda new to openwrt dependency and bulding. I have set the required modules (RFKILL, CONFIG_USB_HSO) in kernel_menuconfig as described in ticket: https://dev.openwrt.org/ticket/6998 . make kernel_menuconfig shows it, but after exiting looking at build_dir/linux-gemini/linux-2.6.32.10/.config it still is unset. Procedure is as follows: get latest svn make symlinks/packages make menuconfig (configure for gemini and kmod-usb2) make (for some reason if make kernel_menuconfig was called before building kernel first time, it gives error. Sorry, didn't note it down, but probably can be reproduced) make kernel_menuconfig make ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Configuring 3G connection to come up on boot
The interfaces configuration take this config according to the wiki(http://wiki.openwrt.org/doc/uci/network): auto boolean no 0 for proto none, else 1Specifies whether to bring up interface on boot I have the following config: config interface wan option device /dev/ttyUSB0 option proto3g option apn internet option pincode 1953 list dns8.8.4.4 list dns8.8.8.8 According to the wiki this connection should come on-line on boot. But don't. Wiki also says that the ifname option is mandatory. What would I choose for this? Regards -- + Nuno Gonçalves + nuno...@gmail.com + http://nunoassimassim.blogspot.com/ + PORTUGAL E-mail sent directly from Google Mail webmail using HTTPS on behalf of Nuno João Pinto Gonçalves, birth date 1986-11-16. E-mail headers provide good assurance that this message was not tampered and originates from nuno...@gmail.com. If you require additional security, I may provide on request X509 electronic signature under Portuguese government chain. Se precisar de assinatura digital do Cartão de Cidadão, de uma apitadela. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] gcc 4.5 patches
On Tuesday 20 April 2010 15:42:35 Bernhard Loos wrote: > Hello > This patches updates the graphite patch with gcc 4.5 support, enables > link time optimization support and fixes some problems with the > patches. > > Bernhard > Applied in r21046, thanks Bernhard! -- Florian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Introduction of a new env script (env2)
Hi, The env2 script has a similar purpose as the env script currently used in OpenWrt. It based on env but adds new features to make it possible to track a whole OpenWrt configuration. env does only track changes to the .config file and the files/ directory. The env2 script permits to track arbitrary files in git. It also implements SVN support. So you can save a coherent and reproducible state of the environment. For example with env2 it is possible to track a adm5120 configuration like this: env2 new adm5120 This creates a new git branch and adds the .config, feeds.conf and files/ to it. It also adds the file .svn/entries for the OpenWrt base directory and the configured feeds. (The .svn/entries are needed for tracking the SVN Revision and tag you use in your branches; so env2 adds some more files the branch by default) Add configuration for an adm5120 router env2 add target/linux/adm5120/Makefile env2 add target/linux/adm5120/router_le/config-2.6.32 Add build images env2 add bin/adm5120/openwrt-adm5120-br-6104kp-squashfs-xmodem.bin env2 add bin/adm5120/openwrt-adm5120-rootfs.tgz Like in the env script you can also base you new configuration on the old one by anwsering "y" to "Do you want to clone the current environment" env2 new adm5120-2.6.32.9 (respond "y" when ask to clone) (edit KERNEL_VERSION to 2.6.32.9 in target/linux/adm5120/Makefile) evn2 save Now you have two branches, one configured for the default kernel, one for the 2.6.32.9 kernel. If you now want to work on another router, say an ar71xxx you would do the following: env2 new ar71xx env2 add target/linux/ar71xx/Makefile env2 add target/linux/ar71xx/config-2.6.32 To switch back to the adm5120 configuration you can do env2 switch adm5120 The switch command in env2 does remove the symlinked files of the current branch from the OpenWrt base directory, switches to the new branch and symlinks the files of the new branch to the OpenWrt base directory. After that it checks if the new SVN URL differs from the old one and performs a "svn switch" if necessary. If the SVN Revision differs a "svn update -r $REV" is also peformed. After that it runs "scripts/feeds/update -i" and "make package/symlinks". Finally it deletes all unwanted files that came along with the svn update (see "env2 unwanted"). To see information the current branch (SVN URL and Revision, branch name) env2 info To remove a file from the branch (AND the environment) env2 remove target/linux/ar71xx/Makefile The env2 script also wraps "git diff", so you can do: env2 gdiff adm5120 adm5120-2.6.32.9 --summary env2 symlinks like env all files from the env2 directory to the OpenWRT base directory. To remove the symlinks and copy all files from you current branch to the OpenWrt base directory do env2 disable Because the script restores automatically SVN revisions there might be some files you have deleted. For example patches you do not want to apply. With env2 you can automatically remove these files using the following commands env2 unwanted package/opkg/patches/009-remove-upgrade-all.patch This will delete the patch everytime when a SVN update pulls it in. If you decide that you want this file again you can do: env2 rewanted package/opkg/patches/009-remove-upgrade-all.patch (Note: there might be a more general, better way to do this in the implementation. This is just a quick hack to also permit keeping track of deletions.) The rest of the commands are the same as in you know them from the env script. The env2 assumes that it is located in the scripts/ directory below the OpenWrt base directory. By doing so it is possible to call it independently from the current $(PWD). So you might just add the scripts directory to you $PATH and env2 should work from anywhere. I have tested this script and it works for me. But this is the first release and there will be most certainly bugs. Happy testing! Oliver Ripka Index: .gitignore === --- .gitignore (revision 21044) +++ .gitignore (working copy) @@ -1,5 +1,6 @@ .*.swp /env +/env2 /dl /.config /.config.old Index: scripts/env2 === --- scripts/env2 (revision 0) +++ scripts/env2 (revision 0) @@ -0,0 +1,453 @@ +#!/usr/bin/env bash + +# Script path +spath=$(cd "${0%/*}" 2>/dev/null; echo "$PWD"/"${0##*/}") + +# OpenWrt checkout, assuming it is one level down from the +# script directory in which this script should be. +BASEDIR=`readlink -f $(dirname $spath)/..` + +ENVNAME="env2" +ENVDIR="$BASEDIR/$ENVNAME" + +UNWANTED=".unwanted" + +#DEBUG=true +#DISABLE_SVN=true + +usage() { + cat < [arguments] +Commands: + helpThis help text + listList environments + clear Delete all environment and rev
Re: [OpenWrt-Devel] Fw: Dlink DIR-615C1: small mistake in mtd layout?
Hi Yury, > Just to make sure: you didn't want to increase the size of the > *-factory.bin (by 64k - 24 bytes) because its size is hardcoded in the > uboot's emergency reflasher? The board id must exist at offset 0x3B in the firmware image. It is hardcoded in the U-Boot, and in the factory firmware. Although we can pad that, so it would end on a 64KB boundary but it is not needed. Regards, Gabor ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Fw: Dlink DIR-615C1: small mistake in mtd layout?
On Tue, 20 Apr 2010 10:09:59 +0200 Gabor Juhos wrote: > The size of the 'art' partition is 64K in real, but in the original firmware > it > covers the previous erase block which contains the 'board id'. It is not used > in > OpenWrt, so we can use that space to extend the rootfs partition a bit. > > Thanks for reporting, it has been fixed with: > https://dev.openwrt.org/changeset/21036 Hello Gabor! Just to make sure: you didn't want to increase the size of the *-factory.bin (by 64k - 24 bytes) because its size is hardcoded in the uboot's emergency reflasher? Thanks for such a quick response! Y signature.asc Description: PGP signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] gcc 4.5 patches
Hello This patches updates the graphite patch with gcc 4.5 support, enables link time optimization support and fixes some problems with the patches. Bernhard gcc45.diff Description: Binary data ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] AR7 Linksys WRTP54G 3.1.27-ETSI
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi. The nvram command has nothing to do with it, edit /etc/sysctl.conf to apply other default values. ~ Jow -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvNnrkACgkQdputYINPTPOuiwCeOMeRseRobJR2cPm52P81IU7f PV4AoIItHq3CdrLML4cKNSg9Nbum9/Np =U0bI -END PGP SIGNATURE- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] AR7 Linksys WRTP54G 3.1.27-ETSI
Dear Developers, I’m sorry bothering you but I don't know personally the clever Dev who patched the Linksys WRTP54G 3.1.27 firmware.http://oldwiki.openwrt.org/attachments/OpenWrtDocs(2f)Hardware(2f)Linksys(2f)WRTP54G/wrt-11.1.1-r070720-3.1.27.ETSI-r070720-aguirre-r080119.imgI'm sure there is a wrong set variable (ip_conntrack_tcp_timeout_established) in this (and in the original one too) firmware.My router begins dropping connections in about every 12 hours with “ip connection table full“ message. I know the cause is “heavy” P2P traffic but I would say the traffic is moderate, the firmware setting is faulty.I read on http://www.dd-wrt.com/wiki/index.php/Router_Slowdownthat the variables should be set about to:echo '2048' > /proc/sys/net/ipv4/netfilter/ip_conntrack_maxecho '600' > /proc/sys/net/ipv4/netfilter/ip_conntrack_generic_timeoutecho '30' > /proc/sys/net/ipv4/netfilter/ip_conntrack_icmp_timeoutecho '10 39; > /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_closeecho '120' > /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_close_waitecho '120' > /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_establishedecho '60' > /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_syn_sentecho '120' > /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_syn_recvecho '120' > /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_fin_waitecho '10' > /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_time_waitecho '60' > /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_last_ackecho '60' > /proc/sys/net/ipv4/netfilter/ip_conntrack_udp_timeoutecho '60' > /proc/sys/net/ipv4/netfilter/ip_conntrack_udp_timeout_stream instead of this the defaults are:cat /proc/sys/net/ipv4/netfilter/ip_conntrack_generic_timeout600cat /proc/sys/net/ipv4/netfilter/ip_conntrack_icmp_timeout30cat /proc/sys/net/ipv4/netfil ter/ip_conntrack_tcp_timeout_close10cat /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_close_wait120cat /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_established86400cat /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_syn_sent30cat /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_syn_recv60cat /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_fin_wait120cat /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_time_wait30cat /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_last_ack30cat /proc/sys/net/ipv4/netfilter/ip_conntrack_udp_timeout90cat /proc/sys/net/ipv4/netfilter/ip_conntrack_udp_timeout_stream180cat /proc/sys/net/ipv4/netfilter/ip_conntrack_max1024cat /proc/sys/net/ipv4/netfilter/ip_conntrack_flush1 I think cat /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_established86400 sec is insane. I could not find any solution to write the right values to the nvram. (No nvram commit command!)Could you give me any advise how to modi fy the default values?Could you possibly patch wrt-11.1.1-r070720-3.1.27.ETSI-r070720-aguirre-r080119.img again? Thank You, Gabor___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Fw: Dlink DIR-615C1: small mistake in mtd layout?
Yury Polyanskiy írta: > Hello! > > I noticed that on my DIR-615C1 kamikaze prints the following mtd layout: > > m25p80 spi0.0: s25sl032a (4096 Kbytes) > 6 cmdlinepart partitions found on MTD device spi0.0 > Creating 6 MTD partitions on "spi0.0": > 0x-0x0002 : "u-boot" > 0x0002-0x0003 : "config" > 0x0003-0x0011 : "kernel" > 0x0011-0x003e : "rootfs" > 0x0025-0x003e : "rootfs_data" > 0x003e-0x003f : "art" > 0x0003-0x003e : "firmware" > > > Thus the art partition does not extend all the way to the end of > device. The original firmware defined art as 0x3e-0x4. The size of the 'rootfs' and the 'firmware' partition is wrong in the cameo_mtdlayout variable. > Unless there is some hidden wisdom to defining the art so, here is the > patch. The size of the 'art' partition is 64K in real, but in the original firmware it covers the previous erase block which contains the 'board id'. It is not used in OpenWrt, so we can use that space to extend the rootfs partition a bit. Thanks for reporting, it has been fixed with: https://dev.openwrt.org/changeset/21036 Regards, Gabor ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel