linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: Matthias Fuchs <matthias.fuchs@esd-electronics.com>
Cc: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: How to get rid of unused data in LKM
Date: Wed, 24 Jul 2002 17:49:09 +0200	[thread overview]
Message-ID: <20020724154914.5C03C10875@denx.denx.de> (raw)
In-Reply-To: Your message of "Wed, 24 Jul 2002 13:39:18 +0200." <3D3E91E6.4000500@esd-electronics.com>


In message <3D3E91E6.4000500@esd-electronics.com> you wrote:
>
> I am writing a LKM that contains a huge constant array of data that is used
> as firmware for a PCI card that is connected to the system where the LKM is loaded.
>
> The module_init function writes the constant data array into the PCI card's RAM and triggers
> a CPU on that card to jump to the firmware code. This works fine.

Why don't you load the firmware using some  ioctl()  _after_  loading
the module?

> But after doing so, the firmware data is still wasting kernel memory on the host system
> and is not used anymore.
> How can I free that memory ? Is there a better way to handle that data ?

If you really think you must link the data with the  module:  Declare
it using "__initdata" ?

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
This is an unauthorized cybernetic announcement.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-07-24 15:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-24 11:39 How to get rid of unused data in LKM Matthias Fuchs
2002-07-24 15:49 ` Wolfgang Denk [this message]
2002-07-24 16:21   ` John Tyner

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=20020724154914.5C03C10875@denx.denx.de \
    --to=wd@denx.de \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=matthias.fuchs@esd-electronics.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;
as well as URLs for NNTP newsgroup(s).