Thread: a general question
Brought to you by:
aeb,
bencollins
From: Mark <to...@to...> - 2000-11-30 08:53:59
|
Is an AMD k6/2-300 too slow to capture data? I have a 7200 rpm IDE drive using DMA, and I still seem to drop about 4 frames per second. Has anyone gotten capture to work on a comparable computer? Here are the specs: 300 mhz 64 megs OHCI PCI firewire card 40 gig 7200 rpm drive Also: the kernel reports both my drives to be using DMA, but when i turn off DMA, i do not notice any difference in hard drive r/w speed tests. Maybe the kernel thinks its using DMA? Any ideas? Also, I am curious how many of you guys do your editing in linux, and what program you use to edit. Thanks, Mark to...@de... |
From: Yuval D. <yu...@sl...> - 2007-04-08 12:18:33
|
Hi all, If for example, a node gets a read request to its ROM space, is it handled by hardware or software? i.e, is that packet brought up to any sw level. Can anyone describe the sw/hw partitioning in linux 1394 system? =20 Thanks,=20 Yuval Dafni.=20 |
From: Stefan R. <st...@s5...> - 2007-04-08 20:42:12
|
Yuval Dafni wrote: > If for example, a node gets a read request to its ROM space, is it > handled by hardware or software? i.e, is that packet brought up to any > sw level. Can anyone describe the sw/hw partitioning in linux 1394 > system? If the PC's link layer controller is an OHCI compliant controller (by far most are), then there are some address ranges handled solely by hardware and the rest handled by software. See OHCI 1.1 section 1.5. "Physical request/ physical response unit" means: Only hardware is at work, no interrupts are generated. To handle read or write requests by software (driver software or application programs), the software has to install an address range mapping (ARM in Linux 1394 lingua). This mapping consists of a memory buffer which is backing the address range or/and a callback which generates responses. -- Stefan Richter -=====-=-=== -=-- -=--- http://arcgraph.de/sr/ |
From: Matteo M. <mat...@ti...> - 2000-11-30 11:16:52
|
Hi, please read comments in your message's body: Mark wrote: > Is an AMD k6/2-300 too slow to capture data? I have a 7200 rpm IDE drive > using DMA, and I still seem to drop about 4 frames per second. Has anyone > gotten capture to work on a comparable computer? Here are the specs: > > 300 mhz > 64 megs > OHCI PCI firewire card > 40 gig 7200 rpm drive > I drop no frames at all on my k6/2-300 160 Mb RAM, OHCI PCI firewire card, 8G 5400 rpm crappy ide drive. :-) > > Also: the kernel reports both my drives to be using DMA, but when i turn > off DMA, i do not notice any difference in hard drive r/w speed > tests. Maybe the kernel thinks its using DMA? Any ideas? > Could you please be more specific? What is your mobo chipset? > > Also, I am curious how many of you guys do your editing in linux, and what > program you use to edit. > Count me; I use bcast2000. > > Thanks, > > Mark > to...@de... > Bye, Matteo |
From: Dan D. <dde...@co...> - 2000-11-30 14:25:05
|
Hi Mark, I saw Matteo's response, which tells you that your hardware should be sufficient. I have an AMD K6-2 333, but I use only ultra scsi. There was a recent fix (about 2 weeks ago?) to the OHCI driver to fix a bug that was causing dropped frames with dvgrab and causing the drivers from not unloading as modules. You should download to the very latest drivers from CVS, and try again. I have written a variation of dvgrab that uses video1394's DMA routines that offers some performance benefit. This is not currently planned to appear directly in dvgrab. Instead, we are exploring ways to build the routine into libraw1393 and video1394 so it is more transparant to applications. That will make it easier to provide the performance boost to bcast2000, the app that really needs all the performance it can get due to MPEG encoding and preview monitoring. I'm not really doing editing yet because I first want to a way to record back my dv camera. I am currently working on this along with the author of dvgrab. Hopefully, we will have this working by the end of the year. Arne Schirmacher, author of dvgrab, wrote a little editor called Kino that's like vi for video editing. I am interested in this because I am building a home theater PC that I want to use for basic editing of home videos. I have this great little RF wireless mouse, and I want to hook up its control codes to Kino's commands to do full screen video editing because a timeline gui is too akward for TV resolution and a remote control mouse. To really make this happen, though, I also need to make Kino leverage Xv extensions with my Matrox card to get the performance of video overlay. Last nite, I wrote a little program to dump uncompressed video from my iBot into a window using Xv. It's almost working, so all of this looks feasible and reasonable in the near term. ----- Original Message ----- From: "Mark" <to...@to...> To: <lin...@li...> Sent: Thursday, November 30, 2000 3:57 AM Subject: a general question > Is an AMD k6/2-300 too slow to capture data? I have a 7200 rpm IDE drive > using DMA, and I still seem to drop about 4 frames per second. Has anyone > gotten capture to work on a comparable computer? Here are the specs: > > 300 mhz > 64 megs > OHCI PCI firewire card > 40 gig 7200 rpm drive > > Also: the kernel reports both my drives to be using DMA, but when i turn > off DMA, i do not notice any difference in hard drive r/w speed > tests. Maybe the kernel thinks its using DMA? Any ideas? > > Also, I am curious how many of you guys do your editing in linux, and what > program you use to edit. > > Thanks, > > Mark > to...@de... > > > _______________________________________________ > mailing list Lin...@li... > http://lists.sourceforge.net/mailman/listinfo/linux1394-user > |
From: Dan D. <dde...@co...> - 2000-11-30 14:25:22
|
Hi Mark, I saw Matteo's response, which tells you that your hardware should be sufficient. I have an AMD K6-2 333, but I use only ultra scsi. There was a recent fix (about 2 weeks ago?) to the OHCI driver to fix a bug that was causing dropped frames with dvgrab and causing the drivers from not unloading as modules. You should download to the very latest drivers from CVS, and try again. I have written a variation of dvgrab that uses video1394's DMA routines that offers some performance benefit. This is not currently planned to appear directly in dvgrab. Instead, we are exploring ways to build the routine into libraw1393 and video1394 so it is more transparant to applications. That will make it easier to provide the performance boost to bcast2000, the app that really needs all the performance it can get due to MPEG encoding and preview monitoring. I'm not really doing editing yet because I first want to a way to record back my dv camera. I am currently working on this along with the author of dvgrab. Hopefully, we will have this working by the end of the year. Arne Schirmacher, author of dvgrab, wrote a little editor called Kino that's like vi for video editing. I am interested in this because I am building a home theater PC that I want to use for basic editing of home videos. I have this great little RF wireless mouse, and I want to hook up its control codes to Kino's commands to do full screen video editing because a timeline gui is too akward for TV resolution and a remote control mouse. To really make this happen, though, I also need to make Kino leverage Xv extensions with my Matrox card to get the performance of video overlay. Last nite, I wrote a little program to dump uncompressed video from my iBot into a window using Xv. It's almost working, so all of this looks feasible and reasonable in the near term. ----- Original Message ----- From: "Mark" <to...@to...> To: <lin...@li...> Sent: Thursday, November 30, 2000 3:57 AM Subject: a general question > Is an AMD k6/2-300 too slow to capture data? I have a 7200 rpm IDE drive > using DMA, and I still seem to drop about 4 frames per second. Has anyone > gotten capture to work on a comparable computer? Here are the specs: > > 300 mhz > 64 megs > OHCI PCI firewire card > 40 gig 7200 rpm drive > > Also: the kernel reports both my drives to be using DMA, but when i turn > off DMA, i do not notice any difference in hard drive r/w speed > tests. Maybe the kernel thinks its using DMA? Any ideas? > > Also, I am curious how many of you guys do your editing in linux, and what > program you use to edit. > > Thanks, > > Mark > to...@de... > > > _______________________________________________ > mailing list Lin...@li... > http://lists.sourceforge.net/mailman/listinfo/linux1394-user > |