From: "Joshua Lamorie" <jpl@xiphos.ca>
To: "Richard Danter" <richard.danter@ntlworld.com>,
"linuxppc-embedded" <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Simple module, but won't build
Date: Tue, 4 May 2004 15:38:53 -0400 [thread overview]
Message-ID: <007c01c4320f$6fd477b0$6f01a8c0@xiphos.ca> (raw)
In-Reply-To: 4097DAEA.5@ntlworld.com
> /opt/eldk3.0/ppc_82xx/usr/include/asm/io.h:235: `CONFIG_KERNEL_START'
> /opt/eldk3.0/ppc_82xx/usr/include/asm/uaccess.h:37: `CONFIG_TASK_SIZE'
These are defined when you are building your kernel. Before building any
modules,
you need to configure the kernel.
Assuming you use 'make menuconfig'.
Under 'Code Maturity Level Options' select 'Prompt for advanced kernel
configuration options'.
Then, under General Setup set
Set Custom Kernel Base Address
Set Custom user task size
My assumption is that the defaults (0xc0000000 and 0x80000000) are just
dandy.
Joshua
p.s. This type of question is easy to answer by using lxr.linux.no and
searching for freetext or identifier. No kernel programming should be
performed without this close at hand.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-05-04 19:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-04 18:03 Simple module, but won't build Richard Danter
2004-05-04 19:10 ` 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 ` Joshua Lamorie [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-08-31 22:55 Simple module, but won't build 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='007c01c4320f$6fd477b0$6f01a8c0@xiphos.ca' \
--to=jpl@xiphos.ca \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=richard.danter@ntlworld.com \
/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).