P1394 Mail Archive: RE: P1394> Ways to do parameter setup

P1394 Mail Archive: RE: P1394> Ways to do parameter setup

RE: P1394> Ways to do parameter setup

George Chrysanthakopoulos (georgioc@microsoft.com)
Mon, 13 Jul 1998 18:59:42 -0700

once again, pritning should come to terms with the fact that if use the core
sbp2 protocol correctly(even if it means being alittle bit creative without
resorting in bloating with abuncg of regs) it provides enough for you to
work with and create great 1394 implementations.

Device type is command set specifc. we need to see hw.

thanx
g

> -----Original Message-----
> From: Greg Shue [SMTP:gregs@sdd.hp.com]
> Sent: Monday, July 13, 1998 4:41 PM
> To: John Nels Fuller
> Cc: p1394@pwg.org; George Chrysanthakopoulos
> Subject: Re: P1394> Ways to do parameter setup
>
> >
> > Hi everyone,
> >
> > I talked to George C. about the three possible ways we were considering
> for
> > setting connection parameters:
> >
> > 1. Using command-set dependant management commands. There is no way
> > for the class driver to cause the SBP-2 driver to send these, so I guess
> > they are out.
>
> Too bad.
>
> > 2. Using additional registers in the command agent register block.
> > There is no way for the class driver to discover these addresses or to
> > deliver requests directly to the 1394 bus driver, so again no luck.
>
> Oh well.
>
> > 3. Using commands in the normal command stream. This will work (as we
> > knew in Monterey), so we'll have to figure out a way to ensure that the
> in
> > and out queues are both idle when they are issued (but we really needed
> to
> > do that for 1 & 2 as well).
>
> Any progress on getting the Device Type to be dependent on Command_Set?
>
>
> --
> Greg Shue
> Hewlett-Packard Company
> All-in-One Division gregs@sdd.hp.com
> ----------------------------------------------------------------