From owner-linux-arm-kernel@lists.arm.linux.org.uk  Wed Jan  5 09:54:30 2000
Received: (from majordomo@localhost)
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) id JAA10335
	for linux-arm-kernel-outgoing; Wed, 5 Jan 2000 09:54:30 GMT
Received: from xanadu.vipswitch.com (generic199.197.205.205.in-addr.arpa [205.205.197.199] (may be forged))
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id JAA10331
	for <linux-arm-kernel@lists.arm.linux.org.uk>; Wed, 5 Jan 2000 09:54:26 GMT
Date: Tue, 4 Jan 2000 17:03:33 -0500 (EST)
From: Nicolas Pitre <nico@CAM.ORG>
To: linux-arm-kernel@lists.arm.linux.org.uk
cc: linux-arm@vger.rutgers.edu
Subject: PCI: master abort
Message-ID: <Pine.LNX.4.10.10001041639160.6732-100000@xanadu.vipswitch.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm-kernel@lists.arm.linux.org.uk
Precedence: bulk

I'm trying to make a Sangoma PCI card work over an EBSA285 PCI bus with
Linux-2.2.13-rmk2. The driver works fine under i386 and only ioremap()'ed
memory is used to communicate with the card.  The card is probed correctly
and initialized, but at some point I get this each time the driver is
launched:

PCI: master abort pc=[<C00DD224>]

The reportd PC is always the same and is located in memset:

...
c00dd20c:       e35c0002        cmp     ip, #2
c00dd210:       b4c31001        strltb  r1, [r3], #1
c00dd214:       d4c31001        strleb  r1, [r3], #1
c00dd218:       e4c31001        strb    r1, [r3], #1
c00dd21c:       e26cc004        rsb     ip, ip, #4
c00dd220:       e042200c        sub     r2, r2, ip
c00dd224:       e1811401        orr     r1, r1, r1, lsl #8
c00dd228:       e1811801        orr     r1, r1, r1, lsl #16
c00dd22c:       e3520c01        cmp     r2, #256
c00dd230:       ba00001d        blt     c00dd2ac <memset+0xb4>
...

After the "master abort" message, the driver times out and fail.

On the same setup, I can play with a 3C905 and a Promise/IDE PCI card
with no problem.

Any idea on what can be wrong?



Nicolas



unsubscribe: body of `unsubscribe linux-arm-kernel' to majordomo@lists.arm.linux.org.uk

From owner-linux-arm-kernel@lists.arm.linux.org.uk  Wed Jan  5 19:14:25 2000
Received: (from majordomo@localhost)
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) id TAA28927
	for linux-arm-kernel-outgoing; Wed, 5 Jan 2000 19:14:25 GMT
Received: from kings-cross.london.uk.eu.org (mail@tazenda.demon.co.uk [158.152.220.239])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id TAA28923
	for <linux-arm-kernel@lists.arm.linux.org.uk>; Wed, 5 Jan 2000 19:14:22 GMT
Received: from localhost
	([::ffff:127.0.0.1] helo=kings-cross.london.uk.eu.org ident=phil)
	by kings-cross.london.uk.eu.org with esmtp (Exim 3.11 #1)
	id 125dz5-0007oZ-00; Wed, 05 Jan 2000 00:07:27 +0000
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: Nicolas Pitre <nico@CAM.ORG>
cc: linux-arm-kernel@lists.arm.linux.org.uk, linux-arm@vger.rutgers.edu
Subject: Re: PCI: master abort 
In-Reply-To: Message from Nicolas Pitre <nico@cam.org> 
   of "Tue, 04 Jan 2000 17:03:33 EST." <Pine.LNX.4.10.10001041639160.6732-100000@xanadu.vipswitch.com> 
References: <Pine.LNX.4.10.10001041639160.6732-100000@xanadu.vipswitch.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 05 Jan 2000 00:07:27 +0000
From: Philip Blundell <Philip.Blundell@pobox.com>
Message-Id: <E125dz5-0007oZ-00@kings-cross.london.uk.eu.org>
Sender: owner-linux-arm-kernel@lists.arm.linux.org.uk
Precedence: bulk

>I'm trying to make a Sangoma PCI card work over an EBSA285 PCI bus with
>Linux-2.2.13-rmk2. The driver works fine under i386 and only ioremap()'ed
>memory is used to communicate with the card.  The card is probed correctly
>and initialized, but at some point I get this each time the driver is
>launched:
>
>PCI: master abort pc=[<C00DD224>]
>
>The reportd PC is always the same and is located in memset:

Sounds like you might be calling memset() directly on ioremap'd memory, rather 
than using memset_io.  Try setting IO_FUDGE_FACTOR to zero and see if that 
helps any.

p.



unsubscribe: body of `unsubscribe linux-arm-kernel' to majordomo@lists.arm.linux.org.uk

From owner-linux-arm-kernel@lists.arm.linux.org.uk  Tue Jan 11 18:11:59 2000
Received: (from majordomo@localhost)
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) id SAA09461
	for linux-arm-kernel-outgoing; Tue, 11 Jan 2000 18:11:59 GMT
Received: from ns-inetext.inet.com ([199.171.211.140])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id SAA09457
	for <linux-arm-kernel@lists.arm.linux.org.uk>; Tue, 11 Jan 2000 18:11:55 GMT
Received: from harpo.inetint.com (harpo [172.16.99.60])
	by ns-inetext.inet.com (8.9.2/8.9.2) with ESMTP id MAA16412
	for <linux-arm-kernel@lists.arm.linux.org.uk>; Tue, 11 Jan 2000 12:10:24 -0600 (CST)
Received: from inet.com ([172.16.13.118]) by harpo.inetint.com
          (Netscape Messaging Server 3.6)  with ESMTP id AAA9F3
          for <linux-arm-kernel@lists.arm.linux.org.uk>;
          Tue, 11 Jan 2000 12:15:30 -0600
Message-ID: <387B7261.186A833B@inet.com>
Date: Tue, 11 Jan 2000 12:11:45 -0600
From: ejc <eli.carter@inet.com>
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5-15 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: linux-arm-kernel@lists.arm.linux.org.uk
Subject: ARM Linux command line
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm-kernel@lists.arm.linux.org.uk
Precedence: bulk

Greetings.

I am trying to use the Linux command-line on an EBSA-285-like board. 
Has anyone else used this functionality?  If so, on what platorm(s)?   
My attempts thus far appear to trigger a kernel panic when it tries to
fork() the init() function.  (I don't know why yet...)  Any information,
hints, documentation pointers, etc. would be greatly appreciated.

TIA,

Eli
eli.carter@inet.com

unsubscribe: body of `unsubscribe linux-arm-kernel' to majordomo@lists.arm.linux.org.uk

From owner-linux-arm-kernel@lists.arm.linux.org.uk  Tue Jan 11 20:35:38 2000
Received: (from majordomo@localhost)
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) id UAA14075
	for linux-arm-kernel-outgoing; Tue, 11 Jan 2000 20:35:38 GMT
Received: from caramon.arm.linux.org.uk (root@p53-cordelia-gui.tch.enablis.net [212.250.233.53])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id UAA14071
	for <linux-arm-kernel@lists.arm.linux.org.uk>; Tue, 11 Jan 2000 20:35:35 GMT
Received: from raistlin.arm.linux.org.uk (linux@raistlin [192.168.0.3])
	by caramon.arm.linux.org.uk (8.9.3/8.9.3) with ESMTP id UAA10651;
	Tue, 11 Jan 2000 20:35:29 GMT
From: Russell King - ARM Linux Admin <linux@arm.linux.org.uk>
Received: (from linux@localhost)
	by raistlin.arm.linux.org.uk (8.7.4/8.7.3) id UAA00565;
	Tue, 11 Jan 2000 20:34:48 GMT
Message-Id: <200001112034.UAA00565@raistlin.arm.linux.org.uk>
Subject: Re: ARM Linux command line
To: eli.carter@inet.com (ejc)
Date: Tue, 11 Jan 2000 20:34:48 +0000 (GMT)
Cc: linux-arm-kernel@lists.arm.linux.org.uk
In-Reply-To: <387B7261.186A833B@inet.com> from "ejc" at Jan 11, 2000 12:11:45 PM
X-Mailer: ELM [version 2.5 PL1]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm-kernel@lists.arm.linux.org.uk
Precedence: bulk

ejc writes:
> I am trying to use the Linux command-line on an EBSA-285-like board. 
> Has anyone else used this functionality?  If so, on what platorm(s)?   
> My attempts thus far appear to trigger a kernel panic when it tries to
> fork() the init() function.  (I don't know why yet...)  Any information,
> hints, documentation pointers, etc. would be greatly appreciated.

What is the kernel panic message?
   _____
  |_____| ------------------------------------------------- ---+---+-
  |   |        Russell King       linux@arm.linux.org.uk      --- ---
  | | | |  http://www.arm.linux.org.uk/~rmk/armlinux.html    /  /  |
  | +-+-+                                                     --- -+-
  /   |               THE developer of ARM Linux              |+| /|\
 /  | | |                                                     ---  |
    +-+-+ -------------------------------------------------  /\\\  |

unsubscribe: body of `unsubscribe linux-arm-kernel' to majordomo@lists.arm.linux.org.uk

From owner-linux-arm-kernel@lists.arm.linux.org.uk  Tue Jan 11 22:46:42 2000
Received: (from majordomo@localhost)
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) id WAA18526
	for linux-arm-kernel-outgoing; Tue, 11 Jan 2000 22:46:42 GMT
Received: from ns-inetext.inet.com (ns-inetext.inet.com [199.171.211.140])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id WAA18522
	for <linux-arm-kernel@lists.arm.linux.org.uk>; Tue, 11 Jan 2000 22:46:38 GMT
Received: from harpo.inetint.com (harpo [172.16.99.60])
	by ns-inetext.inet.com (8.9.2/8.9.2) with ESMTP id QAA22248
	for <linux-arm-kernel@lists.arm.linux.org.uk>; Tue, 11 Jan 2000 16:45:14 -0600 (CST)
Received: from inet.com ([172.16.13.118]) by harpo.inetint.com
          (Netscape Messaging Server 3.6)  with ESMTP id AAA2377;
          Tue, 11 Jan 2000 16:50:20 -0600
Message-ID: <387BB2CB.52DAD38D@inet.com>
Date: Tue, 11 Jan 2000 16:46:35 -0600
From: ejc <eli.carter@inet.com>
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5-15 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Russell King - ARM Linux Admin <linux@arm.linux.org.uk>,
        linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: ARM Linux command line
References: <200001112034.UAA00565@raistlin.arm.linux.org.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm-kernel@lists.arm.linux.org.uk
Precedence: bulk

Russell King - ARM Linux Admin wrote:
> ejc writes:
> > I am trying to use the Linux command-line on an EBSA-285-like board.
> > Has anyone else used this functionality?  If so, on what platorm(s)?
> > My attempts thus far appear to trigger a kernel panic when it tries to
> > fork() the init() function.  (I don't know why yet...)  Any information,
> > hints, documentation pointers, etc. would be greatly appreciated.
> 
> What is the kernel panic message?

Here is the message I get:  (Some comments follow)

POSIX conformance testing by UNIFIX
Unable to handle kernel paging request at virtual address 0a000026
memmap = 00004000, pgd = c0004000
*pgd = 00000000, *pmd = 00000000
Internal error: Oops: 2
CPU: 0
pc : [<c001a2e0>]    lr : [<c010402c>]
sp : c0101f24  ip : c0100000  fp : c0101f70
r10: c00081a0  r9 : c010401c  r8 : c0101fc4
r7 : c0100000  r6 : 00000078  r5 : cfefc000  r4 : c000b8bc
r3 : 00000001  r2 : 0a000012  r1 : 60000013  r0 : c0102e88
Flags: nzCv  IRQs on  FIQs on  Mode SVC_32  Segment kernel
Control: 517D  Table: 0000517D  DAC: 0000001F
Process swapper (pid: 0, stackpage=c0101000)
Stack: 
c0101f00:                                               c010402c
c001a2e0 200000
13 
c0101f20: ffffffff 00000040 c0101f54 fffffff5  00000001 c0101f88
dc6bceae 00000f
00 
c0101f40: 00000000 00000000 00000000 c000b8bc  c000c848 00000078
c0100000 c0101f
c4 
c0101f60: 4401a104 c0101f80 c0101f74 c0010f70  c001a164 00000000
c0101f84 c000c6
c0 
c0101f80: c0010f64 c000b8bc 00000f00 00000000  00000f00 60000013
c000b8bc c01027
60 
c0101fa0: c0120c94 c012e42c c0102994 4401a104  c00081a0 c0101fe0
00000000 dc6bce
ae 
c0101fc0: f77f7fcd c000dbe0 60000013 00000f00  c010275c c0101ffc
c0101fe4 c000b7
d8 
c0101fe0: c000dbc8 c0102a44 c0120d24 c012e42c  00000000 c0102000
c0008284 c000b6
88 
Backtrace: 
Function entered at [<c001a158>] from [<c0010f70>]
  r9 = 4401a104
  r8 = c0101fc4
  r7 = c0100000
  r6 = 00000078
  r5 = c000c848
  r4 = c000b8bc
Function entered at [<c0010f58>] from [<c000c6c0>]
Code: e3520000 0a000012 (e5920014) e3500000 0a00000f 
Kernel panic: Attempted to kill the idle task!
In swapper task - not syncing

---------
Comments:
Based upon System.map,
pc is within do_fork (c001a158 T do_fork)
lr is tarray_freelist (c010402c D tarray_freelist)
I have a printk() at the beginning of init() that is not being printed,
so we're not making it into that.

Ok, I did some test command lines and came up with the following:
The command line I want to be able to use is "root=/dev/sda2 mem=256M
bigphysarea=512"
The root and bigphysarea options appear to work.  ("root=/dev/sda2
bigphysarea=512" does not oops)
However, the commandline of "mem=256M" triggers an oops.

Looking at the code for that (setup_mem()), a bug didn't jump out at
me... I did modify one line in an attempt to fix it, but it had no
obvious effect.
if (c == ' ' && len + 4 < COMMAND_LINE_SIZE) {
instead of 
if (c == ' ' ) {
I'm still studying it...
Suggestions?

TIA,

Eli
eli.carter@inet.com

unsubscribe: body of `unsubscribe linux-arm-kernel' to majordomo@lists.arm.linux.org.uk

From owner-linux-arm-kernel@lists.arm.linux.org.uk  Tue Jan 11 22:56:43 2000
Received: (from majordomo@localhost)
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) id WAA18792
	for linux-arm-kernel-outgoing; Tue, 11 Jan 2000 22:56:43 GMT
Received: from caramon.arm.linux.org.uk (root@p53-cordelia-gui.tch.enablis.net [212.250.233.53])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id WAA18787
	for <linux-arm-kernel@lists.arm.linux.org.uk>; Tue, 11 Jan 2000 22:56:39 GMT
Received: from raistlin.arm.linux.org.uk (linux@raistlin [192.168.0.3])
	by caramon.arm.linux.org.uk (8.9.3/8.9.3) with ESMTP id WAA11261;
	Tue, 11 Jan 2000 22:56:37 GMT
From: Russell King - ARM Linux Admin <linux@arm.linux.org.uk>
Received: (from linux@localhost)
	by raistlin.arm.linux.org.uk (8.7.4/8.7.3) id WAA01110;
	Tue, 11 Jan 2000 22:55:55 GMT
Message-Id: <200001112255.WAA01110@raistlin.arm.linux.org.uk>
Subject: Re: ARM Linux command line
To: eli.carter@inet.com (ejc)
Date: Tue, 11 Jan 2000 22:55:55 +0000 (GMT)
Cc: linux-arm-kernel@lists.arm.linux.org.uk
In-Reply-To: <387BB2CB.52DAD38D@inet.com> from "ejc" at Jan 11, 2000 04:46:35 PM
X-Mailer: ELM [version 2.5 PL1]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm-kernel@lists.arm.linux.org.uk
Precedence: bulk

ejc writes:
> Based upon System.map,
> pc is within do_fork (c001a158 T do_fork)
> lr is tarray_freelist (c010402c D tarray_freelist)
> I have a printk() at the beginning of init() that is not being printed,
> so we're not making it into that.

I'd guess that either the kernel did not compile properly (did you use a
clean source and rebuild everything)?

> Ok, I did some test command lines and came up with the following:
> The command line I want to be able to use is "root=/dev/sda2 mem=256M
> bigphysarea=512"
> The root and bigphysarea options appear to work.  ("root=/dev/sda2
> bigphysarea=512" does not oops)
> However, the commandline of "mem=256M" triggers an oops.

You've got the bigphysarea patches in?  I haven't looked at those, so
can't comment on any behavioural changes.

Does the 'mem=256M' cause the oops you reported, or a different oops?
   _____
  |_____| ------------------------------------------------- ---+---+-
  |   |        Russell King       linux@arm.linux.org.uk      --- ---
  | | | |  http://www.arm.linux.org.uk/~rmk/armlinux.html    /  /  |
  | +-+-+                                                     --- -+-
  /   |               THE developer of ARM Linux              |+| /|\
 /  | | |                                                     ---  |
    +-+-+ -------------------------------------------------  /\\\  |

unsubscribe: body of `unsubscribe linux-arm-kernel' to majordomo@lists.arm.linux.org.uk

From owner-linux-arm-kernel@lists.arm.linux.org.uk  Wed Jan 12 15:48:04 2000
Received: (from majordomo@localhost)
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) id PAA29904
	for linux-arm-kernel-outgoing; Wed, 12 Jan 2000 15:48:04 GMT
Received: from ns-inetext.inet.com (ns-inetext.inet.com [199.171.211.140])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id PAA29900
	for <linux-arm-kernel@lists.arm.linux.org.uk>; Wed, 12 Jan 2000 15:48:01 GMT
Received: from harpo.inetint.com (harpo [172.16.99.60])
	by ns-inetext.inet.com (8.9.2/8.9.2) with ESMTP id JAA03124
	for <linux-arm-kernel@lists.arm.linux.org.uk>; Wed, 12 Jan 2000 09:46:36 -0600 (CST)
Received: from inet.com ([172.16.13.118]) by harpo.inetint.com
          (Netscape Messaging Server 3.6)  with ESMTP id AAA3A11;
          Wed, 12 Jan 2000 09:51:43 -0600
Message-ID: <387CA22D.37E656CC@inet.com>
Date: Wed, 12 Jan 2000 09:47:57 -0600
From: ejc <eli.carter@inet.com>
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5-15 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Russell King - ARM Linux Admin <linux@arm.linux.org.uk>
CC: linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: ARM Linux command line
References: <200001112255.WAA01110@raistlin.arm.linux.org.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm-kernel@lists.arm.linux.org.uk
Precedence: bulk

Russell King - ARM Linux Admin wrote:
> 
> ejc writes:
> > Based upon System.map,
> > pc is within do_fork (c001a158 T do_fork)
> > lr is tarray_freelist (c010402c D tarray_freelist)
> > I have a printk() at the beginning of init() that is not being printed,
> > so we're not making it into that.
> 
> I'd guess that either the kernel did not compile properly (did you use a
> clean source and rebuild everything)?

Doing a `make clean' and rebuilding makes no difference...  Is there
something in particular I can look for?

> > Ok, I did some test command lines and came up with the following:
> > The command line I want to be able to use is "root=/dev/sda2 mem=256M
> > bigphysarea=512"
> > The root and bigphysarea options appear to work.  ("root=/dev/sda2
> > bigphysarea=512" does not oops)
> > However, the commandline of "mem=256M" triggers an oops.
> 
> You've got the bigphysarea patches in?  I haven't looked at those, so
> can't comment on any behavioural changes.

I wouldn't expect this to have an effect on the command line... *shrug*

> Does the 'mem=256M' cause the oops you reported, or a different oops?

An essentially identical oops...  The stack has a couple of slightly
different values, but the backtrace, etc. is identical.  (Copy at the
end of this message.)

I'm happy to study this problem, I was mostly looking for pointers and
confirmation that it is known to work on other EBSA-285[-like] board(s)
to know if it was necessarily my fault.  :)

Suggestions, comments, ideas all welcome.

Thanks,

Eli
eli.carter@inet.com

Commandline: mem=256M
 Defaulting to 512 pages. 
bigphysarea: Allocated 512 pages at 0xc0400000 (0xe0400000 bus,
0x00400000 phys).
Running bigphysarea Debugging tests: Test alloc gave c0400000, c0402000
and c040a000.
bigphysarea: 512 of 512 pages free (0 objects)
Calibrating delay loop... 195.38 BogoMIPS
Memory: 256012k/256M available (984k code, 20k reserved, 5120k data, 8k
init)
POSIX conformance testing by UNIFIX
Unable to handle kernel paging request at virtual address 0a000026
memmap = 00004000, pgd = c0004000
*pgd = 00000000, *pmd = 00000000
Internal error: Oops: 2
CPU: 0
pc : [<c001a2e0>]    lr : [<c010402c>]
sp : c0101f24  ip : c0100000  fp : c0101f70
r10: c00081a0  r9 : c010401c  r8 : c0101fc4
r7 : c0100000  r6 : 00000078  r5 : cfefc000  r4 : c000b8bc
r3 : 00000001  r2 : 0a000012  r1 : 60000013  r0 : c0102e88
Flags: nzCv  IRQs on  FIQs on  Mode SVC_32  Segment kernel
Control: 517D  Table: 0000517D  DAC: 0000001F
Process swapper (pid: 0, stackpage=c0101000)
Stack: 
c0101f00:                                               c010402c
c001a2e0 20000013 
c0101f20: ffffffff 00000040 c0101f54 fffffff5  00000001 c0101f88
dd6beeee 00000f00 
c0101f40: 00000000 00000000 00000000 c000b8bc  c000c848 00000078
c0100000 c0101fc4 
c0101f60: 4401a104 c0101f80 c0101f74 c0010f70  c001a164 00000000
c0101f84 c000c6c0 
c0101f80: c0010f64 c000b8bc 00000f00 00000000  00000f00 60000013
c000b8bc c0102760 
c0101fa0: c0120c94 c012e42c c0102994 4401a104  c00081a0 c0101fe0
00000000 dd6beeee 
c0101fc0: f77f7fcd c000dbe0 60000013 00000f00  c010275c c0101ffc
c0101fe4 c000b7d8 
c0101fe0: c000dbc8 c0102a44 c0120d24 c012e42c  00000000 c0102000
c0008284 c000b688 
Backtrace: 
Function entered at [<c001a158>] from [<c0010f70>]
  r9 = 4401a104
  r8 = c0101fc4
  r7 = c0100000
  r6 = 00000078
  r5 = c000c848
  r4 = c000b8bc
Function entered at [<c0010f58>] from [<c000c6c0>]
Code: e3520000 0a000012 (e5920014) e3500000 0a00000f 
Kernel panic: Attempted to kill the idle task!
In swapper task - not syncing

unsubscribe: body of `unsubscribe linux-arm-kernel' to majordomo@lists.arm.linux.org.uk

From owner-linux-arm-kernel@lists.arm.linux.org.uk  Wed Jan 12 16:41:11 2000
Received: (from majordomo@localhost)
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) id QAA01821
	for linux-arm-kernel-outgoing; Wed, 12 Jan 2000 16:41:11 GMT
Received: from ns-inetext.inet.com (ns-inetext.inet.com [199.171.211.140])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id QAA01803
	for <linux-arm-kernel@lists.arm.linux.org.uk>; Wed, 12 Jan 2000 16:41:08 GMT
Received: from harpo.inetint.com (harpo [172.16.99.60])
	by ns-inetext.inet.com (8.9.2/8.9.2) with ESMTP id KAA04251
	for <linux-arm-kernel@lists.arm.linux.org.uk>; Wed, 12 Jan 2000 10:39:45 -0600 (CST)
Received: from inet.com ([172.16.13.118]) by harpo.inetint.com
          (Netscape Messaging Server 3.6)  with ESMTP id AAA5762;
          Wed, 12 Jan 2000 10:44:51 -0600
Message-ID: <387CAEA2.30A98A38@inet.com>
Date: Wed, 12 Jan 2000 10:41:06 -0600
From: ejc <eli.carter@inet.com>
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5-15 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Russell King - ARM Linux Admin <linux@arm.linux.org.uk>,
        linux-arm-kernel@lists.arm.linux.org.uk
Subject: [SOLVED] Re: ARM Linux command line
References: <200001112255.WAA01110@raistlin.arm.linux.org.uk> <387CA22D.37E656CC@inet.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm-kernel@lists.arm.linux.org.uk
Precedence: bulk

I found my problem.

> > > However, the commandline of "mem=256M" triggers an oops.

This here is a 128M DIMM...  argh.  "mem=128M" works just fine.  (Anyone
have a spare dunce-cap?)

I appologize for taking your time.

Thanks again,

Eli
eli.carter@inet.com

unsubscribe: body of `unsubscribe linux-arm-kernel' to majordomo@lists.arm.linux.org.uk

From owner-linux-arm-kernel@lists.arm.linux.org.uk  Fri Jan 14 02:57:02 2000
Received: (from majordomo@localhost)
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) id CAA22602
	for linux-arm-kernel-outgoing; Fri, 14 Jan 2000 02:57:02 GMT
Received: from thalia.fm.intel.com (thalia.fm.intel.com [132.233.247.11])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id CAA22598
	for <linux-arm-kernel@lists.arm.linux.org.uk>; Fri, 14 Jan 2000 02:56:58 GMT
Received: from SMTP (fmsmsxvs05-1.fm.intel.com [132.233.42.205])
	by thalia.fm.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.18 2000/01/07 21:56:55 dmccart Exp $) with SMTP id CAA27709
	for <linux-arm-kernel@lists.arm.linux.org.uk>; Fri, 14 Jan 2000 02:57:31 GMT
Received: from fmsmsx28.FM.INTEL.COM ([132.233.48.28]) by 132.233.48.205
  (Norton AntiVirus for Internet Email Gateways 1.0) ;
  Fri, 14 Jan 2000 02:56:56 0000 (GMT)
Received: by fmsmsx28.fm.intel.com with Internet Mail Service (5.5.2448.0)
	id <CX89SGVG>; Thu, 13 Jan 2000 18:56:55 -0800
Message-ID: <7DAA70BEB463D211AC3E00A0C96B7AB20405D17C@orsmsx41.jf.intel.com>
From: "Brandewie, Dirk J" <dirk.j.brandewie@intel.com>
To: ARM Kernel list <linux-arm-kernel@lists.arm.linux.org.uk>
Subject: Getting the kernel to boot on the EBSA-285
Date: Thu, 13 Jan 2000 18:56:55 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: owner-linux-arm-kernel@lists.arm.linux.org.uk
Precedence: bulk

Hi All,

I am hoping someone will be able to point out where I am brain
damaged.  I am trying to use the EBSA-285 as a co-processor
"CONFIG_ARCH_CO285"

Here is how I got where I am

1. Built cross development tools ( binutils-2.9.5.0.22 gcc-2.95.2 
   glibc-2.1.2)all seem to work fine.

2. Built Bios v1.06.  Loaded onto board.  boots and runs fine.

3. Added driver to the BIOS so the kernel could be copied into
   memory on the EBSA-285.  The driver works will try to get it
   into shape to be added to the distribution

4. Configured and built zImage with arm-linux patches Linux-2.3.29.
   No problems here.

5. Copied the image onto the board and tried to boot it. 

Here is where I am confused.  The image starts to boot but dies
when trying execute  "bl SYMBOL_NAME(decompress_kernel).  I added a 
putc() call as the first thing in decompress kernel nothing ever
appears.  I added a putc() as the first statement in decompress_kernel()
and nothing appears on the terminal.

Does anyone have any words of wisdom on how to track down why the
image is falling over. I will start sifting through the binary to
see if there is a code generation problem but I doubt it since the
same tools created a working BIOS.

BTW I believe there is a bug in arch-ebsa285/uncompress.h
Line 19 reads "while (DC21285_BASE[6] & 8);"  I think someone meant
to say "while (DC21285_BASE[6] & 10);" if the code was meant to 
wait for the transmit FIFO to be un-busy

Thanks in advance
--Dirk


unsubscribe: body of `unsubscribe linux-arm-kernel' to majordomo@lists.arm.linux.org.uk

From owner-linux-arm-kernel@lists.arm.linux.org.uk  Fri Jan 14 03:52:36 2000
Received: (from majordomo@localhost)
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) id DAA25772
	for linux-arm-kernel-outgoing; Fri, 14 Jan 2000 03:52:36 GMT
Received: from external.rsc.rockwell.com (firewall-user@external.rsc.rockwell.com [130.50.23.2])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id DAA25764
	for <linux-arm-kernel@lists.arm.linux.org.uk>; Fri, 14 Jan 2000 03:52:33 GMT
From: dusty@rsc.rockwell.com
Received: by external.rsc.rockwell.com; id TAA09821; Thu, 13 Jan 2000 19:52:31 -0800 (PST)
Received: from dns.risc.rockwell.com(130.50.4.15) by external.rsc.rockwell.com via smap (V4.2)
	id xma009799; Thu, 13 Jan 00 19:51:40 -0800
Received: from rsctonotes01.rsc.rockwell.com (rsctonotes01.risc.rockwell.com [130.50.4.71]) by dns.risc.rockwell.com (8.9.0/8.6.9) with SMTP id TAA11386 for <linux-arm-kernel@lists.arm.linux.org.uk>; Thu, 13 Jan 2000 19:51:40 -0800 (PST)
Received: by rsctonotes01.rsc.rockwell.com(Lotus SMTP MTA v4.6.3 (778.2 1-4-1999))  id 88256866.00152B0D ; Thu, 13 Jan 2000 19:51:12 -0800
X-Lotus-FromDomain: ROCKWELL
To: linux-arm-kernel@lists.arm.linux.org.uk
Message-ID: <88256866.00152A3D.00@rsctonotes01.rsc.rockwell.com>
Date: Thu, 13 Jan 2000 19:51:18 -0800
Subject: EBSA285 boot problems
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-linux-arm-kernel@lists.arm.linux.org.uk
Precedence: bulk


I'm trying to get the 2.3.35 Linux kernel running on an unmodified EBSA285 in
host mode with no peripherals.  I'm planning on using only a ramdisk in the
final system, but I'm having trouble getting the kernel to load the ramdisk
properly.  I've modified the bios v1.06 to copy my flash images (zImage,
ramdisk.gz) to addresses 0x8000 and 0x800000 respectively.  The ramdisk is a
gzipped ext2 filesystem that I created following the instructions from Intel's
web site.  I have verified that everything is properly copied into RAM at the
appropriate address.  I'm rather unfamiliar with the Linux boot procedure, so
I've tried to imitate the booting procedure of a previous posting to this
newsgroup.

I'm booting the kernel with the following parameters:
initrd_start = 0xC0800000
initrd_size=1392506 (my ramdisk size in bytes)
root_device=0x0100
root_flags=4

These are the results I get from printk:
=======================================
Uncompressing Linux.................................................. done, boot
ing the kernel.
Linux version 2.3.35-rmk1 (mcintire@corona.risc.rockwell.com) (gcc version 2.95.
1 19990816 (release)) #6 Mon Jan 3 12:25:51 PST 2000
On node 0 totalpages: 00001000
zone(0): 4096 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Console: colour dummy device 80x50
Calibrating delay loop... 214.63 BogoMIPS
Memory: 16MB = 16MB total
Memory: 12840KB available (1282K code, 463K data, 112K init)
Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)
Page-cache hash table entries: 4096 (order: 2, 16384 bytes)
POSIX conformance testing by UNIFIX
<7>PCI: DC21285 footbridge, revision 04
<6>Linux NET4.0 for Linux 2.3
<6>Based upon Swansea University Computer Society NET3.039
<6>NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
<6>NET4: Linux TCP/IP 1.0 for NET4.0
<6>IP Protocols: ICMP, UDP, TCP
TCP: Hash tables configured (established 1024 bind 2048)
Starting kswapd v1.6
<7>PCI: master abort pc=[<C0104A0C>]
<6>Serial driver version 4.91 (1999-11-17) with MANY_PORTS SHARE_IRQ SERIAL_PCI
PCI_IOMEM enabled
pty: 256 Unix98 ptys configured
Software Watchdog Timer: 0.05, timer margin: 60 sec
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
<6>loop: registered device at major 7
<6>loop: enabling 8 loop devices
<6>Uniform Multi-Platform E-IDE driver Revision: 6.21
<6>3c59x.c:v0.99H 11/17/98 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drive
rs/vortex.html
<3>IP-Config: No network devices available.
<5>RAMDISK: Couldn't find valid RAM disk image starting at 0.
Freeing initrd memory: 4194303k freed
<6>Real Time Clock Driver v1.09b
<3>rtc: IRQ 8 is not free.
<4>NetWinder Floating Point Emulator V0.95 (c) 1998-1999 Rebel.com
<0>Kernel panic: VFS: Unable to mount root fs on 01:00
=========================================
I've also tried adding rd_start=8192 to the command line, but this gives me the
following oops message.

<1>Unable to handle kernel paging request at virtual address c1000000
<1>pgd = c0004000
<1>*pgd = 00000000, *pmd = 00000000
Internal error: Oops: 2
CPU: 0
pc : [<c012e834>]    lr : [<c00dee8c>]
sp : c095da6c  ip : 00000000  fp : c095daa0
r10: 00800000  r9 : ffffffff  r8 : 00002000
r7 : c095dc68  r6 : c0955000  r5 : c095dc84  r4 : 00000200
r3 : 00000000  r2 : 000001fc  r1 : c1000000  r0 : c0955000
Flags: nzCv  IRQs on  FIQs on  Mode SVC_32  Segment kernel
Control: 517D  Table: 0000517D  DAC: 0000001D
Process swapper (pid: 1, stackpage=c095d000)

It seems as though the initial ramdisk parameters remove the ramdisk image from
the memory map.

Could someone clarify my confusion regarding the proper parameters to pass to
the kernel.  Any help is greatly appreciated.
Thanks.

Dustin.

Dustin McIntire
Engineer
Rockwell Science Center
dhmcintire@rsc.rockwell.com





unsubscribe: body of `unsubscribe linux-arm-kernel' to majordomo@lists.arm.linux.org.uk

From owner-linux-arm-kernel@lists.arm.linux.org.uk  Fri Jan 14 06:26:09 2000
Received: (from majordomo@localhost)
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) id GAA00303
	for linux-arm-kernel-outgoing; Fri, 14 Jan 2000 06:26:09 GMT
Received: from smtppop2.gte.net (smtppop2.gte.net [207.115.153.21])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id GAA32767
	for <linux-arm-kernel@lists.arm.linux.org.uk>; Fri, 14 Jan 2000 06:26:06 GMT
Received: from t5e4i9 (evrtwa1-ar3-168-153.dsl.gtei.net [4.33.168.153])
	by smtppop2.gte.net  with SMTP
	; id AAA13749964
	Fri, 14 Jan 2000 00:24:25 -0600 (CST)
Message-ID: <000801bf5e58$114daf20$99a82104@t5e4i9.dsl.gtei.net>
Reply-To: "Dirk Brandewie" <dirk@homemail.com>
From: "Dirk Brandewie" <djbrande@gte.net>
To: "Brandewie, Dirk J" <dirk.j.brandewie@intel.com>,
        "ARM Kernel list" <linux-arm-kernel@lists.arm.linux.org.uk>
Subject: Re: Getting the kernel to boot on the EBSA-285
Date: Thu, 13 Jan 2000 22:24:46 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3155.0
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0
Sender: owner-linux-arm-kernel@lists.arm.linux.org.uk
Precedence: bulk

Here is the fix for the typo.  I really should have read the post closer
before sending :-(
--Dirk
-----Original Message-----
From: Brandewie, Dirk J <dirk.j.brandewie@intel.com>
To: ARM Kernel list <linux-arm-kernel@lists.arm.linux.org.uk>
Date: Thursday, January 13, 2000 7:57 PM
Subject: Getting the kernel to boot on the EBSA-285



>BTW I believe there is a bug in arch-ebsa285/uncompress.h
>Line 19 reads "while (DC21285_BASE[6] & 8);"  I think someone meant
>to say "while (DC21285_BASE[6] & 10);" if the code was meant to 
>wait for the transmit FIFO to be un-busy
>
Fixed line should be "while (DC21285_BASE[6] & 0x10);" 


unsubscribe: body of `unsubscribe linux-arm-kernel' to majordomo@lists.arm.linux.org.uk

From owner-linux-arm-kernel@lists.arm.linux.org.uk  Fri Jan 14 12:53:07 2000
Received: (from majordomo@localhost)
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) id MAA23042
	for linux-arm-kernel-outgoing; Fri, 14 Jan 2000 12:53:07 GMT
Received: from dhinfo_server.elim.net ([203.239.167.60])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id MAA23037
	for <linux-arm-kernel@lists.arm.linux.org.uk>; Fri, 14 Jan 2000 12:52:43 GMT
Received: from ÀÌÇÐ¸í by dhinfo_server.elim.net with SMTP (Microsoft Exchange Internet Mail Service Version 5.0.1457.7)
	id Y6NBVFFD; Fri, 14 Jan 2000 21:49:33 +0900
Message-ID: <387F1CB9.7E3C9FA3@donghoit.com>
Date: Fri, 14 Jan 2000 21:55:22 +0900
From: hmlee <hmlee@donghoit.com>
X-Mailer: Mozilla 4.05 [en] (Win95; I)
MIME-Version: 1.0
To: linux-arm-kernel@lists.arm.linux.org.uk
Subject: memory violation problem in EBSA-285 like board
Content-Type: text/plain; charset=iso-2022-kr
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm-kernel@lists.arm.linux.org.uk
Precedence: bulk

Hi!
We made a arm-linux system with sa-110 + dc21285 + via82C686(super i/o).

We are using a bios-1.05 version to loading the kernel in flash memory.
The flash memory contains bios-1.05+kernel.
The bios copies zImage to 0x8000 and jump there to running it.
I was compiled with CONFIG_EBSA285 options in kernel config time with
some patch in head-armv.S for debug.
The kernel was running and mounted to root filesystem in
harddisk(/dev/hda1).
We are using a dm-3.0-14beta.tar.gz for making filesystem in /dev/hda1.
The dm-3.0-14beta.tar.gz was untared in /dev/hda1 and connected to our
arm-linux system.
The harddisk has a
    /dev/hda1    linux(ext2 root filesystem)
    /dev/hda2    linux
    /dev/hda3    linux swap

But "memory violation" occured as follows:

Linux version 2.2.13-rmk2 (root@arm-linux.net) (gcc version egcs-2.91.66
19990325/philb (egcs-1.1.2 release)) #104 Fri Jan 14 20:47:10 EST 2000
<4>NetWinder Floating Point Emulator V0.94.1 (c) 1998 Corel Computer
Corp.
PIC Installed Correctly !!
Console: colour VGA+ 80x25

Calibrating delay loop... 4.63 BogoMIPS                <=========  Why ?

Memory: 14848k/16M available (1092k code, 20k reserved, 408k data, 16k
init)
<5>VFS: Diskquotas version dquot_6.4.0 initialized
POSIX conformance testing by UNIFIX
SA110_Control = 0x84aac201
<7>PCI: DEC21285 revision 04
PCI: Probing PCI hardware
<7>PCI: master abort pc=[<C00152A8>]
<7>PCI: parity error data parity error pc=[<C0015328>]
<3>IRQ LOCK: IRQ31 is locking the system, disabled
<7>PCI: 00:38 [102c/00e0] on irq 21
<7>PCI: 00:40 [1106/0686] on irq 24
<7>PCI: 00:41 [1106/0571] on irq 14
<7>PCI: 00:42 [1106/3038] on irq 22
<7>PCI: 00:44 [1106/3057] on irq 22
<6>Linux NET4.0 for Linux 2.2
<6>Based upon Swansea University Computer Society NET3.039
<6>NET4: Unix domain sockets 1.0 for Linux NET4.0.
<6>NET4: Linux TCP/IP 1.0 for NET4.0
<6>IP Protocols: ICMP, UDP, TCP
Starting kswapd v 1.5
<6>parport0: PC-style at 0x3bc [SPP]
<6>parport1: PC-style at 0x378 [SPP]
<6>parport2: PC-style at 0x278 [SPP]
<6>Detected PS/2 Mouse Port.
<6>Serial driver version 4.27 with MANY_PORTS SHARE_IRQ DETECT_IRQ
enabled
Software Watchdog Timer: 0.05, timer margin: 60 sec
<6>Real Time Clock Driver v1.09
RAM disk driver initialized:  16 RAM disks of 4096K size
<6>loop: registered device at major 7
VP_IDE: IDE controller on PCI bus 00 dev 41
VP_IDE: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xe800-0xe807, BIOS settings: hda:pio, hdb:pio
ide0: VIA Bus-Master (U)DMA Timing Config Success
probing for hda: present=0, media=32, probetype=ATA
hda: FUJITSU MPD3084AT, ATA DISK drive
probing for hdb: present=0, media=32, probetype=ATA
probing for hdb: present=0, media=32, probetype=ATAPI
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
<6>hda: FUJITSU MPD3084AT, 8063MB w/512kB Cache, CHS=16383/16/63
<6>Floppy drive(s): fd0 is 1.44M, fd1 is 1.44M
floppy0: Unable to grab DMA2 for the floppy driver
md driver 0.36.6 MAX_MD_DEV=4, MAX_REAL=8
<6>3c59x.c:v0.99H 11/17/98 Donald Becker
http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html
<6>Partition check:
<6> hda: [PTBL] [1027/255/63] hda1 hda2 hda3
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 16k init
sh: memory violation at pc=0xe59cf000, lr=0x40004b9c (bad
address=0xe59cf000, code 3)
sh: memory violation at pc=0xe59cf000, lr=0x40004b9c (bad
address=0xe59cf000, code 3)
sh: memory violation at pc=0xe59cf000, lr=0x40004b9c (bad
address=0xe59cf000, code 3)
sh: memory violation at pc=0xe59cf000, lr=0x40004b9c (bad
address=0xe59cf000, code 3)
sh: memory violation at pc=0xe59cf000, lr=0x40004b9c (bad
address=0xe59cf000, code 3)
.....


Please help me!
If I could incorrectlly, tell me.

email : hmlee@donghoit.com


unsubscribe: body of `unsubscribe linux-arm-kernel' to majordomo@lists.arm.linux.org.uk

From owner-linux-arm-kernel@lists.arm.linux.org.uk  Fri Jan 14 15:18:39 2000
Received: (from majordomo@localhost)
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) id PAA28462
	for linux-arm-kernel-outgoing; Fri, 14 Jan 2000 15:18:39 GMT
Received: from xanadu.vipswitch.com (generic199.197.205.205.in-addr.arpa [205.205.197.199] (may be forged))
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id PAA28458
	for <linux-arm-kernel@lists.arm.linux.org.uk>; Fri, 14 Jan 2000 15:18:27 GMT
Date: Fri, 14 Jan 2000 10:13:37 -0500 (EST)
From: Nicolas Pitre <nico@CAM.ORG>
To: dusty@rsc.rockwell.com
cc: linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: EBSA285 boot problems
In-Reply-To: <88256866.00152A3D.00@rsctonotes01.rsc.rockwell.com>
Message-ID: <Pine.LNX.4.10.10001140959540.9196-100000@xanadu.vipswitch.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm-kernel@lists.arm.linux.org.uk
Precedence: bulk



On Thu, 13 Jan 2000 dusty@rsc.rockwell.com wrote:

[...]
> I've also tried adding rd_start=8192 to the command line, but this gives me the
> following oops message.
> 
> <1>Unable to handle kernel paging request at virtual address c1000000
> <1>pgd = c0004000
> <1>*pgd = 00000000, *pmd = 00000000
> Internal error: Oops: 2
> CPU: 0
> pc : [<c012e834>]    lr : [<c00dee8c>]
[...]

Try to give the corresponding symbol name from the System.map file next
time, especially the name of the function the PC is in.  It's then easier
to tell where the crash is.

I had kind of the same problem with some 2.3.x kernels. Though I don't
know if it is still required, but you could try this patch:

--- ../2.3.35-rmk1/linux/fs/buffer.c    Sat Jan  1 18:59:58 2000
+++ linux/fs/buffer.c   Tue Jan  4 21:49:38 2000
@@ -2456,6 +2456,7 @@
 {
        kernel_thread(bdflush, NULL, CLONE_FS | CLONE_FILES | CLONE_SIGHAND);
        kernel_thread(kupdate, NULL, CLONE_FS | CLONE_FILES | CLONE_SIGHAND);
+       schedule();
        return 0;
 }


Nicolas



unsubscribe: body of `unsubscribe linux-arm-kernel' to majordomo@lists.arm.linux.org.uk

From owner-linux-arm-kernel@lists.arm.linux.org.uk  Fri Jan 14 19:30:16 2000
Received: (from majordomo@localhost)
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) id TAA12742
	for linux-arm-kernel-outgoing; Fri, 14 Jan 2000 19:30:16 GMT
Received: from caramon.arm.linux.org.uk (root@p48-robin-gui.tch.enablis.net [194.168.180.108])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id TAA12737
	for <linux-arm-kernel@lists.arm.linux.org.uk>; Fri, 14 Jan 2000 19:30:11 GMT
Received: from raistlin.arm.linux.org.uk (linux@raistlin [192.168.0.3])
	by caramon.arm.linux.org.uk (8.9.3/8.9.3) with ESMTP id TAA10671;
	Fri, 14 Jan 2000 19:30:06 GMT
From: Russell King - ARM Linux Admin <linux@arm.linux.org.uk>
Received: (from linux@localhost)
	by raistlin.arm.linux.org.uk (8.7.4/8.7.3) id TAA02084;
	Fri, 14 Jan 2000 19:29:24 GMT
Message-Id: <200001141929.TAA02084@raistlin.arm.linux.org.uk>
Subject: Re: memory violation problem in EBSA-285 like board
To: hmlee@donghoit.com (hmlee)
Date: Fri, 14 Jan 2000 19:29:24 +0000 (GMT)
Cc: linux-arm-kernel@lists.arm.linux.org.uk
In-Reply-To: <387F1CB9.7E3C9FA3@donghoit.com> from "hmlee" at Jan 14, 2000 09:55:22 PM
X-Mailer: ELM [version 2.5 PL1]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm-kernel@lists.arm.linux.org.uk
Precedence: bulk

hmlee writes:
> 
> Hi!
> We made a arm-linux system with sa-110 + dc21285 + via82C686(super i/o).
> 
> We are using a bios-1.05 version to loading the kernel in flash memory.
> The flash memory contains bios-1.05+kernel.
> The bios copies zImage to 0x8000 and jump there to running it.
> I was compiled with CONFIG_EBSA285 options in kernel config time with
> some patch in head-armv.S for debug.
> The kernel was running and mounted to root filesystem in
> harddisk(/dev/hda1).
> We are using a dm-3.0-14beta.tar.gz for making filesystem in /dev/hda1.
> The dm-3.0-14beta.tar.gz was untared in /dev/hda1 and connected to our
> arm-linux system.
> The harddisk has a
>     /dev/hda1    linux(ext2 root filesystem)
>     /dev/hda2    linux
>     /dev/hda3    linux swap
> 
> But "memory violation" occured as follows:
> 
> Linux version 2.2.13-rmk2 (root@arm-linux.net) (gcc version egcs-2.91.66
> 19990325/philb (egcs-1.1.2 release)) #104 Fri Jan 14 20:47:10 EST 2000
> <4>NetWinder Floating Point Emulator V0.94.1 (c) 1998 Corel Computer
> Corp.
> PIC Installed Correctly !!
> Console: colour VGA+ 80x25
> 
> Calibrating delay loop... 4.63 BogoMIPS                <=========  Why ?
> 
> Memory: 14848k/16M available (1092k code, 20k reserved, 408k data, 16k
> init)
> <5>VFS: Diskquotas version dquot_6.4.0 initialized
> POSIX conformance testing by UNIFIX
> SA110_Control = 0x84aac201
> <7>PCI: DEC21285 revision 04
> PCI: Probing PCI hardware
> <7>PCI: master abort pc=[<C00152A8>]
> <7>PCI: parity error data parity error pc=[<C0015328>]
> <3>IRQ LOCK: IRQ31 is locking the system, disabled
> <7>PCI: 00:38 [102c/00e0] on irq 21
> <7>PCI: 00:40 [1106/0686] on irq 24
> <7>PCI: 00:41 [1106/0571] on irq 14
> <7>PCI: 00:42 [1106/3038] on irq 22
> <7>PCI: 00:44 [1106/3057] on irq 22
> <6>Linux NET4.0 for Linux 2.2
> <6>Based upon Swansea University Computer Society NET3.039
> <6>NET4: Unix domain sockets 1.0 for Linux NET4.0.
> <6>NET4: Linux TCP/IP 1.0 for NET4.0
> <6>IP Protocols: ICMP, UDP, TCP
> Starting kswapd v 1.5
> <6>parport0: PC-style at 0x3bc [SPP]
> <6>parport1: PC-style at 0x378 [SPP]
> <6>parport2: PC-style at 0x278 [SPP]
> <6>Detected PS/2 Mouse Port.
> <6>Serial driver version 4.27 with MANY_PORTS SHARE_IRQ DETECT_IRQ
> enabled
> Software Watchdog Timer: 0.05, timer margin: 60 sec
> <6>Real Time Clock Driver v1.09
> RAM disk driver initialized:  16 RAM disks of 4096K size
> <6>loop: registered device at major 7
> VP_IDE: IDE controller on PCI bus 00 dev 41
> VP_IDE: not 100% native mode: will probe irqs later
>     ide0: BM-DMA at 0xe800-0xe807, BIOS settings: hda:pio, hdb:pio
> ide0: VIA Bus-Master (U)DMA Timing Config Success
> probing for hda: present=0, media=32, probetype=ATA
> hda: FUJITSU MPD3084AT, ATA DISK drive
> probing for hdb: present=0, media=32, probetype=ATA
> probing for hdb: present=0, media=32, probetype=ATAPI
> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> <6>hda: FUJITSU MPD3084AT, 8063MB w/512kB Cache, CHS=16383/16/63
> <6>Floppy drive(s): fd0 is 1.44M, fd1 is 1.44M
> floppy0: Unable to grab DMA2 for the floppy driver
> md driver 0.36.6 MAX_MD_DEV=4, MAX_REAL=8
> <6>3c59x.c:v0.99H 11/17/98 Donald Becker
> http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html
> <6>Partition check:
> <6> hda: [PTBL] [1027/255/63] hda1 hda2 hda3
> VFS: Mounted root (ext2 filesystem) readonly.
> Freeing unused kernel memory: 16k init
> sh: memory violation at pc=0xe59cf000, lr=0x40004b9c (bad
> address=0xe59cf000, code 3)
> sh: memory violation at pc=0xe59cf000, lr=0x40004b9c (bad
> address=0xe59cf000, code 3)
> sh: memory violation at pc=0xe59cf000, lr=0x40004b9c (bad
> address=0xe59cf000, code 3)
> sh: memory violation at pc=0xe59cf000, lr=0x40004b9c (bad
> address=0xe59cf000, code 3)
> sh: memory violation at pc=0xe59cf000, lr=0x40004b9c (bad
> address=0xe59cf000, code 3)
> .....
> 
> 
> Please help me!
> If I could incorrectlly, tell me.
> 
> email : hmlee@donghoit.com
> 
> 
> unsubscribe: body of `unsubscribe linux-arm-kernel' to majordomo@lists.arm.linux.org.uk
> 


   _____
  |_____| ------------------------------------------------- ---+---+-
  |   |        Russell King       linux@arm.linux.org.uk      --- ---
  | | | |  http://www.arm.linux.org.uk/~rmk/armlinux.html    /  /  |
  | +-+-+                                                     --- -+-
  /   |               THE developer of ARM Linux              |+| /|\
 /  | | |                                                     ---  |
    +-+-+ -------------------------------------------------  /\\\  |

unsubscribe: body of `unsubscribe linux-arm-kernel' to majordomo@lists.arm.linux.org.uk

From owner-linux-arm-kernel@lists.arm.linux.org.uk  Fri Jan 14 19:33:58 2000
Received: (from majordomo@localhost)
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) id TAA12808
	for linux-arm-kernel-outgoing; Fri, 14 Jan 2000 19:33:58 GMT
Received: from caramon.arm.linux.org.uk (root@p48-robin-gui.tch.enablis.net [194.168.180.108])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id TAA12804
	for <linux-arm-kernel@lists.arm.linux.org.uk>; Fri, 14 Jan 2000 19:33:55 GMT
Received: from raistlin.arm.linux.org.uk (linux@raistlin [192.168.0.3])
	by caramon.arm.linux.org.uk (8.9.3/8.9.3) with ESMTP id TAA10682;
	Fri, 14 Jan 2000 19:33:54 GMT
From: Russell King - ARM Linux Admin <linux@arm.linux.org.uk>
Received: (from linux@localhost)
	by raistlin.arm.linux.org.uk (8.7.4/8.7.3) id TAA02119;
	Fri, 14 Jan 2000 19:33:12 GMT
Message-Id: <200001141933.TAA02119@raistlin.arm.linux.org.uk>
Subject: Re: memory violation problem in EBSA-285 like board
To: hmlee@donghoit.com (hmlee)
Date: Fri, 14 Jan 2000 19:33:11 +0000 (GMT)
Cc: linux-arm-kernel@lists.arm.linux.org.uk
In-Reply-To: <387F1CB9.7E3C9FA3@donghoit.com> from "hmlee" at Jan 14, 2000 09:55:22 PM
X-Mailer: ELM [version 2.5 PL1]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm-kernel@lists.arm.linux.org.uk
Precedence: bulk

I'll try again, this time remembering to answer elm 2.5 questions, rather
than elm 2.4 questions!

hmlee writes:
>...
> But "memory violation" occured as follows:
>...
> Calibrating delay loop... 4.63 BogoMIPS                <=========  Why ?

Sounds like the interrupt rate is too fast for some reason.  Can you check
you are only getting timer interrupts at 100Hz?

> PCI: Probing PCI hardware
> <7>PCI: master abort pc=[<C00152A8>]
> <7>PCI: parity error data parity error pc=[<C0015328>]
> <3>IRQ LOCK: IRQ31 is locking the system, disabled

Whoooops!  This is really really bad.  It appears that you are getting
corrupted transfers on the PCI bus.  If it is corrupted, then:

> Freeing unused kernel memory: 16k init
> sh: memory violation at pc=0xe59cf000, lr=0x40004b9c (bad
> address=0xe59cf000, code 3)
> sh: memory violation at pc=0xe59cf000, lr=0x40004b9c (bad
> address=0xe59cf000, code 3)
> sh: memory violation at pc=0xe59cf000, lr=0x40004b9c (bad
> address=0xe59cf000, code 3)
> sh: memory violation at pc=0xe59cf000, lr=0x40004b9c (bad
> address=0xe59cf000, code 3)
> sh: memory violation at pc=0xe59cf000, lr=0x40004b9c (bad
> address=0xe59cf000, code 3)
> .....

this could well be a result of it as well.
   _____
  |_____| ------------------------------------------------- ---+---+-
  |   |        Russell King       linux@arm.linux.org.uk      --- ---
  | | | |  http://www.arm.linux.org.uk/~rmk/armlinux.html    /  /  |
  | +-+-+                                                     --- -+-
  /   |               THE developer of ARM Linux              |+| /|\
 /  | | |                                                     ---  |
    +-+-+ -------------------------------------------------  /\\\  |

unsubscribe: body of `unsubscribe linux-arm-kernel' to majordomo@lists.arm.linux.org.uk

From owner-linux-arm-kernel@lists.arm.linux.org.uk  Fri Jan 14 23:38:34 2000
Received: (from majordomo@localhost)
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) id XAA09297
	for linux-arm-kernel-outgoing; Fri, 14 Jan 2000 23:38:34 GMT
Received: from crl.dec.com (crl.dec.com [192.58.206.2])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id XAA09293
	for <linux-arm-kernel@lists.arm.linux.org.uk>; Fri, 14 Jan 2000 23:38:31 GMT
Received: from ims.crl.dec.com (ims.crl.dec.com [16.11.0.11])
	by crl.dec.com (8.8.8/RWD-1.2) with ESMTP id SAA19485
	for <linux-arm-kernel@lists.arm.linux.org.uk>; Fri, 14 Jan 2000 18:38:31 -0500 (EST)
Received: by ims.crl.dec.com with Internet Mail Service (5.5.2650.21)
	id <C5GFKPZJ>; Fri, 14 Jan 2000 18:41:16 -0500
Message-ID: <D1674834F25BD3118B3208002BB90CD424A9E8@yen.crl.dec.com>
From: George France <france@crl.dec.com>
To: "'linux-arm-kernel@lists.arm.linux.org.uk'"
	 <linux-arm-kernel@lists.arm.linux.org.uk>
Subject: patches for ARM Linux
Date: Fri, 14 Jan 2000 18:38:35 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-linux-arm-kernel@lists.arm.linux.org.uk
Precedence: bulk

It appears to me that the patches for the ARM Linux kernel are getting
bigger and bigger.  Since there is an ARM arch section in the main Linux
distribution, why are the patches not being applied to the main kernel
distribution rather than getting larger and larger?  Please enlighten me.

Best Regards,


--George

George France,      france@crl.dec.com
Cambridge Research Laboratory, Compaq Computer Corporation
One Kendall Square, Building 700     MS: CRL
Cambridge, MA 02139 USA



unsubscribe: body of `unsubscribe linux-arm-kernel' to majordomo@lists.arm.linux.org.uk

From owner-linux-arm-kernel@lists.arm.linux.org.uk  Fri Jan 14 23:52:00 2000
Received: (from majordomo@localhost)
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) id XAA10176
	for linux-arm-kernel-outgoing; Fri, 14 Jan 2000 23:52:00 GMT
Received: from caramon.arm.linux.org.uk (root@p18-robin-gui.tch.enablis.net [194.168.180.78])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id XAA10170
	for <linux-arm-kernel@lists.arm.linux.org.uk>; Fri, 14 Jan 2000 23:51:57 GMT
Received: from raistlin.arm.linux.org.uk (linux@raistlin [192.168.0.3])
	by caramon.arm.linux.org.uk (8.9.3/8.9.3) with ESMTP id XAA11665;
	Fri, 14 Jan 2000 23:51:55 GMT
From: Russell King - ARM Linux Admin <linux@arm.linux.org.uk>
Received: (from linux@localhost)
	by raistlin.arm.linux.org.uk (8.7.4/8.7.3) id XAA01115;
	Fri, 14 Jan 2000 23:51:15 GMT
Message-Id: <200001142351.XAA01115@raistlin.arm.linux.org.uk>
Subject: Re: patches for ARM Linux
To: france@crl.dec.com (George France)
Date: Fri, 14 Jan 2000 23:51:14 +0000 (GMT)
Cc: linux-arm-kernel@lists.arm.linux.org.uk ('linux-arm-kernel@lists.arm.linux.org.uk')
In-Reply-To: <D1674834F25BD3118B3208002BB90CD424A9E8@yen.crl.dec.com> from "George France" at Jan 14, 2000 06:38:35 PM
X-Mailer: ELM [version 2.5 PL1]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm-kernel@lists.arm.linux.org.uk
Precedence: bulk

George France writes:
> It appears to me that the patches for the ARM Linux kernel are getting
> bigger and bigger.  Since there is an ARM arch section in the main Linux
> distribution, why are the patches not being applied to the main kernel
> distribution rather than getting larger and larger?  Please enlighten me.

Because it takes time for me to say "they're ready" - the next patch should
be smaller again.

The size of the patches will go up and down - this is natural.  The ARM
development tree (or the Alpha, sparc etc) can never be totally in sync
with Linus' kernels.
   _____
  |_____| ------------------------------------------------- ---+---+-
  |   |        Russell King       linux@arm.linux.org.uk      --- ---
  | | | |  http://www.arm.linux.org.uk/~rmk/armlinux.html    /  /  |
  | +-+-+                                                     --- -+-
  /   |               THE developer of ARM Linux              |+| /|\
 /  | | |                                                     ---  |
    +-+-+ -------------------------------------------------  /\\\  |

unsubscribe: body of `unsubscribe linux-arm-kernel' to majordomo@lists.arm.linux.org.uk

From owner-linux-arm-kernel@lists.arm.linux.org.uk  Mon Jan 17 22:22:33 2000
Received: (from majordomo@localhost)
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) id WAA15514
	for linux-arm-kernel-outgoing; Mon, 17 Jan 2000 22:22:33 GMT
Received: from fwsrv2.itt.com (fwsrv2.itt.com [151.190.254.230])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with SMTP id WAA15510
	for <linux-arm-kernel@lists.arm.linux.org.uk>; Mon, 17 Jan 2000 22:22:31 GMT
Received: by fwsrv2.itt.com; (5.65v4.0/1.3/10May95) id AA21402; Mon, 17 Jan 2000 09:17:51 -0500
Received: by fwemail2.de.ittind.com with Internet Mail Service (5.5.2650.21)
	id <C4PQLARM>; Mon, 17 Jan 2000 09:17:51 -0500
Message-Id: <CBB2C281DA4DD3119ECE00A0C9EBCEB0066CB8@acdnjmail1.acdnj.itt.com>
From: "Latham, Steve" <SLatham@acdnj.itt.com>
To: "'linux-arm-kernel@lists.arm.linux.org.uk'"
	 <linux-arm-kernel@lists.arm.linux.org.uk>
Subject: Is there a patch for SA-1110/Asabet
Date: Mon, 17 Jan 2000 09:17:48 -0500
Mime-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-linux-arm-kernel@lists.arm.linux.org.uk
Precedence: bulk

Is there a patch for Linux to SA-1110/Asabet?
Steve



unsubscribe: body of `unsubscribe linux-arm-kernel' to majordomo@lists.arm.linux.org.uk

From owner-linux-arm-kernel@lists.arm.linux.org.uk  Mon Jan 17 22:23:31 2000
Received: (from majordomo@localhost)
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) id WAA15532
	for linux-arm-kernel-outgoing; Mon, 17 Jan 2000 22:23:31 GMT
Received: from ganymede.or.intel.com (ganymede.or.intel.com [134.134.248.3])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id WAA15528
	for <linux-arm-kernel@lists.arm.linux.org.uk>; Mon, 17 Jan 2000 22:23:29 GMT
Received: from SMTP (orsmsxvs01-1.jf.intel.com [192.168.65.200])
	by ganymede.or.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.18 2000/01/07 21:56:55 dmccart Exp $) with SMTP id LAA23004
	for <linux-arm-kernel@lists.arm.linux.org.uk>; Mon, 17 Jan 2000 11:18:33 -0800 (PST)
Received: from orsmsx28.jf.intel.com ([192.168.70.28]) by 192.168.70.200
  (Norton AntiVirus for Internet Email Gateways 1.0) ;
  Mon, 17 Jan 2000 19:18:32 0000 (GMT)
Received: by orsmsx28.jf.intel.com with Internet Mail Service (5.5.2448.0)
	id <ZZZQ7JA6>; Mon, 17 Jan 2000 11:18:31 -0800
Message-ID: <7DAA70BEB463D211AC3E00A0C96B7AB20405D420@orsmsx41.jf.intel.com>
From: "Brandewie, Dirk J" <dirk.j.brandewie@intel.com>
To: ARM Kernel list <linux-arm-kernel@lists.arm.linux.org.uk>
Subject: Need help booting Image
Date: Mon, 17 Jan 2000 11:18:19 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_000_01BF611F.A1E56F71"
Sender: owner-linux-arm-kernel@lists.arm.linux.org.uk
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_000_01BF611F.A1E56F71
Content-Type: text/plain;
	charset="iso-8859-1"

Hi All,

I am hoping someone can help me.  The zImage I have built refuses
to boot.  The image starts to run but falls over when decompress_kernel()
is called from head.S.  Attached is the head.S I am using and dump
of the vmlinux image found in arch/arm/boot/compressed.  I do not
know how to disassemble the zImage directly. I someone could 
enlighten me I would like to see the that disassembly also. I
suspect that arm-linux-objdump might be implicated but no way to
prove it at the moment.

When the image boots "AB" is output to the terminal then nothing

I hope there is enough information here for someone to tell me
what I have done wrong. If more info is required please let me know

Thanks
--Dirk


------_=_NextPart_000_01BF611F.A1E56F71
Content-Type: application/octet-stream;
	name="VMLINUX.DIS"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename="VMLINUX.DIS"

=0A=
vmlinux:     file format elf32-littlearm=0A=
=0A=
Disassembly of section .text:=0A=
=0A=
00008000 <start>:=0A=
    8000:	e1a00000 	nop			(mov r0,r0)=0A=
    8004:	e1a00000 	nop			(mov r0,r0)=0A=
    8008:	e1a00000 	nop			(mov r0,r0)=0A=
    800c:	e1a00000 	nop			(mov r0,r0)=0A=
    8010:	e1a00000 	nop			(mov r0,r0)=0A=
    8014:	e1a00000 	nop			(mov r0,r0)=0A=
    8018:	e1a00000 	nop			(mov r0,r0)=0A=
    801c:	e1a00000 	nop			(mov r0,r0)=0A=
    8020:	ea000001 	b	802c <_load_addr+0x2c>=0A=
    8024:	016f2818 	cmneq	pc, r8, lsl r8=0A=
    8028:	00008000 	andeq	r8, r0, r0=0A=
    802c:	e3300000 	teq	r0, #0	; 0x0=0A=
    8030:	1afffffd 	bne	802c <_load_addr+0x2c>=0A=
    8034:	e3a0c041 	mov	r12, #65	; 0x41=0A=
    8038:	eb000061 	bl	81c4 <print_marker>=0A=
    803c:	e1a07001 	mov	r7, r1=0A=
    8040:	ee106f10 	mrc	15, 0, r6, cr0, cr0, {0}=0A=
    8044:	e28f2e21 	add	r2, pc, #528	; 0x210=0A=
    8048:	e892203c 	ldmia	r2, {r2, r3, r4, r5, sp}=0A=
    804c:	e3a00000 	mov	r0, #0	; 0x0=0A=
    8050:	e4820004 	str	r0, [r2], #4=0A=
    8054:	e4820004 	str	r0, [r2], #4=0A=
    8058:	e4820004 	str	r0, [r2], #4=0A=
    805c:	e4820004 	str	r0, [r2], #4=0A=
    8060:	e1520003 	cmp	r2, r3=0A=
    8064:	bafffff9 	blt	8050 <_load_addr+0x50>=0A=
    8068:	e1a0100d 	mov	r1, sp=0A=
    806c:	e28d2801 	add	r2, sp, #65536	; 0x10000=0A=
    8070:	e1340005 	teq	r4, r5=0A=
    8074:	01a05002 	moveq	r5, r2=0A=
    8078:	11a05004 	movne	r5, r4=0A=
    807c:	e1a00005 	mov	r0, r5=0A=
    8080:	e1a03007 	mov	r3, r7=0A=
    8084:	eb00004e 	bl	81c4 <print_marker>=0A=
    8088:	eb000901 	bl	a494 <decompress_kernel>=0A=
    808c:	e1340005 	teq	r4, r5=0A=
    8090:	0a000024 	beq	8128 <call_kernel>=0A=
    8094:	e280007f 	add	r0, r0, #127	; 0x7f=0A=
    8098:	e3c0007f 	bic	r0, r0, #127	; 0x7f=0A=
    809c:	e0851000 	add	r1, r5, r0=0A=
    80a0:	e28f2034 	add	r2, pc, #52	; 0x34=0A=
    80a4:	e28f3e1b 	add	r3, pc, #432	; 0x1b0=0A=
    80a8:	e8b23f00 	ldmia	r2!, {r8, r9, r10, r11, r12, sp}=0A=
    80ac:	e8a13f00 	stmia	r1!, {r8, r9, r10, r11, r12, sp}=0A=
    80b0:	e8b23f00 	ldmia	r2!, {r8, r9, r10, r11, r12, sp}=0A=
    80b4:	e8a13f00 	stmia	r1!, {r8, r9, r10, r11, r12, sp}=0A=
    80b8:	e1520003 	cmp	r2, r3=0A=
    80bc:	bafffff9 	blt	80a8 <_load_addr+0xa8>=0A=
    80c0:	e2261311 	eor	r1, r6, #1140850688	; 0x44000000=0A=
    80c4:	e2211801 	eor	r1, r1, #65536	; 0x10000=0A=
    80c8:	e2211ca1 	eor	r1, r1, #41216	; 0xa100=0A=
    80cc:	e1b01221 	movs	r1, r1, lsr #4=0A=
    80d0:	0e071f17 	mcreq	15, 0, r1, cr7, cr7, {0}=0A=
    80d4:	0e071f9a 	mcreq	15, 0, r1, cr7, cr10, {4}=0A=
    80d8:	e085f000 	add	pc, r5, r0=0A=
=0A=
000080dc <reloc_start>:=0A=
    80dc:	e0858000 	add	r8, r5, r0=0A=
    80e0:	e1a00008 	mov	r0, r8=0A=
    80e4:	e1a01004 	mov	r1, r4=0A=
    80e8:	e8b53f0c 	ldmia	r5!, {r2, r3, r8, r9, r10, r11, r12, sp}=0A=
    80ec:	e8a13f0c 	stmia	r1!, {r2, r3, r8, r9, r10, r11, r12, sp}=0A=
    80f0:	e8b53f0c 	ldmia	r5!, {r2, r3, r8, r9, r10, r11, r12, sp}=0A=
    80f4:	e8a13f0c 	stmia	r1!, {r2, r3, r8, r9, r10, r11, r12, sp}=0A=
    80f8:	e8b53f0c 	ldmia	r5!, {r2, r3, r8, r9, r10, r11, r12, sp}=0A=
    80fc:	e8a13f0c 	stmia	r1!, {r2, r3, r8, r9, r10, r11, r12, sp}=0A=
    8100:	e8b53f0c 	ldmia	r5!, {r2, r3, r8, r9, r10, r11, r12, sp}=0A=
    8104:	e8a13f0c 	stmia	r1!, {r2, r3, r8, r9, r10, r11, r12, sp}=0A=
    8108:	e1550000 	cmp	r5, r0=0A=
    810c:	bafffff5 	blt	80e8 <reloc_start+0xc>=0A=
    8110:	e2260311 	eor	r0, r6, #1140850688	; 0x44000000=0A=
    8114:	e2200801 	eor	r0, r0, #65536	; 0x10000=0A=
    8118:	e2200ca1 	eor	r0, r0, #41216	; 0xa100=0A=
    811c:	e1b00220 	movs	r0, r0, lsr #4=0A=
    8120:	0e070f17 	mcreq	15, 0, r0, cr7, cr7, {0}=0A=
    8124:	0e071f9a 	mcreq	15, 0, r1, cr7, cr10, {4}=0A=
=0A=
00008128 <call_kernel>:=0A=
    8128:	e3a00000 	mov	r0, #0	; 0x0=0A=
    812c:	e1a01007 	mov	r1, r7=0A=
    8130:	e1a0f004 	mov	pc, r4=0A=
=0A=
00008134 <phexbuf>:=0A=
	...=0A=
=0A=
00008140 <phex>:=0A=
    8140:	e24f3014 	sub	r3, pc, #20	; 0x14=0A=
    8144:	e3a02000 	mov	r2, #0	; 0x0=0A=
    8148:	e7c32001 	strb	r2, [r3, r1]=0A=
    814c:	e2511001 	subs	r1, r1, #1	; 0x1=0A=
    8150:	41a00003 	movmi	r0, r3=0A=
    8154:	4a000006 	bmi	8174 <puts>=0A=
    8158:	e200200f 	and	r2, r0, #15	; 0xf=0A=
    815c:	e1a00220 	mov	r0, r0, lsr #4=0A=
    8160:	e352000a 	cmp	r2, #10	; 0xa=0A=
    8164:	a2822007 	addge	r2, r2, #7	; 0x7=0A=
    8168:	e2822030 	add	r2, r2, #48	; 0x30=0A=
    816c:	e7c32001 	strb	r2, [r3, r1]=0A=
    8170:	eafffff5 	b	814c <phex+0xc>=0A=
=0A=
00008174 <puts>:=0A=
    8174:	e3a03403 	mov	r3, #50331648	; 0x3000000=0A=
    8178:	e3833801 	orr	r3, r3, #65536	; 0x10000=0A=
    817c:	e4d02001 	ldrb	r2, [r0], #1=0A=
    8180:	e3320000 	teq	r2, #0	; 0x0=0A=
    8184:	01a0f00e 	moveq	pc, lr=0A=
    8188:	e5c32fe0 	strb	r2, [r3, #4064]=0A=
    818c:	e3a01802 	mov	r1, #131072	; 0x20000=0A=
    8190:	e2511001 	subs	r1, r1, #1	; 0x1=0A=
    8194:	1afffffd 	bne	8190 <puts+0x1c>=0A=
    8198:	e332000a 	teq	r2, #10	; 0xa=0A=
    819c:	03a0200d 	moveq	r2, #13	; 0xd=0A=
    81a0:	0afffff8 	beq	8188 <puts+0x14>=0A=
    81a4:	e3300000 	teq	r0, #0	; 0x0=0A=
    81a8:	1afffff3 	bne	817c <puts+0x8>=0A=
    81ac:	e1a0f00e 	mov	pc, lr=0A=
=0A=
000081b0 <putc>:=0A=
    81b0:	e1a02000 	mov	r2, r0=0A=
    81b4:	e3a00000 	mov	r0, #0	; 0x0=0A=
    81b8:	e3a03403 	mov	r3, #50331648	; 0x3000000=0A=
    81bc:	e3833801 	orr	r3, r3, #65536	; 0x10000=0A=
    81c0:	eafffff0 	b	8188 <puts+0x14>=0A=
=0A=
000081c4 <print_marker>:=0A=
    81c4:	e3a0b442 	mov	r11, #1107296256	; 0x42000000=0A=
    81c8:	e38bbe16 	orr	r11, r11, #352	; 0x160=0A=
    81cc:	e58bc000 	str	r12, [r11]=0A=
    81d0:	e59b9018 	ldr	r9, [r11, #24]=0A=
    81d4:	e3190020 	tst	r9, #32	; 0x20=0A=
    81d8:	1afffffc 	bne	81d0 <print_marker+0xc>=0A=
    81dc:	e28cc001 	add	r12, r12, #1	; 0x1=0A=
    81e0:	e1a0f00e 	mov	pc, lr=0A=
=0A=
000081e4 <memdump>:=0A=
    81e4:	e1a0c000 	mov	r12, r0=0A=
    81e8:	e1a0a00e 	mov	r10, lr=0A=
    81ec:	e3a01008 	mov	r1, #8	; 0x8=0A=
    81f0:	ebffffd2 	bl	8140 <phex>=0A=
    81f4:	e3a0000a 	mov	r0, #10	; 0xa=0A=
    81f8:	ebffffec 	bl	81b0 <putc>=0A=
    81fc:	e3a0b000 	mov	r11, #0	; 0x0=0A=
    8200:	e1a0010b 	mov	r0, r11, lsl #2=0A=
    8204:	e3a01004 	mov	r1, #4	; 0x4=0A=
    8208:	ebffffcc 	bl	8140 <phex>=0A=
    820c:	e3a0003a 	mov	r0, #58	; 0x3a=0A=
    8210:	ebffffe6 	bl	81b0 <putc>=0A=
    8214:	e3a00020 	mov	r0, #32	; 0x20=0A=
    8218:	ebffffe4 	bl	81b0 <putc>=0A=
    821c:	e79c010b 	ldr	r0, [r12, r11, lsl #2]=0A=
    8220:	e3a01008 	mov	r1, #8	; 0x8=0A=
    8224:	ebffffc5 	bl	8140 <phex>=0A=
    8228:	e20b0007 	and	r0, r11, #7	; 0x7=0A=
    822c:	e3300003 	teq	r0, #3	; 0x3=0A=
    8230:	03a00020 	moveq	r0, #32	; 0x20=0A=
    8234:	0bffffdd 	bleq	81b0 <putc>=0A=
    8238:	e20b0007 	and	r0, r11, #7	; 0x7=0A=
    823c:	e28bb001 	add	r11, r11, #1	; 0x1=0A=
    8240:	e3300007 	teq	r0, #7	; 0x7=0A=
    8244:	1afffff2 	bne	8214 <memdump+0x30>=0A=
    8248:	e3a0000a 	mov	r0, #10	; 0xa=0A=
    824c:	ebffffd7 	bl	81b0 <putc>=0A=
    8250:	e35b0040 	cmp	r11, #64	; 0x40=0A=
    8254:	baffffe9 	blt	8200 <memdump+0x1c>=0A=
    8258:	e1a0f00a 	mov	pc, r10=0A=
=0A=
0000825c <LC0>:=0A=
    825c:	00047fc4 	andeq	r7, r4, r4, asr #31=0A=
    8260:	000503fc 	streqsh	r0, [r5], -r12=0A=
    8264:	00008000 	andeq	r8, r0, r0=0A=
    8268:	00008000 	andeq	r8, r0, r0=0A=
    826c:	000513fc 	streqsh	r1, [r5], -r12=0A=
=0A=
00008270 <puts>:=0A=
    8270:	e1a0c00d 	mov	r12, sp=0A=
    8274:	e92dd800 	stmdb	sp!, {r11, r12, lr, pc}=0A=
    8278:	e5d03000 	ldrb	r3, [r0]=0A=
    827c:	e24cb004 	sub	r11, r12, #4	; 0x4=0A=
    8280:	e3530000 	cmp	r3, #0	; 0x0=0A=
    8284:	0a00001c 	beq	82fc <puts+0x8c>=0A=
    8288:	e59fe070 	ldr	lr, [pc, #70]	; 8300 <puts+0x90>=0A=
    828c:	e1a0c000 	mov	r12, r0=0A=
    8290:	e4dc2001 	ldrb	r2, [r12], #1=0A=
    8294:	e59f1068 	ldr	r1, [pc, #68]	; 8304 <puts+0x94>=0A=
    8298:	e5913000 	ldr	r3, [r1]=0A=
    829c:	e3130010 	tst	r3, #16	; 0x10=0A=
    82a0:	1afffffc 	bne	8298 <puts+0x28>=0A=
    82a4:	e58e2000 	str	r2, [lr]=0A=
    82a8:	e59f2054 	ldr	r2, [pc, #54]	; 8304 <puts+0x94>=0A=
    82ac:	e5923000 	ldr	r3, [r2]=0A=
    82b0:	e3130010 	tst	r3, #16	; 0x10=0A=
    82b4:	1afffffc 	bne	82ac <puts+0x3c>=0A=
    82b8:	e5d03000 	ldrb	r3, [r0]=0A=
    82bc:	e353000a 	cmp	r3, #10	; 0xa=0A=
    82c0:	1a000009 	bne	82ec <puts+0x7c>=0A=
    82c4:	e3a0100d 	mov	r1, #13	; 0xd=0A=
    82c8:	e59f2034 	ldr	r2, [pc, #34]	; 8304 <puts+0x94>=0A=
    82cc:	e5923000 	ldr	r3, [r2]=0A=
    82d0:	e3130010 	tst	r3, #16	; 0x10=0A=
    82d4:	1afffffc 	bne	82cc <puts+0x5c>=0A=
    82d8:	e58e1000 	str	r1, [lr]=0A=
    82dc:	e59f2020 	ldr	r2, [pc, #20]	; 8304 <puts+0x94>=0A=
    82e0:	e5923000 	ldr	r3, [r2]=0A=
    82e4:	e3130010 	tst	r3, #16	; 0x10=0A=
    82e8:	1afffffc 	bne	82e0 <puts+0x70>=0A=
    82ec:	e1a0000c 	mov	r0, r12=0A=
    82f0:	e5d03000 	ldrb	r3, [r0]=0A=
    82f4:	e3530000 	cmp	r3, #0	; 0x0=0A=
    82f8:	1affffe3 	bne	828c <puts+0x1c>=0A=
    82fc:	e91ba800 	ldmdb	r11, {r11, sp, pc}=0A=
    8300:	42000160 	andmi	r0, r0, #24	; 0x18=0A=
    8304:	42000178 	andmi	r0, r0, #30	; 0x1e=0A=
=0A=
00008308 <__memzero>:=0A=
    8308:	e1a0c00d 	mov	r12, sp=0A=
    830c:	e92dd800 	stmdb	sp!, {r11, r12, lr, pc}=0A=
    8310:	e24cb004 	sub	r11, r12, #4	; 0x4=0A=
    8314:	e1a022a1 	mov	r2, r1, lsr #5=0A=
    8318:	e3520000 	cmp	r2, #0	; 0x0=0A=
    831c:	da00000b 	ble	8350 <__memzero+0x48>=0A=
    8320:	e3a03000 	mov	r3, #0	; 0x0=0A=
    8324:	e4803004 	str	r3, [r0], #4=0A=
    8328:	e4803004 	str	r3, [r0], #4=0A=
    832c:	e4803004 	str	r3, [r0], #4=0A=
    8330:	e4803004 	str	r3, [r0], #4=0A=
    8334:	e4803004 	str	r3, [r0], #4=0A=
    8338:	e4803004 	str	r3, [r0], #4=0A=
    833c:	e2422001 	sub	r2, r2, #1	; 0x1=0A=
    8340:	e4803004 	str	r3, [r0], #4=0A=
    8344:	e3520000 	cmp	r2, #0	; 0x0=0A=
    8348:	e4803004 	str	r3, [r0], #4=0A=
    834c:	cafffff4 	bgt	8324 <__memzero+0x1c>=0A=
    8350:	e3110010 	tst	r1, #16	; 0x10=0A=
    8354:	0a000004 	beq	836c <__memzero+0x64>=0A=
    8358:	e3a03000 	mov	r3, #0	; 0x0=0A=
    835c:	e4803004 	str	r3, [r0], #4=0A=
    8360:	e4803004 	str	r3, [r0], #4=0A=
    8364:	e4803004 	str	r3, [r0], #4=0A=
    8368:	e4803004 	str	r3, [r0], #4=0A=
    836c:	e3110008 	tst	r1, #8	; 0x8=0A=
    8370:	0a000002 	beq	8380 <__memzero+0x78>=0A=
    8374:	e3a03000 	mov	r3, #0	; 0x0=0A=
    8378:	e4803004 	str	r3, [r0], #4=0A=
    837c:	e4803004 	str	r3, [r0], #4=0A=
    8380:	e3110004 	tst	r1, #4	; 0x4=0A=
    8384:	13a03000 	movne	r3, #0	; 0x0=0A=
    8388:	14803004 	strne	r3, [r0], #4=0A=
    838c:	e3110002 	tst	r1, #2	; 0x2=0A=
    8390:	0a000002 	beq	83a0 <__memzero+0x98>=0A=
    8394:	e3a03000 	mov	r3, #0	; 0x0=0A=
    8398:	e4c03001 	strb	r3, [r0], #1=0A=
    839c:	e4c03001 	strb	r3, [r0], #1=0A=
    83a0:	e3110001 	tst	r1, #1	; 0x1=0A=
    83a4:	13a03000 	movne	r3, #0	; 0x0=0A=
    83a8:	15c03000 	strneb	r3, [r0]=0A=
    83ac:	e91ba800 	ldmdb	r11, {r11, sp, pc}=0A=
=0A=
0000a494 <decompress_kernel>:=0A=
    a494:	e1a0c00d 	mov	r12, sp=0A=
    a498:	e92dd800 	stmdb	sp!, {r11, r12, lr, pc}=0A=
    a49c:	e24cb004 	sub	r11, r12, #4	; 0x4=0A=
    a4a0:	e59fc068 	ldr	r12, [pc, #68]	; a510 =
<decompress_kernel+0x7c>=0A=
    a4a4:	e58c0000 	str	r0, [r12]=0A=
    a4a8:	e59f0064 	ldr	r0, [pc, #64]	; a514 =
<decompress_kernel+0x80>=0A=
    a4ac:	e5801000 	str	r1, [r0]=0A=
    a4b0:	e59f1060 	ldr	r1, [pc, #60]	; a518 =
<decompress_kernel+0x84>=0A=
    a4b4:	e5812000 	str	r2, [r1]=0A=
    a4b8:	e59f205c 	ldr	r2, [pc, #5c]	; a51c =
<decompress_kernel+0x88>=0A=
    a4bc:	e5823000 	str	r3, [r2]=0A=
    a4c0:	ee100f10 	mrc	15, 0, r0, cr0, cr0, {0}=0A=
    a4c4:	e2200311 	eor	r0, r0, #1140850688	; 0x44000000=0A=
    a4c8:	e2200801 	eor	r0, r0, #65536	; 0x10000=0A=
    a4cc:	e2200ca1 	eor	r0, r0, #41216	; 0xa100=0A=
    a4d0:	e1b00220 	movs	r0, r0, lsr #4=0A=
    a4d4:	0e070f15 	mcreq	15, 0, r0, cr7, cr5, {0}=0A=
    a4d8:	0e110f10 	mrceq	15, 0, r0, cr1, cr0, {0}=0A=
    a4dc:	03800a01 	orreq	r0, r0, #4096	; 0x1000=0A=
    a4e0:	0e010f10 	mcreq	15, 0, r0, cr1, cr0, {0}=0A=
    a4e4:	e3a00000 	mov	r0, #0	; 0x0=0A=
    a4e8:	0e0f0f51 	mcreq	15, 0, r0, cr15, cr1, {2}=0A=
    a4ec:	ebfffdc8 	bl	9c14 <makecrc>=0A=
    a4f0:	e59f0028 	ldr	r0, [pc, #28]	; a520 =
<decompress_kernel+0x8c>=0A=
    a4f4:	ebfff75d 	bl	8270 <puts>=0A=
    a4f8:	ebfffdf1 	bl	9cc4 <gunzip>=0A=
    a4fc:	e59f0020 	ldr	r0, [pc, #20]	; a524 =
<decompress_kernel+0x90>=0A=
    a500:	ebfff75a 	bl	8270 <puts>=0A=
    a504:	e59f301c 	ldr	r3, [pc, #1c]	; a528 =
<decompress_kernel+0x94>=0A=
    a508:	e5930000 	ldr	r0, [r3]=0A=
    a50c:	e91ba800 	ldmdb	r11, {r11, sp, pc}=0A=
    a510:	0004ffd4 	streqsb	pc, [r4], -r4=0A=
    a514:	0004ffe0 	andeq	pc, r4, r0, ror #31=0A=
    a518:	0004ffe4 	andeq	pc, r4, r4, ror #31=0A=
    a51c:	000503f8 	streqsh	r0, [r5], -r8=0A=
    a520:	00047f90 	muleq	r4, r0, pc=0A=
    a524:	00047fa8 	andeq	r7, r4, r8, lsr #31=0A=
    a528:	0004ffd8 	streqsb	pc, [r4], -r8=0A=
=0A=
0000a52c <_binary_piggy_gz_start>:=0A=
=0A=
00047b9d <_binary_piggy_gz_end>:=0A=
   47b9d:	Address 0x47b9d is out of bounds.=0A=
=0A=
Disassembly of section .glue_7t:=0A=
Disassembly of section .glue_7:=0A=

------_=_NextPart_000_01BF611F.A1E56F71
Content-Type: application/octet-stream;
	name="HEAD.S"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename="HEAD.S"

/*=0A=
 * linux/arch/arm/boot/compressed/head.S=0A=
 *=0A=
 * Copyright (C) 1996-1999 Russell King=0A=
 */=0A=
#include <linux/linkage.h>=0A=
=0A=
		.section ".start", #alloc, #execinstr=0A=
/*=0A=
 * sort out different calling conventions=0A=
 */=0A=
		.align=0A=
start:=0A=
		.type	start,#function=0A=
		.rept	8=0A=
		mov	r0, r0=0A=
		.endr=0A=
=0A=
		b	1f=0A=
		.word	0x016f2818		@ Magic numbers to help the loader=0A=
		.word	start	=0A=
1:=0A=
=0A=
		/*=0A=
		 * some architecture specific code can=0A=
		 * be inserted by the linker here=0A=
		 */=0A=
=0A=
		.text=0A=
1:		teq	r0, #0=0A=
		bne	1b=0A=
        mov r12, #'A'=0A=
        bl print_marker=0A=
		mov	r7, r1			@ save architecture ID=0A=
		mrc	p15, 0, r6, c0, c0	@ get processor ID=0A=
		adr	r2, LC0=0A=
		ldmia	r2, {r2, r3, r4, r5, sp}=0A=
=0A=
		mov	r0, #0=0A=
1:		str	r0, [r2], #4		@ clear bss=0A=
		str	r0, [r2], #4=0A=
		str	r0, [r2], #4=0A=
		str	r0, [r2], #4=0A=
		cmp	r2, r3=0A=
		blt	1b=0A=
=0A=
		mov	r1, sp			@ malloc space above stack=0A=
		add	r2, sp, #0x10000	@ 64k max=0A=
=0A=
		teq	r4, r5			@ will we overwrite ourselves?=0A=
		moveq	r5, r2=0A=
		movne	r5, r4=0A=
=0A=
		mov	r0, r5=0A=
		mov	r3, r7=0A=
        bl print_marker=0A=
		bl	SYMBOL_NAME(decompress_kernel)=0A=
=0A=
		teq	r4, r5			@ do we need to relocate=0A=
		beq	call_kernel		@ the kernel?=0A=
=0A=
		add	r0, r0, #127=0A=
		bic	r0, r0, #127		@ align the kernel length=0A=
/*=0A=
 * r0     =3D decompressed kernel length=0A=
 * r1-r3  =3D unused=0A=
 * r4     =3D kernel execution address=0A=
 * r5     =3D decompressed kernel start=0A=
 * r6     =3D processor ID=0A=
 * r7     =3D architecture ID=0A=
 * r8-r14 =3D unused=0A=
 */=0A=
		add	r1, r5, r0		@ end of decompressed kernel=0A=
		adr	r2, reloc_start=0A=
		adr	r3, reloc_end=0A=
1:		ldmia	r2!, {r8 - r13}		@ copy relocation code=0A=
		stmia	r1!, {r8 - r13}=0A=
		ldmia	r2!, {r8 - r13}=0A=
		stmia	r1!, {r8 - r13}=0A=
		cmp	r2, r3=0A=
		blt	1b=0A=
=0A=
		eor	r1, r6, #0x44 << 24	@ SA-110?=0A=
		eor	r1, r1, #0x01 << 16=0A=
		eor	r1, r1, #0xa1 << 8=0A=
		movs	r1, r1, lsr #4=0A=
		mcreq	p15, 0, r1, c7, c7, 0	@ flush I & D-cache=0A=
		mcreq	p15, 0, r1, c7, c10, 4	@ drain WB=0A=
		add	pc, r5, r0		@ call relocation code=0A=
=0A=
/*=0A=
 * r0     =3D decompressed kernel length=0A=
 * r1-r3  =3D unused=0A=
 * r4     =3D kernel execution address=0A=
 * r5     =3D decompressed kernel start=0A=
 * r6     =3D processor ID=0A=
 * r7     =3D architecture ID=0A=
 * r8-r14 =3D unused=0A=
 */=0A=
reloc_start:	add	r8, r5, r0=0A=
#if 0=0A=
	mov r0, #'\n'=0A=
	bl putc=0A=
	mov r0, r6=0A=
	mov r1, #8=0A=
	bl phex=0A=
	mov r0, #':'=0A=
	bl putc=0A=
	mov r0, r5=0A=
	mov r1, #8=0A=
	bl phex=0A=
	mov r0, #'-'=0A=
	bl putc=0A=
	mov r0, r8=0A=
	mov r1, #8=0A=
	bl phex=0A=
	mov r0, #'>'=0A=
	bl putc=0A=
	mov r0, r4=0A=
	mov r1, #8=0A=
	bl phex=0A=
	mov r0, #'\n'=0A=
	bl putc=0A=
#endif=0A=
		mov	r0, r8=0A=
		mov	r1, r4=0A=
1:=0A=
		.rept	4=0A=
		ldmia	r5!, {r2, r3, r8 - r13}	@ relocate kernel=0A=
		stmia	r1!, {r2, r3, r8 - r13}=0A=
		.endr=0A=
=0A=
		cmp	r5, r0=0A=
		blt	1b=0A=
#if 0=0A=
	mov r8, r0=0A=
	mov r0, r5=0A=
	mov r1, #8=0A=
	bl phex=0A=
	mov r0, #'-'=0A=
	bl putc=0A=
	mov r0, r8=0A=
	mov r1, #8=0A=
	bl phex=0A=
	mov r0, #'\n'=0A=
	bl putc=0A=
	mov r0, r4=0A=
	bl  memdump=0A=
#endif=0A=
		eor	r0, r6, #0x44 << 24	@ SA-110?=0A=
		eor	r0, r0, #0x01 << 16=0A=
		eor	r0, r0, #0xa1 << 8=0A=
		movs	r0, r0, lsr #4=0A=
		mcreq	p15, 0, r0, c7, c7, 0	@ flush I cache=0A=
		mcreq	p15, 0, r1, c7, c10, 4	@ drain WB=0A=
=0A=
call_kernel:	mov	r0, #0=0A=
		mov	r1, r7			@ restore architecture number=0A=
		mov	pc, r4			@ call kernel=0A=
=0A=
=0A=
phexbuf:	.space	12=0A=
=0A=
#if 0=0A=
		.macro	loadsp,	rb=0A=
		mov	\rb, #0x7c000000=0A=
		.endm=0A=
=0A=
		.macro	writeb,	rb=0A=
		strb	\rb, [r3, #0x3f8]=0A=
		.endm=0A=
#else=0A=
		.macro	loadsp,	rb=0A=
		mov	\rb, #0x03000000=0A=
		orr	\rb, \rb, #0x00010000=0A=
		.endm=0A=
=0A=
		.macro	writeb,	rb=0A=
		strb	\rb, [r3, #0x3f8 << 2]=0A=
		.endm=0A=
#endif=0A=
=0A=
phex:		adr	r3, phexbuf=0A=
		mov	r2, #0=0A=
		strb	r2, [r3, r1]=0A=
1:		subs	r1, r1, #1=0A=
		movmi	r0, r3=0A=
		bmi	puts=0A=
		and	r2, r0, #15=0A=
		mov	r0, r0, lsr #4=0A=
		cmp	r2, #10=0A=
		addge	r2, r2, #7=0A=
		add	r2, r2, #'0'=0A=
		strb	r2, [r3, r1]=0A=
		b	1b=0A=
=0A=
puts:		loadsp	r3=0A=
1:		ldrb	r2, [r0], #1=0A=
		teq	r2, #0=0A=
		moveq	pc, lr=0A=
2:		writeb	r2=0A=
		mov	r1, #0x00020000=0A=
3:		subs	r1, r1, #1=0A=
		bne	3b=0A=
		teq	r2, #'\n'=0A=
		moveq	r2, #'\r'=0A=
		beq	2b=0A=
		teq	r0, #0=0A=
		bne	1b=0A=
		mov	pc, lr=0A=
putc:=0A=
		mov	r2, r0=0A=
		mov	r0, #0=0A=
		loadsp	r3=0A=
		b	2b=0A=
=0A=
print_marker:=0A=
	mov	r11, #0x42000000=0A=
	orr	r11, r11, #0x160=0A=
1:	str	r12, [r11]=0A=
2:	ldr	r9, [r11, #24]=0A=
	tst	r9, #1 << 5=0A=
	bne	2b=0A=
    add r12, r12, #1    =0A=
	mov	pc, lr=0A=
=0A=
memdump:	mov	r12, r0=0A=
		mov	r10, lr=0A=
		mov	r1, #8=0A=
		bl	phex=0A=
		mov	r0, #'\n'=0A=
		bl	putc=0A=
		mov	r11, #0=0A=
2:		mov	r0, r11, lsl #2=0A=
		mov	r1, #4=0A=
		bl	phex=0A=
		mov	r0, #':'=0A=
		bl	putc=0A=
1:		mov	r0, #' '=0A=
		bl	putc=0A=
		ldr	r0, [r12, r11, lsl #2]=0A=
		mov	r1, #8=0A=
		bl	phex=0A=
		and	r0, r11, #7=0A=
		teq	r0, #3=0A=
		moveq	r0, #' '=0A=
		bleq	putc=0A=
		and	r0, r11, #7=0A=
		add	r11, r11, #1=0A=
		teq	r0, #7=0A=
		bne	1b=0A=
		mov	r0, #'\n'=0A=
		bl	putc=0A=
		cmp	r11, #64=0A=
		blt	2b=0A=
		mov	pc, r10=0A=
reloc_end:=0A=
=0A=
LC0:		.word	__bss_start=0A=
		.word	_end=0A=
		.word	_load_addr=0A=
		.word	_start=0A=
		.word	user_stack+4096=0A=
		.align=0A=
=0A=
		.section	".stack"=0A=
user_stack:	.space	4096=0A=

------_=_NextPart_000_01BF611F.A1E56F71--


unsubscribe: body of `unsubscribe linux-arm-kernel' to majordomo@lists.arm.linux.org.uk

From owner-linux-arm-kernel@lists.arm.linux.org.uk  Mon Jan 17 22:39:24 2000
Received: (from majordomo@localhost)
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) id WAA16072
	for linux-arm-kernel-outgoing; Mon, 17 Jan 2000 22:39:24 GMT
Received: from caramon.arm.linux.org.uk (root@p18-magpie-gui.tch.enablis.net [194.168.180.18])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id WAA16068
	for <linux-arm-kernel@lists.arm.linux.org.uk>; Mon, 17 Jan 2000 22:39:20 GMT
Received: from raistlin.arm.linux.org.uk (root@raistlin [192.168.0.3])
	by caramon.arm.linux.org.uk (8.9.3/8.9.3) with ESMTP id WAA25693;
	Mon, 17 Jan 2000 22:39:13 GMT
From: Russell King - ARM Linux Admin <linux@arm.linux.org.uk>
Received: (from linux@localhost)
	by raistlin.arm.linux.org.uk (8.7.4/8.7.3) id WAA00916;
	Mon, 17 Jan 2000 22:38:10 GMT
Message-Id: <200001172238.WAA00916@raistlin.arm.linux.org.uk>
Subject: Re: Getting the kernel to boot on the EBSA-285
To: dirk@homemail.com
Date: Mon, 17 Jan 2000 22:38:09 +0000 (GMT)
Cc: dirk.j.brandewie@intel.com (Brandewie Dirk J),
        linux-arm-kernel@lists.arm.linux.org.uk (ARM Kernel list)
In-Reply-To: <000801bf5e58$114daf20$99a82104@t5e4i9.dsl.gtei.net> from "Dirk Brandewie" at Jan 13, 2000 10:24:46 PM
X-Mailer: ELM [version 2.5 PL1]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm-kernel@lists.arm.linux.org.uk
Precedence: bulk

Dirk Brandewie writes:
> Here is the fix for the typo.  I really should have read the post closer
> before sending :-(
> --Dirk
> -----Original Message-----
> From: Brandewie, Dirk J <dirk.j.brandewie@intel.com>
> To: ARM Kernel list <linux-arm-kernel@lists.arm.linux.org.uk>
> Date: Thursday, January 13, 2000 7:57 PM
> Subject: Getting the kernel to boot on the EBSA-285
> 
> 
> 
> >BTW I believe there is a bug in arch-ebsa285/uncompress.h
> >Line 19 reads "while (DC21285_BASE[6] & 8);"  I think someone meant
> >to say "while (DC21285_BASE[6] & 10);" if the code was meant to 
> >wait for the transmit FIFO to be un-busy
> >
> Fixed line should be "while (DC21285_BASE[6] & 0x10);" 

Err, I think someone's confused.  The bits in the register are defined
to be:

 2:0	Read as 0
 3	Transmitter busy
 4	Receive FIFO status
 5	Transmit FIFO status
 31:6	Read as 0

Therefore, '8' is correct.
   _____
  |_____| ------------------------------------------------- ---+---+-
  |   |        Russell King       linux@arm.linux.org.uk      --- ---
  | | | |  http://www.arm.linux.org.uk/~rmk/armlinux.html    /  /  |
  | +-+-+                                                     --- -+-
  /   |               THE developer of ARM Linux              |+| /|\
 /  | | |                                                     ---  |
    +-+-+ -------------------------------------------------  /\\\  |

unsubscribe: body of `unsubscribe linux-arm-kernel' to majordomo@lists.arm.linux.org.uk

From owner-linux-arm-kernel@lists.arm.linux.org.uk  Tue Jan 18 21:23:40 2000
Received: (from majordomo@localhost)
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) id VAA10188
	for linux-arm-kernel-outgoing; Tue, 18 Jan 2000 21:23:40 GMT
Received: from www3.gmx.net (www3.gmx.net [195.63.104.43])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with SMTP id VAA10184
	for <linux-arm-kernel@lists.arm.linux.org.uk>; Tue, 18 Jan 2000 21:23:38 GMT
Received: (qmail 15698 invoked by uid 0); 17 Jan 2000 01:32:36 -0000
Date: Mon, 17 Jan 2000 02:32:35 +0100 (MET)
From: Stefan Hanske <shanske@gmx.de>
To: linux-arm-kernel@lists.arm.linux.org.uk
MIME-Version: 1.0
Subject: Kernel compiling problems
X-Authenticated-Sender: #0003578408@gmx.net
X-Authenticated-IP: [141.53.8.5]
Message-ID: <15692.948072755@www3.gmx.net>
X-Mailer: WWW-Mail 1.5 (Global Message Exchange)
X-Flags: 0001
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
Sender: owner-linux-arm-kernel@lists.arm.linux.org.uk
Precedence: bulk

Hi there,

I've got problems compiling kernels - they compile fine and start up
correctly but when init starts, I get s segfault from init and a register
dump ála:
INIT: version 2.74 booting
INIT: PANIC: segmentation violation! giving up...
Unable to handle kernel paging request at virtual address c100052c
pgd=c04a8000
*pgd=00000000, *pmd=00000000
Internal error: Oops: 2
CPU: 0
pc: [<c0019254>]        lr: [<c000f7c4>]
sp:  c0479f98   ip:  bffff98c   fp:  00000000
r10: 0205b454   r9:  0205b430   r8:  bffff998
r7:  c0fffc3c   r6:  4d9abb30   r5:  000d0000   r4:  e92dd8f0
r3:  c0479fd4   r2:  00001d25   r1:  8f000000   r0:  c100052c
Flags: nZcv   IRQs off   FIQs on   Mode SVC_32   Segment user
Control: EE133F10   Table: EB003774   DAC: EA00000B
Process init (pid:1, stackpage=c0479000)
Stack:
c0479f80:                   c000f7c4 c0019254 40000093 ffffffff 00000002
bffff998
c0479fa0: 00000000 00000008 00000002 bffffa18 00000006 0205b428 bffff998
0205b430
c0479fc0: 0205b454 bffffc00 bffff98c c100052c 02001548 02004408 20000010
ffffffff
c0479fe0: C000d6f8 c01f2ccc c01e5a84 c01e5ad0 c0179fe4 c047a000 c0011444
c000d708
Backtrace: no frame pointer
code: 70253d70 0000000a (e5904000) e1a029a4 e2022002

However, I can boot into a shell via init=/bin/bash at the kernel command
line.
When I try to execute any program from there by entering it's path/name at
the
command line, nothing happens. I can type in characters, but I can't stop
the process (not even via SYSREQ-I or similar).
I've added some code to fork() and execve() that issue some printk()s at
different points. The result is that the shell fork()s successfully but
execve() isn't called.
Kernels tried: v2.3.19 and up (to 2.3.39-rmk1)
Binutils: 2.9.1.0.23 (patched with some redhat patches for arm) and
          2.9.5.0.22 (unpatched)
gcc: 2.95.2 with patch from ftp.netwinder.org/users/p/philb)
System: RiscPC with ARM710, various kernel configurations
Build method: native and cross-compiled

Has anyone some hints what might me wrong??? Has anybody running v2.3.xx-
kernels on RiscPC with non-SA processor???

Tia.

Stefan


-- 


Sent through Global Message Exchange - http://www.gmx.net


unsubscribe: body of `unsubscribe linux-arm-kernel' to majordomo@lists.arm.linux.org.uk

From owner-linux-arm-kernel@lists.arm.linux.org.uk  Wed Jan 19 14:21:35 2000
Received: (from majordomo@localhost)
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) id OAA17365
	for linux-arm-kernel-outgoing; Wed, 19 Jan 2000 14:21:35 GMT
Received: from salisbury.labs.futuretv.com (salisbury.futuretv.com [194.216.164.17])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id OAA17343
	for <linux-arm-kernel@lists.arm.linux.org.uk>; Wed, 19 Jan 2000 14:21:17 GMT
Received: from zebra.labs.futuretv.com ([192.0.0.67] ident=mail)
	by salisbury.labs.futuretv.com with esmtp (Exim 3.03 #1)
	id 12Aw0R-0002x1-00
	for linux-arm-kernel@lists.arm.linux.org.uk; Wed, 19 Jan 2000 14:22:43 +0000
Received: from [192.0.0.21] (helo=fountain.labs.futuretv.com ident=mail)
	by zebra.labs.futuretv.com with esmtp (Exim 3.03 #1)
	id 12Avz2-0002IW-00
	for linux-arm-kernel@lists.arm.linux.org.uk; Wed, 19 Jan 2000 14:21:16 +0000
Received: from [127.0.0.1] (helo=fountain ident=pb)
	by fountain.labs.futuretv.com with esmtp (Exim 3.03 #1)
	id 12Avz2-0001Al-00
	for linux-arm-kernel@lists.arm.linux.org.uk; Wed, 19 Jan 2000 14:21:16 +0000
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: linux-arm-kernel@lists.arm.linux.org.uk
Subject: llseek compatibility
From: Philip Blundell <pb@futuretv.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 19 Jan 2000 14:21:15 +0000
Message-Id: <E12Avz2-0001Al-00@fountain.labs.futuretv.com>
Sender: owner-linux-arm-kernel@lists.arm.linux.org.uk
Precedence: bulk

This code:

	if (old_calling_standard (regs)) {
		printk (KERN_NOTICE "%s (%d): unsupported llseek call standard\n",
			current->comm, current->pid);
		return -EINVAL;
	}

is causing problems when libc is compiled with particular versions of GCC.  
The `old_calling_standard' heuristic is spuriously firing and causing the call 
to fail.

As far as I know there are no extant binaries still using this old calling 
standard.  I would like to see the code removed from 2.2 kernels; it already 
seems to be gone in 2.3.

Does anybody have any objection to this?

p.



unsubscribe: body of `unsubscribe linux-arm-kernel' to majordomo@lists.arm.linux.org.uk

From owner-linux-arm-kernel@lists.arm.linux.org.uk  Tue Jan 25 23:46:30 2000
Received: (from majordomo@localhost)
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) id XAA22945
	for linux-arm-kernel-outgoing; Tue, 25 Jan 2000 23:46:30 GMT
Received: from caramon.arm.linux.org.uk (root@p01-magpie-gui.tch.enablis.net [194.168.180.1])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id XAA22941
	for <linux-arm-kernel@lists.arm.linux.org.uk>; Tue, 25 Jan 2000 23:46:26 GMT
Received: from raistlin.arm.linux.org.uk (root@raistlin [192.168.0.3])
	by caramon.arm.linux.org.uk (8.9.3/8.9.3) with ESMTP id XAA30366;
	Tue, 25 Jan 2000 23:46:15 GMT
From: Russell King - ARM Linux Admin <linux@arm.linux.org.uk>
Received: (from linux@localhost)
	by raistlin.arm.linux.org.uk (8.7.4/8.7.3) id XAA01099;
	Tue, 25 Jan 2000 23:44:24 GMT
Message-Id: <200001252344.XAA01099@raistlin.arm.linux.org.uk>
Subject: Movement of ARM stuff
To: linux-arm-kernel@lists.arm.linux.org.uk, linux-arm@vger.rutgers.edu
Date: Tue, 25 Jan 2000 23:44:24 +0000 (GMT)
X-Mailer: ELM [version 2.5 PL1]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm-kernel@lists.arm.linux.org.uk
Precedence: bulk

Hi,

This email is probably a little early, but never mind.  A reminder will
be sent out nearer to the time.

The machine currently known as 'zen.ics.uwe.ac.uk' will be gradually
phased out of use over the next few months as far as the ARM Linux
project is concerned.

This machine is responsible for handling the following names:

	ftp.arm.linux.org.uk
		ARM Linux FTP archive

	lists.arm.linux.org.uk
		ARM Linux mailing lists:
			linux-arm-kernel
			linux-arm-announce
			(linux-arm backup list)

If you are using any services relying on the name 'zen.ics.uwe.ac.uk'
relating to ARM Linux (eg, mirroring software, mailing software),
please update NOW to use one of the two addresses under the
arm.linux.org.uk.  Failure to do so will result in possible loss of
service.

I hope to perform the transition as smoothly as possible, and hopefully
no one will have any problems during this period.

The period when these services will move will be notified closer to the
time.
   _____
  |_____| ------------------------------------------------- ---+---+-
  |   |        Russell King       linux@arm.linux.org.uk      --- ---
  | | | |  http://www.arm.linux.org.uk/~rmk/armlinux.html    /  /  |
  | +-+-+                                                     --- -+-
  /   |               THE developer of ARM Linux              |+| /|\
 /  | | |                                                     ---  |
    +-+-+ -------------------------------------------------  /\\\  |

unsubscribe: body of `unsubscribe linux-arm-kernel' to majordomo@lists.arm.linux.org.uk

From owner-linux-arm-kernel@lists.arm.linux.org.uk  Sun Jan 30 10:13:38 2000
Received: (from majordomo@localhost)
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) id KAA08997
	for linux-arm-kernel-outgoing; Sun, 30 Jan 2000 10:13:38 GMT
Received: from web3401.mail.yahoo.com (web3401.mail.yahoo.com [204.71.203.55])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with SMTP id KAA08993
	for <linux-arm-kernel@lists.arm.linux.org.uk>; Sun, 30 Jan 2000 10:13:33 GMT
Message-ID: <20000130072729.29351.qmail@web3401.mail.yahoo.com>
Received: from [202.106.228.40] by web3401.mail.yahoo.com; Sun, 30 Jan 2000 15:27:29 CST
Date: Sun, 30 Jan 2000 15:27:29 +0800 (CST)
From: =?gb2312?q?yan=20fuxiang?= <yanfuxiang@yahoo.com.cn>
Subject: The fb device in /dev/fb
To: linux-arm-kernel@lists.arm.linux.org.uk
MIME-Version: 1.0
Content-Type: text/plain; charset=gb2312
Content-Transfer-Encoding: 8bit
Sender: owner-linux-arm-kernel@lists.arm.linux.org.uk
Precedence: bulk

I have built the frame buffer of SA1100 in arm linux
kernel.but I can not find the device in the
/dev/fb.Who can tell me why and who to make a device
of SA1100 frame buffer in the /dev/fb. 
__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com

unsubscribe: body of `unsubscribe linux-arm-kernel' to majordomo@lists.arm.linux.org.uk

From owner-linux-arm-kernel@lists.arm.linux.org.uk  Sun Jan 30 12:20:45 2000
Received: (from majordomo@localhost)
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) id MAA14063
	for linux-arm-kernel-outgoing; Sun, 30 Jan 2000 12:20:45 GMT
Received: from caramon.arm.linux.org.uk (root@dyn-225.linux.theplanet.co.uk [195.92.192.225])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id MAA14059
	for <linux-arm-kernel@lists.arm.linux.org.uk>; Sun, 30 Jan 2000 12:20:41 GMT
Received: from flint.arm.linux.org.uk (root@flint [195.92.192.228])
	by caramon.arm.linux.org.uk (8.9.3/8.9.3) with ESMTP id KAA03281;
	Sun, 30 Jan 2000 10:17:31 GMT
Received: (from linux@localhost)
	by flint.arm.linux.org.uk (8.9.3/8.9.3) id KAA02632;
	Sun, 30 Jan 2000 10:15:17 GMT
From: Russell King - ARM Linux Admin <linux@arm.linux.org.uk>
Message-Id: <200001301015.KAA02632@flint.arm.linux.org.uk>
Subject: Re: The fb device in /dev/fb
To: yanfuxiang@yahoo.com.cn (yan fuxiang)
Date: Sun, 30 Jan 2000 10:15:17 +0000 (GMT)
Cc: linux-arm-kernel@lists.arm.linux.org.uk
In-Reply-To: <20000130072729.29351.qmail@web3401.mail.yahoo.com> from "yan fuxiang" at Jan 30, 2000 03:27:29 PM
X-Mailer: ELM [version 2.5 PL1]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm-kernel@lists.arm.linux.org.uk
Precedence: bulk

yan fuxiang writes:
> I have built the frame buffer of SA1100 in arm linux
> kernel.but I can not find the device in the
> /dev/fb.Who can tell me why and who to make a device
> of SA1100 frame buffer in the /dev/fb. 

mknod -m 600 /dev/fb0 c 29 0
ln -s fb0 /dev/fb
   _____
  |_____| ------------------------------------------------- ---+---+-
  |   |        Russell King       linux@arm.linux.org.uk      --- ---
  | | | |  http://www.arm.linux.org.uk/~rmk/armlinux.html    /  /  |
  | +-+-+                                                     --- -+-
  /   |               THE developer of ARM Linux              |+| /|\
 /  | | |                                                     ---  |
    +-+-+ -------------------------------------------------  /\\\  |

unsubscribe: body of `unsubscribe linux-arm-kernel' to majordomo@lists.arm.linux.org.uk

From owner-linux-arm-kernel@lists.arm.linux.org.uk  Mon Jan 31 01:46:45 2000
Received: (from majordomo@localhost)
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) id BAA22741
	for linux-arm-kernel-outgoing; Mon, 31 Jan 2000 01:46:45 GMT
Received: from earth.light.com (c657338-a.plstn1.sfba.home.com [24.1.83.42])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id BAA22735
	for <linux-arm-kernel@lists.arm.linux.org.uk>; Mon, 31 Jan 2000 01:46:41 GMT
Received: from localhost (rscott@localhost)
	by earth.light.com (8.9.3/8.8.7) with ESMTP id RAA20133
	for <linux-arm-kernel@lists.arm.linux.org.uk>; Sun, 30 Jan 2000 17:46:35 -0800
X-Authentication-Warning: earth.light.com: rscott owned process doing -bs
Date: Sun, 30 Jan 2000 17:46:35 -0800 (PST)
From: Rob Scott <rscott@mtrob.fdns.net>
To: linux-arm-kernel@lists.arm.linux.org.uk
Subject: New ARM implementation HOWTO?
Message-ID: <Pine.LNX.4.10.10001301535120.19900-100000@earth.light.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm-kernel@lists.arm.linux.org.uk
Precedence: bulk


If there is an ARM implementation porting HOWTO, please point me to it.
I'm sure the following questions would be in it!

1) How do I get a new implementation value? I saw a reference to an
automated system somewhere, but I can't find it again.

2) How do I specify a ARM720T core based processor? Currently, I've
changed the config.in to select CONFIG_CPU_32v4 and CONFIG_CPU_ARM7.

3) What's the preferred frequency of patch submissions? Wait until it
works, i.e. one huge lump, or lots of little bits?

4) Any other advice for a new ARM arch port developer? I know I have to do
stuff in the interrupt handler, and maybe some mmu stuff...

Backround: I'm porting linux to a Linkup Systems L7200 SBC. I've ported my
ColdFire linux booter to ARM, and have built a new toolchain. Previously,
I got uClinux-ColdFire working on a Motorola eLITE developement board, put
DMA support into uClinux-ColdFire, wrote DMA driven LCD drivers, and
ported an MP3 player to it. (See http://www.moretonbay/coldfire/nettelmp3.html
for details). I'd like to get the same setup working on ARM...

Thanks for any help!

Rob Scott




unsubscribe: body of `unsubscribe linux-arm-kernel' to majordomo@lists.arm.linux.org.uk

From owner-linux-arm-kernel@lists.arm.linux.org.uk  Mon Jan 31 21:30:24 2000
Received: (from majordomo@localhost)
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) id VAA12789
	for linux-arm-kernel-outgoing; Mon, 31 Jan 2000 21:30:24 GMT
Received: from mail.uni-greifswald.de (mail.uni-greifswald.de [141.53.8.33])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id VAA12785
	for <linux-arm-kernel@lists.arm.linux.org.uk>; Mon, 31 Jan 2000 21:30:21 GMT
Received: from localhost (sh990154@localhost)
	by mail.uni-greifswald.de (8.9.2/8.9.2) with SMTP id WAA27803
	for <linux-arm-kernel@lists.arm.linux.org.uk>; Mon, 31 Jan 2000 22:30:20 +0100 (MET)
Date: Mon, 31 Jan 2000 22:30:19 +0100 (MET)
From: "Hanske;Stefan" <sh990154@mail.uni-greifswald.de>
To: linux-arm-kernel@lists.arm.linux.org.uk
Subject: v2.3 kernels on RPC w/ ARM710
Message-ID: <Pine.GHP.4.02.10001312223080.27633-100000@mail.uni-greifswald.de>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm-kernel@lists.arm.linux.org.uk
Precedence: bulk


Hi there,

I've found that the problems with v2.3.xx kernels are more generic than I
thought. I've tried all v2.3.xx kernels from ftp.armlinux.org/pub/lkab -
it's still the same as with my home built kernels.
The kernels are initializing fine, but when init has been started, it is
terminated with a SIGSEGV and the kernel dies with a register dump.

Could someone with a RiscPC and ARM[67]10 processor please verify this
problem?
Could the new mm code perhaps be responsible for this behaviour?


TIA.



unsubscribe: body of `unsubscribe linux-arm-kernel' to majordomo@lists.arm.linux.org.uk

From owner-linux-arm-kernel@lists.arm.linux.org.uk  Mon Jan 31 22:33:13 2000
Received: (from majordomo@localhost)
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) id WAA16772
	for linux-arm-kernel-outgoing; Mon, 31 Jan 2000 22:33:13 GMT
Received: from caramon.arm.linux.org.uk (root@dyn-225.linux.theplanet.co.uk [195.92.192.225])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id WAA16766
	for <linux-arm-kernel@lists.arm.linux.org.uk>; Mon, 31 Jan 2000 22:33:08 GMT
Received: from flint.arm.linux.org.uk (root@flint [195.92.192.228])
	by caramon.arm.linux.org.uk (8.9.3/8.9.3) with ESMTP id WAA10506;
	Mon, 31 Jan 2000 22:32:34 GMT
Received: (from linux@localhost)
	by flint.arm.linux.org.uk (8.9.3/8.9.3) id WAA18945;
	Mon, 31 Jan 2000 22:30:11 GMT
From: Russell King - ARM Linux Admin <linux@arm.linux.org.uk>
Message-Id: <200001312230.WAA18945@flint.arm.linux.org.uk>
Subject: Re: v2.3 kernels on RPC w/ ARM710
To: sh990154@mail.uni-greifswald.de (Hanske;Stefan)
Date: Mon, 31 Jan 2000 22:30:10 +0000 (GMT)
Cc: linux-arm-kernel@lists.arm.linux.org.uk
In-Reply-To: <Pine.GHP.4.02.10001312223080.27633-100000@mail.uni-greifswald.de> from "Hanske;Stefan" at Jan 31, 2000 10:30:19 PM
X-Mailer: ELM [version 2.5 PL1]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm-kernel@lists.arm.linux.org.uk
Precedence: bulk

Hanske;Stefan writes:
> I've found that the problems with v2.3.xx kernels are more generic than I
> thought. I've tried all v2.3.xx kernels from ftp.armlinux.org/pub/lkab -
> it's still the same as with my home built kernels.
> The kernels are initializing fine, but when init has been started, it is
> terminated with a SIGSEGV and the kernel dies with a register dump.

Can you forward the register dump please?
   _____
  |_____| ------------------------------------------------- ---+---+-
  |   |        Russell King       linux@arm.linux.org.uk      --- ---
  | | | |  http://www.arm.linux.org.uk/~rmk/armlinux.html    /  /  |
  | +-+-+                                                     --- -+-
  /   |               THE developer of ARM Linux              |+| /|\
 /  | | |                                                     ---  |
    +-+-+ -------------------------------------------------  /\\\  |

unsubscribe: body of `unsubscribe linux-arm-kernel' to majordomo@lists.arm.linux.org.uk

