Modify

Opened 12 years ago

Closed 6 years ago

#99 closed enhancement (fixed)

Add switch drivers to AR7 kernel.

Reported by: noodles-wrt@… Owned by: florian
Priority: normal Milestone: Features Paradise
Component: kernel Version:
Keywords: Cc:

Description

The dg834_g_v1_05_00_src_tar.bz2 tarball from Netgear contains a patch-knl file; this references CONFIG_MIPS_AR7_MARVELL which appears to surround various bits of support for the Marvell switch used on at least the DG834G.

I'll try to take a look at this myself if I get time (turning one of the LAN ports into a WAN port would be really useful to me), but perhaps someone else out there has already done this or knows how to easily.

Attachments (0)

Change History (21)

comment:1 Changed 12 years ago by nbd

  • Milestone set to 2.0
  • Owner changed from developers to nbd
  • Version set to 2.0

comment:2 Changed 11 years ago by nbd

  • Milestone changed from Kamikaze to Afterburner 7.09

comment:3 follow-up: Changed 10 years ago by KillaB

This ticket is so old, are we sure we can't just close it?

See comments: https://dev.openwrt.org/ticket/1614#comment:3

comment:4 in reply to: ↑ 3 Changed 10 years ago by Wipster

Replying to KillaB:

This ticket is so old, are we sure we can't just close it?

See comments: https://dev.openwrt.org/ticket/1614#comment:3

It is old but still would be very usefull for me aswell, so I can access the VLAN functions of the Marvell switch.

comment:6 Changed 9 years ago by anonymous

Did any one tested this patch??

comment:7 Changed 9 years ago by anonymous

I'm eager to access VLAN on marvell.

Can you let me know how can configure and test vlan on my device
[Fonera + kamikaze7.09 + Marvell]

comment:8 Changed 9 years ago by agb

  • Milestone changed from Kamikaze 8.09 to Kamikaze Features Paradize

comment:9 Changed 9 years ago by nico

  • Version 2.0 deleted

comment:10 Changed 9 years ago by florian

  • Owner changed from nbd to florian

comment:11 Changed 8 years ago by KillaB

ar71xx appears to have support for the 88E6060 switch:
https://dev.openwrt.org/browser/trunk/target/linux/ar71xx/patches-2.6.32/121-dsa-add-88e6063-driver.patch

The driver has been available since 2.6.27, so would it be as simple as adding the following to .config to get it to compile, or is there more to it than that?

CONFIG_NET_DSA=y
CONFIG_NET_DSA_MV88E6060=y

comment:12 Changed 8 years ago by florian

It is a bit more complicated, one must call phy_connect on the right phy device, let me cook a patch for you to test.

comment:13 Changed 8 years ago by florian

Errm, for DSA, it it slightly different actually

comment:14 follow-up: Changed 7 years ago by florian

  • Resolution set to fixed
  • Status changed from new to closed

Fixed with r22727.

comment:15 in reply to: ↑ 14 Changed 7 years ago by anonymous

Replying to florian:

Fixed with r22727.

On a DG834Gv3 (AR7 w/ mv88e6060 switch), as of OpenWRT 10.3.1rc3 and newer, it appears that changes have created an undesirable effect.

The 'out of the box' behavior at boot, is now to have only one of the 4 external ethernet ports functional from boot (10.3.1rc2 and earlier, used to work).
There is no mention of the switch in the kernel logs, only the 'cpmac' driver for eth0.
There is no /proc/switch and 'swconfig' appears not to work.
Trying to activate eth0.0 or eth1 does not work...

Any ideas?

comment:16 Changed 7 years ago by Simon Iremonger <wiltslug@…>

  • Resolution fixed deleted
  • Status changed from closed to reopened

Thinking about it (see above post), would it be worth my while learning to rebuild OpenWRT and recompile the kernel with the new switch drivers disabled?
Does anybody else have any success with the latest OpenWRT and AR7 Switch support?

--Simon

comment:17 Changed 7 years ago by vbelo

It seems to be the same problem I had here : /ticket/8525.html
Try removing patches 970 to 972 and it will work like in RC2. I didn't understand the goal of those patch, it only breaks compatibility for me. Maybe should we remove them ?

comment:18 Changed 7 years ago by KillaB

Here's my ticket on the issue: #7836

vbelo, I see you created a set of patches (#8524). Perhaps you could apply for svn access? florian seems to be the only one working on ar7 these days.

comment:19 Changed 7 years ago by vbelo

I would be nice if someone put those patch in trunk (I tested them and I'm currently using an 2.6.36.2 kernel based build on my device) but I don't have the time to develop for OpenWrt...
Anyway it won't solve the issue, deleting patches 970 - 971 - 972 is just a workaround (it's a clean way since those patches are useless for Marvell based routers).

Another thing : WPA2 in Access Point / Client mode is working for ACX111 when you compile it from git. It's now enough stable. My router's wireless is up for a week without failure.

comment:20 Changed 7 years ago by Simon Iremonger

vbelo,
Please let me/us know what you mean by compiling ACX111 from git.

I'm ok with downloading an Openwrt version from subversion and building it. Are you saying you did something along the lines of getting a version of OpenWrt source and using a git repository of acx100 on sourceforge? or rebuilding acx111 afterwards? or what?

Note: OpenWRT r25755 changes to use "kmod-acx-mac80211" and they are now using 2.6.37 kernel.
Basically, I would like to (try) to build a good openwrt version for ar7 that will (hopefully) contain a good acx111 wireless driver ;-). I don't know if I should now use 'trunk' or something else that relates to upcoming 10.3.1 release (after 10.3.1-rc4)... (is this a separate branch?) ?? Would you still recommend replacing the acx111 part from git somewhere? etc.

Thankyou in advance,

--Simon

comment:21 Changed 6 years ago by florian

  • Resolution set to fixed
  • Status changed from reopened to closed

Support for all kind of switches (Marvell, ADM, IC+) is now in trunk. There are separate issues tracked down in separate tickets.

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.