On Friday 21 January 2005 00:54, Ronald S. Bultje wrote:
> > modprobe zr36067 debug=2 card=0
> You're telling it to recognize the DC10(old). See the docs on
> http://mjpeg.sf.net/driver-zoran/ for how to make it detect as a DC30+.
> Shouldn't make a difference technically, but well, it gives
On Thu, 20 Jan 2005, Steven Boswell II wrote:
> OK, I'm pretty sure I understand this. But
> wouldn't I have to have 4:4:4 data (i.e. 720x480
> chroma data to go along with my 720x480 intensity
You only need 4:2:2 or 4:1:1, something that isn't subsampled vertically. 1:2
or 1:4 horizontal subsa
On Thu, 20 Jan 2005, Steven Boswell II wrote:
> OK, I'm pretty sure I understand this. But
> wouldn't I have to have 4:4:4 data (i.e. 720x480
> chroma data to go along with my 720x480 intensity
> data) in order to fix the chroma properly? Can I
> even get that? Also, when dealing with an NTSC
>If you have a progressive frame in 4:2:0, then
>the first chroma line is the average from lines 1
>and 2. The second chroma line is the average of
>3 and 4.
>
>If you have an interlaced frame, the first chroma
>line is the average of the first two lines of the
>first field. With the fields inter
Hi,
On Thu, 2005-01-20 at 22:58, Koos Pol wrote:
> I have a DC30+. Loading the module with
> modprobe zr36067 debug=2 card=0
[..]
You're telling it to recognize the DC10(old). See the docs on
http://mjpeg.sf.net/driver-zoran/ for how to make it detect as a DC30+.
Shouldn't make a difference t
Hi,
I have a DC30+. Loading the module with
modprobe zr36067 debug=2 card=0
shows the following in the syslog:
kernel: Linux video capture interface: v1.00
kernel: Zoran MJPEG board driver version 0.9.5
kernel: ACPI: PCI interrupt :00:08.0[A] -> GSI 10 (level, low) -> IRQ 10
kernel: MJP
On Thu, 20 Jan 2005, Steven Boswell II wrote:
> Eh? It was my understanding that the lines of the
> top field were stored at even y indices, and the
> lines of the bottom field were stored at odd y
> indices, in the YCbCr data returned by
> y4m_read_frame(). The code for y4m_read_fields()
> certa
>o With 4:2:0 material, you can't just re-label a
>stream from "top-field-first" to "progressive" or
>vice-versa: that will screw up the chroma planes.
Eh? It was my understanding that the lines of the
top field were stored at even y indices, and the
lines of the bottom field were stored at odd y
Err, between this:
>From: Jonathan Black <[EMAIL PROTECTED]>
>Date: Wed, 19 Jan 2005 21:17:08 +0100
>
>On Wed, Jan 19, 2005 at 10:02:45AM -0800, Steven Boswell II wrote:
>> Right before I call yuvkineco, I call yuvcorrect to
>> change bottom-field-interlacing to
>> top-field-interlacing.
On Thu, Jan 20, 2005 at 04:43:49AM -0800, Trent Piepho wrote:
> On Thu, 20 Jan 2005, Michael Hanke wrote:
> > Am Donnerstag 20 Januar 2005 11.09 schrieb Dave Dodge:
> > > Well, yes and no. Installing updated vesions of the autotools is
> > > pretty straightforward if you're used to installing thin
On Thu, 20 Jan 2005, Michael Hanke wrote:
> Am Donnerstag 20 Januar 2005 11.09 schrieb Dave Dodge:
> > On Wed, Jan 19, 2005 at 07:31:45PM -0800, Trent Piepho wrote:
> > > On Wed, 19 Jan 2005, Steven M. Schultz wrote:
> > [...]
> > > Have you tried upgrading autoconf on an old system? It's nearly
Am Donnerstag 20 Januar 2005 11.09 schrieb Dave Dodge:
> On Wed, Jan 19, 2005 at 07:31:45PM -0800, Trent Piepho wrote:
> > On Wed, 19 Jan 2005, Steven M. Schultz wrote:
> [...]
> > Have you tried upgrading autoconf on an old system? It's nearly
impossible.
>
> Well, yes and no. Installing updat
On Wed, Jan 19, 2005 at 07:31:45PM -0800, Trent Piepho wrote:
> On Wed, 19 Jan 2005, Steven M. Schultz wrote:
[...]
> Have you tried upgrading autoconf on an old system? It's nearly impossible.
Well, yes and no. Installing updated vesions of the autotools is
pretty straightforward if you're used
13 matches
Mail list logo
