question

BIOS has many key features that lend to real-time embedded development.  Here are a few key features where the configuration step plays a vital part.

Small footprint
A small footprint is important since memory is generally a limited resource. One way to keep the footprint small is by statically defining objects. This removes the need of run-time code for initialization. BIOS could have the user supply the static structures but this is very error-prone and makes moving between versions extremely painful. Instead, the configuration step generates these static structures for the user. This allows portability and is much more user friendly. Also the configuration code has logic to help minimize the footprint.

Error Checking
In an embedded device there are many variables with a system (memory maps, cache, etc.) that an application needs to setup. The logic in the configuration code checks to make sure the user did not attempt to generate an invalid state.

Faster Boot time
Many embedded devices need to get to a running state quickly. By statically configuring as much as possible, there is no need to execute initialization code during the boot (which might include memory allocation). Having some cinit records is much faster than allocating memory and executing code to initial it.

Less Memory allocation
When things are statically generated, there is less need to perform runtime memory allocation.

I'm sure I missed some other reasons, but hopefully this is a start. Is there a specific reason why you are asking this?

Todd

thanks sir ,,,,,,, just i want to know about the basics of that so i posted that question