Return to Answer

video option is to mention the video mode option.Some global options to use in the underlying GPU.And the uvesafb is actually a generic framebuffer driver which makes use of the standards set by the VESA association. mode_option=1280x800-24 means the resolution 1280x800 with 24 as the Color Depth or a.k.a Bits Per Pixel (8-bit for Red , Green and Blue channel each).

video option is to mention the video mode option.Some global options to be used in the underlying GPU.And the uvesafb is actually a generic framebuffer driver which makes use of the standards set by the VESA association. mode_option=1280x800-24 means the resolution 1280x800 with 24 as the Color Depth or a.k.a Bits Per Pixel (8-bit for Red , Green and Blue channel each).

It's actually there to control the scrolling when you're in the text mode(e.g text-mode console not graphical)

In fact it's there to set the mode of the scrolling operation operation when you're in the text mode(e.g text-mode console not graphical)

The mtrr=3 means the write-combining attribute.It's actually a caching technique to buffer the Read/Write requests to later release them in burst mode to better utilize the bandwidth and prevent consistent Read/Write cycles and resource exhaustion perhaps.Because the Read/Write operations aren't released in-order , it can cause sever bugs and problems if gets utilized in most of the programs , but in framebuffers out-of-order memory operations is not a problem.So using it in the framebuffer operations (we're talking about the framebuffer driver uvesafb) makes sense.It can increase the performance quite a lot.

The mtrr=3 means the write-combining attribute.It's actually a caching technique to buffer the Read/Write requests to later release them in burst mode to better utilize the bandwidth and prevent consistent Read/Write cycles and resource exhaustion perhaps.

Because the Read/Write operations aren't released in-order , it can cause sever bugs and problems if gets utilized in most of the programs(Thread-safety is based on the assumption that those operations are done in-order) , but in framebuffers out-of-order memory operations is not a problem(You don't care whether the top-left corner of the image on your screen gets drawn first or the bottom-left one when a frame is rendered in less than 50 msec).So using it in the framebuffer operations (we're talking about the framebuffer driver uvesafb) makes sense.It can increase the performance quite a lot.