From: Hans de Goede <j.w.r.degoede@hhs.nl>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: video4linux-list@redhat.com, linuxkernel@lanrules.de,
bugme-daemon@bugzilla.kernel.org,
Mauro Carvalho Chehab <mchehab@infradead.org>
Subject: Re: [Bugme-new] [Bug 11776] New: Regression: Hardware working with old stock gspca module fails with 2.6.27 module
Date: Tue, 21 Oct 2008 11:10:29 +0200 [thread overview]
Message-ID: <48FD9C85.5040102@hhs.nl> (raw)
In-Reply-To: <20081020165537.9bb9ae8a.akpm@linux-foundation.org>
Andrew Morton wrote:
> (switched to email. Please respond via emailed reply-to-all, not via the
> bugzilla web interface).
>
> gspca doesn't seem to have a MAINTAINERS record. Or it is entered
> under something unobvious so my search failed?
>
We need to fix that then, gspca is maintained by Jean-Francois Moine, with me
co-maintaining.
<snip>
>> This is the information about the webcam given by the old gspca module, still
>> working with 2.6.26:
>> Camera found: lenovo MI1310_SOC
>> Bridge found: VC0323
>> StreamId: JPEG Camera
>> quality 7 autoexpo 1 Timeframe 0 lightfreq 50
>> Available Resolutions width 640 heigth 480 native
>> Available Resolutions width 352 heigth 288 native
>> Available Resolutions width 320 heigth 240 native *
>> Available Resolutions width 176 heigth 144 native
>> Available Resolutions width 160 heigth 120 native
>> unable to probe size !!
>>
Ok, so from this I gather that you are using spcaview to watch images from the
cam. spcaview by default asks the driver for yv12 format video data.
However the vc0323 cam in your laptop delivers video data in JPEG format. The
old gspca driver did format conversion inside the kernel. Which is a very bad
thing to do and thus has been removed in the new version.
Most apps / libraries do not know how to handle the multitude of video formats
webcams can produce. For this I've written libv4l:
http://hansdegoede.livejournal.com/3636.html
Get the latest version here:
http://people.atrpms.net/~hdegoede/libv4l-0.5.1.tar.gz
Then read:
http://moinejf.free.fr/gspca_README.txt
or the included README for install instructions.
As described in the documents you can make existing applications use this lib
with an LD_PRELOAD loadable wrapper.
FOSS applications can be easily adapted to instead use the library directly, a
coordinated cross distro effort is underway to make this happen (including
pushing patches upstream), see:
http://linuxtv.org/v4lwiki/index.php/Libv4l_Progress
You can find patches for quite a few applications here. Help in patching others
is very much welcome! If you need some quick instructions what to change
exactly let me know.
Regards,
Hans
--
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-10-21 9:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-11776-10286@http.bugzilla.kernel.org/>
2008-10-20 23:55 ` [Bugme-new] [Bug 11776] New: Regression: Hardware working with old stock gspca module fails with 2.6.27 module Andrew Morton
2008-10-21 9:10 ` Hans de Goede [this message]
2008-10-21 11:15 ` Mauro Carvalho Chehab
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=48FD9C85.5040102@hhs.nl \
--to=j.w.r.degoede@hhs.nl \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=linuxkernel@lanrules.de \
--cc=mchehab@infradead.org \
--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