linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Richard Danter <richard.danter@ntlworld.com>
To: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Simple module, but won't build
Date: Tue, 04 May 2004 19:03:22 +0100	[thread overview]
Message-ID: <4097DAEA.5@ntlworld.com> (raw)


Hi All,

I am trying to build a simple module which will let me write to a bank
of LED's on my board.

When I #include <asm/io.h> I get this error:

/opt/eldk3.0/ppc_82xx/usr/include/asm/io.h: In function `virt_to_bus':
/opt/eldk3.0/ppc_82xx/usr/include/asm/io.h:235: `CONFIG_KERNEL_START'
undeclared (first use in this function)

the error also occurs in several other functions. I also see errors when
I #include <asm/uaccess.h> as follows:

/opt/eldk3.0/ppc_82xx/usr/include/asm/uaccess.h: In function `verify_area':
/opt/eldk3.0/ppc_82xx/usr/include/asm/uaccess.h:37: `CONFIG_TASK_SIZE'
undeclared (first use in this function)

also in several functions.

I know I have used these with no problems with an older kernel and
compiler. Is there something I need to add to make these work??

I am using ELDK 3.0 with the 2.4.24-pre2 kernel on an 8260 target.

Many thanks,
Rich

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2004-05-04 18:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-04 18:03 Richard Danter [this message]
2004-05-04 19:10 ` Simple module, but won't build Wolfgang Denk
2004-05-04 19:46   ` Richard Danter
2004-05-04 20:19     ` Wolfgang Denk
2004-05-04 21:15     ` Sam Ravnborg
2004-05-04 21:46       ` Wolfgang Denk
2004-05-04 23:50         ` Next steps Brian Hawley
2004-05-05 12:19           ` Bob White
2004-05-04 19:38 ` Simple module, but won't build Joshua Lamorie
  -- strict thread matches above, loose matches on Subject: below --
2006-08-31 22:55 Steven Kaiser
2006-09-01  6:35 ` Josu Onandia
2006-09-06 19:29 Steven Kaiser

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=4097DAEA.5@ntlworld.com \
    --to=richard.danter@ntlworld.com \
    --cc=linuxppc-embedded@lists.linuxppc.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).