This applies to the packages feed. It fixes a case with newer groff
returning different warming messages than expected by the libX11 build
infrastructure expects. This patch was shamelessly swiped from Ubuntu's
package.
---
.../libX11/patches/010-ignore-groff-warnings.patch | 13
I built 2.6.37.6 for both geos and net5501 and it builds fine.
Index: target/linux/x86/Makefile
===
--- target/linux/x86/Makefile (revision 26456)
+++ target/linux/x86/Makefile (working copy)
@@ -12,7 +12,7 @@
FEATURES:=squashfs
On 2011-04-04 1:22 AM, Philip Prindeville wrote:
The previous technique didn't work with "make defconfig" correctly.
Signed-off-by: Philip Prindeville
Applied in r26458
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openw
The previous technique didn't work with "make defconfig" correctly.
Signed-off-by: Philip Prindeville
Index: target/linux/x86/geos/target.mk
===
--- target/linux/x86/geos/target.mk (revision 26456)
+++ target/linux/x86/geos/targe
Hello
This patch add accounting configuration in hostapd.sh
It also change "server, port, key" to "auth_server, auth_port, auth_secret" but
keep backward compatibility
Please patch backfire & trunk
Thanks in advance.
Signed-off-by: Etienne CHAMPETIER
---
Add two helpers for generating correctly tagged images for the T-Home
Speedport W 303V Typ B as well as xor'd ones as required by CFE.
Signed-off-by: Jonas Gorski
---
tools/firmware-utils/Makefile |2 +
tools/firmware-utils/src/spw303v.c | 242 +++
too
This two patches add support for the T-Home Speedport W 303V Typ B, a
Broadcom BCM6358 based ADSL router with VoIP support.
While the device itself is a more or less standard ADSL router/AP, T-Com
(or their supplier) took some measures to make flashing custom firmwares a
bit harder. They modified
Add the required board definition, default config and image generation for
the T-Home Speedport W 303V Typ B.
Signed-off-by: Jonas Gorski
---
.../base-files/etc/defconfig/96358-502V/network| 14
target/linux/brcm63xx/base-files/lib/brcm63xx.sh |5 +
target/linux/brcm63xx/image/M
On Tuesday 01 February 2011 00:02:51 Arnold Schulz wrote:
> Hi there,
>
> would be nice if this could be added to OpenWrt...
>
> Cheers,
> Arnold
>
>
> Changed:
> - Support added for mISDN card driver for Cologne AG's HFC pci cards
> (single port) - Title texts and help texts for some other isd
On Tuesday 29 March 2011 14:26:04 Peter Wagner wrote:
> busybox 1.18.4 update patch for rev 26356
Applied in r26455, tested with Malta, Realview and UML, thanks Peter!
--
Florian
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lis
On Saturday 02 April 2011 10:29:04 Ian Leonard wrote:
> This adds a profile to ffmpeg to support minidlna, similar to the
> libdlna/ushare profile. When minidlna encounters media, it uses ffmpeg to
> figure out what it is. If ffmpeg fails to open it, then minidlna will try
> and fail to read the fi
On Wednesday 02 February 2011 21:14:12 Łukasz Stelmach wrote:
> Netfilter LED target triggers blinkenlichten when a network packet hits
> a rule.
>
> LED target requires iptables 1.4.9 or higher
>
> Signed-off-by: Łukasz Stelmach
>
Applied in r26451, thanks!
--
Florian
___
On Saturday 02 April 2011 10:26:47 Ian Leonard wrote:
> This series, along with previous applied patches, should close tickets
> #7837 and #8831.
>
> This patch exposes additional decoders and demuxers for FFmpeg in
> menuconfig, along with other minor changes.
>
> Additional decoders:
> flac (Fr
ok very thanks!
send me a nudge when it is ready ;)
2011/4/3 Felix Fietkau :
> On 2011-04-03 7:34 PM, Gioacchino Mazzurco wrote:
>>
>> yes this fixed...
>>
>> but why simply naming the wifi-iface section break things??
>>
>> on madwifi devices I do the same thing and it work fine...
>
> The probl
On 2011-04-03 7:34 PM, Gioacchino Mazzurco wrote:
yes this fixed...
but why simply naming the wifi-iface section break things??
on madwifi devices I do the same thing and it work fine...
The problem is the name clash between the wifi-iface section and the
network section from /etc/config/netwo
yes this fixed...
but why simply naming the wifi-iface section break things??
on madwifi devices I do the same thing and it work fine...
i have to open a issue on bug tracker ?
2011/4/3 Felix Fietkau :
> On 2011-04-03 7:15 PM, Gioacchino Mazzurco wrote:
>>
>> Here is it
>>
>> 2011/4/2 Felix Fie
On 2011-04-03 7:15 PM, Gioacchino Mazzurco wrote:
Here is it
2011/4/2 Felix Fietkau:
On 2011-04-02 10:57 PM, Gioacchino Mazzurco wrote:
i can confirm that adhoc is still not working in backfire r26417
here is my /etc/config/wireless
config 'wifi-device' 'radio0'
option 'type'
The makefile was missing the source filename, so it would install a directory
instead of
the coefficients file, breaking voice applications.
Signed-off-by: Luca Olivetti
---
Index: package/ltq-vmmc/Makefile
===
--- package/ltq-vm
Dual image capable CFEs store an image sequence at the same place as
currently OpenWrt stores the actual rootfs length, so it will get
overwritten when flashing through such a CFE.
To prevent this from happening, move the rootfs length field to the next
four bytes, thus completely using the reserv
On 03/30/2011 02:58 PM, Peter Wagner wrote:
> update linux to 2.6.37.6
>
Hi Peter,
Thank you for the patch.
It is applied in r26441 with a small change in
target/linux/generic/patches-2.6.37/801-usb_serial_endpoint_size.patch
Hauke
___
openwrt-devel ma
On 3 April 2011 15:28, Peter Lebbing wrote:
> Hi,
>
> On 03/04/11 14:37, Jonas Gorski wrote:
>> Looking at the datasheet, the chip seems to have Chip ID registers at
>> A0/A1 (p. 161). You can try to read them in the adm6996_probe and use
>> them to verify the chip is an ADM6996M (or do chip ident
Hi,
On 03/04/11 14:37, Jonas Gorski wrote:
> Looking at the datasheet, the chip seems to have Chip ID registers at
> A0/A1 (p. 161). You can try to read them in the adm6996_probe and use
> them to verify the chip is an ADM6996M (or do chip identification
> based on them). At least the ADM6996F dat
On 3 April 2011 14:16, Peter Lebbing wrote:
> This driver implements support for 802.1Q VLANs. It is written for the
> ADM6996M switch chip, but there are currently problems with the chip
> detection. It also triggers on other ADM6996 models, and before this patch
> can be committed, it needs to b
> could oyu resent the all in one patch to the list so patchwork grabs the
> full version, currently only the fix is listed in patchwork
A new version of the patch.
Please note it is a patch on latest backfire. The patch should apply to
trunk, but the directory generic-2.6 was renamed to generic!
This is for an r26418 image generated locally for the Ubiquiti M900 series.
The signal strength forecast by Radio Mobile is -68 dBm. The path is
2 Km. Clearly, there is one tree in the Fresnel zone; if wrong about
the Fresnel zone, the worst case is 300 meters of trees without much
foliage this
25 matches
Mail list logo
