Hello everyone.
I have a couple of questions.
Most of you might have read this
http://renderingpipeline.com/graphics-literature/low-level-gpu-documentation and this https://01.org/linuxgraphics/downloads
Intel has released low level documentation for most of their GPUs like HD4000/HD4400 etc and the other website has Linux implementation with source code. Has anyone done graphics driver/program using these?(In FASM, of-course;For a new OS)
I have Acer-i5-Intel HD 4400. Is it enough to write driver using this information (provided in those documents) or do we need to write any manufacturer specific implementation (Acer, in this case)?
Suppose i have written a graphics driver for my Acer Laptop, will the same driver work equally well for Dell/Lenovo/other laptops with similar configuration?
Any help will be appreciated. Thanks.

I guess it will also depend on the OS.

I mean when programming new OS.

In that case I have moved this topic to "OS Construction".

what you are worried about is something that you usually shouldn't be concerned with. as long as you use PCI Vendor ID and Device ID pair to determine the device you won't (usually) have a problem.

I'm writing a USB2.0 driver and the two devices I'm testing it on have identical VID/PID (in the PCI Config Space) values yet one of them doesn't fire any Port Change interrupts (every other interrupt from the device work). the device can always be defective, though.

my advice is simple: just build a driver according to the specs (given the correct VID/PID pair) first and then deal with other vendors.

- Stefan

Id probably start my OS with VBE3.0. using the protected mode entry point you can get some pretty quick graphics. You can also map the linear frame buffer so you can avoid VBE bank switching. If detect intel HD then load your driver else load VBE interface.

I recommend you create your intel HD driver useing the same routines as the VBE3.0 specs. This will make calling the driver transperant. ie; OS can call a routine that its expected to see.

I have a VBEAF.DRV wich is like having a basic version of directX. the VBE_AF specs can be found on the net