1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Port speed control on WRT54Gv2.2 (or specs for BCM5325E)

Discussion in 'General Discussion' started by Anonymous, May 22, 2005.

  1. Anonymous

    Anonymous Guest

    Does anybody knows, if the Broadcom switch BCM5325E, that is in newer models WRT54G v>2.2, able to force its ports into 10BaseT/HalfDuplex mode?

    I was unable to find any specs for this chip, and the kernel code for it do not contain anything of this type.
     
  2. Guyfromhe

    Guyfromhe Network Guru Member

    i'm pretty sure you can... have you tried the admcfg utiliy on it?
     
  3. firmwaredownload

    firmwaredownload Network Guru Registered

    The admcfg utility won't work. But you can check out OpenWrt. We have a small utility called 'robocfg' that works with the newer Broadcom chips (written by Oleg).
     
  4. __nbd

    __nbd Network Guru Member

    Oops... posted the last message from the account that BugMeNot gave me (firmwaredownload) instead of my real account (__nbd)...
     
  5. Anonymous

    Anonymous Guest

    Thanks, but robocfg does not help

    It does not change the required thing -- the port autonegotiation status or speed.
     
  6. __nbd

    __nbd Network Guru Member

    Hmm, ok. Looks like we need the specs after all... Unfortunately specs for Broadcom chips are hard to get. If you find them anywhere, please let me know. I'd like to put this in robocfg then...
     
  7. __nbd

    __nbd Network Guru Member

    OK. I actually looked at the stuff in the robocfg package dir now. I think the header file in there ("etc53xx.h") should give you enough information to implement this. At least the command definitions (including those for setting the speed) are there, maybe you need to figure out the actual values for the speed settings by trial-and-error, but it still shouldn't be that hard.
     
  8. Anonymous

    Anonymous Guest

    Working!

    Playing with etc53xx.h did not help much.

    But another approach did help -- adding normal SOICSMIIREG and similar ioctls and using mii-tool with phy=0,1,2,3,4.

    At the moment I am thinking how to add that on a more regular basis (seems that the whay I did it now breaks port_based_qos in et driver, they use standard SIOCSMIIREG for that for some reason, which is not a good idea form my point of view, but this is the situation now).

    Anyway, I am writing this from behind my working_at_last WRT54G :)
     
  9. __nbd

    __nbd Network Guru Member

    The reason that we don't want to mess with et too much is, that it's non-free (Broadcom proprietary tags in the source files). We'll probably switch to a modified version of the b44 driver soon, so having that functionality in robocfg would be useful.
     
  10. FedXA

    FedXA Guest

    At the moment it is hard to add this to robocfg -- you need access to phy registers, which is unavailable in et. With b44 driver it should be no problem -- in fact, it was Oleg's idea to do it in this way, and he even has the required ioctls in b44. I was adding this to et just because I have not yet switched to OpenWRT, and really wanted to check now that the hardware i have will work for me. If OpenWRT is in working state with b44, I'll probably just switch to it. If not, then probably I'll do it in both ways :)
     

Share This Page