Firmware: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
Modern chipsets move more and more functionality from fixed-function implementations in silicon to firmware or software. |
Modern chipsets move more and more functionality from fixed-function implementations in silicon to firmware or software. The chip becomes a more generic microcontroller or [[DSP]] that executes the Firmware and does the same jobs. |
||
The chip becomes a more generic microcontroller or [[DSP]] that executes the Firmware and does the same jobs. |
|||
Drawbacks are that this solution may consume more power than an optimized fixed-function design and that different firmware revisions can cause completely different behaviour of the chips. |
Drawbacks are that this solution may consume more power than an optimized fixed-function design and that different firmware revisions can cause completely different behaviour of the chips. |
||
The fact that the firmware can 'fix' bugs later has at some vendors the effect that early firmware revisions are rarely useable -- fixed-function |
The fact that the firmware can 'fix' bugs later has at some vendors the effect that early firmware revisions are rarely useable -- fixed-function hardware is usually more carefully designed. |
||
Revision as of 09:06, 13 September 2004
Modern chipsets move more and more functionality from fixed-function implementations in silicon to firmware or software. The chip becomes a more generic microcontroller or DSP that executes the Firmware and does the same jobs.
Drawbacks are that this solution may consume more power than an optimized fixed-function design and that different firmware revisions can cause completely different behaviour of the chips.
The fact that the firmware can 'fix' bugs later has at some vendors the effect that early firmware revisions are rarely useable -- fixed-function hardware is usually more carefully designed.