From: Devin Heitmueller <dheitmueller@kernellabs.com>
To: Markus Rechberger <mrechberger@gmail.com>
Cc: Edouard Marquez <animatrix30@gmail.com>, linux-media@vger.kernel.org
Subject: Re: Invalid module format
Date: Wed, 9 Sep 2009 15:09:52 -0400 [thread overview]
Message-ID: <829197380909091209x382089beqe805bf2b0895a67f@mail.gmail.com> (raw)
In-Reply-To: <d9def9db0909091202x64b54600s4c499f0f4042a8e6@mail.gmail.com>
On Wed, Sep 9, 2009 at 3:02 PM, Markus Rechberger<mrechberger@gmail.com> wrote:
> this is not true my old driver which is not available anymore did not
> ship any other modules aside the em28xx driver itself.
> This is a video4linux issue and has nothing to do with it.
>
> Best Regards,
> Markus
>
Hello Marks,
While it is true that your driver did not include anything other than
em28xx, I assume it is compiled against a certain set of v4l2 headers,
and if those headers change (such as changes to data structures), then
the em28xx modules you distributed would not work with that version of
the v4l2 modules.
If he wants to use your driver, I would assume he would need to
reinstall the stock kernel (overwriting whatever locally built version
of v4l-dvb he previously installed).
Cheers,
Devin
--
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com
next prev parent reply other threads:[~2009-09-09 19:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-09 16:14 Invalid module format Edouard Marquez
2009-09-09 16:19 ` Devin Heitmueller
[not found] ` <c2885d2b0909091113h2ae6e27ai7541b3efac0e4606@mail.gmail.com>
2009-09-09 18:20 ` Devin Heitmueller
[not found] ` <c2885d2b0909091134w1264b827kf5d4254634bed1d9@mail.gmail.com>
2009-09-09 18:39 ` Devin Heitmueller
2009-09-09 19:02 ` Markus Rechberger
2009-09-09 19:08 ` Markus Rechberger
2009-09-09 19:09 ` Devin Heitmueller [this message]
2009-09-09 19:40 ` Markus Rechberger
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=829197380909091209x382089beqe805bf2b0895a67f@mail.gmail.com \
--to=dheitmueller@kernellabs.com \
--cc=animatrix30@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=mrechberger@gmail.com \
/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