Well, I finally got the latest version running (see my other message to
this list... where did that go, anyway?). The problem was that the code to
deal with CONFIG_PROC_FS is causing a crash... and it looks like it might
be a toolchain bug.
What toolchain are you using?
Hopefully my last message will get through... but basically e1000_main.c
references and extern struct pointer, and the code generated doesn't look
right -- it does a lui v0,0x0 and then a lw v0,0(v0) which causes a crash.
If you're not seeing this, then maybe I'm doing something wrong.
What CFLAGS are you using? I had to modify mine based on an old e-mail
from someone (Pete?) that I found via google.
On Fri, Feb 22, 2002 at 11:59:34PM -0800, Kevin Paul Herbert wrote:
> At 4:22 PM -0800 2/22/02, Matthew Dharm wrote:
> >Does anyone here have the e1000.o driver from Intel for their gigabit
> >ethernet devices working on a MIPS?
> >After overcoming the intitial CFLAGS problem, the darned thing just
> >seems to keep crashing on me during initialization. I'm looking for a
> >datapoint to suggest that it's either (a) a problem with my linux
> >port, or (b) a problem with their driver.
> >Matthew D. Dharm Senior Software Designer
> >Momentum Computer Inc. 1815 Aston Ave. Suite 107
> >(760) 431-8663 X-115 Carlsbad, CA 92008-7310
> >Momentum Works For You www.momenco.com
> I have the e1000 driver working... I've had 3.0 and 3.5 working. The
> only changes that I made were related to the specifics of the
> software defined I/O pins. Are you sure that you have ioremap() and
> your PCI subsystem working correctly? Have you tested any other
> devices that use registers in PCI memory space, or just PCI i/o space?
Matthew Dharm Work: firstname.lastname@example.org
Senior Software Designer, Momentum Computer