From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Gerd Kautzmann <G.Kautzmann@PRIMES.de>
Cc: "buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] Camera Driver diesn't provide 60 FPS
Date: Tue, 22 Aug 2023 12:09:01 +0200 [thread overview]
Message-ID: <20230822120901.41a17d89@windsurf> (raw)
In-Reply-To: <1619D009AA8C9E469331A8EE22395AEC8D762350@Exchange2013.PRIMES.local>
Hello Gerd,
On Tue, 22 Aug 2023 09:39:06 +0000
Gerd Kautzmann <G.Kautzmann@PRIMES.de> wrote:
> I finally managed to build an linux image suporting my imx296 camera
> on the Raspberry-Pi 4 (32 bit) over loadable kernel modules. There
> where good examples for building a helloworld kernel module. At first
> everything looked fine, but than I realised the camera is limited to
> 30 frames per second. I compiled a test program confirming the
> problem under the build root kernel. On a, standart Raspbi image
> (Debian) I got 60 fps using the same drivers (compiled and installed
> over dpkg) with the same settings in the boot-filesystem. The driver
> is reporting the camera to be able to do 60 fps but test program (and
> application) are only reaching 30 fps.
>
> Are there any ideas about settings in the configuration concerning
> cameras I might have missed?
This really isn't a Buildroot-related question, so I'm not sure this
mailing list is the most relevant place to get support on this
question. It's really a RaspberryPi-specific question.
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-08-22 10:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 9:39 [Buildroot] Camera Driver diesn't provide 60 FPS Gerd Kautzmann
2023-08-22 10:09 ` Thomas Petazzoni via buildroot [this message]
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=20230822120901.41a17d89@windsurf \
--to=buildroot@buildroot.org \
--cc=G.Kautzmann@PRIMES.de \
--cc=thomas.petazzoni@bootlin.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