linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Knecht <mknecht@controlnet.com>
To: linux-hotplug@vger.kernel.org
Subject: RE: 1394 SPB-2 Drives
Date: Fri, 19 Jan 2001 14:44:58 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-97991574705482@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-97987128314570@msgid-missing>

> > 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.

[MWK] Careful here. I think this means 'hot plugging' as defined by the
folks working on 1394, not 'hotplugging' as defined by the folks working
here. 1394 devices can be added or removed from the 1394 bus and the 1394
driver stack sees it. However, I think that all this stack does so far
is support an interface library above it for small apps to talk to the 
hardware. [PLEASE REMEMBER, I'M NOT A SOFTWARE GUY!!!]

And while we are discussing ieee1394, how does Linux support use of that bus

as a LAN ?

[MWK] There is the beginnings of a TCP/IP Over 1394 driver that works to
some degree, although I have not used it. Last I heard it had to be
installed
as a module, which I personally rebel against being that I'm a newbie to 
Linux and don't know how to do it reliably and automatically! I am quite
interested in this as I have a similar network up and running using Win ME
and would like to replace it one of these days...

	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

_______________________________________________
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

      parent reply	other threads:[~2001-01-19 14:44 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
2001-01-19 14:44 ` Mark Knecht [this message]

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-97991574705482@msgid-missing \
    --to=mknecht@controlnet.com \
    --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).