From: Halim Sahin <halim.sahin@t-online.de>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Trent Piepho <xyzzy@speakeasy.org>, linux-media@vger.kernel.org
Subject: Re: bttv problem loading takes about several minutes
Date: Wed, 17 Jun 2009 22:41:49 +0200 [thread overview]
Message-ID: <20090617204149.GA12617@halim.local> (raw)
In-Reply-To: <200906172206.27230.hverkuil@xs4all.nl>
Hi,
On Mi, Jun 17, 2009 at 10:06:26 +0200, Hans Verkuil wrote:
> The log is from bttv version 0.9.17. The new code is only present in version
> 0.9.18. So this is definitely not related to any of my changes.
>
Yes it's from a debian lenny kernel 2.6.26.
But I have tested latest v4l-dvb with the same result
under 2.6.28 (ubuntu 9.04).
> The code in bttv_probe (bttv-driver.c) does this:
>
> if (bttv_verbose)
> bttv_gpio_tracking(btv,"init");
>
> /* needs to be done before i2c is registered */
> bttv_init_card1(btv);
>
> /* register i2c + gpio */
> init_bttv_i2c(btv);
>
> /* some card-specific stuff (needs working i2c) */
> bttv_init_card2(btv);
>
> So it looks like it can be either bttv_init_card1 or init_bttv_i2c that is
> causing the delay.
>
> Halim, can you try to put some printk() statements in between the calls
> above to see which call is taking so long? Actually, it would be nice if
> you are able to 'drill-down' as well in whatever function is causing the
> delay, since I truly don't see what might be delaying things for you.
Yes I will test this tomorrow.
Thanks a lot!
Halim
next prev parent reply other threads:[~2009-06-17 20:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 16:24 bttv problem loading takes about several minutes Halim Sahin
2009-06-17 17:11 ` Trent Piepho
2009-06-17 19:38 ` Halim Sahin
2009-06-17 20:06 ` Hans Verkuil
2009-06-17 20:41 ` Halim Sahin [this message]
2009-06-18 9:58 ` Halim Sahin
2009-06-18 10:18 ` ok more details: " Halim Sahin
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=20090617204149.GA12617@halim.local \
--to=halim.sahin@t-online.de \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=xyzzy@speakeasy.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