Blocking non-polling capture is the one to use for most applications. I have developed a simple patch for raw that I am just beginning to test that addresses the raw security issue in a way completely different than Jody’s proposal. I still think that a USB-alike device node for each interface on each device is the right solution; then we can assign groups and permissions on a per-interface or per-device level. For many of the recent releases both the firewire stacks have been available, but the older one selected by default. I read that that is expected since the firewire The Linux kernel can be configured to use various process prioritization strategies, for example.

Uploader: Nir
Date Added: 28 October 2005
File Size: 12.8 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 34147
Price: Free* [*Free Regsitration Required]

Want to know if that peripheral is compatible with Linux? Robert Petersen robert-konweb wrote on The new driver stack ‘juju’ has become the default driver from kernel 2. I’ll be happy to be more precise, if this is of interest in this forum, but I can survive in the current situation.

I don’t know if eth works without physical DMA.


Is the firewire port damaged? So what ueee1394 happen is: PS, kino should work out-of-the box on recent Ubuntu versions, using libraw v2. The latter implementation uses the CMU low-level drivers. The best solution at the moment is to create a new group for raw Is it safe to multi-thread with libdc?


If Ubuntu doesn’t automatically create a device node you can force the creation by typing the following in a Terminal: It just doesn’t make sense to give all users complete control for all firewire devices, that’s not how device management is supposed to work in the kernel.

I used to transfer video by firewire a. The bus can handle up to 64 iwee1394 channels.

New versions of Linux drivers kernel 2. It is difficult to weigh that trade-off.

It very likely is most are opto-isolated but you would want to minimize any risk to the camera. Everybody is still holding their breath for a 2. Not all video cards and XFree86 drivers support this feature.

File a bug for the dvgrab package it should be updated to version 2.

If you need to reset your password, click here. Oh well, I will consider changing the Kino default dv device name or simply try a few popular names in addition to the configured name.

I finally got a chance to setup The libdc developers’ list lists. Start Kino and switch to the ‘Capture’ tab. As it was explained to me, it’s possible to construct a Firewire device that “loops back” 4, providing access to the RAM of the machine that originated the requests. Luciky, this represents about Linux’ sbp2 driver does not work correctly without physical DMA at the moment. FireWire is available as wireless, fiber optic and coaxial versions, all using the same protocol.


This is an unacceptable hack too. How does that deal with Stefan’s issue 4?

Bug # “DV capture over Firewire is broken (no rights for /de” : Bugs : kino package : Ubuntu

It is highly advisable to attach the cable when the device and PC are both powered down, and power up the camcorder only when you are ready to start capturing. Did you blacklist dv and video as well? Syslog tells me this I’m capturing in gutsy using dvgrabwhich makes me wonder if the thing is really fixed. Instead of helping upstream to get the raw security issue annd, your only contribution was to create a huge support workload for the various affected upstream projects.