From: vinai <vroopcha@mcw.edu>
To: Debian PowerPC List <debian-powerpc@lists.debian.org>,
"LinuxPPC Developers' List" <linuxppc-dev@ozlabs.org>
Cc: ivtv-devel@ivtvdriver.org
Subject: ivtv 0.4.2 driver works on powerpc !!
Date: Thu, 26 Jan 2006 23:24:02 -0600 (CST) [thread overview]
Message-ID: <Pine.OSX.4.62.0601262228470.3234@romy.local> (raw)
Hi Folks,
Don't know if this has been made widely known, but I thought I's share
the last couple of days worth of experimenting.
The setup - a PowerMac 8500, running "stock" Debian testing except for
my own kernel compiled from the 2.6.15.1 sources from kernel.org. The
machine has 1 G RAM, 200 MHz 604e PowerPC CPU and a Firmtek SATA drive
controller running a 36 G 10K WD Raptor drive, and the capture device
under testing is a Hauppage 350 PCI card.
In my kernel .config file, I have video4linux and I2C support enabled,
as per the instructions on the ivtv web site. I built and used only
hardware modules from the ivtv 0.4.2 sources. I grabbed the firmware
and installed it, again per instructions.
If I do:
cat /dev/video0 > test.mpg
after a reboot, the hardware won't respond. However, if I remove the
ivtv module then do a modprobe of that module again, the above command
will work. "modprobe"-ing without "rmmod"-ing did not allow the card
to function.
I was able to capture about 20 s of video, with no noticeable dropped
frames, even on this slow machine. This machine can't even play the
captured clips, but transfer to another machine gave me a valid and
playable MPEG-2 file. I plan to do some more testing over the next
few days, and see if I can get this to actually work predictably...
Cheers, and thanks to all whose work and efforts made this happen !!
cheers
vinai
reply other threads:[~2006-01-27 5:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.OSX.4.62.0601262228470.3234@romy.local \
--to=vroopcha@mcw.edu \
--cc=debian-powerpc@lists.debian.org \
--cc=ivtv-devel@ivtvdriver.org \
--cc=linuxppc-dev@ozlabs.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).