linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@mvista.com>
To: Oliver Brown <obrown@adventnetworks.com>
Cc: linuxppc-embedded List <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Module support for 8260 in 2.4(.1) kernel
Date: Fri, 20 Apr 2001 15:22:20 -0400	[thread overview]
Message-ID: <3AE08C6C.2D2F3B3F@mvista.com> (raw)
In-Reply-To: CD5CA14300A9D54A8D13D58CD3C87B422DD731@advcorp-exc01.advent.com


Oliver Brown wrote:

> 2. The m8260_cpm_hostalloc() and m8260_cpm_dpalloc do not have deallocs.
> I can load my module, but I can't unload it.

Yep....I have some patches and someday I may fix it.


> I've added an init_module and cleanup_module to the fcc_enet.c from
> (bitkeeper 2.5 tree).

Since it won't work properly as a module, I would prefer you didn't
do this.  One of the reasons the CPM drivers aren't modules is there
are configuration dependencies built into the drivers.  You don't
have the flexibility to arbitrarily select any I/O configuration
at any time, the drivers have to know what may be conflicting and
avoid these configurations.  While there is an academic challenge
to make this extremely flexible, I haven't seen any production value
to this feature in use by people building real products.  If you
really need the driver, you have to build it in with consideration
of other drivers.


	-- Dan

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

  parent reply	other threads:[~2001-04-20 19:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-20 18:51 Module support for 8260 in 2.4(.1) kernel Oliver Brown
2001-04-20 19:03 ` Tom Rini
2001-04-20 19:22 ` Dan Malek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-04-20 19:26 Oliver Brown
2001-04-20 21:00 Oliver Brown
2001-04-20 21:34 Oliver Brown

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=3AE08C6C.2D2F3B3F@mvista.com \
    --to=dan@mvista.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=obrown@adventnetworks.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).