Re: [osol-code] Programming funny PCI device

2006-11-15 Thread Dan Mick
Cyril Plisko wrote: On 11/15/06, Dan Mick <[EMAIL PROTECTED]> wrote: Cyril: Which device is this, and is its spec freely available? I am not sure the spec is free - I'll check it. And it appears to me now (after some additional research I did on that) that it is BIOS fault/feature. It is BIO

Re: [osol-code] Programming funny PCI device

2006-11-15 Thread Cyril Plisko
On 11/15/06, Dan Mick <[EMAIL PROTECTED]> wrote: Cyril: Which device is this, and is its spec freely available? I am not sure the spec is free - I'll check it. And it appears to me now (after some additional research I did on that) that it is BIOS fault/feature. It is BIOS that were to progra

Re: [osol-code] Programming funny PCI device

2006-11-15 Thread Dan Mick
Cyril: Which device is this, and is its spec freely available? Dan Mick wrote: Cyril Plisko wrote: On 11/14/06, Dan Mick <[EMAIL PROTECTED]> wrote: >> Cyril, what happens when you enabled this BAR - presumably it needs >> resources allocated to it? > > Yes, I need to map this BAR. If that is

Re: [osol-code] Programming funny PCI device

2006-11-14 Thread Dan Mick
Cyril Plisko wrote: On 11/14/06, Dan Mick <[EMAIL PROTECTED]> wrote: >> Cyril, what happens when you enabled this BAR - presumably it needs >> resources allocated to it? > > Yes, I need to map this BAR. If that is what you mean by allocating > resources well, "map this BAR" is ambiguous. Phys

Re: [osol-code] Programming funny PCI device

2006-11-14 Thread Dana H. Myers
Cyril Plisko wrote: > On 11/14/06, Dana H. Myers <[EMAIL PROTECTED]> wrote: >> It sounds like Cyril has a bigger problem - his device has a Base >> Address Register >> which isn't present when the device is enumerated (and possibly >> programmed on >> x86/x64). By the time he gets around to enabl

Re: [osol-code] Programming funny PCI device

2006-11-14 Thread Garrett D'Amore
Cyril Plisko wrote: > On 11/14/06, Dan Mick <[EMAIL PROTECTED]> wrote: > >> >> Cyril, what happens when you enabled this BAR - presumably it needs >> >> resources allocated to it? >> > >> > Yes, I need to map this BAR. If that is what you mean by allocating >> > resources >> >> well, "map this BAR"

Re: [osol-code] Programming funny PCI device

2006-11-14 Thread Paul Durrant
On 11/14/06, Cyril Plisko <[EMAIL PROTECTED]> wrote: On 11/14/06, Dan Mick <[EMAIL PROTECTED]> wrote: > >> Cyril, what happens when you enabled this BAR - presumably it needs > >> resources allocated to it? > > > > Yes, I need to map this BAR. If that is what you mean by allocating > > resources

Re: [osol-code] Programming funny PCI device

2006-11-14 Thread Joerg Schilling
"Dana H. Myers" <[EMAIL PROTECTED]> wrote: > It sounds like Cyril has a bigger problem - his device has a Base Address > Register > which isn't present when the device is enumerated (and possibly programmed on > x86/x64). By the time he gets around to enabling this additional BAR, it's > long af

Re: [osol-code] Programming funny PCI device

2006-11-14 Thread Cyril Plisko
On 11/14/06, Dan Mick <[EMAIL PROTECTED]> wrote: >> Cyril, what happens when you enabled this BAR - presumably it needs >> resources allocated to it? > > Yes, I need to map this BAR. If that is what you mean by allocating > resources well, "map this BAR" is ambiguous. Physical memory space nee

Re: [osol-code] Programming funny PCI device

2006-11-14 Thread Dan Mick
Cyril Plisko wrote: On 11/14/06, Dana H. Myers <[EMAIL PROTECTED]> wrote: Garrett D'Amore wrote: > Cyril Plisko wrote: >> Hi, >> >> Here is the story: >> I am writing [solaris] driver for a PCI device. Should be a simple task, >> but there is a catch - in the PCI configuration space there is a

Re: [osol-code] Programming funny PCI device

2006-11-13 Thread Cyril Plisko
On 11/14/06, Dana H. Myers <[EMAIL PROTECTED]> wrote: Garrett D'Amore wrote: > Cyril Plisko wrote: >> Hi, >> >> Here is the story: >> I am writing [solaris] driver for a PCI device. Should be a simple task, >> but there is a catch - in the PCI configuration space there is a region >> of vendor re

Re: [osol-code] Programming funny PCI device

2006-11-13 Thread Dana H. Myers
Garrett D'Amore wrote: > Cyril Plisko wrote: >> Hi, >> >> Here is the story: >> I am writing [solaris] driver for a PCI device. Should be a simple task, >> but there is a catch - in the PCI configuration space there is a region >> of vendor registers above all the standard registers. In order to ha

Re: [osol-code] Programming funny PCI device

2006-11-13 Thread Garrett D'Amore
Cyril Plisko wrote: > Hi, > > Here is the story: > I am writing [solaris] driver for a PCI device. Should be a simple task, > but there is a catch - in the PCI configuration space there is a region > of vendor registers above all the standard registers. In order to have > one > of the BARs accessib

[osol-code] Programming funny PCI device

2006-11-13 Thread Cyril Plisko
Hi, Here is the story: I am writing [solaris] driver for a PCI device. Should be a simple task, but there is a catch - in the PCI configuration space there is a region of vendor registers above all the standard registers. In order to have one of the BARs accessible I need to tinker with one of th