* udev rule for a 1394 port on a video card?
@ 2006-05-22 17:10 sean
2006-05-22 18:11 ` sean darcy
2006-06-01 12:32 ` Kay Sievers
0 siblings, 2 replies; 3+ messages in thread
From: sean @ 2006-05-22 17:10 UTC (permalink / raw)
To: linux-hotplug
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.
find /dev -name "*1394*" returns nil.
ohci1394 and ieee1394 drivers ( but not raw1394 ) are loaded:
lsmod | grep 1394
ohci1394 71961 0
ieee1394 411865 1 ohci1394
So I used udevinfo to create some rules:
cat /etc/udev/rules.d/09-ieee1394.rules
KERNEL="fw-host0" , SYMLINK="dv1394"
BUS="ieee1394" , SYSFS{vendor_name_kv}="Linux - ohci1394",
SYSFS{vendor_oui}="ATI Technologies Inc.", NAME="%k",
SYMLINK="dv1394"
ran udevtrigger again. Still no dv1394.
How do I get dv1394 created? How do I get the raw1394 loaded?
FWIW:
udevinfo -a -p /sys/class/ieee1394_host/fw-host0
.............................
looking at device '/class/ieee1394_host/fw-host0':
KERNEL="fw-host0"
SUBSYSTEM="ieee1394_host"
looking at device
'/devices/pci0000:00/0000:00:0b.0/0000:01:00.1/0000:02:00.0/fw-host0':
ID="fw-host0"
BUS="ieee1394"
DRIVER=""
SYSFS{is_busmgr}="0"
SYSFS{is_irm}="1"
SYSFS{is_cycmst}="1"
SYSFS{is_root}="1"
SYSFS{in_bus_reset}="0"
SYSFS{nodes_active}="1"
SYSFS{selfid_count}="1"
SYSFS{node_count}="1"
looking at device
'/devices/pci0000:00/0000:00:0b.0/0000:01:00.1/0000:02:00.0':
ID="0000:02:00.0"
BUS="pci"
DRIVER="ohci1394"
SYSFS{modalias}="pci:v000011C1d00005811sv00001002sd00005811bc0Csc00i10"
SYSFS{local_cpus}="00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000001"
SYSFS{irq}="193"
SYSFS{class}="0x0c0010"
SYSFS{subsystem_device}="0x5811"
SYSFS{subsystem_vendor}="0x1002"
SYSFS{device}="0x5811"
SYSFS{vendor}="0x11c1"
looking at device
'/devices/pci0000:00/0000:00:0b.0/0000:01:00.1':
ID="0000:01:00.1"
BUS="pci"
DRIVER=""
SYSFS{modalias}="pci:v00001002d00004243sv00000000sd00000000bc06sc04i00"
SYSFS{local_cpus}="00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000001"
SYSFS{irq}="0"
SYSFS{class}="0x060400"
SYSFS{subsystem_device}="0x0000"
SYSFS{subsystem_vendor}="0x0000"
SYSFS{device}="0x4243"
SYSFS{vendor}="0x1002"
................
sean
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x120709&bid&3057&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
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: udev rule for a 1394 port on a video card?
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
1 sibling, 0 replies; 3+ messages in thread
From: sean darcy @ 2006-05-22 18:11 UTC (permalink / raw)
To: linux-hotplug
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:
>
> Always include version numbers!
>
kernel-2.6.17-rc4
udev-0.92
<feeling somewhat stupid>
> > 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
> And run:
> udevmonitor --env
>
> do:
> echo add > /sys/bus/ieee1394/devices/0006bb0016051a55-0/uevent
> (repeat for all devices you mentioned above)
>
> and copy the output of udevmonitor.
>
> If you find a "dev" file there should be MAJOR/MINOR in the udevmonitor
> output, if not, the driver needs to be fixed.
>
> Kay
>
Since there are no "dev" files it's probably not a surprise
udevmonitor showed no MAJOR/MINOR numbers:
UEVENT[1148320025.647790] add@/class/ieee1394/0006bb0016051a55-0
ACTIONd
DEVPATH=/class/ieee1394/0006bb0016051a55-0
SUBSYSTEM=ieee1394
SEQNUM!40
PHYSDEVPATH=/devices/pci0000:00/0000:00:0b.0/0000:01:00.1/0000:02:00.0/fw-host0/0006bb0016051a55/0006bb0016051a55-0
PHYSDEVBUS=ieee1394
VENDOR_ID\00000
MODEL_ID\00000
GUID\006bb0016051a55
SPECIFIER_ID\0005e
VERSION\00001
MODALIAS=ieee1394:ven00000000mo00000000sp0000005Ever00000001
UEVENT[1148320025.648263] add@/class/ieee1394_node/0006bb0016051a55
ACTIONd
DEVPATH=/class/ieee1394_node/0006bb0016051a55
SUBSYSTEM=ieee1394_node
SEQNUM!41
PHYSDEVPATH=/devices/pci0000:00/0000:00:0b.0/0000:01:00.1/0000:02:00.0/fw-host0/0006bb0016051a55
PHYSDEVBUS=ieee1394
UEVENT[1148320025.648692] add@/class/ieee1394_host/fw-host0
ACTIONd
DEVPATH=/class/ieee1394_host/fw-host0
SUBSYSTEM=ieee1394_host
SEQNUM!42
PHYSDEVPATH=/devices/pci0000:00/0000:00:0b.0/0000:01:00.1/0000:02:00.0/fw-host0
PHYSDEVBUS=ieee1394
So the *1394 drivers need to be fixed? I'll post to the 1394 list.
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?
Thanks for the help.
sean
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd_______________________________________________
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: udev rule for a 1394 port on a video card?
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
1 sibling, 0 replies; 3+ messages in thread
From: Kay Sievers @ 2006-06-01 12:32 UTC (permalink / raw)
To: linux-hotplug
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2006-06-01 12:32 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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).