Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sfp module dom eeprom related issues #46

Open
harold-liu opened this issue Jul 24, 2019 · 0 comments
Open

sfp module dom eeprom related issues #46

harold-liu opened this issue Jul 24, 2019 · 0 comments

Comments

@harold-liu
Copy link

harold-liu commented Jul 24, 2019

sonic-platform-common/sonic_sfp/sfputilbase.py

sfp module dom eeprom related issues(qsfp module works fine):
There are two situations in the DOM information location in the sfp module, we need a unified way to handle both cases.
Case A. i2c addr: 0x50 device node, offset 256-511
Case B. i2c addr: 0x51 device node, offset 0-255

  1. def get_eeprom_dom_raw(self, port_num). This function now actually gets i2c addr: 0x50, offset 0-255, which doesn't seem to work. (The following situation will only use 0x50)

     if port_num in self.port_to_eeprom_mapping.keys():
         sysfs_sfp_i2c_client_eeprom_path = self.port_to_eeprom_mapping[port_num]
    
  2. def get_transceiver_dom_info_dict(self, port_num). This function now actually gets i2c addr: 0x50, offset 256-511, which does not work properly in case B.

  3. line 1020,def get_transceiver_dom_info_dict(self, port_num): sfpd_obj = sff8472Dom() not working, calibration_type is not properly initialized.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant