Re: 1394 OHCI Port Driver API by r_konjeti
r_konjeti
Wed Aug 30 15:01:14 CDT 2006
Joreon,
>> Currently I am looking for an API that gives me access to the LLC and PHY
>> registers on my 1394 board. I need this because I want to be able to read
>> the type/version information from these chips since some work better than
>> others.
I am working on a 1394 driver. Can you give me some data on which
type/versions of LLC and PHY work better than other.
Thanks,
Raj
Doron Holan [MS] wrote:
> you could install a lower filter driver below the port driver that did the
> reading of these registers when it processed IRP_MN_START_DEVICE. you would
> then need to commonicate that to your driver. either both devices (The FDO
> and the filter) are in the same driver (which makes it easier to pass data)
> or are in separate drivers, in which case you need to use device interfaces,
> control devices, or ex callbacks.
>
> d
>
> --
> Please do not send e-mail directly to this alias. this alias is for
> newsgroup purposes only.
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
> "Jeroen Koeter" <j_koeter@hotmail.com> wrote in message
> news:OfaL$diuGHA.5056@TK2MSFTNGP06.phx.gbl...
> > Hi all,
> >
> > Currently I am looking for an API that gives me access to the LLC and PHY
> > registers on my 1394 board. I need this because I want to be able to read
> > the type/version information from these chips since some work better than
> > others. It seems that there is no such functionality in the 1394.h
> > headerfile that ships with the DDK.
> >
> > I have done such a thing before, but then I did it the hard (and ugly?)
> > way:
> > - scan the PCI bus for the 1394 board
> > - Use the PCI interface to access the LLC chip.
> > - Access the PHY trough the LLC chip.
> >
> > I think this is not really thread safe because I have to set the page
> > registers in the PHY, which can be altered in between by the port driver.
> >
> > So, the question is, does anybody know a (more) neat way to do this? Any
> > suggestions will be appreciated.
> >
> > Best regards, Jeroen.
> >