All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dennis Grant" <trog@wincom.net>
To: linux-kernel@vger.kernel.org
Subject: Got DC10+ VFL Video Capture board working
Date: Sun, 01 Dec 102 11:54:41 -0500	[thread overview]
Message-ID: <3dea3f71.59f5.0@wincom.net> (raw)

After much goofing around, I've managed to get a Zoran-based DC10+ video capture
board working with 2.4.20rc4.

Key points: 

1) There doesn't seem to be any way to do this with the vanilla kernel. Trying
to compile in all the VFL devices won't compile (there's a problem with the
bttv driver - and unresolved symbol of some sort) and it seems the zoran driver
is dependant on a module called i2c-old that is only built with the bttv driver?


2) Building the current CVS (which doesn't seem to have been altered in months)
for the driver-zoran project from mjpeg.sourceforge.net produced modules that
worked. A brief visual comparison between them and the .c files in the kernel
source didn't reveal any differences more obvious than some kernel version #ifdefs
in the driver-zoran versions of the drivers - they're the same code, or at least
_very_ similar.

3) I had to build the bttv kernel driver as a module to get the i2c-old.o module
built.

4) I then wrote a rc script that did:

    modprobe i2c-old
    modprobe saa7110
    modprobe adv7175
    modprobe zoran

and this presented the following dmesg output:

i2c: initialized
Zoran ZR36060 + ZR36057/67 MJPEG board driver version 0.9
PCI: Found IRQ 11 for device 00:0e.0
MJPEG[0]: Zoran ZR36067 (rev 2) irq: 11, memory: 0xdd800000
MJPEG[0]: subsystem vendor=0x1031 id=0x7efe
MJPEG[0]: Initializing i2c bus...
saa7110_attach: SAA7110A version 1 at 0x9c, status=0xf0
MJPEG[0]: i2c attach 04
adv7176_attach: adv7176 rev. 1 at 0x56
DC10plus[0]: i2c attach 05
DC10plus[0] card detected
DC10plus[0]: Zoran ZR36060 (rev 1)
MJPEG: 1 card(s) found
MJPEG: using 2 V4L buffers of size 128 KB
DC10plus[0]: Initializing card[0], zr=e0988600
DC10plus[0]: enable_jpg IDLE
DC10plus[0]: Testing interrupts...
DC10plus[0]: interrupts received: GIRQ1:49 queue_state=0/0/0/0
DC10plus[0]: procfs entry /proc/zoran0 allocated. data=e0988600

5) My _guess_ as to what is happening is that:

   a) The zoran/DC10+ stuff depends on the i2c-old code
   b) It also depends on saa7110 and adv7175
   c) When you check the DC10+ option in make config, these dependancies are
not being resolved, and one or more of them don't make it into the kernel when
one attempts to compile DC10+ in monolithic
   d) There may be differences between the driver code in the MJPEG CVS and
the current vanilla kernel

6) As such, to get this working should require:
   a) Sync up the current MJPEG cvs to the current kernel 
   b) Ensure that checking DC10+ gets you:
      i)   i2c-old.o
      ii)  saa7110.o
      iii) adv7175.o
      iv)  zoran.o
   in that order.

Is there someone to carry this forward?

Thanks!

DG



                 reply	other threads:[~2002-12-01 16:50 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=3dea3f71.59f5.0@wincom.net \
    --to=trog@wincom.net \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.