From: Robert Longbottom <rongblor@googlemail.com>
To: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: Conexant PCI-8604PW 4 channel BNC Video capture card (bttv)
Date: Tue, 11 Feb 2014 18:25:17 +0000 [thread overview]
Message-ID: <52FA6B0D.6080706@googlemail.com> (raw)
In-Reply-To: <20140211133805.GA26402@minime.bse>
[-- Attachment #1: Type: text/plain, Size: 2104 bytes --]
On 11/02/14 13:38, Daniel Glöckner wrote:
> On Wed, Feb 05, 2014 at 01:16:53PM +0000, Robert Longbottom wrote:
>> On 28 Jan 2014, at 02:02 AM, Daniel Glöckner <daniel-gl@gmx.net> wrote:
>>> When we cycle through all combinations in one minute, there are about
>>> a hundred PCI cycles per combination left for the chip to be granted
>>> access to the bus. I expect most of the pins to provide a priority
>>> or weighting value for each BT878A, so there should be many combinations
>>> that do something.
>>
>> How difficult is it for me to do this? And is it obvious when it works?
>> I have an old pc that I can put the card in that doesn't matter. And given
>> I can't get the card to work in windows or Linux its not much use to me as
>> it is, so if it breaks then so be it.
>>
>> I've not done any Linux driver development, but I'm happy enough compiling
>> stuff for the most part.
>
> Try the attached program. It must be linked with -lrt. It will set all 24
> GPIOs of that one chip to output. The output file contains one nibble
> per GPIO combination with each bit representing one of the BT878.
>
> In my tests with a single BT878 the 10us delay sometimes was not enough
> for the RISC PC to advance. It should be enough to recognize a pattern,
> though.
>
> Daniel
>
>
> DMA from userspace... I feel dirty...
Neat, thanks, I'm impressed you took the time to implement %-complete
messages :-) And glad you did because it took a while to run, about 15
mins and seemed to go slower in the middle, so slow I thought it had died.
I ran it without anything else running, with no video inputs plugged
into the card and with the bttv module loaded with no additional options
- i.e. I just let it use the autodetect on the card. Let me know if I
should have plugged something in, or specified some module options and
I'll try that.
The output is attached - I've gzip'd it because it was 8Mb and I didn't
want to send something that big to the whole list, but I guess it might
not get through.
I hope it means something to you because it doesn't mean anything to me :-)
Thanks,
Rob.
[-- Attachment #2: out.txt.gz --]
[-- Type: application/gzip, Size: 114657 bytes --]
prev parent reply other threads:[~2014-02-11 18:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 21:39 Conexant PCI-8604PW 4 channel BNC Video capture card (bttv) Robert Longbottom
2014-01-20 22:55 ` Andy Walls
2014-01-21 9:27 ` Robert Longbottom
2014-01-21 10:19 ` Daniel Glöckner
2014-01-21 19:49 ` Robert Longbottom
2014-01-21 20:59 ` Robert Longbottom
2014-01-22 11:53 ` Daniel Glöckner
2014-01-22 13:09 ` Robert Longbottom
2014-01-22 13:50 ` Daniel Glöckner
2014-01-22 18:15 ` Robert Longbottom
2014-01-23 13:27 ` Daniel Glöckner
2014-01-23 14:29 ` Robert Longbottom
2014-01-25 15:23 ` Daniel Glöckner
2014-01-26 11:21 ` Robert Longbottom
2014-01-26 12:55 ` Daniel Glöckner
2014-01-26 16:23 ` Robert Longbottom
2014-01-27 3:20 ` Daniel Glöckner
2014-01-27 20:55 ` Robert Longbottom
2014-01-28 2:02 ` Daniel Glöckner
2014-02-05 13:16 ` Robert Longbottom
2014-02-11 13:38 ` Daniel Glöckner
2014-02-11 18:25 ` Robert Longbottom [this message]
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=52FA6B0D.6080706@googlemail.com \
--to=rongblor@googlemail.com \
--cc=linux-media@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.