OSDev.org

octacone wrote:Also: why does paging mess up my LBF, when I enable paging I can't plot pixels.

octacone wrote:uint32_t Read32BitPCI(uint8_t bus, uint8_t device, uint8_t function, uint32_t offset)

Can I see if my vendor id device exists using that?

SpyderTL wrote:

octacone wrote:Also: why does paging mess up my LBF, when I enable paging I can't plot pixels.

You need to make sure that you map enough pages to cover your entire LFB, either exactly the same as your physical address (identity map), or if not, make sure your code is using your new virtual address instead of your physical address. You also need to make sure these pages are locked so that they don't get swapped to disk.

omarrx024 wrote:Never, ever, hard-code anything. The linear frame buffer can be anywhere. It's only ISA BGA that has it at 0xE0000000. PCI BGA can be anywhere; there are no rules. Even Bochs supports PCI BGA if you enable it in your configuration and the framebuffer can be relocated.
PCI is very easy, and your question says you didn't read the PCI Wiki entry.
Just for completion:

Code: Select all

unsigned int pci_read(pci_dev_t* device, char reg)
{
	unsigned char bus, slot, function;
	unsigned int config;
	bus = device->bus;
	slot = device->slot;
	function = device->function;
	config = (unsigned int)(bus<<16) | (slot<<11) | (function<<8) | (reg&0xFC) | 0x80000000;
	outd(PCI_CONFIG_INDEX, config);
	iowait();
	return (unsigned int)ind(PCI_CONFIG_DATA);
}

void pci_write(pci_dev_t* device, char reg, unsigned int val)
{
	char bus, slot, function;
	unsigned int config;
	bus = device->bus;
	slot = device->slot;
	function = device->function;
	config = (unsigned int)(bus<<16) | (slot<<11) | (function<<8) | (reg&0xFC) | 0x80000000;
	outd(PCI_CONFIG_INDEX, config);
	iowait();
	outd(PCI_CONFIG_DATA, val);
	iowait();
}

Kazinsal wrote:If reading and understanding the wiki page on PCI is too complex for you, this may not be your field.

octacone wrote:

Kazinsal wrote:If reading and understanding the wiki page on PCI is too complex for you, this may not be your field.

Better say it is time consuming.

omarrx024 wrote:

octacone wrote:

Kazinsal wrote:If reading and understanding the wiki page on PCI is too complex for you, this may not be your field.

Better say it is time consuming.

No, it is not. It took me less than a day to write my first PCI enumerator, which could search for devices by class codes or device/vendor ID combinations.

Kazinsal wrote:I stand even more firmly by my previous statement now.

If you give up on something after two hours you're going to drop this hobby like it's on fire the second you encounter a heisenbug.

octacone wrote:Just another question: once I get all the vendor IDs, device IDs, slots, functions, etc... How am I going to tell which one of them is Linear Frame Buffer?

sleephacker wrote:

octacone wrote:Just another question: once I get all the vendor IDs, device IDs, slots, functions, etc... How am I going to tell which one of them is Linear Frame Buffer?

By reading the wiki.

octacone wrote:I am not going to drop my hobby because I am annoyed. Already working on my PCI controller, I hope to finish it in less than two days and after that I want to be able to read my Linear Frame Buffer.

Just another question: once I get all the vendor IDs, device IDs, slots, functions, etc... How am I going to tell which one of them is Linear Frame Buffer?

;Function to detect the presence of the PCI controller/bus
;using Configuration Mechanism 1.
;
;If it was found, it will return 0x80000000.
;;
_00000000__Detect_PCI_Bus_Presence_Config_Mechanism_1:
 pushf
 push ebx
 push edx



 .PCI_Addr_Reg_Write_Bus0_Dev0_Fn0_Reg0:
 ;;
  mov dx,0xCFC
  mov ebx,0x80000000
  mov eax,ebx
  out dx,eax


 .PCI_Addr_Reg_Read_Bus0_Dev0_Fn0_Reg0:
 ;;
  in eax,dx
  cmp eax,ebx
  je .FoundAndEnd


     .NotFound:
     ;;
      xor eax,eax



 .FoundAndEnd:
 ;;


 pop edx
 pop ebx
 popf
ret



;EOF