From: Brendan Simon <bsimon@ctam.com.au>
To: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: mpc8xx-2.3.10 directory structure
Date: Tue, 14 Sep 1999 13:23:43 +1000 [thread overview]
Message-ID: <37DDBFBF.FF1DF439@ctam.com.au> (raw)
I downloaded the mpc8xx-2.3.10 archive last night. I was happy with the
configuration changes for 8xx targets though I will need to add and
Ethernet on SCC3 for our board.
I noticed that all the 860 board variants MBX, RPX and BSE are all
contained within the mbxboot directory tree. This makes it easy to
maintain if the bootload stuff is very similar. I was hoping to keep my
stuff speperated as much as possible from the mbxboot directory. I
guess I am reasonably happy with this directory structure if the name
mbxboot was changed to something more generic (maybe 8xxboot or
boot8xx).
I can't remember which file it was now (embed_config.c I think) which
has bse_cfg(), rpx_cfg() etc. I would have thought it would make sense
to split board specific stuff into there own files. Each new board
would have it's own file for the board specific functions.
For now I'll just hack away in the mbxboot directory and try not to
create any files just to make the configuration and build process
easier. I'll probably seperate my stuff to a different file at a later
stage and move all the stuff out of the mbxboot directory to our own
directory if need be.
Any comments on the directory structure for 8xx stuff ?
Brendan Simon.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
reply other threads:[~1999-09-14 3:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=37DDBFBF.FF1DF439@ctam.com.au \
--to=bsimon@ctam.com.au \
--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).