From: Jarod Wilson <jarod@redhat.com>
To: Trent Piepho <xyzzy@speakeasy.org>
Cc: Steven Toth <stoth@kernellabs.com>, linux-media@vger.kernel.org
Subject: Re: [PATCH] dvb: make digital side of pcHDTV HD-3000 functional again
Date: Wed, 22 Jul 2009 13:59:00 -0400 [thread overview]
Message-ID: <200907221359.00892.jarod@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0907212343130.11911@shell2.speakeasy.net>
On Wednesday 22 July 2009 02:51:12 Trent Piepho wrote:
> On Tue, 21 Jul 2009, Jarod Wilson wrote:
> > On Tuesday 21 July 2009 10:23:53 Steven Toth wrote:
> > > > Hrm, okay, I'll double-check that... If its not there, perhaps the card
> > > > isn't quite seated correctly. Or the machine is bunk. Or the card has
> > > > gone belly up. Amusing that it works as much as it does though, if any
> > > > of the above is the case...
> > > >
> > > > Thanks for the info!
> > > >
> > >
> > > Jrod,
> > >
> > > Yeah. If the pci enable bit for the transport engine is not enabled (thus
> > > showing up as pci device 8802) then I'm going to be surprised if the risc engine
> > > runs up at all (or runs perfectly).
> > >
> > > I've seen issue like this in the past with various cx88 boards and it invariable
> > > turn out to be a corrupt eeprom or a badly seated PCI card.
> > >
> > > or, no eeprom at all (unlikely on this board).
> >
> > So its either I have *two* machines with bad, but only slightly bad,
> > and in the same way, PCI slots which seem to work fine with any other
> > card I have (uh, unlikely), or my HD-3000 has gone belly up on me in
> > some subtle way. The cx8802 part never shows up under lspci on either
> > machine I've tried it in. Suck.
>
> Check your eeprom, it could be set incorrectly.
>
> "i2cdump -f 0 0x50" will show the contents if the HD-3000 has i2c bus 0.
> i2cdump with no arguments will tell you what each bus is.
>
> The first 12 bytes should look something like this:
> 00: 06 ff ff ff 63 70 00 30 e0 01 40 ff 00 00 00 00 ?...cp.0??@.....
>
>
> The first byte should have bit 0x04 set to enable mpeg.
So here's what was in my eeprom:
00: 00 00 00 00 63 70 00 30 e0 01 40 ff 00 00 00 00 ....cp.0??@.....
Sooo... For funsies, I figured out how to use i2cset, and made it match
your example. After rebooting, I have the cx8802 device showing up
again. Cool! Now to see if it actually *works*... :)
--
Jarod Wilson
jarod@redhat.com
next prev parent reply other threads:[~2009-07-22 18:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-20 14:20 [PATCH] dvb: make digital side of pcHDTV HD-3000 functional again Jarod Wilson
2009-07-20 19:51 ` Trent Piepho
2009-07-20 20:50 ` Jarod Wilson
2009-07-21 14:23 ` Steven Toth
2009-07-22 1:35 ` Jarod Wilson
2009-07-22 1:48 ` Bob Hepple
2009-07-22 15:54 ` Steven Toth
2009-07-22 16:06 ` Devin Heitmueller
2009-07-22 6:51 ` Trent Piepho
2009-07-22 11:57 ` Andy Walls
2009-07-22 17:59 ` Jarod Wilson [this message]
2009-07-22 18:12 ` Jarod Wilson
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=200907221359.00892.jarod@redhat.com \
--to=jarod@redhat.com \
--cc=linux-media@vger.kernel.org \
--cc=stoth@kernellabs.com \
--cc=xyzzy@speakeasy.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