This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM6548: Marvell PHY driver

Part Number: AM6548

The TI SDK 06.00.00.07 includes a Marvell driver that is out of date. (marvell.c)

How can I update the file to work with Marvell Q2112.

What steps are recommended ?

Links ?

 

  • Part Number: AM6548

    TI SDK for the am65xx .

    I need to update or replace a driver.

    What steps do i need to take ( be as complete as possible) to update the driver ?

    If I need to replace the driver completely - what do I have to do ? Rebuild the SDK ... ? Is it a yocto project ?

    I am new at this so a detail answer would make me understand better!

     

  • Hi,

    The kernel source tree that TI places in the SDK snapshots or starts with a LTS version of the kernel source from the Linux mainline source tree. Whatever drivers in the tree at that time are taken as is. In this case the driver for the Marvell PHY is maintained by Marvell and Marvell would have the responsibility for maintaining their driver in the kernel source tree. I recommend contacting Marvell to see if they have the info and links on how to update the driver in the kernel source tree. 

    Best Regards,

    Schuyler

  • So your answer is telling me to go and ask marvell about a new driver ....that they should update in the kernel source tree... I do not believe this is very helpful ...

  • Hi,

    I can appreciate your frustration with the response but please understand that this is the nature of how the open source community works. The contributors are responsible for maintaining what they want to maintain in the mainline kernel source tree. Submitting drivers to the kernel tree goes through a somewhat rigorous process and Marvell may not have been to update their driver for a variety of reasons, only Marvell will know this since it is their driver. TI only takes what is in the source tree when TI builds the SDK. TI does not have contact with Marvell or any other contributor unless it is related directly to supporting a TI peripheral internal to the processor in the kernel.

    Best Regards,

    Schuyler

  • Hi thank you for your response and time spent on it, sincerely!

    But my question refers more to how do I change a driver in the TI SDK , the process?

    I need guidance in including a new driver , by myself, in the TI SDK 

    The link http://software-dl.ti.com/processor-sdk-linux/esd/docs/latest/linux/Overview_Building_the_SDK.html does not offer to much help in how to rebuild the SDK with a new driver ...

    Please advise!

  • Hi,

    The documentation that you are pointing to is on how to recreate the SDK which will build the kernel, there is a more direct documentation about building the kernel. Please understand that TI is not going to have documentation on individual steps on replacing a driver in the kernel source tree.

    This is a very brute force method that is not friendly to sustained development. Ideally you would patch the file in the git tree. If you have the updated driver then you can copy over the file in this directory:

    drivers/net/phy/marvell.c

    Since the file exists you should not have to change makefiles or menuconfig. 

    You can build the kernel one of two ways, here is a link on how to build the kernel in the SDK.

    Kernel build instructions

    There is a top level make command that is documented, I recommend the above step since it discusses how to install the kernel, drivers and DTB files.

    This is the best I can do for you though as TI does not support driver updating and I have not tried so this is only a suggestion. For example, the step of copying over the file may not be enough in that there may be additional include files that are required to build the driver. Ideally the vendor has a patch set or some instructions on the changes necessary to build the driver. 

    Best Regards,

    Schuyler

  • Hi, 

    Thank you, Thank You Thank YOU!

    I thought that was how is done too but I kind of needed a confirmation. I understand you did not do it but theoretically it should work !

    Thank you once again and hopefully it works !