From: Tom Rini <trini@kernel.crashing.org>
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 12:03:29 -0700 [thread overview]
Message-ID: <20010420120329.B13403@opus.bloom.county> (raw)
In-Reply-To: <CD5CA14300A9D54A8D13D58CD3C87B422DD731@advcorp-exc01.advent.com>; from obrown@adventnetworks.com on Fri, Apr 20, 2001 at 01:51:00PM -0500
On Fri, Apr 20, 2001 at 01:51:00PM -0500, Oliver Brown wrote:
> I am working on loadable driver modules for the 8260. I had to make the
> changes below to the ppc_ksyms.c file to export the symbols in needed.
>
> The problems I am having are
> 1. The udelay marco is not exportable. Is there a substitute? For now I
> am using __delay() which is not a constant delay.
Er, you should be able to at least kludge around this and use __udelay
which skips the macro (which just does sanity checks).
> 2. The m8260_cpm_hostalloc() and m8260_cpm_dpalloc do not have deallocs.
> I can load my module, but I can't unload it.
>
> I've added an init_module and cleanup_module to the fcc_enet.c from
> (bitkeeper 2.5 tree). Also, I had to replace all of the udelay()'s with
> __delay()'s. And I've diabled the MDIO PHY support.
Er, what tree is this vs exactly? Also, can you send a unified diff
next time?
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-04-20 19:03 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 [this message]
2001-04-20 19:22 ` Dan Malek
-- 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=20010420120329.B13403@opus.bloom.county \
--to=trini@kernel.crashing.org \
--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).