From: Robin Gilks <robin.gilks@tait.co.nz>
To: ppc embedded list <linuxppc-embedded@ozlabs.org>
Subject: Building new FEC code on 8xx with 2.6.17 kernel
Date: Fri, 27 Oct 2006 14:41:06 +1300 [thread overview]
Message-ID: <454163B2.4010308@tait.co.nz> (raw)
Greetings
Just having a first stab at building for an 859T based product so I
assume I'll be using the new FEC driver. I'm getting two unresolved
references as follows:
drivers/built-in.o: In function
`fec_8xx_init':fec_main.c:(.init.text+0x1a40): undefined reference to
`fec_8xx_platform_init'
drivers/built-in.o: In function
`fec_8xx_cleanup':fec_main.c:(.exit.text+0x39c): undefined reference to
`fec_8xx_platform_cleanup'
No big deal as I can see an example for the netta platform (whatever
that is) that defines these functions and I can hack that to suit my
hardware - what I can't find is where CONFIG_NETTA is defined. I can't
find it in any Kconfig file, and I want to use the same mechanism for
selecting my platform.
Any ideas? (or is FEC still broken on CPM1 processors)
Cheers
--
Robin
=======================================================================
This email, including any attachments, is only for the intended
addressee. It is subject to copyright, is confidential and may be
the subject of legal or other privilege, none of which is waived or
lost by reason of this transmission.
If the receiver is not the intended addressee, please accept our
apologies, notify us by return, delete all copies and perform no
other act on the email.
Unfortunately, we cannot warrant that the email has not been
altered or corrupted during transmission.
=======================================================================
next reply other threads:[~2006-10-27 1:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-27 1:41 Robin Gilks [this message]
2006-10-27 13:38 ` Building new FEC code on 8xx with 2.6.17 kernel Vitaly Bordug
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=454163B2.4010308@tait.co.nz \
--to=robin.gilks@tait.co.nz \
--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).