-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Work on powerpc/beatnik/if_mve network driver (epics codeathon 2021) #4
Open
till-s
wants to merge
7
commits into
RTEMS:5-freebsd-12
Choose a base branch
from
paulscherrerinstitute:5-TS_if_mve_work_epics_codeathon_2021
base: 5-freebsd-12
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Work on powerpc/beatnik/if_mve network driver (epics codeathon 2021) #4
till-s
wants to merge
7
commits into
RTEMS:5-freebsd-12
from
paulscherrerinstitute:5-TS_if_mve_work_epics_codeathon_2021
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
First stab at mv643xx; port almost complete (mii stuff missing) and compiles -- no tests yet!
was delayed by waf not printing compiler warnings by default! Three little typos cost me almost a day: - missing 'return 0;' at the end of mve_attach() - two bad pointers (wrong type) used All of these would have been found within minutes had the warnings not been disabled :-(
The recursive lock takes care of this...
Testing (TCP with larger amounts of data while MVETH_TESTING was defined which reduces the ring sizes to very small numbers) revealed that the BSD stack honours the 'sendqlen' and never hands us chains exceeding the ring size.
…r statistics The 'legal' access by means of a special ioctl() is way too cumbersome when you need to do quick diagnosis.
avoid using struct members directly.
Is this a PCI bus device? |
The ethernet adapter is part of the system controller and accessible directly (w/o going through PCI). |
Maybe I have the wrong board. Do you have a link to the board's datasheet? The beatnik I have looked at has an octet Marvel NIC and there are are 8 marvel devices appearing in the PCI probes. The e1000 is on a secondary PCI bus. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull-request adds a nexus ethernet driver for the Marvell mv643xx chip which is present on the MVME6100 board (beatnik BSP). Note that the patch requires a companion patch to the RTEMS BSP.