From: Eugene Surovegin <ebs@ebshome.net>
To: Aleck Lin <aleck@gdatech.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Ethernet driver for Linux kernel 2.6 running on ML403
Date: Wed, 13 Sep 2006 18:48:52 -0700 [thread overview]
Message-ID: <20060914014852.GA8375@gate.ebshome.net> (raw)
In-Reply-To: <002501c6d79e$cca7ee40$800101df@monstertop>
On Wed, Sep 13, 2006 at 06:40:40PM -0700, Aleck Lin wrote:
> Hi,
>
> I'm able to boot Linux 2.6 on ML403 board (with a ramdisk file system).
>
> However, during the kernel booting, it complains that "No network devices
> available," So I figured I probably didn't enable the ethernet driver in the
> kernel.
>
> >From doing "make menuconfig", under "Device Drivers" --> "Network device
> support" --> "Ethernet(10 or 100Mbit)", I checked the box of both "Ethernet
> (10 or 100Mbit)" and "PowerPC 4xx on-chip Ethernet support." I then
> save/exit the menuconfig to compile the kernel again. I've attached the
> error output at the bottom.
>
> The problem is that I don't have any define in my .config file that matches
> "CONFIG_405GP", "CONFIG_405GPR" or "CONFIG_405EP" in the
> /drivers/net/ibm_emac/ibm_emac.h file, so it complains that I might not have
> correct defines.
Yes, I put that check there exactly to prevent people from using my
driver on non-compatible hardware :).
> 1st question: Which one of the CONFIG_405xxx should I use? I was searching
> around but couldn't find an answer, but my intuition tells me that it should
> probably be CONFIG_405GP.
No.
> 2nd question: So I decided to try with CONFIG_405GP just to see what
> happens. However, some compilation errors were still there. And it complains
> about "dereferencing pointer to incomplete type". Does anyone have any
> experience working with this driver and perhaps found that there's an error
> in the kernel for this driver?
This driver isn't for your chip and simply cannot work.
--
Eugene
next prev parent reply other threads:[~2006-09-14 1:55 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.241.1158193867.2423.linuxppc-embedded@ozlabs.org>
2006-09-14 1:40 ` Ethernet driver for Linux kernel 2.6 running on ML403 Aleck Lin
2006-09-14 1:48 ` Eugene Surovegin [this message]
2006-09-14 1:52 ` Grant Likely
2006-09-14 11:18 ` David H. Lynch Jr.
2006-09-14 13:53 ` Michael Galassi
2006-09-14 14:34 ` Grant Likely
2006-09-14 15:47 ` Keith J Outwater
2006-09-14 22:57 ` Grant Likely
2006-09-19 7:48 ` Peter Korsgaard
2006-09-19 14:17 ` Grant Likely
2006-09-19 20:10 ` Grant Likely
2006-09-19 20:40 ` David H. Lynch Jr.
2006-09-19 21:27 ` Grant Likely
2006-09-24 5:42 ` David H. Lynch Jr.
2006-09-24 14:35 ` Grant Likely
2006-09-14 23:02 ` David H. Lynch Jr.
2006-09-14 16:40 John Bonesio
2006-09-14 17:36 ` Keith J Outwater
2006-09-14 22:02 ` T Ziomek
2006-09-14 23:16 ` David H. Lynch Jr.
2006-09-14 22:49 ` Grant Likely
2006-09-15 16:11 ` T Ziomek
2006-09-19 10:13 ` Peter Korsgaard
2006-09-19 18:06 ` Andrew
-- strict thread matches above, loose matches on Subject: below --
2006-09-14 17:52 John Bonesio
2006-09-14 23:08 ` Keith J Outwater
2006-09-15 0:08 ` David H. Lynch Jr.
2006-09-15 1:14 ` David H. Lynch Jr.
2006-09-15 19:13 John Bonesio
2006-09-19 14:16 ` Grant Likely
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=20060914014852.GA8375@gate.ebshome.net \
--to=ebs@ebshome.net \
--cc=aleck@gdatech.com \
--cc=linuxppc-embedded@ozlabs.org \
/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).