Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Some device drivers calculate various timing related things based on | bschmidt | 2010-11-13 | 1 | -0/+1 |
| | | | | | | | | the currently selected rate. The calculations of course need a valid rate. To make that possible before any call to node_rate() is done, initialize ni_txrate on none_node_init() calls. MFC after: 1 week | ||||
* | Fix an undefined behaviour if the desired ratectl algo is not available. | bschmidt | 2010-10-19 | 1 | -0/+113 |
This can happen if the algos are built as modules but are not loaded. If the selected ratectl algo is not available, try to load it (The load module functions does nothing currently). Add a dummy ratectl algo which always selects the first available rate. Use that one if the desired algo is not available. MFC after: 1 week |