From: Oliver Neukum <Oliver.Neukum@lrz.uni-muenchen.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: 1394 SPB-2 Drives
Date: Fri, 19 Jan 2001 08:48:35 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-97989400419118@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-97987128314570@msgid-missing>
> > As there are a lot of device on a firewire bus, it probably can't use the
> > pseudo host controller hack. And shouldn't - it's a hack, which is
> > unfortunately necessary for usb.
>
> I don't know where that came from, but notice I never said
> anything about such stuff. In fact, neither does the firewire
> code I glanced at -- Initiator/Target is the terminology.
That's from usb-storage. It's the only currently working way
to get a device that uses the scsi command set to support
hotplugging.
>
> > At present hotplugging in this driver sucks and will continue to
> > do so until the scsi subsystem is extended.
>
> I didn't see any hooks to scsi in drivers/ieee1394, so this also
> seems unrelated to the basic hotplug checklist I gave. Perhaps
> you're referring to a specific driver that's not in that directory
> of generic 1394 code?
I was referring to the SPB-2 subclass of ieee1394 devices which like
usb-storage use the scsi command set. The driver for them indeed
is not part of the standard kernel. These disks (and scanners) are
the hardest case. If they work everything works in terms of hotplugging.
> > Even then for configuration there's a need to further support.
> > The raw news about a device is of little use. You need the information
> > about partitions and other things.
>
> Once the bus code has hotplugged a disk-style device so that a block
> device driver is hooked in, then yes -- then you need partition info.
>
> But that's pretty late in the game, and can't apply to devices like
> video cameras or a VCR.
Exactly. Hotplugging for those already worksaccording to the statius page of
1394. Disks are the hard part.
And while we are discussing ieee1394, how does Linux support use of that bus
as a LAN ?
Regards
Oliver
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2001-01-19 8:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-19 2:29 1394 SPB-2 Drives David Brownell
2001-01-19 8:48 ` Oliver Neukum [this message]
2001-01-19 14:44 ` Mark Knecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-linux-hotplug-97989400419118@msgid-missing \
--to=oliver.neukum@lrz.uni-muenchen.de \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).