From mboxrd@z Thu Jan 1 00:00:00 1970 From: "w.n. jacobs" Message-ID: <16231.2907.456193.80116@gargle.gargle.HOWL> Date: Tue, 16 Sep 2003 15:08:43 +0200 To: "Nishen Brijraj" Cc: "w.n. jacobs" , , Subject: RE: atm8260-1.0.1 In-Reply-To: <742AC4678EF8464697DDDFE3B40F6ECD37DA5E@srv-mailrnd.azisa.co.za> References: <742AC4678EF8464697DDDFE3B40F6ECD37DA5E@srv-mailrnd.azisa.co.za> MIME-Version: 1.0 (Generated by Clearswift ES version 4.8.1.149) Content-Type: text/plain; charset=us-ascii Sender: owner-linuxppc-embedded@lists.linuxppc.org List-Id: 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/