Hello,
I have made some progress narrowing down the issue. It seems the
ath79_eth0_pll_data.pll_1000 is not configured correctly. I do not
understand how to determine what the correct value should be.
Originally the mach-rb95x.c did not have any definition for this
variable. I looked at other
I decided to try and toggle all of the bits by setting
ath79_eth0_pll_data.pll_1000=0x6f00 and it seems to be flowing Ok:
root@OpenWrt:/# arp -n
IP address HW type Flags HW addressMask Device
root@OpenWrt:/# brctl delif br-lan eth0
[ 30.20] device eth0
On 10/12/2014 09:29, David Hutchison wrote:
I am once again just guessing with 0x6f00, so I am sure this is wrong.
I would love to learn if you could give me insight :-)
I would also love to make a patch for both the 951G and the rb2011
(gigabit switch version). I don't have packet
On 10/12/2014 14:44, Chris Green wrote:
On Wed, Dec 10, 2014 at 10:23:12AM +, Chris Green wrote:
On Wed, Dec 10, 2014 at 09:59:29AM +0100, John Crispin wrote:
On 10/12/2014 09:29, David Hutchison wrote:
I am once again just guessing with 0x6f00, so I am sure
this is wrong. I
Hello John,
Thank you for the prompt response. It looks like it works with 29:26 set:
ath79_eth0_pll_data.pll_1000 = 0x3c00;
I think we found a solution :)
Since we are now toggling RX/TX Delays. Should we also change
ath79_setup_ar934x_eth_cfg(AR934X_ETH_CFG_RGMII_GMAC0 |
On 10/12/2014 18:27, David Hutchison wrote:
Hello John,
Thank you for the prompt response. It looks like it works with
29:26 set:
ath79_eth0_pll_data.pll_1000 = 0x3c00;
I think we found a solution :)
looking at the other routerboards bit 25 is always set does 0x3e00
work ?
I confirmed 0x3e00 works, we can toggle bit 25 as well :)
I left in the AR934X_ETH_CFG_RXD_DELAY
However ar71xx_regs.h does not contain AR934X_ETH_CFG_TXD_DELAY
definition. AR934X_ETH_CFG_RXD_DELAY is set to BIT(14). I can add the
AR934X_ETH_CFG_TXD_DELAY definition to the ar71xx_regs.h file
Hi,
felix just pointed out that we could simply read the settings inside the
kernel head after boot and see what the bootloader used.
i'll try to cook a patch tomorrow that you can use to test this.
John
On 10/12/2014 20:06, John Crispin wrote:
On 10/12/2014 20:02, David Hutchison
That sounds like the way to go, if we can grab that information from
boot. I can't wait to see how this is done!
-- Davey
On Wed, Dec 10, 2014 at 1:06 PM, John Crispin blo...@openwrt.org wrote:
Hi,
felix just pointed out that we could simply read the settings inside the
kernel head after
Hello,
I did some more poking around. I don't know if I am way off course or
not, but I hope these findings trigger some ideas.
Firstly, I contacted Mikrotik and actually received a response:
Hello,
that patch will not help you much. However, you can try to debug your FW on
RB2011 as it uses
On Fri, Dec 05, 2014 at 11:18:10PM -0500, Soren Harward wrote:
On Fri, Dec 5, 2014 at 5:21 AM, Chris Green c...@isbd.net wrote:
Some people with the RB2011 (other incarnations but presumably
basically the same) have it working OK.
I'm one of those that has a working RB2011; it's currently
On Dec 6, 2014 5:15 AM, Chris Green c...@isbd.net wrote:
To indicate that the problem is definitely something to do with eth0
not being 'hooked up' properly see the following:-
root@OpenWrt:~# swconfig dev eth0 show
Failed to connect to the switch. Use the list command to see which
On Sat, Dec 06, 2014 at 08:58:05AM -0500, Soren Harward wrote:
On Dec 6, 2014 5:15 AM, Chris Green [1]c...@isbd.net wrote:
To indicate that the problem is definitely something to do with eth0
not being 'hooked up' properly see the following:-
root@OpenWrt:~#
This sounds very like the bug #18401 I have raised for my
RB2011UiAS-2HnD-IN.
I have exactly the same problem of everything appearing to be detected
OK and interfaces OK but eth0 simply doesn't do anything.
I can try patches etc. if/when necessary.
On Thu, Dec 04, 2014 at 10:13:52PM -0700,
its your lucky day, according to the DHL website my RB2011UiAS-2HnD-IN
will arrive in the next 2-3 hours :)
On 05/12/2014 10:21, Chris Green wrote:
This sounds very like the bug #18401 I have raised for my
RB2011UiAS-2HnD-IN.
I have exactly the same problem of everything appearing to be
On Fri, Dec 5, 2014 at 10:21 AM, Chris Green c...@isbd.net wrote:
This sounds very like the bug #18401 I have raised for my
RB2011UiAS-2HnD-IN.
I have exactly the same problem of everything appearing to be detected
OK and interfaces OK but eth0 simply doesn't do anything.
Ticket 18401 relates
On Fri, Dec 05, 2014 at 10:59:11AM +0100, Heiner Kallweit wrote:
On Fri, Dec 5, 2014 at 10:21 AM, Chris Green c...@isbd.net wrote:
This sounds very like the bug #18401 I have raised for my
RB2011UiAS-2HnD-IN.
I have exactly the same problem of everything appearing to be detected
OK and
Hello,
Yes the problem remains when enable_vlan is set to 0
I don't think it's related to your changes either. I synced with trunk
in hope that your changes made a difference with my problem. However
that does not seem to be the case.
I was hoping someone could point me in the right direction.
I meant to say Could it be as simple as the switch just isn't fully
initialized? instead of *recognized*... the ar8216 driver definitely
recognizes it properly, and exposes the switch0 interface. I was
thinking perhaps something else had to happen during init for the
eth0 interface.
-- Davey
On
On 2014-12-05 17:15, David Hutchison wrote:
Hello,
Yes the problem remains when enable_vlan is set to 0
I don't think it's related to your changes either. I synced with trunk
in hope that your changes made a difference with my problem. However
that does not seem to be the case.
I was
On Fri, Dec 05, 2014 at 05:37:31PM +0100, Felix Fietkau wrote:
On 2014-12-05 17:15, David Hutchison wrote:
The other thing to note ( and i'm not sure if this is by design ).. I
used to be able to do swconfig dev eth0 show and show the switch the
eth0 was connected to. Now I must use
I am using a very simple test setup with no vlans for now:
root@OpenWrt:/# cat /etc/config/network
config interface 'loopback'
option ifname 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
config globals 'globals'
option
Here is a test I did by setting up swconfig manually. As you can see I
put ports 1 and 2 into vlangroup 1. Traffic from port 2 can ping
10.128.41.1 which is a device on port 1. However eth0.1 which as
address 10.128.41.249 cannot ping 10.128.41.1 device on port 1.
Attached is the swconfig setup,
On Fri, Dec 05, 2014 at 12:39:16PM -0700, David Hutchison wrote:
Here is a test I did by setting up swconfig manually. As you can see I
put ports 1 and 2 into vlangroup 1. Traffic from port 2 can ping
10.128.41.1 which is a device on port 1. However eth0.1 which as
address 10.128.41.249 cannot
On Fri, Dec 5, 2014 at 5:21 AM, Chris Green c...@isbd.net wrote:
Some people with the RB2011 (other incarnations but presumably
basically the same) have it working OK.
I'm one of those that has a working RB2011; it's currently running
r41293 with my RB2011UiAS patch (
Hi,
I ran into an issue with the Mikrotik Routerboard 951G's switch chip.
The new batch that we received use an updated ar8327 switch chip. The
switch chip would not function properly so I decided to load trunk and
utilize your patches.
dmesg shows the following:
switch0: Atheros AR8327 rev. 4
Am 05.12.2014 um 06:13 schrieb David Hutchison:
Hi,
I ran into an issue with the Mikrotik Routerboard 951G's switch chip.
The new batch that we received use an updated ar8327 switch chip. The
switch chip would not function properly so I decided to load trunk and
utilize your patches.
27 matches
Mail list logo
