All of lore.kernel.org
 help / color / mirror / Atom feed
From: "sarah.ddff" <sarah.ddff@gmail.com>
To: linuxppc-embedded@ozlabs.org
Subject: Re: XUPV2P + EDK 9.1 + Linux 2.4
Date: Fri, 12 Dec 2008 06:39:01 -0800 (PST)	[thread overview]
Message-ID: <20976787.post@talk.nabble.com> (raw)
In-Reply-To: <4941CB50.6060704@bucknell.edu>


I have linux 2.6 running on the xupv2p with uart and ethernet.
Also, I have linux 2.6 running with uart, sysace and ethernet.=20
You can find here: https://rm-rfroot.net/xupv2p/ useful instructions to por=
t
linux 2.4 to the xupv2p board.


Juliana Su wrote:
>=20
> Hi,
>=20
> I'm relatively new to the XUPV2P. Up until about a month ago, I had been=
=20
> working with an ML310. Anyway, I noticed the =E2=80=9CXUPV2P update to ke=
rnel=20
> 2.6 fails=E2=80=9D thread and saw that quite a few people have been succe=
ssful=20
> with the XUPV2P; I was hoping that those of you who have been successful=
=20
> with the XUPV2P could help me out.
>=20
> First some background...
>=20
> I am using EDK 9.1, EDK 10.1, the MontaVista Linux 2.4 kernel=20
> (linuxppc_2_4_devel), and a 256 MB DDR DIMM. I was able to get a basic=20
> system (XPS UART16550, DDR SDRAM - MPMC, XPS SYSACE, Linux 2.4) made in=
=20
> EDK 10.1 to work. However, I have not had any success getting a similar=
=20
> system (UART16550, DDR_SDRAM_32Mx64 - PLB DDR, OPB SYSACE, Linux 2.4)=20
> built in EDK 9.1 to work. The issue is that, when I turn on the board,=20
> nothing shows up in minicom. I checked the contents of the log_buf; it=20
> was filled with junk.
>=20
> My goal is a system with SysACE support, Ethernet, and the AC-97 audio=20
> CODEC that can mount a hard drive. It seems like it would be easier to=20
> create this system using EDK 9.1 than EDK 10.1. Right now, though, just=
=20
> getting a basic system to work using EDK 9.1 would be great.
>=20
> For those of you who have been successful with the XUPV2P, what=20
> configurations in the EDK 9.1 Base System Builder Wizard and what Linux=
=20
> kernel worked for you? Any suggestions as to why I might not be getting=
=20
> any output? Would it be possible for me to use Linux 2.6 or should I=20
> stick with Linux 2.4? (I feel like Linux 2.4 would be better, but I=20
> thought I would ask anyway.) Also, are there any known issues with EDK=20
> 9.1 and the XUPV2P? I vaguely remember reading about memory issues=20
> somewhere, but I can=E2=80=99t remember if they were related to EDK 9.1, =
EDK=20
> 10.1, or both.
>=20
> Let me know if I should provide any additional information. Thanks!
>=20
>=20
> -Juliana
>=20
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>=20
>=20

--=20
View this message in context: http://www.nabble.com/XUPV2P-%2B-EDK-9.1-%2B-=
Linux-2.4-tp20969433p20976787.html
Sent from the linuxppc-embedded mailing list archive at Nabble.com.

  reply	other threads:[~2008-12-12 14:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-12  2:24 XUPV2P + EDK 9.1 + Linux 2.4 Juliana Su
2008-12-12 14:39 ` sarah.ddff [this message]
2008-12-13  1:26 ` Juliana Su
2008-12-15  9:04   ` xavier.vvv

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=20976787.post@talk.nabble.com \
    --to=sarah.ddff@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.