From: Dan Malek <dan@mvista.com>
To: "Kevin B. Hendricks" <khendricks@ivey.uwo.ca>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: drivers - modules versus compiled in?
Date: Thu, 01 Nov 2001 12:48:20 -0500 [thread overview]
Message-ID: <3BE18AE4.1070507@mvista.com> (raw)
In-Reply-To: 20011031211539.SIZF7882.tomts5-srv.bellnexxia.net@there
Kevin B. Hendricks wrote:
> Are the allocated memory areas differnt?
Yes, this is usually why you may see different behavior. First,
the module itself is allocated from kernel memory that other errant
pointers could access that wouldn't otherwise. Usually, the problem
is related to buffers or data structures the driver allocates that
are further used for DMA operations. Things like 'virt_to_bus()'
won't work on static objects in a module, while it will in a
compiled driver.
> Any hints as to what might have changed?
Provide some hints to us :-). What type of system, what
kernel, what driver?
Thanks.
-- Dan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-11-01 17:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-31 21:18 drivers - modules versus compiled in? Kevin B. Hendricks
2001-11-01 17:48 ` Dan Malek [this message]
2001-11-01 18:01 ` Kevin B. Hendricks
2001-11-01 18:11 ` Kevin B. Hendricks
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=3BE18AE4.1070507@mvista.com \
--to=dan@mvista.com \
--cc=khendricks@ivey.uwo.ca \
--cc=linuxppc-dev@lists.linuxppc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).