From: "w.n. jacobs" <willy.jacobs@nl.thalesgroup.com>
To: "Nishen Brijraj" <Nishen.Brijraj@za.flextronics.com>
Cc: "w.n. jacobs" <willy.jacobs@nl.thalesgroup.com>,
<shagitgy@techst02.technion.ac.il>,
<linuxppc-embedded@lists.linuxppc.org>
Subject: RE: atm8260-1.0.1
Date: Tue, 16 Sep 2003 15:08:43 +0200 [thread overview]
Message-ID: <16231.2907.456193.80116@gargle.gargle.HOWL> (raw)
In-Reply-To: <742AC4678EF8464697DDDFE3B40F6ECD37DA5E@srv-mailrnd.azisa.co.za>
Nishen Brijraj writes:
> Hello all.
>
> I am using the mpc8260ads board running the 2.4.4 kernel and the phy is
> also the pm5350.
You also need to set the kernel configuation variable:
CONFIG_ATM_VADS=y
and extend the Makefile with vads_phy.o:
obj-$(CONFIG_UTOPIA) += mpc8260sar.o mpc8260sar_detect.o intpool.o mpool.o \
risctimer.o mm.o cpmtimer.o utopia.o debug.o \
mpc8260iop.o vads_phy.o
> In reference to the message below, why can't you use the code as a
> loadable module? I have tried it this way, and it does eventually
> compile and insert, although it doesn't do much else at the moment.
Allocation and de-allocation of buffer descriptors and other buffers in
dual-port memory might give problems.
> I have also tried to compile the code into the kernel, but that is
> proving to be more difficult than just doing what you stated below.
> There are a whole lot of undefined reference errors.
Such as? I compiled it without problems (but without vads_phy.o).
--
willy
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-09-16 13:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-16 12:04 atm8260-1.0.1 Nishen Brijraj
2003-09-16 13:08 ` w.n. jacobs [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-16 13:37 atm8260-1.0.1 Nishen Brijraj
2003-09-15 15:03 atm8260-1.0.1 shagitgy
2003-09-16 6:23 ` atm8260-1.0.1 w.n. jacobs
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=16231.2907.456193.80116@gargle.gargle.HOWL \
--to=willy.jacobs@nl.thalesgroup.com \
--cc=Nishen.Brijraj@za.flextronics.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=shagitgy@techst02.technion.ac.il \
/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).