Hello Pashant,

Yes, netmap is separate repo:
https://git.linaro.org/lng/odp-netmap.git

You can find that it was branched from linux-generic, then separate platform was created: ./platforms/linux-netmap

In general it follows the latest changes in linux-generic and should have symmetrical tags. At least have some synchronization points. For now it's a little bit behind linux-generic due to all power now is on odp-1.0 release. If you need some specific you can
ask Ciprian.

Best regards,
Maxim.

On 01/21/2015 07:44 AM, Prashant Upadhyaya wrote:

Hi,

In v0.2 the packet socket and netmap backends were part of the main repository.

Now I see that there is a ‘main’ repository whose linux generic backend has packet sockets.

Netmap has gone into a different repository.

Now my question is – is the ODP-Netmap a standalone repo i.e when I build it and link it with my application I don’t need the libraries from what I call the main repo for which versions like v0.7, v0.8 etc. are being released ?

If ODP-Netmap is indeed a standalone repo, then I expect that it should be tagged as well in lock step with the main repo releases so that if my application is compliant with main repo v0.X, then I need to have a corresponding tag in the ODP-Netmap which is also compliant with v0.X, so that my application can build against ODP-Netmap seamlessly. Eg. can it be said that the ODP-Netmap repo is as good in its linux-generic borrowed part as the v0.8 linux-generic of the main repo.

I am open to being educated on the workflow for my application given the above background for linking with ODP-Netmap as I move ahead of v0.2 when everything was together.

Regards

-Prashant

"DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus."


_______________________________________________
lng-odp mailing list
[email protected]
http://lists.linaro.org/mailman/listinfo/lng-odp


_______________________________________________
lng-odp mailing list
[email protected]
http://lists.linaro.org/mailman/listinfo/lng-odp

Reply via email to