Re: [OpenWrt-Devel] PCI broken on au1000
Hi Bruno, On Monday 05 April 2010 03:23:49 Bruno Randolf wrote: > hi! > > currently PCI is broken on the au1000 platforms. > > this is also the reason for: > https://dev.openwrt.org/ticket/6851 > > in order to debug this further, does anyone know when the au1000 was > working last? which kernel version? has anyone tried openwrt on au1000 > recently? OpenWrt works fine for me on MTX-1 under 2.6.32. I know Manuel Lauss did get lots of changes mainstream in-between. Will try tonight when I am back home. -- Florian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH v2 0/2] Add support for ar8316.
Hi, *sigh* shortly after it got committed to trunk, I think I see how I broke ar8216 on ar71xx (actually it was already "broken" before): The header mode gets handled by the ar8216 driver itself, in theory, but the ar8216_netif_rx never gets called by the ag71xx driver. This leads to following situations: Header mode is disabled (= no VLANs): rx: ag71xx tries to remove header, fails => no rx tx: ag71xx adds header => packet gets dropped by switch Header mode is enabled: rx: ag71xx tries to remove header, succeeds => ok tx: ar8216 driver adds header, ag71xx adds header => 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.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] ag71xx: Fix ar8216 devices and remove the ar8216 workaround.
The inclusion of the ar8216 driver in ar71xx most probably broke
networking for those devices.
The ag71xx driver currently unconditionally adds/removes the header
on ar8216 devices independent whether the header is enabled or not.
The ar8216 driver can handle that itself, but needs support by 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
---
target/linux/ar71xx/config-2.6.32 |2 +-
target/linux/ar71xx/config-2.6.33 |2 +-
target/linux/ar71xx/config-2.6.34 |2 +-
.../linux/ar71xx/files/drivers/net/ag71xx/Kconfig |8
.../linux/ar71xx/files/drivers/net/ag71xx/Makefile |1 -
.../linux/ar71xx/files/drivers/net/ag71xx/ag71xx.h | 21 -
.../files/drivers/net/ag71xx/ag71xx_ar8216.c | 45
.../ar71xx/files/drivers/net/ag71xx/ag71xx_main.c | 20 -
8 files changed, 12 insertions(+), 89 deletions(-)
delete mode 100644 target/linux/ar71xx/files/drivers/net/ag71xx/ag71xx_ar8216.c
diff --git a/target/linux/ar71xx/config-2.6.32
b/target/linux/ar71xx/config-2.6.32
index 417d718..347e603 100644
--- a/target/linux/ar71xx/config-2.6.32
+++ b/target/linux/ar71xx/config-2.6.32
@@ -1,7 +1,7 @@
CONFIG_32BIT=y
# CONFIG_64BIT is not set
CONFIG_AG71XX=y
-CONFIG_AG71XX_AR8216_SUPPORT=y
+# CONFIG_AG71XX_AR8216_SUPPORT is not set
# CONFIG_AG71XX_DEBUG is not set
# CONFIG_AG71XX_DEBUG_FS is not set
# CONFIG_ALCHEMY_GPIO_INDIRECT is not set
diff --git a/target/linux/ar71xx/config-2.6.33
b/target/linux/ar71xx/config-2.6.33
index e147b01..d8567ef 100644
--- a/target/linux/ar71xx/config-2.6.33
+++ b/target/linux/ar71xx/config-2.6.33
@@ -1,7 +1,7 @@
CONFIG_32BIT=y
# CONFIG_64BIT is not set
CONFIG_AG71XX=y
-CONFIG_AG71XX_AR8216_SUPPORT=y
+# CONFIG_AG71XX_AR8216_SUPPORT is not set
# CONFIG_AG71XX_DEBUG is not set
# CONFIG_AG71XX_DEBUG_FS is not set
# CONFIG_ALCHEMY_GPIO_INDIRECT is not set
diff --git a/target/linux/ar71xx/config-2.6.34
b/target/linux/ar71xx/config-2.6.34
index 549b7a8..8cdbb87 100644
--- a/target/linux/ar71xx/config-2.6.34
+++ b/target/linux/ar71xx/config-2.6.34
@@ -1,7 +1,7 @@
CONFIG_32BIT=y
# CONFIG_64BIT is not set
CONFIG_AG71XX=y
-CONFIG_AG71XX_AR8216_SUPPORT=y
+# CONFIG_AG71XX_AR8216_SUPPORT is not set
# CONFIG_AG71XX_DEBUG is not set
# CONFIG_ALCHEMY_GPIO_INDIRECT is not set
# CONFIG_AR7 is not set
diff --git a/target/linux/ar71xx/files/drivers/net/ag71xx/Kconfig
b/target/linux/ar71xx/files/drivers/net/ag71xx/Kconfig
index 7db779e..fff31c0 100644
--- a/target/linux/ar71xx/files/drivers/net/ag71xx/Kconfig
+++ b/target/linux/ar71xx/files/drivers/net/ag71xx/Kconfig
@@ -22,12 +22,4 @@ config AG71XX_DEBUG_FS
Say Y, if you need access to various statistics provided by
the ag71xx driver.
-config AG71XX_AR8216_SUPPORT
- bool "special support for the Atheros AR8216 switch"
- default n
- default y if AR71XX_MACH_WNR2000 || AR71XX_MACH_MZK_W04NU
- help
- Say 'y' here if you want to enable special support for the
- Atheros AR8216 switch found on some boards.
-
endif
diff --git a/target/linux/ar71xx/files/drivers/net/ag71xx/Makefile
b/target/linux/ar71xx/files/drivers/net/ag71xx/Makefile
index 3485ab3..4c83696 100644
--- a/target/linux/ar71xx/files/drivers/net/ag71xx/Makefile
+++ b/target/linux/ar71xx/files/drivers/net/ag71xx/Makefile
@@ -8,7 +8,6 @@ ag71xx-y+= ag71xx_phy.o
ag71xx-y += ag71xx_mdio.o
ag71xx-$(CONFIG_AG71XX_DEBUG_FS) += ag71xx_debugfs.o
-ag71xx-$(CONFIG_AG71XX_AR8216_SUPPORT) += ag71xx_ar8216.o
obj-$(CONFIG_AG71XX) += ag71xx.o
diff --git a/target/linux/ar71xx/files/drivers/net/ag71xx/ag71xx.h
b/target/linux/ar71xx/files/drivers/net/ag71xx/ag71xx.h
index a64b4a8..03653df 100644
--- a/target/linux/ar71xx/files/drivers/net/ag71xx/ag71xx.h
+++ b/target/linux/ar71xx/files/drivers/net/ag71xx/ag71xx.h
@@ -453,31 +453,10 @@ static void inline ag71xx_mii_ctrl_set_speed(struct
ag71xx *ag,
ag71xx_mii_ctrl_wr(ag, t);
}
-#ifdef CONFIG_AG71XX_AR8216_SUPPORT
-void ag71xx_add_ar8216_header(struct ag71xx *ag, struct sk_buff *skb);
-int ag71xx_remove_ar8216_header(struct ag71xx *ag, struct sk_buff *skb,
- int pktlen);
static inline int ag71xx_has_ar8216(struct ag71xx *ag)
{
return ag71xx_get_pdata(ag)->has_ar8216;
}
-#else
-static inline void ag71xx_add_ar8216_header(struct ag71xx *ag,
- struct sk_buff *skb)
-{
-}
-
-static inline int ag71xx_remove_ar8216_header(struct ag71xx *ag,
- struct sk_buff *skb,
- int pktlen)
-{
- return 0;
-}
-static inline int ag71xx_has_ar8216(struct
Re: [OpenWrt-Devel] [PATCH v2 0/2] Add support for ar8316.
Jonas Gorski írta: > Hi, > > *sigh* shortly after it got committed to trunk, I think I see how I > broke ar8216 on ar71xx (actually it was already "broken" before): Nah, it was not "broken". The AR8216 driver was disabled by default because it is not usable on the AR913x based boards. The reason behind this is that you can't communicate with the switch via the MDIO bus, because its speed is too fast for the switch. The speed of the MDIO bus depends on the speed of the AHB bus. In theory it would be possible to decrease the speed of the AHB bus in the board init code, but that would affect the performance of the whole system. Another solution is to decrease the speed of the AHB bus before each MDIO bus access, and restore it after, but i don't know how it would affect other devices on the AHB bus. To be precise, there is yet another solution: configuring the AR8216 switch with special ethernet packets. > The header mode gets handled by the ar8216 driver itself, in theory, > but the ar8216_netif_rx never gets called by the ag71xx driver. This > leads to following situations: > > Header mode is disabled (= no VLANs): > rx: ag71xx tries to remove header, fails => no rx > tx: ag71xx adds header => packet gets dropped by switch > > Header mode is enabled: > rx: ag71xx tries to remove header, succeeds => ok > tx: ar8216 driver adds header, ag71xx adds header => 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. The automatic detection won't work with this switch due to the MDIO bus issue, so it won't be registered never. At the end, you can't use the netif_rx function of the phy device. Regards, Gabor ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [OpenWrt] #6852: PPTP wrong gateway detection
On Tue, 2010-04-06 at 01:49 +, OpenWrt wrote: > #6852: PPTP wrong gateway detection > --+- > Reporter: abr...@… | Owner: cshore > Type: defect| Status: accepted > Priority: normal| Milestone: Kamikaze > Component: packages | Version: Trunk > Keywords: pptp | > --+- > > Comment(by abr...@…): > > So is there any other way to determine the route instead of 'ip route > get'? > Traceroute maybe (but it will fail if the first hop drops icmp)? > if /sbin/route doesn't have the info, then I'm not aware of anything. -- And that's my crabbing done for the day. Got it out of the way early, now I have the rest of the afternoon to sniff fragrant tea-roses or strangle cute bunnies or something. -- Michael Devore GnuPG Key Fingerprint 86 F5 81 A5 D4 2E 1F 1C http://gnupg.org The C Shore (Daniel Dickinson's Website) http://cshore.is-a-geek.com signature.asc Description: This is a digitally signed message part ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Massive problems accessing DLINK DIR-300 and OpenWrt Backfire rc3
Hi, I´m having massive problems accessing my DLINK DIR-300 after flashing with the new OpenWrt Backfire 10.03 RC3. If I use my normal tool to flash the device, I can´t ping the device and can´t access it over telnet/ssh/webinterface. I tried accessing on wan and lan ports on the IP 192.168.1.1 and I am in the same subnet. I used this tool http://x-alina.freifunk-potsdam.de/downloads/dir300-flash/ to flash and there was nothing abnormal during the flashprocess. I tried it several times. Flashing and accessing OpenWrt 8.09.02 works fine so I flashed OpenWrt 8.09.02 on the device. Then I reebooted and connected again over ssh and the ip I got with dhcp and flashed an openwrt backfire rc3 combined squashfs with sysupgrade. Then I connected the device over the wan port an could ping it. Nmap shows it as well. But I can´t acces the webiterface, ssh or telnet because I get an connection refused. I did the same procedure with sysupgrade -n (to not save my config files) and I got complete failure again. I have no serial cable here to look what´s going on in the device so I can´t provide you with more data. Please make OpenWrt Backfire usabale on DIR-300 again because it is heavily used in several freifunk networks. Thanks Clemens signature.asc Description: This is a digitally signed message part. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Massive problems accessing DLINK DIR-300 and OpenWrt Backfire rc3
Can you access Redboot? On Wed, Apr 7, 2010 at 5:29 AM, Clemens John wrote: > Hi, > > I´m having massive problems accessing my DLINK DIR-300 after flashing with > the > new OpenWrt Backfire 10.03 RC3. > > If I use my normal tool to flash the device, I can´t ping the device and > can´t > access it over telnet/ssh/webinterface. > I tried accessing on wan and lan ports on the IP 192.168.1.1 and I am in > the > same subnet. > I used this tool > http://x-alina.freifunk-potsdam.de/downloads/dir300-flash/ to > flash and there was nothing abnormal during the flashprocess. I tried it > several > times. > Flashing and accessing OpenWrt 8.09.02 works fine so I flashed OpenWrt > 8.09.02 > on the device. > > Then I reebooted and connected again over ssh and the ip I got with dhcp > and > flashed an openwrt backfire rc3 combined squashfs with sysupgrade. > Then I connected the device over the wan port an could ping it. Nmap shows > it > as well. But I can´t acces the webiterface, ssh or telnet because I get an > connection refused. > > I did the same procedure with sysupgrade -n (to not save my config files) > and I > got complete failure again. > > I have no serial cable here to look what´s going on in the device so I > can´t > provide you with more data. > > Please make OpenWrt Backfire usabale on DIR-300 again because it is heavily > used in several freifunk networks. > > Thanks > Clemens > > ___ > 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] Massive problems accessing DLINK DIR-300 and OpenWrt Backfire rc3
On Tuesday 06 April 2010 23:31:17 jason duhamell wrote: > Can you access Redboot? Yes I think I can but I´m not getting behind this: [r...@myhost floh]# ./redboot.sh Setting up network Network setup Waiting for Redboot to boot. Press CTRL + C to quit Router Awake Trying 192.168.20.81... Connected to 192.168.20.81. Escape character is '^]'. == Executing boot script in 4.060 seconds - enter ^C to abort ^C ^C ^C ^C ^C Bye Clemens signature.asc Description: This is a digitally signed message part. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Massive problems accessing DLINK DIR-300 and OpenWrt Backfire rc3
On Tuesday 06 April 2010 23:31:17 jason duhamell wrote: > Can you access Redboot? I managed to enter Redboot now. I put this in my .telnetrc: "192.168.20.81 mode line" [r...@myhost ~]# ./redboot.sh Setting up network Network setup Waiting for Redboot to boot. Press CTRL + C to quit Router Awake Trying 192.168.20.81... Connected to 192.168.20.81. Escape character is '^]'. == Executing boot script in 4.990 seconds - enter ^C to abort ^C^C DD-WRT> Bye Clemens signature.asc Description: This is a digitally signed message part. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Massive problems accessing DLINK DIR-300 and OpenWrt Backfire rc3
Can you tell me which redboot version you are using? On Wed, Apr 7, 2010 at 6:24 AM, Clemens John wrote: > On Tuesday 06 April 2010 23:31:17 jason duhamell wrote: > > Can you access Redboot? > > I managed to enter Redboot now. > I put this in my .telnetrc: > "192.168.20.81 mode line" > > [r...@myhost ~]# ./redboot.sh > Setting up network > Network setup > Waiting for Redboot to boot. Press CTRL + C to quit > Router Awake > Trying 192.168.20.81... > Connected to 192.168.20.81. > Escape character is '^]'. > == Executing boot script in 4.990 seconds - enter ^C to abort > ^C^C > DD-WRT> > > Bye > Clemens > > ___ > 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] Massive problems accessing DLINK DIR-300 and OpenWrt Backfire rc3
Hi Clemens, the problem seems to be related to the Linux telnet client. The problem doesn't occur with putty. > == Executing boot script in 4.060 seconds - enter ^C to abort > ^C > ^C > ^C > ^C > ^C Cheers, Elektra ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Massive problems accessing DLINK DIR-300 and OpenWrt Backfire rc3
I just have experience with redboot. I havent had a chance to use the new backfire one yet as I only use gargoyle. I just wanted to help you get to a redboot prompt so you can recover it. On Wed, Apr 7, 2010 at 6:26 AM, elektra wrote: > Hi Clemens, > > the problem seems to be related to the Linux telnet client. The problem > doesn't occur with putty. > > > == Executing boot script in 4.060 seconds - enter ^C to abort > > ^C > > ^C > > ^C > > ^C > > ^C > > Cheers, > Elektra > ___ > 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] Massive problems accessing DLINK DIR-300 and OpenWrt Backfire rc3
On Wednesday 07 April 2010 00:25:50 jason duhamell wrote: > Can you tell me which redboot version you are using? DD-WRT> version RedBoot(tm) bootstrap and debug environment [ROMRAM] production release, version "2.1.3" - built 18:43:19, Sep 20 2007 Platform: ap61 (Atheros WiSOC) Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc. Copyright (C) 2007, NewMedia-NET GmbH. Board: DLINK DIR-300 RAM: 0x8000-0x8100, [0x80040580-0x80fe1000] available FLASH: 0xbfc0 - 0xbfff, 64 blocks of 0x0001 bytes each. Bye Clemens signature.asc Description: This is a digitally signed message part. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Massive problems accessing DLINK DIR-300 and OpenWrt Backfire rc3
Do you have a ttl to serial adapter to record the start up log on putty so I can see where it chokes at? On Wed, Apr 7, 2010 at 6:37 AM, Clemens John wrote: > On Wednesday 07 April 2010 00:25:50 jason duhamell wrote: > > Can you tell me which redboot version you are using? > > DD-WRT> version > > RedBoot(tm) bootstrap and debug environment [ROMRAM] > production release, version "2.1.3" - built 18:43:19, Sep 20 2007 > > Platform: ap61 (Atheros WiSOC) > Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc. > Copyright (C) 2007, NewMedia-NET GmbH. > > Board: DLINK DIR-300 > RAM: 0x8000-0x8100, [0x80040580-0x80fe1000] available > FLASH: 0xbfc0 - 0xbfff, 64 blocks of 0x0001 bytes each. > > Bye > Clemens > > ___ > 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] Massive problems accessing DLINK DIR-300 and OpenWrt Backfire rc3
If you hold reset while booting for about 10 seconds, it should stop it from booting and go directly to redboot. On Wed, Apr 7, 2010 at 6:20 AM, Clemens John wrote: > On Tuesday 06 April 2010 23:31:17 jason duhamell wrote: > > Can you access Redboot? > > Yes I think I can but I´m not getting behind this: > > [r...@myhost floh]# ./redboot.sh > Setting up network > Network setup > Waiting for Redboot to boot. Press CTRL + C to quit > Router Awake > Trying 192.168.20.81... > Connected to 192.168.20.81. > Escape character is '^]'. > == Executing boot script in 4.060 seconds - enter ^C to abort > ^C > ^C > ^C > ^C > ^C > > Bye > Clemens > > ___ > 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] Massive problems accessing DLINK DIR-300 and OpenWrt Backfire rc3
On Wednesday 07 April 2010 00:41:52 jason duhamell wrote: > Do you have a ttl to serial adapter to record the start up log on putty so > I can see where it chokes at? No I´m sorry I don´t have one. Bye Clemens signature.asc Description: This is a digitally signed message part. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Massive problems accessing DLINK DIR-300 and OpenWrt Backfire rc3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Should be fixed by https://dev.openwrt.org/changeset/20733 ~ J. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEUEARECAAYFAku7ulcACgkQdputYINPTPOQlgCXQ2w/oV8mzYs5XLK9v3s+5xo2 PwCfQah+vsQe+l5i9dxsWD6KvUxP3R0= =Mygt -END PGP SIGNATURE- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Massive problems accessing DLINK DIR-300 and OpenWrt Backfire rc3
I have about 2000 of them, I can send you one for a few dollars if you want. I am also building a few ar2317 based router solutions. I also have an original dir-300 and a clone dir-300. It turns out that the only way you can use the ar2317 with linux is by using the tools built for the dir-300. Give me an hour and I will make a log. On Wed, Apr 7, 2010 at 6:46 AM, Clemens John wrote: > On Wednesday 07 April 2010 00:41:52 jason duhamell wrote: > > Do you have a ttl to serial adapter to record the start up log on putty > so > > I can see where it chokes at? > > No I´m sorry I don´t have one. > > Bye > Clemens > > ___ > 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] Massive problems accessing DLINK DIR-300 and OpenWrt Backfire rc3
On Wednesday 07 April 2010 00:48:55 Jo-Philipp Wich wrote: > Should be fixed by https://dev.openwrt.org/changeset/20733 I saw it just the same time you checked this in. I´ll build a new Image now and report to you if it works *happy* Bye Clemens signature.asc Description: This is a digitally signed message part. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Support for AR8216
Hi, On 04/06/2010 04:30 PM, Gabor Juhos wrote: > Nah, it was not "broken". The AR8216 driver was disabled by default because it > is not usable on the AR913x based boards. The reason behind this is that you > can't communicate with the switch via the MDIO bus, because its speed is too > fast for the switch. Interesting. Does this imply that OpenWRT currently doesn't control the AR8216, i.e. the configuration from reset or bootloader is kept? Running OpenWRT svn r20534 on a Netgear WNR2000 says: Atheros AR9130 rev 1, CPU:400.000 MHz, AHB:200.000 MHz, DDR:400.000 MHz In the bootloader I can see the PHY @ addr 0...4 (AFAIK integrated into the AR8216): ar7100> mii info PHY_PHYIDR2 @ 0x0 = 0xd042 PHY_PHYIDR[1,2] @ 0x0 = 0x004dd042 PHY 0x00: OUI = 0x1374, Model = 0x04, Rev = 0x02, 10baseT, HDX PHY_PHYIDR2 @ 0x1 = 0xd042 PHY_PHYIDR[1,2] @ 0x1 = 0x004dd042 PHY 0x01: OUI = 0x1374, Model = 0x04, Rev = 0x02, 10baseT, HDX PHY_PHYIDR2 @ 0x2 = 0xd042 PHY_PHYIDR[1,2] @ 0x2 = 0x004dd042 PHY 0x02: OUI = 0x1374, Model = 0x04, Rev = 0x02, 10baseT, HDX PHY_PHYIDR2 @ 0x3 = 0xd042 PHY_PHYIDR[1,2] @ 0x3 = 0x004dd042 PHY 0x03: OUI = 0x1374, Model = 0x04, Rev = 0x02, 100baseT, FDX PHY_PHYIDR2 @ 0x4 = 0xd042 PHY_PHYIDR[1,2] @ 0x4 = 0x004dd042 PHY 0x04: OUI = 0x1374, Model = 0x04, Rev = 0x02, 10baseT, HDX Is it just the switch core not able to cope with the high frequency on the MDIO bus or does the bootloader run the AHB at a lower speed? I guess the register AG71XX_REG_MII_CFG (drivers/net/ag71xx/ag71xx.h) contains the divider for AHB clock => MDIO clock, set in ag71xx_mdio.c::ag71xx_mdio_reset(). Is 28 (coded as 7) the highest possible divider, i.e. only three bit for DIV? > The speed of the MDIO bus depends on the speed of the AHB bus. > > In theory it would be possible to decrease the speed of the AHB bus in the > board > init code, but that would affect the performance of the whole system. > > Another solution is to decrease the speed of the AHB bus before each MDIO bus > access, and restore it after, but i don't know how it would affect other > devices > on the AHB bus. What is the highest MDIO and AHB frequency the AR8216 can work at? > To be precise, there is yet another solution: configuring the AR8216 switch > with > special ethernet packets. Is there any example source code for this (I guess headers != 0x10 80 are needed)? Does the same apply to the AR7240, whose built-in switch seems to be derived from the AR8216? ag71xx_mdio.c::ag71xx_mdio_reset() sets the divider to 6 for the AR7240. Regards, Jörg. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] PCI broken on au1000
On Tuesday 06 April 2010 17:42:12 Florian Fainelli wrote: > Hi Bruno, > > On Monday 05 April 2010 03:23:49 Bruno Randolf wrote: > > hi! > > > > currently PCI is broken on the au1000 platforms. > > > > this is also the reason for: > > https://dev.openwrt.org/ticket/6851 > > > > in order to debug this further, does anyone know when the au1000 was > > > > working last? which kernel version? has anyone tried openwrt on au1000 > > recently? > > OpenWrt works fine for me on MTX-1 under 2.6.32. I know Manuel Lauss did > get lots of changes mainstream in-between. Will try tonight when I am back > home. -- well, that's good to hear :) so it can't be too serious. anyhow there must be a reason for https://dev.openwrt.org/ticket/6851... i'm curious to hear about your results with current openwrt trunk or backfire. bruno ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
