Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: ivtv: devel

I2C Write Issues

 

 

ivtv devel RSS feed   Index | Next | Previous | View Threaded


knisleyjw at yahoo

Feb 27, 2005, 1:39 AM

Post #1 of 4 (802 views)
Permalink
I2C Write Issues

Hi all,

I had a problem back a while ago when I initially
posted my tuner data to the forum, but no one got
round to it and here it is cropping up again. I had a
Compaq test machine that I put the PVR-500 in and it
worked rather well (except it was too damn slow to be
of any good).

I originally had the board in what was my record box
with a PVR-250, an IWill DP400 with dual P4 Xeon 2.4.
I was getting this:

cx25840: I2C set default write failed, length 10, ret
-38

when loading things. Actually, quite a few of those.

Now, I thought all would be great as it functions
beautifully (well, most of it) on the Compaq machine,
however with a new install of linux, mythtv, and ivtv
all patched up, the problem returns. I tried to run
mplayer and mythtv in spite of those errors but get
nothing but black in mythtv and nothing beyond format
identification in mplayer.

Anyone have any thoughts on what's happening? I could
try this again with a uniprocessor kernel, maybe, but
it really defeats the purpose of having a dual board.

Jason


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel


knisleyjw at yahoo

Feb 27, 2005, 3:33 AM

Post #2 of 4 (776 views)
Permalink
Re: I2C Write Issues [In reply to]

Whee! I've found the source of the problem, just
trying to see the format of probe or ignore while
searching through the code to find out why the cx25840
driver isn't verifying that it's attaching to an
actual cx25840. I found a big FIXME in cx25840-driver
that had something to that affect.

It turns out that a majority of my monitoring stuff
for my motherboard is done with i2c. So when the i2c
modules load (no sensors, just the bus detector), it
has i2c-c0. Well, I found that cx25840 thought it had
three of cx25840's, including the one on i2c-c0 (when
the rest of the card modules say that they're only
attached to 1 and 2).

Anyone got any quick fix (or hopefully more permanant
fix) suggestions on how to work around this? I'll see
if I can play with the code.

Thanks,
Jason

--- Jason Knisley <knisleyjw [at] yahoo> wrote:

> Hi all,
>
> I had a problem back a while ago when I initially
> posted my tuner data to the forum, but no one got
> round to it and here it is cropping up again. I had
> a
> Compaq test machine that I put the PVR-500 in and it
> worked rather well (except it was too damn slow to
> be
> of any good).
>
> I originally had the board in what was my record box
> with a PVR-250, an IWill DP400 with dual P4 Xeon
> 2.4.
> I was getting this:
>
> cx25840: I2C set default write failed, length 10,
> ret
> -38
>
> when loading things. Actually, quite a few of those.
>
> Now, I thought all would be great as it functions
> beautifully (well, most of it) on the Compaq
> machine,
> however with a new install of linux, mythtv, and
> ivtv
> all patched up, the problem returns. I tried to run
> mplayer and mythtv in spite of those errors but get
> nothing but black in mythtv and nothing beyond
> format
> identification in mplayer.
>
> Anyone have any thoughts on what's happening? I
> could
> try this again with a uniprocessor kernel, maybe,
> but
> it really defeats the purpose of having a dual
> board.
>
> Jason
>
>
>
-------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT
> Products from real users.
> Discover which products truly live up to the hype.
> Start reading now.
>
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> ivtv-devel mailing list
> ivtv-devel [at] lists
>
https://lists.sourceforge.net/lists/listinfo/ivtv-devel
>



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel


ttrafford at gmail

Feb 27, 2005, 12:44 PM

Post #3 of 4 (769 views)
Permalink
Re: I2C Write Issues [In reply to]

If I understand you correctly, you should look at the i2c_enable paramter.


On Sun, 27 Feb 2005 02:33:29 -0800 (PST), Jason Knisley
<knisleyjw [at] yahoo> wrote:
> Whee! I've found the source of the problem, just
> trying to see the format of probe or ignore while
> searching through the code to find out why the cx25840
> driver isn't verifying that it's attaching to an
> actual cx25840. I found a big FIXME in cx25840-driver
> that had something to that affect.
>
> It turns out that a majority of my monitoring stuff
> for my motherboard is done with i2c. So when the i2c
> modules load (no sensors, just the bus detector), it
> has i2c-c0. Well, I found that cx25840 thought it had
> three of cx25840's, including the one on i2c-c0 (when
> the rest of the card modules say that they're only
> attached to 1 and 2).
>
> Anyone got any quick fix (or hopefully more permanant
> fix) suggestions on how to work around this? I'll see
> if I can play with the code.
>
> Thanks,
> Jason
>
> --- Jason Knisley <knisleyjw [at] yahoo> wrote:
>
> > Hi all,
> >
> > I had a problem back a while ago when I initially
> > posted my tuner data to the forum, but no one got
> > round to it and here it is cropping up again. I had
> > a
> > Compaq test machine that I put the PVR-500 in and it
> > worked rather well (except it was too damn slow to
> > be
> > of any good).
> >
> > I originally had the board in what was my record box
> > with a PVR-250, an IWill DP400 with dual P4 Xeon
> > 2.4.
> > I was getting this:
> >
> > cx25840: I2C set default write failed, length 10,
> > ret
> > -38
> >
> > when loading things. Actually, quite a few of those.
> >
> > Now, I thought all would be great as it functions
> > beautifully (well, most of it) on the Compaq
> > machine,
> > however with a new install of linux, mythtv, and
> > ivtv
> > all patched up, the problem returns. I tried to run
> > mplayer and mythtv in spite of those errors but get
> > nothing but black in mythtv and nothing beyond
> > format
> > identification in mplayer.
> >
> > Anyone have any thoughts on what's happening? I
> > could
> > try this again with a uniprocessor kernel, maybe,
> > but
> > it really defeats the purpose of having a dual
> > board.
> >
> > Jason
> >
> >
> >
> -------------------------------------------------------
> > SF email is sponsored by - The IT Product Guide
> > Read honest & candid reviews on hundreds of IT
> > Products from real users.
> > Discover which products truly live up to the hype.
> > Start reading now.
> >
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> > _______________________________________________
> > ivtv-devel mailing list
> > ivtv-devel [at] lists
> >
> https://lists.sourceforge.net/lists/listinfo/ivtv-devel
> >
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> ivtv-devel mailing list
> ivtv-devel [at] lists
> https://lists.sourceforge.net/lists/listinfo/ivtv-devel
>


--
Tyler Trafford


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel


knisleyjw at yahoo

Feb 27, 2005, 11:31 PM

Post #4 of 4 (777 views)
Permalink
Re: I2C Write Issues [In reply to]

Well, what I need is to exclude adapter 0 in the
scanning. I tried something like i2c_enable=0,1,1 - it
looks like the correct format for the parameter from
reading the code. That didn't solve my problem. Only
the little haphazard code addition did. Am I doing
something wrong with the syntax? Also, is there any
way that the modinfos can be updated across the board
so that they have the correct syntax for each
parameter?

It would probably reduce the chance of more of people
asking about module parameters on here. :)

Thanks,
Jason


--- Tyler Trafford <ttrafford [at] gmail> wrote:

> If I understand you correctly, you should look at
> the i2c_enable paramter.
>
>
> On Sun, 27 Feb 2005 02:33:29 -0800 (PST), Jason
> Knisley
> <knisleyjw [at] yahoo> wrote:
> > Whee! I've found the source of the problem, just
> > trying to see the format of probe or ignore while
> > searching through the code to find out why the
> cx25840
> > driver isn't verifying that it's attaching to an
> > actual cx25840. I found a big FIXME in
> cx25840-driver
> > that had something to that affect.
> >
> > It turns out that a majority of my monitoring
> stuff
> > for my motherboard is done with i2c. So when the
> i2c
> > modules load (no sensors, just the bus detector),
> it
> > has i2c-c0. Well, I found that cx25840 thought it
> had
> > three of cx25840's, including the one on i2c-c0
> (when
> > the rest of the card modules say that they're only
> > attached to 1 and 2).
> >
> > Anyone got any quick fix (or hopefully more
> permanant
> > fix) suggestions on how to work around this? I'll
> see
> > if I can play with the code.
> >
> > Thanks,
> > Jason
> >
> > --- Jason Knisley <knisleyjw [at] yahoo> wrote:
> >
> > > Hi all,
> > >
> > > I had a problem back a while ago when I
> initially
> > > posted my tuner data to the forum, but no one
> got
> > > round to it and here it is cropping up again. I
> had
> > > a
> > > Compaq test machine that I put the PVR-500 in
> and it
> > > worked rather well (except it was too damn slow
> to
> > > be
> > > of any good).
> > >
> > > I originally had the board in what was my record
> box
> > > with a PVR-250, an IWill DP400 with dual P4 Xeon
> > > 2.4.
> > > I was getting this:
> > >
> > > cx25840: I2C set default write failed, length
> 10,
> > > ret
> > > -38
> > >
> > > when loading things. Actually, quite a few of
> those.
> > >
> > > Now, I thought all would be great as it
> functions
> > > beautifully (well, most of it) on the Compaq
> > > machine,
> > > however with a new install of linux, mythtv, and
> > > ivtv
> > > all patched up, the problem returns. I tried to
> run
> > > mplayer and mythtv in spite of those errors but
> get
> > > nothing but black in mythtv and nothing beyond
> > > format
> > > identification in mplayer.
> > >
> > > Anyone have any thoughts on what's happening? I
> > > could
> > > try this again with a uniprocessor kernel,
> maybe,
> > > but
> > > it really defeats the purpose of having a dual
> > > board.
> > >
> > > Jason
> > >
> > >
> > >
> >
>
-------------------------------------------------------
> > > SF email is sponsored by - The IT Product Guide
> > > Read honest & candid reviews on hundreds of IT
> > > Products from real users.
> > > Discover which products truly live up to the
> hype.
> > > Start reading now.
> > >
> >
>
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> > > _______________________________________________
> > > ivtv-devel mailing list
> > > ivtv-devel [at] lists
> > >
> >
>
https://lists.sourceforge.net/lists/listinfo/ivtv-devel
> > >
> >
> >
>
-------------------------------------------------------
> > SF email is sponsored by - The IT Product Guide
> > Read honest & candid reviews on hundreds of IT
> Products from real users.
> > Discover which products truly live up to the hype.
> Start reading now.
> >
>
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> > _______________________________________________
> > ivtv-devel mailing list
> > ivtv-devel [at] lists
> >
>
https://lists.sourceforge.net/lists/listinfo/ivtv-devel
> >
>
>
> --
> Tyler Trafford
>
>
>
-------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT
> Products from real users.
> Discover which products truly live up to the hype.
> Start reading now.
>
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> ivtv-devel mailing list
> ivtv-devel [at] lists
>
https://lists.sourceforge.net/lists/listinfo/ivtv-devel
>



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

ivtv devel RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.