linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "woyuzhilei" <woyuzhilei@163.com>
To: "Grant Likely" <grant.likely@secretlab.ca>
Cc: linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: Re: Problems on porting linux 2.6 to xilinx ML410
Date: Sat, 25 Aug 2007 15:37:14 +0800	[thread overview]
Message-ID: <200708251537084534299@163.com> (raw)
In-Reply-To: fa686aa40708241121s359fbaf2r7adb8886a2d3ff65@mail.gmail.com

[-- Attachment #1: Type: text/plain, Size: 1966 bytes --]


Thank you very much for your help!I think there may be somthing wrong with my kernel command  line.



woyuzhilei
2007-08-25



发件人: Grant Likely
发送时间: 2007-08-25 02:21:11
收件人: woyuzhilei
抄送: linuxppc-embedded
主题: Re: Problems on porting linux 2.6 to xilinx ML410

On 8/23/07, woyuzhilei  <woyuzhilei@163.com > wrote:
>
>
> Hey:
>     Recently I'm doing some project on Xilinx Ml410 evaluation board.The
> first step is porting linux 2.6 to ml410,but I got some problems on this,and
> my project cann't proceed,so I come to you for some help.
>     I use the linux kernel source tree download from
> http://git.secretlab.ca/git/linux-2.6-virtex.git  (The
> latest one).Add the file the xparameters.h,xparameter_ml40x.h.  Then add
> arch/ppc/platforms/4xx/xilinx_generic_ppc.c(Use the patch I
> get here),and change it's name to ml40x.c,then I make some necessay change
> of the configuration files to accept selecting a Ml40x type board.

You shouldn't need to do all of this; only the xparameters_ml40x.h
file is needed.  To get started, I'd just use replace
xparameters_ml403.h with your custom xparameters_ml40x.h and use the
ml403 board port.  Once you've got it booting, you can get more fancy.

> Then
> compile the kernel,and get the image file from arch/ppc/boot/images, (On
> kernel compiling,the only device driver  I sellect is " 8250/16550 and
> compatible serial support ").After that  I download the zImage.elf file to
> the target board,and run it.But there is no output from the serial port at
> all.Am I doing somthing wrong?I really don't know goes wrong.
>     Can anyone here help me with this?Any help from you is appreciated.Thank
> you very much!

Make sure you've got 16550 console support enabled and
'console=/dev/ttyS0' in your kernel command line.

Cheers,
g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195

[-- Attachment #2: Type: text/html, Size: 5832 bytes --]

  reply	other threads:[~2007-08-25  7:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-24  3:11 Problems on porting linux 2.6 to xilinx ML410 woyuzhilei
2007-08-24 18:21 ` Grant Likely
2007-08-25  7:37   ` woyuzhilei [this message]
2007-08-25  8:48   ` how to get your linux-2.6-virtex tree? Ming Liu
2007-08-25 14:10     ` Grant Likely
2007-08-25 14:29       ` Jon Smirl
2007-08-25 14:46       ` Ming Liu
2007-08-25 15:24         ` Grant Likely
2007-08-25 16:13           ` Ming Liu
     [not found] <mailman.726.1187970656.2970.linuxppc-embedded@ozlabs.org>
2007-08-25  1:53 ` Re:Problems on porting linux 2.6 to xilinx ML410 林瑶

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=200708251537084534299@163.com \
    --to=woyuzhilei@163.com \
    --cc=grant.likely@secretlab.ca \
    --cc=linuxppc-embedded@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).