public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Buesch <fsdeveloper@yahoo.de>
To: Gerd Knorr <kraxel@bytesex.org>
Cc: video4linux-list@redhat.com,
	linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [2.6-test3] bttv driver doesn't run
Date: Mon, 11 Aug 2003 18:13:20 +0200	[thread overview]
Message-ID: <200308111813.56558.fsdeveloper@yahoo.de> (raw)
In-Reply-To: <20030811121546.GA8998@bytesex.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday 11 August 2003 14:15, Gerd Knorr wrote:
> Yea, the reinitialize function doesn't re-enable the interrupts.
> Try latest patches from bytesex.org/patches/ which have this fixed, that
> should improve error recovery ...

I applied this patch:
http://bytesex.org/patches/2.6.0-test3/patch-2.6.0-test3-kraxel.gz

bttv run's fine, now.
I only got some small error-messages recently:

Aug 11 18:08:58 lfs kernel: bttv0: skipped frame. no signal? high irq latency?
Aug 11 18:10:57 lfs last message repeated 2 times

Most error messages I got before have gone and my tv-application
runs fine.

Thank you, for support, Gerd.

>   Gerd

- -- 
Regards Michael Buesch  [ http://www.8ung.at/tuxsoft ]
Animals on this machine: some GNUs and Penguin 2.6.0-test3

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE/N8DAoxoigfggmSgRAowNAJ9kh1kB08tEqh2b3ew1uGToS93PwACeK8sg
h2KeiMi4k+k8JEEHMK3ZYRI=
=j5bm
-----END PGP SIGNATURE-----


  parent reply	other threads:[~2003-08-11 16:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-09 19:04 [2.6-test3] bttv driver doesn't run Michael Buesch
2003-08-11 12:15 ` Gerd Knorr
2003-08-11 12:19   ` Michael Buesch
2003-08-11 13:29     ` Gerd Knorr
2003-08-11 16:13   ` Michael Buesch [this message]
2003-08-13  9:05     ` [2.6-test3] bttv driver confuses PS2 mouse Michael Buesch

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=200308111813.56558.fsdeveloper@yahoo.de \
    --to=fsdeveloper@yahoo.de \
    --cc=kraxel@bytesex.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=video4linux-list@redhat.com \
    /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