Skip site navigation (1)Skip section navigation (2)
Date:      29 Jun 1999 12:04:04 +0200
From:      Frode Vatvedt Fjeld <frodef@acm.org>
To:        freebsd-multimedia@freebsd.org
Subject:   Re: bt848 channel frequencies
Message-ID:  <2h9093s4q3.fsf@dslab7.cs.uit.no>
In-Reply-To: Roger Hardiman's message of "Tue, 29 Jun 1999 04:09:59 %2B0100"
References:  <19990627074316.A1600@ipass.net> <199906272257.QAA07116@orthanc.ab.ca> <19990627194019.A1726@ipass.net> <2hzp1ksk05.fsf@dslab7.cs.uit.no> <37783907.94141BC7@cs.strath.ac.uk>

next in thread | previous in thread | raw e-mail | index | archive | help
Roger Hardiman <roger@cs.strath.ac.uk> writes:
> a) select()-able. Can you explain a bit mode.

I want to use select(2) in order to wait for an frame (well, a field
actually) instead of the current signal interface.

> b) module-cabable. Do you mean KLDs (the new version of LKMs).  Then
> the bt848 driver in -current was converted to a loadable module 2
> weeks ago.

That's good news! Now I just need to switch from -stable to -current
(I'm very unhappy about the stability of -stable anyways, so that's no
loss).

> c) meteor interface.
> I have meteor cards too, and I quite like the common interface.  I
> can see a few places where it holds us back like having different
> capture sizes for even and odd fields.  But if we adopt a new API,
> it should be V4L2 based.

It's not that the drivers share some of the interface in itself that
is the problem, but when there is stuff like "compatibility modes" in
the bktr driver, something is wrong. I have plenty of trouble with the
bktr driver, and I can't (don't want to) look at such code to figure
things out.

V4L2 does at least seem better to me than anything else out there.

-- 
Frode Vatvedt Fjeld


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-multimedia" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2h9093s4q3.fsf>