From: Adrian Cox <apc@agelectronics.co.uk>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: embedded PowerPC porting coordination [was Re: Motorola Web Site]
Date: Sat, 31 Jul 1999 09:57:22 +0100 [thread overview]
Message-ID: <37A2BA72.6478427F@agelectronics.co.uk> (raw)
In-Reply-To: 37A19963.AE7DBE66@mitre.org
Charles Lepple wrote:
> Wolfgang Denk wrote:
> > To support a broader range ofborads some cleanup is necessary,
> > isolating HW dependent parts of the code in "BSP" like groups,
> > allowing for easier configuration of device configuration, port pin
> > assignment etc.
>
> I'm not exactly volunteering for the job of coordinating this, but I
> would have to agree. Would it make sense to start another list
> ("linuxppc-embedded," perhaps?) to discuss this at greater length?
Another thing to consider - linuxppc-dev is already a mix of PPC kernel
development, and linuxppc distribution userspace issues. I've ported
2.2.10 to my embedded board, but I'm using a Debian userspace.
The PPC kernel is halfway towards a sensible BSP structure already - all
it needs is some tidying up, a sensible directory structure for BSPs,
and a few new conditions like CONFIG_PPC_HAVE_OPEN_FIRMWARE. The main
area to work on is arch/ppc/mm/init.c, which has to have too many board
specific functions in its current form.
- Adrian Cox, AG Electronics.
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next prev parent reply other threads:[~1999-07-31 8:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199907290636.IAA07134@denx.muc.de>
1999-07-30 12:24 ` embedded PowerPC porting coordination [was Re: Motorola Web Site] Charles Lepple
1999-07-31 8:57 ` Adrian Cox [this message]
1999-07-31 10:48 ` Hartmut Koptein
1999-07-31 17:53 ` 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=37A2BA72.6478427F@agelectronics.co.uk \
--to=apc@agelectronics.co.uk \
--cc=linuxppc-dev@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).