From: Robert Jarzmik <robert.jarzmik@free.fr>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: video4linux-list@redhat.com
Subject: Re: soc-camera: current stack
Date: Wed, 24 Dec 2008 18:26:06 +0100 [thread overview]
Message-ID: <87wsdplc29.fsf@free.fr> (raw)
In-Reply-To: <Pine.LNX.4.64.0812200104090.9649@axis700.grange> (Guennadi Liakhovetski's message of "Sat\, 20 Dec 2008 02\:14\:15 +0100 \(CET\)")
Guennadi Liakhovetski <g.liakhovetski@gmx.de> writes:
> This should produce an equivalent of what is currently in my hg tree - at
> least in what soc-camera concerns. If there's any interest, I might look
> into installing a git-server and providing a git-tree with soc-camera
> patches on that server, for 3 users to pull 5 putches every 2 weeks my
> 400MHz ARM9 on a dyndns ADSL line should be enough:-)
>
> Next on queue (not yet in any of the directories on that server)
Hi Guennadi,
I made some tests of your patches against mainline tree (2.6.28-rc4 actually),
on pxa271 + mt9m111.
I have one little problem I can't remember having before :
[ 728.372987] Backtrace:
[ 728.378014] [<bf05f230>] (mt9m111_set_register+0x0/0x80 [mt9m111]) from [<bf056300>] (soc_camera_s_register+0x2c/0x38 [soc_camera])
[ 728.388248] r5:039e6cf0 r4:00000018
[ 728.393278] [<bf0562d4>] (soc_camera_s_register+0x0/0x38 [soc_camera]) from [<c0164734>] (__video_ioctl2+0x684/0x39a4)
[ 728.403419] [<c01640b0>] (__video_ioctl2+0x0/0x39a4) from [<c0167a70>] (video_ioctl2+0x1c/0x20)
[ 728.413404] [<c0167a54>] (video_ioctl2+0x0/0x20) from [<c009a8fc>] (vfs_ioctl+0x74/0x78)
[ 728.423393] [<c009a888>] (vfs_ioctl+0x0/0x78) from [<c009acb8>] (do_vfs_ioctl+0x390/0x4ac)
[ 728.433342] r5:039e6cf0 r4:c39d3340
[ 728.438221] [<c009a928>] (do_vfs_ioctl+0x0/0x4ac) from [<c009ae14>] (sys_ioctl+0x40/0x68)
[ 728.447976] [<c009add4>] (sys_ioctl+0x0/0x68) from [<c0024e80>] (ret_fast_syscall+0x0/0x2c)
[ 728.457785] r7:00000036 r6:4018564f r5:039e6cf0 r4:00000000
[ 728.462692] Code: e89da800 e1a0c00d e92dd830 e24cb004 (e5913000)
[ 728.468135] ---[ end trace a231255d0862dac6 ]---
I'm not sure whether the problem is not on my setup, I hadn't touched it for
days. I know after opening the video device, I setup a camera register before
taking the picture (to set up the test pattern and automate my non-regression
tests).
Will check after Christmas :)
Cheers.
--
Robert
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
next prev parent reply other threads:[~2008-12-24 17:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-01 21:15 [PATCH] mt9m111: Add automatic white balance control Robert Jarzmik
2008-12-17 18:20 ` Robert Jarzmik
2008-12-17 18:30 ` soc-camera: current stack (was Re: [PATCH] mt9m111: Add automatic white balance control) Guennadi Liakhovetski
2008-12-20 1:14 ` soc-camera: current stack Guennadi Liakhovetski
2008-12-24 17:26 ` Robert Jarzmik [this message]
2008-12-24 17:34 ` Guennadi Liakhovetski
2008-12-24 17:36 ` Robert Jarzmik
2008-12-24 17:39 ` Guennadi Liakhovetski
[not found] <20081218170015.10DD88E03CC@hormel.redhat.com>
2008-12-19 11:58 ` Agustin
2008-12-19 12:29 ` Guennadi Liakhovetski
2008-12-22 9:32 ` Robert Schwebel
2008-12-22 10:30 ` Guennadi Liakhovetski
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=87wsdplc29.fsf@free.fr \
--to=robert.jarzmik@free.fr \
--cc=g.liakhovetski@gmx.de \
--cc=video4linux-list@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox