This is probably a basic issue, hopefully easily resolved by someone with more experience than me. (my area is more BSD sys admin, now turned linux home hobbyist)
I'm running a full and fresh install of RH 8.0, kernel 2.4.18-14.
I've also played around with the defaults in .xawtv to no avail. THe person who responded to my original query below indicated that tuner should be set to "tuner=33", but I don't know quite where to set that.
Thank you all for any help you can spare on this.
Jim D.
On Thursday, October 24, 2002, at 08:07 AM, Marius Kotsbak wrote:
On Wed, Oct 23, 2002 at 07:18:48PM -0300, Jim D wrote:I like my Pinnacle PCTV PRO. It installs by just loading the bttv-driver and specifying tuner=33. The radio is not working yet though.Hello all,I'm running RH 8.0 on a P III 500 mhz, 320 ram, on-board video card. Could anyone suggest a TV tuner card that would be a very basic and easy install?
Then use any v4l-compatible program like xawtv or zapping.
One for which I won't have to research the net for
drivers and the appropriate setup configuration, but can simply drop
into a PCI slot, maybe have to run an RPM against for support, and take
a stock X app for TV watching and possibly capture and be ready to run
with.
It all doesn't have to be quite that simple, but close to it would be
great. Thank you all for any assistance you can give on this matter.
Respectfully,
J...etc.
On Wednesday, October 23, 2002, at 07:47 PM, Mark McClelland wrote:
Peter Schlaf wrote:You're probably right about that. Some other things could be added toGerd Knorr wrote:We do need a 'mode' field in v4l2_frequency for that, I think. That
field could also be used for setting spectrum inversion for ATSC,
antenna polarization for sat, etc...
I added a type field to the tuner struct, so we can add support forFor the implementation of selection the antenna polarization and other
ATSC+stuff later. Also plenty of "reserved" fields to v4l2_frequency
...
satellite related switches it is IMHO better to have an own struct,
e.g. struct v4l2_antenna and two ioctl calls for reading and setting
this struct. This would make the API more cleaner.
that struct too, like rotator control. I think we should wait until we
have a good selection of hardware to study before adding any of that
to the API, though (the same goes for ATSC for the most part). These
things can be implemented as driver-specific ioctls or even v4l2
controls at first, and then added to the official API once we have
more experience.
--
Mark McClelland
[EMAIL PROTECTED]
_______________________________________________
Video4linux-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/video4linux-list
_______________________________________________ Video4linux-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/video4linux-list_______________________________________________ Video4linux-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/video4linux-list
-- video4linux-list mailing list Unsubscribe mailto:video4linux-list-request@;redhat.com?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/video4linux-list
