linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "vincent.liu" <vincent.liu@bmrtech.com>
To: "linuxppc-dev" <linuxppc-dev@ozlabs.org>
Subject: help  linux for linux2.6
Date: Fri, 9 Nov 2007 14:39:04 +0800	[thread overview]
Message-ID: <200711091439036094772@bmrtech.com> (raw)
In-Reply-To: 200711091434079212507@bmrtech.com

Hi 
These days I am working on a MPC8270 based board with linux 2.6.10 kernel.
When I use the default kernel and load the uImage to the target board.
The kernel hangs after uncompressing kernel image ... ok .
I am freshman in the embedded linux area,So I do not know how to go on this project.
>From internet , I searched many articles,and no gain.
Please help me .
Thanks a lot.
 				
--------------
vincent.liu
2007-11-09

       reply	other threads:[~2007-11-09  6:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200711091434079212507@bmrtech.com>
2007-11-09  6:39 ` vincent.liu [this message]
2007-11-09 17:15   ` help linux for linux2.6 Scott Wood

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=200711091439036094772@bmrtech.com \
    --to=vincent.liu@bmrtech.com \
    --cc=linuxppc-dev@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).