[OpenWrt-Devel] [RFC] Several small fixes for the ar8216 driver.

tuations where the vlan's VIDs aren't the same as their position in the table. Regards, Jonas Gorski Several-small-fixes-for-ar8216-driver.patch Description: Binary data ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https

Re: [OpenWrt-Devel] AR7240 switch // was: TP-Link TL-WR741ND: broadcasts on ethernet not reaching CPU

t the ar7240 dsa driver to it. Best regards, Jonas Gorski [1] <https://forum.openwrt.org/viewtopic.php?pid=104435#p104435> and following posts [2] <http://patchwork.ozlabs.org/patch/16578/> ___ openwrt-devel mailing list openwrt-devel@list

Re: [OpenWrt-Devel] AR7240 switch // was: TP-Link TL-WR741ND: broadcasts on ethernet not reaching CPU

Hi On 14 March 2010 00:07, Joerg Albert wrote: > On 03/13/2010 09:29 PM, Jonas Gorski wrote: > The revision of the AR7240 is 2. Another way to identify the device may be > the ID of the > integrated PHYs (AR7240 004d:d041) If the revision is different we can use that. Unfortunatel

[OpenWrt-Devel] [PATCH 0/2] Add support for ar8316.

braking config_probe, the full 4k entries makes it bigger than 12kB and therefore bigger than kmalloc's max value. * Jumbo frames are always enabled on ar8316, but the cpu can't receive them since the ag71xx driver has no jumbo frame support. Best Regards, Jonas Gorski Jon

[OpenWrt-Devel] [PATCH 1/2] Add support for the ar8316 switch.

This patch enhances the ar8216 driver with ar8316 support and fixes some minor issues with the ar8216 driver itself. It should not break anything, but isn't tested on ar8216 devices. --- .../generic-2.6/files/drivers/net/phy/ar8216.c | 233 .../generic-2.6/files/drivers/n

[OpenWrt-Devel] [PATCH 2/2] ar71xx: Add the ar8316 driver to rs pro/rb-450g.

Add the ar8216 driver to the ar71xx target, and add network configurations for the RouterStation Pro and the RouterBoard RB-450G. --- .../base-files/etc/defconfig/rb-450g/network | 27 .../etc/defconfig/routerstation-pro/network| 11 target/linux/ar7

[OpenWrt-Devel] [PATCH v2 0/2] Add support for ar8316.

't receive them since the ag71xx driver has no jumbo frame support. * The internal port numbers have nothing in common with the labels on the ports. * The port 1 isn't usable on the RouterStation Pro. Best Regards, Jonas Gorski Gorski (2): Add support for the ar8316 switch. ar71

[OpenWrt-Devel] [PATCH v2 1/2] Add support for the ar8316 switch.

This patch enhances the ar8216 driver with ar8316 support and fixes some minor issues with the ar8216 driver itself. It should not break anything, but isn't tested on ar8216 devices. --- .../generic-2.6/files/drivers/net/phy/ar8216.c | 231 .../generic-2.6/files/drivers/n

[OpenWrt-Devel] [PATCH v2 2/2] ar71xx: Add the ar8316 driver to rs pro/rb-450g.

Add the ar8216 driver to the ar71xx target, and add network configurations for the RouterStation Pro and the RouterBoard RB-450G. --- .../base-files/etc/defconfig/rb-450g/network | 26 .../etc/defconfig/routerstation-pro/network| 10 +++ target/linux/ar71

[OpenWrt-Devel] [PATCH] nmap: Add nmap-os-db to package.

This patch adds nmap-os-db to the nmap package. Nmap cannot identify OS's without it (actually it doesn't even try). Signed-off-by: Jonas Gorski --- net/nmap/Makefile |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/net/nmap/Makefile b/net/nmap/Makefile ind

Re: [OpenWrt-Devel] [PATCH v2 0/2] Add support for ar8316.

Hi, any comments on these patches? It would be really nice if these made it into backfire, as they not only make vlan configuration possible, but also solve a multicast problem for the Routerstation Pro (and probably the RB450G/750G). Regards, Jonas Gorski

Re: [OpenWrt-Devel] [PATCH v2 0/2] Add support for ar8316.

ader => packet gets dropped I'll take a look at where the ag71xx should call the phy's netif_rx(), this should make the special ar8216 support obselete in general. Regards, Jonas Gorski ___ openwrt-devel mailing list openwrt-devel@lists.openw

[OpenWrt-Devel] [PATCH] ag71xx: Fix ar8216 devices and remove the ar8216 workaround.

the ag71xx driver to call ar8216's netif_receive_skb. This patch removed the ar8216 packet header workaround in the ag71xx driver and instead calls ar8216's netif_receive_skb so that there is only header handling if it enabled. Regards, Jonas Gorski Signed-off-by: Jonas Gorski --- ta

Re: [OpenWrt-Devel] Support for AR8216

derived > from the AR8216? > ag71xx_mdio.c::ag71xx_mdio_reset() sets the divider to 6 for the AR7240. No, that one does gets controlled through MDIO, but uses a different driver that doesn't make most features available. Regards, Jonas Gorski ___ openwrt-de

Re: [OpenWrt-Devel] [PATCH v2 0/2] Add support for ar8316.

Hi, I hope you don't mind if I move the discussion back to openwrt-devel. Answering only you wasn't intentional; I changed my default now to "reply all" so it doesn't happen again. On 7 April 2010 17:12, Gabor Juhos wrote: > Jonas Gorski írta: >> On 6 Ap

Re: [OpenWrt-Devel] [PATCH v2 0/2] Add support for ar8316.

ve_skb, but it doesn't. I'll send a patch shortly. After that all devices where the AR8216 driver attaches successfully do not need their has_ar8216 flag anymore, as then the phy driver itself can handle it. The problems with the ar8216 driver itself will be adressed in a separa

[OpenWrt-Devel] [PATCH] ag71xx: call the phy driver's netif_receive_skb()

Ag71xx needs to call the phy's netif_receive_skb() to allow phy drivers to mangle rx packets. This patch fixes it. This fixes the header mangling of the AR8216 driver. Signed-off-by: Jonas Gorski --- .../linux/ar71xx/files/drivers/net/ag71xx/ag71xx.h |2 +- .../ar71xx/files/driver

Re: [OpenWrt-Devel] [PATCH] ag71xx: call the phy driver's netif_receive_skb()

On 9 April 2010 10:41, Gabor Juhos wrote: > Applied: https://dev.openwrt.org/changeset/20750 Thanks, Jonas P.S: Looks like email address anonymization in trac only works for the first address: > Signed-off-by: Jonas Gorski > Cc:backf...@op

[OpenWrt-Devel] [PATCH] Generic: Clean up output of AR8216 driver.

taching as phy driver. * Correctly return NET_RX_DROP when dropping packets. Signed-off-by: Jonas Gorski --- .../generic-2.6/files/drivers/net/phy/ar8216.c | 14 -- 1 files changed, 8 insertions(+), 6 deletions(-) diff --git a/target/linux/generic-2.6/files/drivers/net/phy/a

[OpenWrt-Devel] [PATCH 2/2] swconfig: Add cpu port index to help output.

Let swconfig provide the cpu port index in its help page. This is needed as e.g. Atheros switches have their cpu port at port 0, not port 5. This could allow e.g. luci to get a rough overview of the layout of the switch. Signed-off-by: Jonas Gorski --- package/swconfig/src/cli.c

[OpenWrt-Devel] [PATCH] swconfig: Check vlan/port indexes for validity.

Swconfig needs to make sure that requested vlans/ports actually exist, else it might read or modify memory not belonging to itself. This patch adds a quick range check in swconfig's kernel part to prevent accidential or intentional memory modification. Signed-off-by: Jonas G

Re: [OpenWrt-Devel] [PATCH 2/2] swconfig: Add cpu port index to help output.

On 9 April 2010 20:15, Jonas Gorski wrote: > [PATCH 2/2] swconfig: Add cpu port index to help output. Oops. There isn't a 1/2 for this. I accidentially generated numbered patches. Regards, Jonas Gorski ___ openwrt-devel mailing list openw

[OpenWrt-Devel] [PATCH] swconfig: Fix switch name.

This patch fixes a small typo in swconfig's client side that caused it to print the interface name instead of the switch's device name on the help page. Signed-off-by: Jonas Gorski --- package/swconfig/src/swlib.c |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git

Re: [OpenWrt-Devel] [PATCH] Disable IPv6 autoconfiguration

ion on "dhcp" interfaces, too. You might have a DHCPv6 server (I don't know how common these are), so this making this an option makes more sense, IMHO. Regards, Jonas Gorski ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] [PATCH] ngircd: Add berlios mirror.

Add the official berlios mirror to ngircd's download urls so it doesn't brake when ngircd.barton.de is down. Signed-off-by: Jonas Gorski --- net/ngircd/Makefile |4 +++- 1 files changed, 3 insertions(+), 1 deletions(-) diff --git a/net/ngircd/Makefile b/net/ngircd/Makefile ind

[OpenWrt-Devel] OpenWRT on T-Com Speedport W500V

). Since this device seems to be virtually indistinguishable from a default 96348GW, it looks like it needs a special image. Any pointers on how to do that? Best regards, Jonas Gorski ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https

Re: [OpenWrt-Devel] OpenWRT on T-Com Speedport W500V

Hi Florian, On 17 June 2010 23:40, Florian Fainelli wrote: > Most likely you will not be able to use a fixup just like the neufbox4 because > that one still contains a valid identifier somewhere on the flash. Yeah, I figured that too. > I guess the only solution we have is to pass some informat

Re: [OpenWrt-Devel] OpenWRT on T-Com Speedport W500V

Hi Florian, On 18 June 2010 13:13, Florian Fainelli wrote: >> 1. Extend imagetag with an additional parameter to set this field. >> 2. Add a Build/Image/W500V* and call it in bcm63xx/image/Makefile >> 3. Add a fixup to the kernel in setup.c that checks for it (also, add >> the board info itself).

[OpenWrt-Devel] [PATCH] Firmware-utils: Add support for board id overrides for bcm63xx.

Add a switch for using the information1 field to hardcode a board id in the bcm tag for boards that don't provide any usable identification but need special handling. Signed-off-by: Jonas Gorski --- tools/firmware-utils/src/imagetag.c | 19 ++- 1 files changed, 14 inser

[OpenWrt-Devel] [PATCH] bcm63xx: Add very basic support for the T-Com Speedport W 500V.

Add support for the T-Com Speedport W 500V using a special tagged image as it identifies itself as a 96348GW, but has some gpios wired differently, and also has only one ethernet port. Signed-off-by: Jonas Gorski --- target/linux/brcm63xx/image/Makefile | 10 +++ .../patches

[OpenWrt-Devel] [PATCH] bcm63xx: Add basic support for T-Com Speedport W 500V.

tside. Jonas Gorski (3): Firmware-utils: Add support for board id overrides for bcm63xx. bcm63xx: Add board id override fixup. bcm63xx: Add very basic support for the T-Com Speedport W 500V. target/linux/brcm63xx/image/Makefile | 10 +++ .../patches-2.6.3

[OpenWrt-Devel] [PATCH] bcm63xx: Add board id override fixup.

Add a fixup for the kernel to check the bcm tag of the image for a board id in the information1 field, and use that instead of the supplied one by cfe. Signed-off-by: Jonas Gorski --- .../patches-2.6.32/270-generic_boardid_fixup.patch | 42 1 files changed, 42 insertions

Re: [OpenWrt-Devel] Is this router openwrt compatible?

Hi, On 25 June 2010 21:58, Gioacchino Mazzurco wrote: > Hey all! > I see this big promotion on axuse.com site > http://www.axuse.com/produkt/AX10447/Router_TLWR340G_TPLink/448/24/001001004/en/ > > I am looking for if it is compatible with openwrt, and if it support > multiple Acces Point with one

Re: [OpenWrt-Devel] Solos 4610 (conexant) adsl router, anyone?

Hi, On 29 July 2010 15:36, Stefan Monnier wrote: > I inherited from a DSL modem+router whose firmware describe as a "Solos > 4610 RD / Solos 461x CSP v1.0", and telnet shows me a big > `conexant' banner. Just going from the hardware, this seems to be a Connexant CX96410 based device. There is no

Re: [OpenWrt-Devel] [PATCH] ramips: allow USB

Hello, some (more or less) generic comments: On 14 August 2010 10:39, Luis Correia wrote: > (...) > --- target/linux/ramips/rt305x/config-2.6.32    (revision 22631) > +++ target/linux/ramips/rt305x/config-2.6.32    (working copy) > @@ -149,8 +149,6 @@ >  CONFIG_TRAD_SIGNALS=y >  # CONFIG_TREE_PR

Re: [OpenWrt-Devel] [PATCH V2] ramips: allow USB

Hi Luis, On 16 August 2010 00:59, Luis Correia wrote: > (...) > --- target/linux/ramips/rt305x/config-2.6.32(revision 22663) > +++ target/linux/ramips/rt305x/config-2.6.32(working copy) > (...) > +CONFIG_USB=y kmod-usb-core already provides this built as a module, so installing that sho

Re: [OpenWrt-Devel] [PATCH] kmod-sctp: Add SCTP kernel support

Hello Sebastien, On 18 August 2010 09:32, Sebastien Decugis wrote: > (...) > + CONFIG_IP_SCTP=m \ > (...) > + KCONFIG:=CONFIG_LIBCRC32C=m The "=m" isn't necessary, this is implied as default. > (...) > diff --git a/target/linux/generic/config-2.6.34 > b/target/linux/generic/config-2.6.34

Re: [OpenWrt-Devel] [PATCH] Modifying target/linux/kirkwood to add Dockstar

Hi Gerrit, great to see some progress on the DockStar front :) On 21 August 2010 22:13, Gerrit Visser wrote: > Presently there is a default target for the Sheevaplug. The Seagate Dockstar > is similar but due to kernel differences I separated into 2 Targets: > GlobalScale and CloudEngines, each

Re: [OpenWrt-Devel] Development board/unit

On 21 September 2010 11:14, Dennis M.D. Ljungmark wrote: > Ahoy, >   We're currently looking at aquiring a few development boards for > running OpenWRT on,  ( not the other way around, for once) so I figured > I'd ask here, what's a decent board/hardware unit to make a few proof of > concept units

Re: [OpenWrt-Devel] Development board/unit

On 21 September 2010 12:43, Jonas Gorski wrote: > The Routerstation Pro is always a good start, it's even part of an > official MIPS evaluation kit. Plenty of Ram (128 MB), gigabit > ethernet, JTAG, USB, three mini-PCI slots, etc. Another less expensive alternative would be t

Re: [OpenWrt-Devel] Development board/unit

On 22 September 2010 11:32, Dennis M.D. Ljungmark wrote: > Looks like the dockstar would be near perfect for me, cheap and nice and > prefab. > > The bifferboard looks _very_ tempting though I fear the lack of FPU may > cause SSL to be a bit of a tight fit. Though I guess some ciphers might > work

Re: [OpenWrt-Devel] Problem adding a new package

Hi, On 23 September 2010 14:16, Stephen Thornton wrote: > it works just fine for my kernel-mod) but when I hit make it refuses to > build the package (same for make V=99). > > Foo666-2:trunk steve$ make package/matrix-apd/compile V=99 > make[1]: Entering directory `/Volumes/Development/trunk' > m

[OpenWrt-Devel] [PATCH] [RTL8366S/RB] Fix autonegotiation for the WAN port.

The RTL8366S/RB support connecting a second mac to it and using the 5th port as an independent phy. Therefore we need to handle autonegotiation changes for phy 4 like on a single phy device. This fixes #7980, verified on a WNDR3700. Signed-off-by: Jonas Gorski --- .../generic/files/drivers/net

[OpenWrt-Devel] [PATCH v2] RTL8366S/RB: Fix autonegotiation for the WAN port.

The RTL8366S/RB support connecting a second mac to it and using the 5th port as an independent phy. Therefore we need to handle autonegotiation changes for phy 4 like on a single phy device. This fixes #7980, verified on a WNDR3700. Signed-off-by: Jonas Gorski --- .../generic/files/drivers/net

Re: [OpenWrt-Devel] [PATCH] add rtl8366 switch kernel packages

Hi On 29 September 2010 13:22, Roman Yeryomin wrote: > Add rtl8366 switch kernel packages so that they could be selected if a > user has board with such switch. I do not think this will work for most targets. The last time I tried, phy devices are only probed on ethernet device driver registrati

Re: [OpenWrt-Devel] [PATCH v2] RTL8366S/RB: Fix autonegotiation for the WAN port.

On 27 September 2010 16:52, Gabor Juhos wrote: > 2010.09.24. 13:13 keltezéssel, Jonas Gorski írta: >> The RTL8366S/RB support connecting a second mac to it and using the 5th >> port as an independent phy. Therefore we need to handle autonegotiation >> changes for phy 4 like o

[OpenWrt-Devel] [PATCH 1/3] ZNC: upate to 0.094.

Update ZNC to the newest version. Building modules cannot be disabled anymore, so just remove the only one that doesn't build (webadmin). Signed-off-by: Jonas Gorski --- net/znc/Makefile |9 + 1 files changed, 5 insertions(+), 4 deletions(-) diff --git a/net/znc/Makefile b/ne

[OpenWrt-Devel] [PATCH 2/3] ZNC: Package modules.

Create packages for all modules except webadmin, since it doesn't compile. The extra modules are ignored for now. Signed-off-by: Jonas Gorski --- net/znc/Makefile | 526 +- 1 files changed, 524 insertions(+), 2 deletions(-) diff --git

[OpenWrt-Devel] [PATCH 3/3] ZNC: Add startup script and uci config.

Add a startup and a uci configuration for ZNC. This allows configuring multiple users, loading modules with parameters (global and per user) and starts the ZNC binary as nobody. The latter requires su, so add this as a dependecy. Signed-off-by: Jonas Gorski --- net/znc/Makefile | 10

Re: [OpenWrt-Devel] [PATCH 2/3] ZNC: Package modules.

On 25 October 2010 04:04, Outback Dingo wrote: > > Committed revision 23627 - Reverts Commit 23626 - Needs fixing I'd gladly fix it, but I need something more specific than "needs fixing" ;-). It builds and runs fine for me on ar71xx, current trunk. Regards, Jonas ___

[OpenWrt-Devel] [PATCH] ZNC: Add extra modules and include droproot.

Also build and package the extra modules and package the droproot module with ZNC. This allows dropping the dependency to coreutils-su. Signed-off-by: Jonas Gorski --- net/znc/Makefile | 41 ++--- net/znc/files/znc.init |4 +++- 2 files changed

[OpenWrt-Devel] [PATCH] CUPS: Update to 1.4.4.

Update CUPS to current 1.4.4: "CUPS 1.4.4 fixes several security, scheduler, printing, and conformance issues." Also remove PKG_BUILD_DEPENDS, since zlib is already a normal dependency. Signed-off-by: Jonas Gorski --- Tested on ar71xx, running fine for over a week. net/cups/Makef

[OpenWrt-Devel] [PATCH v2 0/4] bcm63xx: Add support for T-Com Speedport W 500V.

adds a way of defining custom default configurations for different devices. This is mostly copied verbatim from the ar71xx target. The final patch adds the actual definition for the Speedport, and also adds the image generation part for it. Jonas Gorski (4): Firmware-utils: Add support for board

[OpenWrt-Devel] [PATCH v2 1/4] Firmware-utils: Add support for board id overrides for bcm63xx.

Add a switch for using the information1 field to hardcode a board id in the bcm tag for boards that don't provide any usable identification but need special handling. Signed-off-by: Jonas Gorski --- tools/firmware-utils/src/imagetag.c | 19 ++- 1 files changed, 14 inser

[OpenWrt-Devel] [PATCH v2 2/4] bcm63xx: Add board id override fixup.

Add a fixup for the kernel to check the bcm tag of the image for a board id in the information1 field, and use that instead of the supplied one by cfe. Signed-off-by: Jonas Gorski --- .../patches-2.6.35/400-generic_boardid_fixup.patch | 42 1 files changed, 42 insertions

[OpenWrt-Devel] [PATCH v2 4/4] bcm63xx: Add support for the T-Com Speedport W 500V.

Add support for the T-Com Speedport W 500V using a special tagged image as it identifies itself as a 96348GW, but has some gpios wired differently, and also has only one ethernet port without a switch attached to it. Signed-off-by: Jonas Gorski --- v1 -> v2: * added has_uart0 * added netw

[OpenWrt-Devel] [PATCH v2 3/4] bcm63xx: Add defconfigs.

Port the mechanism for different default configurations from ar71xx and use the old configuration as the default configuration. This should have no functional differences to before. While we are at it, remove the obsolete nat option. Signed-off-by: Jonas Gorski --- .../linux/brcm63xx/base-files

Re: [OpenWrt-Devel] [PATCH] ag71xx: Fix ar8216 devices and remove the ar8216 workaround.

On 2 November 2010 17:25, Luca Olivetti wrote: > BTW, doesn't the ar8216 driver already modifies the function table of the > attached device? > > >        /* VID fixup only needed on ar8216 */ >        if (pdev->addr == 0 && priv->chip == AR8216) { >                pdev->pkt_align = 2; >          

Re: [OpenWrt-Devel] [PATCH] ag71xx: Fix ar8216 devices and remove the ar8216 workaround.

On 2 November 2010 21:24, Luca Olivetti wrote: > Well, I tried but I failed (unsurprisingly since I know nothing about Linux > network code). > This is a danube based board and this is the patch I tried: > --- trunk/target/linux/ifxmips/files-2.6.33/drivers/net/ifxmips.c.orig > 2010-11-02 17:53:28

Re: [OpenWrt-Devel] [PATCH] ag71xx: Fix ar8216 devices and remove the ar8216 workaround.

On 4 November 2010 19:44, Luca Olivetti wrote: > It turns out that the mac was different than the one set in u-boot. > For some reason the switch doesn't accept a different mac than the initial > one (though in u-boot I can change the mac at will, once it boots linux it > has to be the same mac).

[OpenWrt-Devel] [PATCH] bcm63xx: Finalize support for DSL-274xB, rev C2.

The DSL-2740B/DSL-2741B rev C2 support was missing the board definition, resulting in a kernel panic on boot. This patch adds it, and also renames the generated image name to properly reflect that it is for the revision C2, and for both the DSL-2740B and DSL-2741B. Signed-off-by: Jonas Gorski

Re: [OpenWrt-Devel] [PATCH] triggerhappy: update to 0.1.6

On 22 November 2010 09:41, Matthias Buecher / Germany wrote: > On 22.11.2010 09:35, Stefan Tomanek wrote: > As far as I know your setup shouldn't mangle the patch. > Can someone confirm? The patch looks fine for me ("show original" in GMail shows it with tabs where appropriate).

[OpenWrt-Devel] [PATCH 0/6] bcm63xx: Add support for DSL-274xB and T-Com Speedport W 500V

for devices reusing board ids of other devices. Jonas Gorski (6): bcm63xx: Add defconfigs. bcm63xx: Don't hardcode the switch ethernet interface in preinit. bcm63xx: Allow 'colored' power leds. bcm63xx: Finalize support for DSL-274xB, rev C2. bcm63xx: Add board id override f

[OpenWrt-Devel] [PATCH 1/6] bcm63xx: Add defconfigs.

Port the mechanism for different default configurations from ar71xx and use the old configuration as the default configuration. This should have no functional differences to before. While we are at it, remove the obsolete nat option. Signed-off-by: Jonas Gorski --- v1 -> v2: * Remove the b

[OpenWrt-Devel] [PATCH 2/6] bcm63xx: Don't hardcode the switch ethernet interface in preinit.

Currently eth1 is hardcoded as the expected interface switches in diagmode. This patch replaces the eth1 with the ifname, and also directly tests if the interface specified by ifname has a switch attached. Signed-off-by: Jonas Gorski --- .../lib/preinit/05_failsafe_config_switch_brcm63xx |6

[OpenWrt-Devel] [PATCH 3/6] bcm63xx: Allow 'colored' power leds.

Since some devices have more than one power led, they might be separated by their color in the name. To also allow them to be on after leaving preinit, set any status led starting with 'power' to on instead of only those with the exact name of 'power'. Signed-off-by: Jonas

[OpenWrt-Devel] [PATCH 4/6] bcm63xx: Finalize support for DSL-274xB, rev C2.

The DSL-2740B/DSL-2741B rev C2 support was missing the board definition, resulting in a kernel panic on boot. This patch adds it, and also renames the generated image name to properly reflect that it is for the revision C2, and for both the DSL-2740B and DSL-2741B. Signed-off-by: Jonas Gorski

[OpenWrt-Devel] [PATCH 6/6] bcm63xx: Add support for the T-Com Speedport W 500V.

Add support for the T-Com Speedport W 500V using a special tagged image as it identifies itself as a 96348GW, but has some gpios wired differently, and also has only one ethernet port without a switch attached to it. Signed-off-by: Jonas Gorski --- v2 -> v3: * fixed typo in power led trig

[OpenWrt-Devel] [PATCH 5/6] bcm63xx: Add board id override fixup.

-off-by: Jonas Gorski --- v1 -> v2: * Adapt the code to cshore's imagebuilder changes * Make the fixup only fire if it's a CFE bootloader target/linux/brcm63xx/image/Makefile | 16 - .../patches-2.6.35/410-boardid_fixup.patch | 62

Re: [OpenWrt-Devel] WarpComm TK71 Port

On 9 December 2010 01:12, green wrote: > Hi, > > KanjiMonster asked me as a response to my threat on the OpenWRT forum > (https://forum.openwrt.org/viewtopic.php?pid=122891) to send my patch as a > mail attachment to the dev-list. Good to see it here. I probably should have linked you to

[OpenWrt-Devel] [PATCH] ZNC: Update to 0.096, fix build and minor changes.

verbose for easier adaption. Signed-off-by: Jonas Gorski --- net/znc/Makefile | 13 -- net/znc/files/znc.conf | 10 - net/znc/files/znc.init | 11 +- .../patches/001

Re: [OpenWrt-Devel] [PATCH] miniupnpd config change

Hi, On 14 December 2010 12:35, Bogdan Giuglea wrote: > This changes miniupnpd init so user can enable/disable nat-pmp and upnp > functions via /etc/config/upnpd by adding "option 'natpmp' '1'" and "option > 'upnp' '1'" > upnp function is enabled by default > > Signed-off-by: Bogdan > > --- openw

Re: [OpenWrt-Devel] WRT610n v2 support

On 16 December 2010 18:09, Ryan Bair wrote: > Has anyone attempted to flash the wrt610n v2 from trunk? Can anyone > let me know what the current status of the 4716 (and the wrt610n v2 > specifically) is and what next steps are? Currently there is no support in OpenWrt, but Bernhard Loos posted so

Re: [OpenWrt-Devel] WRT610n v2 support

On 18 December 2010 04:50, Ryan Bair wrote: > It looks like there is source code for this router from linksys, looks > to be binary free too. Has anyone looked at these? At first glance, > they seem to be complete and binary free, although 2.4 based. Yes, but probably some of this is "unpublished

Re: [OpenWrt-Devel] WRT610n v2 support

Okay, the patch(es) can be found at , either as a patch against trunk or as individual patches against the linux-mips git tree. Note that the OpenWrt patch removes two patches that get replaced by these patches. Also I didn't make sure it does

Re: [OpenWrt-Devel] WRT610n v2 support

On 18 December 2010 18:59, Hauke Mehrtens wrote: > In 0008-SSB-Add-support-for-the-PMU-of-newer-Broadcoms.patch you are > checking for 47162 shouldn't it be 0x47162 or did Broadcom some new > strange thing. No, this is correct, the BCM4716's chipid is 0xB83A, which translates to 47162 (0x47162 wo

[OpenWrt-Devel] [PATCH] bcm63xx: Fix build of brcm-wl.

The fallback needs to be exported for bcm63xx, too. Runtime tested with a BCM4322 on a BCM6358. Signed-off-by: Jonas Gorski --- .../977-ssb_export_fallback_sprom.patch| 20 1 files changed, 20 insertions(+), 0 deletions(-) create mode 100644 target/linux

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

The device is called SPW500V, not SP500W. Signed-off-by: Jonas Gorski --- Quite an embarressing typo. .../base-files/etc/defconfig/SP500W/network| 14 -- .../base-files/etc/defconfig/SPW500V/network | 14 ++ 2 files changed, 14 insertions(+), 14

Re: [OpenWrt-Devel] [PATCH 002/002] ASUS RT-N16 kmod-diag and base-files detection/setup support

On 13 February 2011 22:24, Георгий Кашперко wrote: > + * Broadcom SSB GMAC ethernet driver for Linux > ++ * > ++ * Copyright (C) 2011, George Kashperko > ++ * Copyright (C) 2009, Broadcom Corporation > ++ * > ++ * This program is free software; you can redistribute it and/or modify > ++ * it unde

Re: [OpenWrt-Devel] [PATCH 002/002] ASUS RT-N16 kmod-diag and base-files detection/setup support

On 14 February 2011 01:49, George Kashperko wrote: > Hi, >> >> May I ask how you got GPL compatible sources? The last time I looked >> the driver was still closed source/proprietary licensed. >> >> Regards, >> Jonas > > etcgmac.c which was for me the only source of knowledge how the gmac is > work

Re: [OpenWrt-Devel] [PATCH] bcm63xx/MAGIC board support

Hi Laurento, Ah, I was too slow, it's already commited; I do have some comments. Perhaps you could do a follow up patch, assuming you agree with my comments. On 15 February 2011 18:28, Laurento Frittella wrote: > Thanks to KanjiMonster for the support on the IRC channel. You're welcome :) > I

Re: [OpenWrt-Devel] ar8216 doesn't pass data between ports

Hi, On 26 February 2011 20:20, Luca Olivetti wrote: > I'm still trying to make openwrt work on my router (now a lantiq target, > previously ifxmips) and I just noticed that the switch (an ar8216) doesn't > pass data between ports, i.e (warning, lousy ASCII art follows): Do you configure the swit

[OpenWrt-Devel] [PATCH] squashfs4: Add support for LZMA Magic to unsquashfs.

Some vendor firmwares use a different super block magic to indicate LZMA compression. This patches adds support for detecting this and enable extraction for those firmware's root filesystems. Signed-off-by: Jonas Gorski --- I chose to only add this to unsquashfs to make inspecting v

[OpenWrt-Devel] [PATCH] bcm63xx: Really fix the flash driver in 2.6.37

Read back the actual rootfs length from the image tag. Signed-off-by: Jonas Gorski --- (Hopefully) *sigh* third time is the charm. This time thoroughly tested on two different devices. I chose to put these changes into its own patch as it's unreleated to the redboot partition support in

[OpenWrt-Devel] [PATCH] bcm63xx: Move the OpenWrt rootfs length field

reserved1 field. Since the reserved1 field is now completely in use, it does not make sense to allow it to be set from the imagetag utility, so remove the option. Signed-off-by: Jonas Gorski --- .../arch/mips/include/asm/mach-bcm63xx/bcm_tag.h |4 +- .../041-bcm963xx_real_rootfs_length.patch

Re: [OpenWrt-Devel] [PATCH] bcm63xx: Move the OpenWrt rootfs length field

On 2 April 2011 13:08, Florian Fainelli wrote: > Hello, > > Le samedi 02 avril 2011 07:25:32, Daniel Dickinson a écrit : >> Hi, >> >> Did Florian apply this already? > > I did not yet, will do during the weekend. Please wait for a V2. >> If not could I get you to redo the >> command line parsing

Re: [OpenWrt-Devel] [PATCH] 802.1Q VLAN support for Infineon ADM6996 switch chip

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

Re: [OpenWrt-Devel] [PATCH] 802.1Q VLAN support for Infineon ADM6996 switch chip

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

[OpenWrt-Devel] [PATCH V2] bcm63xx: Move the OpenWrt rootfs length field

reserved1 field. Since the reserved1 field is now completely in use, it does not make sense to allow it to be set from the imagetag utility, so remove the option. Signed-off-by: Jonas Gorski --- V1 -> V2: Used gengetopt to regenerate imagetag_cmdline.* .../arch/mips/include/asm/mach-bcm6

[OpenWrt-Devel] [PATCH 2/2] bcm63xx: Add support for the T-Home Speedport W 303V

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

[OpenWrt-Devel] [PATCH 0/2] Add Support for the T-Home Speedport W 303V Typ B

ial flashing of the device. Initial flashing is easy, but subsequent flashing through CFE is a bit harder since this is a "dual image" CFE. The wireless in this device (a BCM4322) only works with the proprietiary broadcom driver, but with it it can be used as an AP. Jonas Gorski (2)

[OpenWrt-Devel] [PATCH 1/2] bcm63xx: Add firmware helpers for T-Home Speedport W 303V

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 |

[OpenWrt-Devel] [PATCH] rtl8366s/rb: Move PHY driver MII bus check into probe

hes ... - rtl8366s_phy_config_init gets called and fails (since wrong MII bus) - eth1 is unsable Moving the MII bus check into the probe fixes this as then the next matching driver gets tried (the correct rtl8366rb phy driver), but this produces a bit of log spam (each failed probe get reported). Signed-off-by: Jo

Re: [OpenWrt-Devel] [PATCH] 802.1Q VLAN support for Infineon ADM6996 switch chip

Hi, On 3 April 2011 15:28, Peter Lebbing wrote: > Yeah, that's the whole problem. If I look at the datasheets I can find about > the F model, it would seem the chip identification will not match at all. In > practice, it turns out people with a chip labeled as FC have a register set > very simila

Re: [OpenWrt-Devel] [PATCH] rtl8366s/rb: Move PHY driver MII bus check into probe

On 4 April 2011 11:23, Jonas Gorski wrote: > Both RTL8366x PHY drivers use the same PHY ID, so both match for either > chip, which results in the following behavior when using a RTL8366RB with > Port 4 as separate WAN port (seen on a WZR-HP-G301NH): > >  - rtl8366rb probes addr

Re: [OpenWrt-Devel] [PATCH] 802.1Q VLAN support for Infineon ADM6996 switch chip

On 5 April 2011 14:00, Jonas Gorski wrote: > I talked with the Lantiq guys, and they said there should be > differences in the default reset values of some registers, so only > indirect hints. Probably you should dump the (default) register values > of the FC and the M and compare the

Re: [OpenWrt-Devel] 802.1Q VLAN support for Infineon ADM6996 switch chip for UBNT RouterStation

On 5 April 2011 08:52, Yeoh Chun Yeow wrote: > Any reason why the first configuration failed? > config 'switch_vlan' >     option 'ports' '0t 1 5t' > > config 'switch_vlan' >     option 'ports' '0t 1 5t' Generally you can't have a port untagged for more than one VLAN, for all others it h

Re: [OpenWrt-Devel] [PATCH] 802.1Q VLAN support for Infineon ADM6996 switch chip

On 7 April 2011 12:04, Peter Lebbing wrote: > Any chance that you can get a datasheet for the FC chip? It would help > implementing FC functionality a lot. I can ask them, but I doubt it. For what they care, I am not much more than a random guy on the internet ;-) Also since I don't have access

Re: [OpenWrt-Devel] 802.1Q VLAN support for Infineon ADM6996 switch chip for UBNT RouterStation

On 6 April 2011 16:18, Yeoh Chun Yeow wrote: > Hi, Jonas, > UBNT RS has two ports connected to eth1, port 0 and port 1. If you connect > your Ethernet cable to port 0 without first connecting Ethernet cable to > port 1, it won't work. You will see a lot of messages "Trying 100/FULL, > Trying 10/HA

Re: [OpenWrt-Devel] [PATCH] rtl8366s/rb: Move PHY driver MII bus check into probe

Okay, disregard this patch. Equate on IRC was kind enough to test for me that at least the WNDR3700 is fine with having no Realtek PHY driver. I'll send a new one removing it. Jonas ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://l

<    1   2   3   4   5   6   7   >