* [Fwd: Re: How to get rid of unused data in LKM]
@ 2002-07-25 9:07 Dan Taylor
2002-07-25 9:55 ` Matthias Fuchs
0 siblings, 1 reply; 2+ messages in thread
From: Dan Taylor @ 2002-07-25 9:07 UTC (permalink / raw)
To: linuxppc-embedded
-------- Original Message --------
Subject: Re: How to get rid of unused data in LKM
Date: Thu, 25 Jul 2002 02:04:53 -0700
From: Dan Taylor <danieltaylor@attbi.com>
Reply-To: danieltaylor@acm.org
To: Matthias Fuchs <matthias.fuchs@esd-electronics.com>
References: <20020724154914.5C03C10875@denx.denx.de> <3D3FA821.40106@esd-electronics.com>
Couldn't you do a kernel file open during module_init, store the
PCI device code and close the file?
Regards,
Dan
Matthias Fuchs wrote:
>
> Hi Wolfgang,
>
>>
>>
>> Why don't you load the firmware using some ioctl() _after_ loading
>> the module?
>
> Of course this is a good and definetly the default solution. But our
> application requires
> that everything is done by the init function of the module.
> Life would be boring and mailing list obsolete, if we can always use the
> default solutions :-)
>
>>> 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" ?
>
> I think that John is right. __initdata only makes sense, when the module
> is compiled into
> the kernel. But I will check it again, just to be sure.
>
> Matthias
>
>
>
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2002-07-25 9:55 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-07-25 9:07 [Fwd: Re: How to get rid of unused data in LKM] Dan Taylor
2002-07-25 9:55 ` Matthias Fuchs
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).