From: Adam Kaczynski <kaczor@dgt-lab.com.pl>
To: Alex Zeffertt <ajz@cambridgebroadband.com>
Cc: Sanjay Kumar <skumar@giga-stream.de>,
"linuxppc-embedded@lists.linuxppc.org"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: m8260_cpm_dpfree( )
Date: Mon, 28 Jul 2003 22:13:44 +0200 [thread overview]
Message-ID: <3F2583F8.9060300@dgt-lab.com.pl> (raw)
In-Reply-To: 1059403782.2835.193.camel@zambia.cambridgebroadband.com
Alex Zeffertt wrote:
> Sanjay,
>>1. where can I get m8260_cpm_dpfree() function implementation ?
> You could try porting the dpfree function in
> arch/ppc/8xx_io/commproc.c. However, this function should only really
> be necessary if you wish to rmmod the driver.
>
I had the same problem last year when I was working with the simple ATM
driver
(http://www.dgt-lab.com.pl/Serwis/ATMdrv8260.tar.gz )
and I decided to make a kind of not very nice looking work-around -
simply to grab and later free the block of memory I needed from the top.
This feature was important for us to debug the driver since I was able
to load, test and later rmmod the driver. However this work-around would
work only if the driver is loaded as the last one (from the drivers
using dp_mem).
I think that there is no reason to implement any more robust allocator
for dp memory since it is used only for very special purposes, allocated
only during drivers initialization and because this resource is so
limited that any normal allocation mechanism (with a pool of memory
blocks) would be inefficient.
Regards,
Adam
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-07-28 20:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-28 13:15 m8260_cpm_dpfree( ) Sanjay Kumar
2003-07-28 14:49 ` Alex Zeffertt
2003-07-28 20:13 ` Adam Kaczynski [this message]
2003-07-29 6:15 ` Pantelis Antoniou
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=3F2583F8.9060300@dgt-lab.com.pl \
--to=kaczor@dgt-lab.com.pl \
--cc=ajz@cambridgebroadband.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=skumar@giga-stream.de \
/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).