From: Randy Dunlap <rdunlap@xenotime.net>
To: Yang Bai <hamo.by@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Q: What will happen if I insmod a new version driver when it has already been statically in kernel?
Date: Mon, 27 Aug 2012 16:38:33 -0700 [thread overview]
Message-ID: <503C04F9.5070808@xenotime.net> (raw)
In-Reply-To: <CAO_0yfNxa9m0BR-MxMezC-CZ8M=JkOmnLrpWyUcti-cT8f3zzA@mail.gmail.com>
On 08/27/2012 03:06 AM, Yang Bai wrote:
> Hi all,
>
> We have one driver which has been statically compiled into kernel, and
> now we want to upgrade it. But we only have a new version module for
> this driver. Could I just insmod this module and make the new driver
> work?
No, that should not work -- unless the in-kernel driver has a
close/release method that you can somehow trigger.
> If so, what happens to the static old one?
It stays.
> If not, Can we upgrade this driver without re-compile the kernel to
> make the in-kernel driver out or module?
If the current driver is not a loadable module, you cannot
replace it. Assuming that they use mostly the same resources,
like I/O devices or memory BARs or however the device presents
its control & data interfaces, the new module would not be
able to access the device interfaces since they would still
be used/owned by the in-kernel driver.
--
~Randy
prev parent reply other threads:[~2012-08-27 23:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-27 10:06 Q: What will happen if I insmod a new version driver when it has already been statically in kernel? Yang Bai
2012-08-27 23:38 ` Randy Dunlap [this message]
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=503C04F9.5070808@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=hamo.by@gmail.com \
--cc=linux-kernel@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.