Jump to content

solarnetone

Members
  • Posts

    7
  • Joined

  • Last visited

  1. Last night's linux-next builds the SFP portion of the kernel... just fyi. Kernel detects SFP interface when interface is plugged into the cage.
  2. Thank you. I will follow the progress on it. Looks like the list of merges is here: https://lkml.org/lkml/2018/1/31/589 While I could likely hack up the dts, it looked like the main devs had some other changes to go in there as well, as relates to how the switch chip interfaces with the arm cores. While I don't mind pitching in, I don't want to screw something up either!
  3. So, I am working on a Clearfog Pro here, having compiled a 4.14.17 kernel and built a Debian Buster image on the m2 ssd via debootstrap. The board boots, and all the network ports behave as expected, but for the SFP cage. After spending some time digging through menuconfig, and not finding the appropriate option, I hunted a little, and found that sfp.c, sfp-bus.c, and phylink.c are all in the kernel code, but no manner of configuration can access them. I have dug up a couple of patchsets which seem necessary, but the dts patches (2nd link, january 2nd-7th, 2017 patches, near the bottom of the page) at least seem not to be merged into the mainline tree. I have not examined the kernel code yet for inclusion of the phylink/i2c/sfp related code on a line for line basis, but I do see the aforementioned .c files and related headers present in the drivers/net/phy directory of the tree. http://www.home.arm.linux.org.uk/~rmk/clearfog/v4.4-rc1-1/ https://patchwork.kernel.org/project/linux-arm-kernel/list/?submitter=165511&page=2 That is where I am at on it now, and am juggling several other responsibilities at the moment, so unfortunately fiber on the clearfog can't get my full attention just now. I will update when I have made some progress, unless anybody has better ideas. Enjoy, Scott
  4. It is only three pins that you have to solder. Not so tough. The rest of it was the hard part to figure out;)
  5. Sounds like either a) said patch is allocating a PHY for the fiber interface, or otherwise interfering with the phy for lan6 OR, some other factor, like lack of kernel module, or physical defect, is preventing the PHY from coming up. What does dmesg|grep phy say?
  6. I notice nobody mentioning the 88e6176. That as well required a 4.4.4 kernel. CONFIG_HAVE_NET_DSA=y CONFIG_NET_DSA=y CONFIG_NET_DSA_HWMON=y CONFIG_NET_DSA_TAG_EDSA=y CONFIG_NET_DSA_MV88E6XXX=m CONFIG_NET_DSA_MV88E6352=m Simply add mv88e6xxx_drv to /etc/modules after compilation. Interfaces are presented as lan1-lan6, such that normal network control tools like ip, ifconfig, and properly configured ifup/ifdown work as expected.
  7. Hi Ireng, I have been running the MK80 and MK80+ on the desktop for some time. Yes, the kernel is a bit crusty, but I was able to get Debian on the box. Maybe this groundwork can assist in an Armbian port. http://www.rikomagic.co.uk/forum/viewtopic.php?f=24&t=7603 Enjoy, Scott
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines