VGA support: Difference between revisions

From coreboot
Jump to navigation Jump to search
Line 23: Line 23:


If you want to use the onboard VGA chip, you have to add the following options in addition to the CONFIG options described above.
If you want to use the onboard VGA chip, you have to add the following options in addition to the CONFIG options described above.
=== Mainboard Configuration ===


1. In the mainboard Config.lb (./src/mainboard/<mfg>/<board>/Config.lb) You need to specify the device number for your onboard VGA and the address that the video bios will show up at in the system.
1. In the mainboard Config.lb (./src/mainboard/<mfg>/<board>/Config.lb) You need to specify the device number for your onboard VGA and the address that the video bios will show up at in the system.
Line 38: Line 40:
Replace the 9.0 with the dev.fn of your vga device.  You can find this number by doing a 'lspci' from the board booted under linux.
Replace the 9.0 with the dev.fn of your vga device.  You can find this number by doing a 'lspci' from the board booted under linux.
Please make sure the device number is correct. Otherwise the config code can not compute the proper ROM address.
Please make sure the device number is correct. Otherwise the config code can not compute the proper ROM address.
==== How to compute the "rom_address" value ====
ROM (called 'flash' a lot) chips are located directly below 4Gbyte  (0xffffffff) boundary.
So you need to calculate the address by subtracting the
flash chip size (and adding the offset within the image)
In coreboot the offset within the image is 0, because its the first
thing in the coreboot image.
So you need to compute the address in the systems memory space where the start of the video bios will show up.
To do this you take the 4Gb of address and subtract the size of your coreboot image.
0x100000000 - (ROM size in Kb * 1024)
You can do this in bash by:
biossize=256
printf "0x%x\n" $(( 0x100000000 - ($biossize*1024) ))
Addresses for popular chip sizes:
256K  0xfffc0000
512k  0xfff80000
1024k 0xfff00000
=== Target Configuration ===


2. You still need to modify your target 'Config.lb' to reserve space for the additional video bios.  Reduce the size of your coreboot image by the size of the video bios. You will prepend the video bios to the coreboot image in step 3.
2. You still need to modify your target 'Config.lb' to reserve space for the additional video bios.  Reduce the size of your coreboot image by the size of the video bios. You will prepend the video bios to the coreboot image in step 3.
Line 52: Line 82:


In the above example the bios chip is 512Kb part.  The video bios is  48Kb.  So (512*1024)-(48*1024) = 475136.
In the above example the bios chip is 512Kb part.  The video bios is  48Kb.  So (512*1024)-(48*1024) = 475136.
=== Creating an Image ===


3. Finally, prepend your video bios to the coreboot.rom
3. Finally, prepend your video bios to the coreboot.rom
Line 64: Line 96:
dd is helpfull to get your <videobios.bin> when booted under the  factory BIOS.
dd is helpfull to get your <videobios.bin> when booted under the  factory BIOS.


===== How to compute the "rom_address" value =====
ROM (called 'flash' a lot) chips are located directly below 4Gbyte  (0xffffffff) boundary.
So you need to calculate the address by subtracting the
flash chip size (and adding the offset within the image)
In coreboot the offset within the image is 0, because its the first
thing in the coreboot image.
So you need to compute the address in the systems memory space where the start of the video bios will show up.
To do this you take the 4Gb of address and subtract the size of your coreboot image.
0x100000000 - (ROM size in Kb * 1024)
You can do this in bash by:
biossize=256
printf "0x%x\n" $(( 0x100000000 - ($biossize*1024) ))
Addresses for popular chip sizes:
256K  0xfffc0000
512k  0xfff80000
1024k 0xfff00000


===== How to retrieve a good video bios =====
== How to retrieve a good video bios ==
There are sites that have video bios roms on their website. (I know of this one for nvidia cards: [http://whitebunny.demon.nl/hardware/chipset_nvidia.html])
There are sites that have video bios roms on their website. (I know of this one for nvidia cards: [http://whitebunny.demon.nl/hardware/chipset_nvidia.html])


Line 102: Line 111:
* You now have a video bios image
* You now have a video bios image


===== Perl script to dump out your video bios =====
=== Perl script to dump out your video bios ===


This is a simple script that computes the size and offset then uses
This is a simple script that computes the size and offset then uses

Revision as of 16:21, 18 June 2008

There are two kinds of VGA devices

  1. on-board VGA
  2. add-on cards

VGA initialization in coreboot v2

General

You need to enable two CONFIG options in your Mainboard Option.lb

 #VGA Console
 option CONFIG_CONSOLE_VGA=1
 option CONFIG_PCI_ROM_RUN=1

CONFIG_PCI_ROM_RUN will use the embedded x86 emulator to run the BIOS image in the expansion ROM of a PCI device. CONFIG_CONSOLE_VGA will redirect console messages to the VGA screen once VGA card is initialized.

For addon VGA cards, you don't have to do anything else besides these two CONFIG options. If your mainboard has an onboard VGA chip and you insert another VGA addon card, the addon VGA card will be used instead of the onboard VGA chip.

Onboard Video

If you want to use the onboard VGA chip, you have to add the following options in addition to the CONFIG options described above.

Mainboard Configuration

1. In the mainboard Config.lb (./src/mainboard/<mfg>/<board>/Config.lb) You need to specify the device number for your onboard VGA and the address that the video bios will show up at in the system.

<source lang = bash>

device pci 9.0 on  # PCI
        chip drivers/pci/onboard
                device pci 9.0 on end
                register "rom_address" = "0xfff80000" #512k image
                #register "rom_address" = "0xfff00000" #1M image
        end
end

</source>

Replace the 9.0 with the dev.fn of your vga device. You can find this number by doing a 'lspci' from the board booted under linux. Please make sure the device number is correct. Otherwise the config code can not compute the proper ROM address.


How to compute the "rom_address" value

ROM (called 'flash' a lot) chips are located directly below 4Gbyte (0xffffffff) boundary.

So you need to calculate the address by subtracting the flash chip size (and adding the offset within the image)

In coreboot the offset within the image is 0, because its the first thing in the coreboot image.

So you need to compute the address in the systems memory space where the start of the video bios will show up.

To do this you take the 4Gb of address and subtract the size of your coreboot image.

0x100000000 - (ROM size in Kb * 1024)

You can do this in bash by:

biossize=256
printf "0x%x\n" $(( 0x100000000 - ($biossize*1024) ))

Addresses for popular chip sizes:

256K  0xfffc0000
512k  0xfff80000
1024k 0xfff00000


Target Configuration

2. You still need to modify your target 'Config.lb' to reserve space for the additional video bios. Reduce the size of your coreboot image by the size of the video bios. You will prepend the video bios to the coreboot image in step 3.

in the normal section

<source lang="bash"> romimage "normal"

  1. 48K for SCSI FW or ATI ROM

option ROM_SIZE = 475136 </source>

or if you only have a "fallback" boot then use the "fallback" section instead.

In the above example the bios chip is 512Kb part. The video bios is 48Kb. So (512*1024)-(48*1024) = 475136.

Creating an Image

3. Finally, prepend your video bios to the coreboot.rom

<source lang="bash"> cat <videobios.bin> coreboot.rom > final_coreboot.rom </source>

where <videobios.bin> is the name of your video bios image. You need to make sure the final_coreboot.rom size is the size of your ROM chip. Normally 256kb, 512kb, or 1024Kb.

dd is helpfull to get your <videobios.bin> when booted under the factory BIOS.


How to retrieve a good video bios

There are sites that have video bios roms on their website. (I know of this one for nvidia cards: [1])

However you should be able to retrieve your own video bios as well with linux.

  • Boot up a machine with a commercial bios (not coreboot) with the video card you wish to work under coreboot.
  • From the command line enter:
    dd if=/dev/mem of=vgabios.bin skip=1536 count=128 or
    dd if=/dev/mem of=vgabios.bin bs=1k count=64 skip=768
    This assumes you card's bios is cached at 0xc0000, and is 64K long. You
    can see where and how much your card's bios is using by
    doing a cat iomem | grep "Video ROM"
    • dd Explained (man dd to learn more):
      • if is the location to retrieve from.
      • of is the output file (your rom image)
      • skip jumps n blocks where the default n is 512 bytes
      • count is how many blocks you wish to read
      • bs is the block size
  • You now have a video bios image

Perl script to dump out your video bios

This is a simple script that computes the size and offset then uses the command dd to dump your video bios to a file.

<source lang="perl">

#!/usr/bin/perl

($range, $info) = split /:/, `grep "Video ROM" /proc/iomem`; ($start, $end) = split /-/, $range;

if( $start eq "" ) {

       print "Couldn't find Video ROM in /proc/iomem\n";
       exit;

}

$offset = hex "0x$start"; $tmp = hex "0x$end"; $size = 1 + $tmp - $offset;

$command = "dd if=/dev/mem of=saved_vgabios.bin bs=1c count=$size skip=$offset"; print "range = $range, start = $start, size = $size\n"; print "$command\n"; system $command; </source>