All of lore.kernel.org
 help / color / mirror / Atom feed
From: Francesco Schiavarelli <kaboom@tiscalinet.it>
To: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] dvbnet not working anymore with 2.6.25
Date: Mon, 19 May 2008 18:37:44 +0200	[thread overview]
Message-ID: <g0sact$e6d$1@ger.gmane.org> (raw)
In-Reply-To: <g072jh$h25$1@ger.gmane.org>

I've done a bit of testing and seems like the problem it's related to 
kernel version and not v4l-dvb.
I've managed to compile actual v4l-dvb (rev7901) against debian kernel 
2.6.18-4-486 and everything works.
Next step is checking every kernel between 2.6.22-3 and 2.6.25-1 trying 
to isolate the problem.

Anyone guessing which change in the kernel tree may have broken dvbnet?
Suggestions are more than welcome.

Francesco


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

  reply	other threads:[~2008-05-19 16:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-11 15:15 [linux-dvb] dvbnet not working anymore with 2.6.25 Francesco Schiavarelli
2008-05-19 16:37 ` Francesco Schiavarelli [this message]
2008-05-26 21:04   ` Francesco Schiavarelli
2008-10-06 17:13   ` Francesco Schiavarelli

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='g0sact$e6d$1@ger.gmane.org' \
    --to=kaboom@tiscalinet.it \
    --cc=linux-dvb@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 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.