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: udev rule for a 1394 port on a video card?
Date: Thu, 01 Jun 2006 12:32:10 +0000	[thread overview]
Message-ID: <1149165131.3419.44.camel@pim.off.vrfy.org> (raw)
In-Reply-To: <e4srb1$f45$1@sea.gmane.org>

On Mon, 2006-05-22 at 14:11 -0400, sean darcy wrote:
> On 5/22/06, Kay Sievers <kay.sievers@vrfy.org> wrote:
> > On Mon, 2006-05-22 at 13:10 -0400, sean wrote:
> > > I have a radeon dv video card, that has an ieee1394 port.
> > > The kernel finds it:

> > > dmesg | grep 1394
> > > ieee1394: Initialized config rom entry `ip1394'
> > > ohci1394: fw-host0: OHCI-1394 1.0 (PCI): IRQ=[193]
> > > MMIO=[f5000000-f50007ff]  Max Packet=[2048]  IR/IT
> > > contexts=[8/8]
> > > ieee1394: Host added: ID:BUS[0-00:1023]  GUID[0006bb0016051a55]
> > >
> > >
> > >   I'm trying to create /dev/dv1394 , raw1394.
> > >
> > > udev appears to find the port:
> > >
> > > udevtrigger --verbose | grep 1394
> > > /sys/bus/ieee1394/devices/0006bb0016051a55-0
> > > /sys/bus/ieee1394/devices/0006bb0016051a55
> > > /sys/bus/ieee1394/devices/fw-host0
> > > /sys/class/ieee1394/0006bb0016051a55-0
> > > /sys/class/ieee1394_node/0006bb0016051a55
> > > /sys/class/ieee1394_host/fw-host0
> > >
> > > but neither dv1394 or raw1394 are created, and I can't
> > > figure out what devices are created.
> >
> > What does:
> >   ls -l /sys/bus/ieee1394/devices/0006bb0016051a55-0
> >   (repeat for all devices you mentioned above)
> > print? Is there a "dev" file?
> >
>  Nope:
> find /sys/class/ieee1394 -name dev
> find /sys/bus/ieee1394 -name dev

Don't you have: /sys/class/ieee1394_protocol/ ?

> Since there are no "dev" files it's probably not a surprise
> udevmonitor showed no MAJOR/MINOR numbers:

Right, but I think the nodes are expected in ieee1394_protocol.

> So the *1394 drivers need to be fixed?  I'll post to the 1394 list.

Not sure.

> In the mean time, do I manually mknod the /dev/*1394? How does udev
> know to connect this physical device to those /dev files? Or is that
> the drivers' problem?

A device node has a major/minor number, that is passed to the kernel and
the kernel finds the matching driver with that number. Udev itself is
not involved with connecting anything, it just creates the nodes with
the right numbers.

Kay



-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x107521&bid$8729&dat\x121642
_______________________________________________
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:[~2006-06-01 12:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-22 17:10 udev rule for a 1394 port on a video card? sean
2006-05-22 18:11 ` sean darcy
2006-06-01 12:32 ` 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=1149165131.3419.44.camel@pim.off.vrfy.org \
    --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).