Hi James,
- For two devices with same type (say two harddisks, SBP-2 support), do I
have to create two unit directory for each device or just one unit
directory
for two devices?
I donot understand this question.
doesn’t your SBP harddisk contain a unit directory for SBP-2.
Each harddisk must have a unit directory each for SBP-2. I mean here the
unit directory should be in CSR space of the HDD.
So if you have 2 Hdds, each HDDs config Rom should contain a unit directory
for SBP-2.
- If I put two Logical_Unit_Number entries for two harddisks under one
same
Unit Directory, how many PDOs will be created?
I donot think MS’s 1394 bus driver currently will enumerate it into 1 pdo
only.
Could you also tell me what info the system use to load the driver (my
very
first question)?
I donot remember , but I think 1394 bus enumerator does uses the unit spec
id & unit software version
you can better look at the enum\1394 key in registry to see exactly.
Regards
Jeseem
mailto:xxxxx@hotmail.com
----- Original Message -----
From: “Zhou, James”
To: “NT Developers Interest List”
Sent: Wednesday, September 06, 2000 9:26 PM
Subject: [ntdev] RE: [ntdev]1394 driver loading
> Hi Jeseem,
>
> Thank you very much for the help.
>
> I need your help to clarify the following.
>
> 1. For two devices with same type (say two harddisks, SBP-2 support), do I
> have to create two unit directory for each device or just one unit
directory
> for two devices?
>
> 2. If I put two Logical_Unit_Number entries for two harddisks under one
same
> Unit Directory, how many PDOs will be created?
>
> Could you also tell me what info the system use to load the driver (my
very
> first question)?
>
> Thanks a lot
>
> James
>
> -----Original Message-----
> From: Jeseem [mailto:xxxxx@hotmail.com]
> Sent: Thursday, September 07, 2000 3:55 AM
> To: NT Developers Interest List
> Subject: [ntdev] RE: [ntdev]1394 driver loading
>
>
> The 1394 bus driver create a pdo for each unit directory.
> So if you have 2 unit directories you will have 2 PDOs.
>
> If you have 2 hardisks having same unit directories, two pdo of same type
> will be enumerated.
>
> If you have a device with 2 different unit directories, say 1 for 1394
> another for 61883,
> then 2 different pdos will be enumerated. It is possible for you to have 2
> different drivers to handle these different PDOs.
>
> So in short a unit directory of 1394 is considered as a logical device for
> windows.
>
> regards
> jeseem
> mailto:xxxxx@hotmail.com
>
> ----- Original Message -----
> From: “Zhou, James”
> To: “NT Developers Interest List”
> Sent: Wednesday, September 06, 2000 2:43 AM
> Subject: [ntdev] RE: [ntdev]1394 driver loading
>
>
> > One more question:
> >
> > If my 1394 contains two logical units that belong to same type, for
> > instance, two IDE hard disks, how may time will the driver be loaded? Or
> in
> > another words, how many PDOs will be created for this 1394 device?
> >
> > Thanks
> >
> > James
> >
> > -----Original Message-----
> > From: Zhou, James [mailto:xxxxx@asia.adaptec.com]
> > Sent: Wednesday, September 06, 2000 5:34 PM
> > To: NT Developers Interest List
> > Subject: [ntdev] [ntdev]1394 driver loading
> >
> >
> > Hi,
> >
> > I am new to 1394 driver and I just started working on a driver for SBP-2
> > device. Can any body tell what information Windows needs from a 1394
> device
> > to load a driver for it? I.e., in addition to vendor ID, what else is
> > needed? ChipID in InfoBlock? unit_spec_id? unit_sw_version? or
> > unit_unique_ID leaf?
> >
> > Thanks in advance
> >
> > James
> >
> > —
> > You are currently subscribed to ntdev as: xxxxx@asia.adaptec.com
> > To unsubscribe send a blank email to $subst(‘Email.Unsub’)
> >
> > —
> > You are currently subscribed to ntdev as: xxxxx@hotmail.com
> > To unsubscribe send a blank email to $subst(‘Email.Unsub’)
> >
> >
>
> —
> You are currently subscribed to ntdev as: xxxxx@asia.adaptec.com
> To unsubscribe send a blank email to $subst(‘Email.Unsub’)
>
> —
> You are currently subscribed to ntdev as: xxxxx@hotmail.com
> To unsubscribe send a blank email to $subst(‘Email.Unsub’)
>
>