linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: grant.likely@secretlab.ca
To: linuxppc-dev@ozlabs.com
Subject: [PATCH 0/4] Series short description
Date: Thu, 19 Jul 2007 12:34:15 -0600	[thread overview]
Message-ID: <20070719183415.7458.42622.stgit@trillian> (raw)

The following series makes the mpc8349emitx* cuImage work 'out of the box'
Major changes are adding the linux,network-index property to the Ethernet
nodes and adding a default linux,stdout-path to the .dts files.  With
these changes, a cuImage created by 'make mpc834x_itx_defconfig; make zImage'
should boot without changes.

Cheers,
g.

--
Grant Likely, B.Sc. P.Eng.
Secret Lab Technologies Ltd.

             reply	other threads:[~2007-07-19 18:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-19 18:34 grant.likely [this message]
2007-07-19 18:37 ` [PATCH 1/4] bootwrapper: In cuImage, print message for ENET devices not found in tree Grant Likely
2007-07-19 18:37 ` [PATCH 2/4] mpc8349: Add linux,network-index to ethernet nodes in device tree Grant Likely
2007-07-19 18:37 ` [PATCH 3/4] mpc8349emitx: Add chosen node for default stdout path Grant Likely
2007-07-19 18:59   ` Scott Wood
2007-07-19 19:43     ` Grant Likely
2007-07-19 19:58       ` Jerry Van Baren
2007-07-19 20:00         ` Grant Likely
2007-07-19 21:40       ` Kim Phillips
2007-07-19 21:44         ` Scott Wood
2007-07-19 22:28           ` Kim Phillips
2007-07-20  2:00           ` Jerry Van Baren
2007-07-20 16:14             ` Scott Wood
2007-07-20 16:46               ` Jerry Van Baren
2007-07-23 13:12             ` Timur Tabi
2007-07-19 22:12         ` Grant Likely
2007-07-19 18:37 ` [PATCH 4/4] mpc8349emitx(gp): update defconfigs for 2.6.23 Grant Likely

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=20070719183415.7458.42622.stgit@trillian \
    --to=grant.likely@secretlab.ca \
    --cc=linuxppc-dev@ozlabs.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).