From: Oliver Neukum <Oliver.Neukum@lrz.uni-muenchen.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: netdevice problem - 1394 SPB-2 Drives
Date: Thu, 18 Jan 2001 23:18:00 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-97985981220031@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-97984098021600@msgid-missing>
On Thursday 18 January 2001 22:47, David Brownell wrote:
> > How do you guys seeing 1394 disk drives fitting into the hot-plug mix?
>
> Right on top of basic 1394 hotplug support!
>
> The hotplug bus support for PCI and USB is pretty similar ... how well
> do these map to the ieee1394 subsystem?
That's not the issue in this case. SCSI is the problem.
I've looked at that driver. It needs to deal with device addition/removal.
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.
At present hotplugging in this driver sucks and will continue to
do so until the scsi subsystem is extended.
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.
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-18 23:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-18 18:03 netdevice problem - 1394 SPB-2 Drives Mark Knecht
2001-01-18 18:20 ` Greg KH
2001-01-18 18:45 ` Mark Knecht
2001-01-18 18:49 ` Greg KH
2001-01-18 21:47 ` David Brownell
2001-01-18 23:18 ` Oliver Neukum [this message]
2001-01-19 0:22 ` 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-97985981220031@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).