Re: [OpenWrt-Devel] [PATCH 7/7] ramips: enable USB

2011-02-09 Thread HP Teoh
Hi Alexander, I have applied this usb patch and the dwc_otg patches to my trunk but I still can't get the USB option to show up in make menuconfig -> Kernel modules -> USB Support. Thanks. -Hp On Tue, Feb 1, 2011 at 8:08 PM, Alexander Gordeev wrote: > Signed-off-by: Alexander Gordeev > --- >

[OpenWrt-Devel] [PATCH v2 1/1] Enable DSCP QoS for openssh-5.7p1

2011-02-09 Thread Philip Prindeville
The default values for OpenSSH QoS markings are wrong. They use 'lowdelay' and 'throughput' for interactive and bulk traffic, respectively. Unfortunately, these values were retired in 1998 when the low-order 2 bits of ToS field were repurposed for DSCP: originally RFC-2474 marked the lower 2 b

[OpenWrt-Devel] [PATCH 1/1] Enable DSCP QoS for openssh-5.7p1

2011-02-09 Thread Philip Prindeville
The default values for OpenSSH QoS markings are wrong. They use 'lowdelay' and 'throughput' for interactive and bulk traffic, respectively. Unfortunately, these values were retired in 1998 when the low-order 2 bits of ToS field were repurposed for DSCP: originally RFC-2474 marked the lower 2 b

Re: [OpenWrt-Devel] Refactoring base-files

2011-02-09 Thread Philip Prindeville
On 2/9/11 7:08 AM, Stefan Monnier wrote: - clean code (not obfuscated) Obviously agreed. But there are likely disagreements about what is "clean" and what is "obfuscated". Turning a oneliner sed into a 10-liner read/while/case/set loop is usually not an improvement in my book (as discussed pre

Re: [OpenWrt-Devel] [OpenWrt-Commits] r25414 - trunk/package/hotplug2/patches

2011-02-09 Thread Philip Prindeville
On 2/9/11 2:15 AM, Vasilis Tsiligiannis wrote: Why not just have the requirement that /etc/hotplug2-platform.rules be present, even if it's zero-length? Because an empty include rules file would then be required in base-files overrides of each target. That doesn't seem like such a bad thing..

Re: [OpenWrt-Devel] [PATCH] opencdk-0.6.6

2011-02-09 Thread Florian Fainelli
On Monday 17 January 2011 20:50:01 Daniel A. Nagy wrote: > This patch fixes a bug in the upstream library that prevents the > verification of clearsigned documents with \r\n line endings. Obviously, > it should go under feeds/packages/libs/opencdk/patches/ > > Signed-off-by: Daniel A. Nagy Appli

Re: [OpenWrt-Devel] [PATCH] libusb: prevent building unused stuff

2011-02-09 Thread Florian Fainelli
On Friday 04 February 2011 11:21:13 Joachim Schlipper wrote: > This patch prevents the processing of the 'doc' and 'tests' > subdirectories of the libusb package. Since the result of building these > directories is never included in the ipkg package, omitting them saves > compilation time and avoid

Re: [OpenWrt-Devel] [PATCH] libs/jpeg fails parallel build due to all and install targets in same make instance

2011-02-09 Thread Florian Fainelli
On Sunday 05 December 2010 18:24:49 Joseph Roback wrote: > For parallel builds, make targets that build need to be separated from > targets that install ;-) > > Signed-off-by: Joe Roback Applied in r25435, thanks Joe! -- Florian ___ openwrt-devel maili

Re: [OpenWrt-Devel] [PATCH] update eggdrop package to 1.6.20

2011-02-09 Thread Florian Fainelli
Hello, On Friday 07 January 2011 09:56:58 Chris Moeller wrote: > This patch updates the feeds Makefile, removes a patch which is no > longer necessary, and updates the main.c root check patch for the new > contextual lines surrounding the two changed lines. > > Also, for some reason, I was unable

[OpenWrt-Devel] [PATCH] Update toolchain gdb to 7.2

2011-02-09 Thread Steve Brown
This patch updates the toolchain gdb from 6.8 to 7.2 Signed-off-by: Steve Brown --- For some reason, gdb 6.8 isn't working on mac80211.ko, but seems fine with other modules. I've tried the gdb build with both the mips and x86 toolchains. I ran nm on the two modules below and the output looked r

Re: [OpenWrt-Devel] Supporting a new brcm63xx board

2011-02-09 Thread devendra.aaru
Hi, u can use the kernel that is downloaded when u have done make (but u need to see the arch specific code as florian said). goto arch/mips/bcm63xx/ here the board specific code will be present. u can go through the code and change it according to ur board and make a patch and place it in target

Re: [OpenWrt-Devel] Supporting a new brcm63xx board

2011-02-09 Thread Marco Antonio Mauro
On Tue, Feb 8, 2011 at 3:54 PM, Florian Fainelli wrote: > You basically need to adapt arch/mips/bcm63xx/boards/board_bcm963xx.c and add > a specific definition for your board, that is: > > - describing the expected CPU type it will be found running on > - external peripherals which are present on

Re: [OpenWrt-Devel] Refactoring base-files

2011-02-09 Thread Stefan Monnier
> - clean code (not obfuscated) Obviously agreed. But there are likely disagreements about what is "clean" and what is "obfuscated". Turning a oneliner sed into a 10-liner read/while/case/set loop is usually not an improvement in my book (as discussed previously). If you want to avoid forking a

Re: [OpenWrt-Devel] coreutils version bump

2011-02-09 Thread Florian Fainelli
On Thursday 23 December 2010 20:31:56 Alexander Khryukin wrote: > Good day. > coreutils version bump > Signed-off-by: Alexander Khryukin Applied in r25432, thanks Alexander! -- Florian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https

Re: [OpenWrt-Devel] [PATCH] bcm63xx: Fix T-Com Speedport W 500V default config.

2011-02-09 Thread Florian Fainelli
On Thursday 03 February 2011 23:36:06 Jonas Gorski wrote: > The device is called SPW500V, not SP500W. > > Signed-off-by: Jonas Gorski > --- Applied in r25431, thanks Jonas! ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.op

[OpenWrt-Devel] Compiling for EABI on armv4 CPUs

2011-02-09 Thread Jochen Friedrich
Hi, i noticed in r25322 a patch has been committed to support EABI on thumbless ARM v4 CPUs. However, the patch only works if -marmv4 is passed to the linker as the default is armv5t. Unlike openembedded, openwrt does not pass this option to the linker so i modified the patch to #define TARGE

Re: [OpenWrt-Devel] [OpenWrt-Commits] r25414 - trunk/package/hotplug2/patches

2011-02-09 Thread Vasilis Tsiligiannis
On Wednesday 09 February 2011 12:24:26 Mikhail Gusarov wrote: > There was a patch merged in hotplug2 recently which allows wildcard > expansion, so /etc/hotplug2.d/platform.rules could be included from main > file as $include Which one is that? -- Vasilis Tsiligiannis signature.asc Descripti

Re: [OpenWrt-Devel] [OpenWrt-Commits] r25417 - trunk/package/busybox/files

2011-02-09 Thread Vasilis Tsiligiannis
> This is at least an explicit declaration that something else ought to > be treated as ${HOME}; if someone sets it badly, all sorts of things > are subject to failure. All sorts of things can be subject to failure. Remote access cannot. -- Vasilis Tsiligiannis signature.asc Description: This

Re: [OpenWrt-Devel] [OpenWrt-Commits] r25414 - trunk/package/hotplug2/patches

2011-02-09 Thread Mikhail Gusarov
Twas brillig at 12:15:44 09.02.2011 UTC+02 when b_tsiligian...@silverton.gr did gyre and gimble: >> Why not just have the requirement that /etc/hotplug2-platform.rules >> be present, even if it's zero-length? VT> Because an empty include rules file would then be required in base-files VT>

Re: [OpenWrt-Devel] [OpenWrt-Commits] r25414 - trunk/package/hotplug2/patches

2011-02-09 Thread Vasilis Tsiligiannis
> Why not just have the requirement that /etc/hotplug2-platform.rules be > present, even if it's zero-length? Because an empty include rules file would then be required in base-files overrides of each target. -- Vasilis Tsiligiannis signature.asc Description: This is a digitally signed messag