Re: Cannot configure second Kodicom 4400R

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I realized that my command line was wrong.  Stupid me.
xawtv -c /dev/videox
where x = 0 to 7

That worked.
I will go away now!

On Sat, Oct 15, 2011 at 8:15 PM, Allan Macdonald
<allan.w.macdonald@xxxxxxxxx> wrote:
> On Tue, Oct 11, 2011 at 12:37 PM, Allan Macdonald
> <allan.w.macdonald@xxxxxxxxx> wrote:
>> On Mon, Oct 10, 2011 at 5:17 PM, Patrick Dickey <pdickeybeta@xxxxxxxxx> wrote:
>>> Hi there Allan,
>>>
>>> I'm not familiar with the card (so you'll want to defer to someone else
>>> if their answer differs from mine).  It looks like video0 and video1 are
>>> assigned to the first card, and video2 and video3 are assigned to the
>>> second card.  So, you might want to try
>>>
>>> xawtv -d /dev/video2'
>>>
>>> or
>>>
>>> xawtv -d /dev/video3
>>>
>>> and see if one of those uses the second card (you could try video4 or
>>> video5 also, since they're assigned to cards).
>>>
>>> Have a great day:)
>>> Patrick.
>>>
>>> On 10/10/2011 01:45 PM, Allan Macdonald wrote:
>>>> Hi to all,
>>>>
>>>> I am new to this list.
>>>>
>>>> I have been successfully using a Kodicom 4400R with zoneminder but I
>>>> wanted to expand so I bought a second card and installed it.  The
>>>> problem with this card is that I cannot seem to be able to get the
>>>> second card to work.  I tried using xawtv with the following command:
>>>>
>>>> xawtv -d /dev/video1
>>>>
>>>> The result is that I get images from /dev/video0
>>>>
>>>> I also tried:
>>>>
>>>> xawtv -d /dev/video4
>>>>
>>>> with the same result.
>>>>
>>>> I obviously don't understand what's going on.
>>>>
>>>> I tried following the instructions here, to no avail:
>>>>
>>>> http://www.zoneminder.com/wiki/index.php/Kodicom_4400r
>>>>
>>>> I also looked here:
>>>>
>>>> http://linuxtv.org/wiki/index.php/Kodicom_4400R
>>>>
>>>> but, unfortunately, the following page does not explain what happens
>>>> with more than one card installed.
>>>>
>>>> Here's my bttv.conf:
>>>>
>>>> [code]
>>>> options bttv gbuffers=32 card=133,132,133,133,133,132,133,133 tuner=4
>>>> chroma_agc=1
>>>> [/code]
>>>>
>>>> I have attached a dmesg output and an lsmod output.
>>>>
>>>> I would greatly appreciate some help.  Many thanks in advance.
>>>>
>>>> Regards,
>>>>
>>>> Allan Macdonald
>>>
>>
>> Thanks for your reply, Patrick.  I tried every device from /dev/video0
>> to /dev/video5 and several channel numbers.
>>
>> The wierd thing is that, if I pick video0, I can see inputs 0 - 3.
>>
>> When I select devices video1 - 4, I still see the inputs for video0.
>>
>> To the list:
>>
>> What I'd really like to know is:
>>
>> 1. I had previously assumed that video0 was the first card installed,
>> video1 was the second, etc.  Is this incorrect?  Please clarify.
>>
>> 2. The card is a 4-input card.  I presume these inputs were
>> composite(0) to composite(3).  Am I mistaken here too?  Please
>> clarify.
>>
>> As an educational exercise, (or just plain insanity - you judge!) I
>> have been playing around with the example C code found here:
>>
>> http://linuxtv.org/downloads/v4l-dvb-apis/capture-example.html
>>
>> and inserted the following couple of lines around line 457 (just after
>> the "Select video input" comment)
>>
>>        int index;
>>
>>        index = 0;
>>
>>        if (-1 == ioctl (fd, VIDIOC_S_INPUT, &index)) {
>>                      perror ("VIDIOC_S_INPUT");
>>                      exit (EXIT_FAILURE);
>>        }
>>
>> Questions about this software:
>>
>> 1. I had assumed that, if I wanted the second input on the second
>> card, I would make the index variable equal to 1, compile and  run the
>> program with option -d /dev/video1.  Am I out to lunch?  (I actually
>> made the input number a command-line option but that source is at home
>> and I'm at work now).
>>
>> 2. Also, is the index passed to the VIDIOC_S_INPUT ioctl the same
>> index passed to VIDIOC_QBUF and VIDIOC_DQBUF"?
>>
>> 3. What does the documentation mean by "enqueue" and "dequeue"  I
>> believe to "dequeue" is to cause the driver to transfer a frame from
>> its internal fifo buffer to the destination buffer and move the oldest
>> data pointer to the next oldest item.  Is this correct?  Why does the
>> example program then go and "enqueue" the same data to the same
>> device?
>>
>> I should point out that I don't really know what this program is
>> actually doing... The only thing I can figure is that the program gets
>> frames from the video device and stores them in a ram buffer (assuming
>> default options).  I guess the data is just a big binary blob and
>> another process is required to handle the data in some way (i.e.
>> display it, or whatever).  As you can see, I am totally new at this
>> and some help there would be appreciated as well.  Please help a baby
>> learn to crawl!
>>
>> Cheers,
>> Allan
>>
> Dear Linux Media community,
>
> OK, since I haven't heard from anybody since my last post, maybe this
> additonal info might help pique somebody's interest:
>
> According to the web page,
> http://linuxtv.org/wiki/index.php/Kodicom_4400R, the Kodicom 4400R has
> 4 Conexant BT878A ICs.  Each chip can select one of 16 inputs which
> are routed through via a crosspoint video switch IC (Intersil
> CD22M3494MQ) .  This is controlled by means of the GPIO on the
> “master” BT878A (the “second”, “fifth”, etc. BT878A, according to the
> BTTV driver ).  The crosspoint switch IC has 16 inputs and 4 outputs
> (that’s what the web page says but the CD22M3484 data sheet says the
> chip has 8 outputs, not 4).  The inputs are connected to the camera
> input pins, the 4 BNC inputs shared with the 16 header pins.  The 4
> outputs go to the inputs of the 4 BT878A IC’s.
>
> Of course, the web page doesn’t describe which of the 8 crosspoint
> switch outputs go to which 4 BT878A’s or which GPIO channels are used
> to do this.
>
> Nevertheless, the web page explains that the driver supposedly assigns
> each BT878A one of the device files /dev/video0 to /dev/video3.
> Presumably, a second card should have its 4 BT878A’s assigned to
> /dev/video4 to /dev/video7.  Unfortunately, this is not happening.
>
> Experiments using xawtv:
>
> I tried the following command line
> xawtv /dev/video0
> and selected composite(0) to composite(15) and found the 4 cameras on
> the 4 cards on the first 4 channels, with the remaining channels blank
>
> I then tried every /dev/videoX from /dev/video1 up to /dev/video7 and
> found exactly the SAME results on every device as /dev/video0!  On
> every video device, I found only the first four channels on the first
> card!
>
> This looks very much like a driver problem (it could be a problem with
> xawtv but that seems unlikely since xawtv is probably just using the
> v4l2 api to select the video device and channel).
>
> One might ask if the second card is broken.  If the second card was
> broken, then wouldn't I just see nothing at all from /dev/video4 and
> up?  The driver appears to be assigning the second 4 device files to
> the first card.
>
> Allan
>
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Input]     [Video for Linux]     [Gstreamer Embedded]     [Mplayer Users]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]
  Powered by Linux