title: How drivers work out of the box in x86 and not in embedded computers like Android phone
body: <p>I'm curious about how the drivers work out of the box in x86 motherboards, like display, USB controllers etc.</p>
  
  <p>For example :
  Booting a toy custom kernel in x86 can display to screen without doing any extra work on the drivers space, however for an Android phone which is an embedded system, it seems almost impossible to display to screen with my own toy custom kernel (as there is information out there available about the memory map of the device and how the display is interfaced with the device).</p>
  
  <p>Why is that I/O works out of the box in x86 motherboards and doesn't on embedded computers?</p>