All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Adam Luchjenbroers" <adam@luchjenbroers.com>
To: linux-newbie@vger.kernel.org
Subject: skystar2\mt312 driver does not timeout under kernel 2.6.6
Date: Thu, 20 May 2004 0:35:47 -0500	[thread overview]
Message-ID: <200405200435.AAA87673@m1.name2host.com> (raw)

Under kernel 2.6.6 (modules dvbcore, mt312, skystar2 loaded) dvbtune enters
an infinite polling loop, as shown below.

polling....
Getting frontend event
FE_STATUS:
polling....
Getting frontend event
FE_STATUS: FE_HAS_CARRIER
polling....
Getting frontend event
FE_STATUS:
polling....
Getting frontend event
FE_STATUS: FE_HAS_CARRIER
polling....
Getting frontend event
...

Under 2.4.20 it simply pauses a few seconds then
receives an FE_TIMEDOUT and stops.

The following code has been identified in dvbtune, and it looks simply like
the driver is not responding with an FE_TIMEDOUT where perhaps it should be.

while (((event.status & FE_TIMEDOUT)==0) && ((event.status &
FE_HAS_LOCK)==0)) {
fprintf(stderr,"polling....\n");
if (poll(pfd,1,10000)){
if (pfd[0].revents & POLLIN){
fprintf(stderr,"Getting frontend event\n");
if ((status = ioctl(fd_frontend, FE_GET_EVENT, &event)) < 0){
if (errno != EOVERFLOW) {
perror("FE_GET_EVENT");
fprintf(stderr,"status = %d\n", status);
fprintf(stderr,"errno = %d\n", errno);
return -1;
}
else fprintf(stderr,"Overflow error, trying again (status = %d, errno =
%d)", status, errno);
}
}
print_status(stderr,event.status);
}
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

                 reply	other threads:[~2004-05-20  5:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200405200435.AAA87673@m1.name2host.com \
    --to=adam@luchjenbroers.com \
    --cc=linux-newbie@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.