From: Peter Asemann <peter.asemann@web.de>
To: linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Creating a configuration for my custom MPC875 board
Date: Mon, 07 Feb 2005 15:53:42 +0100 [thread overview]
Message-ID: <420780F6.70209@web.de> (raw)
Some days ago I was told on this mailinglist I needed to create a custom
configuration in order to get linux running on my custom hardware.
So I did as I was told and created an own <name>_defconfig and entries
in the menu via editing arch/ppc/config.in and so on.
Well, every board seems to include it's custom header file from
platforms/<NAME>.h in the include/asm/mpc8xx.h header file.
Now I'm curious if I also need to include something?
It seems there usually isn't much stuff in the <name>.h file, only an
IMAP_ADDR define and the definition of struct bd_info.
Do I need this stuff - or how do I find out?
Best regards,
Peter Asemann
next reply other threads:[~2005-02-07 14:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-07 14:53 Peter Asemann [this message]
2005-02-07 16:54 ` Creating a configuration for my custom MPC875 board Bryan O'Donoghue
2005-02-08 13:00 ` Wolfgang Denk
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=420780F6.70209@web.de \
--to=peter.asemann@web.de \
--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).