From: "Daniel W. S. Almeida" <dwlsalmeida@gmail.com>
To: "mchehab@kernel.org" <mchehab@kernel.org>
Cc: "skhan@linuxfoundation.org" <skhan@linuxfoundation.org>,
"Linux Media Mailing List" <linux-media@vger.kernel.org>,
"linux-kernel-mentees@lists.linuxfoundation.org"
<linux-kernel-mentees@lists.linuxfoundation.org>
Subject: modprobing 'vidtv' doesn't really do anything
Date: Sat, 16 May 2020 19:09:35 -0300 [thread overview]
Message-ID: <DE1E173D-8D56-4CA5-9838-E9476B24DD69@getmailspring.com> (raw)
Hi Mauro!
I am trying to iron out the bugs in the virtual DVB driver I have been
working on for the past few months.
modprobing vidtv_bridge apparently works, i.e. 'vidtv_bridge' gets
listed in the output of 'lsmod' and there's a message on dmesg warning
against loading out of tree modules.
It does not seem like the probe function actually runs, though. I have
added a printk call in vidtv_bridge_i2c_probe() but it does not output
anything to dmesg.
Also, I am using QEMU + KGDB and the debugger does not break into this
function (or into any other function in vidtv_bridg.c) at all, although
it can actually get the addresses for them, i.e.
4 breakpoint keep y 0xffffffffc0000025 in
vidtv_bridge_i2c_probe at drivers/media/test-drivers/vidtv/vidtv_bridg.c:373
5 breakpoint keep y 0xffffffffc0000523 in
vidtv_bridge_i2c_remove at drivers/media/test-drivers/vidtv/vidtv_bridg.c:416
It can't find these, though:
2 breakpoint keep y <PENDING> drivers/media/test-drivers/vidtv/vidtv_bridg.c:vidtv_bridge_driver_exit
3 breakpoint keep y <PENDING> drivers/media/test-drivers/vidtv/vidtv_bridg.c:vidtv_bridge_driver_init
>The best is to start using dvbv5 tools inside v4l-utils.
>The first step to check if the demod code was properly loaded is to run:
>$ dvb-fe-tool
I tried this, but to no avail.
>WARNING device dvb0.frontend0 not found
I am stuck, can I get some help with this issue?
Thanks!
-Daniel
next reply other threads:[~2020-05-16 22:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-16 22:09 Daniel W. S. Almeida [this message]
[not found] <20200517014237.30e521dd@coco.lan>
2020-05-17 0:04 ` modprobing 'vidtv' doesn't really do anything Daniel W. S. Almeida
[not found] <20200517022115.5ce8136c@coco.lan>
2020-05-19 7:13 ` Daniel W. S. Almeida
[not found] <20200519104834.3c4bf5d7@coco.lan>
2020-05-20 7:22 ` Daniel W. S. Almeida
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=DE1E173D-8D56-4CA5-9838-E9476B24DD69@getmailspring.com \
--to=dwlsalmeida@gmail.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=skhan@linuxfoundation.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;
as well as URLs for NNTP newsgroup(s).