Page MenuHomeFreeBSD

Allow building VNIC as a module
ClosedPublic

Authored by wma on May 13 2016, 8:12 AM.
Tags
None
Referenced Files
Unknown Object (File)
Dec 20 2023, 12:19 AM
Unknown Object (File)
Dec 12 2023, 5:06 PM
Unknown Object (File)
Nov 11 2023, 12:29 AM
Unknown Object (File)
Nov 6 2023, 7:07 PM
Unknown Object (File)
Oct 30 2023, 9:35 AM
Unknown Object (File)
Oct 9 2023, 11:27 PM
Unknown Object (File)
Oct 5 2023, 6:17 PM
Unknown Object (File)
Sep 23 2023, 1:32 PM
Subscribers

Details

Summary
Add directory structure and fix dependencies to be able to
build and use Cavium VNIC driver as a module.

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

wma retitled this revision from to Allow building VNIC as a module.
wma updated this object.
wma edited the test plan for this revision. (Show Details)
wma added reviewers: zbb, emaste.
wma set the repository for this revision to rS FreeBSD src repository - subversion.
zbb edited edge metadata.

Very few files in the tree contain copyrights in the modules Makefiles. IMHO it would be better to just keep the minimum contents ($FreeBSD$ string) and that's all.
All the necessary copyrights are in the files that are build in the process.

This revision is now accepted and ready to land.May 20 2016, 7:34 AM
sys/dev/vnic/nic_main.c
140 ↗(On Diff #16278)

BTW. I don't like the name change. Why is it needed. The proper name for this device is NIC whereas virtual instances are VNICs

It's mostly to keep the module name fit the vnic convention. The "NIC" name is too generic IMHO. As discussed today, agreed to leave vnicpf.

This revision was automatically updated to reflect the committed changes.