RE: more info about: odd result of pci_read_config

> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Nicolas Souchu > Sent: Monday, January 22, 2001 10:48 AM > To: Steve Shoecraft > Cc: 'John Baldwin'; 'Donald J . Maddox'; [EMAIL PROTECTED] > Su

RE: more info about: odd result of pci_read_config

> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Nicolas Souchu > Sent: Sunday, January 21, 2001 4:19 AM > To: John Baldwin > Cc: Donald J . Maddox; [EMAIL PROTECTED] > Subject: Re: more info about: odd result of pci_read_config > > > On Sat, Jan 20,

RE: more info about: odd result of pci_read_config

Nic - 0x6 is the return value from the error_method routine. > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Donald > J . Maddox > Sent: Saturday, January 20, 2001 6:28 PM > To: Nicolas Souchu > Cc: [EMAIL PROTECTED] > Subject: Re: more inf

RE: RE: FreeBSD vs Linux, Solaris, and NT

om: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Matt Dillon > Sent: Tuesday, December 19, 2000 2:36 PM > To: Steve Shoecraft > Cc: 'Soren Schmidt'; [EMAIL PROTECTED] > Subject: Re: RE: FreeBSD vs Linux, Solaris, and NT > > > Yes, it's a pre

RE: FreeBSD vs Linux, Solaris, and NT

> > It seems Steve Shoecraft wrote: > > > > There are a number of reasons why a manufacturer can > not/will not release > > source code for a driver. A few that come to mind are: > > > > a) A device driver is a reflection of the &

RE: FreeBSD vs Linux, Solaris, and NT

There are a number of reasons why a manufacturer can not/will not release source code for a driver. A few that come to mind are: a) A device driver is a reflection of the hardware. Manufacturers in highly competitive markets could potentially be giving away trade secret

RE: Accessing the Video Bios on a PCI card?? (vm_map ?)

Well, I never did get that to work last night. Any maps outside of the memory range on the machine (which only has 128 meg) turned up all 1s in all bits. I dropped the issue for the moment and looked at AGP ... I'm currently doing DMA transfers, but it's an AGP card, and I'm wondering a

RE: Accessing the Video Bios on a PCI card?? (vm_map ?)

(this is a winblows system with my work-related email on it - you expect sane wrapping?) Anyway ... I got the size of the bios using the method you suggested. I used malloc to get a chunk of memory, turned the ptr into a physical addr, then used free to get rid of it. I then us

RE: Accessing the Video Bios on a PCI card?? (vm_map ?)

: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Steve Shoecraft Sent: Tuesday, December 12, 2000 2:02 AM To: [EMAIL PROTECTED] Subject: Accessing the Video Bios on a PCI card?? I have a ATI rage 128 all-in-blunder agp card. I'm currently writing a driver for video capture.

Accessing the Video Bios on a PCI card??

I have a ATI rage 128 all-in-blunder agp card. I'm currently writing a driver for video capture. I got everything to work properly so far, but I'm using "plugged-in" values for certain things that REQUIRE I get them from the video bios on the card (multimedia table, tv-out table, etc.).