> 2. CM3 code has very small footprint requirement, we cannot
> implement the complete Serdes and PHY infrastructure that kernel
> provides as part of CM3 application. Therefore I would like to
> continue relying on kernel configuration for that.
How can that work? How does Linux know when CM3 has up'ed the
interface? How does CM3 know the status of the link? How does CM3 set
its flow control depending on what auto-neg determines, etc?
> 3. In some cases we need to dynamically switch the port "user"
> between CM3 and kernel. So I would like to preserve this
> functionality.
And how do you synchronize between Linux and CM3 so you know how is
using it and who cannot use it?
Andrew
