public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Jarzmik <robert.jarzmik@free.fr>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: Soc-camera and 2.6.33
Date: Tue, 01 Jun 2010 00:27:14 +0200	[thread overview]
Message-ID: <87bpbvvha5.fsf@free.fr> (raw)
In-Reply-To: <Pine.LNX.4.64.1005312338280.16053@axis700.grange> (Guennadi Liakhovetski's message of "Mon\, 31 May 2010 23\:51\:43 +0200 \(CEST\)")

Guennadi Liakhovetski <g.liakhovetski@gmx.de> writes:

> Hi Robert
>
> a lot of things changed in and around soc-camera between 2.6.30 and 
> .33... E.g., previously you could load driver modules in any order, it 
> would work in any case. Now if you load your host driver (pxa) and your 
> client driver is not there yet, it should be automatically loaded. 
> However, if your user-space doesn't support this, it won't work. Can this 
> be the reason gor your problem? Otherwise, I'd suspect a problem with your 
> platform data (cf. other platforms), or, eventually with mt9m111.

I have a very tiny system :
 - udev
 - a shell (/bin/ash)
 - a libc
 - busybox (insmod/modprobe/rmmod/ls)
 - capture_example compiled as my testbed

I do :
 - insmod mt9m111.ko
 - insmod pxa_camera.ko

My userspace hasn't changed since 2.6.30 (constant executables, ARM-EABI). My
platform was converted by you in commit a48c24a696f0d93c49f913b7818e9819612b1f4e
if I remember correctly.

Any hint for me to track down my problem ?

Cheers.


-- 
Robert

  reply	other threads:[~2010-05-31 22:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-31 20:24 Soc-camera and 2.6.33 Robert Jarzmik
2010-05-31 21:51 ` Guennadi Liakhovetski
2010-05-31 22:27   ` Robert Jarzmik [this message]
2010-06-01 20:20   ` Robert Jarzmik
2010-06-01 20:31     ` 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=87bpbvvha5.fsf@free.fr \
    --to=robert.jarzmik@free.fr \
    --cc=g.liakhovetski@gmx.de \
    --cc=linux-media@vger.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