2009. 06. 22, 오후 11:01, Aguirre Rodriguez, Sergio Alberto 작성:
-Original Message-
From: linux-media-ow...@vger.kernel.org [mailto:linux-media-
ow...@vger.kernel.org] On Behalf Of Tuukka.O Toivonen
Sent: Monday, June 22, 2009 8:52 AM
To: ext Dongsoo, Nathaniel Kim
Cc: Sakari Ailus; linux-
2009. 06. 22, 오후 10:52, Tuukka.O Toivonen 작성:
On Saturday 20 June 2009 12:05:13 ext Dongsoo, Nathaniel Kim wrote:
Following patch.
http://www.gitorious.org/omap3camera/mainline/commit/d92c96406296310a977b00f45b209523929b15b5
What happens to the capability when the int device is dummy? (does it
Hi Hans,
2009. 05. 22, 오후 9:40, Hans Verkuil 작성:
On Friday 22 May 2009 04:05:47 Dongsoo, Nathaniel Kim wrote:
Hi Hans,
On Thu, May 21, 2009 at 9:07 PM, Hans Verkuil
wrote:
On Wednesday 20 May 2009 13:48:08 Dongsoo, Nathaniel Kim wrote:
Hello everyone,
Doing a new camera interface drive
Hello Hans and Hiremath,
One of my recent job is making S3C64XX camera interface driver (even
though other jobs of mine are not finished yet...;-()
And, what a incident! S3C64XX has also similar H/W block in camera
interface.
Resizer in S3C camera interface can be used in system wide like the
2009. 04. 16, 오후 11:56, Guennadi Liakhovetski 작성:
On Thu, 16 Apr 2009, Dongsoo Kim wrote:
And about camera client with several inputs question, I will say
that
almost every 3G UMTS phone has dual camera on it. And we can
consider
every 3G UMTS smart phones have dual camera on it with soc
2009. 04. 16, 오후 9:59, Guennadi Liakhovetski 작성:
On Thu, 16 Apr 2009, Dongsoo, Nathaniel Kim wrote:
Hello Guennadi,
On Thu, Apr 16, 2009 at 9:06 PM, Guennadi Liakhovetski
wrote:
3. you open videoX, one "default" camera gets activated
immediately - not
all applications issue S_INPUT, so,
Hi,
2009. 03. 28, 오전 1:19, Laurent Pinchart 작성:
Hi,
On Friday 27 March 2009 08:24:27 Hans Verkuil wrote:
On Friday 27 March 2009 07:20:51 Kim, Heung Jun wrote:
Hello, Hans & everyone.
I'm trying to adapt the various FOCUS MODE int the NEC ISP driver.
NEC ISP supports 4 focus mode, AUTO/MAC
Hi Tony,
I think I can join you. And also Kyungmin Park I guess.
See you then.
Nate
2009. 03. 18, 오전 1:45, Tony Lindgren 작성:
* Kevin Hilman [090317 07:50]:
Hans Verkuil wrote:
On Tuesday 17 March 2009 01:14:28 Steve Sakoman wrote:
On Mon, Mar 16, 2009 at 3:56 PM, Tony Lindgren
wrote:
*
Hello Hans.
I went too far.
Just forgot what we can do through porting job.
You are right. That should be board specific item.
Cheers,
Nate
2009. 02. 18, 오후 11:36, Hans de Goede 작성:
DongSoo(Nathaniel) Kim wrote:
Hello Adam,
I've been thinking exactly the same issue not usb but SoC based
board with NEC ISP...but
unfortunately not working yet ;(
I should try more harder. more research is needed :)
Cheers,
On Thu, Feb 12, 2009 at 4:09 PM, Sakari Ailus
wrote:
> DongSoo Kim wrote:
>>
>> Hello.
>
> Hi, and thanks for the comments!
>
>> +static int o
Hello.
+static int omap34xxcam_open(struct inode *inode, struct file *file)
+{
+ if (atomic_inc_return(&vdev->users) == 1) {
+ isp_get();
+ if (omap34xxcam_slave_power_set(vdev, V4L2_POWER_ON,
+ OMAP34XXCAM_SLAVE_PO
Hello.
This could be something trivial.
On Tue, Jan 13, 2009 at 11:03 AM, Aguirre Rodriguez, Sergio Alberto
wrote:
> +/**
> + * struct omap34xxcam_hw_config - struct for vidioc_int_g_priv ioctl
> + * @xclk: OMAP34XXCAM_XCLK_A or OMAP34XXCAM_XCLK_B
> + * @sensor_isp: Is sensor smart/SOC or raw
>
Hello.
Since I was working on OMAP3 camera driver with camera interface
driver in OMAPZOOM repository,
I could not figure it out how to control strobe device.
I found that strobe control depends on CSI1 (MIPI)..but how could I
control that?
In my opinion, in case of OMAP3 ISP has to be made in
On 화, 2009-02-03 at 11:20 +0100, Laurent Pinchart wrote:
> Hi Nate,
>
> On Thursday 29 January 2009, Dongsoo Kim wrote:
> > Thank you.
> >
> > So if V4L2_CID_EXPOSURE is for Exposure Value control, I think there
> > is no api for exposure metering. right?
&g
, DongSoo Kim wrote:
Hello.
When we take pictures, sometimes we don't get satisfied with the
exposure of picture. Too dark or too bright.
For that reason, we need to bias EV which represents Exposure Value.
So..if I want to control digital camera module with V4L2 API, which
API should I tak
Hello.
> +#define VIDIOC_S_COLOR_SPACE_CONV _IOW('V', 83, struct
> v4l2_color_space_conversion)
> +#define VIDIOC_G_COLOR_SPACE_CONV _IOR('V', 84, struct
> v4l2_color_space_conversion)
Do you mind if I ask a question about those ioctls?
Because as far as I understand, we can use VIDIO
Hello.
When we take pictures, sometimes we don't get satisfied with the
exposure of picture. Too dark or too bright.
For that reason, we need to bias EV which represents Exposure Value.
So..if I want to control digital camera module with V4L2 API, which
API should I take for EV control?
V4L2 do
Jan 2009 12:20:16 +0900
> "DongSoo Kim" wrote:
>
>> Hello everyone.
>>
>> I'm facing with some questions about "Can I make it ioctl or CID?"
>
> For most cases, creating a control (CID) is better than using another ioctl.
>
>> Because if
Hello everyone.
I'm facing with some questions about "Can I make it ioctl or CID?"
Because if I make it in ioctl It should occupy one of the extra ioctl
number for v4l2, and I'm afraid it deserves that.
Actually I'm working on strobe flash device (like xenon flash, LED
flash and so on...) for di
on kernel git tree.
is somebody working on it? I'm looking forward that I could see them
soon on kernel repo.
cheers,
Nate
On Wed, Jan 7, 2009 at 7:29 PM, Mauro Carvalho Chehab
wrote:
> Hi DongSoo,
>
> On Wed, 7 Jan 2009 13:38:56 +0900
> "DongSoo Kim" wrote:
>
&g
Hello V4L2 people.
I'm working on camera device drivers over 5M pixel and made drivers
based on V4L2 API.
Actually I'm still working on it.
By the way, I have some questions in exposure control.
If my guess is right, V4L2_CID_EXPOSURE_* CIDs are what I'm looking for.
Control factors that I int
21 matches
Mail list logo
