From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: 1394 SPB-2 Drives
Date: Fri, 19 Jan 2001 02:29:16 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-97987128314570@msgid-missing> (raw)
Mark --
> So, I think part of the issue here is that the 1394 stack is going to
> have a fairly low level part that is handling the hardware part of notifying
> the system that something has happened. Above that the 1394 stack will
> probably need to let the hot plugging system know about certain device
> changes, but possibly not about all devices. Do you see this software being
> responsible when I plug in 1394 printers, cameras, speakers, home theatre
> equipment, as well as disk drives? I'm not clear...
Yes, I see that stack handling all such notifications because, as you noted,
1394 is more USB-like than SCSI-like when it comes to hotplugging. More
different kinds of device; isochrony; and so on. Very much in particular,
disks aren't the "typical 1394" device (I think of video :-).
Oliver --
> 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.
> 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?
> 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.
- Dave
_______________________________________________
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 reply other threads:[~2001-01-19 2:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-19 2:29 David Brownell [this message]
2001-01-19 8:48 ` 1394 SPB-2 Drives Oliver Neukum
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-97987128314570@msgid-missing \
--to=david-b@pacbell.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.