From: "Guy M. Streeter" <streeter@redhat.com>
To: Srinivasa Hebbar <sshebbar@yahoo.com>
Cc: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: bash: Segmentation fault on 8280
Date: 17 Nov 2003 09:56:56 -0600 [thread overview]
Message-ID: <1069084615.1046.2.camel@jarjar.hsv.redhat.com> (raw)
In-Reply-To: <000f01c3ad19$16bc9070$3d40000a@wisdom>
[-- Attachment #1: Type: text/plain, Size: 555 bytes --]
On Mon, 2003-11-17 at 08:42, Srinivasa Hebbar wrote:
> Dear All,
>
> We have 2 identical custom board with MPC-8260 and MPC-8280 CPUs.
> The bash (Came with denx CD) works fine on MPC-8260 board.
> But the same bash program encounters a "Segmentation Fault"
> on 8280 based custom board.
>
> We are using ppc_82xx-gcc compiler to build the linux.
> The linux version is denx-2.4.20
Your kernel might not have 8280 support. See if something like the
attached patch has been applied.
--Guy
>
> Any help is highly appreciated.
>
> Regards,
> S. Hebbar.
>
[-- Attachment #2: 8280.patch --]
[-- Type: text/plain, Size: 695 bytes --]
--- v2.4.22_linuxppc_2_4_devel/arch/ppc/kernel/cputable.c 2003-07-25 14:39:48.000000000 +0000
+++ sbcPowerQUICCII/arch/ppc/kernel/cputable.c 2003-10-14 18:51:45.000000000 +0000
@@ -299,6 +299,14 @@ struct cpu_spec cpu_specs[] = {
32, 32,
__setup_cpu_603
},
+ { /* 8280 is a G2_LE (603e core, plus some) */
+ 0x7fff0000, 0x00820000, "8280",
+ CPU_FTR_SPLIT_ID_CACHE | CPU_FTR_CAN_DOZE | CPU_FTR_USE_TB |
+ CPU_FTR_CAN_NAP | CPU_FTR_HAS_HIGH_BATS,
+ COMMON_PPC,
+ 32, 32,
+ __setup_cpu_603
+ },
{ /* default match, we assume split I/D cache & TB (non-601)... */
0x00000000, 0x00000000, "(generic PPC)",
CPU_FTR_SPLIT_ID_CACHE | CPU_FTR_USE_TB | CPU_FTR_HPTE_TABLE,
prev parent reply other threads:[~2003-11-17 15:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-17 14:42 bash: Segmentation fault on 8280 Srinivasa Hebbar
2003-11-17 15:56 ` Guy M. Streeter [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=1069084615.1046.2.camel@jarjar.hsv.redhat.com \
--to=streeter@redhat.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=sshebbar@yahoo.com \
/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).