linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: wangyanlong <killyouatonce@gmail.com>
To: linuxppc-dev@ozlabs.org
Subject: Re: Fwd: linux2.6 does not boot from XUP
Date: Tue, 6 May 2008 00:04:22 -0700 (PDT)	[thread overview]
Message-ID: <17077099.post@talk.nabble.com> (raw)
In-Reply-To: <2c8360dd0805051732v64966f4ej7ded735519c63f65@mail.gmail.com>


Hi ,boys . I am in the XiDian universtiy of china . I am doing the things i=
ke
yours.You can try set ttyUL0,if you use the Uartlite. If it don't work , ma=
y
be  gcc 4.1.0  miscompile the kernel 2.6 , I am using the gcc3.4.4.
Good luck
=20

=E5=BC=A0=E8=BD=B6 wrote:
>=20
> ---------- Forwarded message ----------
> From: =E5=BC=A0=E8=BD=B6 <zhangyihere@gmail.com>
> Date: 2008/5/5
> Subject: linux2.6 does not boot from XUP
> To: grant.likely@secretlab.ca
>=20
>=20
> Hi,Grant
>=20
> I hope I could get some advices from you about how to fix the error of
> porting linux2.6 to Xilinx XUPV2P.
>=20
> The kernel I am using is 2.6.24,gcc 4.1.0,glibc 2.3.6,and the board Xilin=
x
> XUPV2P
>=20
> It compiles successfully with some warnings like below:
>   MODPOST vmlinux.o
> WARNING: vmlinux.o(.text+0x223c): Section mismatch: reference to
> .init.text:early_init (between 'start_here' and 'initial_mmu')
> WARNING: vmlinux.o(.text+0x2254): Section mismatch: reference to
> .init.text:machine_init (between 'start_here' and 'initial_mmu')
> WARNING: vmlinux.o(.text+0x2258): Section mismatch: reference to
> .init.text:MMU_init (between 'start_here' and 'initial_mmu')
> WARNING: vmlinux.o(.text+0x22b2): Section mismatch: reference to
> .init.text:start_kernel (between 'start_here' and 'initial_mmu')
> WARNING: vmlinux.o(.text+0x22b6): Section mismatch: reference to
> .init.text:start_kernel (between 'start_here' and 'initial_mmu')
>    LD      vmlinux
>=20
> The system is created as ACE file and booted from CF Card
>=20
> After uncompressing the kernel,the system hangs.The information is like
> below:
>=20
> loaded at:     00400000 0056619C
> board data at: 00000000 0000007C
> relocated to:  00404068 004040E4
> zimage at:     00404E51 00563BF4
> avail ram:     00567000 7C9E2370
>=20
> Linux/PPC load: console=3DttyS0,9600 root=3D/dev/xsysace/disc0/part3 rw
> Uncompressing Linux...done.
> Now booting the kernel
> I wonder if it is the upper WARNINGs that causes the hang of the system,
> and
> how can I fix it.
>=20
> Thanks in advance, any advice would be helpful
>=20
> Best Regards
>=20
> Yi
>=20
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
>=20

--=20
View this message in context: http://www.nabble.com/Fwd%3A-linux2.6-does-no=
t-boot-from-XUP-tp17074762p17077099.html
Sent from the linuxppc-dev mailing list archive at Nabble.com.

      parent reply	other threads:[~2008-05-06  7:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2c8360dd0805050632q4f7b90akc5b7f01ad97c02de@mail.gmail.com>
2008-05-06  0:32 ` Fwd: linux2.6 does not boot from XUP 张轶
2008-05-06  3:15   ` Grant Likely
2008-05-06  7:04   ` wangyanlong [this message]

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=17077099.post@talk.nabble.com \
    --to=killyouatonce@gmail.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).