public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gerd Knorr <kraxel@bytesex.org>
To: James Bruce <bruce@andrew.cmu.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Potentially dead bttv cards from 2.6.10
Date: 01 Mar 2005 09:44:42 +0100	[thread overview]
Message-ID: <87is4b21s5.fsf@bytesex.org> (raw)
In-Reply-To: <42240EB3.6040504@andrew.cmu.edu>

James Bruce <bruce@andrew.cmu.edu> writes:

> If you could suggest a very well tested kernel for bttv (2.6.9?),

What do you expect?  With just one single report and not remotely
being clear what exactly caused it ...

> I've heard that there is some way to dump eeproms; Is there a way to
> write them also?

Yes, you can.  That works only if you can still talk to it though.

> If I could copy the eeprom from the unused cards to the (now broken)
> pair that might fix things.

No.  It's not accessable, not just the content scrambled.

  Gerd
 
-- 
#define printk(args...) fprintf(stderr, ## args)

  reply	other threads:[~2005-03-01  8:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-26  4:57 Potentially dead bttv cards from 2.6.10 James Bruce
2005-02-28 13:44 ` Gerd Knorr
2005-02-28 14:43   ` James Bruce
2005-02-28 16:02     ` Gerd Knorr
2005-02-28 16:45       ` Folkert van Heusden
2005-02-28 16:52         ` Gerd Knorr
2005-03-01  6:41       ` James Bruce
2005-03-01  8:44         ` Gerd Knorr [this message]
2005-03-01 13:10           ` James Bruce
2005-03-04 20:37           ` James Bruce
2005-02-28 23:14     ` Bill Davidsen
2005-03-01  7:06       ` James Bruce
2005-03-01 14:11         ` Paulo Marques
2005-03-01 15:44           ` James Bruce
2005-03-01 16:03             ` Gerd Knorr
2005-03-01 20:32             ` Bill Davidsen

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=87is4b21s5.fsf@bytesex.org \
    --to=kraxel@bytesex.org \
    --cc=bruce@andrew.cmu.edu \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox