[platform]: update mitac platform drivers and device #2024
Conversation
Signed-off-by: Stane Shieh <[email protected]>
Signed-off-by: Stane Shieh <[email protected]>
… of i2c modules. Signed-off-by: Stane Shieh <[email protected]>
Signed-off-by: Stane Shieh <[email protected]>
| * RETURNS: | ||
| * No. | ||
| */ | ||
| void* bms_xcvr_polld(void *args) |
There was a problem hiding this comment.
this is essentially the xrcvd does.
There was a problem hiding this comment.
If our xcvr-servd is not running in SONiC, we will not see "state UP" via the "ip addr" command and will not see anything through the "show interfaces transceiver eeprom" command when plugging in the transceiver.
The implementation difference between our xcvr-servd and SONiC's xrcvd might be related to our hardware design. Please allow our xcvr-servd to run on SONiC for our platform module.
|
we need license for all source code file, for user space file, please use apache license. |
Signed-off-by: Stane Shieh <[email protected]>
| * for other cases, negative errno is returned. | ||
| */ | ||
| static int | ||
| bms_xcvr_i2c_write(unsigned char bus, |
There was a problem hiding this comment.
we have sff_8436_eeprom driver allow you user to access sfp eeprom data via sysfs. It is redudant to have same code in user space that does the same thing.
| @@ -0,0 +1,345 @@ | |||
| /* | |||
| * Licensed to the Apache Software Foundation (ASF) under one | |||
There was a problem hiding this comment.
the function here is overalpping with the sff_8436_eeprom driver in sonic.
There was a problem hiding this comment.
There are two main benefits to access EEPROM via the API of bms_xcvr_access.c
- it is a portable implementation that does not depend on any EEPROM driver.
- the execution performance is faster than calling three APIs open(), read()/write(), and close() to access sysfs.
|
minigraph.xml is no longer needed. |
|
remove minigraph.xml |
|
According to the console output at https://sonic-jenkins.westus2.cloudapp.azure.com/job/broadcom/job/buildimage-brcm-all-pr/2928/, the failure was caused by "port 443: the network is unreachable". Can you help us solve the problem "port 443: the network is unreachable" by your side? |
|
We will modify the default level of low-speed pins for plug&play of QSFP and remove the controversial "xcvr_servd" of MiTAC. |
- What I did
Update ly1200 to support stretch
- How I did it
Modify driver code
- How to verify it
Upload image to DUT to ensure all modules are running correctly.
- Description for the changelog
- A picture of a cute animal (not mandatory but encouraged)