From: Tom Rini <trini@kernel.crashing.org>
To: alebas@televes.com, Kumar Gala <kumar.gala@freescale.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Kernel 2.6.10 running on mpc8272ads
Date: Wed, 5 Jan 2005 10:48:38 -0700 [thread overview]
Message-ID: <20050105174838.GF4213@smtp.west.cox.net> (raw)
In-Reply-To: <1102585377.41b81e218d6df@webmail.televes.com:443>
On Thu, Dec 09, 2004 at 10:42:57AM +0100, alebas@televes.com wrote:
> Hi to all,
>
> Finally I got my mpc8272ads board running the 2.6.20-rc1 kernel.
> The trick was:
>
> First, I had to comment out the BCSR modification for second UART
> in m82xx_board_init function (arch/ppc/platforms/pq2ads.c). As
> suggested by Dan Malek, MMU is still off at this point.
Indeed. While I had a PQ2FADS for a bit, I had to do that as well.
Kumar, what/why is that needed exactly? Did I screw up in re-working
the 82xx init stuff and it needs to happen a bit later in boot?
--
Tom Rini
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2005-01-05 17:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-09 9:42 Kernel 2.6.10 running on mpc8272ads alebas
2005-01-05 17:48 ` Tom Rini [this message]
2005-01-05 19:03 ` Dan Malek
2005-01-12 14:19 ` Tom Rini
2005-01-12 14:22 ` [PATCH 2.6.10] ppc32: Fix mpc8272ads Tom Rini
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=20050105174838.GF4213@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=alebas@televes.com \
--cc=kumar.gala@freescale.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 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).