linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: /dev question
Date: Sun, 13 Mar 2005 19:16:59 +0000	[thread overview]
Message-ID: <1110741419.4999.44.camel@localhost.localdomain> (raw)
In-Reply-To: <79B99414.46BBE1A5.001775B0@cs.com>

On Sun, 2005-03-13 at 14:02 -0500, Jachete@cs.com wrote:
> Hello,
> 
> i am very new to the linux world, but would like to use my AMD64 powered linux (Ubuntu) box to edit video.
> 
> Both Cinelerra and Kino require /dev/raw1394 and /dev/dv1394, but these are not present on my system. 
> 
> Can anyone tell me how to make these present at boot time, so that I don't have to fight so hard any more?

The kernel driver does not create sysfs entries for that device and
therefore udev will do nothing here. This was already implemented for
the 1394 drivers the last time I looked in their CVS, but I don't know
if it is already merged into the mainline kernel. 

For now just do:
  mknod /dev/raw1394 c 171 0
  mknod /dev/dv1394 c 171 32

You may read this:
  http://ubuntuforums.org/showthread.php?t'92

Good luck,
Kay



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

      parent reply	other threads:[~2005-03-13 19:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-13 19:02 /dev question Jachete
2005-03-13 19:09 ` Todd Musall
2005-03-13 19:16 ` Kay Sievers [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=1110741419.4999.44.camel@localhost.localdomain \
    --to=kay.sievers@vrfy.org \
    --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).