From: Keith Owens <kaos@ocs.com.au>
To: Eyal Lebedinsky <eyal@eyal.emu.id.au>
Cc: linux-kernel@vger.kernel.org,
Kristian Hogsberg <hogsberg@users.sourceforge.net>,
linux1394-devel@lists.sourceforge.net
Subject: Re: Announce: modutils 2.4.9 is available
Date: Wed, 26 Sep 2001 12:33:18 +1000 [thread overview]
Message-ID: <25245.1001471598@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Wed, 26 Sep 2001 11:30:11 +1000." <3BB12FA3.96460B90@eyal.emu.id.au>
On Wed, 26 Sep 2001 11:30:11 +1000,
Eyal Lebedinsky <eyal@eyal.emu.id.au> wrote:
>I just built and installed modutils-2.4.9.
>depmod: Unexpected value (20) in
>'/lib/modules/2.4.10/kernel/drivers/ieee1394/sbp2.o' for
>ieee1394_device_size
> It is likely that the kernel structure has changed, if so then
> you probably need a new version of modutils to handle this
>kernel.
struct ieee1394_device_id in the kernel does not match the layout in
the modutils ieee1394 patch from Kristian Hogsberg. Kristian's patch
to me had an extra field at the end. I suggest adding
void *driver_data;
to the end of struct ieee1394_device_id in
drivers/ieee1394/ieee1394_hotplug.h.
Index: 10.1/drivers/ieee1394/ieee1394_hotplug.h
--- 10.1/drivers/ieee1394/ieee1394_hotplug.h Mon, 13 Aug 2001 14:14:10 +1000 kaos (linux-2.4/Q/e/44_ieee1394_h 1.1 644)
+++ 10.1(w)/drivers/ieee1394/ieee1394_hotplug.h Wed, 26 Sep 2001 12:32:33 +1000 kaos (linux-2.4/Q/e/44_ieee1394_h 1.1 644)
@@ -14,6 +14,7 @@ struct ieee1394_device_id {
u32 model_id;
u32 sw_specifier_id;
u32 sw_specifier_version;
+ void *driver_data;
};
#define IEEE1394_PROTOCOL(id, version) { \
next prev parent reply other threads:[~2001-09-26 2:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-25 7:48 Announce: modutils 2.4.9 is available Keith Owens
2001-09-26 1:30 ` Eyal Lebedinsky
2001-09-26 2:33 ` Keith Owens [this message]
2001-09-26 2:48 ` Ben Collins
2001-09-26 12:52 ` Kristian Hogsberg
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=25245.1001471598@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=eyal@eyal.emu.id.au \
--cc=hogsberg@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
/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