Georgi,
Thanks for replying. I apologize for getting back so late, but Xmas has
been consuming my time.
I really would like to understand this logic. I'm trying to help this guy
put a "part4" block device in the right location on his system so his Zip
drive works correctly and because he has both host0 and host2 sub-directories
under /dev/ide, I'm not sure where to locate it.
If you or anyone else finds a document explaining the "hostx" business, I
sure would appreciate a link to it's location.
Thanks again,
Robert
On Friday 13 December 2002 2:02 pm, you wrote:
> I read somewhere that host0 and host1 are assigned for on-board IDE
> interfaces, and IDE controllers on PCI slots receive host2 and up.
>
> I was a little surprised myself, when the IDE controller I bought recently
> became host2...
>
> Robert wrote:
> > Hello,
> > I'm trying to understand the structure of host0, host1, host2, etc in
> > regards to IDE devices. I did read Richards FAQ, and he did discuss
> > this for scsi devices, but I didn't see the logic explained for the IDE
> > devices or whatever determines the host# scheme. ( ...or it was in
> > there, but I didn't understand it ) If someone could explain this, I
> > sure would appreciate it.
> >
> > In regards to the /bus#/target# logic, maybe someone could confirm my
> > understanding of this as well as I have listed below.
> >
> > /bus0/target0 = primary master
> > /bus0/target1 = primary slave
> > /bus1/target0 = secondary master
> > /bus1/target1 = secondary slave.
> >
> > I'm trying to get this fellows internal zip drive working on his
> > system, but because he has a different HD and Zip configuration off his
> > IDE slots than I do, it's necessary I understand how to figure this out
> > so I can get his block device (part4) in the right place for his system.
> >
> > Thanks,
> > Robert
|