Difference between revisions of "MCE firmware"
From MCEWiki
(→Source code and version-control system) |
|||
| Line 26: | Line 26: | ||
* [[ Firmware Accessing the svn repository | Accessing the svn repository ]] | * [[ Firmware Accessing the svn repository | Accessing the svn repository ]] | ||
* [[ Firmware svn commit guidelines | svn commit guidelines ]] | * [[ Firmware svn commit guidelines | svn commit guidelines ]] | ||
| − | * | + | * svn basic operations |
** [[ Firmware svn tagging | tagging ]] | ** [[ Firmware svn tagging | tagging ]] | ||
** [[ Firmware svn merging | merging ]] | ** [[ Firmware svn merging | merging ]] | ||
** [[ Firmware svn branching | branching ]] | ** [[ Firmware svn branching | branching ]] | ||
** [[ Firmware svn undelete | resurrecting deleted items ]] | ** [[ Firmware svn undelete | resurrecting deleted items ]] | ||
Revision as of 15:52, 2 May 2008
Feature descriptions
Procedures for keeping DAS/MCE healthy during firmware upgrades, power cycles, etc.
It is good practice to do a resetmce and a resetpci after any firmware upgrades or power cycles. This is basically to clear out communications channels that may acquire garbage during these operations.
Currently the PCI firmware does not clear its fibre fifo on reset. This means that if there are fewer than 32 bits of garbage in the fifo, it doesn't get cleared until a valid reply from the MCE arrives. As a result, we may expect the first MCE command following power up to fail some of the time. Part of the power-up procedure should be to issue a command, then clear_fifo_mce_reply. After this, the PCI should be in a stable state.
MFH plans to resolve this issue in PCI firmware version U.1.4.
Source code and version-control system
We are migrating from CVS to SVN.
- Accessing the svn repository
- svn commit guidelines
- svn basic operations
