All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Frank Schäfer" <fschaefer.oss@googlemail.com>
To: Chris Rankin <rankincj@yahoo.com>
Cc: Devin Heitmueller <dheitmueller@kernellabs.com>,
	Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: Very verbose message about em28174 chip.
Date: Sun, 28 Jul 2013 16:24:24 +0200	[thread overview]
Message-ID: <51F52998.1000700@googlemail.com> (raw)
In-Reply-To: <CAGoCfiy0dq2yF3WjT1AdYghOZnWcBO=9mWrTqyjKAcBY=17t1A@mail.gmail.com>

Am 28.07.2013 16:05, schrieb Devin Heitmueller:
> On Sun, Jul 28, 2013 at 9:58 AM, Chris Rankin <rankincj@yahoo.com> wrote:
>> ----- Original Message -----
>>
>> From: Devin Heitmueller <dheitmueller@kernellabs.com>
>>
>>> The amount of output is not inconsistent with most other linuxtv drivers though.
>> It's the EEPROM dump that really caught my eye: 16+ lines of pure "WTF?".
> Yeah, nowadays the eeprom output is one of the less useful pieces of
> output (in fact, I intentionally didn't do support for dumping it out
> on the em2874, but somebody did it anyway).

We've always been dumping the eeprom content (which doesn't mean that we
have to do it forever ;) ).
IIRC, the reason why we didn't dump the eeprom of the newer em2874+
devices up to now, that they are using 16bit eeproms and Devin thought
it was too dangerous to read them. ;)
It should also be mentioned, that we haven't decoded the meaning of this
eeprom type yet completely.

I don't care too much.

Regards,
Frank


      reply	other threads:[~2013-07-28 14:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-28 13:19 Very verbose message about em28174 chip Chris Rankin
2013-07-28 13:34 ` Steve Kerrison
2013-07-28 13:41 ` Devin Heitmueller
2013-07-28 13:58   ` Chris Rankin
2013-07-28 14:05     ` Devin Heitmueller
2013-07-28 14:24       ` Frank Schäfer [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=51F52998.1000700@googlemail.com \
    --to=fschaefer.oss@googlemail.com \
    --cc=dheitmueller@kernellabs.com \
    --cc=linux-media@vger.kernel.org \
    --cc=rankincj@yahoo.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 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.