Re: [OpenWrt-Devel] [PATCH] ath79: use downstream ag71xx for Kernel 5.4

Hi David, On Fri, 2020-03-13 at 01:07 +0100, David Bauer wrote: > The ag71xx driver from Linux 5.4 currently has various shortcomings > when used with OpenWrt compared to our downstream version. > > For example, the upstream driver does not support modifying the > ethernet > clock and configuring

[OpenWrt-Devel] V5.4: Probe of eth0 fails on TP-Link Archer A7V5

I get: [0.541856] libphy: Fixed MDIO Bus: probed [0.548637] ag71xx: probe of 1900.eth failed with error -2 On 4.19.98, I get: [0.508331] libphy: Fixed MDIO Bus: probed [1.199161] libphy: ag71xx_mdio: probed [1.206146] switch0: Atheros AR8337 rev. 2 switch registered on md

Re: [OpenWrt-Devel] [PATCH v2] fstools: Add support to read-only MTD partitions (eg. recovery images)

Hi Bruno, Your suggested fix works on my TPLink A7-V5. diff --git a/target/linux/ath79/image/common-tp-link.mk b/target/linux/ath79/image/common-tp-link.mk index 9048e8340c..8aa6a5a2be 100644 --- a/target/linux/ath79/image/common-tp-link.mk +++ b/target/linux/ath79/image/common-tp-link.mk @@ -71

Re: [OpenWrt-Devel] [PATCH v2] fstools: Add support to read-only MTD partitions (eg. recovery images)

gt; On Wed, Jan 22, 2020, 07:13 Bruno Pena wrote: > > Hi Steve, > > > > Thank you for testing. > > You implemented my suggestion correctly but it seems that it didn't > > actually pad anything (the sizes of the partitions should be > > rounded to the nex

Re: [OpenWrt-Devel] [PATCH v2] fstools: Add support to read-only MTD partitions (eg. recovery images)

Hi Bruno, That didn't seem to solve the problem. The padding didn't seem to take effect. I reverted 0f81a0979 and 0c707d37b. dev:size erasesize name mtd0: 0002 0001 "factory-uboot" mtd1: 0002 0001 "u-boot" mtd2: 00ec 0001 "firmware" mtd3: 001a3a07 0001 "kernel"

Re: [OpenWrt-Devel] [PATCH v2] fstools: Add support to read-only MTD partitions (eg. recovery images)

gt; On Tue, Jan 21, 2020, 12:09 Steve Brown wrote: > > Below: > > > > Steve > > > > > > > > /proc/cmdline: > > console=ttyS0,115200n8 rootfstype=squashfs,jffs2 > > > > /proc/mtd: > > mtd0: 0002

Re: [OpenWrt-Devel] [PATCH v2] fstools: Add support to read-only MTD partitions (eg. recovery images)

nclude the contents of "dmesg" and of the files > "/proc/cmdline" and "/proc/mtd". > > Best regards, > Bruno Pena > > On Tue, Jan 21, 2020, 11:01 Bruno Pena wrote: > > Hi Steve, > > > > These patches should only impact partitions

Re: [OpenWrt-Devel] [PATCH v2] fstools: Add support to read-only MTD partitions (eg. recovery images)

tem) readonly on device 31:4. Thanks, Steve On Tue, 2020-01-21 at 11:01 +0100, Bruno Pena wrote: > Hi Steve, > > These patches should only impact partitions that are marked as read > only. > Can you please provide more details about your configuration? > (architecture, devic

Re: [OpenWrt-Devel] [PATCH v2] fstools: Add support to read-only MTD partitions (eg. recovery images)

Hi Bruno, On Sat, 2020-01-04 at 12:52 +0100, Bruno Pena wrote: > This patch enables fstools to open read-only MTD partitions, which in > turn also enables OpenWrt to boot from read-only partitions. > > The use of read-only partitions is of special importance for WiFi- > only > devices, where a pr

Re: [OpenWrt-Devel] OpenWrt 19.03 plans

On Mon, 2019-02-25 at 12:10 +0100, Daniel Engberg wrote: > Hi, > > > Mesh is broken using ath10k-ct? > https://bugs.openwrt.org/index.php?do=details&task_id=2123 > The combination of ath10k-ct and firmware ver 10.2.4-1.0-00043 works on my QCA9880 (tp-link archer a7 v5). According to debugfs, at

Re: [OpenWrt-Devel] [PATCH v2] ar71xx: Allow to use ath79_gpio_output_select on QCA955x

Sven, On Mon, 2015-07-20 at 19:10 +0200, Sven Eckelmann wrote: > Signed-off-by: Sven Eckelmann > --- > v2: Rebased to fix conflict with r46207 > > ...79-add-gpio-func-register-for-QCA955x-SoC.patch | 60 > ++ > ...79-add-gpio-func-register-for-QCA955x-SoC.patch | 60 >

Re: [OpenWrt-Devel] SSB-HCD driver

On Tue, 2012-01-10 at 00:30 +0100, Hauke Mehrtens wrote: > Hi George, > > Also, for bcma-based EHCI to work correctly it requires OHCI to be driven > > as well > > or USB1.1 devices won't work (researched and reported by Joel Crisp > > ) so it seems reasonable to have > > +kmod-usb-ohci in package

Re: [OpenWrt-Devel] new service wrapper in /etc/rc.common

On Thu, 2011-11-10 at 16:02 +0100, Jo-Philipp Wich wrote: > Care to explain what you mean? It looks fine in both Trac and my local > svn checkout. > > ~ Jow > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/

[OpenWrt-Devel] new service wrapper in /etc/rc.common

Patch 28834 doesn't seem to have been completely applied to trunk. The copyright got updated, but the service_xxx stuff didn't with predictable results. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/

Re: [OpenWrt-Devel] [PATCH] mac80211: allow AP configuration of beacon interval, DTIM period, maximum permissible STA listen interval, and basic rates

On 3/3/2011 2:35 PM, Björn Smedman wrote: If I'm not mistaking it's possible to run multiple instances of hostapd, one for each ap vif (created with iw), and configure them with different beacon intervals. But I guess OpenWrt doesn't do that (?), and in that case it seems reasonable to set beacon

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

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 out

[OpenWrt-Devel] toolchain's gdb add-symbol-file doesn't honor file address

The line number is correct, but the start/end addresses ignore the file address. $ ./staging_dir/toolchain-mips_r2_gcc-4.3.3+cs_uClibc-0.9.31/bin/mips-openwrt-linux-gdb GNU gdb 6.8 Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later

[OpenWrt-Devel] Luci & 80211s (mesh)

Luci allows configuring an interface as 80211s. However, there doesn't seem to be any way to configure the mesh_id. The ssid in "Interface Configuration" is set as "option ssid" in /etc/config/wireless, but /lib/wifi/mac80211.sh uses "option mesh_id" to set the mesh_id. Is this a Luci problem or s

Re: [OpenWrt-Devel] BCM5354-based routers fail to boot starting at rev 24167

On Sun, 2010-12-05 at 20:37 +0100, Hauke Mehrtens wrote: > Hi Steve, > > Thank you for reporting and finding the problem. This should be fixed in > trunk for kernel 2.6.36 and 2.6.37 now. > > Hauke The current trunk, r24267, w/ either 2.6.36.1 or 2.6.37-rc4 kernels build and boot on a BCM5354.

Re: [OpenWrt-Devel] BCM5354-based routers fail to boot starting at rev 24167

On Sun, 2010-12-05 at 15:47 +0100, Hauke Mehrtens wrote: > Hi Steve, > > with your change the kernel do not try to access the cfe storage to get > the configuration values, which are not stored there any way. Please try > kernel 2.6.37-rc4, it contains some more fixes and do not try to access > c

Re: [OpenWrt-Devel] BCM5354-based routers fail to boot starting at rev 24167

On Sun, 2010-12-05 at 15:47 +0100, Hauke Mehrtens wrote: > > > > With the patch below, 2.6.36 now boots on both a BCM5352 and BCM5354. > > > > I don't understand enough of what's going on to propose a fix. > > > > Steve > > > > > > Hi Steve, > > with your change the kernel do not try to a

Re: [OpenWrt-Devel] BCM5354-based routers fail to boot starting at rev 24167

On Fri, 2010-12-03 at 20:57 +0100, Hauke Mehrtens wrote: > On 12/03/2010 08:13 PM, Steve Brown wrote: > > Tested on Asus 520gu and 500gpv2. > > > > Hangs at: "Starting program at 0x80001000" > > > > No output thereafter. > > > > Rev 2416

Re: [OpenWrt-Devel] BCM5354-based routers fail to boot starting at rev 24167

On Fri, 2010-12-03 at 20:57 +0100, Hauke Mehrtens wrote: > On 12/03/2010 08:13 PM, Steve Brown wrote: > > Tested on Asus 520gu and 500gpv2. > > > > Hangs at: "Starting program at 0x80001000" > > > > No output thereafter. > > > > Rev 2416

Re: [OpenWrt-Devel] BCM5354-based routers fail to boot starting at rev 24167

On Fri, 2010-12-03 at 20:57 +0100, Hauke Mehrtens wrote: > On 12/03/2010 08:13 PM, Steve Brown wrote: > > Tested on Asus 520gu and 500gpv2. > > > > Hangs at: "Starting program at 0x80001000" > > > > No output thereafter. > > > > Rev 2416

Re: [OpenWrt-Devel] BCM5354-based routers fail to boot starting at rev 24167

On Fri, 2010-12-03 at 20:57 +0100, Hauke Mehrtens wrote: > Hi Steve, > > Thank you for the information. To fix the problem we need some more > informations. Please also test version r24166. > distclean r24166 boots. The same image (r24166) also boots on a BCM5352 (Buffalo whr-hp-g54). > Does th

[OpenWrt-Devel] BCM5354-based routers fail to boot starting at rev 24167

Tested on Asus 520gu and 500gpv2. Hangs at: "Starting program at 0x80001000" No output thereafter. Rev 24162 boots on both routers. Steve ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openw

[OpenWrt-Devel] [PATCH] Allow SSB EHCI/OHCI drivers to co-exist

needed. If only high speed devices are needed or a transaction translating hub that converts low speed devices to high speed, only the ehci driver is required. Signed-off-by: Steve Brown CC: Hauke Mehrtens --- Hauke, thanks for packaging all this for upstream. I'm not sure how to do this wi

[OpenWrt-Devel] wl520gu won't boot after 22423

22423 boots, while 22424 doesn't. I'm building the default 2.6.34.1 kernel. 22424 hangs after these cfe messages: Closing network. Starting program at 0x80001000 Any idea where to start looking? Steve ___ openwrt-devel mailing list openwrt-devel@li

Re: [OpenWrt-Devel] WL500GPv2 USB and 2.6 kernel

On 2/24/2010 11:34 AM, Kövesdi György wrote: You could start with providing some more informations. like: dmesg output, lsmod output, /proc/bus/pci, logread and whatever else seems useful. The boot log and the directory contents of /sys/bus/pci/ are attached. The command lspci says nothing

Re: [OpenWrt-Devel] WL500GPv2 USB and 2.6 kernel

On 2/23/2010 6:45 AM, Kövesdi György wrote: Hi, I have a Asus WL500GPv2 and i would like to use its USB with 2.6 kernel. I downloaded the recent version of openwrt-brcm-2.4- squashfs.trx and everything works well, including the USB. The recent version of openwrt-brcm47xx-squashfs.trx (2.6 kerne

[OpenWrt-Devel] [PATCH] wpa_supplicant.sh is missing initialization for eap_type

Add missing initialization for eap_type. Without it, the generated wpa_supplicant.conf is incomplete. Signed-off-by: Steve Brown --- Index: package/wpa_supplicant/files/wpa_supplicant.sh === --- package/wpa_supplicant/files

Re: [OpenWrt-Devel] [BUG] 2.6.30+: BCM5354 USB LOCKUP (ehci-ssb) due to missed kernel changes

On 12/23/2009 01:57 AM, Andreas Mohr wrote: And I would be very pleased if ehci-ssb.c could find its way into mainline pretty soon, Yeah. Care to do so? Huh what me? :) I'll get this nailed. I wouldn't want this unfortunate thing to happen again. Thanks, Andreas Mohr I ha

Re: [OpenWrt-Devel] [PATCH 1/2] SSB USB - work around for silicon error in bcm5354 usb20 core

On 09/07/2009 08:31 AM, Michael Buesch wrote: On Monday 07 September 2009 15:23:59 Steve Brown wrote: Michael Buesch wrote: On Sunday 16 August 2009 17:23:40 Steve Brown wrote: Found in the Asus GPL sources. This is very noticable with a Seagate FreeAgent drive. Without

Re: [OpenWrt-Devel] [PATCH 1/2] SSB USB - work around for silicon error in bcm5354 usb20 core

Michael Buesch wrote: On Sunday 16 August 2009 17:23:40 Steve Brown wrote: Found in the Asus GPL sources. This is very noticable with a Seagate FreeAgent drive. Without the patch, long writes give a "reset high speed usb" error and hang until the drive is disconnnected. The pa

Re: [OpenWrt-Devel] [PATCH 1/2] SSB USB - work around for silicon error in bcm5354 usb20 core

On 08/16/2009 02:31 PM, Michael Buesch wrote: On Sunday 16 August 2009 17:23:40 Steve Brown wrote: Found in the Asus GPL sources. This is very noticable with a Seagate FreeAgent drive. Without the patch, long writes give a "reset high speed usb" error and hang until th

[OpenWrt-Devel] [PATCH 2/2] SSB USB - allow building ohci driver without also building ehci

Fix build error. Steve 276-ohci-ssb-build.patch Description: application/mbox ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] [PATCH 1/2] SSB USB - work around for silicon error in bcm5354 usb20 core

lf of both the ohci and ehci devices. Reference: GPL/WL-520gu-NewUI/src/linux/linux/arch/mips/brcm-boards/bcm947xx/pcibios.c GPL/WL-500gPV2-NewUI/src/linux/linux/arch/mips/brcm-boards/bcm947xx/pcibios.c Signed-off-by: Steve Brown --- --- a/drivers/usb/host/ohci-ssb.c.orig 2009-07-30 12:03:26.52229

[OpenWrt-Devel] [PATCH] Fix broken i2c module loading in R17269

Strip .ko suffix from module name. Fix typo in name of i2c-scx200-acb module to be loaded. Steve Signed-off-by: Steve Brown --- Index: package/kernel/modules/i2c.mk === --- package/kernel/modules/i2c.mk (revision 17277

Re: [OpenWrt-Devel] warnings compiling b43/main.c "comparison is always false"

Steve Brown wrote: > I get these warnings compiling for brcm47xx w/ wireless-testing tree. > > CC [M] drivers/net/wireless/b43/main.o > drivers/net/wireless/b43/main.c: In function 'b43_qos_params_upload': > drivers/net/wireless/b43/main.c:3085: warning: comparison

[OpenWrt-Devel] warnings compiling b43/main.c "comparison is always false"

I get these warnings compiling for brcm47xx w/ wireless-testing tree. CC [M] drivers/net/wireless/b43/main.o drivers/net/wireless/b43/main.c: In function 'b43_qos_params_upload': drivers/net/wireless/b43/main.c:3085: warning: comparison is always false due to limited range of data type drivers/n

Re: [OpenWrt-Devel] 2.6 kernel and b43 driver

Tomasz Chmielewski wrote: > Steve Brown schrieb: >> Tomasz Chmielewski wrote: >>> Stefan Monnier schrieb: >>> >>> (...) >>> >>> >>>>> The b43 driver now loads, loads firmware and returns scan results. >>>>&

Re: [OpenWrt-Devel] 2.6 kernel and b43 driver

Tomasz Chmielewski wrote: > Stefan Monnier schrieb: > > (...) > > >>> The b43 driver now loads, loads firmware and returns scan results. >>> >> With the above patch (and a freshly updated svn checkout of Kamikaze), >> my WL700gE indeed loads the driver, it seems to load the firmware as >>

Re: [OpenWrt-Devel] 2.6 kernel and b43 driver

v2). > > Steve can you verify the modifications of the test, please, I want to > reproduce the result. > > } //else > //ssb_pcicore_dev_irqvecs_enable(&sdev->bus->pcicore, sdev); > > Thanks, > Fmay > On Fri, 2008-07-04 at 20:33 -0400, Steve Brown wrote: >

Re: [OpenWrt-Devel] 2.6 kernel and b43 driver

Forgot the cc's. And to close the thread. Michael Buesch wrote: > On Friday 04 July 2008 21:39:46 Steve Brown wrote: > >> Michael Buesch wrote: >> >>> On Tuesday 01 July 2008 21:50:43 Steve Brown wrote: >>> >>> >>>> I

Re: [OpenWrt-Devel] 2.6 kernel and b43 driver

Michael Buesch wrote: > On Tuesday 01 July 2008 21:50:43 Steve Brown wrote: > >> It looks like (almost) every other phy register doesn't respond. I put >> in a large (200us) delay between accesses with no change in behaviour. >> If it is timing, it must be on

Re: [OpenWrt-Devel] 2.6 kernel and b43 driver

Michael Buesch wrote: > I'm sorry, I cannot tell you what causes this. But I guess, however, > it is some change in the ssb setup code that broke this. > > Here's some more evidence. I scanned the phy register space using get_dbe. Here are the results: Addr Value 3e0 0x3207 (looks ok) 3

Re: [OpenWrt-Devel] 2.6 kernel and b43 driver

Michael Buesch wrote: > On Sunday 29 June 2008 15:12:47 Steve Brown wrote: > >> What should I do next? >> > > Can you try this patch? > > Index: wireless-testing/drivers/net/wireless/b43/main.c > =

Re: [OpenWrt-Devel] 2.6 kernel and b43 driver

Steve Brown wrote: > Peter Denison wrote: > >> Rather than saying "current svn", it would really help if you can >> state the exact revision you're using. To summarise the reports at >> #3510 and here, b43 seems to work on r10154, but not on r11363, r1

Re: [OpenWrt-Devel] 2.6 kernel and b43 driver

Peter Denison wrote: > Rather than saying "current svn", it would really help if you can > state the exact revision you're using. To summarise the reports at > #3510 and here, b43 seems to work on r10154, but not on r11363, r11372 > or r11579. > > Unfortunately, I don't have a huge amount of tim

Re: [OpenWrt-Devel] 2.6 kernel and b43 driver

Stefan Monnier wrote: > I'm trying to use my WL-700gE's wifi card with the b43 driver but bumped > into the problem reported at https://dev.openwrt.org/ticket/3510. > > This is with revision 11579 of the svn trunk. > > Is there something I can do to try and help resolve this problem? > > >

Re: [OpenWrt-Devel] [PATCH] Add ehci host support for BCM5354 USB20 core

Felipe Maya wrote: > Ooops, Sorry for the confusion... The patch (ehci-ssb support) wasn't > applied correctly in my distribution. I had to apply the patch manually. > > Something wrong happens applying this patch (wl500gp-v2): > > //ping message/ > PING 192.168.1.1 (192.168.1.1) 56(84) byt

Re: [OpenWrt-Devel] [PATCH] Add ehci host support for BCM5354 USB20 core

Felipe Maya wrote: > The patch works with one USB port, but with two USB simultaneously > something wrong happens. > > I changed the driver_mipscore.c to enable SSB_DEV_USB11_HOST for bcm5354 > at this line (208): > > > if (((bus->chip_id == 0x4710) || (bus->chip_id == 0x5354)) && (irq <= > 4))

Re: [OpenWrt-Devel] [PATCH] Add ehci host support for BCM5354 USB20 core

Michael Buesch wrote: > On Monday 09 June 2008 13:48:35 Steve Brown wrote: > >> This adds support to ehci-hcd for the ehci host function of the USB20 ssb >> core in the Broadcom BCM5354. That core implements both ehci and ohci. The >> support is implemented as a lib

[OpenWrt-Devel] [PATCH] Add ehci host support for BCM5354 USB20 core

load before the ohci-hcd driver. Signed-off-by: Steve Brown <[EMAIL PROTECTED]> Cc: Michael Buesch <[EMAIL PROTECTED]> --- diff --git a/package/kernel/modules/usb.mk b/package/kernel/modules/usb.mk index e4868eb..5ed16ad 100644 --- a/package/kernel/modules/usb.mk +++ b/package/ke

Re: [OpenWrt-Devel] [PATCH] Add ehci host support for BCM5354 USB20 core

Michael Buesch wrote: On Sunday 08 June 2008 02:08:14 Steve Brown wrote: This adds support for the ehci host function of the USB20 ssb core in the Broadcom BCM5354 to the ehci-hcd driver. That core implements both ehci and ohci. The driver is implemented as a library or extension to the

[OpenWrt-Devel] [PATCH] Add ehci host support for BCM5354 USB20 core

before the ohci-hcd driver. Signed-off-by: Steve Brown <[EMAIL PROTECTED]> --- diff --git a/package/kernel/modules/usb.mk b/package/kernel/modules/usb.mk index e4868eb..5ed16ad 100644 --- a/package/kernel/modules/usb.mk +++ b/package/kernel/modules/usb.mk @@ -27,6 +27,10 @@ define

Re: [OpenWrt-Devel] [PATCH] usb ehci driver for ssb

Michael Buesch wrote: > On Wednesday 04 June 2008 23:56:36 Steve Brown wrote: > >> Here is another cut at an ssb ehci driver. >> >> Hope this is closer. >> >> Steve >> >> >> > > Ok, looks a lot better. Thanks. > But I&#

Re: [OpenWrt-Devel] [PATCH] usb ehci driver for ssb

Here is another cut at an ssb ehci driver. Hope this is closer. Steve diff --git a/target/linux/brcm47xx/config-2.6.25 b/target/linux/brcm47xx/config-2.6.25 index 6ddcd22..720d961 100644 --- a/target/linux/brcm47xx/config-2.6.25 +++ b/target/linux/brcm47xx/config-2.6.25 @@ -257,10 +257,13 @@ CO

Re: [OpenWrt-Devel] [PATCH] usb ehci driver for ssb

Michael Buesch wrote: > On Monday 02 June 2008 23:30:52 Steve Brown wrote: > >> This patch adds a ssb ehci driver as well as support for ssb >> multifunction cores. >> >> It is needed to use the ehci function in the BCM5354's USB2 core. >> >> See

Re: [OpenWrt-Devel] brcm47xx 2.6 still does not compile

Steve Brown wrote: > Peter Denison wrote: > >> On Tue, 20 May 2008, Steve Brown wrote: >> >> >>> My BCM5354 (Asus WL520gu) hangs on on boot after the "Entry at >>> 0x80001000". Nothing after. >>> >>> The same image bo

[OpenWrt-Devel] [PATCH] usb ehci driver for ssb

igned-off-by: Steve Brown <[EMAIL PROTECTED]> diff --git a/target/linux/brcm47xx/config-2.6.23 b/target/linux/brcm47xx/config-2.6.23 index 41b440b..92247db 100644 --- a/target/linux/brcm47xx/config-2.6.23 +++ b/target/linux/brcm47xx/config-2.6.23 @@ -220,6 +220,8 @@ CONFIG_TRAD_SIGNALS=

Re: [OpenWrt-Devel] brcm47xx 2.6 still does not compile

Peter Denison wrote: > On Tue, 20 May 2008, Steve Brown wrote: > >> My BCM5354 (Asus WL520gu) hangs on on boot after the "Entry at >> 0x80001000". Nothing after. >> >> The same image boots fine on a BCM4704 (Asus WL500GP) and a BCM5352 >> (Buffalo WHR-

Re: [OpenWrt-Devel] brcm47xx 2.6 still does not compile

; From: "Peter Denison" <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED], "OpenWrt Development List" > > Sent: Ter, Maio 20, 2008 5:23 am > Subject: Re: [OpenWrt-Devel] brcm47xx 2.6 still does not compile > > On Mon, 19 May 2008, Steve Brown wrote: > >

Re: [OpenWrt-Devel] brcm47xx 2.6 still does not compile

Dirk Nehring wrote: > [...] > make[5]: Leaving directory > `/home/technik/dnehring/openwrt/build_dir/linux-brcm47xx/linux-2.6.25.1' > make[5]: Entering directory > `/home/technik/dnehring/openwrt/build_dir/linux-brcm47xx/linux-2.6.25.1' > CHK include/linux/version.h > CHK include/linu