From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Daniel Ritz <daniel.ritz@gmx.ch>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] uvcvideo: add another YUYV format GUID
Date: Thu, 03 Dec 2009 20:59:35 -0800 [thread overview]
Message-ID: <4B189737.1010100@gmail.com> (raw)
In-Reply-To: <1259892337.2335.34.camel@MacRitz2>
On 12/03/09 18:05, Daniel Ritz wrote:
> Hi Laurent
>
> On Thu, 2009-12-03 at 21:15 +0100, Laurent Pinchart wrote:
>> Hi Daniel,
>>
>> On Wednesday 02 December 2009 00:48:44 Daniel Ritz wrote:
>>> For some unknown reason, on a MacBookPro5,3 the iSight
>>
>> Could you please send me the output of lsusb -v both with the correct and
>> wrong GUID ?
>
> sure. i attached three files:
> isight-good.txt, isight-bad.txt, isight-good2.txt
>
> this is three reboots in a row from like 10 minutes ago. the first
> boot into linux was actually rebooting from OSX...first cold boot
> today directly into linux had the right GUID.
>
>>
>>> _sometimes_ report a different video format GUID.
>>
>> Sometimes only ? Now that's weird. Is that completely random ?
>
> yes, sometimes only. it seems to be related to reboots, but i don't
> know what exactly triggers it. rmmod/modprobe doesn't trigger it.
> also, when the wrong GUID is reported, the only way of fixing it is
> to reboot. it really is just the GUID. even when the wrong one is
> reported, the device works just fine.
>
> i started with a plain ubuntu 9.10, kernel 2.6.31 which was supposed
> to fail, so i upgraded to a 2.6.32-rc8 to fix the iSight and some other
> things, just to see it fail again. a reboot later and it worked, some
> time and reboot later it failed again...
>
> rgds
> -daniel
>
>>> This patch add the other (wrong) GUID to the format table, making the iSight
>>> work always w/o other problems.
>>>
>>> What it should report: 32595559-0000-0010-8000-00aa00389b71
>>> What it often reports: 32595559-0000-0010-8000-000000389b71
>>>
>>> Signed-off-by: Daniel Ritz<daniel.ritz@gmx.ch>
>>
>> --
>> Regards,
>>
>> Laurent Pinchart
>
I get weiredness whenever
I shutdown the machine and then boot.
If I boot, then reboot things work.
Justin P. Mattock
next prev parent reply other threads:[~2009-12-04 4:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-01 23:48 [PATCH] uvcvideo: add another YUYV format GUID Daniel Ritz
2009-12-03 20:15 ` Laurent Pinchart
2009-12-04 2:05 ` Daniel Ritz
2009-12-04 4:59 ` Justin P. Mattock [this message]
2009-12-08 15:04 ` Daniel Ritz
2009-12-10 1:46 ` Laurent Pinchart
2009-12-10 16:34 ` Daniel Ritz
2009-12-11 1:21 ` Laurent Pinchart
2009-12-11 10:19 ` Daniel Ritz
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=4B189737.1010100@gmail.com \
--to=justinmattock@gmail.com \
--cc=daniel.ritz@gmx.ch \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.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 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.