linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dag Nygren <dag@newtech.fi>
To: <linuxppc-embedded@lists.linuxppc.org>
Cc: dag@newtech.fi
Subject: PPC embedded plans ?
Date: Tue, 21 Aug 2001 09:52:40 +0300	[thread overview]
Message-ID: <20010821065240.1853.qmail@dag.newtech.fi> (raw)


Hi,

I have a working 2.4.2 port for a board for SBS-or (VG4) here
and wanted to migrate this port to 2.4.9.

Checking out the sources I think I  can notice that there is a strong
push towards some kind of "one file" machine definition.

Is this right ?
And what would be the best 2.4.9 to start out with ?
Any written policy on the setup of the machine dependant stuff ?
Any way of getting my board defs into the official (?) PPC source tree ?

BRGDS


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

             reply	other threads:[~2001-08-21  6:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-21  6:52 Dag Nygren [this message]
2001-08-21 10:49 ` PPC embedded plans ? Matt Porter
2001-08-21 15:19 ` Tom Rini

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=20010821065240.1853.qmail@dag.newtech.fi \
    --to=dag@newtech.fi \
    --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).