From: Markus Dahms <mad@automagically.de>
To: Mikael Nousiainen <turja@mbnet.fi>
Cc: linux-mips@linux-mips.org
Subject: Re: New VINO video drivers for Indy
Date: Fri, 15 Jul 2005 13:00:21 +0200 [thread overview]
Message-ID: <20050715110021.GA15740@gaspode.automagically.de> (raw)
In-Reply-To: <42D4BF49.4040907@mbnet.fi>
Hello Mikael,
> I've released new drivers for SGI Indy's VINO video input (for 2.6 kernels).
That's what I've already waited for. Slowly 2.6.x should get usable for
SGI machines :).
> Please test the driver and report the results so that bugs
> (yes, I can promise there are lots of them :) can be squashed.
I only get a bla[nc]k image using the patched camsource or xawtv from
from Debian Sarge with my IndyCam[1] :(. With the old driver for
2.4.x I got some more results (striped, but at least an image...).
I hope you could give me some hints where to start debugging...
| SGI VINO driver version 0.0.1
| VINO with chip ID 11, revision 0 found
| Philips SAA7191 driver version 0.0.1
| SAA7191 initialized
| SGI IndyCam driver version 0.0.1
| IndyCam v1.0 detected
| IndyCam initialized
What I noticed, too:
* you should really include a directory in your package, I (most people?)
did 'cd src/; tar zxvf vino-0.0.1.tar.gz' and screwed up my source
directory a bit.
* (not so important) I cross-compile all kernel-related stuff. Although
'make -C $MIPSKERNELDIR SUBDIRS=`pwd`' is not as difficult, there
COULD be support for cross-compiling in the Makefile.
Markus
[1] yes, I opened the cover ;). channel was correct, too.
>
>
>
>
next prev parent reply other threads:[~2005-07-15 10:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-13 7:14 New VINO video drivers for Indy Mikael Nousiainen
2005-07-15 11:00 ` Markus Dahms [this message]
2005-07-15 21:53 ` Mikael Nousiainen
2005-07-16 11:27 ` Markus Dahms
2005-07-31 18:47 ` Mikael Nousiainen
2005-08-01 8:44 ` Markus Dahms
2005-08-01 18:42 ` Mikael Nousiainen
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=20050715110021.GA15740@gaspode.automagically.de \
--to=mad@automagically.de \
--cc=linux-mips@linux-mips.org \
--cc=turja@mbnet.fi \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox