|tagger||Luis R. Rodriguez <firstname.lastname@example.org>||Thu Jan 24 08:00:25 2013 -0800|
With a slew of updates from Xiong
|author||xiong <email@example.com>||Sat Jan 19 13:15:10 2013 +0800|
|committer||Luis R. Rodriguez <firstname.lastname@example.org>||Thu Jan 24 07:56:06 2013 -0800|
alx: improve self-test for FPGA define new registers value for C0 version for register checking test, and untouch PHY setting when do MAC loopback test. PS. PHY external loopback isn't supported for FPGA due to board limitation. Signed-off-by: xiong <email@example.com> Signed-off-by: Luis R. Rodriguez <firstname.lastname@example.org>
The puropose of this development tree is to enable us to do development on alx for both BSD and Linux with a single unified repository. This enables us to synchronize fixes for both BSD and Linux. The idea is to help end typical proprietary driver development for good:
Linux support targets the alx driver to be built in synch with linux-next.git as the base development tree. Backport kernel support is provided by utilizing the compat-drivers framework.
To build for linux you will need a few trees. We have scripts to let you get all that you need:
Contributions to compat follow the same mechanisms as used in the Linux kernel, this means you should provide as Singed-off-by tag as documented on the Developer's Certificate of Origin 1.1.
compat and compat-drivers contributions follow the contribution model implemented by the Linux kernel. Patches or pull requests for compat and compat-drivers must have be signed-offed. If you don‘t sign off on them they will not accepted. This means adding a line that says “Signed-off-by: Name email” at the end of each commit, indicating that you wrote the code and have the right to pass it on as an open source patch. For exact definition of what the Signed-off-by tag is you can read the definition of the "Developer’s Certificate of Origin 1.1", which you can read here:
You can send patches as follows: