LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Angielski <jeff@theptrgroup.com>
To: LinuxPPC Embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: rpx8260_defconfig problems
Date: 06 Aug 2004 13:06:21 -0400	[thread overview]
Message-ID: <1091811981.4179.20.camel@localhost.localdomain> (raw)
In-Reply-To: <1091647026.4233.95.camel@localhost.localdomain>


On Wed, 2004-08-04 at 15:17, Jeff Angielski wrote:
> Doing a bk pull on the latest linuxppc-2.4 says that as of July 2004,
> support for the Embedded Planet EP8260 was working.  However, using the
> default rpx8260_defconfig will not work on my board.

I finally managed to get a booting linuxppc-2.4 kernel and some console
output.  Now onto getting a working rootfs...

For reference in case anybody tries this at home, the problems were:

1) arch/ppc/platforms/rpx8260.h defined it's own bd_info structure which
was not consistent with u-boot.  This caused the time settings to be
wrong, which in turn caused the decrementer to be set to zero... "That's
it man, game over man, game over, man!"

2) drivers/char/tty_io.c has a typo on the CPM2 support in
console_init() that prevents it from working with anything but 8xx
architectures

- #if defined(CONFIG_8xx) || defined(CONFIG_CONFIG_CPM2_UART)
+ #if defined(CONFIG_8xx) || defined(CONFIG_CPM2_UART)


Cheers,

Jeff Angielski
The PTR Group


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2004-08-06 17:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-04 19:17 rpx8260_defconfig problems Jeff Angielski
2004-08-04 19:56 ` Dan Malek
2004-08-06 17:06 ` Jeff Angielski [this message]
2004-08-06 18:53   ` Dan Malek

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=1091811981.4179.20.camel@localhost.localdomain \
    --to=jeff@theptrgroup.com \
    --cc=linuxppc-embedded@lists.linuxppc.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