linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jean Delvare" <khali@linux-fr.org>
To: rbultje@ronald.bitfreak.net
Cc: "Chris Wright" <chrisw@osdl.org>,
	"Randy.Dunlap" <rddunlap@osdl.org>,
	"Daniel Staaf" <dst@bostream.nu>,
	"LKML" <linux-kernel@vger.kernel.org>,
	"Andrei Mikhailovsky" <andrei@arhont.com>,
	"Ian Campbell" <icampbell@arcom.com>,
	"Gerd Knorr" <kraxel@bytesex.org>,
	stable@kernel.org
Subject: Re: [PATCH 2.6] Fix i2c messsage flags in video drivers
Date: Thu, 10 Mar 2005 11:56:10 +0100 (CET)	[thread overview]
Message-ID: <6TEha2ac.1110452170.7309170.khali@localhost> (raw)
In-Reply-To: <Pine.LNX.4.56.0503092336240.16415@www.ithos.nl>


Hi Ronald,

[Jean Delvare]
> It is possible that people are able to get their board to still work
> without my patch, if the chips were properly configured in the first
> place and they don't attempt to reconfigure them (like norm change). I
> don't know the chips well enough to tell how probable this is.

[Ronald S. Bultje]
> I'm pretty sure the patch is correct, I trust you a lot more on that than
> myself (I still need to test it, though; but that's a detail). However,
> this statement is not correct. I test this driver daily, I still own a
> whole bunch of such cards. Even after hard reboots, they still just work.
> Norm changes, input changes, everything works. I test (and use) all of
> this. I would've noticed if it was really as broken as you're describing
> above.

I'm glad to learn you are testing things. Still the oops in saa7110 went
unnoticed for the past 3 months, so I guess that either you don't have
a DC10(+) in your test panel, or you did not test mm/rc kernels.

I've gone through the code again, and here is what I think is broken in
2.6.11 on the various Zoran-based boards. Then everyone will be free to
pick any patch chunk he/she wants and apply it to any tree he/she likes.

BUZ:
Input (saa7111): works
Output (saa7185): no init, cannot set norm

DC10:
Input (saa7110): oops
Output (adv7175): no init, cannot set norm

DC30:
Input (vpx3220): works
Output (adv7175): no init, cannot set norm

LM33:
Input (bt819): no init
Output (bt856): works

LM33R10:
Input (saa7114): no init, cannot set norm
Output (adv7170): no init, cannot set norm

As you can see, all boards are affected at some level but every user
might not be equally affected, depends whether you use input or output
or both. Note that "no init" might not affect everyone either, depends
on the chip init defaults and the user needs. Ronald, can you tell us
what exactly in the above you are testing?

Personally I have only been able to test input on a DC10+ board (saa7110
driver). I lack hardware to test the output.

Hope that clarifies things,
--
Jean Delvare

  reply	other threads:[~2005-03-10 10:59 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-05 12:11 amd64 2.6.11 oops on modprobe Andrei Mikhailovsky
2005-03-06  0:53 ` Randy.Dunlap
2005-03-06 13:33   ` Andrei Mikhailovsky
2005-03-07  3:52     ` Randy.Dunlap
2005-03-07  5:01     ` Randy.Dunlap
2005-03-07 21:47     ` Randy.Dunlap
2005-03-08 19:15       ` Jean Delvare
2005-03-08 19:25         ` [PATCH 2.6] Fix i2c messsage flags in video drivers Jean Delvare
2005-03-09 18:40           ` Chris Wright
2005-03-09 21:55             ` Jean Delvare
2005-03-09 22:40               ` Ronald S. Bultje
2005-03-10 10:56                 ` Jean Delvare [this message]
2005-03-10  0:47                   ` Ronald S. Bultje
2005-03-10 11:50                     ` Jean Delvare
2005-03-10  1:33                       ` Ronald S. Bultje
2005-03-09 23:28               ` Chris Wright
2005-03-21 22:47 ` amd64 2.6.11 oops on modprobe Andrew Morton
2005-05-25 22:24 ` Andrew Morton

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=6TEha2ac.1110452170.7309170.khali@localhost \
    --to=khali@linux-fr.org \
    --cc=andrei@arhont.com \
    --cc=chrisw@osdl.org \
    --cc=dst@bostream.nu \
    --cc=icampbell@arcom.com \
    --cc=kraxel@bytesex.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rbultje@ronald.bitfreak.net \
    --cc=rddunlap@osdl.org \
    --cc=stable@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;
as well as URLs for NNTP newsgroup(s).