From: Matthias Schwarzott <zzam@gentoo.org>
To: linux-media@vger.kernel.org
Cc: Steven Toth <stoth@linuxtv.org>
Subject: struct dvb_frontend not initialized correctly / random id value since MFE merge
Date: Sun, 22 Feb 2009 20:31:59 +0100 [thread overview]
Message-ID: <200902222031.59364.zzam@gentoo.org> (raw)
Hi there!
MFE patches added a variable "id" to struct dvb_frontend.
This variable seems to be uninitialized for some drivers.
The result is for my skystar2 card (using stv0299 frontend) it sometimes is 0
as it should but sometimes it is a random value, so I get this register
message:
DVB: registering adapter 1 frontend -10551321 (ST STV0299 DVB-S)
The related kernel thread then also has a strange name like:
kdvb-ad-1-fe--1
The same happens for my dvb-ttpci card using ves1x93 frontend.
Now I wonder if all frontend drivers should be switched to use kzalloc instead
of kmalloc for struct dvb_frontend, or if it is the bridge driver that should
init the id-value.
What about all other members of this struct? Will they be initialized
correctly?
Regards
Matthias
next reply other threads:[~2009-02-22 19:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-22 19:31 Matthias Schwarzott [this message]
2009-02-22 23:44 ` struct dvb_frontend not initialized correctly / random id value since MFE merge Andreas Oberritter
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=200902222031.59364.zzam@gentoo.org \
--to=zzam@gentoo.org \
--cc=linux-media@vger.kernel.org \
--cc=stoth@linuxtv.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