From owner-linux-arm-outgoing@vger.rutgers.edu  Fri Oct  1 07:48:26 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id HAA23929
	for <linux-arm-archive@lists.arm.linux.org.uk>; Fri, 1 Oct 1999 07:48:26 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id D322213DEA; Fri,  1 Oct 1999 08:47:42 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156733AbPI3W1o>;
	Thu, 30 Sep 1999 18:27:44 -0400
Received: by vger.rutgers.edu id <S156654AbPI3W1h>;
	Thu, 30 Sep 1999 18:27:37 -0400
Received: from tazenda.demon.co.uk ([158.152.220.239]:1120 "EHLO
        kings-cross.london.uk.eu.org") by vger.rutgers.edu with ESMTP
	id <S156790AbPI3W0T>; Thu, 30 Sep 1999 18:26:19 -0400
Received: from localhost
	([127.0.0.1] helo=kings-cross.london.uk.eu.org ident=phil)
	by kings-cross.london.uk.eu.org with esmtp (Exim 2.05 #1)
	id 11WoaG-0000Mj-00; Thu, 30 Sep 1999 23:21:52 +0100
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: mestery@visi.com
Cc: linux-arm@vger.rutgers.edu
Subject: Re: jre for Linux/ARM 
In-Reply-To: Message from <mestery@visi.com> 
   of "Thu, 30 Sep 1999 14:17:19 CDT." <Pine.GSO.4.10.9909301414250.14173-100000@isis.visi.com> 
References: <Pine.GSO.4.10.9909301414250.14173-100000@isis.visi.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date:   Thu, 30 Sep 1999 23:21:52 +0100
From: Philip Blundell <Philip.Blundell@pobox.com>
Message-Id: <E11WoaG-0000Mj-00@kings-cross.london.uk.eu.org>
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

>/root/java/jdk118_v1/bin/jre: /root/java/jdk118_v1/bin/../bin/armv4l/green_thr
>eads/jre: No such file or directory

That sort of problem can be caused by a bad dynamic linker path.  Some older 
Corel-derived binaries look for /usr/lib/ld.so.1.  You can usually detect this 
by using `strings' on the executable.

p.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Fri Oct  1 07:53:07 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id HAA24081
	for <linux-arm-archive@lists.arm.linux.org.uk>; Fri, 1 Oct 1999 07:53:07 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 93F9613F4E; Fri,  1 Oct 1999 08:49:05 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156740AbPI3WkS>;
	Thu, 30 Sep 1999 18:40:18 -0400
Received: by vger.rutgers.edu id <S156838AbPI3Whd>;
	Thu, 30 Sep 1999 18:37:33 -0400
Received: from tazenda.demon.co.uk ([158.152.220.239]:1138 "EHLO
        kings-cross.london.uk.eu.org") by vger.rutgers.edu with ESMTP
	id <S156822AbPI3Wdc>; Thu, 30 Sep 1999 18:33:32 -0400
Received: from localhost
	([127.0.0.1] helo=kings-cross.london.uk.eu.org ident=phil)
	by kings-cross.london.uk.eu.org with esmtp (Exim 2.05 #1)
	id 11WolP-0000Oa-00; Thu, 30 Sep 1999 23:33:23 +0100
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: "Dave Borja" <dave_bb@pacbell.net>
Cc: "linux-arm" <linux-arm@vger.rutgers.edu>
Subject: Re: ramdisk.gz and downloadiing the kernel (newbie question) 
In-Reply-To: Message from "Dave Borja" <dave_bb@pacbell.net> 
   of "Thu, 30 Sep 1999 12:54:09 PDT." <081a01bf0b7d$900a60c0$529765d8@java> 
References: <081a01bf0b7d$900a60c0$529765d8@java> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date:   Thu, 30 Sep 1999 23:33:23 +0100
From: Philip Blundell <Philip.Blundell@pobox.com>
Message-Id: <E11WolP-0000Oa-00@kings-cross.london.uk.eu.org>
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

>Once I get my application built and an arm kernal image
>(iZimage) I'm not quite clear on the process for downloading
>to the brutus. The intel documentation on their web site 
>calls for creating a ramdisk.gz file containing the the
>application and c library (?). But not the kernel? I thought
>this ramdisk would be the boot device?

The ramdisk doesn't contain the kernel; the two are downloaded separately.  
Yes, the ramdisk is the boot/initial root device.

>built angelboot from the code in angelboot.tgz. Apparently angelboot
>needs to be pointed at a zImage and it will communicate with the
>ANGEL monitor on the brutus to download both the kernel image
>and the ramdisk. I'm not sure what happens after that.

That's right.  Both the kernel and the ramdisk image are downloaded to 
particular addresses in RAM, and then control just passes to the kernel.  It 
uncompresses itself, locates the RAM disk image and away you go.

p.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Fri Oct  1 07:55:24 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id HAA24219
	for <linux-arm-archive@lists.arm.linux.org.uk>; Fri, 1 Oct 1999 07:55:23 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 0169F14042; Fri,  1 Oct 1999 08:54:58 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156911AbPI3XLL>;
	Thu, 30 Sep 1999 19:11:11 -0400
Received: by vger.rutgers.edu id <S156825AbPI3XK5>;
	Thu, 30 Sep 1999 19:10:57 -0400
Received: from kauket.visi.com ([209.98.98.22]:54856 "HELO mail-out.visi.com")
	by vger.rutgers.edu with SMTP id <S156919AbPI3XKS>;
	Thu, 30 Sep 1999 19:10:18 -0400
Received: from isis.visi.com (isis.visi.com [209.98.98.8])
	by mail-out.visi.com (Postfix) with ESMTP
	id C1D2837CB; Thu, 30 Sep 1999 18:10:13 -0500 (CDT)
Received: from localhost (mestery@localhost)
	by isis.visi.com (8.8.8/8.8.8) with ESMTP id SAA29883;
	Thu, 30 Sep 1999 18:10:13 -0500 (CDT)
X-Authentication-Warning: isis.visi.com: mestery owned process doing -bs
Date:   Thu, 30 Sep 1999 18:10:13 -0500 (CDT)
From: <mestery@visi.com>
To: Philip Blundell <Philip.Blundell@pobox.com>
Cc: linux-arm@vger.rutgers.edu
Subject: Re: jre for Linux/ARM 
In-Reply-To: <E11WoaG-0000Mj-00@kings-cross.london.uk.eu.org>
Message-ID: <Pine.GSO.4.10.9909301809190.29823-100000@isis.visi.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Hi,

On Thu, 30 Sep 1999, Philip Blundell wrote:

> >/root/java/jdk118_v1/bin/jre: /root/java/jdk118_v1/bin/../bin/armv4l/green_thr
> >eads/jre: No such file or directory
> 
> That sort of problem can be caused by a bad dynamic linker path.  Some older 
> Corel-derived binaries look for /usr/lib/ld.so.1.  You can usually detect this
> by using `strings' on the executable.
> 
That was the problem.  I linked /lib/libc-2.1.so to /usr/lib/ld.so.1 and
things seem better now.  Now I'm getting an undefined symbol, which I'm
tracking down now.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Fri Oct  1 07:58:44 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id HAA24257
	for <linux-arm-archive@lists.arm.linux.org.uk>; Fri, 1 Oct 1999 07:58:44 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 71E1414146; Fri,  1 Oct 1999 08:58:10 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156728AbPI3WbP>;
	Thu, 30 Sep 1999 18:31:15 -0400
Received: by vger.rutgers.edu id <S156585AbPI3WbI>;
	Thu, 30 Sep 1999 18:31:08 -0400
Received: from tazenda.demon.co.uk ([158.152.220.239]:1134 "EHLO
        kings-cross.london.uk.eu.org") by vger.rutgers.edu with ESMTP
	id <S156728AbPI3Waz>; Thu, 30 Sep 1999 18:30:55 -0400
Received: from localhost
	([127.0.0.1] helo=kings-cross.london.uk.eu.org ident=phil)
	by kings-cross.london.uk.eu.org with esmtp (Exim 2.05 #1)
	id 11Woig-0000OK-00; Thu, 30 Sep 1999 23:30:34 +0100
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: "Dave Borja" <dave_bb@pacbell.net>
Cc: "linux-arm" <linux-arm@vger.rutgers.edu>
Subject: Re: linux-arm-gcc won't find the *.h files 
In-Reply-To: Message from "Dave Borja" <dave_bb@pacbell.net> 
   of "Thu, 30 Sep 1999 11:56:23 PDT." <07f801bf0b75$7da0c2b0$529765d8@java> 
References: <07f801bf0b75$7da0c2b0$529765d8@java> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date:   Thu, 30 Sep 1999 23:30:34 +0100
From: Philip Blundell <Philip.Blundell@pobox.com>
Message-Id: <E11Woig-0000OK-00@kings-cross.london.uk.eu.org>
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

>#include "..." search starts here:
>#include <...> search starts here:
> /usr/local/arm/lib/gcc-lib/arm-linux/egcs-2.91.60/include
> /usr/local/arm/arm-linux/include
>End of search list.
>hello.c:1: stdio.h: No such file or directory
>
>It seems to be looking in the wrong place for the .h files as well as other
>things. They are there, but just not in the dirs it looks for.

What directory are they in, in fact?  That search path looks pretty much right 
to me.

>3) Built GLIBC library

You didn't mention what `configure' command you used for this.  I suspect the 
problem may lie in the --prefix argument you used.

p.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Fri Oct  1 07:59:17 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id HAA24267
	for <linux-arm-archive@lists.arm.linux.org.uk>; Fri, 1 Oct 1999 07:59:17 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 721F31414C; Fri,  1 Oct 1999 08:58:20 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156927AbPI3XcF>;
	Thu, 30 Sep 1999 19:32:05 -0400
Received: by vger.rutgers.edu id <S156878AbPI3Xbl>;
	Thu, 30 Sep 1999 19:31:41 -0400
Received: from [208.193.202.3] ([208.193.202.3]:42912 "HELO
        fw-losgatos.losgatos.arm.com") by vger.rutgers.edu with SMTP
	id <S156905AbPI3XbO>; Thu, 30 Sep 1999 19:31:14 -0400
Received: by fw-losgatos.losgatos.arm.com; id QAA08441; Thu, 30 Sep 1999 16:28:03 -0700
Received: from dhcp47.losgatos.arm.com(194.202.50.238) by fw-losgatos.losgatos.arm.com via smap (4.1)
	id xma008426; Thu, 30 Sep 99 16:27:18 -0700
Message-ID: <37F3D5BE.BD308FD5@pobox.com>
Date:   Thu, 30 Sep 1999 16:27:26 -0500
From: Ian Field <ianfield@pobox.com>
X-Mailer: Mozilla 4.51 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
Cc: linux-arm <linux-arm@vger.rutgers.edu>
Subject: Re: ramdisk.gz and downloadiing the kernel (newbie question)
References: <081a01bf0b7d$900a60c0$529765d8@java>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: unlisted-recipients: ; (no To-header on input)
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Hi Dave,

> Once I get my application built and an arm kernal image
> (iZimage) I'm not quite clear on the process for downloading
> to the brutus. The intel documentation on their web site
> calls for creating a ramdisk.gz file containing the the
> application and c library (?). But not the kernel? I thought
> this ramdisk would be the boot device? In any case, there
> is supposedly a prepared ramdisk with the libraries at
>
> ftp://ssdl-redstone.stanford.edu/pub/ramdisk.gz

When I get home, I can email you this file. It would be a real pain to
reproduce all the stuff in this image.

Check out the following sites for more info on ramdisks ::
 http://developer.intel.com/design/strong/applnots/sa1100lx/download.htm#1001846

 http://www.linuxhq.com/doc20/ramdisk.txt

-------------------------------------------------
The intel site is pretty good as an introduction to tools and arm-linux.

http://developer.intel.com/design/strong/applnots/sa1100lx/sa1100lx.htm
http://developer.intel.com/design/strong/applnots/sa1100lx/download.htm
base 0x8000
entry 0xc0008000
device /dev/ttyS0
options "9600 8N1"
baud 115200
otherfile ramdisk.gz
otherbase 0x800000
-------------------------------------------------

Using my bootloader on a custom board, I just put the kernel at 0xC0008000 and
the ramdisk at 0xC0800000.


Cheers, IAN



unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Fri Oct  1 08:46:22 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id IAA25802
	for <linux-arm-archive@lists.arm.linux.org.uk>; Fri, 1 Oct 1999 08:46:22 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 683B113DC2; Fri,  1 Oct 1999 09:46:20 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156641AbPJAHpj>;
	Fri, 1 Oct 1999 03:45:39 -0400
Received: by vger.rutgers.edu id <S156585AbPJAHpd>;
	Fri, 1 Oct 1999 03:45:33 -0400
Received: from adsl-216-100-248-143.dsl.snfc21.pacbell.net ([216.100.248.143]:25248
        "EHLO adsl-216-100-248-143.dsl.snfc21.pacbell.net")
	by vger.rutgers.edu with ESMTP id <S156587AbPJAHpK>;
	Fri, 1 Oct 1999 03:45:10 -0400
Received: from biff (biff [192.168.1.4])
	by adsl-216-100-248-143.dsl.snfc21.pacbell.net (8.8.7/8.8.7) with SMTP id AAA15077
	for <linux-arm@vger.rutgers.edu>; Fri, 1 Oct 1999 00:40:25 -0700
Message-ID: <003101bf0be0$d59a43e0$0401a8c0@casagrande.way>
From: "Ian Field" <ianfield@pobox.com>
To: "linux-arm" <linux-arm@vger.rutgers.edu>
References: <081a01bf0b7d$900a60c0$529765d8@java>  <E11WolP-0000Oa-00@kings-cross.london.uk.eu.org>
Subject: Re: ramdisk.gz
Date:   Fri, 1 Oct 1999 00:44:46 -0700
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 5.00.2014.211
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

> The ramdisk doesn't contain the kernel; the two are downloaded separately.
> Yes, the ramdisk is the boot/initial root device.

On the SA1100 or in general, has anybody else found problems with compressed
ramdisks. I find an uncompressed ext2 image works fine, but when I gzip it,
it fails alot of the time ...



unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Fri Oct  1 12:31:12 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id MAA11995
	for <linux-arm-archive@lists.arm.linux.org.uk>; Fri, 1 Oct 1999 12:31:12 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 1280813DBB; Fri,  1 Oct 1999 13:31:11 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156632AbPJALbB>;
	Fri, 1 Oct 1999 07:31:01 -0400
Received: by vger.rutgers.edu id <S156587AbPJALap>;
	Fri, 1 Oct 1999 07:30:45 -0400
Received: from note.orchestra.cse.unsw.EDU.AU ([129.94.242.29]:3940 "HELO
        note.orchestra.cse.unsw.EDU.AU") by vger.rutgers.edu with SMTP
	id <S156641AbPJALad>; Fri, 1 Oct 1999 07:30:33 -0400
Received: From paulaner With LocalMail ; Fri, 1 Oct 99 21:29:54 +1000 
From: "Adam 'WeirdArms' Wiggins" <awiggins@cse.unsw.EDU.AU>
To: linux-arm@vger.rutgers.edu
Date:   Fri, 1 Oct 1999 21:29:44 +1000 (EST)
X-Sender: awiggins@paulaner.disy.cse.unsw.EDU.AU
Subject: (Off-topic) Real-Time kernels on ARM
Message-ID: <Pine.OSF.3.95.991001212534.25259A-100000@paulaner.disy.cse.unsw.EDU.AU>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

	I'm after any references or design information for real time
kernels on top of the ARM. What I'm after is how to design fast re-entrant
exception handlers given the sometimes painful register banking of ARM.
Conversly if real time kernels on arm handle register banking via
non-reentrant handlers please let me know. Any pointers appreciated.

	BTW are ARM linux exception handlers re-entrant? How preemptable
is ARM linux?

	Cheers Adam

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Fri Oct  1 16:28:53 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id QAA28992
	for <linux-arm-archive@lists.arm.linux.org.uk>; Fri, 1 Oct 1999 16:28:52 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id B1DA113E68; Fri,  1 Oct 1999 17:28:51 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156669AbPJAP2X>;
	Fri, 1 Oct 1999 11:28:23 -0400
Received: by vger.rutgers.edu id <S156652AbPJAP2P>;
	Fri, 1 Oct 1999 11:28:15 -0400
Received: from sparkle.Generation.NET ([205.205.119.4]:41515 "EHLO
        sparkle.Generation.NET") by vger.rutgers.edu with ESMTP
	id <S156703AbPJAP04>; Fri, 1 Oct 1999 11:26:56 -0400
Received: from dual (generic253.197.205.205.IN-ADDR.ARPA [205.205.197.253] (may be forged))
	by sparkle.Generation.NET (8.9.3/8.9.3) with SMTP id LAA08578
	for <linux-arm@vger.rutgers.edu>; Fri, 1 Oct 1999 11:27:07 -0400 (EDT)
From: Francois Desloges <fd@vipswitch.com>
To: linux-arm@vger.rutgers.edu
Subject: gcc-2.95.1 message
Date:   Fri, 1 Oct 1999 11:13:39 -0400
Content-Type: text/plain
MIME-Version: 1.0
Message-Id: <99100111253801.14871@dual>
Content-Transfer-Encoding: 8bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Just a little question.

When buliding  gcc-2.95.1 with
# make LANGUAGES="c"
There is that message, after linking everything, shown just before completion,
that reads:
>thr-vxworks.c           ..linked
>thr-win32.c             ..linked
>thr.c           ..linked
>creating cache ./config.cache
>checking if compiler cc1obj has been built... no
>rmdir: libobjc: Directory not empty

What is that cc1obj compiler?
Do I need it?

Thanks in advance for the answer,

--
François Desloges
fd@vipswitch.com
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Fri Oct  1 16:57:14 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id QAA30107
	for <linux-arm-archive@lists.arm.linux.org.uk>; Fri, 1 Oct 1999 16:57:13 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 68DFC13E71; Fri,  1 Oct 1999 17:57:11 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156669AbPJAP4D>;
	Fri, 1 Oct 1999 11:56:03 -0400
Received: by vger.rutgers.edu id <S156666AbPJAPzq>;
	Fri, 1 Oct 1999 11:55:46 -0400
Received: from ns-inetext.inet.com ([199.171.211.140]:34991 "EHLO
        ns-inetext.inet.com") by vger.rutgers.edu with ESMTP
	id <S156732AbPJAPzV>; Fri, 1 Oct 1999 11:55:21 -0400
Received: from harpo.inetint.com (harpo [172.16.99.60])
	by ns-inetext.inet.com (8.9.2/8.9.2) with ESMTP id KAA25585
	for <linux-arm@vger.rutgers.edu>; Fri, 1 Oct 1999 10:53:25 -0500 (CDT)
Received: from inet.com ([172.16.13.73]) by harpo.inetint.com
          (Netscape Messaging Server 3.6)  with ESMTP id AAA2938
          for <linux-arm@vger.rutgers.edu>; Fri, 1 Oct 1999 10:54:25 -0500
Message-ID: <37F4D914.14CB103@inet.com>
Date:   Fri, 01 Oct 1999 10:53:56 -0500
From: Dave Baukus <dave.baukus@inet.com>
Organization: Inet Technologies Inc.
X-Mailer: Mozilla 4.5 [en] (X11; U; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: linux-arm@vger.rutgers.edu
Subject: ebsa like board
References: <99100111253801.14871@dual>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

I have an a board w/ SA110/21285 that I was hoping would behave
much like the ebsa. It has 128M sdram and I'm attempting
to get 2.2.10-mk2 to boot on the thing. 

I boot all the way up into pcibios_init(); at this point
I look at the PCI memory address range (0xe0000000virt).
I expect to see all 0xF's because no devices are mapped
in yet, but unfortunately I see 64k of garbage.

Any suggestions as to where to start looking ? Unfortunately,
a different in-house OS does not exhibit this 64k of garbage.

Was there at one time a problem w/ ebsa and large memory ?

thanks for your help.

--
dave.baukus@inet.com			
	Inet Technologies Inc.
	Plano, Texas, USA.
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Fri Oct  1 17:19:30 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id RAA30696
	for <linux-arm-archive@lists.arm.linux.org.uk>; Fri, 1 Oct 1999 17:19:29 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 55B0413E08; Fri,  1 Oct 1999 18:19:22 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156666AbPJAQTA>;
	Fri, 1 Oct 1999 12:19:00 -0400
Received: by vger.rutgers.edu id <S156658AbPJAQSs>;
	Fri, 1 Oct 1999 12:18:48 -0400
Received: from nexus.carleton.ca ([134.117.76.10]:4033 "EHLO nexus.carleton.ca")
	by vger.rutgers.edu with ESMTP id <S156688AbPJAQSI>;
	Fri, 1 Oct 1999 12:18:08 -0400
Received: from localhost (stewart@localhost)
	by nexus.carleton.ca (8.9.3/8.9.3) with ESMTP id LAA10231;
	Fri, 1 Oct 1999 11:37:13 -0400
Date:   Fri, 1 Oct 1999 11:37:13 -0400 (EDT)
From: Rod Stewart <stewart@nexus.carleton.ca>
To: Francois Desloges <fd@vipswitch.com>
Cc: linux-arm@vger.rutgers.edu
Subject: Re: gcc-2.95.1 message
In-Reply-To: <99100111253801.14871@dual>
Message-ID: <Pine.LNX.4.10.9910011135130.10206-100000@nexus.carleton.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing


On Fri, 1 Oct 1999, Francois Desloges wrote:

> Just a little question.
> 
> When buliding  gcc-2.95.1 with
[...]
> >checking if compiler cc1obj has been built... no
> >rmdir: libobjc: Directory not empty
> 
> What is that cc1obj compiler?
> Do I need it?

It is part of the Objective C package.  You do not need it, unless you
want to use Objective C.  But then the Objective C backend is not all that
reliable under ARM...

-Rms

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Fri Oct  1 17:45:35 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id RAA31841
	for <linux-arm-archive@lists.arm.linux.org.uk>; Fri, 1 Oct 1999 17:45:34 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 868F413DEF; Fri,  1 Oct 1999 18:45:33 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156687AbPJAQpD>;
	Fri, 1 Oct 1999 12:45:03 -0400
Received: by vger.rutgers.edu id <S156625AbPJAQn5>;
	Fri, 1 Oct 1999 12:43:57 -0400
Received: from nexusel.demon.co.uk ([158.152.30.195]:16182 "EHLO
        globe.nexus.co.uk") by vger.rutgers.edu with ESMTP
	id <S156692AbPJAQkm>; Fri, 1 Oct 1999 12:40:42 -0400
Received: from [192.0.0.21] (helo=fountain.nexus.co.uk ident=mail)
	by globe.nexus.co.uk with smtp (Exim 2.12 #1)
	id 11X5Rs-0006Gq-00; Fri, 1 Oct 1999 17:22:20 +0100
Received: from [127.0.0.1] (helo=fountain ident=pb)
	by fountain.nexus.co.uk with esmtp (Exim 3.03 #1)
	id 11X5Rr-0001Tk-00; Fri, 01 Oct 1999 17:22:19 +0100
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: Francois Desloges <fd@vipswitch.com>
Cc: linux-arm@vger.rutgers.edu
Subject: Re: gcc-2.95.1 message 
In-Reply-To: Message from Francois Desloges <fd@vipswitch.com> 
   of "Fri, 01 Oct 1999 11:13:39 EDT." <99100111253801.14871@dual> 
References: <99100111253801.14871@dual> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date:   Fri, 01 Oct 1999 17:22:19 +0100
From: Philip Blundell <pb@nexus.co.uk>
Message-Id: <E11X5Rr-0001Tk-00@fountain.nexus.co.uk>
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

>>checking if compiler cc1obj has been built... no
>>rmdir: libobjc: Directory not empty
>
>What is that cc1obj compiler?
>Do I need it?

Objective C and no.

p.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Fri Oct  1 18:23:36 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id SAA01391
	for <linux-arm-archive@lists.arm.linux.org.uk>; Fri, 1 Oct 1999 18:23:36 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id A645713DF4; Fri,  1 Oct 1999 19:23:34 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156652AbPJARXB>;
	Fri, 1 Oct 1999 13:23:01 -0400
Received: by vger.rutgers.edu id <S156658AbPJARWe>;
	Fri, 1 Oct 1999 13:22:34 -0400
Received: from mail-gw6.pacbell.net ([206.13.28.41]:55775 "EHLO
        mail-gw6.pacbell.net") by vger.rutgers.edu with ESMTP
	id <S156652AbPJARWL>; Fri, 1 Oct 1999 13:22:11 -0400
Received: from java (adsl-216-101-151-82.dsl.snfc21.pacbell.net [216.101.151.82])
	by mail-gw6.pacbell.net (8.9.3/8.9.3) with SMTP id KAA08439
	for <linux-arm@vger.rutgers.edu.>; Fri, 1 Oct 1999 10:22:05 -0700 (PDT)
Message-ID: <088c01bf0c32$cf277170$529765d8@java>
From: "Dave Borja" <dave_bb@pacbell.net>
To: "linux-arm" <linux-arm@vger.rutgers.edu>
Subject: Re: ramdisk.gz and downloadiing the kernel (newbie question)
Date:   Fri, 1 Oct 1999 10:31:34 -0700
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.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

hmmm, thanks. The node seems to not be running an ftp
daemon. Anyone know what's going on?

Thanks,
 Dave
-----Original Message-----
From: Ian Field <ianfield@pobox.com>
To: Dave Borja <dave_bb@pacbell.net>
Date: Friday, October 01, 1999 8:59 AM
Subject: Re: ramdisk.gz and downloadiing the kernel (newbie question)


>Try,
>
>ftp://staticip.cx/pub/
>
>This is the ramdisk image that you would normally download from the page
the
>intel site refers to. Enjoy.
>
>Cheers, IAN
>
>
>

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Fri Oct  1 19:12:08 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id TAA04013
	for <linux-arm-archive@lists.arm.linux.org.uk>; Fri, 1 Oct 1999 19:12:08 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 84AED13E19; Fri,  1 Oct 1999 20:12:07 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156857AbPJASLh>;
	Fri, 1 Oct 1999 14:11:37 -0400
Received: by vger.rutgers.edu id <S156723AbPJASL2>;
	Fri, 1 Oct 1999 14:11:28 -0400
Received: from sparkle.Generation.NET ([205.205.119.4]:49084 "EHLO
        sparkle.Generation.NET") by vger.rutgers.edu with ESMTP
	id <S156855AbPJASIy>; Fri, 1 Oct 1999 14:08:54 -0400
Received: from dual (generic253.197.205.205.IN-ADDR.ARPA [205.205.197.253] (may be forged))
	by sparkle.Generation.NET (8.9.3/8.9.3) with SMTP id OAA27579
	for <linux-arm@vger.rutgers.edu>; Fri, 1 Oct 1999 14:09:01 -0400 (EDT)
From: Francois Desloges <fd@vipswitch.com>
To: linux-arm@vger.rutgers.edu
Subject: Gcc-Error & Thread Safe Library
Date:   Fri, 1 Oct 1999 13:33:58 -0400
Content-Type: text/plain
MIME-Version: 1.0
Message-Id: <99100114073202.14871@dual>
Content-Transfer-Encoding: 8bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Remember the 
>./libgcc2.c:41: stdlib.h: No such file or directory 
error when building gcc-2.95.1?

The solution was to:
------- 
Edit gcc/config/arm/t-linux and add "-Dinhibit_libc" and
"-D__gthr_posix_h" to TARGET_LIBGCC2_CFLAGS
Delete #include "gthr.h" in libgcc2.c
Add the "--disable-threads" option to configure
-------

However these consequences worried me:
>>1) What effect will the "inhibit_libc", "__gthr_posix_h", and
>>"--disable-threads" options have on my compiler?
>
>The generated libraries will not be thread safe.  This will bite you if, for 
>example, you have a multithreaded C++ program that uses exceptions.

So as I need a fully functionnal toolchain, I asked:
>>Or what about building gcc with "inhibit_libc", --disable-threads, etc., 
>>and again build/install glibc for arm, rebuild gcc with the new arm header
>>and whitout the "inhibit_libc", --disable-threads, etc.? 
Philip Blundell's answer:
>This is the correct way to solve the problem.

So my last question about this is:
Once, after glibc has been built, gcc is built for the second time without
the "inhibit_libc", "__gthr_posix_h", and "--disable-threads" options, do I
need to rebuild glibc as well for all the libraries to be thread safe, or is
only rebuilding gcc sufficient ?

Thanks!
And have a good day!
--
François Desloges
fd@vipswitch.com
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Fri Oct  1 19:19:49 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id TAA04509
	for <linux-arm-archive@lists.arm.linux.org.uk>; Fri, 1 Oct 1999 19:19:49 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 29CF113E5D; Fri,  1 Oct 1999 20:19:31 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156788AbPJASS6>;
	Fri, 1 Oct 1999 14:18:58 -0400
Received: by vger.rutgers.edu id <S156680AbPJASSk>;
	Fri, 1 Oct 1999 14:18:40 -0400
Received: from tazenda.demon.co.uk ([158.152.220.239]:1045 "EHLO
        kings-cross.london.uk.eu.org") by vger.rutgers.edu with ESMTP
	id <S156855AbPJASSU>; Fri, 1 Oct 1999 14:18:20 -0400
Received: from localhost
	([127.0.0.1] helo=kings-cross.london.uk.eu.org ident=phil)
	by kings-cross.london.uk.eu.org with esmtp (Exim 2.05 #1)
	id 11X7CH-0000AQ-00; Fri, 1 Oct 1999 19:14:21 +0100
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: Rod Stewart <stewart@nexus.carleton.ca>
Cc: Francois Desloges <fd@vipswitch.com>, linux-arm@vger.rutgers.edu
Subject: Re: gcc-2.95.1 message 
In-Reply-To: Message from Rod Stewart <stewart@nexus.carleton.ca> 
   of "Fri, 01 Oct 1999 11:37:13 EDT." <Pine.LNX.4.10.9910011135130.10206-100000@nexus.carleton.ca> 
References: <Pine.LNX.4.10.9910011135130.10206-100000@nexus.carleton.ca> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date:   Fri, 01 Oct 1999 19:14:21 +0100
From: Philip Blundell <Philip.Blundell@pobox.com>
Message-Id: <E11X7CH-0000AQ-00@kings-cross.london.uk.eu.org>
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

>It is part of the Objective C package.  You do not need it, unless you
>want to use Objective C.  But then the Objective C backend is not all that
>reliable under ARM...

In fact, last time I looked, the Objective C runtime didn't actually work 
at all on the ARM.  Nobody seemed to care so I didn't spend too much time on 
trying to fix it.

p.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Fri Oct  1 19:21:11 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id TAA04780
	for <linux-arm-archive@lists.arm.linux.org.uk>; Fri, 1 Oct 1999 19:21:11 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id EECD313E0C; Fri,  1 Oct 1999 20:20:58 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156753AbPJASU3>;
	Fri, 1 Oct 1999 14:20:29 -0400
Received: by vger.rutgers.edu id <S156680AbPJASUL>;
	Fri, 1 Oct 1999 14:20:11 -0400
Received: from tazenda.demon.co.uk ([158.152.220.239]:1056 "EHLO
        kings-cross.london.uk.eu.org") by vger.rutgers.edu with ESMTP
	id <S156723AbPJAST4>; Fri, 1 Oct 1999 14:19:56 -0400
Received: from localhost
	([127.0.0.1] helo=kings-cross.london.uk.eu.org ident=phil)
	by kings-cross.london.uk.eu.org with esmtp (Exim 2.05 #1)
	id 11X7HU-0000De-00; Fri, 1 Oct 1999 19:19:44 +0100
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: Francois Desloges <fd@vipswitch.com>
Cc: linux-arm@vger.rutgers.edu
Subject: Re: Gcc-Error & Thread Safe Library 
In-Reply-To: Message from Francois Desloges <fd@vipswitch.com> 
   of "Fri, 01 Oct 1999 13:33:58 EDT." <99100114073202.14871@dual> 
References: <99100114073202.14871@dual> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date:   Fri, 01 Oct 1999 19:19:44 +0100
From: Philip Blundell <Philip.Blundell@pobox.com>
Message-Id: <E11X7HU-0000De-00@kings-cross.london.uk.eu.org>
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

>So my last question about this is:
>Once, after glibc has been built, gcc is built for the second time with
>out the "inhibit_libc", "__gthr_posix_h", and "--disable-threads" options,
>do I need to rebuild glibc as well for all the libraries to be thread safe,
>or is only rebuilding gcc sufficient ?

Just gcc.  Glibc is always thread safe (well, as long as you enable 
LinuxThreads).

p.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Fri Oct  1 19:27:18 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id TAA05047
	for <linux-arm-archive@lists.arm.linux.org.uk>; Fri, 1 Oct 1999 19:27:13 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 48DF813E88; Fri,  1 Oct 1999 20:27:12 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156934AbPJAS0C>;
	Fri, 1 Oct 1999 14:26:02 -0400
Received: by vger.rutgers.edu id <S156781AbPJASZu>;
	Fri, 1 Oct 1999 14:25:50 -0400
Received: from mail-gw6.pacbell.net ([206.13.28.41]:47121 "EHLO
        mail-gw6.pacbell.net") by vger.rutgers.edu with ESMTP
	id <S156926AbPJASXo>; Fri, 1 Oct 1999 14:23:44 -0400
Received: from java (adsl-216-101-151-82.dsl.snfc21.pacbell.net [216.101.151.82])
	by mail-gw6.pacbell.net (8.9.3/8.9.3) with SMTP id LAA06513
	for <linux-arm@vger.rutgers.edu.>; Fri, 1 Oct 1999 11:23:38 -0700 (PDT)
Message-ID: <08ba01bf0c3b$6894a8c0$529765d8@java>
From: "Dave Borja" <dave_bb@pacbell.net>
To: "linux-arm" <linux-arm@vger.rutgers.edu>
Subject: Re: linux-arm-gcc won't find the *.h files
Date:   Fri, 1 Oct 1999 11:33:07 -0700
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.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing


>>#include "..." search starts here:
>>#include <...> search starts here:
>> /usr/local/arm/lib/gcc-lib/arm-linux/egcs-2.91.60/include
>> /usr/local/arm/arm-linux/include
>>End of search list.
>>hello.c:1: stdio.h: No such file or directory
>>
>>It seems to be looking in the wrong place for the .h files as well as
other
>>things. They are there, but just not in the dirs it looks for.
>
>What directory are they in, in fact?  That search path looks pretty much
right
>to me.
>
>>3) Built GLIBC library
>
>You didn't mention what `configure' command you used for this.  I suspect
the
>problem may lie in the --prefix argument you used.
>
>p.
>
----------------------------------------------------------------------------
-------------------------
Hmmm...well I rebuilt the whole thing paying attention to --prefix, etc.
and got the same problem, somehow the configuration makes the
compiler search the wrong directories.....

What follows is all the gory details.....this is really frustrating
(especially
to my boss!).....

Thanks for any help/suggestions.

--------Here is how I built glibc--------------------
[root@harry Dave]# CC=arm-linux-gcc ./configure
arm-linux --build=i686-pc-linux-gnu
--prefix=/usr/local/arm/glibc/arm-linux-glibc --enable-add-ons
--with-headers=/usr/src/armlinux-2.2.12/linux/includels
make
make install

--------------This is what happens after trying the compiler on hello
workd-------

[root@harry Dave]# arm-linux-gcc -v -o helloarm hello.c
Reading specs from /usr/local/arm/lib/gcc-lib/arm-linux/egcs-2.91.66/specs
gcc version egcs-2.91.66 19990325/philb (egcs-1.1.2 release)

/usr/local/arm/lib/gcc-lib/arm-linux/egcs-2.91.66/cpp -lang-c -v -undef -D__
GNUC__=2 -D__GNUC_MINOR__=91 -Dunix -Darm -Dlinux -D__ELF__ -D__unix__ -D__a
rm__ -D__linux__ -D__ELF__ -D__unix -D__arm -D__linux -Asystem(unix) -Asyste
m(posix) -Acpu(arm) -Amachine(arm) -D__CHAR_UNSIGNED__ -D__ARM_ARCH_3__ -D__
APCS_32__ hello.c /tmp/cc7I7ALN.i
GNU CPP version egcs-2.91.66 19990325/philb (egcs-1.1.2 release) (ARM
GNU/Linux with ELF)
#include "..." search starts here:
#include <...> search starts here:
/usr/local/arm/lib/gcc-lib/arm-linux/egcs-2.91.66/include
/usr/local/arm/arm-linux/include
End of search list.
hello.c:1: stdio.h: No such file or directory

----------------This appears to be where the *.h files actually
are!------------
[root@harry gz]# find /usr/local/arm -name "stdio.h"
/usr/local/arm/glibc/arm-linux-glibc/include/bits/stdio.h
/usr/local/arm/glibc/arm-linux-glibc/include/stdio.h

----So, let's look in the directories that arm-linux-gcc searches --------

[root@harry egcs-2.91.66]# pwd
/usr/local/arm/lib/gcc-lib/arm-linux/egcs-2.91.66

[root@harry egcs-2.91.66]# ls
cc1   cpp       crtbeginS.o  crtendS.o  libgcc.a
collect2  crtbegin.o  crtend.o    include    specs

[root@harry egcs-2.91.66]# cd include
[root@harry include]# pwd
/usr/local/arm/lib/gcc-lib/arm-linux/egcs-2.91.66/include
root@harry include]# ls stdio.h
ls: stdio.h: No such file or directory

[root@harry include]# ls
README    new.h typeinfo      va-i960.h     va-pa.h va-v850.h
exception  proto.h va-alpha.h    va-m32r.h     va-ppc.h varargs.h
float.h    stdarg.h va-arc.h      va-m88k.h     va-pyr.h
iso646.h   stdbool.h va-clipper.h  va-mips.h     va-sh.h
limits.h   stddef.h va-h8300.h    va-mn10200.h  va-sparc.h
new    syslimits.h va-i860.h     va-mn10300.h  va-spur.h

------Hmmm. if I use -I option to show it where the *.h is, it fails at
link!------
...and can't find crt1.o ....

[root@harry Dave]#
arm-linux-gcc -v -I/usr/local/arm/glibc/arm-linux-glibc/include
                    -o features.helloarm hello.c
Reading specs from /usr/local/arm/lib/gcc-lib/arm-linux/egcs-2.91.66/specs
gcc version egcs-2.91.66 19990325/philb (egcs-1.1.2 release)
/usr/local/arm/lib/gcc-lib/arm-linux/egcs-2.91.66/cpp -lang-c -v
-I/usr/local/arm/glibc/arm-linux-glibc/include -undef -D__GNUC__=2 -D__GNUC
_MINOR__=91 -Dunix -Darm -Dlinux -D__ELF__ -D__unix__ -D__arm__ -D__linux__
-D__ELF__ -D__unix -D__arm -D__linux -Asystem(unix) -Asystem(posix) -Acpu(ar
m) -Amachine(arm) -D__CHAR_UNSIGNED__ -D__ARM_ARCH_3__ -D__APCS_32__ hello.c
/tmp/ccVQVKnS.i
GNU CPP version egcs-2.91.66 19990325/philb (egcs-1.1.2 release) (ARM
GNU/Linux with ELF)
#include "..." search starts here:
#include <...> search starts here:
/usr/local/arm/glibc/arm-linux-glibc/include
/usr/local/arm/lib/gcc-lib/arm-linux/egcs-2.91.66/include
/usr/local/arm/arm-linux/include
End of search list.
/usr/local/arm/lib/gcc-lib/arm-linux/egcs-2.91.66/cc1
/tmp/ccVQVKnS.i -quiet -dumpbase hello.c -version -o /tmp/ccePzjkJ.s
GNU C version egcs-2.91.66 19990325/philb (egcs-1.1.2 release) (arm-linux)
compiled by GNU C version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release).
/usr/local/arm/arm-linux/bin/as -o /tmp/ccwiBqW7.o /tmp/ccePzjkJ.s
/usr/local/arm/lib/gcc-lib/arm-linux/egcs-2.91.66/collect2 -dynamic-linker
/lib/ld-linux.so.2 -X -m elf32arm -o features.helloarm crt1.o crti.o
/usr/local/arm/lib/gcc-lib/arm-linux/egcs-2.91.66/crtbegin.o -L/usr/local/ar
m/lib/gcc-lib/arm-linux/egcs-2.91.66 -L/usr/local/arm/arm-linux/lib
/tmp/ccwiBqW7.o -lgcc -lc -lgcc
/usr/local/arm/lib/gcc-lib/arm-linux/egcs-2.91.66/crtend.o crtn.o
/usr/local/arm/arm-linux/bin/ld: cannot open crt1.o: No such file or
directory
collect2: ld returned 1 exit status


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Fri Oct  1 19:37:22 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id TAA05703
	for <linux-arm-archive@lists.arm.linux.org.uk>; Fri, 1 Oct 1999 19:37:22 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 475A613EB3; Fri,  1 Oct 1999 20:37:21 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156970AbPJASgy>;
	Fri, 1 Oct 1999 14:36:54 -0400
Received: by vger.rutgers.edu id <S156969AbPJASdv>;
	Fri, 1 Oct 1999 14:33:51 -0400
Received: from tazenda.demon.co.uk ([158.152.220.239]:1091 "EHLO
        kings-cross.london.uk.eu.org") by vger.rutgers.edu with ESMTP
	id <S156909AbPJASc3>; Fri, 1 Oct 1999 14:32:29 -0400
Received: from localhost
	([127.0.0.1] helo=kings-cross.london.uk.eu.org ident=phil)
	by kings-cross.london.uk.eu.org with esmtp (Exim 2.05 #1)
	id 11X7Tj-0000GW-00
	for linux-arm@vger.rutgers.edu; Fri, 1 Oct 1999 19:32:23 +0100
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: "Dave Borja" <dave_bb@pacbell.net>
Subject: Re: linux-arm-gcc won't find the *.h files 
In-Reply-To: Message from "Dave Borja" <dave_bb@pacbell.net> 
   of "Fri, 01 Oct 1999 11:30:33 PDT." <08ab01bf0c3b$0c7a7920$529765d8@java> 
References: <08ab01bf0c3b$0c7a7920$529765d8@java> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date:   Fri, 01 Oct 1999 19:31:43 +0100
From: Philip Blundell <phil@kings-cross.london.uk.eu.org>
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
Message-Id: <19991001183646Z156969-2080+879@vger.rutgers.edu>
X-Orcpt: rfc822;linux-arm-outgoing

>--------Here is how I built glibc--------------------
>[root@harry Dave]# CC=arm-linux-gcc ./configure
>arm-linux --build=i686-pc-linux-gnu
>--prefix=/usr/local/arm/glibc/arm-linux-glibc --enable-add-ons
>--with-headers=/usr/src/armlinux-2.2.12/linux/includels

That seems dubious.  How did you configure GCC?

If you configure GCC with, say, --prefix=/usr/local/arm-tools/, you must 
configure glibc with --prefix=/usr/local/arm-tools/arm-linux/.  It's important 
that one is a subdirectory of the other.

You can't just configure the two with arbitrary prefixes and expect them to 
find each other.

> /usr/local/arm/lib/gcc-lib/arm-linux/egcs-2.91.66/include
> /usr/local/arm/arm-linux/include

That is correct if you configured gcc with --prefix=/usr/local/arm/.

>------Hmmm. if I use -I option to show it where the *.h is, it fails at
>link!------
>...and can't find crt1.o ....

Same problem.

p.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Fri Oct  1 21:32:45 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id VAA09037
	for <linux-arm-archive@lists.arm.linux.org.uk>; Fri, 1 Oct 1999 21:32:40 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id E851313EC7; Fri,  1 Oct 1999 22:32:38 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157504AbPJAUcI>;
	Fri, 1 Oct 1999 16:32:08 -0400
Received: by vger.rutgers.edu id <S157496AbPJAUby>;
	Fri, 1 Oct 1999 16:31:54 -0400
Received: from dfw7-1.relay.mail.uu.net ([199.171.54.106]:63901 "EHLO
        dfw7-1.relay.mail.uu.net") by vger.rutgers.edu with ESMTP
	id <S157499AbPJAUbc>; Fri, 1 Oct 1999 16:31:32 -0400
Received: from xedia.com by dfw7sosrv11.alter.net with SMTP 
	(peer crosschecked as: madway.xedia.com [198.202.232.199])
	id QQhjcc22554;
	Fri, 1 Oct 1999 20:31:25 GMT
Received: from tonga.xedia.com by xedia.com (4.1/SMI-4.1)
	id AA26036; Fri, 1 Oct 99 16:29:39 EDT
Received: by tonga.xedia.com (SMI-8.6/SMI-SVR4)
	id QAA03290; Fri, 1 Oct 1999 16:31:21 -0400
Date:   Fri, 1 Oct 1999 16:31:21 -0400
Message-Id: <199910012031.QAA03290@tonga.xedia.com>
From: Paul Koning <pkoning@xedia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: awiggins@cse.unsw.EDU.AU
Cc: linux-arm@vger.rutgers.edu
Subject: Re: (Off-topic) Real-Time kernels on ARM
References: <Pine.OSF.3.95.991001212534.25259A-100000@paulaner.disy.cse.unsw.EDU.AU>
X-Mailer: VM 6.34 under 20.3 "Vatican City" XEmacs  Lucid
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

>>>>> "Wiggins" == Wiggins  <Adam> writes:

 Wiggins> I'm after any references or design information for real time
 Wiggins> kernels on top of the ARM.

Several of us are interested in something like RTLinux ported to ARM.
I haven't been able to do anything about this yet, unfortunately.

I found some notes on an RTLinux for ARM effort, from Joshua Lamorie
(jpl@xiphos.ca) and Eric LaForest (di458@freenet.carleton.ca).  That
was about a year ago, I don't have newer status.

Alex Holden (<alex_holden@geocities.com) also mentioned this sort of
topic, though it sounds like the RTLinux approach doesn't fit his
needs well.

	paul
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Fri Oct  1 22:30:15 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id WAA11480
	for <linux-arm-archive@lists.arm.linux.org.uk>; Fri, 1 Oct 1999 22:30:15 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 02E7113F27; Fri,  1 Oct 1999 23:30:13 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157646AbPJAV3o>;
	Fri, 1 Oct 1999 17:29:44 -0400
Received: by vger.rutgers.edu id <S157615AbPJAV30>;
	Fri, 1 Oct 1999 17:29:26 -0400
Received: from sparkle.Generation.NET ([205.205.119.4]:58676 "EHLO
        sparkle.Generation.NET") by vger.rutgers.edu with ESMTP
	id <S157676AbPJAV2c>; Fri, 1 Oct 1999 17:28:32 -0400
Received: from dual (generic253.197.205.205.IN-ADDR.ARPA [205.205.197.253] (may be forged))
	by sparkle.Generation.NET (8.9.3/8.9.3) with SMTP id RAA02403
	for <linux-arm@vger.rutgers.edu>; Fri, 1 Oct 1999 17:28:45 -0400 (EDT)
From: Francois Desloges <fd@vipswitch.com>
To: linux-arm@vger.rutgers.edu
Subject: Promise Ultra33 ARM Linux kernel configuration
Date:   Fri, 1 Oct 1999 17:18:02 -0400
Content-Type: text/plain
MIME-Version: 1.0
Message-Id: <99100117271603.14871@dual>
Content-Transfer-Encoding: 8bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

I want to use a Promise Ultra33 controller with my linux-2.2.10 kernel. I know
from ARM Linux website that this is supported.  The two chips on my Ultra33
Controller show the name Promise and the number PDC20247 and PDC20246.
I don't find any of the previous names/numbers as possible choice in the ide
sections of the ARM Linux kernel configuration. The closest thing is a PROMISE
DC4030 support (EXPERIMENTAL) (NEW)

Anybody know what I should use as kernel configuration option for the Promise
Ultra33 ide controler?
--
François Desloges
fd@vipswitch.com
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Fri Oct  1 23:17:15 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id XAA12940
	for <linux-arm-archive@lists.arm.linux.org.uk>; Fri, 1 Oct 1999 23:17:15 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id ED72913DF4; Sat,  2 Oct 1999 00:17:11 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S160064AbPJAWQm>;
	Fri, 1 Oct 1999 18:16:42 -0400
Received: by vger.rutgers.edu id <S156757AbPJAWQc>;
	Fri, 1 Oct 1999 18:16:32 -0400
Received: from [212.219.8.163] ([212.219.8.163]:1327 "HELO inkvine.fluff.org")
	by vger.rutgers.edu with SMTP id <S160086AbPJAWQI>;
	Fri, 1 Oct 1999 18:16:08 -0400
Received: from localhost (localhost [127.0.0.1])
	by inkvine.fluff.org (Postfix) with ESMTP id 2DDB646842
	for <linux-arm@vger.rutgers.edu>; Fri,  1 Oct 1999 23:34:16 +0100 (BST)
Date:   Fri, 1 Oct 1999 23:34:15 +0100 (BST)
From: Chris Rutter <chris@fluff.org>
Reply-To: chris@fluff.org
To: ARM Linux mailing list <linux-arm@vger.rutgers.edu>
Subject: Debian-ARM at LinuxExpo 99
Message-ID: <Pine.LNX.4.10.9910012324490.6186-100000@inkvine.fluff.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Debian are hosting a stand at the forthcoming LinuxExpo in Olympia,
at which (hopefully) there should be a RiscPC stuffed full of the
latest Debian distribution, showing off its wares, as well as a
collection of Debian-ARM stuff for people to duplicate and take away.

See more at <http://www.itevents.co.uk/exhibitions/Linux/> -- come
support!

-- 
Chris <chris@fluff.org>                         ( http://www.fluff.org/chris )

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Fri Oct  1 23:45:44 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id XAA14196
	for <linux-arm-archive@lists.arm.linux.org.uk>; Fri, 1 Oct 1999 23:45:44 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 5D29113F18; Sat,  2 Oct 1999 00:45:43 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156930AbPJAWpO>;
	Fri, 1 Oct 1999 18:45:14 -0400
Received: by vger.rutgers.edu id <S156708AbPJAWo4>;
	Fri, 1 Oct 1999 18:44:56 -0400
Received: from mail-gw6.pacbell.net ([206.13.28.41]:47243 "EHLO
        mail-gw6.pacbell.net") by vger.rutgers.edu with ESMTP
	id <S160072AbPJAWoo>; Fri, 1 Oct 1999 18:44:44 -0400
Received: from java (adsl-216-101-151-82.dsl.snfc21.pacbell.net [216.101.151.82])
	by mail-gw6.pacbell.net (8.9.3/8.9.3) with SMTP id PAA29728
	for <linux-arm@vger.rutgers.edu>; Fri, 1 Oct 1999 15:44:41 -0700 (PDT)
Message-ID: <090901bf0c5f$e03688c0$529765d8@java>
From: "Dave Borja" <dave_bb@pacbell.net>
To: "linux-arm" <linux-arm@vger.rutgers.edu>
Subject: Fw: linux-arm-gcc won't find the *.h files 
Date:   Fri, 1 Oct 1999 15:54:10 -0700
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.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

ok thanks, when I built the egcs stuff, i configured
the prefix as /usr/local/arm and did the make  and make install.

The prefix for glibc build is specified by the intel web site for
building the kernel for brutus and is:
         usr/local/arm/glibc/arm-linux-glibc

It doesn't work for me....

>From your note below, I take it that I should set the prefix for building
glibc to /usr/local/arm/arm-linux, is that correct? I'll try it and see what
happens. Is there a need for the sub directory arm-linux-glibc as
seen in the prefix specified by intel??
  thanks so much,
Dave Borja
MMT Corp
-----Original Message-----
From: Philip Blundell <Philip.Blundell@pobox.com>
To: Dave Borja <dave_bb@pacbell.net>
Date: Friday, October 01, 1999 11:31 AM
Subject: Re: linux-arm-gcc won't find the *.h files


>>--------Here is how I built glibc--------------------
>>[root@harry Dave]# CC=arm-linux-gcc ./configure
>>arm-linux --build=i686-pc-linux-gnu
>>--prefix=/usr/local/arm/glibc/arm-linux-glibc --enable-add-ons
>>--with-headers=/usr/src/armlinux-2.2.12/linux/includels
>
>That seems dubious.  How did you configure GCC?
>
>If you configure GCC with, say, --prefix=/usr/local/arm-tools/, you must
>configure glibc with --prefix=/usr/local/arm-tools/arm-linux/.  It's
important
>that one is a subdirectory of the other.
>
>You can't just configure the two with arbitrary prefixes and expect them to
>find each other.
>
>> /usr/local/arm/lib/gcc-lib/arm-linux/egcs-2.91.66/include
>> /usr/local/arm/arm-linux/include
>
>That is correct if you configured gcc with --prefix=/usr/local/arm/.
>
>>------Hmmm. if I use -I option to show it where the *.h is, it fails at
>>link!------
>>...and can't find crt1.o ....
>
>Same problem.
>
>p.
>
>


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Fri Oct  1 23:53:31 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id XAA14363
	for <linux-arm-archive@lists.arm.linux.org.uk>; Fri, 1 Oct 1999 23:53:31 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 9929113F19; Sat,  2 Oct 1999 00:53:29 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S160090AbPJAWw7>;
	Fri, 1 Oct 1999 18:52:59 -0400
Received: by vger.rutgers.edu id <S160092AbPJAWwu>;
	Fri, 1 Oct 1999 18:52:50 -0400
Received: from tazenda.demon.co.uk ([158.152.220.239]:1235 "EHLO
        kings-cross.london.uk.eu.org") by vger.rutgers.edu with ESMTP
	id <S160090AbPJAWwi>; Fri, 1 Oct 1999 18:52:38 -0400
Received: from localhost
	([127.0.0.1] helo=kings-cross.london.uk.eu.org ident=phil)
	by kings-cross.london.uk.eu.org with esmtp (Exim 2.05 #1)
	id 11XBXN-0001gN-00; Fri, 1 Oct 1999 23:52:25 +0100
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: "Dave Borja" <dave_bb@pacbell.net>
Cc: "linux-arm" <linux-arm@vger.rutgers.edu>
Subject: Re: Fw: linux-arm-gcc won't find the *.h files 
In-Reply-To: Message from "Dave Borja" <dave_bb@pacbell.net> 
   of "Fri, 01 Oct 1999 15:54:10 PDT." <090901bf0c5f$e03688c0$529765d8@java> 
References: <090901bf0c5f$e03688c0$529765d8@java> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date:   Fri, 01 Oct 1999 23:52:24 +0100
From: Philip Blundell <Philip.Blundell@pobox.com>
Message-Id: <E11XBXN-0001gN-00@kings-cross.london.uk.eu.org>
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

>ok thanks, when I built the egcs stuff, i configured
>the prefix as /usr/local/arm and did the make  and make install.
>[...]
>>From your note below, I take it that I should set the prefix for building
>glibc to /usr/local/arm/arm-linux, is that correct?

Yup.

>Is there a need for the sub directory arm-linux-glibc as
>seen in the prefix specified by intel??

Not as far as I know.

p.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sat Oct  2 02:51:07 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id CAA19551
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sat, 2 Oct 1999 02:51:06 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 4B9B313F7B; Sat,  2 Oct 1999 03:50:55 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156698AbPJBBuY>;
	Fri, 1 Oct 1999 21:50:24 -0400
Received: by vger.rutgers.edu id <S156658AbPJBBuK>;
	Fri, 1 Oct 1999 21:50:10 -0400
Received: from mta4.snfc21.pbi.net ([206.13.28.142]:42142 "EHLO
        mta4.snfc21.pbi.net") by vger.rutgers.edu with ESMTP
	id <S156666AbPJBBtw>; Fri, 1 Oct 1999 21:49:52 -0400
Received: from mmtdave ([207.214.214.96])
 by mta4.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.1999.05.24.18.28.p7)
 with SMTP id <0FIY00DGUD2TTQ@mta4.snfc21.pbi.net> for
 linux-arm@vger.rutgers.edu; Fri,  1 Oct 1999 18:49:43 -0700 (PDT)
Date:   Fri, 01 Oct 1999 18:46:33 -0700
From: Dave Borja <dave_bb@pacbell.net>
Subject: linux-arm-gcc won't find the *.h files
To: linux arm <linux-arm@vger.rutgers.edu>
Message-id: <001f01bf0c78$000e28c0$4df63cd1@mmtdave>
MIME-version: 1.0
X-Mailer: Microsoft Outlook Express 4.72.3110.1
Content-type: text/plain; charset="iso-8859-1"
Content-transfer-encoding: 7bit
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
X-Priority: 3
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Thanks for all the help on that, it works-- I just compiled my first
arm "hello world"....I guess that stuff on the intel website is suspect.

Which brings me to another question. After the binutils/egcs/glibc
builds, the instructions call for building the kernel image to be
downloaded.
It is a little bit ambiguous as to which compiler should be used to build
this image-- the gcc native to the host or the arm-linux-gcc we just
built. Intel calls for something like this:

Download the source and unzip/untar:

%cd /home/~user~/armbuild/
            %gzip -dc /home/~user~/gz/linux-2.2.2.tar.gz | tar xvf -
            %cd linux
            %gzip -dc /home/~user~/gz/patch-2.2.2-rmk5.gz | patch -p1
            %gzip -dc /home/~user~/gz/diff-2.2.2-rmk5-np3.gz | patch -p1
Build the kernel and choose defaults when prompted:

            %make config
            %make zImage

            This seems wrong to me-- it will build a kernel
            for the i686 using the native gcc compiler.
            Don't we need to edit or configure the make to
            build an arm target and produce a zImage in linux/arch/arm/boot?
            THanks,
            Dave Borja
            MMT Corp






unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sat Oct  2 03:21:48 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id DAA20379
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sat, 2 Oct 1999 03:21:47 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 2071813F8D; Sat,  2 Oct 1999 04:21:46 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156669AbPJBCVT>;
	Fri, 1 Oct 1999 22:21:19 -0400
Received: by vger.rutgers.edu id <S156666AbPJBCVA>;
	Fri, 1 Oct 1999 22:21:00 -0400
Received: from [212.219.8.163] ([212.219.8.163]:1343 "HELO inkvine.fluff.org")
	by vger.rutgers.edu with SMTP id <S156652AbPJBCUm>;
	Fri, 1 Oct 1999 22:20:42 -0400
Received: from localhost (localhost [127.0.0.1])
	by inkvine.fluff.org (Postfix) with ESMTP
	id D08BB46842; Sat,  2 Oct 1999 03:38:53 +0100 (BST)
Date:   Sat, 2 Oct 1999 03:38:53 +0100 (BST)
From: Chris Rutter <chris@fluff.org>
Reply-To: chris@fluff.org
To: "thomas.marx" <thomas.marx@dialup.rwth-aachen.de>
Cc: linux-arm@vger.rutgers.edu
Subject: Re: Probs with installing RPMs
In-Reply-To: <5737561949%thomas.marx@tm913045.dialup.rwth-aachen.de>
Message-ID: <Pine.LNX.4.10.9910020337410.6186-100000@inkvine.fluff.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

On Mon, 28 Jun 1999, thomas.marx wrote:

> So I got the new rpm package (rpm-3.0-6.0) and wnated to upgrade.
> It gave me the same error.

If you haven't yet fixed this (note the date above), then you need
to use the rpm in the `a.out+libc4' directory on the FTP site as
a stepping stone -- check the mailing list archive for a posting from
me about it.

-- 
Chris <chris@fluff.org>                         ( http://www.fluff.org/chris )

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sat Oct  2 03:23:46 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id DAA20391
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sat, 2 Oct 1999 03:23:46 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 1293E13F8B; Sat,  2 Oct 1999 04:23:38 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156680AbPJBCXK>;
	Fri, 1 Oct 1999 22:23:10 -0400
Received: by vger.rutgers.edu id <S156666AbPJBCWx>;
	Fri, 1 Oct 1999 22:22:53 -0400
Received: from [212.219.8.163] ([212.219.8.163]:1346 "HELO inkvine.fluff.org")
	by vger.rutgers.edu with SMTP id <S156652AbPJBCWe>;
	Fri, 1 Oct 1999 22:22:34 -0400
Received: from localhost (localhost [127.0.0.1])
	by inkvine.fluff.org (Postfix) with ESMTP id 16AD846874
	for <linux-arm@vger.rutgers.edu>; Sat,  2 Oct 1999 03:40:46 +0100 (BST)
Date:   Sat, 2 Oct 1999 03:40:46 +0100 (BST)
From: Chris Rutter <chris@fluff.org>
Reply-To: chris@fluff.org
To: ARM Linux mailing list <linux-arm@vger.rutgers.edu>
Subject: Re: Probs with installing RPMs
In-Reply-To: <Pine.LNX.4.10.9906282153130.9126-100000@nexus.carleton.ca>
Message-ID: <Pine.LNX.4.10.9910020339360.6186-100000@inkvine.fluff.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

On Mon, 28 Jun 1999, Rod m. Stewart wrote:

> Now rpm should understand your Datatype (I think), and you can upgrade as
> you like...

No no!  *Bad* idea -- he probably almost certainly only has the libc4
support libraries on his machine, even if he has ELF support in the
kernel.  He wants to use the special a.out/libc4 version of RPM
on my FTP site.

-- 
Chris <chris@fluff.org>                         ( http://www.fluff.org/chris )

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sat Oct  2 03:31:56 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id DAA20664
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sat, 2 Oct 1999 03:31:56 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 1475513F93; Sat,  2 Oct 1999 04:31:54 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156683AbPJBCbX>;
	Fri, 1 Oct 1999 22:31:23 -0400
Received: by vger.rutgers.edu id <S156669AbPJBCbO>;
	Fri, 1 Oct 1999 22:31:14 -0400
Received: from [212.219.8.163] ([212.219.8.163]:1348 "HELO inkvine.fluff.org")
	by vger.rutgers.edu with SMTP id <S156666AbPJBCbF>;
	Fri, 1 Oct 1999 22:31:05 -0400
Received: from localhost (localhost [127.0.0.1])
	by inkvine.fluff.org (Postfix) with ESMTP id 27E8346874
	for <linux-arm@vger.rutgers.edu>; Sat,  2 Oct 1999 03:49:12 +0100 (BST)
Date:   Sat, 2 Oct 1999 03:49:12 +0100 (BST)
From: Chris Rutter <chris@fluff.org>
Reply-To: chris@fluff.org
To: ARM Linux mailing list <linux-arm@vger.rutgers.edu>
Subject: Re: This time it's gcc... :-( 
In-Reply-To: <E11Bwmq-0003pM-00@fountain.nexus.co.uk>
Message-ID: <Pine.LNX.4.10.9910020347180.6186-100000@inkvine.fluff.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

On Wed, 4 Aug 1999, Philip Blundell wrote:

> Don't do that, then - just configure and make at the top level.  The gcc 
> subdirectory depends on other things such as libiberty that need to be built 
> first.

What happens to all the bits of the compiler that depend on libc?
Presumably it's impossible to reach a working `make install' target
unless you inhibt make from considering these?  Is `make LANGUAGES="c"'
at the top level the correct way of doing this?

-- 
Chris <chris@fluff.org>                         ( http://www.fluff.org/chris )

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sat Oct  2 04:01:15 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id EAA21527
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sat, 2 Oct 1999 04:01:15 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 7D94E13F51; Sat,  2 Oct 1999 05:01:12 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156669AbPJBDAh>;
	Fri, 1 Oct 1999 23:00:37 -0400
Received: by vger.rutgers.edu id <S156666AbPJBDAJ>;
	Fri, 1 Oct 1999 23:00:09 -0400
Received: from [212.219.8.163] ([212.219.8.163]:1351 "HELO inkvine.fluff.org")
	by vger.rutgers.edu with SMTP id <S156652AbPJBC77>;
	Fri, 1 Oct 1999 22:59:59 -0400
Received: from localhost (localhost [127.0.0.1])
	by inkvine.fluff.org (Postfix) with ESMTP id 00EEC46842
	for <linux-arm@vger.rutgers.edu>; Sat,  2 Oct 1999 03:59:57 +0100 (BST)
Date:   Sat, 2 Oct 1999 03:59:57 +0100 (BST)
From: Chris Rutter <chris@fluff.org>
Reply-To: chris@fluff.org
To: ARM Linux mailing list <linux-arm@vger.rutgers.edu>
Subject: Re: ArmLinux on an A5000 8MB
In-Reply-To: <199909161936.UAA32182@raistlin.armlinux.org.uk>
Message-ID: <Pine.LNX.4.10.9910020355560.13764-100000@inkvine.fluff.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

On Thu, 16 Sep 1999 linux@arm.linux.org.uk wrote:

> > What Ethernet cards (if any) do you have in this machine?  Freezes
> > on attempting rebooting is very common with ARM Linux -- just hit
> > the power switch.
> 
> They are?  Would someone like to send comprehensive details of these
> "very common" problems?
>    _____
>   |_____| ------------------------------------------------- ---+---+-
>   |   |        Russell King       linux@arm.linux.org.uk      --- ---
>   | | | |  http://www.arm.linux.org.uk/~rmk/armlinux.html    /  /  |
>   | +-+-+                                                     --- -+-
>   /   |               THE developer of ARM Linux              |+| /|\
>  /  | | |                                                     ---  |
>     +-+-+ -------------------------------------------------  /\\\  |

Yeah, I already did, about six months ago.  In the end I contacted
George Hawes directly, and got put on to the author of the RISC OS
driver (for the EtherH), and negotiated with him privately a bit.
I never bothered fixing the problem, because I've actually been
less than active for a few months.  I'll debug it with you at some
later date; it's a pain, as it prevents remote kernel upgrade or
reboot.

Oh, and you know the Emily Postnews FAQ... "-- "...

-- 
Chris <chris@fluff.org>                         ( http://www.fluff.org/chris )

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sat Oct  2 04:12:27 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id EAA21864
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sat, 2 Oct 1999 04:12:27 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id D15A513F92; Sat,  2 Oct 1999 05:12:24 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156666AbPJBDMD>;
	Fri, 1 Oct 1999 23:12:03 -0400
Received: by vger.rutgers.edu id <S156652AbPJBDLz>;
	Fri, 1 Oct 1999 23:11:55 -0400
Received: from [212.219.8.163] ([212.219.8.163]:1356 "HELO inkvine.fluff.org")
	by vger.rutgers.edu with SMTP id <S156658AbPJBDLo>;
	Fri, 1 Oct 1999 23:11:44 -0400
Received: from localhost (localhost [127.0.0.1])
	by inkvine.fluff.org (Postfix) with ESMTP
	id AF19546842; Sat,  2 Oct 1999 04:11:42 +0100 (BST)
Date:   Sat, 2 Oct 1999 04:11:42 +0100 (BST)
From: Chris Rutter <chris@fluff.org>
Reply-To: chris@fluff.org
To: Jan-Uwe Finck <ju_finck@mail.netwave.de>
Cc: ARM Linux mailing list <linux-arm@vger.rutgers.edu>
Subject: Re: glibc-build still fails
In-Reply-To: <19990923222929.A5283@mail.netwave.de>
Message-ID: <Pine.LNX.4.10.9910020410370.13764-100000@inkvine.fluff.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

On Thu, 23 Sep 1999, Jan-Uwe Finck wrote:

> after expanding my RiscPC's RAM to 96 MB I still can not build the
> glibc-2.1.2pre3.
> The error remains the same, memory exhausted (I still can't believe
> that, 'top' said, there was nearly no swap used..)

Er, dim question perhaps, but is a.out involved at any stage of the
build process?  Remember that the a.out shared library mechanism
introduces a 12MB maximum data segment size (or someting similar
that causes premature memory exhaustion)...

-- 
Chris <chris@fluff.org>                         ( http://www.fluff.org/chris )

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sat Oct  2 04:14:51 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id EAA21941
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sat, 2 Oct 1999 04:14:51 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id C414B13EB5; Sat,  2 Oct 1999 05:14:45 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156669AbPJBDOY>;
	Fri, 1 Oct 1999 23:14:24 -0400
Received: by vger.rutgers.edu id <S156658AbPJBDOP>;
	Fri, 1 Oct 1999 23:14:15 -0400
Received: from [212.219.8.163] ([212.219.8.163]:1359 "HELO inkvine.fluff.org")
	by vger.rutgers.edu with SMTP id <S156652AbPJBDN7>;
	Fri, 1 Oct 1999 23:13:59 -0400
Received: from localhost (localhost [127.0.0.1])
	by inkvine.fluff.org (Postfix) with ESMTP id 1B2F846842
	for <linux-arm@vger.rutgers.edu>; Sat,  2 Oct 1999 04:13:58 +0100 (BST)
Date:   Sat, 2 Oct 1999 04:13:58 +0100 (BST)
From: Chris Rutter <chris@fluff.org>
Reply-To: chris@fluff.org
To: ARM Linux mailing list <linux-arm@vger.rutgers.edu>
Subject: Re: glibc-build still fails 
In-Reply-To: <E11USmk-0002ee-00@fountain.nexus.co.uk>
Message-ID: <Pine.LNX.4.10.9910020413000.13764-100000@inkvine.fluff.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

On Fri, 24 Sep 1999, Philip Blundell wrote:

> Ah.  I thought you'd installed the Debian versions.  If you are still using 
> a.out you will suffer from the infamous 12MB limit.

Ack, I rid myself of my last statically-linked `ld' binary; could
someone supply me with one of these gems, so I can link to it from
the toolchain guide?

(As in old binutils, a.out ld.)

-- 
Chris <chris@fluff.org>                         ( http://www.fluff.org/chris )

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sat Oct  2 12:53:48 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id MAA03677
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sat, 2 Oct 1999 12:53:48 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 2457813E7B; Sat,  2 Oct 1999 13:53:46 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156673AbPJBLxN>;
	Sat, 2 Oct 1999 07:53:13 -0400
Received: by vger.rutgers.edu id <S156680AbPJBLwz>;
	Sat, 2 Oct 1999 07:52:55 -0400
Received: from tazenda.demon.co.uk ([158.152.220.239]:1261 "EHLO
        kings-cross.london.uk.eu.org") by vger.rutgers.edu with ESMTP
	id <S156652AbPJBLwq>; Sat, 2 Oct 1999 07:52:46 -0400
Received: from localhost
	([127.0.0.1] helo=kings-cross.london.uk.eu.org ident=phil)
	by kings-cross.london.uk.eu.org with esmtp (Exim 2.05 #1)
	id 11XNfc-0002qx-00; Sat, 2 Oct 1999 12:49:44 +0100
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: chris@fluff.org
Cc: ARM Linux mailing list <linux-arm@vger.rutgers.edu>
Subject: Re: This time it's gcc... :-( 
In-Reply-To: Message from Chris Rutter <chris@fluff.org> 
   of "Sat, 02 Oct 1999 03:49:12 BST." <Pine.LNX.4.10.9910020347180.6186-100000@inkvine.fluff.org> 
References: <Pine.LNX.4.10.9910020347180.6186-100000@inkvine.fluff.org> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date:   Sat, 02 Oct 1999 12:49:44 +0100
From: Philip Blundell <Philip.Blundell@pobox.com>
Message-Id: <E11XNfc-0002qx-00@kings-cross.london.uk.eu.org>
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

>> Don't do that, then - just configure and make at the top level.  The gcc 
>> subdirectory depends on other things such as libiberty that need to be built
>> first.
>
>What happens to all the bits of the compiler that depend on libc?
>Presumably it's impossible to reach a working `make install' target
>unless you inhibt make from considering these?  Is `make LANGUAGES="c"'
>at the top level the correct way of doing this?

I don't think that will work.  What you have to do is `make' at the top level, 
wait for it to crash, then `make install' in the gcc subdirectory.

p.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sat Oct  2 12:54:16 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id MAA03701
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sat, 2 Oct 1999 12:54:16 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id B4B4A13E39; Sat,  2 Oct 1999 13:54:14 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156683AbPJBLxo>;
	Sat, 2 Oct 1999 07:53:44 -0400
Received: by vger.rutgers.edu id <S156680AbPJBLxP>;
	Sat, 2 Oct 1999 07:53:15 -0400
Received: from tazenda.demon.co.uk ([158.152.220.239]:1265 "EHLO
        kings-cross.london.uk.eu.org") by vger.rutgers.edu with ESMTP
	id <S156666AbPJBLw4>; Sat, 2 Oct 1999 07:52:56 -0400
Received: from localhost
	([127.0.0.1] helo=kings-cross.london.uk.eu.org ident=phil)
	by kings-cross.london.uk.eu.org with esmtp (Exim 2.05 #1)
	id 11XLDe-0002pN-00; Sat, 2 Oct 1999 10:12:42 +0100
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: Dave Borja <dave_bb@pacbell.net>
Cc: linux arm <linux-arm@vger.rutgers.edu>
Subject: Re: linux-arm-gcc won't find the *.h files 
In-Reply-To: Message from Dave Borja <dave_bb@pacbell.net> 
   of "Fri, 01 Oct 1999 18:46:33 PDT." <001f01bf0c78$000e28c0$4df63cd1@mmtdave> 
References: <001f01bf0c78$000e28c0$4df63cd1@mmtdave> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date:   Sat, 02 Oct 1999 10:12:42 +0100
From: Philip Blundell <Philip.Blundell@pobox.com>
Message-Id: <E11XLDe-0002pN-00@kings-cross.london.uk.eu.org>
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

>It is a little bit ambiguous as to which compiler should be used to build
>this image-- the gcc native to the host or the arm-linux-gcc we just
>built. Intel calls for something like this:

It's the latter one you need.

>            Don't we need to edit or configure the make to
>            build an arm target and produce a zImage in linux/arch/arm/boot?

Yes.  This is the definition of CROSS_COMPILE in linux/Makefile.  Set it to 
something like "arm-linux-" and make sure `arm-linux-gcc' is in your PATH.

p.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sat Oct  2 14:53:21 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id OAA07035
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sat, 2 Oct 1999 14:53:21 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 08D5913EEB; Sat,  2 Oct 1999 15:53:20 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156669AbPJBNw7>;
	Sat, 2 Oct 1999 09:52:59 -0400
Received: by vger.rutgers.edu id <S156652AbPJBNwv>;
	Sat, 2 Oct 1999 09:52:51 -0400
Received: from m54-nsv1-trogon.tch.cableol.net ([194.168.16.54]:61026 "EHLO
        caramon.armlinux.org.uk") by vger.rutgers.edu with ESMTP
	id <S156666AbPJBNwW>; Sat, 2 Oct 1999 09:52:22 -0400
Received: from raistlin.armlinux.org.uk (linux@raistlin [192.168.0.3])
	by caramon.armlinux.org.uk (8.8.7/8.8.7) with ESMTP id OAA08941;
	Sat, 2 Oct 1999 14:51:57 +0100
From: linux@arm.linux.org.uk
Received: (from linux@localhost) by raistlin.armlinux.org.uk (8.7.4/8.7.3) id OAA26540; Sat, 2 Oct 1999 14:50:14 +0100
Message-Id: <199910021350.OAA26540@raistlin.armlinux.org.uk>
Subject: Re: Promise Ultra33 ARM Linux kernel configuration
To: fd@vipswitch.com (Francois Desloges)
Date:   Sat, 2 Oct 1999 14:50:13 +0100 (BST)
Cc: linux-arm@vger.rutgers.edu
In-Reply-To: <99100117271603.14871@dual> from "Francois Desloges" at Oct 1, 99 05:18:02 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Francois Desloges writes:
> I want to use a Promise Ultra33 controller with my linux-2.2.10 kernel. I know
> from ARM Linux website that this is supported.  The two chips on my Ultra33
> Controller show the name Promise and the number PDC20247 and PDC20246.
> I don't find any of the previous names/numbers as possible choice in the ide
> sections of the ARM Linux kernel configuration. The closest thing is a PROMISE
> DC4030 support (EXPERIMENTAL) (NEW)

You want to select the following options:

 Generic PCI bus-master DMA support
 Use PCI DMA by default when available

The Promise card is supported as a Generic PCI bus-master card.
   _____
  |_____| ------------------------------------------------- ---+---+-
  |   |        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' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sat Oct  2 19:34:07 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id TAA18428
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sat, 2 Oct 1999 19:34:02 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id ED4F613F68; Sat,  2 Oct 1999 20:34:00 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156669AbPJBSda>;
	Sat, 2 Oct 1999 14:33:30 -0400
Received: by vger.rutgers.edu id <S156666AbPJBSdX>;
	Sat, 2 Oct 1999 14:33:23 -0400
Received: from thorgal.et.tudelft.nl ([130.161.40.91]:12423 "EHLO
        thorgal.et.tudelft.nl") by vger.rutgers.edu with ESMTP
	id <S156787AbPJBS3v>; Sat, 2 Oct 1999 14:29:51 -0400
Received: from [130.161.40.82] (tvs082.et.tudelft.nl [130.161.40.82])
	by thorgal.et.tudelft.nl (8.8.7/8.8.7) with ESMTP id UAA05611;
	Sat, 2 Oct 1999 20:29:22 +0200
Message-Id: <v03130300b41bf2bb8381@[130.161.40.82]>
In-Reply-To: <003101bf0be0$d59a43e0$0401a8c0@casagrande.way>
References: <081a01bf0b7d$900a60c0$529765d8@java>
 <E11WolP-0000Oa-00@kings-cross.london.uk.eu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date:   Sat, 2 Oct 1999 19:36:33 +0200
To: Ian Field <ianfield@pobox.com>
From: "J.D. Bakker" <bakker@thorgal.et.tudelft.nl>
Subject: Re: ramdisk.gz
Cc: linux-arm <linux-arm@vger.rutgers.edu>
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

At 09:44 +0200 01-10-1999, Ian Field wrote:
>On the SA1100 or in general, has anybody else found problems with compressed
>ramdisks. I find an uncompressed ext2 image works fine, but when I gzip it,
>it fails alot of the time ...

No problems for me; I use that setup all the time on my embedded SA1100
board. What kernel/compiler are you using ? ISTR that I had some initial
trouble when compiling the kernel with 2.95.1.

JDB.

--
Why is my good friend the Y2K cobol programmer selling all his goods,
buying gold, guns & food and moving his family to a place in the
mountains? And trying to convince me to do the same?
                                        -- Tom ONeil in the Monastery


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sun Oct  3 01:45:44 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id BAA30732
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sun, 3 Oct 1999 01:45:44 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 168DE14036; Sun,  3 Oct 1999 02:45:43 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156816AbPJCApX>;
	Sat, 2 Oct 1999 20:45:23 -0400
Received: by vger.rutgers.edu id <S156795AbPJCApL>;
	Sat, 2 Oct 1999 20:45:11 -0400
Received: from proxy4.ba.best.com ([206.184.139.15]:3684 "EHLO
        proxy4.ba.best.com") by vger.rutgers.edu with ESMTP
	id <S156677AbPJCAo4>; Sat, 2 Oct 1999 20:44:56 -0400
Received: from mmtdave (ppp-207-214-212-23.sntc01.pacbell.net [207.214.212.23])
	by proxy4.ba.best.com (8.9.3/8.9.2/best.out) with SMTP id RAA29021
	for <linux-arm@vger.rutgers.edu>; Sat, 2 Oct 1999 17:43:33 -0700 (PDT)
Message-ID: <001101bf0d37$edd22d80$4df63cd1@mmtdave>
From: "Tony Xu" <tonyx@millentek.com>
To: "linux arm" <linux-arm@vger.rutgers.edu>
Subject: brutus kernel image won't boot
Date:   Sat, 2 Oct 1999 17:39:23 -0700
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.3110.1
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Thanks for all the help so far in getting
our cross compile environment going. We
got it set up and successfully compiled and
linked an arm executable.

Now we are having download headaches-- how
do we tell what is going on (both right and
wrong?). This is on a brutus-- we are following
the directions on the intel site 

(http://developer.intel.com/design/strong/applnots/sa1100lx).


We expect to be able to see the kernel console using
a terminal program on the host (but it's not clear to
us how the kernel knows to use the com port on the
brutus as the console).

So far, we aren't getting anything to boot.

The details:

We fixed up the make file thusly, 
   ARCH:=arm 
   CROSS_COMPILE = arm-linux-

   %make config
   %make zImage
and compiled there kernel, getting a nice
zImage in arch/arm.

We copied our app to the ramdisk and compressed
it again to ramdisk.gz 

We are uing angelboot to do the download with
the opt file configued with:                         
                        
opt file:    
   base 0x8000
   entry 0xc0008000
   device /dev/ttyS0
   options "9600 8N1"
   baud 115200
   otherfile ramdisk.gz
   otherbase 0x800000
                        
We connected a null modem serial cable from COM1
(/dev/tty/S0) on  our linux host to port J23 on
the brutus (also com1 there?) We connected 
another null modem serial cable from j22 on
the brutus to a com port on a windows 98 machine
and accessed the port using hyperterminal.
Our parms here were 9600 baud n81 (we are using cheap
machines, w/only one external serial port!).

Kicking off angelboot downloads our ramdisk and zImage (or
at least it looks like it. But no LOGON prompt comes
up on our hyper terminal. I'm assumming that the
boot loader should get immediate control right
after angel finishes the download and nothing further
should be required on our part. Any help
would be much appreciated! 

We've tried some variations 
(using an uncompressed ramdisk and specifying
the entry parm inthe opt file as 0xc0008020
instead of 0xc0008000 but nothing helps :(

Thanks,
Dave



unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sun Oct  3 12:08:58 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id MAA14994
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sun, 3 Oct 1999 12:08:53 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 0488B13EA2; Sun,  3 Oct 1999 13:08:51 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156829AbPJCLIS>;
	Sun, 3 Oct 1999 07:08:18 -0400
Received: by vger.rutgers.edu id <S156816AbPJCLHt>;
	Sun, 3 Oct 1999 07:07:49 -0400
Received: from [212.219.8.163] ([212.219.8.163]:1468 "HELO inkvine.fluff.org")
	by vger.rutgers.edu with SMTP id <S156701AbPJCLHc>;
	Sun, 3 Oct 1999 07:07:32 -0400
Received: from localhost (localhost [127.0.0.1])
	by inkvine.fluff.org (Postfix) with ESMTP id 44EBB46842
	for <linux-arm@vger.rutgers.edu>; Sun,  3 Oct 1999 12:07:15 +0100 (BST)
Date:   Sun, 3 Oct 1999 12:07:15 +0100 (BST)
From: Chris Rutter <chris@fluff.org>
Reply-To: chris@fluff.org
To: ARM Linux mailing list <linux-arm@vger.rutgers.edu>
Subject: Toolchain guide
Message-ID: <Pine.LNX.4.10.9910031204430.15828-100000@inkvine.fluff.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

I've finally had an overhaul and update of my toolchain guide; you
can find the result, as ever, at:

  http://www.inkvine.fluff.org/~chris/arm-tools.html

Stuff like the inhibit_libc hack is now mentioned, along with some
extra patches, and stuff.

One caveat: I just tried following through the whole document and
got some build error in glibc re: threads, although according to
the mailing list archives I think it should work.  I'll post more
when Jenny hasn't got the PC in Windoze *grumble grumble*.

-- 
Chris <chris@fluff.org>                         ( http://www.fluff.org/chris )

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sun Oct  3 13:25:54 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id NAA18309
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sun, 3 Oct 1999 13:25:54 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 9A8C0140A4; Sun,  3 Oct 1999 14:25:52 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156697AbPJCMZT>;
	Sun, 3 Oct 1999 08:25:19 -0400
Received: by vger.rutgers.edu id <S156652AbPJCMZD>;
	Sun, 3 Oct 1999 08:25:03 -0400
Received: from oskar.nanoteq.co.za ([196.37.91.10]:2015 "EHLO
        oskar.nanoteq.co.za") by vger.rutgers.edu with ESMTP
	id <S156696AbPJCMYp>; Sun, 3 Oct 1999 08:24:45 -0400
Received: from craul.nanoteq.co.za (IDENT:chris@craul.nanoteq.co.za [196.37.91.24])
	by oskar.nanoteq.co.za (8.9.0/8.9.0) with ESMTP id OAA03158
	for <linux-arm@vger.rutgers.edu>; Sun, 3 Oct 1999 14:27:42 +0200 (SAT)
Message-ID: <37F78360.5C3E48C2@craul.nanoteq.co.za>
Date:   Sun, 03 Oct 1999 14:25:04 -0200
From: Chris Bohme <chris@craul.nanoteq.co.za>
Reply-To: cbo@nanoteq.co.za
Organization: Nanoteq
X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.2.10 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: linux-arm <linux-arm@vger.rutgers.edu>
Subject: Russell's bios/bootloader (or booting the EBSA285)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Hi there,

maybe this is a silly question: how do you actually use Russell's
bootloader for the ebsa285 ? Host bridge mode or add in mode ? From
glancing through the source, hmmm ... keyboard events, so  do actually
stick the card into a motherboard or a passive back plane ?

The actual question for those of you who got linux to work on the
ebsa285: How did you get started ? (I'm really battling here....)

Tried to download kernel image via angelboot (as zImage and as AIF) but
nothing is seen on the serial port and the LEDs are just dead.

Tried Russell's bios, but the card never gets as far as initializing
either network or screen card (all 3 LEDs remain on).

Can anyone who is using the ebsa285 give me an idea how you got started
?

Thanks !

Chris



unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sun Oct  3 18:57:01 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id SAA28115
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sun, 3 Oct 1999 18:57:00 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id AAF7014084; Sun,  3 Oct 1999 19:56:59 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156762AbPJCR41>;
	Sun, 3 Oct 1999 13:56:27 -0400
Received: by vger.rutgers.edu id <S156709AbPJCR4S>;
	Sun, 3 Oct 1999 13:56:18 -0400
Received: from note.orchestra.cse.unsw.EDU.AU ([129.94.242.29]:2172 "HELO
        note.orchestra.cse.unsw.EDU.AU") by vger.rutgers.edu with SMTP
	id <S156680AbPJCR4H>; Sun, 3 Oct 1999 13:56:07 -0400
Received: From paulaner With LocalMail ; Mon, 4 Oct 99 03:55:29 +1000 
From: "Adam 'WeirdArms' Wiggins" <awiggins@cse.unsw.EDU.AU>
To: Paul Koning <pkoning@xedia.com>
Date:   Mon, 4 Oct 1999 03:55:29 +1000 (EST)
X-Sender: awiggins@paulaner.disy.cse.unsw.EDU.AU
Cc: linux-arm@vger.rutgers.edu
Subject: Re: (Off-topic) Real-Time kernels on ARM
In-Reply-To: <199910012031.QAA03290@tonga.xedia.com>
Message-ID: <Pine.OSF.3.95.991004034235.7227H-100000@paulaner.disy.cse.unsw.EDU.AU>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

On Fri, 1 Oct 1999, Paul Koning wrote:

> >>>>> "Wiggins" == Wiggins  <Adam> writes:
> 
>  Wiggins> I'm after any references or design information for real time
>  Wiggins> kernels on top of the ARM.
> 
> Several of us are interested in something like RTLinux ported to ARM.
> I haven't been able to do anything about this yet, unfortunately.
> 
> I found some notes on an RTLinux for ARM effort, from Joshua Lamorie
> (jpl@xiphos.ca) and Eric LaForest (di458@freenet.carleton.ca).  That
> was about a year ago, I don't have newer status.

	While RTLinux is a very interesting and worthwhile project it
didn't help too much :( Beyound clarifying a few things and bringing about
a few minor idea's its the wrong things for what I'm looking for.
Particularly the RT executive itself is not preemptable, the RT threads
run in a single address space as well. These are the problems I'm looking
to solve. I have some idea's but they still need formalising. Also no one
seems to be interested in Microkernel development (due to asumptions about
performance) which makes it hard to get feedback.
	The main problem is this, we have a high performance Microkernel
and a fairly good back or developers and users with a couple of ports.
However no one is using it for hard real time systems sand none of us have
any background with hard real time systems so I'm at a loss.
	
	Anyway thats probably heaps off topic so if anyone can point me to
a place I can get some information on I'd appreciate it. I've not found a
good reference point yet. RTLinux aswas the best so far as all Real Time
ARM kernels I've found have been relatively propriatry. Can any point out
some Real Time interest groups I might bother ;)

	Cheers Adam
 
> > Alex Holden (<alex_holden@geocities.com) also mentioned this sort of
> topic, though it sounds like the RTLinux approach doesn't fit his
> needs well.

	I'd be interested to hear why it didn't fit his needs, Alex?

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sun Oct  3 20:25:10 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id UAA30731
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sun, 3 Oct 1999 20:25:10 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 27F89140BB; Sun,  3 Oct 1999 21:25:09 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156782AbPJCTYf>;
	Sun, 3 Oct 1999 15:24:35 -0400
Received: by vger.rutgers.edu id <S156703AbPJCTY2>;
	Sun, 3 Oct 1999 15:24:28 -0400
Received: from adsl-63-192-134-89.dsl.snfc21.pacbell.net ([63.192.134.89]:1386
        "EHLO tsuenwan.causality.com") by vger.rutgers.edu with ESMTP
	id <S156680AbPJCTV4>; Sun, 3 Oct 1999 15:21:56 -0400
Received: from causality.com (localhost [127.0.0.1])
	by tsuenwan.causality.com (8.9.3/8.9.2) with ESMTP id MAA06272;
	Sun, 3 Oct 1999 12:17:09 -0700 (PDT)
	(envelope-from neil@causality.com)
Message-ID: <37F7ABB5.6FFE08D0@causality.com>
Date:   Sun, 03 Oct 1999 12:17:09 -0700
From: "Neil A. Carson" <neil@causality.com>
Organization: Causality Limited
X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 3.2-RELEASE i386)
X-Accept-Language: en-GB
MIME-Version: 1.0
To: "Adam 'WeirdArms' Wiggins" <awiggins@cse.unsw.EDU.AU>
Cc: Paul Koning <pkoning@xedia.com>, linux-arm@vger.rutgers.edu
Subject: Re: (Off-topic) Real-Time kernels on ARM
References: <Pine.OSF.3.95.991004034235.7227H-100000@paulaner.disy.cse.unsw.EDU.AU>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

We wrote a hard real time microkernel called kelad-1 for work. Although
I can't distribute the source, I might be able to answer any operational
and performaance and scalability questions off news-group. It was
probably the best overall OS architecture I've seen yet...

	Neil
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sun Oct  3 22:05:40 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id WAA00978
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sun, 3 Oct 1999 22:05:39 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id D76CC140F9; Sun,  3 Oct 1999 23:05:37 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156704AbPJCVFH>;
	Sun, 3 Oct 1999 17:05:07 -0400
Received: by vger.rutgers.edu id <S156680AbPJCVE6>;
	Sun, 3 Oct 1999 17:04:58 -0400
Received: from [216.50.211.108] ([216.50.211.108]:24716 "EHLO
        mail.quackware.com") by vger.rutgers.edu with ESMTP
	id <S156703AbPJCVEo>; Sun, 3 Oct 1999 17:04:44 -0400
Received: from quackware.com (IDENT:jon@anyprice.com [216.50.211.108])
	by mail.quackware.com (8.9.3/8.9.3) with ESMTP id OAA29454
	for <linux-arm@vger.rutgers.edu>; Sun, 3 Oct 1999 14:04:40 -0700
Message-ID: <37F7C4E7.53317B4@quackware.com>
Date:   Sun, 03 Oct 1999 14:04:39 -0700
From: Jonathan Foster Kliegman <jon@quackware.com>
Organization: Quackware
X-Mailer: Mozilla 4.61 [en] (X11; U; Linux 2.0.35 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: linux-arm@vger.rutgers.edu
Subject: Re: Russell's bios/bootloader (or booting the EBSA285)
References: <37F78360.5C3E48C2@craul.nanoteq.co.za>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

If you have the EBSA in a host PC, you can use Mark's tools to do so. 
It lets you download the kernel over the PCI bus and is what we used at
CMU.  Very good stuff...

-Jon

-----
     Subject: EBSA-285 as co-processor
     Date:  Wed, 30 Jun 1999 15:26:54 +0200
     From:  Mark van Doesburg <m.j.s.vandoesburg@student.utwente.nl>
     To:   linux-arm@vger.rutgers.edu
 
     I've finally been able to setup an ftp site for this. You can get
the
     data at ftp://nt4.el.utwente.nl/pub/co285 (and no, nt stands for
     networking theory)
 
     greetings,
 
     Mark.


Chris Bohme wrote:
> 
> Hi there,
> 
> maybe this is a silly question: how do you actually use Russell's
> bootloader for the ebsa285 ? Host bridge mode or add in mode ? From
> glancing through the source, hmmm ... keyboard events, so  do actually
> stick the card into a motherboard or a passive back plane ?
> 
> The actual question for those of you who got linux to work on the
> ebsa285: How did you get started ? (I'm really battling here....)
> 
> Tried to download kernel image via angelboot (as zImage and as AIF) but
> nothing is seen on the serial port and the LEDs are just dead.
> 
> Tried Russell's bios, but the card never gets as far as initializing
> either network or screen card (all 3 LEDs remain on).
> 
> Can anyone who is using the ebsa285 give me an idea how you got started
> ?
> 
> Thanks !
> 
> Chris
> 
> unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sun Oct  3 23:08:30 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id XAA02501
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sun, 3 Oct 1999 23:08:29 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id B2F65140BD; Mon,  4 Oct 1999 00:08:26 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156704AbPJCWIE>;
	Sun, 3 Oct 1999 18:08:04 -0400
Received: by vger.rutgers.edu id <S156703AbPJCWHp>;
	Sun, 3 Oct 1999 18:07:45 -0400
Received: from m32-nsv1-trogon.tch.cableol.net ([194.168.16.32]:2479 "EHLO
        caramon.armlinux.org.uk") by vger.rutgers.edu with ESMTP
	id <S156680AbPJCWHZ>; Sun, 3 Oct 1999 18:07:25 -0400
Received: from flint.armlinux.org.uk (root@flint [192.168.0.4])
	by caramon.armlinux.org.uk (8.8.7/8.8.7) with ESMTP id XAA05482;
	Sun, 3 Oct 1999 23:06:50 +0100
Received: (from linux@localhost)
	by flint.armlinux.org.uk (8.8.7/8.8.7) id XAA04077;
	Sun, 3 Oct 1999 23:05:27 +0100
From: Russell King - ARM Linux Admin <linux@arm.linux.org.uk>
Message-Id: <199910032205.XAA04077@flint.armlinux.org.uk>
Subject: Re: Russell's bios/bootloader (or booting the EBSA285)
To: cbo@nanoteq.co.za
Date:   Sun, 3 Oct 1999 23:05:27 +0100 (BST)
Cc: linux-arm@vger.rutgers.edu
In-Reply-To: <37F78360.5C3E48C2@craul.nanoteq.co.za> from "Chris Bohme" at Oct 3, 99 02:25:04 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Chris Bohme writes:
> maybe this is a silly question: how do you actually use Russell's
> bootloader for the ebsa285 ? Host bridge mode or add in mode ? From
> glancing through the source, hmmm ... keyboard events, so  do actually
> stick the card into a motherboard or a passive back plane ?

The bios will only use the keyboard if it finds it, otherwise it'll use
the serial port.

> The actual question for those of you who got linux to work on the
> ebsa285: How did you get started ? (I'm really battling here....)

You need to use the angel stuff to download the bios.  Preferably read
the makefile, and put it in the specified flash image location.  Then
twiddle the switch to that image number, and hit the reset button.

There are plans to allow it to download images via the serial port, and
directly from flash (but haven't materialised yet).
   _____
  |_____| ------------------------------------------------- ---+---+-
  |   |        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' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Mon Oct  4 12:06:21 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id MAA02305
	for <linux-arm-archive@lists.arm.linux.org.uk>; Mon, 4 Oct 1999 12:06:15 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id D09D4140AB; Mon,  4 Oct 1999 10:58:47 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157115AbPJDI5a>;
	Mon, 4 Oct 1999 04:57:30 -0400
Received: by vger.rutgers.edu id <S156683AbPJDI5V>;
	Mon, 4 Oct 1999 04:57:21 -0400
Received: from [194.201.77.34] ([194.201.77.34]:49116 "HELO
        fw-maid.maidenhead.arm.com") by vger.rutgers.edu with SMTP
	id <S157151AbPJDIyM>; Mon, 4 Oct 1999 04:54:12 -0400
Received: by fw-maid.maidenhead.arm.com; id KAA08525; Mon, 4 Oct 1999 10:54:44 +0100
Received: from unknown(192.168.2.10) by fw-maid.maidenhead.arm.com via smap (V5.0)
	id xma008517; Mon, 4 Oct 99 10:53:54 +0100
Received: from arm.com (dhcp14 [192.168.2.174])
	by mhsun1.maidenhead.arm.com (8.9.3/8.9.3) with ESMTP id JAA26436;
	Mon, 4 Oct 1999 09:52:54 +0100 (BST)
Message-ID: <37F86EC2.8FD8163E@arm.com>
Date:   Mon, 04 Oct 1999 10:09:23 +0100
From: David Rusling <david.rusling@arm.com>
X-Mailer: Mozilla 4.5 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Paul Koning <pkoning@xedia.com>
Cc: awiggins@cse.unsw.edu.au, linux-arm@vger.rutgers.edu
Subject: Re: (Off-topic) Real-Time kernels on ARM
References: <Pine.OSF.3.95.991001212534.25259A-100000@paulaner.disy.cse.unsw.EDU.AU> <199910012031.QAA03290@tonga.xedia.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

I would too.   Looking at it, it doesn't seem all that difficult to use the
Intel based stuff.    By the way, has anyone used the ROM FS with
ARM Linux yet - I'm playing with it now and it makes a lot of sense.

Dave

Paul Koning wrote:

> >>>>> "Wiggins" == Wiggins  <Adam> writes:
>
>  Wiggins> I'm after any references or design information for real time
>  Wiggins> kernels on top of the ARM.
>
> Several of us are interested in something like RTLinux ported to ARM.
> I haven't been able to do anything about this yet, unfortunately.
>
> I found some notes on an RTLinux for ARM effort, from Joshua Lamorie
> (jpl@xiphos.ca) and Eric LaForest (di458@freenet.carleton.ca).  That
> was about a year ago, I don't have newer status.
>
> Alex Holden (<alex_holden@geocities.com) also mentioned this sort of
> topic, though it sounds like the RTLinux approach doesn't fit his
> needs well.
>
>         paul
> unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

--
----------------------------------------------------------------------
David A Rusling   Consulting Engineer
    ARM Limited
    Liberty House,
    Moorbridge Road,
    Maidenhead, SL6 8LT

    Tel: UK-(0)1628-427754
    Fax: UK-(0)1628-780551
    e-mail: david.rusling@arm.com
----------------------------------------------------------------------


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Mon Oct  4 15:26:16 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id PAA08517
	for <linux-arm-archive@lists.arm.linux.org.uk>; Mon, 4 Oct 1999 15:26:15 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id D22D513E63; Mon,  4 Oct 1999 16:25:56 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156827AbPJDOYa>;
	Mon, 4 Oct 1999 10:24:30 -0400
Received: by vger.rutgers.edu id <S156968AbPJDOSa>;
	Mon, 4 Oct 1999 10:18:30 -0400
Received: from dfw7-1.relay.mail.uu.net ([199.171.54.106]:34871 "EHLO
        dfw7-1.relay.mail.uu.net") by vger.rutgers.edu with ESMTP
	id <S157120AbPJDOLf>; Mon, 4 Oct 1999 10:11:35 -0400
Received: from xedia.com by dfw7sosrv11.alter.net with SMTP 
	(peer crosschecked as: madway.xedia.com [198.202.232.199])
	id QQhjme25025;
	Mon, 4 Oct 1999 14:11:30 GMT
Received: from tonga.xedia.com by xedia.com (4.1/SMI-4.1)
	id AA26395; Mon, 4 Oct 99 10:09:44 EDT
Received: by tonga.xedia.com (SMI-8.6/SMI-SVR4)
	id KAA13849; Mon, 4 Oct 1999 10:11:28 -0400
Date:   Mon, 4 Oct 1999 10:11:28 -0400
Message-Id: <199910041411.KAA13849@tonga.xedia.com>
From: Paul Koning <pkoning@xedia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: awiggins@cse.unsw.EDU.AU
Cc: linux-arm@vger.rutgers.edu
Subject: Re: (Off-topic) Real-Time kernels on ARM
References: <199910012031.QAA03290@tonga.xedia.com>
	<Pine.OSF.3.95.991004034235.7227H-100000@paulaner.disy.cse.unsw.EDU.AU>
X-Mailer: VM 6.34 under 20.3 "Vatican City" XEmacs  Lucid
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

>>>>> "Wiggins" == Wiggins  <Adam> writes:

 Wiggins> On Fri, 1 Oct 1999, Paul Koning wrote:
 >> >>>>> "Wiggins" == Wiggins <Adam> writes:
 >> 
 Wiggins> I'm after any references or design information for real time
 Wiggins> kernels on top of the ARM.
 >>  Several of us are interested in something like RTLinux ported to
 >> ARM.  I haven't been able to do anything about this yet,
 >> unfortunately.
 >> 
 >> I found some notes on an RTLinux for ARM effort, from Joshua
 >> Lamorie (jpl@xiphos.ca) and Eric LaForest
 >> (di458@freenet.carleton.ca).  That was about a year ago, I don't
 >> have newer status.

 Wiggins> While RTLinux is a very interesting and worthwhile project
 Wiggins> it didn't help too much :( Beyound clarifying a few things
 Wiggins> and bringing about a few minor idea's its the wrong things
 Wiggins> for what I'm looking for.  Particularly the RT executive
 Wiggins> itself is not preemptable, the RT threads run in a single
 Wiggins> address space as well. These are the problems I'm looking to
 Wiggins> solve. I have some idea's but they still need
 Wiggins> formalising. Also no one seems to be interested in
 Wiggins> Microkernel development (due to asumptions about
 Wiggins> performance) which makes it hard to get feedback.

You might look at RTAI (Paolo Montegazza); as I recall it uses those
words.  I haven't looked at it, thought.  Don't know of any ARM
porting effort for that one.

As for being non-preemptable, in my mind that's a benefit, not a
drawback.  I know of real time systems that have failed due to relying 
on priority mechanisms and pre-emption.  If you design your system
without preemption and with a single priority level, you find yourself 
having to pay attention to guaranteeing that everything that must get
done, will get done.  That's the way you create reliable systems...

	paul

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Mon Oct  4 15:38:07 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id PAA08812
	for <linux-arm-archive@lists.arm.linux.org.uk>; Mon, 4 Oct 1999 15:38:06 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id B4A8B13DD4; Mon,  4 Oct 1999 16:38:04 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156688AbPJDOhb>;
	Mon, 4 Oct 1999 10:37:31 -0400
Received: by vger.rutgers.edu id <S156696AbPJDOhC>;
	Mon, 4 Oct 1999 10:37:02 -0400
Received: from note.orchestra.cse.unsw.EDU.AU ([129.94.242.29]:1191 "HELO
        note.orchestra.cse.unsw.EDU.AU") by vger.rutgers.edu with SMTP
	id <S156688AbPJDOgs>; Mon, 4 Oct 1999 10:36:48 -0400
Received: From paulaner With LocalMail ; Tue, 5 Oct 99 00:36:11 +1000 
From: "Adam 'WeirdArms' Wiggins" <awiggins@cse.unsw.EDU.AU>
To: Paul Koning <pkoning@xedia.com>
Date:   Tue, 5 Oct 1999 00:36:11 +1000 (EST)
X-Sender: awiggins@paulaner.disy.cse.unsw.EDU.AU
Cc: linux-arm@vger.rutgers.edu
Subject: Re: (Off-topic) Real-Time kernels on ARM
In-Reply-To: <199910041411.KAA13849@tonga.xedia.com>
Message-ID: <Pine.OSF.3.95.991005002020.14234A-100000@paulaner.disy.cse.unsw.EDU.AU>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

On Mon, 4 Oct 1999, Paul Koning wrote:

> 
>  Wiggins> While RTLinux is a very interesting and worthwhile project
>  Wiggins> it didn't help too much :( Beyound clarifying a few things
>  Wiggins> and bringing about a few minor idea's its the wrong things
>  Wiggins> for what I'm looking for.  Particularly the RT executive
>  Wiggins> itself is not preemptable, the RT threads run in a single
>  Wiggins> address space as well. These are the problems I'm looking to
>  Wiggins> solve. I have some idea's but they still need
>  Wiggins> formalising. Also no one seems to be interested in
>  Wiggins> Microkernel development (due to asumptions about
>  Wiggins> performance) which makes it hard to get feedback.
> 
> You might look at RTAI (Paolo Montegazza); as I recall it uses those
> words.  I haven't looked at it, thought.  Don't know of any ARM
> porting effort for that one.
> 
> As for being non-preemptable, in my mind that's a benefit, not a
> drawback.  I know of real time systems that have failed due to relying 
> on priority mechanisms and pre-emption.  If you design your system
> without preemption and with a single priority level, you find yourself 
> having to pay attention to guaranteeing that everything that must get
> done, will get done.  That's the way you create reliable systems...

	Priority is build into L4 it uses hard priority with round robin
on the same priority level. After thinking about the pre-emption issue
though I'm not sure its needed since the critical syscall IPC is about 1us
on a 100Mhz mips machine I hope to get something similar for the SA-1100.
a big problem though is address space context switches being expensive and
potentially interfering with RT tasks.

	Maybe its about time to move this discustion to another list or
private or does no one mind it being here?


	Cheers Adam

 > > paul > 

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Mon Oct  4 16:02:49 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id QAA09786
	for <linux-arm-archive@lists.arm.linux.org.uk>; Mon, 4 Oct 1999 16:02:48 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 387A313DDC; Mon,  4 Oct 1999 17:02:47 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156723AbPJDPCH>;
	Mon, 4 Oct 1999 11:02:07 -0400
Received: by vger.rutgers.edu id <S156721AbPJDPBv>;
	Mon, 4 Oct 1999 11:01:51 -0400
Received: from thorgal.et.tudelft.nl ([130.161.40.91]:17477 "EHLO
        thorgal.et.tudelft.nl") by vger.rutgers.edu with ESMTP
	id <S156723AbPJDPBZ>; Mon, 4 Oct 1999 11:01:25 -0400
Received: from [130.161.40.82] (tvs082.et.tudelft.nl [130.161.40.82])
	by thorgal.et.tudelft.nl (8.8.7/8.8.7) with ESMTP id RAA09936;
	Mon, 4 Oct 1999 17:01:12 +0200
Message-Id: <v03130307b41e70b5cd80@[130.161.40.82]>
In-Reply-To: 
        =?ISO-8859-1?Q?<Pine.OSF.3.95.991005002020.14234A-100000@paulaner.disy.cse.unsw.EDU.AU>=0DReferences:?=
 <199910041411.KAA13849@tonga.xedia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date:   Mon, 4 Oct 1999 17:00:17 +0200
To: "Adam 'WeirdArms' Wiggins" <awiggins@cse.unsw.EDU.AU>
From: "J.D. Bakker" <bakker@thorgal.et.tudelft.nl>
Subject: Re: (Off-topic) Real-Time kernels on ARM
Cc: linux-arm@vger.rutgers.edu
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

At 16:36 +0200 04-10-1999, Adam 'WeirdArms' Wiggins wrote:
>	Priority is build into L4 it uses hard priority with round robin
>on the same priority level. After thinking about the pre-emption issue
>though I'm not sure its needed since the critical syscall IPC is about 1us
>on a 100Mhz mips machine I hope to get something similar for the SA-1100.

For reference:

bash-2.01# ./lat_syscall null
Simple syscall: 0.6472 microseconds

This on a 220MHz SA-1100, kernel 2.2.12, with not-quite-tuned 60ns EDO
DRAM, using lat_syscall from lmbench. Surely L4 can beat that ;-)

JDB.

--
If you think the problem is bad now, just wait until we've solved it.
                                                     -- Arthur Kasspe


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Mon Oct  4 16:08:42 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id QAA09991
	for <linux-arm-archive@lists.arm.linux.org.uk>; Mon, 4 Oct 1999 16:08:42 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id F0E3713E4B; Mon,  4 Oct 1999 17:08:39 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156692AbPJDPHs>;
	Mon, 4 Oct 1999 11:07:48 -0400
Received: by vger.rutgers.edu id <S156683AbPJDPH2>;
	Mon, 4 Oct 1999 11:07:28 -0400
Received: from dfw7-1.relay.mail.uu.net ([199.171.54.106]:52629 "EHLO
        dfw7-1.relay.mail.uu.net") by vger.rutgers.edu with ESMTP
	id <S156820AbPJDPHI>; Mon, 4 Oct 1999 11:07:08 -0400
Received: from xedia.com by dfw7sosrv11.alter.net with SMTP 
	(peer crosschecked as: madway.xedia.com [198.202.232.199])
	id QQhjmi13291;
	Mon, 4 Oct 1999 15:07:00 GMT
Received: from tonga.xedia.com by xedia.com (4.1/SMI-4.1)
	id AA27552; Mon, 4 Oct 99 11:05:14 EDT
Received: by tonga.xedia.com (SMI-8.6/SMI-SVR4)
	id LAA14038; Mon, 4 Oct 1999 11:06:54 -0400
Date:   Mon, 4 Oct 1999 11:06:54 -0400
Message-Id: <199910041506.LAA14038@tonga.xedia.com>
From: Paul Koning <pkoning@xedia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: awiggins@cse.unsw.EDU.AU
Cc: linux-arm@vger.rutgers.edu
Subject: Re: (Off-topic) Real-Time kernels on ARM
References: <199910041411.KAA13849@tonga.xedia.com>
	<Pine.OSF.3.95.991005002020.14234A-100000@paulaner.disy.cse.unsw.EDU.AU>
X-Mailer: VM 6.34 under 20.3 "Vatican City" XEmacs  Lucid
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

>>>>> "Wiggins" == Wiggins  <Adam> writes:
 Wiggins> Priority is build into L4 it uses hard priority with round
 Wiggins> robin on the same priority level.

Sure, most RTOSs have priority.  That doesn't mean it should be used.
As I said, I know of some real world experiences that demonstrate why
it's dangerous to use priority.

That's not to say you should *never* use it.  I avoid it when
possible, which so far has been all the time.  I can imagine cases
where one or two tasks have such low latency requirements that they do 
need priority.  If so, use it, but be aware you're playing with fire.

 Wiggins> Maybe its about time to move this discustion to another list
 Wiggins> or private or does no one mind it being here?

It's been discussed some on the RTLinux list.  I could dig up some of
the archived stuff from there, and post it here, or offline, either
way.

	paul
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Mon Oct  4 17:37:35 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id RAA01743
	for <linux-arm-archive@lists.arm.linux.org.uk>; Mon, 4 Oct 1999 17:37:34 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id C0FC713E1C; Mon,  4 Oct 1999 17:52:31 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156961AbPJDPld>;
	Mon, 4 Oct 1999 11:41:33 -0400
Received: by vger.rutgers.edu id <S156827AbPJDPag>;
	Mon, 4 Oct 1999 11:30:36 -0400
Received: from note.orchestra.cse.unsw.EDU.AU ([129.94.242.29]:1307 "HELO
        note.orchestra.cse.unsw.EDU.AU") by vger.rutgers.edu with SMTP
	id <S156968AbPJDPWs>; Mon, 4 Oct 1999 11:22:48 -0400
Received: From paulaner With LocalMail ; Tue, 5 Oct 99 01:21:05 +1000 
From: "Adam 'WeirdArms' Wiggins" <awiggins@cse.unsw.EDU.AU>
To: "J.D. Bakker" <bakker@thorgal.et.tudelft.nl>
Date:   Tue, 5 Oct 1999 01:20:49 +1000 (EST)
X-Sender: awiggins@paulaner.disy.cse.unsw.EDU.AU
Cc: linux-arm@vger.rutgers.edu
Subject: Re: (Off-topic) Real-Time kernels on ARM
In-Reply-To: <v03130307b41e70b5cd80@130.161.40.82]>
Message-ID: <Pine.OSF.3.95.991005010914.15425A-100000@paulaner.disy.cse.unsw.EDU.AU>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

yOn Mon, 4 Oct 1999, J.D. Bakker wrote:

> At 16:36 +0200 04-10-1999, Adam 'WeirdArms' Wiggins wrote:
> >	Priority is build into L4 it uses hard priority with round robin
> >on the same priority level. After thinking about the pre-emption issue
> >though I'm not sure its needed since the critical syscall IPC is about 1us
> >on a 100Mhz mips machine I hope to get something similar for the SA-1100.
> 
> For reference:
> 
> bash-2.01# ./lat_syscall null
> Simple syscall: 0.6472 microseconds
>
	Whats it do? The L4 Null syscall (get_my_id) is much less then IPC
:)
 
> This on a 220MHz SA-1100, kernel 2.2.12, with not-quite-tuned 60ns EDO
> DRAM, using lat_syscall from lmbench. Surely L4 can beat that ;-)
> 
	Well on the MIPS 100Mhz single issue cpu its 1us for IPC which
transferes 8 dwords (64bit) of data. I hope to keep the same number of
instructio cycles so about 100 cycles at 200Mhz thats gives us 0.5us to
transfere 8 aarm registers of data or 8 words (32 bit). But I've yet to
get around to writting the IPC path.
	Anyone interested in helping is welcome to say so ;) The code is
GPL, just not released until I get IPC working (a month or so... I hope)


	Cheers Adam

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Mon Oct  4 17:37:43 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id RAA01754
	for <linux-arm-archive@lists.arm.linux.org.uk>; Mon, 4 Oct 1999 17:37:42 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 8F0EA13E45; Mon,  4 Oct 1999 17:53:37 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156701AbPJDPoD>;
	Mon, 4 Oct 1999 11:44:03 -0400
Received: by vger.rutgers.edu id <S156683AbPJDPf1>;
	Mon, 4 Oct 1999 11:35:27 -0400
Received: from note.orchestra.cse.unsw.EDU.AU ([129.94.242.29]:1319 "HELO
        note.orchestra.cse.unsw.EDU.AU") by vger.rutgers.edu with SMTP
	id <S156945AbPJDP0j>; Mon, 4 Oct 1999 11:26:39 -0400
Received: From paulaner With LocalMail ; Tue, 5 Oct 99 01:26:09 +1000 
From: "Adam 'WeirdArms' Wiggins" <awiggins@cse.unsw.EDU.AU>
To: Paul Koning <pkoning@xedia.com>
Date:   Tue, 5 Oct 1999 01:26:03 +1000 (EST)
X-Sender: awiggins@paulaner.disy.cse.unsw.EDU.AU
Cc: linux-arm@vger.rutgers.edu
Subject: Re: (Off-topic) Real-Time kernels on ARM
In-Reply-To: <199910041506.LAA14038@tonga.xedia.com>
Message-ID: <Pine.OSF.3.95.991005012131.15425B-100000@paulaner.disy.cse.unsw.EDU.AU>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

On Mon, 4 Oct 1999, Paul Koning wrote:

> >>>>> "Wiggins" == Wiggins  <Adam> writes:
>  Wiggins> Priority is build into L4 it uses hard priority with round
>  Wiggins> robin on the same priority level.
> 
> Sure, most RTOSs have priority.  That doesn't mean it should be used.
> As I said, I know of some real world experiences that demonstrate why
> it's dangerous to use priority.

	Sure within the real time component don't use it.. The thing is
the micro-kernel is supposed to be generic and be usable to impliment any
type of OS or applications. Howevver for real time it only make sense to
use a micro-kernel if you are going to have a non-real time component and
the two are securly issolated (cept for controled communication)

>  Wiggins> or private or does no one mind it being here?
> 
> It's been discussed some on the RTLinux list.  I could dig up some of
> the archived stuff from there, and post it here, or offline, either
> way.

	I would be inteerested in anything you can dig up just mail it to
me perosonaly or make it avaliable somewhere on the web.

	Cheers Adam

> 
> 	paul
> 

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Mon Oct  4 18:24:00 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id SAA03230
	for <linux-arm-archive@lists.arm.linux.org.uk>; Mon, 4 Oct 1999 18:24:00 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id E773B13DBB; Mon,  4 Oct 1999 19:23:46 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156696AbPJDRWg>;
	Mon, 4 Oct 1999 13:22:36 -0400
Received: by vger.rutgers.edu id <S156683AbPJDROw>;
	Mon, 4 Oct 1999 13:14:52 -0400
Received: from nexusel.demon.co.uk ([158.152.30.195]:19138 "EHLO
        globe.nexus.co.uk") by vger.rutgers.edu with ESMTP
	id <S156688AbPJDREW>; Mon, 4 Oct 1999 13:04:22 -0400
Received: from [192.0.0.21] (helo=fountain.nexus.co.uk ident=mail)
	by globe.nexus.co.uk with smtp (Exim 2.12 #1)
	id 11YBWK-0000uw-00; Mon, 4 Oct 1999 18:03:28 +0100
Received: from [127.0.0.1] (helo=fountain ident=pb)
	by fountain.nexus.co.uk with esmtp (Exim 3.03 #1)
	id 11YBWJ-0003tZ-00; Mon, 04 Oct 1999 18:03:27 +0100
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: "Adam 'WeirdArms' Wiggins" <awiggins@cse.unsw.EDU.AU>
Cc: "J.D. Bakker" <bakker@thorgal.et.tudelft.nl>, linux-arm@vger.rutgers.edu
Subject: Re: (Off-topic) Real-Time kernels on ARM 
In-Reply-To: Message from Adam 'WeirdArms' Wiggins <awiggins@cse.unsw.EDU.AU> 
   of "Tue, 05 Oct 1999 01:20:49 +1000." <Pine.OSF.3.95.991005010914.15425A-100000@paulaner.disy.cse.unsw.EDU.AU> 
References: <Pine.OSF.3.95.991005010914.15425A-100000@paulaner.disy.cse.unsw.EDU.AU> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date:   Mon, 04 Oct 1999 18:03:25 +0100
From: Philip Blundell <pb@nexus.co.uk>
Message-Id: <E11YBWJ-0003tZ-00@fountain.nexus.co.uk>
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

>> bash-2.01# ./lat_syscall null
>> Simple syscall: 0.6472 microseconds
>>
>	Whats it do? The L4 Null syscall (get_my_id) is much less then IPC
>:)

The lmbench `null' syscall is getpid() or something similar.  So it's pretty 
close to measuring the raw system call overhead.  On a NetWinder it's about 
0.48us, for interest's sake.

p.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Mon Oct  4 22:10:11 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id WAA10205
	for <linux-arm-archive@lists.arm.linux.org.uk>; Mon, 4 Oct 1999 22:10:10 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 480D213EDE; Mon,  4 Oct 1999 23:10:09 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156816AbPJDVJA>;
	Mon, 4 Oct 1999 17:09:00 -0400
Received: by vger.rutgers.edu id <S156692AbPJDVHV>;
	Mon, 4 Oct 1999 17:07:21 -0400
Received: from sparkle.Generation.NET ([205.205.119.4]:59718 "EHLO
        sparkle.Generation.NET") by vger.rutgers.edu with ESMTP
	id <S156832AbPJDVCv>; Mon, 4 Oct 1999 17:02:51 -0400
Received: from dual (generic253.197.205.205.IN-ADDR.ARPA [205.205.197.253] (may be forged))
	by sparkle.Generation.NET (8.9.3/8.9.3) with SMTP id RAA11496;
	Mon, 4 Oct 1999 17:02:22 -0400 (EDT)
From: Francois Desloges <fd@vipswitch.com>
To: chris@fluff.org, Philip Blundell <pb@nexus.co.uk>
Subject: Re: Toolchain guide
Date:   Mon, 4 Oct 1999 13:50:14 -0400
Content-Type: text/plain
References: <Pine.LNX.4.10.9910031204430.15828-100000@inkvine.fluff.org>
Cc: linux-arm@vger.rutgers.edu
MIME-Version: 1.0
Message-Id: <99100417005704.14871@dual>
Content-Transfer-Encoding: 8bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

On Sun, 03 Oct 1999, Chris Rutter wrote:
> I've finally had an overhaul and update of my toolchain guide; you
> can find the result, as ever, at:
> 
>   http://www.inkvine.fluff.org/~chris/arm-tools.html
> 
> Stuff like the inhibit_libc hack is now mentioned, along with some
> extra patches, and stuff.
> 
> One caveat: I just tried following through the whole document and
> got some build error in glibc re: threads, although according to
> the mailing list archives I think it should work.  I'll post more
> when Jenny hasn't got the PC in Windoze *grumble grumble*.
> 
> -- 
> Chris <chris@fluff.org>                         ( http://www.fluff.org/chris )

I've read the new guide and am very enthusiastic about it.  Just before it was
released, on friday, I succeeded at building a complete ToolChain, I'm _very_
newbie, which would explain how lost I felt in the middle of gcc & glibc
configure and makefile structure nightmare. But well, I finally did it, so I
think the following can be useful.

Here is therefore a condensed version (the new guide does most of the job) of my
experience on an Intel dual Celeron based Linux system (running Mandrake 6.1
with pgcc).

The crossplatform toolchain I succeeded to built from scratch is based on:
-linux-2.2.10  (I've heard of 2.2.12 working)
-binutils-2.9.5.0.13 (the latest at this time)
-gcc-2.95.1
-glibc-2.1.2

I chose target = arm-linux, PREFIX=/usr, TARGET-PREFIX=/usr/arm-linux

BINUTILS:
Binutils building went exactly as specified by the new (and old) guide.  As
specified by Philip, no patch need to be added to the 2.9.5 binutils, 
especially not the 2.9.1 ones.

GCC:
The kernel header I used are from linux-2.2.10, though later version probably
work (I've heard of 2.2.12 working). 
I applied patch 2.2.10-rmk3 from Russel. The latest 2.2.10 patches from Philip
are to be applied against 2.2.10-rmk2 and some of them has been included in
rmk3. So I haven't included any Philip's patches. 

In the old version, the guide suggests to:
# cp -a /usr/src/linux-2.2.10/include/asm-arm /usr/arm-linux/include/asm 
# cp -a /usr/src/linux-2.2.10/include/linux /usr/arm-linux/include/linux 
while in the new version, it suggests to:
# cp -dR /usr/src/linux-2.2.10/include/asm-arm /usr/arm-linux/include/asm 
# cp -dR /usr/src/linux-2.2.10/include/linux /usr/arm-linux/include/linux 
Why does it suggests cp. Wouldn't symlink do the job?

As is suggested in the new guide, I did: 
-Used gcc-2.95.1 sources from egcs.cygnus.com mirrors, 
-Applied 2.95-diff-990730 patch from ftp://ftp.netwinder.org/users/p/philb/,
-Changed #if 0 to #if 1 in gcc/config/arm/linux-elf.h (for binutils-2.9.5.x)
-Applied by hand the patch sent by Philip to gcc/fold-const.c (for the kernel)
-In order to avoid the fact that libgcc2.c build cannot find stdlib.h, I had to:
------- 
Edit gcc/config/arm/t-linux and add "-Dinhibit_libc" and
"-D__gthr_posix_h" to TARGET_LIBGCC2_CFLAGS
Delete #include "gthr.h" in libgcc2.c
Add the "--disable-threads" option to configure
-------
This last patch has bad consequences as specified by Philip B:
>The generated libraries will not be threadsafe.  This will bite you if, for
>example, you have a multithreaded C++ program that uses exceptions.

However, this problem can be fixed. Once glibc has succesfully been built,
all you have to do is rebuild gcc again whitout these corrections (you don't
need to recompile glibc a second time however). I will cover that later.

While doing the ./configure, I noted the host type, as suggested at Step 7. of
Intel note http://developer.intel.com/design/strong/applnots/sa1100lx/egcs_c.htm
The host type is given in the first output lines of ./configure, looking like:
configuring for a i686-pc-linux-gnu host
This (i686-pc-linux-gnu or whatever configure give you as host type) will be
used as --build argument when configuring glibc, later.

Chris corrected the erronous "cd gcc" before the make and make install statement
and that is good, since it avoid the famous libiberty/libiberty.a Error.

However I've found this from Chris and Philip on the Mailing List
On Sat, 02 Oct 1999, Philip Blundell wrote:
> >> Don't do that, then - just configure and make at the top level.  The gcc 
> >> subdirectory depends on other things such as libiberty that need to be built
> >> first.
> >
> >What happens to all the bits of the compiler that depend on libc?
> >Presumably it's impossible to reach a working `make install' target
> >unless you inhibt make from considering these?  Is `make LANGUAGES="c"'
> >at the top level the correct way of doing this?
> 
> I don't think that will work.  What you have to do is `make' at the top level, 
> wait for it to crash, then `make install' in the gcc subdirectory.
> 
> p.

I have the feeling that this _may_ be more complicated. The first time I tried
building my toolchian I did exactly this:
[/usr/src/gcc-2.95.1] #./configure --target=arm-linux --prefix=/usr --disable-threads                            
[/usr/src/gcc-2.95.1] #make LANGUAGES="c"

Very late in the build process (at the linking stage I think) it generated the
famous libio Error:

make[1]: Leaving directory `/usr/src/gcc-2.95.1/gcc'
Configuring in arm-linux/libiberty
COPYING.LIB                        ..linked
ChangeLog                            ..linked
Makefile                              ..linked
Makefile.in                        ..linked
README                  ..linked
acconfig.h                          ..linked
...
A lot more linked modules from a to z...
...
xxstrdup.o                            ..linked
xstrerror.c                        ..linked
xstrerror.o                        ..linked
make[1]: Entering directory `/usr/src/gcc-2.95.1/arm-linux/libiberty'
make[2]: Entering directory `/usr/src/gcc-2.95.1/arm-linux/libiberty/testsuite' rm -f test-us.c test-filter
make[2]: Leaving directory `/usr/src/gcc-2.95.1/arm-linux/libiberty/testsuite'
rm -rf *.o pic core errs \#* *.E a.out
rm -f needed.awk needed2.awk errors dummy needed-list config.h stamp-*
rm -f    stamp-picdir
make[2]: Entering directory `/usr/src/gcc-2.95.1/arm-linux/libiberty/testsuite'rm -f test-us.c test-filter
make[2]: Leaving directory `/usr/src/gcc-2.95.1/arm-linux/libiberty/testsuite'
rm -f *.a required-list tmpmulti.out
make[2]: Entering directory `/usr/src/gcc-2.95.1/arm-linux/libiberty/testsuite' rm -f test-us.c test-filter
rm -f Makefile
make[2]: Leaving directory `/usr/src/gcc-2.95.1/arm-linux/libiberty/testsuite'
rm -f *~ Makefile config.status xhost-mkfrag TAGS multilib.out
rm -f config.log
make[1]: Leaving directory `/usr/src/gcc-2.95.1/arm-linux/libiberty'
loading cache ./config.cache
checking host system type... arm-unknown-linux-gnu
checking build system type... i686-pc-linux-gnu
checking for arm-linux-ar... arm-linux-ar
checking for arm-linux-ranlib... arm-linux-ranlib
checking for gcc... /usr/src/gcc-2.95.1/gcc/xgcc -B/usr/src/gcc-2.95.1/gcc/ -B/u
sr/arm-linux/bin/
checking whether we are using GNU C... yes
checking whether /usr/src/gcc-2.95.1/gcc/xgcc -B/usr/src/gcc-2.95.1/gcc/ -B/usr/
arm-linux/bin/ accepts -g... yes
checking for POSIXized ISC... no
checking for a BSD compatible install... /usr/bin/install -c
checking how to run the C preprocessor... /lib/cpp
checking for sys/file.h... yes
checking for sys/param.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for unistd.h... yes
checking for strings.h... yes
checking for sys/time.h... yes
checking whether the C compiler (/usr/src/gcc-2.95.1/gcc/xgcc -B/usr/src/gcc-2.9
5.1/gcc/ -B/usr/arm-linux/bin/ -g -O2 ) works... no
configure: error: installation or configuration problem: C comipler cannot
create executables.
make[1]: Entering directory `/usr/src/gcc-2.95.1/arm-linux/libio'
if [ x"no" = xyes ] && [ ! -d pic ]; then \
  mkdir pic; \
else true; fi
touch stamp-picdir
test x"no" != xyes ||\
  /usr/src/gcc-2.95.1/gcc/xgcc -B/usr/src/gcc-2.95.1/gcc/ -B/usr/arm-linux/bin/
-c -g -O2 -I. -I. -D_IO_MTSAFE_IO  iogetline.c -o pic/iogetline.o
/usr/src/gcc-2.95.1/gcc/xgcc -B/usr/src/gcc-2.95.1/gcc/ -B/usr/arm-linux/bin/ -c -g -O2 -I. -I. -D_IO_MTSAFE_IO iogetline.c
In file included from iogetline.c:26:
libioP.h:30: errno.h: No such file or directory                                                                
In file included from iolibio.h:1,
                                from libioP.h:47,
                                from iogetline.c:26:
libio.h:30: _G_config.h: No such file or directory
iogetline.c:27: string.h: No such file or directory
make[1]: *** [iogetline.o] Error 1
make[1]: Leaving directory `/usr/src/gcc-2.95.1/arm-linux/libio'
make: *** [all-target-libio] Error 2 

So following Philip B suggestion, I just did
[/usr/src/gcc-2.95.1] #make LANGUAGES="c" install
Everything got installed, and I moved to glibc.

I have, as explained bellow, reasons to believe that this is wrong (but I cannot
explain it since I just have _NO_ idea what is happening here ;-().

Anyway I _feel_ you should redo:
[/usr/src/gcc-2.95.1] #make LANGUAGES="c"
[/usr/src/gcc-2.95.1] #make LANGUAGES="c" install
again to make sure everything got build completely before moving to glibc. I
didn't do it the first time and I ran in the ld.so.map Error in building glibc.
More later.

GLIBC:
I used:
glibc-2.1.2.tar.bz2      
glibc-linuxthreads-2.1.2.tar.bz2
glibc-crypt-2.0.111.tar.gz

As told in binutils-2.9.5.0.12 release note, found at
ftp://ftp.varesearch.com:/pub/support/hjl/binutils/release.binutils-2.9.5.0.12:
>
>For arm-linux targets, there are some important differences in behaviour 
>between these tools and binutils 2.9.1.0.x.  The linker emulation name has 
>changed from elf32arm{26} to armelf_linux{26}.  Also, the "-p" flag must be 
>passed with the linker when working with object files (or static libraries) 
>created using older versions of the assembler.  If this flag is omitted the 
>linker will silently generate bad output when given old input files.
>
>To get the correct behaviour from gcc, amend the *link section of your specs 
>file as follows:
>
>*link:
>%{h*} %{version:-v}      %{b} %{Wl,*:%*}      %{static:-Bstatic}    
>%{shared:-shared }      %{symbolic:-Bsymbolic}      %{rdynamic:-export-dynamic}    
>%{!dynamic-linker: -dynamic-linker /lib/ld-linux.so.2}      -X    
>%{mbig-endian:-EB} %{mapcs-26:-m armelf_linux26}
>%{!mapcs-26:-m armelf_linux} -p
>
The refered specs file is /usr/lib/gcc-lib/arm-linux/2.95.1/specs.
I add nothing to modify, although I know many had to permform the changes

So I did
# CC=linux-arm-gcc
# ./configure arm-linux --build=i686-pc-linux-gnu --prefix=/usr/arm-linux --enable-add-ons
# make 

Note that the --build option is the host type I got from gcc configure not
i586-linux as suggested.

The first time, I then hit the infamous ld.so.map Error, in the late building
phase of glibc. That was _BAD_ since I was just _begining_ to learn the syntax
of bash, makefile, sed awk (very newbie, said I)
Nobody had fixed that problem before, Philip thought it could be a problem
with awk, refered me to the alpha mailing-list. I previously was fool enough to
assign only 1 week of works on my tight schedule for building the toolchain.
That had already slipped to 3 weeks, and I couldn't imagine how I would
become a makefile expert quick enough (this gcc and glibc configure/makefile is
really a nightmare for a newbie) to fix this without losing a month or so. 

That's when Nicolas Pitre sent me that little E-Mail that brought me
hope. He actually succeeded at building a gcc-2.95.1/glibc2.1.2 toolchain. 
After a few days of Makefile darkness, I just decided to restart everything from
scratch.

When after a few hours of building binutils and patching/building gcc, I
hit the gcc libio Error, I just said to my self: "Hey! could that incomplete
gcc build be the reason why glibc fail later?" So after instaling gcc I did:
make clean, configure, make and make install again. Everyting went well. On the
second make it didn't complained about libio Error.

So I started building glibc and it went through! No more ld.so.map Error! (I've
just _no_ idea why: Trust your feeling Luke ;-)
Then, I installed glibc. It went well.

I even went back to gcc-2.95.1 and rebuild it without the corrections:
------ 
Edit gcc/config/arm/t-linux and add "-Dinhibit_libc" and
"-D__gthr_posix_h" to TARGET_LIBGCC2_CFLAGS
Delete #include "gthr.h" in libgcc2.c
Add the "--disable-threads" option to configure
-------
in order for gcc to generate thread safe code. That went well.

At that moment, I thought: Can I reproduce the original ld.so.map Error in
glibc? (So that this will confirm or not my "double gcc make" hypothesis)
So I erase the complete content of /usr/src and /usr/arm-linux, and did the
entire process again without double compiling gcc-2.95.1.  But, there is
probably something else installed somewhere that I didn't erase,  because "make
LANGUAGES="c"" went succesfully through without the libio Error on the first
attempt. And glibc was successful as well on first attempt. So I wasn't able to
invalidate my "double gcc make" hypothesis.

The only other difference I can remember (I took precise notes) between the
first, 3-weeks-long toolchain build, that resulted in a ld.so.map Error and the
second succesful one, is that I used --with-cpu=strongarm110
as a gcc ./configure argument the second time, that I didn't use the first
time. But I didn't verify this. (Complete toolchain build takes a lot of time)

If I'm right on this one (I hope Philip can confirm this), one would have to
build gcc 3 times in order to have a completely foncionnal toolchain:
-Build/install binutils
-Patch/Build/install gcc
-Build/install gcc again
-Build/install glibc
-Build/install gcc a third time without the -Dinhibit_libc corrections. 

Am I totally wrong here or what ?
 --
François Desloges
fd@vipswitch.com
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Mon Oct  4 23:00:50 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id XAA12454
	for <linux-arm-archive@lists.arm.linux.org.uk>; Mon, 4 Oct 1999 23:00:49 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 8D27A13E51; Tue,  5 Oct 1999 00:00:44 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156696AbPJDWAO>;
	Mon, 4 Oct 1999 18:00:14 -0400
Received: by vger.rutgers.edu id <S156683AbPJDWAK>;
	Mon, 4 Oct 1999 18:00:10 -0400
Received: from duteinh.et.tudelft.nl ([130.161.42.1]:3755 "HELO
        duteinh.et.tudelft.nl") by vger.rutgers.edu with SMTP
	id <S156817AbPJDV7j>; Mon, 4 Oct 1999 17:59:39 -0400
Received: from dutein71 (dutein71.et.tudelft.nl) by duteinh.et.tudelft.nl (4.1/BB-2.0)
	id AA03047; Mon, 4 Oct 99 23:58:04 +0200
Date:   Mon, 4 Oct 99 23:58:03 +0200
Message-Id: <9910042158.AA03047@duteinh.et.tudelft.nl>
From: Erik Mouw <J.A.K.Mouw@its.tudelft.nl>
To: sa1100-linux@pa.dec.com, linux-arm@vger.rutgers.edu
Subject: Announce: blob-1.0.0, a bootloader for SA1100 based systems
Organization: Eric conspiracy secret labs
X-Face: "!Z|1XjFg!3Iw)BwM^M\k)J5KHiPddz}#/Zw%?$&Q!xqob"OA|})3_@&BTTiQERo?/^g[Z<9P4R8:5C:aqq.cw!hotLc=+u-"+1rq@9$V^8PbOUlodyi_sejt+D`iqkLpx$>.aXl%vnfPIt"LK|/%>94_Zrm8jy?`_[RKt'TuoxUxfk(gMhY(n|DBBl~c$dhO>G%6}R4+DGX3|idBm4oU&UM/XUP4I9aoN{]`ax%B?rgD(I3OJ<62Y6L
X-Mailer: XCmail 0.99.6 - with PGP support, PGP engine version 0.5
X-Mailerorigin: http://www.fsai.fh-trier.de/~schmitzj/Xclasses/XCmail/
X-Eric-Conspiracy: There is no conspiracy!
X-Loop: erik@it.et.tudelft.nl
Mime-Version: 1.0
Content-Type: 	text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Hi all,

I'd like to announce the first release of blob, a bootloader for SA1100
based systems. From the README file:

  ** What is blob?
  ----------------

  Blob is the Boot Loader OBject, the boot loader for the LART. Blob is
  able to boot a Linux kernel stored in flash or RAM and provide that
  kernel with a ramdisk (again from flash or RAM).

  Blob is copyrighted by Jan-Derk Bakker (J.D.Bakker@its.tudelft.nl) and
  Erik Mouw (J.A.K.Mouw@its.tudelft.nl). Blob is released with a GNU GPL
  license.


  ** So what is LART?
  -------------------

  LART is the Linux Advanced Radio Terminal, a small low power computing
  element used in the MMC project (http://mmc.et.tudelft.nl/ and
  http://www-ict.its.tudelft.nl/~erik/open-source/LART/).


  ** Commands
  -----------

  Blob knows several commands, typing "help" (without the ") will show
  you which:

    Help for blob 1.0.0, the LART bootloader
    The following commands are supported:
    * boot [kernel options]      Boot Linux with optional kernel options
    * download {kernel|ramdisk}  Download kernel or ramdisk image to RAM
    * flash {kernel|ramdisk}     Copy kernel or ramdisk from RAM to flash
    * help                       Get this help
    * reload {kernel|ramdisk}    Reload kernel or ramdisk from flash to RAM
    * reset                      Reset terminal
    * speed                      Set download speed
    * status                     Display current status


Blob is distributed with a GNU GPL license and can be downloaded from
http://www-ict.its.tudelft.nl/~erik/open-source/blob/ (sorry, no nifty
webpage yet).


Erik

-- 
J.A.K. (Erik) Mouw, Information and Communication Theory Group, Department
of Electrical Engineering, Faculty of Information Technology and Systems,
Delft University of Technology, PO BOX 5031,  2600 GA Delft, The Netherlands
Phone: +31-15-2785859  Fax: +31-15-2781843  Email J.A.K.Mouw@its.tudelft.nl
WWW: http://www-ict.its.tudelft.nl/~erik/


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Tue Oct  5 00:05:30 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id AAA14667
	for <linux-arm-archive@lists.arm.linux.org.uk>; Tue, 5 Oct 1999 00:05:29 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 509A013EDB; Tue,  5 Oct 1999 01:05:26 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157017AbPJDXBt>;
	Mon, 4 Oct 1999 19:01:49 -0400
Received: by vger.rutgers.edu id <S156897AbPJDW5G>;
	Mon, 4 Oct 1999 18:57:06 -0400
Received: from neon-best.transmeta.com ([206.184.214.10]:4263 "EHLO
        neon.transmeta.com") by vger.rutgers.edu with ESMTP
	id <S156996AbPJDW4j>; Mon, 4 Oct 1999 18:56:39 -0400
Received: from deepthought.transmeta.com (mailhost.transmeta.com [10.1.1.15])
	by neon.transmeta.com (8.9.1/8.9.1) with ESMTP id PAA13404
	for <linux-arm@vger.rutgers.edu>; Mon, 4 Oct 1999 15:55:44 -0700
Received: from palladium.transmeta.com (root@palladium.transmeta.com [10.1.1.46])
	by deepthought.transmeta.com (8.8.8+spamcan/8.8.5) with ESMTP id PAA16484
	for <linux-arm@vger.rutgers.edu>; Mon, 4 Oct 1999 15:55:44 -0700 (PDT)
Received: (from bin@localhost)
	by palladium.transmeta.com (8.8.5/8.8.5) id PAA05171
	for linux-arm@vger.rutgers.edu; Mon, 4 Oct 1999 15:55:43 -0700
X-Authentication-Warning: palladium.transmeta.com: bin set sender to news@transmeta.com using -f
To: linux-arm@vger.rutgers.edu
From: hpa@transmeta.com (H. Peter Anvin)
Subject: ELF and ARM
Date:   4 Oct 1999 22:55:42 GMT
Organization: Transmeta Corporation, Santa Clara CA
Message-ID: <7tbb9e$51e$1@palladium.transmeta.com>
Reply-To: hpa@transmeta.com (H. Peter Anvin)
Mime-Version: 1.0
Content-Type: 	text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Disclaimer: Not speaking for Transmeta in any way, shape, or form.
Copyright: Copyright 1999 H. Peter Anvin - All Rights Reserved
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Hello everybody,

Sorry for ask something that's at least semi-off-topic, but I would
like to ask what the situation is regarding ELF on ARM.  I do remember
a long time ago something about a discussion that there was no
definition for ARM ELF; is that still the case, or are the current
snags elsewhere?  All I know is that binutils 2.9.1 doesn't seem to
support ARM ELF -- if there is work that needs to be done in this are,
perhaps I could lend a hand, but I'd like to know the current status
:)

Many thanks,

	-hpa
-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Tue Oct  5 01:05:33 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id BAA16352
	for <linux-arm-archive@lists.arm.linux.org.uk>; Tue, 5 Oct 1999 01:05:33 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 4B7F413E58; Tue,  5 Oct 1999 02:05:14 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156965AbPJEAEx>;
	Mon, 4 Oct 1999 20:04:53 -0400
Received: by vger.rutgers.edu id <S157052AbPJEAEi>;
	Mon, 4 Oct 1999 20:04:38 -0400
Received: from [212.219.8.163] ([212.219.8.163]:1684 "HELO inkvine.fluff.org")
	by vger.rutgers.edu with SMTP id <S156945AbPJEAEP>;
	Mon, 4 Oct 1999 20:04:15 -0400
Received: from localhost (localhost [127.0.0.1])
	by inkvine.fluff.org (Postfix) with ESMTP
	id 0EFDB46842; Tue,  5 Oct 1999 01:04:00 +0100 (BST)
Date:   Tue, 5 Oct 1999 01:04:00 +0100 (BST)
From: Chris Rutter <chris@fluff.org>
Reply-To: chris@fluff.org
To: "H. Peter Anvin" <hpa@transmeta.com>
Cc: linux-arm@vger.rutgers.edu
Subject: Re: ELF and ARM
In-Reply-To: <7tbb9e$51e$1@palladium.transmeta.com>
Message-ID: <Pine.LNX.4.10.9910050100430.12229-100000@inkvine.fluff.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

On 4 Oct 1999, H. Peter Anvin wrote:

> Sorry for ask something that's at least semi-off-topic, but I would
> like to ask what the situation is regarding ELF on ARM.  I do remember

I couldn't tell you in great technical detail, but the primary
binary format in use on the ARM is definitely now ELF; it's been
workable for about 1--2 years now, I think.

> support ARM ELF -- if there is work that needs to be done in this are,

Oh, no, 2.9.1 definitely supports ELF -- configure for an "arm-linux"
target.

(You really want to ask Phil Blundell, but I'm sure he'll reply
to your post. :)

-- 
Chris <chris@fluff.org>                         ( http://www.fluff.org/chris )

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Tue Oct  5 03:35:55 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id DAA20603
	for <linux-arm-archive@lists.arm.linux.org.uk>; Tue, 5 Oct 1999 03:35:54 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id B964013E97; Tue,  5 Oct 1999 04:35:47 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156728AbPJECfZ>;
	Mon, 4 Oct 1999 22:35:25 -0400
Received: by vger.rutgers.edu id <S156827AbPJECfQ>;
	Mon, 4 Oct 1999 22:35:16 -0400
Received: from law2-f126.hotmail.com ([216.32.181.126]:4849 "HELO hotmail.com")
	by vger.rutgers.edu with SMTP id <S156721AbPJECfH>;
	Mon, 4 Oct 1999 22:35:07 -0400
Received: (qmail 99335 invoked by uid 0); 5 Oct 1999 02:34:56 -0000
Message-ID: <19991005023456.99334.qmail@hotmail.com>
Received: from 130.65.157.236 by www.hotmail.com with HTTP;
	Mon, 04 Oct 1999 19:34:56 PDT
X-Originating-IP: [130.65.157.236]
From: "John_Justin_Ray _" <latenitesolution@hotmail.com>
To: Sa1100-linux@pa.dec.com
Cc: Devel@netwinder.com, Linux-arm@vger.rutgers.edu
Subject: RAMDISK image
Date:   Mon, 04 Oct 1999 19:34:56 PDT
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Our group would like to know where we can obtain a RAMdisk image or creating 
a RAMdisk image for the Sa1100 board using the Strongarm chip.  The link in:

http://developer.intel.com/design/strong/applnots/sa1100lx/download.htm#1001846

which is: ftp://ssdl-redstone.stanford.edu/pub/ramdisk.gz

is broken.

______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Tue Oct  5 09:26:09 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id JAA31190
	for <linux-arm-archive@lists.arm.linux.org.uk>; Tue, 5 Oct 1999 09:26:09 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 0901513F35; Tue,  5 Oct 1999 10:25:40 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156692AbPJEIYh>;
	Tue, 5 Oct 1999 04:24:37 -0400
Received: by vger.rutgers.edu id <S156920AbPJEIXF>;
	Tue, 5 Oct 1999 04:23:05 -0400
Received: from studict.student.utwente.nl ([130.89.220.2]:3580 "EHLO
        studict.student.utwente.nl") by vger.rutgers.edu with ESMTP
	id <S157163AbPJEINz>; Tue, 5 Oct 1999 04:13:55 -0400
Received: from poekie.test (ut125204.inbel.utwente.nl [130.89.125.204])
          by studict.student.utwente.nl (8.8.6/MQT) with ESMTP id KAA03601;
          Tue, 5 Oct 1999 10:13:45 +0200 (METDST)
Received: (from mark@localhost)
	by poekie.test (8.9.1/8.9.1) id BAA26576;
	Mon, 4 Oct 1999 01:48:36 +0200
Date:   Mon, 4 Oct 1999 01:48:36 +0200
From: Mark van Doesburg <mark@nt4.el.utwente.nl>
Message-Id: <199910032348.BAA26576@poekie.test>
To: jon@quackware.com, linux-arm@vger.rutgers.edu
Subject: Re: Russell's bios/bootloader (or booting the EBSA285)
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

	If you have the EBSA in a host PC, you can use Mark's tools to
	do so. It lets you download the kernel over the PCI bus and is
	what we used at CMU.  Very good stuff...

Well, not that good. Russell's boot loader autodetects the SDRAM size. I
want to add that to my own boot loader when I have the time :-)

greetings,

Mark.
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Tue Oct  5 09:26:57 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id JAA31274
	for <linux-arm-archive@lists.arm.linux.org.uk>; Tue, 5 Oct 1999 09:26:52 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id A742313DE0; Tue,  5 Oct 1999 10:26:38 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156807AbPJEIZv>;
	Tue, 5 Oct 1999 04:25:51 -0400
Received: by vger.rutgers.edu id <S156771AbPJEIYp>;
	Tue, 5 Oct 1999 04:24:45 -0400
Received: from nexusel.demon.co.uk ([158.152.30.195]:19372 "EHLO
        globe.nexus.co.uk") by vger.rutgers.edu with ESMTP
	id <S156807AbPJEIXC>; Tue, 5 Oct 1999 04:23:02 -0400
Received: from [192.0.0.21] (helo=fountain.nexus.co.uk ident=mail)
	by globe.nexus.co.uk with smtp (Exim 2.12 #1)
	id 11YPrC-0001SA-00; Tue, 5 Oct 1999 09:21:58 +0100
Received: from [127.0.0.1] (helo=fountain ident=pb)
	by fountain.nexus.co.uk with esmtp (Exim 3.03 #1)
	id 11YPrC-0008LB-00; Tue, 05 Oct 1999 09:21:58 +0100
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: hpa@transmeta.com (H. Peter Anvin)
Cc: linux-arm@vger.rutgers.edu
Subject: Re: ELF and ARM 
In-Reply-To: Message from hpa@transmeta.com (H. Peter Anvin) 
   of "04 Oct 1999 22:55:42 GMT." <7tbb9e$51e$1@palladium.transmeta.com> 
References: <7tbb9e$51e$1@palladium.transmeta.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date:   Tue, 05 Oct 1999 09:21:58 +0100
From: Philip Blundell <pb@nexus.co.uk>
Message-Id: <E11YPrC-0008LB-00@fountain.nexus.co.uk>
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

>a long time ago something about a discussion that there was no
>definition for ARM ELF; is that still the case, or are the current
>snags elsewhere?

There are no snags I know of -- use binutils 2.9.5 and all should be well.  
You can download the appropriate specifications from the ARM web site if 
you want them.

p.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Tue Oct  5 16:35:22 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id QAA02721
	for <linux-arm-archive@lists.arm.linux.org.uk>; Tue, 5 Oct 1999 16:35:21 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 3DB6413FD1; Tue,  5 Oct 1999 17:35:19 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157306AbPJEP06>;
	Tue, 5 Oct 1999 11:26:58 -0400
Received: by vger.rutgers.edu id <S156736AbPJEPUh>;
	Tue, 5 Oct 1999 11:20:37 -0400
Received: from [194.201.77.34] ([194.201.77.34]:56765 "HELO
        fw-maid.maidenhead.arm.com") by vger.rutgers.edu with SMTP
	id <S157175AbPJEPE0>; Tue, 5 Oct 1999 11:04:26 -0400
Received: by fw-maid.maidenhead.arm.com; id RAA12115; Tue, 5 Oct 1999 17:04:54 +0100
Received: from unknown(192.168.2.10) by fw-maid.maidenhead.arm.com via smap (V5.0)
	id xma012113; Tue, 5 Oct 99 17:04:08 +0100
Received: from arm.com (dhcp14 [192.168.2.174])
	by mhsun1.maidenhead.arm.com (8.9.3/8.9.3) with ESMTP id QAA28197
	for <linux-arm@vger.rutgers.edu>; Tue, 5 Oct 1999 16:03:13 +0100 (BST)
Message-ID: <37FA1715.95C48D23@arm.com>
Date:   Tue, 05 Oct 1999 16:19:49 +0100
From: David Rusling <david.rusling@arm.com>
X-Mailer: Mozilla 4.5 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: linux-arm@vger.rutgers.edu
Subject: init process/program
References: <199910032348.BAA26576@poekie.test>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

I'm fiddling about with a PCI based ARM system (Integrator, it's
just gone on sale).   I'm booting a system with a ROMFS sat in flash
(with a simple device driver that can find the file system in flash and
read it's blocks).

I'm using init/inittab etc to start up the system.  Unfortunately, init
wants to create files and my file system is read only (very read only).
So, for example, it cannot create /dev/initctl and it gets upset.  I'm
also seeing some shared library wierdnesses and so I've moved to
a staticly  built image.  Oh, and the serial driver is half written.

OK, the question.   Is there a brain dead easy init that I can use to
get the system off its knees.  I guess the answer is to use a command
shell, but I'd like a more viable longer term solution.   Long term I'd
like to boot a system that uses a RAM disk for the writable files (eg
log files etc).

Any help appreciated.

Dave

ps PCI subsystem looks very good, it can find/recognise SCSI disks
and their partitions as well as a 21x4x ethernet device...
----------------------------------------------------------------------
David A Rusling   Consulting Engineer
    ARM Limited
    Liberty House,
    Moorbridge Road,
    Maidenhead, SL6 8LT

    Tel: UK-(0)1628-427754
    Fax: UK-(0)1628-780551
    e-mail: david.rusling@arm.com
----------------------------------------------------------------------


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Tue Oct  5 17:29:46 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id RAA04179
	for <linux-arm-archive@lists.arm.linux.org.uk>; Tue, 5 Oct 1999 17:29:45 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 8355014064; Tue,  5 Oct 1999 18:29:42 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156740AbPJEQZB>;
	Tue, 5 Oct 1999 12:25:01 -0400
Received: by vger.rutgers.edu id <S156725AbPJEQUU>;
	Tue, 5 Oct 1999 12:20:20 -0400
Received: from mail-gw3.pacbell.net ([206.13.28.55]:50911 "EHLO
        mail-gw3.pacbell.net") by vger.rutgers.edu with ESMTP
	id <S156818AbPJEQQm>; Tue, 5 Oct 1999 12:16:42 -0400
Received: from java (adsl-216-101-151-82.dsl.snfc21.pacbell.net [216.101.151.82])
	by mail-gw3.pacbell.net (8.9.3/8.9.3) with SMTP id JAA05181;
	Tue, 5 Oct 1999 09:15:31 -0700 (PDT)
Message-ID: <008001bf0f4e$429a08c0$529765d8@java>
From: "Dave Borja" <dave_bb@pacbell.net>
To: "Adam 'WeirdArms' Wiggins" <awiggins@cse.unsw.EDU.AU>,
        "Paul Koning" <pkoning@xedia.com>
Cc: <linux-arm@vger.rutgers.edu>
Subject: Re: (Off-topic) Real-Time kernels on ARM
Date:   Tue, 5 Oct 1999 09:25:00 -0700
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.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing



>
> Maybe its about time to move this discustion to another list or
>private or does no one mind it being here?
>
>
> Cheers Adam
>
> > > paul > 
>
No, no...please continue- The stuff is facinating and useful even
if a lot of us aren't doing that stuff right now.

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Tue Oct  5 18:18:16 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id SAA06153
	for <linux-arm-archive@lists.arm.linux.org.uk>; Tue, 5 Oct 1999 18:18:16 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 37DF013D90; Tue,  5 Oct 1999 19:17:55 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156882AbPJERPn>;
	Tue, 5 Oct 1999 13:15:43 -0400
Received: by vger.rutgers.edu id <S156703AbPJERJD>;
	Tue, 5 Oct 1999 13:09:03 -0400
Received: from tazenda.demon.co.uk ([158.152.220.239]:1458 "EHLO
        kings-cross.london.uk.eu.org") by vger.rutgers.edu with ESMTP
	id <S156838AbPJERGz>; Tue, 5 Oct 1999 13:06:55 -0400
Received: from localhost
	([127.0.0.1] helo=kings-cross.london.uk.eu.org ident=phil)
	by kings-cross.london.uk.eu.org with esmtp (Exim 2.05 #1)
	id 11YY32-0003f4-00; Tue, 5 Oct 1999 18:06:44 +0100
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: David Rusling <david.rusling@arm.com>
Cc: linux-arm@vger.rutgers.edu
Subject: Re: init process/program 
In-Reply-To: Message from David Rusling <david.rusling@arm.com> 
   of "Tue, 05 Oct 1999 16:19:49 BST." <37FA1715.95C48D23@arm.com> 
References: <199910032348.BAA26576@poekie.test>  <37FA1715.95C48D23@arm.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date:   Tue, 05 Oct 1999 18:06:44 +0100
From: Philip Blundell <Philip.Blundell@pobox.com>
Message-Id: <E11YY32-0003f4-00@kings-cross.london.uk.eu.org>
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

>I'm using init/inittab etc to start up the system.  Unfortunately, init
>wants to create files and my file system is read only (very read only).
>So, for example, it cannot create /dev/initctl and it gets upset.  I'm
>also seeing some shared library wierdnesses and so I've moved to
>a staticly  built image.  Oh, and the serial driver is half written.
>
>OK, the question.   Is there a brain dead easy init that I can use to
>get the system off its knees.  I guess the answer is to use a command

Sounds like your best bet is to get the source to sysvinit and chop out the 
bits you don't want.  What sort of problem did you have with shared libraries?

p.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Tue Oct  5 20:24:10 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id UAA14917
	for <linux-arm-archive@lists.arm.linux.org.uk>; Tue, 5 Oct 1999 20:24:10 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 8068E13E82; Tue,  5 Oct 1999 21:24:07 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156723AbPJETXh>;
	Tue, 5 Oct 1999 15:23:37 -0400
Received: by vger.rutgers.edu id <S156873AbPJETXX>;
	Tue, 5 Oct 1999 15:23:23 -0400
Received: from mail-gw3.pacbell.net ([206.13.28.55]:51155 "EHLO
        mail-gw3.pacbell.net") by vger.rutgers.edu with ESMTP
	id <S156876AbPJETRW>; Tue, 5 Oct 1999 15:17:22 -0400
Received: from java (adsl-216-101-151-82.dsl.snfc21.pacbell.net [216.101.151.82])
	by mail-gw3.pacbell.net (8.9.3/8.9.3) with SMTP id MAA25346;
	Tue, 5 Oct 1999 12:16:52 -0700 (PDT)
Message-ID: <019501bf0f67$8bebae70$529765d8@java>
From: "Dave Borja" <dave_bb@pacbell.net>
To: "John_Justin_Ray _" <latenitesolution@hotmail.com>
Cc: <linux-arm@vger.rutgers.edu>
Subject: Re: RAMDISK image
Date:   Tue, 5 Oct 1999 12:25:56 -0700
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.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Yes, that link is either down or no longer works. I ran into the same
problem. Fortunely,  Ian Field <ianfield@pobox.com> was very kind in giving
me access
to something he had put together. He pointed me to:

http://216.100.248.143/~ian/projects/arm-zone/files/

Download it and unzip it.
-----Original Message-----
From: John_Justin_Ray _ <latenitesolution@hotmail.com>
To: Sa1100-linux@pa.dec.com <Sa1100-linux@pa.dec.com>
Cc: Devel@netwinder.com <Devel@netwinder.com>; Linux-arm@vger.rutgers.edu
<Linux-arm@vger.rutgers.edu>
Date: Monday, October 04, 1999 7:36 PM
Subject: RAMDISK image


>Our group would like to know where we can obtain a RAMdisk image or
creating
>a RAMdisk image for the Sa1100 board using the Strongarm chip.  The link
in:
>
>http://developer.intel.com/design/strong/applnots/sa1100lx/download.htm#100
1846
>
>which is: ftp://ssdl-redstone.stanford.edu/pub/ramdisk.gz
>
>is broken.
>
>______________________________________________________
>Get Your Private, Free Email at http://www.hotmail.com
>unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu
>

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Tue Oct  5 21:11:00 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id VAA16317
	for <linux-arm-archive@lists.arm.linux.org.uk>; Tue, 5 Oct 1999 21:10:59 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 3851113ECB; Tue,  5 Oct 1999 22:10:47 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156688AbPJEUJt>;
	Tue, 5 Oct 1999 16:09:49 -0400
Received: by vger.rutgers.edu id <S156719AbPJEUJe>;
	Tue, 5 Oct 1999 16:09:34 -0400
Received: from mail-gw3.pacbell.net ([206.13.28.55]:60298 "EHLO
        mail-gw3.pacbell.net") by vger.rutgers.edu with ESMTP
	id <S156873AbPJEUGn>; Tue, 5 Oct 1999 16:06:43 -0400
Received: from java (adsl-216-101-151-82.dsl.snfc21.pacbell.net [216.101.151.82])
	by mail-gw3.pacbell.net (8.9.3/8.9.3) with SMTP id NAA16138
	for <linux-arm@vger.rutgers.edu>; Tue, 5 Oct 1999 13:06:41 -0700 (PDT)
Message-ID: <01e201bf0f6e$76f8f6b0$529765d8@java>
From: "Dave Borja" <dave_bb@pacbell.net>
To: "linux-arm" <linux-arm@vger.rutgers.edu>
Subject: 
Date:   Tue, 5 Oct 1999 13:16:10 -0700
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.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

I posted (under the Tony Xu id) a description of compiling and
downloading for the brutus boad a few days ago.  We get
things to download (using agnelboot) but nothing happens,
no response or indication on our serial port 2 (j22 connector)
console. I was wondering how to proceed when this happens.
Is there any way to use the ARM v2.11a debugger to help
here?  I suppose we should go back and check.recheck our
kernal build procedure (we are doing this as best we can with
the knowledge we have) and also our angelboot configuration
and serial port connections, etc. But is there any hints out there
at what we should look at or a way to get an indication of how
we messed up? Thanks,
  Dave Borja
  MMT Corp

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Wed Oct  6 10:55:21 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id KAA16269
	for <linux-arm-archive@lists.arm.linux.org.uk>; Wed, 6 Oct 1999 10:55:21 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id EAB8C13E4E; Wed,  6 Oct 1999 11:55:19 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156732AbPJFJy3>;
	Wed, 6 Oct 1999 05:54:29 -0400
Received: by vger.rutgers.edu id <S156725AbPJFJyT>;
	Wed, 6 Oct 1999 05:54:19 -0400
Received: from apsn05.zeneca.com ([193.132.159.6]:52280 "EHLO
        apsn05.zeneca.com") by vger.rutgers.edu with ESMTP
	id <S156771AbPJFJsX>; Wed, 6 Oct 1999 05:48:23 -0400
Received: from apsn15.ukap.zeneca.com by apsn05.zeneca.com (SMI-8.6/SMI-SVR4)
	id KAA07342; Wed, 6 Oct 1999 10:48:21 +0100
Received: by apsn15.ukap.zeneca.com; id KAA14030; Wed, 6 Oct 1999 10:44:31 +0100
Received: by ukapzcmsxhub01.ukap.zeneca.com with Internet Mail Service (5.5.2448.0)
	id <4CXSXAZW>; Wed, 6 Oct 1999 10:44:31 +0100
Message-ID: <01E7A94C7AD7D011995C00805FFE4DC00291E837@UKAPPHDEVMSX04>
From: Aubury Mike M <Mike.Aubury@astrazeneca.com>
To: "'linux-arm@vger.rutgers.edu'" <linux-arm@vger.rutgers.edu>
Subject: Cirrus Logic evaluation boards
Date:   Wed, 6 Oct 1999 10:44:28 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Have any ports been done to any of the cirrus logic arm evaluation boards ?

I've been trying to get linux installed on an ebd7111-2 but with absolutly
no success (maybe its just angel 1.4 being a devil).

Any pointers would be appreciated.

TIA

Mike Aubury
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Wed Oct  6 12:14:56 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id MAA21716
	for <linux-arm-archive@lists.arm.linux.org.uk>; Wed, 6 Oct 1999 12:14:50 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 21A2114130; Wed,  6 Oct 1999 13:14:49 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156725AbPJFLOI>;
	Wed, 6 Oct 1999 07:14:08 -0400
Received: by vger.rutgers.edu id <S156730AbPJFLOF>;
	Wed, 6 Oct 1999 07:14:05 -0400
Received: from nexusel.demon.co.uk ([158.152.30.195]:22588 "EHLO
        globe.nexus.co.uk") by vger.rutgers.edu with ESMTP
	id <S156719AbPJFLLC>; Wed, 6 Oct 1999 07:11:02 -0400
Received: from [192.0.0.21] (helo=fountain.nexus.co.uk ident=mail)
	by globe.nexus.co.uk with smtp (Exim 2.12 #1)
	id 11YoxY-0002sx-00; Wed, 6 Oct 1999 12:10:12 +0100
Received: from [127.0.0.1] (helo=fountain ident=pb)
	by fountain.nexus.co.uk with esmtp (Exim 3.03 #1)
	id 11YoxX-0001OI-00; Wed, 06 Oct 1999 12:10:11 +0100
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: Aubury Mike M <Mike.Aubury@astrazeneca.com>
Cc: "'linux-arm@vger.rutgers.edu'" <linux-arm@vger.rutgers.edu>
Subject: Re: Cirrus Logic evaluation boards 
In-Reply-To: Message from Aubury Mike M <Mike.Aubury@astrazeneca.com> 
   of "Wed, 06 Oct 1999 10:44:28 BST." <01E7A94C7AD7D011995C00805FFE4DC00291E837@UKAPPHDEVMSX04> 
References: <01E7A94C7AD7D011995C00805FFE4DC00291E837@UKAPPHDEVMSX04> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date:   Wed, 06 Oct 1999 12:10:10 +0100
From: Philip Blundell <pb@nexus.co.uk>
Message-Id: <E11YoxX-0001OI-00@fountain.nexus.co.uk>
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

>Have any ports been done to any of the cirrus logic arm evaluation boards ?

The 7500 port, including the startup code you were asking about, is included 
in the latest patches at <ftp://ftp.netwinder.org/users/p/philb/kernel>.

p.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Wed Oct  6 14:43:38 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id OAA26352
	for <linux-arm-archive@lists.arm.linux.org.uk>; Wed, 6 Oct 1999 14:43:37 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 83F0013F59; Wed,  6 Oct 1999 15:43:26 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156804AbPJFNm4>;
	Wed, 6 Oct 1999 09:42:56 -0400
Received: by vger.rutgers.edu id <S156743AbPJFNlu>;
	Wed, 6 Oct 1999 09:41:50 -0400
Received: from sparkle.Generation.NET ([205.205.119.4]:34192 "EHLO
        sparkle.Generation.NET") by vger.rutgers.edu with ESMTP
	id <S156923AbPJFNa6>; Wed, 6 Oct 1999 09:30:58 -0400
Received: from dual (generic253.197.205.205.IN-ADDR.ARPA [205.205.197.253] (may be forged))
	by sparkle.Generation.NET (8.9.3/8.9.3) with SMTP id JAA03265
	for <linux-arm@vger.rutgers.edu>; Wed, 6 Oct 1999 09:31:09 -0400 (EDT)
From: Francois Desloges <fd@vipswitch.com>
To: linux-arm@vger.rutgers.edu
Subject: More kernel options questions
Date:   Tue, 5 Oct 1999 14:03:07 -0400
Content-Type: text/plain
MIME-Version: 1.0
Message-Id: <99100609294405.14871@dual>
Content-Transfer-Encoding: 8bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

3 quick questions:

Any body knows if the Unix 98 PTYs, and the associated /dev/pts
filesystems, are reported to be well tested/used on ARM-Linux ?

There's a recommended hard drive for EBSA+Promise Ultra33 IDE, somewhere on
http://www.arm.uk.linux.org. From drivers point of view aren't all hard drive
using ide/UltraDMA the same? Why would I stick with a specific brand of HD?

On Thu, 09 Sep 1999, Philip Blundell wrote:
> >Do you have a patch somewhere that contains all changes required
> >for a 2.2.x RK kernel to be compiled with gcc 2.95?  
> 
> Not an especially up-to-date one at the moment.  There is some stuff in
> <ftp://ftp.netwinder.org/users/p/philb/kernel/> that does contain the changes 
> but it may be a little old by now.  I will try to find time to generate a new 
> patch soon, though my latest 2.2 kernels seem to be acting up a bit at the 
> moment.
> 
> p.
Which versions of 2.2.x kernel are reported to be buildable with gcc-2.95.1?
 --
François Desloges
fd@vipswitch.com
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Wed Oct  6 23:19:46 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id XAA17306
	for <linux-arm-archive@lists.arm.linux.org.uk>; Wed, 6 Oct 1999 23:19:45 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 0AF0A141D5; Thu,  7 Oct 1999 00:19:30 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157126AbPJFWDx>;
	Wed, 6 Oct 1999 18:03:53 -0400
Received: by vger.rutgers.edu id <S156839AbPJFV6D>;
	Wed, 6 Oct 1999 17:58:03 -0400
Received: from tazenda.demon.co.uk ([158.152.220.239]:1642 "EHLO
        kings-cross.london.uk.eu.org") by vger.rutgers.edu with ESMTP
	id <S156873AbPJFVfU>; Wed, 6 Oct 1999 17:35:20 -0400
Received: from localhost
	([127.0.0.1] helo=kings-cross.london.uk.eu.org ident=phil)
	by kings-cross.london.uk.eu.org with esmtp (Exim 2.05 #1)
	id 11Yyhd-00057P-00; Wed, 6 Oct 1999 22:34:25 +0100
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: Francois Desloges <fd@vipswitch.com>
Cc: linux-arm@vger.rutgers.edu
Subject: Re: More kernel options questions 
In-Reply-To: Message from Francois Desloges <fd@vipswitch.com> 
   of "Tue, 05 Oct 1999 14:03:07 EDT." <99100609294405.14871@dual> 
References: <99100609294405.14871@dual> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date:   Wed, 06 Oct 1999 22:34:25 +0100
From: Philip Blundell <Philip.Blundell@pobox.com>
Message-Id: <E11Yyhd-00057P-00@kings-cross.london.uk.eu.org>
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

>Any body knows if the Unix 98 PTYs, and the associated /dev/pts
>filesystems, are reported to be well tested/used on ARM-Linux ?

I use them every day with no problems.

>From drivers point of view aren't all hard drive using ide/UltraDMA the 
>same? Why would I stick with a specific brand of HD?

Aside from bugs, yes they are all pretty much the same.  I guess the reason 
for sticking with one is just because it's known to work.

p.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Wed Oct  6 23:58:58 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id XAA18650
	for <linux-arm-archive@lists.arm.linux.org.uk>; Wed, 6 Oct 1999 23:58:57 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id AF54E141CE; Thu,  7 Oct 1999 00:58:55 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156976AbPJFWlk>;
	Wed, 6 Oct 1999 18:41:40 -0400
Received: by vger.rutgers.edu id <S156809AbPJFWEs>;
	Wed, 6 Oct 1999 18:04:48 -0400
Received: from m10-nsv1-trogon.tch.cableol.net ([194.168.16.10]:4407 "EHLO
        caramon.armlinux.org.uk") by vger.rutgers.edu with ESMTP
	id <S156868AbPJFWAX>; Wed, 6 Oct 1999 18:00:23 -0400
Received: from raistlin.armlinux.org.uk (linux@raistlin [192.168.0.3])
	by caramon.armlinux.org.uk (8.8.7/8.8.7) with ESMTP id WAA19628;
	Wed, 6 Oct 1999 22:59:56 +0100
From: linux@arm.linux.org.uk
Received: (from linux@localhost) by raistlin.armlinux.org.uk (8.7.4/8.7.3) id WAA23440; Wed, 6 Oct 1999 22:58:27 +0100
Message-Id: <199910062158.WAA23440@raistlin.armlinux.org.uk>
Subject: Re: More kernel options questions
To: fd@vipswitch.com (Francois Desloges)
Date:   Wed, 6 Oct 1999 22:58:25 +0100 (BST)
Cc: linux-arm@vger.rutgers.edu
In-Reply-To: <99100609294405.14871@dual> from "Francois Desloges" at Oct 5, 99 02:03:07 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Francois Desloges writes:
> Any body knows if the Unix 98 PTYs, and the associated /dev/pts
> filesystems, are reported to be well tested/used on ARM-Linux ?

I think Rebel.com may be using them in their latest disk images.

> There's a recommended hard drive for EBSA+Promise Ultra33 IDE,
> somewhere on http://www.arm.uk.linux.org. From drivers point of
> view aren't all hard drive using ide/UltraDMA the same? Why
> would I stick with a specific brand of HD?

I don't see any recommendations of hard drive types on my web site.
The only possibility is in one GIF image of my EBSA285, and the
other one is on the benchmark page.  Neither of these are a
recommendation - it's the hardware I have which seems to work ok.
   _____
  |_____| ------------------------------------------------- ---+---+-
  |   |        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' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Thu Oct  7 08:29:29 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id IAA00965
	for <linux-arm-archive@lists.arm.linux.org.uk>; Thu, 7 Oct 1999 08:29:29 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 2EDB413DDA; Thu,  7 Oct 1999 09:26:55 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156747AbPJGH0S>;
	Thu, 7 Oct 1999 03:26:18 -0400
Received: by vger.rutgers.edu id <S156745AbPJGH0A>;
	Thu, 7 Oct 1999 03:26:00 -0400
Received: from ns0.utdallas.edu ([129.110.10.1]:44584 "HELO ns0.utdallas.edu")
	by vger.rutgers.edu with SMTP id <S156723AbPJGHZu>;
	Thu, 7 Oct 1999 03:25:50 -0400
Received: from apache.utdallas.edu (apache.utdallas.edu [129.110.16.9])
	by ns0.utdallas.edu (Postfix) with ESMTP id A0C0119FFC6
	for <linux-arm@vger.rutgers.edu>; Thu,  7 Oct 1999 02:25:49 -0500 (CDT)
Received: from localhost (vasantr@localhost)
	by apache.utdallas.edu (8.9.1/8.9.1) with SMTP id CAA05056
	for <linux-arm@vger.rutgers.edu>; Thu, 7 Oct 1999 02:25:58 -0500 (CDT)
X-Authentication-Warning: apache.utdallas.edu: vasantr owned process doing -bs
Date:   Thu, 7 Oct 1999 02:25:58 -0500 (CDT)
From: Vasant Ramasubramanian <vasantr@utdallas.edu>
To: linux-arm@vger.rutgers.edu
Subject: Brutus Woes, any help?
In-Reply-To: <01e201bf0f6e$76f8f6b0$529765d8@java>
Message-ID: <Pine.GSO.3.96.991007021944.4840A-100000@apache.utdallas.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Hello all!

I'm trying to setup my Brutus board to run the basic test programs that
come with the Kit (requires the SDT 2.50 to run, which I have) and I am
not even sure that my Brutus is working. From all the documentation I've
read (what little is provided) connecting the null-modem cable to J23 on
the Brutus and to a COM port on the PC should at least bring up a message
about Angel running on Brutus, right?

I used 9600,8,N,1 and 115200,8.N,1 for the serial port settings yet when I
turned Brutus on, I didn't get anything. I'm certain the PC is fine, the
serial port is fine, the null modem cable is fine, I've checked those
things out. I also made sure all the dip swtiches were in the default
position specified in the .pdf documentation for Brutus. Any ideas?

I haven't gotten to using angelboot.tgz or putting my RAM DISK on there or
anything like that.

For the ARM SDT 2.5 portion, I was using Win95 OSR2.

I'm running Red Hat 6.0 for the Linux end of things, hopefully if my
Brutus is working I can get it to boot Linux...

I'd appreciate any help/suggestions.

Thanks, Vasant.

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Thu Oct  7 16:29:46 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id QAA25312
	for <linux-arm-archive@lists.arm.linux.org.uk>; Thu, 7 Oct 1999 16:29:46 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id A3EF113F70; Thu,  7 Oct 1999 17:29:29 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157042AbPJGPVr>;
	Thu, 7 Oct 1999 11:21:47 -0400
Received: by vger.rutgers.edu id <S156919AbPJGPHC>;
	Thu, 7 Oct 1999 11:07:02 -0400
Received: from sparkle.Generation.NET ([205.205.119.4]:54122 "EHLO
        sparkle.Generation.NET") by vger.rutgers.edu with ESMTP
	id <S157158AbPJGOkD>; Thu, 7 Oct 1999 10:40:03 -0400
Received: from dual (generic253.197.205.205.IN-ADDR.ARPA [205.205.197.253] (may be forged))
	by sparkle.Generation.NET (8.9.3/8.9.3) with SMTP id KAA29705
	for <linux-arm@vger.rutgers.edu>; Thu, 7 Oct 1999 10:40:11 -0400 (EDT)
From: Francois Desloges <fd@vipswitch.com>
To: linux-arm@vger.rutgers.edu
Subject: Fwd: Re: More kernel options questions
Date:   Thu, 7 Oct 1999 10:37:58 -0400
Content-Type: text/plain
MIME-Version: 1.0
Message-Id: <99100710384907.14871@dual>
Content-Transfer-Encoding: 8bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

On Wed, 06 Oct 1999, linux@arm.linux.org.uk wrote:
> Francois Desloges writes:
> > There's a recommended hard drive for EBSA+Promise Ultra33 IDE,
> > somewhere on http://www.arm.uk.linux.org. From drivers point of
> > view aren't all hard drive using ide/UltraDMA the same? Why
> > would I stick with a specific brand of HD?
> 
> I don't see any recommendations of hard drive types on my web site.
> The only possibility is in one GIF image of my EBSA285, and the
> other one is on the benchmark page.  Neither of these are a
> recommendation - it's the hardware I have which seems to work ok.

Sorry for the confusion, here. I now remember where I've found the
"recommended" HD. It was in the bios-1.05 README:

>Bios for EBSA-285
>-----------------
...
>Supported devices
>-----------------
>
>Currently, bios has been tested with:
>
>- 3com 3c59x network card
>- S3 Trio64V2+ VGA card
>- Promise UDMA IDE card
>   (Only tested on a Seagate ST35651A UDMA2 drive)

Of course the drive is not "recommended", but there's enough variable parameter
in this project for my mind to convert points that seem solid in recommended
ones ;-) What would have been the appropriate term "known to work"?  My english
may just not be good enough. I'll do better next time.

And, yes, I meant HD brand, not interface, 'cause I tought all ide HD were
supposed to use the same ide driver whitout problem. That's the reason for my
question.

Thanks for the answer ! 
--
François Desloges
fd@vipswitch.com
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Thu Oct  7 17:37:56 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id RAA29055
	for <linux-arm-archive@lists.arm.linux.org.uk>; Thu, 7 Oct 1999 17:37:55 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 27CB313F76; Thu,  7 Oct 1999 18:37:05 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157231AbPJGQYP>;
	Thu, 7 Oct 1999 12:24:15 -0400
Received: by vger.rutgers.edu id <S156988AbPJGQKo>;
	Thu, 7 Oct 1999 12:10:44 -0400
Received: from mail-gw5.pacbell.net ([206.13.28.23]:43114 "EHLO
        mail-gw5.pacbell.net") by vger.rutgers.edu with ESMTP
	id <S157275AbPJGPgP>; Thu, 7 Oct 1999 11:36:15 -0400
Received: from java (adsl-216-101-151-82.dsl.snfc21.pacbell.net [216.101.151.82])
	by mail-gw5.pacbell.net (8.9.3/8.9.3) with SMTP id IAA00496
	for <linux-arm@vger.rutgers.edu>; Thu, 7 Oct 1999 08:36:11 -0700 (PDT)
Message-ID: <003701bf10db$02b28780$529765d8@java>
From: "Dave Borja" <dave_bb@pacbell.net>
To: <linux-arm@vger.rutgers.edu>
Subject: Re: Brutus Woes, any help?
Date:   Thu, 7 Oct 1999 08:45:39 -0700
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.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

This setup you describe-- right now you are just trying
to talk to it via ADK ARM debug? We got that far,
using ARM 2.11a sdk on a windows 98 box.. 
We had a similar problem with 
no response from angel  and switched all the baudrate
settings to 9600. Now we can run the test apps.

Or we could. The brutus board seems to taken a
hike south. The numeric LED is showing a 7 now
everytime we power up and we can't make a connection
to it either with the debugger SDK or angleboot on linux.

Anyone seen the 7? It's not documented anyplace that I can
find.
  Thanks,
 Dave
-----Original Message-----
From: Vasant Ramasubramanian <vasantr@utdallas.edu>
To: linux-arm@vger.rutgers.edu <linux-arm@vger.rutgers.edu>
Date: Thursday, October 07, 1999 12:27 AM
Subject: Brutus Woes, any help?


>Hello all!
>
>I'm trying to setup my Brutus board to run the basic test programs that
>come with the Kit (requires the SDT 2.50 to run, which I have) and I am
>not even sure that my Brutus is working. From all the documentation I've
>read (what little is provided) connecting the null-modem cable to J23 on
>the Brutus and to a COM port on the PC should at least bring up a message
>about Angel running on Brutus, right?
>
>I used 9600,8,N,1 and 115200,8.N,1 for the serial port settings yet when I
>turned Brutus on, I didn't get anything. I'm certain the PC is fine, the
>serial port is fine, the null modem cable is fine, I've checked those
>things out. I also made sure all the dip swtiches were in the default
>position specified in the .pdf documentation for Brutus. Any ideas?
>
>I haven't gotten to using angelboot.tgz or putting my RAM DISK on there or
>anything like that.
>
>For the ARM SDT 2.5 portion, I was using Win95 OSR2.
>
>I'm running Red Hat 6.0 for the Linux end of things, hopefully if my
>Brutus is working I can get it to boot Linux...
>
>I'd appreciate any help/suggestions.
>
>Thanks, Vasant.
>
>unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu
>

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Thu Oct  7 17:59:05 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id RAA30417
	for <linux-arm-archive@lists.arm.linux.org.uk>; Thu, 7 Oct 1999 17:59:04 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 9A5B813F28; Thu,  7 Oct 1999 18:59:03 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156773AbPJGQvu>;
	Thu, 7 Oct 1999 12:51:50 -0400
Received: by vger.rutgers.edu id <S156942AbPJGQvk>;
	Thu, 7 Oct 1999 12:51:40 -0400
Received: from sparkle.Generation.NET ([205.205.119.4]:60021 "EHLO
        sparkle.Generation.NET") by vger.rutgers.edu with ESMTP
	id <S156763AbPJGQlF>; Thu, 7 Oct 1999 12:41:05 -0400
Received: from dual (generic253.197.205.205.IN-ADDR.ARPA [205.205.197.253] (may be forged))
	by sparkle.Generation.NET (8.9.3/8.9.3) with SMTP id MAA07219
	for <linux-arm@vger.rutgers.edu>; Thu, 7 Oct 1999 12:41:14 -0400 (EDT)
From: Francois Desloges <fd@vipswitch.com>
To: linux-arm@vger.rutgers.edu
Subject: Errors Building ARM-Linux-2.2.10 with gcc-2.95.1
Date:   Wed, 6 Oct 1999 11:12:47 -0400
Content-Type: text/plain
MIME-Version: 1.0
Message-Id: <99100712395208.14871@dual>
Content-Transfer-Encoding: 8bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Building Linux-2.2.10 with patch-2.2.10-rmk3

"make zImage", in /usr/src/linux/arch/arm/lib, trying to create constant.h with:
perl extractconstants.pl /usr/arm-linux/bin/objdump > constants.h
gives me:
sh: /usr/arm-linux/bin/objdump: No such file or directory
which in turn of course fail to buil cheksum.o from checksum.S.

The binary objdump from binutils 2.9.5.0.13 has only been installed as
/usr/bin/arm-linux-objdump not as /usr/arm-linux/bin/objdump.
I've created a /usr/arm-linux/bin/objdump symlink that points to 
/usr/bin/arm-linux-objdump, which seems to work.
Is that right?

The next Error I hit was building arch/arm/kernel/kernel.o.  It read:

>/usr/arm-linux/bin/ld  -r -o kernel.o armksyms.o leds-footbridge.o dma.o
>hw-foot bridge.o entry-armv.o irq.o process.o ptrace.o setup.o signal.o
>sys_arm.o time.o  traps.o ioport.o dma-footbridge.o  isa.o dec21285.o
>/usr/arm-linux/bin/ld: cannot open ioport.o: No such file or directory
>make[1]: *** [kernel.o] Error 1
>make[1]: Leaving directory `/usr/src/linux-2.2.10/arch/arm/kernel'
>make: *** [_dir_arch/arm/kernel] Error 2

The arch/arm/kernel directory has no ioport.c file (there is one in
each arch/{i386, sparc,mips,sparc64}/kernel.
So I change arch/arm/kernel/Makefile that read:
>O_TARGET := kernel.o
>O_OBJS   := $(ENTRY_OBJ) irq.o process.o ptrace.o setup.o \
>	    signal.o sys_arm.o time.o traps.o ioport.o
by erasing ioport.o. That seemed to work.
Is that right?
Would this be destroyed by a new 'make dep' as told in the Makefile header?

The next error I met was:
>make[1]: Leaving directory `/usr/src/linux-2.2.10/arch/arm/nwfpe'
>/usr/arm-linux/bin/ld -T /usr/src/linux/arch/arm/vmlinux-armv.lds -e stext
>-Ttext 0xC0008000 arch/arm/kernel/head-armv.o arch/arm/kernel/init_task.o
>init/main.o init/version.o \ --start-group \ arch/arm/kernel/kernel.o
>arch/arm/mm/mm.o kernel/kernel.o mm/mm.o fs/fs.o ipc/ipc.o \ fs/filesystems.a \
>net/network.a \
>drivers/block/block.a drivers/char/char.a drivers/misc/misc.a drivers/net/net.a
>drivers/pci/pci.a arch/arm/special/special.a arch/arm/nwfpe/math-emu.a \
>arch/arm/lib/lib.a /usr/src/linux/lib/lib.a `/usr/arm-linux/bin/gcc
>-D__KERNEL__ -I/usr/src/linux/include  -mapcs-32 -mshort-load-bytes
>-mcpu=strongarm110 --print-libgcc-file-name` \         --end-group \         -o
>vmlinux /usr/arm-linux/bin/ld: target elf32-arm not found
>make: *** [vmlinux] Error 1                                                  

I know that elf32-arm should be armelf_linux.  I've already made the changes
in /usr/lib/gcc-lib/arm-linux/2.95.1/specs as required by
release.binutils-2.9.5.0.12 (although I thought this was only for glibc?)

Where (if I'm guessing right) are the variables to change, or what else should I
do?

Thank you all so much
--
François Desloges
fd@vipswitch.com
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Thu Oct  7 18:31:28 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id SAA32278
	for <linux-arm-archive@lists.arm.linux.org.uk>; Thu, 7 Oct 1999 18:31:27 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id CED3513DD5; Thu,  7 Oct 1999 19:31:25 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157259AbPJGRYk>;
	Thu, 7 Oct 1999 13:24:40 -0400
Received: by vger.rutgers.edu id <S156878AbPJGQ73>;
	Thu, 7 Oct 1999 12:59:29 -0400
Received: from sparkle.Generation.NET ([205.205.119.4]:60508 "EHLO
        sparkle.Generation.NET") by vger.rutgers.edu with ESMTP
	id <S156906AbPJGQyH>; Thu, 7 Oct 1999 12:54:07 -0400
Received: from dual (generic253.197.205.205.IN-ADDR.ARPA [205.205.197.253] (may be forged))
	by sparkle.Generation.NET (8.9.3/8.9.3) with SMTP id MAA10659
	for <linux-arm@vger.rutgers.edu>; Thu, 7 Oct 1999 12:54:17 -0400 (EDT)
From: Francois Desloges <fd@vipswitch.com>
To: linux-arm@vger.rutgers.edu
Subject: Re: Errors Building ARM-Linux-2.2.10 with gcc-2.95.1
Date:   Thu, 7 Oct 1999 12:49:08 -0400
Content-Type: text/plain
References: <99100712395208.14871@dual>
MIME-Version: 1.0
Message-Id: <99100712525109.14871@dual>
Content-Transfer-Encoding: 8bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

On Wed, 06 Oct 1999, I wrote:
> >make[1]: Leaving directory `/usr/src/linux-2.2.10/arch/arm/nwfpe'
> >/usr/arm-linux/bin/ld -T /usr/src/linux/arch/arm/vmlinux-armv.lds -e stext
> >-Ttext 0xC0008000 arch/arm/kernel/head-armv.o arch/arm/kernel/init_task.o
> >init/main.o init/version.o \ --start-group \ arch/arm/kernel/kernel.o
> >arch/arm/mm/mm.o kernel/kernel.o mm/mm.o fs/fs.o ipc/ipc.o \ fs/filesystems.a \
> >net/network.a \
> >drivers/block/block.a drivers/char/char.a drivers/misc/misc.a drivers/net/net.a
> >drivers/pci/pci.a arch/arm/special/special.a arch/arm/nwfpe/math-emu.a \
> >arch/arm/lib/lib.a /usr/src/linux/lib/lib.a `/usr/arm-linux/bin/gcc
> >-D__KERNEL__ -I/usr/src/linux/include  -mapcs-32 -mshort-load-bytes
> >-mcpu=strongarm110 --print-libgcc-file-name` \         --end-group \         -o
> >vmlinux /usr/arm-linux/bin/ld: target elf32-arm not found
> >make: *** [vmlinux] Error 1                                                  
> 
> I know that elf32-arm should be armelf_linux.  I've already made the changes
> in /usr/lib/gcc-lib/arm-linux/2.95.1/specs as required by
> release.binutils-2.9.5.0.12 (although I thought this was only for glibc?)
> 
> Where (if I'm guessing right) are the variables to change, or what else should I
> do?
Answering my own question, I've found that file called
arch/arm/vmlinux-armv.lds which pretty much seems to be the responsible.
Anybody knows what should I do with it?

Oh, thank you so much again!
--
François Desloges
fd@vipswitch.com
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Thu Oct  7 18:54:52 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id SAA00385
	for <linux-arm-archive@lists.arm.linux.org.uk>; Thu, 7 Oct 1999 18:54:52 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id D234A13E05; Thu,  7 Oct 1999 19:54:50 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156723AbPJGRxn>;
	Thu, 7 Oct 1999 13:53:43 -0400
Received: by vger.rutgers.edu id <S156806AbPJGRrM>;
	Thu, 7 Oct 1999 13:47:12 -0400
Received: from ns0.utdallas.edu ([129.110.10.1]:58225 "HELO ns0.utdallas.edu")
	by vger.rutgers.edu with SMTP id <S156793AbPJGRjJ>;
	Thu, 7 Oct 1999 13:39:09 -0400
Received: from apache.utdallas.edu (apache.utdallas.edu [129.110.16.9])
	by ns0.utdallas.edu (Postfix) with ESMTP
	id B1C6D1A00C7; Thu,  7 Oct 1999 12:38:59 -0500 (CDT)
Received: from localhost (vasantr@localhost)
	by apache.utdallas.edu (8.9.1/8.9.1) with SMTP id MAA09028;
	Thu, 7 Oct 1999 12:39:09 -0500 (CDT)
X-Authentication-Warning: apache.utdallas.edu: vasantr owned process doing -bs
Date:   Thu, 7 Oct 1999 12:39:09 -0500 (CDT)
From: Vasant Ramasubramanian <vasantr@utdallas.edu>
To: Dave Borja <dave_bb@pacbell.net>
Cc: linux-arm@vger.rutgers.edu
Subject: Re: Brutus Woes, any help?
In-Reply-To: <003701bf10db$02b28780$529765d8@java>
Message-ID: <Pine.GSO.3.96.991007123731.7377A-100000@apache.utdallas.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing



On Thu, 7 Oct 1999, Dave Borja wrote:

> This setup you describe-- right now you are just trying
> to talk to it via ADK ARM debug? We got that far,
> using ARM 2.11a sdk on a windows 98 box.. 
> We had a similar problem with 
> no response from angel  and switched all the baudrate
> settings to 9600. Now we can run the test apps.

Yeah I can't even get it to talk to the ARM debug.
> 
> Or we could. The brutus board seems to taken a
> hike south. The numeric LED is showing a 7 now
> everytime we power up and we can't make a connection
> to it either with the debugger SDK or angleboot on linux.
> 
> Anyone seen the 7? It's not documented anyplace that I can
> find.

I've always gotten that 7 (this is the first time I've tried to use
Brutus) and I don't know what it means either...

Vasant.


>  Dave
> -----Original Message-----
> From: Vasant Ramasubramanian <vasantr@utdallas.edu>
> To: linux-arm@vger.rutgers.edu <linux-arm@vger.rutgers.edu>
> Date: Thursday, October 07, 1999 12:27 AM
> Subject: Brutus Woes, any help?
> 
> 
> >Hello all!
> >
> >I'm trying to setup my Brutus board to run the basic test programs that
> >come with the Kit (requires the SDT 2.50 to run, which I have) and I am
> >not even sure that my Brutus is working. From all the documentation I've
> >read (what little is provided) connecting the null-modem cable to J23 on
> >the Brutus and to a COM port on the PC should at least bring up a message
> >about Angel running on Brutus, right?
> >
> >I used 9600,8,N,1 and 115200,8.N,1 for the serial port settings yet when I
> >turned Brutus on, I didn't get anything. I'm certain the PC is fine, the
> >serial port is fine, the null modem cable is fine, I've checked those
> >things out. I also made sure all the dip swtiches were in the default
> >position specified in the .pdf documentation for Brutus. Any ideas?
> >
> >I haven't gotten to using angelboot.tgz or putting my RAM DISK on there or
> >anything like that.
> >
> >For the ARM SDT 2.5 portion, I was using Win95 OSR2.
> >
> >I'm running Red Hat 6.0 for the Linux end of things, hopefully if my
> >Brutus is working I can get it to boot Linux...
> >
> >I'd appreciate any help/suggestions.
> >
> >Thanks, Vasant.
> >
> >unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu
> >
> 
> unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu
> 

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Thu Oct  7 18:57:35 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id SAA00523
	for <linux-arm-archive@lists.arm.linux.org.uk>; Thu, 7 Oct 1999 18:57:35 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 2DB7F13F83; Thu,  7 Oct 1999 19:57:01 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156817AbPJGRyE>;
	Thu, 7 Oct 1999 13:54:04 -0400
Received: by vger.rutgers.edu id <S156801AbPJGRkg>;
	Thu, 7 Oct 1999 13:40:36 -0400
Received: from mail-gw5.pacbell.net ([206.13.28.23]:50815 "EHLO
        mail-gw5.pacbell.net") by vger.rutgers.edu with ESMTP
	id <S156868AbPJGReW>; Thu, 7 Oct 1999 13:34:22 -0400
Received: from java (adsl-216-101-151-82.dsl.snfc21.pacbell.net [216.101.151.82])
	by mail-gw5.pacbell.net (8.9.3/8.9.3) with SMTP id KAA08165
	for <linux-arm@vger.rutgers.edu>; Thu, 7 Oct 1999 10:34:20 -0700 (PDT)
Message-ID: <00dd01bf10eb$82dddbc0$529765d8@java>
From: "Dave Borja" <dave_bb@pacbell.net>
To: "linux-arm" <linux-arm@vger.rutgers.edu>
Subject: 
Date:   Thu, 7 Oct 1999 10:43:48 -0700
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.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Does anyone if binutils-2.9.1.0.25.tar.gz from:

ftp://ftp.varesearch.com/pub/support/hjl/binutils/2.9.1/

will work for building the brutus cross development environment?
I can't find an diff-arm patch for it as for the binutils-2.9.1.0.19a
archive.

Thanks,
 Dave

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Thu Oct  7 19:08:44 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id TAA00830
	for <linux-arm-archive@lists.arm.linux.org.uk>; Thu, 7 Oct 1999 19:08:43 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 73C4713FA9; Thu,  7 Oct 1999 20:08:42 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156901AbPJGSHd>;
	Thu, 7 Oct 1999 14:07:33 -0400
Received: by vger.rutgers.edu id <S156816AbPJGSEU>;
	Thu, 7 Oct 1999 14:04:20 -0400
Received: from ns0.utdallas.edu ([129.110.10.1]:59194 "HELO ns0.utdallas.edu")
	by vger.rutgers.edu with SMTP id <S156804AbPJGSCm>;
	Thu, 7 Oct 1999 14:02:42 -0400
Received: from apache.utdallas.edu (apache.utdallas.edu [129.110.16.9])
	by ns0.utdallas.edu (Postfix) with ESMTP
	id BA7C61A00C3; Thu,  7 Oct 1999 13:02:31 -0500 (CDT)
Received: from localhost (vasantr@localhost)
	by apache.utdallas.edu (8.9.1/8.9.1) with SMTP id NAA11846;
	Thu, 7 Oct 1999 13:02:41 -0500 (CDT)
X-Authentication-Warning: apache.utdallas.edu: vasantr owned process doing -bs
Date:   Thu, 7 Oct 1999 13:02:41 -0500 (CDT)
From: Vasant Ramasubramanian <vasantr@utdallas.edu>
To: Dave Borja <dave_bb@pacbell.net>
Cc: linux-arm@vger.rutgers.edu
Subject: Re: Brutus Woes, any help?
In-Reply-To: <003701bf10db$02b28780$529765d8@java>
Message-ID: <Pine.GSO.3.96.991007124108.7377B-100000@apache.utdallas.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

I got that 7 to go away by telling it to use DRAM istead of SRAM (a NO-DOT
on S14). Then Brutus did send data via the serial port...I've put a call
into Intel, we'll see what they say.

Vasant.

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Thu Oct  7 19:37:51 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id TAA01797
	for <linux-arm-archive@lists.arm.linux.org.uk>; Thu, 7 Oct 1999 19:37:50 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id E324413E25; Thu,  7 Oct 1999 20:37:48 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156767AbPJGSd3>;
	Thu, 7 Oct 1999 14:33:29 -0400
Received: by vger.rutgers.edu id <S156801AbPJGSdD>;
	Thu, 7 Oct 1999 14:33:03 -0400
Received: from nas01-200.156.thefree.net ([195.34.200.156]:1062 "EHLO
        hyperspace.linuxhacker.org") by vger.rutgers.edu with ESMTP
	id <S156949AbPJGSZ2>; Thu, 7 Oct 1999 14:25:28 -0400
Received: from localhost (alex@localhost [127.0.0.1])
	by hyperspace.linuxhacker.org (8.8.7/8.8.7) with ESMTP id TAA00742;
	Thu, 7 Oct 1999 19:16:53 +0100
Date:   Thu, 7 Oct 1999 19:16:53 +0100 (GMT)
From: Alex Holden <alex@linuxhacker.org>
To: David Rusling <david.rusling@arm.com>
Cc: linux-arm@vger.rutgers.edu
Subject: Re: init process/program
In-Reply-To: <37FA1715.95C48D23@arm.com>
Message-ID: <Pine.LNX.4.04.9910071915550.430-100000@hyperspace>
X-OS:   Linux-2.3.0
X-Subliminal-Message: Use Linux!
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

On Tue, 5 Oct 1999, David Rusling wrote:
> I'm fiddling about with a PCI based ARM system (Integrator, it's
> just gone on sale).

Do you have any URLs to more detail about them?

--------------- Linux- the choice of a GNU generation. --------------
: Alex Holden (M1CJD)- Caver, Programmer, Land Rover nut, Radio Ham :
-------------------- http://www.linuxhacker.org/ --------------------

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Thu Oct  7 20:23:21 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id UAA03024
	for <linux-arm-archive@lists.arm.linux.org.uk>; Thu, 7 Oct 1999 20:23:21 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id EBED213F97; Thu,  7 Oct 1999 21:23:19 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156983AbPJGTVQ>;
	Thu, 7 Oct 1999 15:21:16 -0400
Received: by vger.rutgers.edu id <S156975AbPJGTQS>;
	Thu, 7 Oct 1999 15:16:18 -0400
Received: from tazenda.demon.co.uk ([158.152.220.239]:1713 "EHLO
        kings-cross.london.uk.eu.org") by vger.rutgers.edu with ESMTP
	id <S156822AbPJGTKe>; Thu, 7 Oct 1999 15:10:34 -0400
Received: from localhost
	([127.0.0.1] helo=kings-cross.london.uk.eu.org ident=phil)
	by kings-cross.london.uk.eu.org with esmtp (Exim 2.05 #1)
	id 11ZIvl-0005yr-00; Thu, 7 Oct 1999 20:10:21 +0100
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: "Dave Borja" <dave_bb@pacbell.net>
Cc: "linux-arm" <linux-arm@vger.rutgers.edu>
Subject: Re: 
In-Reply-To: Message from "Dave Borja" <dave_bb@pacbell.net> 
   of "Thu, 07 Oct 1999 10:43:48 PDT." <00dd01bf10eb$82dddbc0$529765d8@java> 
References: <00dd01bf10eb$82dddbc0$529765d8@java> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date:   Thu, 07 Oct 1999 20:10:21 +0100
From: Philip Blundell <Philip.Blundell@pobox.com>
Message-Id: <E11ZIvl-0005yr-00@kings-cross.london.uk.eu.org>
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

>Does anyone if binutils-2.9.1.0.25.tar.gz from:
>
>ftp://ftp.varesearch.com/pub/support/hjl/binutils/2.9.1/
>
>will work for building the brutus cross development environment?
>I can't find an diff-arm patch for it as for the binutils-2.9.1.0.19a
>archive.

It should be OK, but the 2.9.5 track is better (if you can tolerate the odd 
incompatibility).  The patch for 2.9.1.0.19a is probably not something you 
want to apply in any case; it fixes one problem at the expense of introducing 
others.

p.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Thu Oct  7 20:59:49 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id UAA03969
	for <linux-arm-archive@lists.arm.linux.org.uk>; Thu, 7 Oct 1999 20:59:48 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 742C013F6B; Thu,  7 Oct 1999 21:59:47 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156977AbPJGTzq>;
	Thu, 7 Oct 1999 15:55:46 -0400
Received: by vger.rutgers.edu id <S157078AbPJGTpf>;
	Thu, 7 Oct 1999 15:45:35 -0400
Received: from sparkle.Generation.NET ([205.205.119.4]:35717 "EHLO
        sparkle.Generation.NET") by vger.rutgers.edu with ESMTP
	id <S156945AbPJGTkU>; Thu, 7 Oct 1999 15:40:20 -0400
Received: from dual (generic253.197.205.205.IN-ADDR.ARPA [205.205.197.253] (may be forged))
	by sparkle.Generation.NET (8.9.3/8.9.3) with SMTP id PAA02081
	for <linux-arm@vger.rutgers.edu>; Thu, 7 Oct 1999 15:40:26 -0400 (EDT)
From: Francois Desloges <fd@vipswitch.com>
To: linux-arm@vger.rutgers.edu
Subject: Re: Errors Building ARM-Linux-2.2.10 with gcc-2.95.1
Date:   Thu, 7 Oct 1999 15:38:34 -0400
Content-Type: text/plain
MIME-Version: 1.0
Message-Id: <9910071539040B.14871@dual>
Content-Transfer-Encoding: 8bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

On Thu, 07 Oct 1999, you wrote:
> >Answering my own question, I've found that file called
> >arch/arm/vmlinux-armv.lds which pretty much seems to be the responsible=
> >Anybody knows what should I do with it?
> 
> ftp://ftp.netwinder.org/users/p/philb/kernel/

Hummm. There's no patch for 2.2.10rmk3, yours stop at rmk2 and Russel's rmk3
seems to inculde half of the patch of your own rmk2.diff

Anyway! I realised that binutils where still in versions 2.9.1 at
the time of kernel 2.2.10. I use binutils-2.9.5.x, so I just move to kernel
2.2.12, approprietely patched as usual, and everything worked, provided that I
created 2 symlinks:
/usr/arm-linux/bin/objdump -> /usr/bin/arm-linux-objdump
/usr/arm-linux/bin/objcopy -> /usr/bin/arm-linux-objcopy
since I guessed binutils-2.9.5.0.13 forgot to create a copy of objdump
and objcopy in /usr/arm-linux/bin/.

Anybody can confirm me this was the right thing to do?
Thanks!
--
François Desloges
fd@vipswitch.com
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Thu Oct  7 21:07:53 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id VAA04253
	for <linux-arm-archive@lists.arm.linux.org.uk>; Thu, 7 Oct 1999 21:07:53 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 2812D13F70; Thu,  7 Oct 1999 22:07:51 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157063AbPJGUCS>;
	Thu, 7 Oct 1999 16:02:18 -0400
Received: by vger.rutgers.edu id <S157111AbPJGT67>;
	Thu, 7 Oct 1999 15:58:59 -0400
Received: from m12-nsv1-trogon.tch.cableol.net ([194.168.16.12]:4847 "EHLO
        caramon.armlinux.org.uk") by vger.rutgers.edu with ESMTP
	id <S156919AbPJGTzN>; Thu, 7 Oct 1999 15:55:13 -0400
Received: from raistlin.armlinux.org.uk (linux@raistlin [192.168.0.3])
	by caramon.armlinux.org.uk (8.8.7/8.8.7) with ESMTP id UAA23803;
	Thu, 7 Oct 1999 20:55:07 +0100
From: linux@arm.linux.org.uk
Received: (from linux@localhost) by raistlin.armlinux.org.uk (8.7.4/8.7.3) id UAA31276; Thu, 7 Oct 1999 20:53:35 +0100
Message-Id: <199910071953.UAA31276@raistlin.armlinux.org.uk>
Subject: Re: Errors Building ARM-Linux-2.2.10 with gcc-2.95.1
To: fd@vipswitch.com (Francois Desloges)
Date:   Thu, 7 Oct 1999 20:53:34 +0100 (BST)
Cc: linux-arm@vger.rutgers.edu
In-Reply-To: <99100712395208.14871@dual> from "Francois Desloges" at Oct 6, 99 11:12:47 am
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Francois Desloges writes:
> "make zImage", in /usr/src/linux/arch/arm/lib, trying to create constant.h with:
> perl extractconstants.pl /usr/arm-linux/bin/objdump > constants.h
> gives me:
> sh: /usr/arm-linux/bin/objdump: No such file or directory
> which in turn of course fail to buil cheksum.o from checksum.S.

Either your installation of the binutils failed in some manner (it created
/usr/arm-linux/bin/ld and not /usr/arm=linux/bin/objdump), or you have not
correctly set CROSS_COMPILE.  I always use the "arm-linux-" version, and
have not been using the full path with it for months now.

> /usr/bin/arm-linux-objdump, which seems to work.
> Is that right?

It's an acceptable way to get around the problem, but it should be reported
to the binutils maintainers.

> >/usr/arm-linux/bin/ld  -r -o kernel.o armksyms.o leds-footbridge.o dma.o
> >hw-foot bridge.o entry-armv.o irq.o process.o ptrace.o setup.o signal.o
> >sys_arm.o time.o  traps.o ioport.o dma-footbridge.o  isa.o dec21285.o
> >/usr/arm-linux/bin/ld: cannot open ioport.o: No such file or directory
> >make[1]: *** [kernel.o] Error 1
> >make[1]: Leaving directory `/usr/src/linux-2.2.10/arch/arm/kernel'
> >make: *** [_dir_arch/arm/kernel] Error 2

Known problem with 2.2.10.  Why not use 2.2.12?

> by erasing ioport.o. That seemed to work.
> Is that right?

No.  Get a later version of the source.  ioport.c got missed out (cause I
have the reference tree and 4 built trees, ioport.c never got back to the
reference tree for some reason).

> I know that elf32-arm should be armelf_linux.  I've already made the changes
> in /usr/lib/gcc-lib/arm-linux/2.95.1/specs as required by
> release.binutils-2.9.5.0.12 (although I thought this was only for glibc?)

You need to remove the `OUTPUT_FORMAT("elf32-arm", "elf32-arm", "elf32-arm")' line
from arch/arm/vmlinux-armv.lds

   _____
  |_____| ------------------------------------------------- ---+---+-
  |   |        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' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Thu Oct  7 21:26:38 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id VAA04780
	for <linux-arm-archive@lists.arm.linux.org.uk>; Thu, 7 Oct 1999 21:26:38 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id A7EC913FCA; Thu,  7 Oct 1999 22:26:36 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157231AbPJGUPn>;
	Thu, 7 Oct 1999 16:15:43 -0400
Received: by vger.rutgers.edu id <S156773AbPJGUP3>;
	Thu, 7 Oct 1999 16:15:29 -0400
Received: from m12-nsv1-trogon.tch.cableol.net ([194.168.16.12]:4850 "EHLO
        caramon.armlinux.org.uk") by vger.rutgers.edu with ESMTP
	id <S156735AbPJGT6n>; Thu, 7 Oct 1999 15:58:43 -0400
Received: from raistlin.armlinux.org.uk (linux@raistlin [192.168.0.3])
	by caramon.armlinux.org.uk (8.8.7/8.8.7) with ESMTP id UAA23815;
	Thu, 7 Oct 1999 20:58:37 +0100
From: linux@arm.linux.org.uk
Received: (from linux@localhost) by raistlin.armlinux.org.uk (8.7.4/8.7.3) id UAA31296; Thu, 7 Oct 1999 20:57:06 +0100
Message-Id: <199910071957.UAA31296@raistlin.armlinux.org.uk>
Subject: Re: Fwd: Re: More kernel options questions
To: fd@vipswitch.com (Francois Desloges)
Date:   Thu, 7 Oct 1999 20:57:05 +0100 (BST)
Cc: linux-arm@vger.rutgers.edu
In-Reply-To: <99100710384907.14871@dual> from "Francois Desloges" at Oct 7, 99 10:37:58 am
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Francois Desloges writes:
> And, yes, I meant HD brand, not interface, 'cause I tought all ide HD were
> supposed to use the same ide driver whitout problem. That's the reason for my
> question.

I believe that the only really dodgy hard drives are Western Digital ones -
there's a list of the drives that are definite "we won't do DMA to this
drive even if it claims to support it".
   _____
  |_____| ------------------------------------------------- ---+---+-
  |   |        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' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Thu Oct  7 21:30:38 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id VAA04924
	for <linux-arm-archive@lists.arm.linux.org.uk>; Thu, 7 Oct 1999 21:30:37 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 4EA4213FCF; Thu,  7 Oct 1999 22:30:36 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156779AbPJGU3u>;
	Thu, 7 Oct 1999 16:29:50 -0400
Received: by vger.rutgers.edu id <S156876AbPJGUVy>;
	Thu, 7 Oct 1999 16:21:54 -0400
Received: from m12-nsv1-trogon.tch.cableol.net ([194.168.16.12]:4853 "EHLO
        caramon.armlinux.org.uk") by vger.rutgers.edu with ESMTP
	id <S157077AbPJGUDE>; Thu, 7 Oct 1999 16:03:04 -0400
Received: from raistlin.armlinux.org.uk (linux@raistlin [192.168.0.3])
	by caramon.armlinux.org.uk (8.8.7/8.8.7) with ESMTP id VAA23829;
	Thu, 7 Oct 1999 21:02:52 +0100
From: linux@arm.linux.org.uk
Received: (from linux@localhost) by raistlin.armlinux.org.uk (8.7.4/8.7.3) id VAA31314; Thu, 7 Oct 1999 21:01:21 +0100
Message-Id: <199910072001.VAA31314@raistlin.armlinux.org.uk>
Subject: Re: Web Problem Report Form (Can't even test-boot kernel under RISC OS 4)
To: peter@mezzo.net (Peter =?ISO-8859-1?Q?K=F6llner?=)
Date:   Thu, 7 Oct 1999 21:01:21 +0100 (BST)
Cc: linux-arm@vger.rutgers.edu
In-Reply-To: <24a64f4d49.peter@mezzo.net> from "Peter =?ISO-8859-1?Q?K=F6llner"?= at Oct 7, 99 04:53:01 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Peter Köllner writes:
> In message <199910061836.TAA21515@raistlin.armlinux.org.uk> you wrote:
> > Go to the task manager, new task, type in "Filer_OpenDir Pipe:$", and
> > then use it like a normal filer window.  Note that you can only read
> > the files once.
> 
> It looks like the trouble already starts there. I get the window
> for Pipe:$ with an entry for
> 
> C_Debug  WR/    Directory
> 
> but when I try to open that I get an error
> 
> Error when reading Pipe:$.C_Debug - 'C_Debug' is a file

Anyone like to comment?  This looks like another "brokenness" of RISC OS 4.
If this is the case, then I am not going to even attempt to find out what's
going on with RISC OS 4 and !Linux, since I shall take the view that
RISC OS 4 is totally unsuitable, and suggest you upgrade to RISC OS 3.7 or
3.8 which actually works.

(forwarded to the mailing list to see if anyone else has any useful
 suggestions).
   _____
  |_____| ------------------------------------------------- ---+---+-
  |   |        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' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Thu Oct  7 22:15:07 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id WAA06211
	for <linux-arm-archive@lists.arm.linux.org.uk>; Thu, 7 Oct 1999 22:15:06 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 2C3CD13DD0; Thu,  7 Oct 1999 23:15:05 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157242AbPJGUo5>;
	Thu, 7 Oct 1999 16:44:57 -0400
Received: by vger.rutgers.edu id <S157101AbPJGUaV>;
	Thu, 7 Oct 1999 16:30:21 -0400
Received: from tazenda.demon.co.uk ([158.152.220.239]:1750 "EHLO
        kings-cross.london.uk.eu.org") by vger.rutgers.edu with ESMTP
	id <S157085AbPJGUYY>; Thu, 7 Oct 1999 16:24:24 -0400
Received: from localhost
	([127.0.0.1] helo=kings-cross.london.uk.eu.org ident=phil)
	by kings-cross.london.uk.eu.org with esmtp (Exim 2.05 #1)
	id 11ZK5L-00064o-00
	for linux-arm@vger.rutgers.edu; Thu, 7 Oct 1999 21:24:19 +0100
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: Francois Desloges <fd@vipswitch.com>
Subject: Re: Errors Building ARM-Linux-2.2.10 with gcc-2.95.1 
In-Reply-To: Message from Francois Desloges <fd@vipswitch.com> 
   of "Thu, 07 Oct 1999 15:08:15 EDT." <9910071538140A.14871@dual> 
References: <E11ZItM-0005yE-00@kings-cross.london.uk.eu.org>  <9910071538140A.14871@dual> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date:   Thu, 07 Oct 1999 21:23:07 +0100
From: Philip Blundell <phil@kings-cross.london.uk.eu.org>
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
Message-Id: <19991007204448Z157101-15068+738@vger.rutgers.edu>
X-Orcpt: rfc822;linux-arm-outgoing

>Hummm. There's no patch for 2.2.10rmk3, yours stop at rmk2 and Russel's rmk3
>seems to inculde half of the patch of your own rmk2.diff

I thought there was one there for the latest 2.2 (.12 I guess).  But I could 
be wrong about that.  There certainly aren't patches for every single revision 
though.

>/usr/arm-linux/bin/objdump -> /usr/bin/arm-linux-objdump
>/usr/arm-linux/bin/objcopy -> /usr/bin/arm-linux-objcopy
>since I guessed binutils-2.9.5.0.13 forgot to create a copy of objdump
>and objcopy in /usr/arm-linux/bin/.
>
>Anybody can confirm me this was the right thing to do?

Yes, that's right.  I'm surprised `make install' didn't create those itself; 
you might report it to the binutils people.

p.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Thu Oct  7 22:39:42 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id WAA06817
	for <linux-arm-archive@lists.arm.linux.org.uk>; Thu, 7 Oct 1999 22:39:42 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id D99E113FB2; Thu,  7 Oct 1999 23:39:40 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157028AbPJGVTw>;
	Thu, 7 Oct 1999 17:19:52 -0400
Received: by vger.rutgers.edu id <S156916AbPJGVN3>;
	Thu, 7 Oct 1999 17:13:29 -0400
Received: from mail15.svr.pol.co.uk ([195.92.193.25]:29379 "EHLO
        mail15.svr.pol.co.uk") by vger.rutgers.edu with ESMTP
	id <S157047AbPJGUlo>; Thu, 7 Oct 1999 16:41:44 -0400
Received: from modem-26.uranium.dialup.pol.co.uk ([62.136.45.154] helo=freeserve)
	by mail15.svr.pol.co.uk with smtp (Exim 2.12 #2)
	id 11ZKM6-0003rH-00
	for linux-arm@vger.rutgers.edu; Thu, 7 Oct 1999 21:41:38 +0100
Date:   Thu, 07 Oct 1999 21:40:29 +0100
From: Peter Naulls <peter@erble.freeserve.co.uk>
To: linux-arm@vger.rutgers.edu
Subject: Re: Web Problem Report Form (Can't even test-boot kernel under RISC OS 4)
Message-ID: <28766f4d49%peter@erble.freeserve.co.uk>
In-Reply-To: <199910072001.VAA31314@raistlin.armlinux.org.uk>
X-Mailer: Messenger v1.40f for RISC OS
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Posting-Agent: RISC OS Newsbase 0.60m
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

In message <199910072001.VAA31314@raistlin.armlinux.org.uk>
          linux@arm.linux.org.uk wrote:

> > C_Debug  WR/    Directory
> > 
> > but when I try to open that I get an error
> > 
> > Error when reading Pipe:$.C_Debug - 'C_Debug' is a file
> 
> Anyone like to comment?  This looks like another "brokenness" of RISC OS 4.
> If this is the case, then I am not going to even attempt to find out what's
> going on with RISC OS 4 and !Linux, since I shall take the view that
> RISC OS 4 is totally unsuitable, and suggest you upgrade to RISC OS 3.7 or
> 3.8 which actually works.
> 

I think Russell's been a bit fast off the mark here :-)

RO3.8 is essentially RO4 for the puporses of ARMLinux (and most other
purposes)
!Linux doesn't work on either at this point in time, but linloader does.

<fx: *bops* Russell>  :-)


Peter

-- 
+---------------------------------------------+-----------------------------+
| Peter Naulls - pnaulls@usa.net              |                             |
| http://free.prohosting.com/~chocky/         | Java and JVM Consultant     |
| Java for RISC OS and ARM - java-arm@usa.net | Technical Author            |
| http://free.prohosting.com/~chocky/java/    | Program performance analyst |
+---------------------------------------------+-----------------------------+
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Thu Oct  7 22:42:13 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id WAA06951
	for <linux-arm-archive@lists.arm.linux.org.uk>; Thu, 7 Oct 1999 22:42:12 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 475F313FC7; Thu,  7 Oct 1999 23:42:11 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157066AbPJGVUo>;
	Thu, 7 Oct 1999 17:20:44 -0400
Received: by vger.rutgers.edu id <S157237AbPJGU71>;
	Thu, 7 Oct 1999 16:59:27 -0400
Received: from proxy2.ba.best.com ([206.184.139.14]:3863 "EHLO
        proxy2.ba.best.com") by vger.rutgers.edu with ESMTP
	id <S157279AbPJGUsv>; Thu, 7 Oct 1999 16:48:51 -0400
Received: from mmtdave (ppp-207-214-211-168.sntc01.pacbell.net [207.214.211.168])
	by proxy2.ba.best.com (8.9.3/8.9.2/best.out) with SMTP id NAA21884;
	Thu, 7 Oct 1999 13:41:26 -0700 (PDT)
Message-ID: <004901bf1103$e75143e0$4df63cd1@mmtdave>
From: "Tony Xu" <tonyx@millentek.com>
To: "Vasant Ramasubramanian" <vasantr@utdallas.edu>,
        <linux-arm@vger.rutgers.edu>
Subject: Re: Brutus Woes, any help?
Date:   Thu, 7 Oct 1999 13:38:19 -0700
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.3110.1
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Hi-- you were right about the switch 14 problem causing
7 on the numeric LED. We configured our switch and now
can communicate via angelboot and have boot linux on
the brutus.  What hung us up before was a bad zImage due
to a badly applied (or wrong) patch file.
   Dave


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Thu Oct  7 23:14:07 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id XAA07767
	for <linux-arm-archive@lists.arm.linux.org.uk>; Thu, 7 Oct 1999 23:14:07 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 8184313FB8; Fri,  8 Oct 1999 00:14:05 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157030AbPJGVlw>;
	Thu, 7 Oct 1999 17:41:52 -0400
Received: by vger.rutgers.edu id <S157057AbPJGVUb>;
	Thu, 7 Oct 1999 17:20:31 -0400
Received: from ns0.utdallas.edu ([129.110.10.1]:32883 "HELO ns0.utdallas.edu")
	by vger.rutgers.edu with SMTP id <S157008AbPJGU62>;
	Thu, 7 Oct 1999 16:58:28 -0400
Received: from apache.utdallas.edu (apache.utdallas.edu [129.110.16.9])
	by ns0.utdallas.edu (Postfix) with ESMTP
	id 5BA1B1A010B; Thu,  7 Oct 1999 15:57:53 -0500 (CDT)
Received: from localhost (vasantr@localhost)
	by apache.utdallas.edu (8.9.1/8.9.1) with SMTP id PAA08956;
	Thu, 7 Oct 1999 15:58:00 -0500 (CDT)
X-Authentication-Warning: apache.utdallas.edu: vasantr owned process doing -bs
Date:   Thu, 7 Oct 1999 15:57:59 -0500 (CDT)
From: Vasant Ramasubramanian <vasantr@utdallas.edu>
To: Tony Xu <tonyx@millentek.com>
Cc: linux-arm@vger.rutgers.edu
Subject: Re: Brutus Woes, any help?
In-Reply-To: <004901bf1103$e75143e0$4df63cd1@mmtdave>
Message-ID: <Pine.GSO.3.96.991007155141.7377C-100000@apache.utdallas.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing



On Thu, 7 Oct 1999, Tony Xu wrote:

> Hi-- you were right about the switch 14 problem causing
> 7 on the numeric LED. We configured our switch and now
> can communicate via angelboot and have boot linux on
> the brutus.  What hung us up before was a bad zImage due
> to a badly applied (or wrong) patch file.
>    Dave

And I just got the sample programs to run. I talked to Intel, apparently
that is a mistake in the documentation (SW14 DOT/NO DOT) and they know
about it. Also they said that Angel isn't setup to use DRAM, so if you
want to use the DRAM on Brutus you have to write code to configure the
memory controller; I'm making this point because the documentation for
Brutus simply states you can use SRAM or DRAM but doesn't say that Angel
is only setup to use SRAM... 

BW: The SW14 default should be NO dot meaning *SRAM* is used.

When putting Linux into Brutus, do you have to mess with SW21/22 at all?
(I.e. which bank of Flash, etc?).

Vasant.

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Thu Oct  7 23:48:12 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id XAA09021
	for <linux-arm-archive@lists.arm.linux.org.uk>; Thu, 7 Oct 1999 23:48:11 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id A5BC013F84; Fri,  8 Oct 1999 00:48:09 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157205AbPJGWmH>;
	Thu, 7 Oct 1999 18:42:07 -0400
Received: by vger.rutgers.edu id <S157553AbPJGWU7>;
	Thu, 7 Oct 1999 18:20:59 -0400
Received: from sparkle.Generation.NET ([205.205.119.4]:41946 "EHLO
        sparkle.Generation.NET") by vger.rutgers.edu with ESMTP
	id <S157106AbPJGVqW>; Thu, 7 Oct 1999 17:46:22 -0400
Received: from dual (generic253.197.205.205.IN-ADDR.ARPA [205.205.197.253] (may be forged))
	by sparkle.Generation.NET (8.9.3/8.9.3) with SMTP id RAA08602
	for <linux-arm@vger.rutgers.edu>; Thu, 7 Oct 1999 17:46:36 -0400 (EDT)
From: Francois Desloges <fd@vipswitch.com>
To: linux-arm@vger.rutgers.edu
Subject: Re: Errors Building ARM-Linux-2.2.10 with gcc-2.95.1
Date:   Thu, 7 Oct 1999 17:34:55 -0400
Content-Type: text/plain
References: <199910072132.RAA04003@tonga.xedia.com>
MIME-Version: 1.0
Message-Id: <9910071745140G.14871@dual>
Content-Transfer-Encoding: 8bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Here's the answer from the binutils people:

On Thu, 07 Oct 1999, Ian Lance Taylor wrote:
> From: Francois Desloges <fd@vipswitch.com>
>    Date: Thu, 7 Oct 1999 16:19:09 -0400
> 
>    Neither objdump nor objcopy could be found in the /usr/arm-linux/bin where all
>    the other binutils target were installed.
> 
> That is correct.  The /usr/arm-linux/bin directory is a directory
> which gcc uses to find compiler passes, when gcc and the binutils are
> configured with the same --prefix and --target options.  Only programs
> required by gcc are installed there.
> 
>    I've found that all of them were installed as well as /usr/bin/arm-linux-*
> 
> Yes, that's the normal place for them.
> 
>    The Linux-ARM maintainers suggested me to report you that the objdump, objcopy
>    were not appropriately installed in /usr/arm-linux/bin/.
> 
> The Linux-ARM maintainers should not be expecting to find those
> programs there.  They have never been installed there.  That is not
> what that directory is for.
> 
> Ian

So Russell was right: arm-linux- should be used as CROSS-COMPILE value, not
TARGET-PREFIX/bin/ (using the syntax of Chris Rutter's toolchain guide).

--
François Desloges
fd@vipswitch.com
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Fri Oct  8 15:08:15 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id PAA13649
	for <linux-arm-archive@lists.arm.linux.org.uk>; Fri, 8 Oct 1999 15:08:13 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 3A59A1400B; Fri,  8 Oct 1999 16:08:02 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157048AbPJHOGO>;
	Fri, 8 Oct 1999 10:06:14 -0400
Received: by vger.rutgers.edu id <S157005AbPJHOAY>;
	Fri, 8 Oct 1999 10:00:24 -0400
Received: from [212.219.8.163] ([212.219.8.163]:1960 "HELO inkvine.fluff.org")
	by vger.rutgers.edu with SMTP id <S156767AbPJHN5u>;
	Fri, 8 Oct 1999 09:57:50 -0400
Received: from localhost (localhost [127.0.0.1])
	by inkvine.fluff.org (Postfix) with ESMTP
	id B9E9346842; Fri,  8 Oct 1999 14:57:51 +0100 (BST)
Date:   Fri, 8 Oct 1999 14:57:51 +0100 (BST)
From: Chris Rutter <chris@fluff.org>
Reply-To: chris@fluff.org
To: Dave Borja <dave_bb@pacbell.net>
Cc: linux-arm <linux-arm@vger.rutgers.edu>
Subject: Re: your mail
In-Reply-To: <00dd01bf10eb$82dddbc0$529765d8@java>
Message-ID: <Pine.LNX.4.10.9910081457220.12229-100000@inkvine.fluff.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

On Thu, 7 Oct 1999, Dave Borja wrote:

> will work for building the brutus cross development environment?

Yup, it should do.

> I can't find an diff-arm patch for it as for the binutils-2.9.1.0.19a
> archive.

No problem; it doesn't need one.

-- 
Chris <chris@fluff.org>                         ( http://www.fluff.org/chris )

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Fri Oct  8 15:08:32 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id PAA13660
	for <linux-arm-archive@lists.arm.linux.org.uk>; Fri, 8 Oct 1999 15:08:32 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id B490214120; Fri,  8 Oct 1999 16:08:23 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156894AbPJHODZ>;
	Fri, 8 Oct 1999 10:03:25 -0400
Received: by vger.rutgers.edu id <S156745AbPJHOAf>;
	Fri, 8 Oct 1999 10:00:35 -0400
Received: from [212.219.8.163] ([212.219.8.163]:1957 "HELO inkvine.fluff.org")
	by vger.rutgers.edu with SMTP id <S156868AbPJHN5C>;
	Fri, 8 Oct 1999 09:57:02 -0400
Received: from localhost (localhost [127.0.0.1])
	by inkvine.fluff.org (Postfix) with ESMTP
	id 4879D46842; Fri,  8 Oct 1999 14:57:03 +0100 (BST)
Date:   Fri, 8 Oct 1999 14:57:03 +0100 (BST)
From: Chris Rutter <chris@fluff.org>
Reply-To: chris@fluff.org
To: Francois Desloges <fd@vipswitch.com>
Cc: linux-arm@vger.rutgers.edu
Subject: Re: Errors Building ARM-Linux-2.2.10 with gcc-2.95.1
In-Reply-To: <99100712395208.14871@dual>
Message-ID: <Pine.LNX.4.10.9910081449070.12229-100000@inkvine.fluff.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

On Wed, 6 Oct 1999, Francois Desloges wrote:

> The binary objdump from binutils 2.9.5.0.13 has only been installed as
> /usr/bin/arm-linux-objdump not as /usr/arm-linux/bin/objdump.

I can't comment on the ultimate validity of that, but I can tell
you that the conventional way of specifying a cross-compiler
is by using a string of the form `CROSS_COMPILE = arm-linux' in
the top-level Makefile; using this would solve your problems.

> I've created a /usr/arm-linux/bin/objdump symlink that points to 
> /usr/bin/arm-linux-objdump, which seems to work.
> Is that right?

Yeah; I can't see anything wrong with that.  You're hardly 
trying to build pristine packages or anything.

> The arch/arm/kernel directory has no ioport.c file (there is one in
> each arch/{i386, sparc,mips,sparc64}/kernel.

Odd; I've got one in my 2.2.12+rmk+CVS kernel tree.  It provides
only one function sys_iopl(); if you grep through the arm/
directory you'll probably find that this function is somewhere
in one of the other files in the particular version you've got.

I suggest upgrading to 2.2.12.

> >vmlinux /usr/arm-linux/bin/ld: target elf32-arm not found
> >make: *** [vmlinux] Error 1                                                  

You are correct in that you have to change a variable somewhere
in the kernel source, I think.  The CVS patches from netwinder.org
rectify this, I think; download the latest and search through
it until you find where the patch is, then you can apply it
to your latest kernel.

-- 
Chris <chris@fluff.org>                         ( http://www.fluff.org/chris )

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Fri Oct  8 16:19:40 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id QAA19649
	for <linux-arm-archive@lists.arm.linux.org.uk>; Fri, 8 Oct 1999 16:19:39 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 8988413F7D; Fri,  8 Oct 1999 17:19:37 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157227AbPJHOrQ>;
	Fri, 8 Oct 1999 10:47:16 -0400
Received: by vger.rutgers.edu id <S157015AbPJHOiy>;
	Fri, 8 Oct 1999 10:38:54 -0400
Received: from wheelo.gsfc.nasa.gov ([128.183.50.20]:50054 "EHLO
        wheelo.gsfc.nasa.gov") by vger.rutgers.edu with ESMTP
	id <S157011AbPJHOcZ>; Fri, 8 Oct 1999 10:32:25 -0400
Received: from fan745.gsfc.nasa.gov (root@fan745.gsfc.nasa.gov [128.183.146.42])
	by wheelo.gsfc.nasa.gov (8.8.8/8.8.8) with ESMTP id KAA15671
	for <linux-arm@vger.rutgers.edu>; Fri, 8 Oct 1999 10:33:28 -0400 (EDT)
From: niles@fan745.gsfc.nasa.gov
Received: from fan745.gsfc.nasa.gov (IDENT:niles@localhost [127.0.0.1])
	by fan745.gsfc.nasa.gov (8.9.3/8.8.7) with ESMTP id KAA15531;
	Fri, 8 Oct 1999 10:34:18 -0400
Message-Id: <199910081434.KAA15531@fan745.gsfc.nasa.gov>
To: linux-arm@vger.rutgers.edu
Cc: niles@fan745.gsfc.nasa.gov
Subject: Chalice CATS support?
Date:   Fri, 08 Oct 1999 10:34:18 -0400
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing


I just order a Chalice CATS system which has a SA-110.  The Chalice
web page claims to have early support for Linux done by Philip
Blundell.  What is the state of this?  It it being carried along as a
valid port?  What are the problems?  How can I get more info?

      Thanks,
      Rick Niles
      NASA/GSFC
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Fri Oct  8 17:25:36 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id RAA23189
	for <linux-arm-archive@lists.arm.linux.org.uk>; Fri, 8 Oct 1999 17:25:35 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 11FDA14168; Fri,  8 Oct 1999 18:25:28 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157483AbPJHPqN>;
	Fri, 8 Oct 1999 11:46:13 -0400
Received: by vger.rutgers.edu id <S157004AbPJHPTZ>;
	Fri, 8 Oct 1999 11:19:25 -0400
Received: from netwinder.org ([207.245.35.202]:29765 "EHLO www.netwinder.org")
	by vger.rutgers.edu with ESMTP id <S157011AbPJHOvC>;
	Fri, 8 Oct 1999 10:51:02 -0400
Received: from gw.rebel.com (gate.rebel.com [207.245.35.200])
	by www.netwinder.org (8.8.7/8.8.7) with SMTP id KAA06661;
	Fri, 8 Oct 1999 10:50:35 -0400
Message-ID: <37FE03FA.D5E54C66@netwinder.org>
Received: from dhcp111.isa.ott.rebel.com by gw.rebel.com
          via smtpd (for netwinder.org [207.245.35.202]) with SMTP; 8 Oct 1999 14:47:45 UT
Date:   Fri, 08 Oct 1999 10:47:22 -0400
From: Scott Bambrough <scottb@netwinder.org>
Organization: Rebel.com
X-Mailer: Mozilla 4.61 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
To: chris@fluff.org
Cc: Francois Desloges <fd@vipswitch.com>, linux-arm@vger.rutgers.edu
Subject: Re: Errors Building ARM-Linux-2.2.10 with gcc-2.95.1
References: <Pine.LNX.4.10.9910081449070.12229-100000@inkvine.fluff.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Chris Rutter wrote:
> 
> > The binary objdump from binutils 2.9.5.0.13 has only been installed as
> > /usr/bin/arm-linux-objdump not as /usr/arm-linux/bin/objdump.
> 
> > >vmlinux /usr/arm-linux/bin/ld: target elf32-arm not found
> > >make: *** [vmlinux] Error 1
> 

This problems is caused by using the new binutils (2.9.5xxx).  The
target names were changed between 2.9.1 and 2.9.5 when our code was
integrated with the code from Cygnus.  You need to rebuild your
compiler, after having changed the link spec.  See
gcc/config/arm/linux-elf.h and do a search for LINK_SPEC.  You want to
use armelf_linux rather than elf32arm.

Scott
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Fri Oct  8 19:54:49 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id TAA28800
	for <linux-arm-archive@lists.arm.linux.org.uk>; Fri, 8 Oct 1999 19:54:48 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 36E1C14097; Fri,  8 Oct 1999 20:54:47 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157560AbPJHSJL>;
	Fri, 8 Oct 1999 14:09:11 -0400
Received: by vger.rutgers.edu id <S156937AbPJHRWN>;
	Fri, 8 Oct 1999 13:22:13 -0400
Received: from nexusel.demon.co.uk ([158.152.30.195]:30742 "EHLO
        globe.nexus.co.uk") by vger.rutgers.edu with ESMTP
	id <S156972AbPJHQqr>; Fri, 8 Oct 1999 12:46:47 -0400
Received: from [192.0.0.21] (helo=fountain.nexus.co.uk ident=mail)
	by globe.nexus.co.uk with smtp (Exim 2.12 #1)
	id 11Zd8l-0005Rk-00; Fri, 8 Oct 1999 17:45:07 +0100
Received: from [127.0.0.1] (helo=fountain ident=pb)
	by fountain.nexus.co.uk with esmtp (Exim 3.03 #1)
	id 11Zd8k-0007vD-00; Fri, 08 Oct 1999 17:45:06 +0100
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: niles@fan745.gsfc.nasa.gov
Cc: linux-arm@vger.rutgers.edu
Subject: Re: Chalice CATS support? 
In-Reply-To: Message from niles@fan745.gsfc.nasa.gov 
   of "Fri, 08 Oct 1999 10:34:18 EDT." <199910081434.KAA15531@fan745.gsfc.nasa.gov> 
References: <199910081434.KAA15531@fan745.gsfc.nasa.gov> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date:   Fri, 08 Oct 1999 17:45:06 +0100
From: Philip Blundell <pb@nexus.co.uk>
Message-Id: <E11Zd8k-0007vD-00@fountain.nexus.co.uk>
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

>I just order a Chalice CATS system which has a SA-110.  The Chalice
>web page claims to have early support for Linux done by Philip
>Blundell.  What is the state of this?  It it being carried along as a
>valid port?  What are the problems?  How can I get more info?

Yes, the CATS is supported as an EBSA-285-alike system.  I'm not aware of any 
particular problems with it right now.  Get the latest 2.2.12 kernel and the 
patches from ftp.netwinder.org:/users/p/philb/kernel/ and you should be all 
set.

p.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Fri Oct  8 21:20:49 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id VAA32006
	for <linux-arm-archive@lists.arm.linux.org.uk>; Fri, 8 Oct 1999 21:20:48 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id CF1F1140E9; Fri,  8 Oct 1999 22:20:46 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156856AbPJHSjc>;
	Fri, 8 Oct 1999 14:39:32 -0400
Received: by vger.rutgers.edu id <S156995AbPJHRrm>;
	Fri, 8 Oct 1999 13:47:42 -0400
Received: from sparkle.Generation.NET ([205.205.119.4]:40979 "EHLO
        sparkle.Generation.NET") by vger.rutgers.edu with ESMTP
	id <S157077AbPJHQeC>; Fri, 8 Oct 1999 12:34:02 -0400
Received: from dual (generic253.197.205.205.IN-ADDR.ARPA [205.205.197.253] (may be forged))
	by sparkle.Generation.NET (8.9.3/8.9.3) with SMTP id MAA20480
	for <linux-arm@vger.rutgers.edu>; Fri, 8 Oct 1999 12:34:14 -0400 (EDT)
From: Francois Desloges <fd@vipswitch.com>
To: linux-arm@vger.rutgers.edu
Subject: bios 1.05 questions
Date:   Fri, 8 Oct 1999 10:49:01 -0400
Content-Type: text/plain
MIME-Version: 1.0
Message-Id: <9910081232550I.14871@dual>
Content-Transfer-Encoding: 8bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

May somebody can help?

On my system, with binutils 2.9.5.0.13:
# arm-linux-ld -V
GNU ld version 2.9.5 (with BFD 2.9.5.0.13)
  Supported emulations:
   armelf_linux
   armelf_linux26
   armelf                                                                       

I want to build an ELF bios.
I think I will have problem with the following lines in bios' Makefile:
> ELF		:= $(shell $(LD) -V | grep 'elf32arm' > /dev/null && echo y)
>
>ifeq ($(ELF),y)
>CFLAGS		+= -mapcs-32 -mcpu=strongarm110 -DELF
>BIOS		= bios.elf
>else
>CFLAGS		+= -m6 -Wa,-msa110
>BIOS		= bios.a.out
>endif

I guess 'elf32arm' should be changed by one of: 
	armelf_linux
	armelf_linux26
	armelf                                                                       
What are the differences between these 3 values and which one should be used
with all binutils-2.9.5.x ?
(Of course, in my case anyone would be OK, but it's always preferable to know
the GoodAnswer)

>From my problems with building linux-2.2.12:
On Thu, 07 Oct 1999, Russell wrote:
> Francois Desloges writes:
> > I know that elf32-arm should be armelf_linux.  I've already made the changes
> > in /usr/lib/gcc-lib/arm-linux/2.95.1/specs as required by
> > release.binutils-2.9.5.0.12 (although I thought this was only for glibc?)
> 
> You need to remove the `OUTPUT_FORMAT("elf32-arm", "elf32-arm", "elf32-arm")' line
> from arch/arm/vmlinux-armv.lds

I guess that the same correction shoul be done in bios/elfbios.lds if i get
the same kind of Error?
Why not put a new OUTPUT_FORMAT() base on a derivative of "armelf"?

--
François Desloges
fd@vipswitch.com
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sat Oct  9 03:13:46 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id DAA10313
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sat, 9 Oct 1999 03:13:45 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 8BFE214186; Sat,  9 Oct 1999 04:13:44 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157543AbPJIBdW>;
	Fri, 8 Oct 1999 21:33:22 -0400
Received: by vger.rutgers.edu id <S157114AbPJHXMj>;
	Fri, 8 Oct 1999 19:12:39 -0400
Received: from m22-nsv1-trogon.tch.cableol.net ([194.168.16.22]:1498 "EHLO
        caramon.armlinux.org.uk") by vger.rutgers.edu with ESMTP
	id <S160550AbPJHWj1>; Fri, 8 Oct 1999 18:39:27 -0400
Received: from raistlin.armlinux.org.uk (linux@raistlin [192.168.0.3])
	by caramon.armlinux.org.uk (8.8.7/8.8.7) with ESMTP id XAA29383
	for <linux-arm@vger.rutgers.edu>; Fri, 8 Oct 1999 23:39:19 +0100
From: linux@arm.linux.org.uk
Received: (from linux@localhost) by raistlin.armlinux.org.uk (8.7.4/8.7.3) id XAA07726 for linux-arm@vger.rutgers.edu; Fri, 8 Oct 1999 23:37:42 +0100
Message-Id: <199910082237.XAA07726@raistlin.armlinux.org.uk>
Subject: Re: Web Problem Report Form (Can't even test-boot kernel under RISC OS 4)
To: linux-arm@vger.rutgers.edu
Date:   Fri, 8 Oct 1999 23:37:42 +0100 (BST)
In-Reply-To: <Pine.LNX.3.93.991008203114.296A-100000@apocalypse.paradise> from "Ian Jeffray" at Oct 8, 99 08:35:17 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Ian Jeffray writes:
> I do recall some changes to PipeFS since 3.7, but I don't really see how
> such a fundamental mistake can have been made.

The response I got from Matthew Bullock was:
-> I am not aware of any changes to PipeFS in RO4. That does not preclude
-> the possibility that Acorn broke it before we got it...

To check out the problem, someone may want to try the following basic
program:

10 SYS"OS_Find",&86,"Pipe:$.C_Debug.xxxx","" TO F%
20 BPUT#F%,0
30 CLOSE#F%
40 *EX Pipe:$
40 *EX Pipe:$.C_Debug

You should end up with the following output:

Dir. Pipe:$ Option 00 (Off)
CSD  Pipe:"Unset"
Lib. Pipe:"Unset"
URD  Pipe:"Unset"
C_Debug      DWR/    Directory 23:23:39 08-Oct-1999    1  byte
Dir. Pipe:$.C_Debug Option 00 (Off)
CSD  Pipe:"Unset"
Lib. Pipe:"Unset"
URD  Pipe:"Unset"
xxxx         WR/     Data      23:23:39 08-Oct-1999    1  byte

Can someone try this ASAP and report back 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' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sat Oct  9 04:54:24 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id EAA13202
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sat, 9 Oct 1999 04:54:23 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id AE9D8142D9; Sat,  9 Oct 1999 05:54:22 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157084AbPJIAdP>;
	Fri, 8 Oct 1999 20:33:15 -0400
Received: by vger.rutgers.edu id <S157478AbPJHUuE>;
	Fri, 8 Oct 1999 16:50:04 -0400
Received: from proxy4.ba.best.com ([206.184.139.15]:4820 "EHLO
        proxy4.ba.best.com") by vger.rutgers.edu with ESMTP
	id <S157355AbPJHTWQ>; Fri, 8 Oct 1999 15:22:16 -0400
Received: from mmtdave (ppp-206-170-2-227.sntc01.pacbell.net [206.170.2.227])
	by proxy4.ba.best.com (8.9.3/8.9.2/best.out) with SMTP id MAA22535;
	Fri, 8 Oct 1999 12:16:01 -0700 (PDT)
Message-ID: <002e01bf11c1$23ea9640$4df63cd1@mmtdave>
From: "Tony Xu" <tonyx@millentek.com>
To: "Vasant Ramasubramanian" <vasantr@utdallas.edu>
Cc: <linux-arm@vger.rutgers.edu>
Subject: Re: Brutus Woes, any help?
Date:   Fri, 8 Oct 1999 12:12:48 -0700
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.3110.1
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing




>
>
>On Thu, 7 Oct 1999, Tony Xu wrote:
>
>> Hi-- you were right about the switch 14 problem causing
>> 7 on the numeric LED. We configured our switch and now
>> can communicate via angelboot and have boot linux on
>> the brutus.  What hung us up before was a bad zImage due
>> to a badly applied (or wrong) patch file.
>>    Dave
>
>And I just got the sample programs to run. I talked to Intel, apparently
>that is a mistake in the documentation (SW14 DOT/NO DOT) and they know
>about it. Also they said that Angel isn't setup to use DRAM, so if you
>want to use the DRAM on Brutus you have to write code to configure the
>memory controller; I'm making this point because the documentation for
>Brutus simply states you can use SRAM or DRAM but doesn't say that Angel
>is only setup to use SRAM...
>
>BW: The SW14 default should be NO dot meaning *SRAM* is used.
>
>When putting Linux into Brutus, do you have to mess with SW21/22 at all?
>(I.e. which bank of Flash, etc?).
>
>Vasant.
>

Sorry for not replying sooner. Very interesting about the switch 14 thing. I
hope
you have gotten to the thing to boot right now. We don't mess with sw21/22
at
all, they are both set to dot. I don't think flash is involved in this at
all, angle
just plunks the stuff down into ram and hands it control. If you want to
mess
with flash, u need to download the flash management utility, give it control
and then flash the stuff thru that.
  Dave


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sat Oct  9 06:26:49 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id GAA15677
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sat, 9 Oct 1999 06:26:49 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 0FCB4142E1; Sat,  9 Oct 1999 07:26:47 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157181AbPJIEBS>;
	Sat, 9 Oct 1999 00:01:18 -0400
Received: by vger.rutgers.edu id <S157534AbPJIAs6>;
	Fri, 8 Oct 1999 20:48:58 -0400
Received: from tazenda.demon.co.uk ([158.152.220.239]:1908 "EHLO
        kings-cross.london.uk.eu.org") by vger.rutgers.edu with ESMTP
	id <S157123AbPJHV1s>; Fri, 8 Oct 1999 17:27:48 -0400
Received: from localhost
	([127.0.0.1] helo=kings-cross.london.uk.eu.org ident=phil)
	by kings-cross.london.uk.eu.org with esmtp (Exim 2.05 #1)
	id 11ZhX2-0000D2-00; Fri, 8 Oct 1999 22:26:28 +0100
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: Francois Desloges <fd@vipswitch.com>
Cc: linux-arm@vger.rutgers.edu
Subject: Re: bios 1.05 questions 
In-Reply-To: Message from Francois Desloges <fd@vipswitch.com> 
   of "Fri, 08 Oct 1999 10:49:01 EDT." <9910081232550I.14871@dual> 
References: <9910081232550I.14871@dual> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date:   Fri, 08 Oct 1999 22:26:28 +0100
From: Philip Blundell <Philip.Blundell@pobox.com>
Message-Id: <E11ZhX2-0000D2-00@kings-cross.london.uk.eu.org>
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

>I guess 'elf32arm' should be changed by one of:=20
>	armelf_linux
>	armelf_linux26
>	armelf                                                               

>What are the differences between these 3 values and which one should be used
>with all binutils-2.9.5.x ?

There is very little difference.  The linker scripts for the three emulations 
vary slightly but that's all.  For ARM GNU/Linux you always want 
`armelf_linux', or `armelf_linux26' for 26-bit hardware.

>Why not put a new OUTPUT_FORMAT() base on a derivative of "armelf"?

Actually, for the new linker the OUTPUT_FORMAT name would have to be 
`elf32-littlearm'.  Adding a line like that would be benign but useless --
the default is to use an appropriate format anyway.

p.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sat Oct  9 08:20:46 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id IAA18734
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sat, 9 Oct 1999 08:20:46 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 38B8314255; Sat,  9 Oct 1999 09:20:38 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157029AbPJIHGd>;
	Sat, 9 Oct 1999 03:06:33 -0400
Received: by vger.rutgers.edu id <S156868AbPJIHD7>;
	Sat, 9 Oct 1999 03:03:59 -0400
Received: from smtp.mail.big-orange.net ([143.179.236.32]:43966 "EHLO
        Lesothosaurus.big-orange.net") by vger.rutgers.edu with ESMTP
	id <S157355AbPJIFvy>; Sat, 9 Oct 1999 01:51:54 -0400
Received: from jtalen ([143.179.153.44]) by Lesothosaurus.big-orange.net
          (Netscape Messaging Server 3.6)  with SMTP id AAA4EA8;
          Sat, 9 Oct 1999 07:51:35 +0200
MIME-Version: 1.0
From: "John Talen @ GiroNet" <John.Talen@gironet.nl>
To: <linux@arm.linux.org.uk>
Cc: linux-arm@vger.rutgers.edu
Date:   Sat, 09 Oct 1999 07:29:15 +0200
Subject: Re: Web Problem Report Form (Can't even test-boot kernel under RISC OS 4)
Message-ID: <494e23b38dJohn.Talen@gironet.nl>
In-Reply-To: <199910082237.XAA07726@raistlin.armlinux.org.uk>
References: <Pine.LNX.3.93.991008203114.296A-100000@apocalypse.paradise> <199910082237.XAA07726@raistlin.armlinux.org.uk>
User-Agent: Pluto/0.49a (RISC-OS/4.02) POPstar/2.01b12
Content-Type: text/plain
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

> 10 SYS"OS_Find",&86,"Pipe:$.C_Debug.xxxx","" TO F%
> 20 BPUT#F%,0
> 30 CLOSE#F%
> 40 *EX Pipe:$
> 40 *EX Pipe:$.C_Debug

> You should end up with the following output:

> Dir. Pipe:$ Option 00 (Off)
> CSD  Pipe:"Unset"
> Lib. Pipe:"Unset"
> URD  Pipe:"Unset"
> C_Debug      DWR/    Directory 23:23:39 08-Oct-1999    1  byte
> Dir. Pipe:$.C_Debug Option 00 (Off)
> CSD  Pipe:"Unset"
> Lib. Pipe:"Unset"
> URD  Pipe:"Unset"
> xxxx         WR/     Data      23:23:39 08-Oct-1999    1  byte
Done it:(after changing the second 40 into 50!)

*ram
*articl
Dir. Pipe:$ Option 00 (Off) 
CSD  Pipe:"Unset"
Lib. Pipe:"Unset"
URD  Pipe:"Unset"
C_Debug      DWR/    Directory 07:24:27 09-Oct-1999    1  byte 
Dir. Pipe:$.C_Debug Option 00 (Off) 
CSD  Pipe:"Unset"
Lib. Pipe:"Unset"
URD  Pipe:"Unset"
xxxx         WR/     Data      07:24:27 09-Oct-1999    1  byte 
*
*fx0
RISC OS 4.02 (10 Aug 1999)
*help romp.
==> Help on keyword ROMPatch
Syntax: ROMPatch <address> <old contents> <new contents> | -f[ile]
<filename>
==> Help on keyword ROMPatch
Module is: ROMPatch        0.01 (27 Jul 1999)

Commands provided:
ROMPatch
*

-- 
Error : buffer overflow !

signature removed !
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sat Oct  9 18:35:31 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id SAA03424
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sat, 9 Oct 1999 18:35:31 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 1781C14255; Sat,  9 Oct 1999 19:35:30 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156767AbPJIRd3>;
	Sat, 9 Oct 1999 13:33:29 -0400
Received: by vger.rutgers.edu id <S156889AbPJIRay>;
	Sat, 9 Oct 1999 13:30:54 -0400
Received: from relay3.mail.uk.psi.net ([154.32.109.6]:40249 "EHLO
        relay3.mail.uk.psi.net") by vger.rutgers.edu with ESMTP
	id <S156824AbPJIR3s>; Sat, 9 Oct 1999 13:29:48 -0400
Received: from morrison.empeg.co.uk ([193.119.19.130] helo=empeg.com)
	by relay3.mail.uk.psi.net with esmtp (Exim 2.12 #2)
	id 11a0JU-0000qB-00
	for linux-arm@vger.rutgers.edu; Sat, 9 Oct 1999 18:29:44 +0100
Received: from deneb (deneb.internal.empeg.com [10.1.1.42])
	by empeg.com (8.8.7/8.8.7) with SMTP id SAA06151
	for <linux-arm@vger.rutgers.edu>; Sat, 9 Oct 1999 18:29:24 +0100
Message-ID: <05e901bf127c$35e0c1b0$2a01010a@internal.empeg.com>
From: "Mike Crowe" <mac@empeg.com>
To: <linux-arm@vger.rutgers.edu>
Subject: gcc 2.95.2/binutils 2.9.5.0.14 won't configure glibc-2.1.2
Date:   Sat, 9 Oct 1999 18:32:07 +0100
Organization: empeg ltd
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 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

After discussing gcc versions with Chris Rutter at the UK Linux Expo I
decided to give gcc 2.95 a whirl with binutils-2.9.5.0.14. I wanted to
build it completely from scratch rather than use any part of my previous
egcs-1.1.2+philb patches install so I needed to use the
inhibit_libc/threads hack but gcc appeared to compile and install
correctly - my usual method of not bothering to do this but using the fact
that enough of the compiler was actually built by the time it bombed out
doesn't seem to work anymore :-(

It seems that quite a lot of stuff has changed and I was first worried by
the following message when I tried to configure glibc-2.1.2.

checking for ld --version-script... no
*** WARNING: You should not compile GNU libc without versioning. Not using
*** versioning will introduce incompatibilities so that old binaries
*** will not run anymore.
*** For versioning you need recent binutils (binutils-2.8.1.0.23 or
newer).

The config.log contains:

configure:2312: checking for ld --version-script
configure:2335: arm-empeg-linux-gcc  -shared -o conftest.so
conftest.o -nostartfiles -nostdlib -Wl,-
-version-script,conftest.map 1>&5
/home/mac/empeg-nocvs/gcc295/arm-empeg-linux/bin/ld: cannot represent
machine `arm:amachine.adomain'
collect2: ld returned 1 exit status

It seems that ld is failing rather than the --version-script causing a
problem.

I had a look at the scripts in target/lib/ldscripts and all the _linux
ones seem to contain the output architecture defined as arm:FQDN. I looked
at the equivalent directory for egcs-1.1.2 and everything seems to have
changed rather a lot but all the files just mentioned an output
architecture of arm.

Is this arm:FQDN stuff correct? Should I be looking elsewhere for the root
of the problem?

Also, once I do persuade this to work I assume I have to go right back to
the beginning and compile without the inhibit_libc/threads hack and then
compile glibc again to get threads support.

TIA

--
Mike Crowe

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sun Oct 10 07:42:06 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id HAA25233
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sun, 10 Oct 1999 07:42:06 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 0A66514056; Sun, 10 Oct 1999 08:41:52 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156745AbPJJGlO>;
	Sun, 10 Oct 1999 02:41:14 -0400
Received: by vger.rutgers.edu id <S156736AbPJJGkp>;
	Sun, 10 Oct 1999 02:40:45 -0400
Received: from ns0.utdallas.edu ([129.110.10.1]:51142 "HELO ns0.utdallas.edu")
	by vger.rutgers.edu with SMTP id <S156723AbPJJGk3>;
	Sun, 10 Oct 1999 02:40:29 -0400
Received: from apache.utdallas.edu (apache.utdallas.edu [129.110.16.9])
	by ns0.utdallas.edu (Postfix) with ESMTP
	id 4235C19FFDE; Sun, 10 Oct 1999 01:40:31 -0500 (CDT)
Received: from localhost (vasantr@localhost)
	by apache.utdallas.edu (8.9.1/8.9.1) with SMTP id BAA29074;
	Sun, 10 Oct 1999 01:40:40 -0500 (CDT)
X-Authentication-Warning: apache.utdallas.edu: vasantr owned process doing -bs
Date:   Sun, 10 Oct 1999 01:40:40 -0500 (CDT)
From: Vasant Ramasubramanian <vasantr@utdallas.edu>
To: sa1100-linux@pa.dec.com
Cc: linux-arm@vger.rutgers.edu
Subject: Brutus Info
In-Reply-To: <002e01bf11c1$23ea9640$4df63cd1@mmtdave>
Message-ID: <Pine.GSO.3.96.991010012805.28280A-100000@apache.utdallas.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Actually looking over the spread of documentation for Brutus, I found that
the version of Angel that runs on Brutus uses *DRAM* and not SRAM. This
means that the switch (14) that choose between SRAM / DRAM on the Brutus
board is correct as marked in the documentation, however Angel isn't
configured for SRAM usage. 

I'm sending an e-mail because the Intel representative I spoke to simply
stated that "S14 is opposite of what's in the documentation." That's not
correct, the *default* value should be opposite(use DRAM instead of SRAM),
yet SW14 maintains the exact same functionality as marked in the
documentation. 

Understandably, this more than likely won't matter too much if you want to
get Linux going; it's a heads up for those of us who might be doing more /
different things.

Also, has anyone soldered in the 1Mx16 Flash parts and gotten it to work?

Thanks, Vasant.

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sun Oct 10 10:56:00 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id KAA30843
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sun, 10 Oct 1999 10:56:00 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 4E14C13E41; Sun, 10 Oct 1999 11:55:58 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156763AbPJJJzZ>;
	Sun, 10 Oct 1999 05:55:25 -0400
Received: by vger.rutgers.edu id <S156745AbPJJJy5>;
	Sun, 10 Oct 1999 05:54:57 -0400
Received: from tazenda.demon.co.uk ([158.152.220.239]:2495 "EHLO
        kings-cross.london.uk.eu.org") by vger.rutgers.edu with ESMTP
	id <S156736AbPJJJys>; Sun, 10 Oct 1999 05:54:48 -0400
Received: from localhost
	([127.0.0.1] helo=kings-cross.london.uk.eu.org ident=phil)
	by kings-cross.london.uk.eu.org with esmtp (Exim 2.05 #1)
	id 11aFfo-0006o5-00; Sun, 10 Oct 1999 10:53:48 +0100
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: "Mike Crowe" <mac@empeg.com>
Cc: linux-arm@vger.rutgers.edu
Subject: Re: gcc 2.95.2/binutils 2.9.5.0.14 won't configure glibc-2.1.2 
In-Reply-To: Message from "Mike Crowe" <mac@empeg.com> 
   of "Sat, 09 Oct 1999 18:32:07 BST." <05e901bf127c$35e0c1b0$2a01010a@internal.empeg.com> 
References: <05e901bf127c$35e0c1b0$2a01010a@internal.empeg.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date:   Sun, 10 Oct 1999 10:53:48 +0100
From: Philip Blundell <Philip.Blundell@pobox.com>
Message-Id: <E11aFfo-0006o5-00@kings-cross.london.uk.eu.org>
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

>Is this arm:FQDN stuff correct? Should I be looking elsewhere for the root
>of the problem?

No, I don't think this is correct.  Can you tell where it crept in?

>Also, once I do persuade this to work I assume I have to go right back to
>the beginning and compile without the inhibit_libc/threads hack and then
>compile glibc again to get threads support.

Yes.

p.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sun Oct 10 13:39:27 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id NAA02506
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sun, 10 Oct 1999 13:39:26 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 3A10213DED; Sun, 10 Oct 1999 14:39:25 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156765AbPJJMiv>;
	Sun, 10 Oct 1999 08:38:51 -0400
Received: by vger.rutgers.edu id <S156745AbPJJMid>;
	Sun, 10 Oct 1999 08:38:33 -0400
Received: from finch-post-10.mail.demon.net ([194.217.242.38]:2191 "EHLO
        finch-post-10.mail.demon.net") by vger.rutgers.edu with ESMTP
	id <S156736AbPJJMi2>; Sun, 10 Oct 1999 08:38:28 -0400
Received: from nedman.demon.co.uk ([158.152.8.32] helo=nedman)
	by finch-post-10.mail.demon.net with smtp (Exim 2.12 #1)
	id 11aIF8-000DgU-0A
	for linux-arm@vger.rutgers.edu; Sun, 10 Oct 1999 12:38:26 +0000
MIME-Version: 1.0
From: Chris Gransden <chrisg@nedman.demon.co.uk>
To: linux-arm@vger.rutgers.edu
Date:   Sun, 10 Oct 1999 13:38:13 +0100
Subject: Ilegal instruction starting RiscPC Xserver
Message-ID: <494eced0bbchrisg@nedman.demon.co.uk>
User-Agent: Pluto/1.12t (RISC-OS/4.02)
Content-Type: text/plain
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

I get the following straight after running startx,


X Version 11 Release 6 X Window System
(Protocol Version 11, revision 0, vendor release 6000)
Operating system: linux 
Using VT 7
Server: support for 2 16 256 colors
Screen: 1024 by 768 pixels, 256 colour

Xserver internal failure: signal 4 (Illegal instruction).

XIO:  fatal IO error 104 (Connection reset by peer) on X server ":0.0"
      after 0 requests (0 known processed) with 0 events remaining.
abort from 0x2000903c


I get this with both 2.2.12-rmk1 and 2.3.19-rmk1.

Chris.

-- 
Email: chrisg@nedman.demon.co.uk
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sun Oct 10 16:58:40 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id QAA07906
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sun, 10 Oct 1999 16:58:40 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id F0FF413DED; Sun, 10 Oct 1999 17:58:38 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156767AbPJJP6J>;
	Sun, 10 Oct 1999 11:58:09 -0400
Received: by vger.rutgers.edu id <S156736AbPJJP5w>;
	Sun, 10 Oct 1999 11:57:52 -0400
Received: from oskar.nanoteq.co.za ([196.37.91.10]:4297 "EHLO
        oskar.nanoteq.co.za") by vger.rutgers.edu with ESMTP
	id <S156805AbPJJP5P>; Sun, 10 Oct 1999 11:57:15 -0400
Received: from craul.nanoteq.co.za (IDENT:chris@craul.nanoteq.co.za [196.37.91.24])
	by oskar.nanoteq.co.za (8.9.0/8.9.0) with ESMTP id SAA05961
	for <linux-arm@vger.rutgers.edu>; Sun, 10 Oct 1999 18:00:12 +0200 (SAT)
Message-ID: <3800EFA6.5842F6C3@craul.nanoteq.co.za>
Date:   Sun, 10 Oct 1999 17:57:26 -0200
From: Chris Bohme <chris@craul.nanoteq.co.za>
Reply-To: cbo@nanoteq.co.za
Organization: Nanoteq
X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.2.10 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: linux-arm <linux-arm@vger.rutgers.edu>
Subject: TFTP bootloader with dec21041
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Hi,

I have tried to boot linux with russell's bootloader via tftp using the
DEC 21041 card.
The boot process hangs in dec21041.c in  nd_21041_open(), patiently
spinning on  'while (transdesc[0] & 0x80000000);' and waiting for a
response from the hardware. I tried two working cards and experienced
the same problems.

Any ides ?
Anyone got any more info on the card ?

Regards,
Chris

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sun Oct 10 20:43:09 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id UAA14143
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sun, 10 Oct 1999 20:43:09 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 7B64613E37; Sun, 10 Oct 1999 21:43:08 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156823AbPJJTmj>;
	Sun, 10 Oct 1999 15:42:39 -0400
Received: by vger.rutgers.edu id <S156767AbPJJTlk>;
	Sun, 10 Oct 1999 15:41:40 -0400
Received: from oracle.clara.net ([195.8.69.94]:2725 "EHLO oracle.clara.net")
	by vger.rutgers.edu with ESMTP id <S156765AbPJJTkz>;
	Sun, 10 Oct 1999 15:40:55 -0400
Received: from [212.126.132.90] (helo=tardis)
	by oracle.clara.net with esmtp (Exim 2.12 #2)
	id 11aOoe-0002zI-00; Sun, 10 Oct 1999 20:39:32 +0100
Date:   Sun, 10 Oct 1999 20:34:27 +0100 (BST)
From: Dave Gilbert <gilbertd@treblig.org>
X-Sender: gilbertd@tardis.home.dave
To: cbo@nanoteq.co.za
Cc: linux-arm <linux-arm@vger.rutgers.edu>
Subject: Re: TFTP bootloader with dec21041
In-Reply-To: <3800EFA6.5842F6C3@craul.nanoteq.co.za>
Message-ID: <Pine.LNX.4.10.9910102020590.537-100000@tardis.home.dave>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

On Sun, 10 Oct 1999, Chris Bohme wrote:

> Hi,
> 
> I have tried to boot linux with russell's bootloader via tftp using the
> DEC 21041 card.
> The boot process hangs in dec21041.c in  nd_21041_open(), patiently
> spinning on  'while (transdesc[0] & 0x80000000);' and waiting for a
> response from the hardware. I tried two working cards and experienced
> the same problems.

This is a bootloader for what type of system - lets guess an EBSA285 ?
The data sheet for the 21041 (and its cousins) were on DECs web site - but
that was when DEC was DEC, I suspect they are still around there
somewhere.

Now as for why you've got the problem - that top bit is an ownership bit -
the computer sets the bit thus giving the tulip a job to do, when it has
finished it should clear it.  The fact that it is getting stuck there
means the tulip is never doing the job.

Get hold of the docs, and then check for tulip error conditions etc before
the loop.

Dave

-- 
 --------------------------------------------------------------------   
/ Dr. David Alan Gilbert      | Running Linux on           |  Happy  \ 
\   gro.gilbert @ treblig.org |  Alpha, x86, ARM and SPARC |  In Hex /
 ____________________________|___ http://www.treblig.clara.net   __/

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sun Oct 10 22:21:14 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id WAA16947
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sun, 10 Oct 1999 22:21:14 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 89AF613D9B; Sun, 10 Oct 1999 23:21:12 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156778AbPJJVUt>;
	Sun, 10 Oct 1999 17:20:49 -0400
Received: by vger.rutgers.edu id <S156765AbPJJVUl>;
	Sun, 10 Oct 1999 17:20:41 -0400
Received: from m58-nsv3-trogon.tch.cableol.net ([194.168.16.208]:3336 "EHLO
        caramon.armlinux.org.uk") by vger.rutgers.edu with ESMTP
	id <S156763AbPJJVUb>; Sun, 10 Oct 1999 17:20:31 -0400
Received: from raistlin.armlinux.org.uk (linux@raistlin [192.168.0.3])
	by caramon.armlinux.org.uk (8.8.7/8.8.7) with ESMTP id RAA05124;
	Sun, 10 Oct 1999 17:25:44 +0100
From: linux@arm.linux.org.uk
Received: (from linux@localhost) by raistlin.armlinux.org.uk (8.7.4/8.7.3) id RAA06650; Sun, 10 Oct 1999 17:24:31 +0100
Message-Id: <199910101624.RAA06650@raistlin.armlinux.org.uk>
Subject: Re: Ilegal instruction starting RiscPC Xserver
To: chrisg@nedman.demon.co.uk (Chris Gransden)
Date:   Sun, 10 Oct 1999 17:24:30 +0100 (BST)
Cc: linux-arm@vger.rutgers.edu
In-Reply-To: <494eced0bbchrisg@nedman.demon.co.uk> from "Chris Gransden" at Oct 10, 99 01:38:13 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Chris Gransden writes:
> Xserver internal failure: signal 4 (Illegal instruction).
> I get this with both 2.2.12-rmk1 and 2.3.19-rmk1.

Do you have either nwfpe or the FPE module loaded?
   _____
  |_____| ------------------------------------------------- ---+---+-
  |   |        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' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sun Oct 10 23:56:10 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id XAA21120
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sun, 10 Oct 1999 23:56:10 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 0639313E4C; Mon, 11 Oct 1999 00:56:09 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156805AbPJJWvS>;
	Sun, 10 Oct 1999 18:51:18 -0400
Received: by vger.rutgers.edu id <S156781AbPJJWvH>;
	Sun, 10 Oct 1999 18:51:07 -0400
Received: from relay4.mail.uk.psi.net ([154.32.111.6]:33749 "EHLO
        relay4.mail.uk.psi.net") by vger.rutgers.edu with ESMTP
	id <S156763AbPJJWiS>; Sun, 10 Oct 1999 18:38:18 -0400
Received: from morrison.empeg.co.uk ([193.119.19.130] helo=empeg.com)
	by relay4.mail.uk.psi.net with esmtp (Exim 2.12 #2)
	id 11aRZK-00034c-00
	for linux-arm@vger.rutgers.edu; Sun, 10 Oct 1999 23:35:54 +0100
Received: (from mac@localhost)
	by empeg.com (8.8.7/8.8.7) id XAA22796
	for linux-arm@vger.rutgers.edu; Sun, 10 Oct 1999 23:38:04 +0100
Date:   Sun, 10 Oct 1999 23:38:04 +0100
From: Mike Crowe <mac@empeg.com>
To: linux-arm@vger.rutgers.edu
Subject: Re: gcc 2.95.2/binutils 2.9.5.0.14 won't configure glibc-2.1.2
Message-ID: <19991010233804.B13382@fatboy.internal.empeg.com>
References: <05e901bf127c$35e0c1b0$2a01010a@internal.empeg.com> <mac@empeg.com> <E11aFfo-0006o5-00@kings-cross.london.uk.eu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.1i
In-Reply-To: <E11aFfo-0006o5-00@kings-cross.london.uk.eu.org>; from Philip Blundell on Sun, Oct 10, 1999 at 10:53:48AM +0100
X-Operating-System: Linux 2.2.12 i686
X-Webpage: http://www.empeg.com/
X-Sending-Host: fatboy.internal.empeg.com
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

On Sun, Oct 10, 1999 at 10:53:48AM +0100, Philip Blundell wrote:
> >Is this arm:FQDN stuff correct? Should I be looking elsewhere for the root
> >of the problem?
> 
> No, I don't think this is correct.  Can you tell where it crept in?

It just dawned on me that I replied only to Phil about this. In case
anyone is intinterested it was due to me having an environment
variable exported from my shell called MACHINE.

-- 
Mike Crowe
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Mon Oct 11 18:58:01 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id SAA28975
	for <linux-arm-archive@lists.arm.linux.org.uk>; Mon, 11 Oct 1999 18:58:01 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 2CE1613DC6; Mon, 11 Oct 1999 19:57:53 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157155AbPJKRrw>;
	Mon, 11 Oct 1999 13:47:52 -0400
Received: by vger.rutgers.edu id <S157013AbPJKRn4>;
	Mon, 11 Oct 1999 13:43:56 -0400
Received: from [194.201.77.34] ([194.201.77.34]:34336 "HELO
        fw-maid.maidenhead.arm.com") by vger.rutgers.edu with SMTP
	id <S157128AbPJKRVk>; Mon, 11 Oct 1999 13:21:40 -0400
Received: by fw-maid.maidenhead.arm.com; id TAA02552; Mon, 11 Oct 1999 19:22:07 +0100
Received: from unknown(192.168.2.10) by fw-maid.maidenhead.arm.com via smap (V5.0)
	id xma002548; Mon, 11 Oct 99 19:21:28 +0100
Received: from arm.com (dhcp14 [192.168.2.174])
	by mhsun1.maidenhead.arm.com (8.9.3/8.9.3) with ESMTP id SAA25117;
	Mon, 11 Oct 1999 18:20:08 +0100 (BST)
Message-ID: <3802205B.CC7D7781@arm.com>
Date:   Mon, 11 Oct 1999 18:37:31 +0100
From: David Rusling <david.rusling@arm.com>
X-Mailer: Mozilla 4.5 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Russell King - ARM Linux Admin <linux@arm.linux.org.uk>
Cc: linux-arm@vger.rutgers.edu
Subject: ARM720/Integrator - more help/hints wanted/needed
References: <199909231453.PAA18249@flint.armlinux.org.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

All,

    thanks for your responses, I'm getting a little further.   One useful
avenue is to boot a shell, in this case ash.static.   This gives me a '#'
prompt.    I only had to write an interrupt driven serial device driver and
(hey presto) I've got something that is responding to commands (well, sort
of).   This got me pretty excited on Friday.

    The big issue that I have is that no commands actually return.   So,
for example, if I launch a new ash.static, I can use it's internal commands
but if I exit, well I never see a prompt from the original ash.static.   I
have
a statically linked "hello world" program too and that never comes back
(it should just print 'hello cruel world' and exit).   I light the amber LED
when the idle task is running and it doesn't relight (normally, it's lit when
ash is waiting for input).  Does this mean that something is making the
system busy?  It (the kernel) can be found in or near the signal code
when I stop the box and peek.  What would stop signals working?
Could it be the terminal driver?   It seems happy, characters are echoed
but nothing is done about them (shell not now really running?).

    Shared libraries just plain don't work.   It's maybe the above problem
but I've fixed at least one problem with the ROM FS (it never returned
an error if genuinely couldn't find a file).   The shared library loaded
claims that I have 'invalid ELF libraries'.   Soft links stuffed?   Maybe but
it gets /dev/console right - that's a soft link to /dev/tty0.  I guess that I
could use a ramdisk at startup.   Way back though, I think that I was
having the same problems.

    OK, so I though, it's caches.    I checked out the cache flushing
code with a _fine_ toothcomb and (in the end) I turned the caches off
(720 has a unified I and D cache of 8K) - no change.

    Oh, and the SCSI disk that I have is OSF formatted (ie alpha Linux)
with 3 partitions.  The ncr810 code recognises all of this but cannot find
an ext2 filesystem on the second partition, /dev/sda2.

    Going back to /sbin/init - that crashes the system somewhere in
setscheduler()
with r2 corrupted (I think).   Why is setscheduler() being called?

    Any hints appreciated.

Dave

----------------------------------------------------------------------
David A Rusling   Consulting Engineer
    ARM Limited
    Liberty House,
    Moorbridge Road,
    Maidenhead, SL6 8LT

    Tel: UK-(0)1628-427754
    Fax: UK-(0)1628-780551
    e-mail: david.rusling@arm.com
----------------------------------------------------------------------


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Mon Oct 11 19:17:21 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id TAA29582
	for <linux-arm-archive@lists.arm.linux.org.uk>; Mon, 11 Oct 1999 19:17:21 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 7B17613FC3; Mon, 11 Oct 1999 20:17:19 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156947AbPJKSFP>;
	Mon, 11 Oct 1999 14:05:15 -0400
Received: by vger.rutgers.edu id <S156778AbPJKRyS>;
	Mon, 11 Oct 1999 13:54:18 -0400
Received: from finch-post-12.mail.demon.net ([194.217.242.41]:1528 "EHLO
        finch-post-12.mail.demon.net") by vger.rutgers.edu with ESMTP
	id <S156904AbPJKRqF>; Mon, 11 Oct 1999 13:46:05 -0400
Received: from nedman.demon.co.uk ([158.152.8.32] helo=nedman)
	by finch-post-12.mail.demon.net with smtp (Exim 2.12 #1)
	id 11ajWQ-0004WS-0C
	for linux-arm@vger.rutgers.edu; Mon, 11 Oct 1999 17:46:06 +0000
MIME-Version: 1.0
From: Chris Gransden <chrisg@nedman.demon.co.uk>
To: linux-arm@vger.rutgers.edu
Date:   Mon, 11 Oct 1999 18:33:57 +0100
Subject: Re: Ilegal instruction starting RiscPC Xserver
Message-ID: <494f6db9f4chrisg@nedman.demon.co.uk>
In-Reply-To: <199910101624.RAA06650@raistlin.armlinux.org.uk>
References: <494eced0bbchrisg@nedman.demon.co.uk> <199910101624.RAA06650@raistlin.armlinux.org.uk>
User-Agent: Pluto/1.12t (RISC-OS/4.02)
Content-Type: text/plain
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

In article <199910101624.RAA06650@raistlin.armlinux.org.uk>,
   <linux@arm.linux.org.uk> wrote:
> Chris Gransden writes:
> > Xserver internal failure: signal 4 (Illegal instruction).
> > I get this with both 2.2.12-rmk1 and 2.3.19-rmk1.

> Do you have either nwfpe or the FPE module loaded?

I've got nwfpe compiled into the kernel. I get "NetWinder Floating Point
Emulator V0.95 (c) 1998-1999 Rebel.com" in the boot messages. I haven't
had the error from any others programs.

Chris.

-- 
Email: chrisg@nedman.demon.co.uk
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Mon Oct 11 19:26:23 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id TAA29892
	for <linux-arm-archive@lists.arm.linux.org.uk>; Mon, 11 Oct 1999 19:26:23 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id DC8CA14034; Mon, 11 Oct 1999 20:26:21 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156995AbPJKSRg>;
	Mon, 11 Oct 1999 14:17:36 -0400
Received: by vger.rutgers.edu id <S157031AbPJKSLO>;
	Mon, 11 Oct 1999 14:11:14 -0400
Received: from m38-nsv3-trogon.tch.cableol.net ([194.168.16.188]:3600 "EHLO
        caramon.armlinux.org.uk") by vger.rutgers.edu with ESMTP
	id <S156988AbPJKR5p>; Mon, 11 Oct 1999 13:57:45 -0400
Received: from raistlin.armlinux.org.uk (linux@raistlin [192.168.0.3])
	by caramon.armlinux.org.uk (8.8.7/8.8.7) with ESMTP id SAA09701
	for <linux-arm@vger.rutgers.edu>; Mon, 11 Oct 1999 18:56:55 +0100
From: linux@arm.linux.org.uk
Received: (from linux@localhost) by raistlin.armlinux.org.uk (8.7.4/8.7.3) id SAA13765 for linux-arm@vger.rutgers.edu; Mon, 11 Oct 1999 18:55:37 +0100
Message-Id: <199910111755.SAA13765@raistlin.armlinux.org.uk>
Subject: Me
To: linux-arm@vger.rutgers.edu
Date:   Mon, 11 Oct 1999 18:55:37 +0100 (BST)
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

I shall be away from my mail for a few days since I'm going to be in
Preston on business (oh joy of joys).

This means I won't be responding to any emails from today onwards.  I
shall reply once I'm back.

Thanks for waiting.
   _____
  |_____| ------------------------------------------------- ---+---+-
  |   |        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' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Tue Oct 12 00:25:17 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id AAA06665
	for <linux-arm-archive@lists.arm.linux.org.uk>; Tue, 12 Oct 1999 00:25:16 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 9903314030; Tue, 12 Oct 1999 01:25:15 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156904AbPJKXCl>;
	Mon, 11 Oct 1999 19:02:41 -0400
Received: by vger.rutgers.edu id <S156944AbPJKWlk>;
	Mon, 11 Oct 1999 18:41:40 -0400
Received: from tazenda.demon.co.uk ([158.152.220.239]:1297 "EHLO
        kings-cross.london.uk.eu.org") by vger.rutgers.edu with ESMTP
	id <S157138AbPJKWlI>; Mon, 11 Oct 1999 18:41:08 -0400
Received: from localhost
	([127.0.0.1] helo=kings-cross.london.uk.eu.org ident=phil)
	by kings-cross.london.uk.eu.org with esmtp (Exim 2.05 #1)
	id 11ao7Y-0000Vu-00; Mon, 11 Oct 1999 23:40:44 +0100
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: Chris Gransden <chrisg@nedman.demon.co.uk>
Cc: linux-arm@vger.rutgers.edu
Subject: Re: Ilegal instruction starting RiscPC Xserver 
In-Reply-To: Message from Chris Gransden <chrisg@nedman.demon.co.uk> 
   of "Mon, 11 Oct 1999 18:33:57 BST." <494f6db9f4chrisg@nedman.demon.co.uk> 
References: <494eced0bbchrisg@nedman.demon.co.uk> <199910101624.RAA06650@raistlin.armlinux.org.uk>  <494f6db9f4chrisg@nedman.demon.co.uk> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date:   Mon, 11 Oct 1999 23:40:42 +0100
From: Philip Blundell <Philip.Blundell@pobox.com>
Message-Id: <E11ao7Y-0000Vu-00@kings-cross.london.uk.eu.org>
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

>Emulator V0.95 (c) 1998-1999 Rebel.com" in the boot messages. I haven't
>had the error from any others programs.

Can you find out what the faulting instruction is?  Either use the debugger if 
you have one, or build a kernel with CONFIG_DEBUG_USER set and use objdump.

p.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Tue Oct 12 02:06:17 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id CAA09524
	for <linux-arm-archive@lists.arm.linux.org.uk>; Tue, 12 Oct 1999 02:06:17 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 8E17B13F1F; Tue, 12 Oct 1999 03:06:15 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156951AbPJLBBF>;
	Mon, 11 Oct 1999 21:01:05 -0400
Received: by vger.rutgers.edu id <S156942AbPJLA4i>;
	Mon, 11 Oct 1999 20:56:38 -0400
Received: from [216.50.211.108] ([216.50.211.108]:2345 "EHLO
        mail.quackware.com") by vger.rutgers.edu with ESMTP
	id <S157261AbPJLAd3>; Mon, 11 Oct 1999 20:33:29 -0400
Received: from quackware.com (IDENT:jon@www.anyprice.com [216.50.211.108])
	by mail.quackware.com (8.9.3/8.9.3) with ESMTP id RAA11032;
	Mon, 11 Oct 1999 17:19:51 -0700
Message-ID: <38027EA7.8F83BA7D@quackware.com>
Date:   Mon, 11 Oct 1999 17:19:51 -0700
From: Jonathan Kliegman <jon@quackware.com>
Organization: Quackware
X-Mailer: Mozilla 4.61 [en] (X11; U; Linux 2.2.12 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: cbo@nanoteq.co.za, linux-arm <linux-arm@vger.rutgers.edu>
Subject: Re: TFTP bootloader with dec21041
References: <3800EFA6.5842F6C3@craul.nanoteq.co.za>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Chris Bohme wrote:
> 
> Hi,
> 
> I have tried to boot linux with russell's bootloader via tftp using the
> DEC 21041 card.
> The boot process hangs in dec21041.c in  nd_21041_open(), patiently
> spinning on  'while (transdesc[0] & 0x80000000);' and waiting for a
> response from the hardware. I tried two working cards and experienced
> the same problems.
> 
> Any ides ?
> Anyone got any more info on the card ?
> 
> Regards,
> Chris
> 
> unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

Try using the tulip.c driver instead.  It is written to take into
account the cache coherency (or lack of) on the StrongARM.  The 'while
(transdesc[0] & 0x80000000);' line looks like it will not work unless
the region of RAM it's reading from is marked uncacheable (which isn't
likely).

-Jon
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Tue Oct 12 09:17:22 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id JAA21016
	for <linux-arm-archive@lists.arm.linux.org.uk>; Tue, 12 Oct 1999 09:17:22 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id CD32713E8D; Tue, 12 Oct 1999 10:17:20 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156938AbPJLIQv>;
	Tue, 12 Oct 1999 04:16:51 -0400
Received: by vger.rutgers.edu id <S156778AbPJLIQk>;
	Tue, 12 Oct 1999 04:16:40 -0400
Received: from mailhost.mipsys.com ([62.161.177.33]:8001 "EHLO [62.161.177.33]")
	by vger.rutgers.edu with ESMTP id <S156942AbPJLIOs>;
	Tue, 12 Oct 1999 04:14:48 -0400
Received: from [192.168.1.10] by [192.168.1.2]
     with SMTP (QuickMail Pro Server for Mac 2.0); 12 OCT 99 10:22:25 UT
In-Reply-To: <38027EA7.8F83BA7D@quackware.com>
X-Mailer: CTM PowerMail 2.4v6 <http://www.ctmdev.com>
x-sender: benh@mailhost.mipsys.com
Date:   Tue, 12 Oct 1999 10:14:34 +0200
To: Jonathan Kliegman <jon@quackware.com>, linux-arm@vger.rutgers.edu
From: Benjamin Herrenschmidt <benh@mipsys.com>
Subject: Re(2): TFTP bootloader with dec21041
Message-Id: <19991012101434.012096@mailhost.mipsys.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

On Mon, Oct 11, 1999, Jonathan Kliegman <jon@quackware.com> wrote:

>Try using the tulip.c driver instead.  It is written to take into
>account the cache coherency (or lack of) on the StrongARM.  The 'while
>(transdesc[0] & 0x80000000);' line looks like it will not work unless
>the region of RAM it's reading from is marked uncacheable (which isn't
>likely).

No, he's not using the Linux kernel, but Russel's bootloader, which runs
with data cache disabled, so this should not be an issue. I should put
your hand on the chip's documentation, you probably lack some kind of
initialisation (do you have a PROM providing the hw eth adress for
example ? If you don't you'll probably have to set it up manually from
the driver).

BenH.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Tue Oct 12 13:42:24 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id NAA28669
	for <linux-arm-archive@lists.arm.linux.org.uk>; Tue, 12 Oct 1999 13:42:24 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id C0D2913DE6; Tue, 12 Oct 1999 14:42:21 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156937AbPJLMlv>;
	Tue, 12 Oct 1999 08:41:51 -0400
Received: by vger.rutgers.edu id <S156790AbPJLMle>;
	Tue, 12 Oct 1999 08:41:34 -0400
Received: from note.orchestra.cse.unsw.EDU.AU ([129.94.242.29]:3140 "HELO
        note.orchestra.cse.unsw.EDU.AU") by vger.rutgers.edu with SMTP
	id <S156864AbPJLMlU>; Tue, 12 Oct 1999 08:41:20 -0400
Received: From paulaner With LocalMail ; Tue, 12 Oct 99 22:21:35 +1000 
From: "Adam 'WeirdArms' Wiggins" <awiggins@cse.unsw.EDU.AU>
To: linux-arm <linux-arm@vger.rutgers.edu>
Date:   Tue, 12 Oct 1999 22:21:35 +1000 (EST)
X-Sender: awiggins@paulaner.disy.cse.unsw.EDU.AU
Subject: SA-1100 cache clean
In-Reply-To: <38027EA7.8F83BA7D@quackware.com>
Message-ID: <Pine.OSF.3.95.991012222031.13114A-100000@paulaner.disy.cse.unsw.EDU.AU>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

	Can anyone point me out to the bit of code that cleans the DCache
for the SA-1100, how many cycles does it take?

	Cheers Adam

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Tue Oct 12 13:58:50 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id NAA29118
	for <linux-arm-archive@lists.arm.linux.org.uk>; Tue, 12 Oct 1999 13:58:50 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 6E5C913EE4; Tue, 12 Oct 1999 14:58:48 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156974AbPJLM6Q>;
	Tue, 12 Oct 1999 08:58:16 -0400
Received: by vger.rutgers.edu id <S156790AbPJLM6E>;
	Tue, 12 Oct 1999 08:58:04 -0400
Received: from relay3.mail.uk.psi.net ([154.32.109.6]:51986 "EHLO
        relay3.mail.uk.psi.net") by vger.rutgers.edu with ESMTP
	id <S157015AbPJLM5L>; Tue, 12 Oct 1999 08:57:11 -0400
Received: from morrison.empeg.co.uk ([193.119.19.130] helo=empeg.com)
	by relay3.mail.uk.psi.net with esmtp (Exim 2.12 #2)
	id 11b1UJ-0007IN-00
	for linux-arm@vger.rutgers.edu; Tue, 12 Oct 1999 13:57:07 +0100
Received: from deneb (deneb.internal.empeg.com [10.1.1.42])
	by empeg.com (8.8.7/8.8.7) with SMTP id NAA02227
	for <linux-arm@vger.rutgers.edu>; Tue, 12 Oct 1999 13:57:16 +0100
Message-ID: <093e01bf14b1$a301bbf0$2a01010a@internal.empeg.com>
From: "Mike Crowe" <mac@empeg.com>
To: <linux-arm@vger.rutgers.edu>
References: <37ECE91E.7ADED48@msoe.edu>
Subject: Re: Problem with gcc (building full toolchain)
Date:   Tue, 12 Oct 1999 13:59:36 +0100
Organization: empeg ltd
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 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Benjamin Stocks wrote:
> Hi in the process of building an cross compiling glibc on an i86 box, I
> realized that I built the cross compiling gcc2.95 wrong so I went back
> to do it right and hit an error. The build appears to run normal for a
> little while and then exits with this error:
>
> make[3]: Entering directory
> `/usr/local/arm/src/gcc-2.95/arm-linux/libiberty'
> make[3]: *** No targets.  Stop.
> make[3]: Leaving directory
> `/usr/local/arm/src/gcc-2.95/arm-linux/libiberty'
> make[2]: *** [../libiberty/libiberty.a] Error 2
> make[2]: Leaving directory
> `/usr/local/arm/src/gcc-2.95/arm-linux/libstdc++'
> make[1]: *** [all-target-libstdc++] Error 2
> make[1]: Leaving directory `/usr/local/arm/src/gcc-2.95'
> make: *** [cross] Error 2

> Looking back from the output of the build I found this line:
>
> configure: error: installation or configuration problem: C compiler
> cannot create executables.

After successfully building a LANGUAGES="c", inhibit_libc gcc-2.95.1
compiler (with glibc) I've gone back and tried to build a full compiler
with C++ and threads support. I'm now seeing this error too.

I've been through the archives and all references to this error say to do
the LANGUAGES="c", inhibit_libc hack which is obviously no use to me. Any
clues as to where else I should be looking?

I'm using the same binutils as I built the hack compiler with and the
following configure line:

./configure --target=arm-empeg-linux --prefix=/home/mac/gcc295 --with-cpu=
strongarm110

--
Mike Crowe
empeg ltd

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Tue Oct 12 15:23:43 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id PAA32021
	for <linux-arm-archive@lists.arm.linux.org.uk>; Tue, 12 Oct 1999 15:23:42 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id E318F13DD8; Tue, 12 Oct 1999 16:23:40 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156983AbPJLOWw>;
	Tue, 12 Oct 1999 10:22:52 -0400
Received: by vger.rutgers.edu id <S156943AbPJLOWi>;
	Tue, 12 Oct 1999 10:22:38 -0400
Received: from sparkle.Generation.NET ([205.205.119.4]:52858 "EHLO
        sparkle.Generation.NET") by vger.rutgers.edu with ESMTP
	id <S157002AbPJLOWR>; Tue, 12 Oct 1999 10:22:17 -0400
Received: from dual (generic253.197.205.205.IN-ADDR.ARPA [205.205.197.253] (may be forged))
	by sparkle.Generation.NET (8.9.3/8.9.3) with SMTP id KAA12323
	for <linux-arm@vger.rutgers.edu>; Tue, 12 Oct 1999 10:22:29 -0400 (EDT)
From: Francois Desloges <fd@vipswitch.com>
To: linux-arm@vger.rutgers.edu
Subject: Re: Problem with gcc (building full toolchain)
Date:   Tue, 12 Oct 1999 10:10:29 -0400
Content-Type: text/plain
References: <093e01bf14b1$a301bbf0$2a01010a@internal.empeg.com>
MIME-Version: 1.0
Message-Id: <99101210211302.14975@dual>
Content-Transfer-Encoding: 8bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

On Tue, 12 Oct 1999, Mike Crowe wrote:
> Benjamin Stocks wrote:
> > make[3]: Entering directory
> > `/usr/local/arm/src/gcc-2.95/arm-linux/libiberty'
> > make[3]: *** No targets.  Stop.
> > make[3]: Leaving directory
> > `/usr/local/arm/src/gcc-2.95/arm-linux/libiberty'
> > make[2]: *** [../libiberty/libiberty.a] Error 2
> > make[2]: Leaving directory
> > `/usr/local/arm/src/gcc-2.95/arm-linux/libstdc++'
> > make[1]: *** [all-target-libstdc++] Error 2
> > make[1]: Leaving directory `/usr/local/arm/src/gcc-2.95'
> > make: *** [cross] Error 2

Normally, this is caused by trying to make gcc in the gcc subdirectory rather
than in the top gcc-2.95* top directory.

What follows is extracted from a long mail with subject:"Re: Toolchain guide"
in the Mail Archive. It has never been confirmed by Philip Blundell or Chris
Rutter but, Hey! it worked for me ;-)

>One would have to build gcc 3 timesin order to have a completely fonctionnal
>toolchain (built form scratch):
>-Build/install binutils
>-Patch/Build/install gcc
>-Build/install gcc again
>-Build/install glibc
>-Build/install gcc a third time without the -Dinhibit_libc corrections. 

Hope it will help,
--
François Desloges
fd@vipswitch.com
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Tue Oct 12 16:52:44 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id QAA03253
	for <linux-arm-archive@lists.arm.linux.org.uk>; Tue, 12 Oct 1999 16:52:44 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 743BE13E6E; Tue, 12 Oct 1999 17:52:42 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156995AbPJLPwL>;
	Tue, 12 Oct 1999 11:52:11 -0400
Received: by vger.rutgers.edu id <S156942AbPJLPvx>;
	Tue, 12 Oct 1999 11:51:53 -0400
Received: from nexusel.demon.co.uk ([158.152.30.195]:12061 "EHLO
        globe.nexus.co.uk") by vger.rutgers.edu with ESMTP
	id <S156790AbPJLPvj>; Tue, 12 Oct 1999 11:51:39 -0400
Received: from [192.0.0.21] (helo=fountain.nexus.co.uk ident=mail)
	by globe.nexus.co.uk with smtp (Exim 2.12 #1)
	id 11b3y8-0000cd-00; Tue, 12 Oct 1999 16:36:04 +0100
Received: from [127.0.0.1] (helo=fountain ident=pb)
	by fountain.nexus.co.uk with esmtp (Exim 3.03 #1)
	id 11b3y7-0006eF-00; Tue, 12 Oct 1999 16:36:03 +0100
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: "Mike Crowe" <mac@empeg.com>
Cc: linux-arm@vger.rutgers.edu
Subject: Re: Problem with gcc (building full toolchain) 
In-Reply-To: Message from "Mike Crowe" <mac@empeg.com> 
   of "Tue, 12 Oct 1999 13:59:36 BST." <093e01bf14b1$a301bbf0$2a01010a@internal.empeg.com> 
References: <37ECE91E.7ADED48@msoe.edu>  <093e01bf14b1$a301bbf0$2a01010a@internal.empeg.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date:   Tue, 12 Oct 1999 16:36:02 +0100
From: Philip Blundell <pb@nexus.co.uk>
Message-Id: <E11b3y7-0006eF-00@fountain.nexus.co.uk>
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

>> configure: error: installation or configuration problem: C compiler
>> cannot create executables.
>
>After successfully building a LANGUAGES="c", inhibit_libc gcc-2.95.1
>compiler (with glibc) I've gone back and tried to build a full compiler
>with C++ and threads support. I'm now seeing this error too.

See the config.log file for details of what went wrong.  Without that 
information it's hard to suggest a fix.

>I've been through the archives and all references to this error say to do
>the LANGUAGES="c", inhibit_libc hack which is obviously no use to me.

That hack is only of use for compiling libgcc.  If that isn't where you're 
having trouble it won't help.

p.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Tue Oct 12 17:17:30 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id RAA04105
	for <linux-arm-archive@lists.arm.linux.org.uk>; Tue, 12 Oct 1999 17:17:29 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 5F9B913D8E; Tue, 12 Oct 1999 18:17:28 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156995AbPJLQQs>;
	Tue, 12 Oct 1999 12:16:48 -0400
Received: by vger.rutgers.edu id <S156790AbPJLQQa>;
	Tue, 12 Oct 1999 12:16:30 -0400
Received: from relay1.mail.uk.psi.net ([154.32.105.6]:58594 "EHLO
        relay1.mail.uk.psi.net") by vger.rutgers.edu with ESMTP
	id <S156995AbPJLQPV>; Tue, 12 Oct 1999 12:15:21 -0400
Received: from morrison.empeg.co.uk ([193.119.19.130] helo=empeg.com)
	by relay1.mail.uk.psi.net with esmtp (Exim 2.12 #2)
	id 11b4Yb-0001f7-00; Tue, 12 Oct 1999 17:13:46 +0100
Received: from deneb (deneb.internal.empeg.com [10.1.1.42])
	by empeg.com (8.8.7/8.8.7) with SMTP id RAA09471;
	Tue, 12 Oct 1999 17:13:56 +0100
Message-ID: <0a0201bf14cd$1b8d9ce0$2a01010a@internal.empeg.com>
From: "Mike Crowe" <mac@empeg.com>
To: "Philip Blundell" <pb@nexus.co.uk>
Cc: <linux-arm@vger.rutgers.edu>
References: <37ECE91E.7ADED48@msoe.edu>  <093e01bf14b1$a301bbf0$2a01010a@internal.empeg.com>  <E11b3y7-0006eF-00@fountain.nexus.co.uk>
Subject: Re: Problem with gcc (building full toolchain) 
Date:   Tue, 12 Oct 1999 17:16:14 +0100
Organization: empeg ltd
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 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

> See the config.log file for details of what went wrong.  Without that
> information it's hard to suggest a fix.

I think I see what's failing. During the build I need to sneak in and fix
the specs file in gcc/ (elf32arm -> armelf_linux) - is there any way I can
change the code that generates the specs file so it puts the right thing
in there?

Alternatively, is there a CVS snapshot available as a tar I should try
instead?

--
Mike Crowe
empeg ltd

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Tue Oct 12 17:48:47 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id RAA04985
	for <linux-arm-archive@lists.arm.linux.org.uk>; Tue, 12 Oct 1999 17:48:47 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id A298F13EFB; Tue, 12 Oct 1999 18:48:45 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157076AbPJLQq4>;
	Tue, 12 Oct 1999 12:46:56 -0400
Received: by vger.rutgers.edu id <S156995AbPJLQoD>;
	Tue, 12 Oct 1999 12:44:03 -0400
Received: from nexusel.demon.co.uk ([158.152.30.195]:12305 "EHLO
        globe.nexus.co.uk") by vger.rutgers.edu with ESMTP
	id <S157063AbPJLQmW>; Tue, 12 Oct 1999 12:42:22 -0400
Received: from [192.0.0.21] (helo=fountain.nexus.co.uk ident=mail)
	by globe.nexus.co.uk with smtp (Exim 2.12 #1)
	id 11b4yz-0000gr-00; Tue, 12 Oct 1999 17:41:01 +0100
Received: from [127.0.0.1] (helo=fountain ident=pb)
	by fountain.nexus.co.uk with esmtp (Exim 3.03 #1)
	id 11b4yz-0006nP-00; Tue, 12 Oct 1999 17:41:01 +0100
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: "Mike Crowe" <mac@empeg.com>
Cc: linux-arm@vger.rutgers.edu
Subject: Re: Problem with gcc (building full toolchain) 
In-Reply-To: Message from "Mike Crowe" <mac@empeg.com> 
   of "Tue, 12 Oct 1999 17:16:14 BST." <0a0201bf14cd$1b8d9ce0$2a01010a@internal.empeg.com> 
References: <37ECE91E.7ADED48@msoe.edu> <093e01bf14b1$a301bbf0$2a01010a@internal.empeg.com> <E11b3y7-0006eF-00@fountain.nexus.co.uk>  <0a0201bf14cd$1b8d9ce0$2a01010a@internal.empeg.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date:   Tue, 12 Oct 1999 17:41:01 +0100
From: Philip Blundell <pb@nexus.co.uk>
Message-Id: <E11b4yz-0006nP-00@fountain.nexus.co.uk>
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

>I think I see what's failing. During the build I need to sneak in and fix
>the specs file in gcc/ (elf32arm -> armelf_linux) - is there any way I can
>change the code that generates the specs file so it puts the right thing
>in there?

There is a "#if 0" somewhere near the top of gcc/config/arm/linux-elf.h.  
Change it to "#if 1", or vice versa, and you should be in business.

>Alternatively, is there a CVS snapshot available as a tar I should try
>instead?

Yes, see <http://gcc.gnu.org/> for details of how to get snapshots.

p.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Tue Oct 12 19:29:15 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id TAA08215
	for <linux-arm-archive@lists.arm.linux.org.uk>; Tue, 12 Oct 1999 19:29:15 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 2AA5713D9D; Tue, 12 Oct 1999 20:28:54 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157008AbPJLS2Z>;
	Tue, 12 Oct 1999 14:28:25 -0400
Received: by vger.rutgers.edu id <S157002AbPJLS1p>;
	Tue, 12 Oct 1999 14:27:45 -0400
Received: from note.orchestra.cse.unsw.EDU.AU ([129.94.242.29]:4264 "HELO
        note.orchestra.cse.unsw.EDU.AU") by vger.rutgers.edu with SMTP
	id <S156790AbPJLS1W>; Tue, 12 Oct 1999 14:27:22 -0400
Received: From paulaner With LocalMail ; Wed, 13 Oct 99 04:21:02 +1000 
From: "Adam 'WeirdArms' Wiggins" <awiggins@cse.unsw.EDU.AU>
To: linux-arm@vger.rutgers.edu
Date:   Wed, 13 Oct 1999 04:20:42 +1000 (EST)
X-Sender: awiggins@paulaner.disy.cse.unsw.EDU.AU
Subject: More joyous binutils questions
Message-ID: <Pine.OSF.3.95.991013041632.5750A-100000@paulaner.disy.cse.unsw.EDU.AU>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

	Yes I'm still trying to get the most out of my ELF :) 
QUESTION: I've got a kernel I'm developing and I'd like to add the initial
server to the kernel's elf file (this makes loading easier for me because
its hard to deal with more then one elf file with my firmware) by adding
it to its own section with its own segment description. I tried using
objcopy but it doesn't give you any way of adding a new segment
descriptor! When I try to set the section flag to loadable it complains
the section is not assosiated with any segment.
	I want to add the initial server as a binary file to the kernel
elf executable AFTER the kernel executable is linked. 
	Any suggestions or do I have to write my own ELF utility to do
this?

	Cheers Adam

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Tue Oct 12 19:45:43 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id TAA08809
	for <linux-arm-archive@lists.arm.linux.org.uk>; Tue, 12 Oct 1999 19:45:42 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 45C0113E9A; Tue, 12 Oct 1999 20:45:41 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156942AbPJLSpK>;
	Tue, 12 Oct 1999 14:45:10 -0400
Received: by vger.rutgers.edu id <S156790AbPJLSos>;
	Tue, 12 Oct 1999 14:44:48 -0400
Received: from tazenda.demon.co.uk ([158.152.220.239]:1038 "EHLO
        kings-cross.london.uk.eu.org") by vger.rutgers.edu with ESMTP
	id <S156995AbPJLSnC>; Tue, 12 Oct 1999 14:43:02 -0400
Received: from localhost
	([127.0.0.1] helo=kings-cross.london.uk.eu.org ident=phil)
	by kings-cross.london.uk.eu.org with esmtp (Exim 2.05 #1)
	id 11b6sj-0000HI-00; Tue, 12 Oct 1999 19:42:41 +0100
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: "Adam 'WeirdArms' Wiggins" <awiggins@cse.unsw.EDU.AU>
Cc: linux-arm@vger.rutgers.edu
Subject: Re: More joyous binutils questions 
In-Reply-To: Message from Adam 'WeirdArms' Wiggins <awiggins@cse.unsw.EDU.AU> 
   of "Wed, 13 Oct 1999 04:20:42 +1000." <Pine.OSF.3.95.991013041632.5750A-100000@paulaner.disy.cse.unsw.EDU.AU> 
References: <Pine.OSF.3.95.991013041632.5750A-100000@paulaner.disy.cse.unsw.EDU.AU> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date:   Tue, 12 Oct 1999 19:42:41 +0100
From: Philip Blundell <Philip.Blundell@pobox.com>
Message-Id: <E11b6sj-0000HI-00@kings-cross.london.uk.eu.org>
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

>QUESTION: I've got a kernel I'm developing and I'd like to add the initial
>server to the kernel's elf file (this makes loading easier for me because
>its hard to deal with more then one elf file with my firmware) by adding
>it to its own section with its own segment description. I tried using
>objcopy but it doesn't give you any way of adding a new segment
>descriptor! When I try to set the section flag to loadable it complains
>the section is not assosiated with any segment.
>	I want to add the initial server as a binary file to the kernel
>elf executable AFTER the kernel executable is linked. 

Adding a new section to an executable is not a particularly meaningful thing 
to do.  In the execution view of ELF it is mostly segments that matter, which 
is probably why objcopy is complaining.

Could you explain what you want to do with this new section?

p.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Tue Oct 12 21:02:41 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id VAA11023
	for <linux-arm-archive@lists.arm.linux.org.uk>; Tue, 12 Oct 1999 21:02:41 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id CB15613F3A; Tue, 12 Oct 1999 22:02:39 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157068AbPJLUCL>;
	Tue, 12 Oct 1999 16:02:11 -0400
Received: by vger.rutgers.edu id <S156985AbPJLUBK>;
	Tue, 12 Oct 1999 16:01:10 -0400
Received: from tazenda.demon.co.uk ([158.152.220.239]:1105 "EHLO
        kings-cross.london.uk.eu.org") by vger.rutgers.edu with ESMTP
	id <S157121AbPJLT6g>; Tue, 12 Oct 1999 15:58:36 -0400
Received: from localhost
	([127.0.0.1] helo=kings-cross.london.uk.eu.org ident=phil)
	by kings-cross.london.uk.eu.org with esmtp (Exim 2.05 #1)
	id 11b841-0000QY-00; Tue, 12 Oct 1999 20:58:25 +0100
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: "Adam 'WeirdArms' Wiggins" <awiggins@cse.unsw.EDU.AU>
Cc: linux-arm@vger.rutgers.edu
Subject: Re: More joyous binutils questions 
In-Reply-To: Message from Adam 'WeirdArms' Wiggins <awiggins@cse.unsw.EDU.AU> 
   of "Wed, 13 Oct 1999 04:20:42 +1000." <Pine.OSF.3.95.991013041632.5750A-100000@paulaner.disy.cse.unsw.EDU.AU> 
References: <Pine.OSF.3.95.991013041632.5750A-100000@paulaner.disy.cse.unsw.EDU.AU> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date:   Tue, 12 Oct 1999 20:58:25 +0100
From: Philip Blundell <Philip.Blundell@pobox.com>
Message-Id: <E11b841-0000QY-00@kings-cross.london.uk.eu.org>
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

>	Any suggestions or do I have to write my own ELF utility to do
>this?

To actually answer your question (which I forgot to do in my last message), I 
think you do have to write your own utility if you want to add new segments.  
Or teach objcopy to do it I suppose.  I can't think of any other program 
offhand with this ability.

p.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Tue Oct 12 21:47:51 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id VAA12289
	for <linux-arm-archive@lists.arm.linux.org.uk>; Tue, 12 Oct 1999 21:47:51 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 0C8E413EE2; Tue, 12 Oct 1999 22:43:05 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157089AbPJLUmU>;
	Tue, 12 Oct 1999 16:42:20 -0400
Received: by vger.rutgers.edu id <S157068AbPJLUly>;
	Tue, 12 Oct 1999 16:41:54 -0400
Received: from note.orchestra.cse.unsw.EDU.AU ([129.94.242.29]:1117 "HELO
        note.orchestra.cse.unsw.EDU.AU") by vger.rutgers.edu with SMTP
	id <S157084AbPJLUhU>; Tue, 12 Oct 1999 16:37:20 -0400
Received: From paulaner With LocalMail ; Wed, 13 Oct 99 06:26:58 +1000 
From: "Adam 'WeirdArms' Wiggins" <awiggins@cse.unsw.EDU.AU>
To: Philip Blundell <Philip.Blundell@pobox.com>
Date:   Wed, 13 Oct 1999 06:26:58 +1000 (EST)
X-Sender: awiggins@paulaner.disy.cse.unsw.EDU.AU
Cc: linux-arm@vger.rutgers.edu
Subject: Re: More joyous binutils questions 
In-Reply-To: <E11b841-0000QY-00@kings-cross.london.uk.eu.org>
Message-ID: <Pine.OSF.3.95.991013062552.6033B-100000@paulaner.disy.cse.unsw.EDU.AU>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

On Tue, 12 Oct 1999, Philip Blundell wrote:

> >	Any suggestions or do I have to write my own ELF utility to do
> >this?
> 
> To actually answer your question (which I forgot to do in my last message), I 
> think you do have to write your own utility if you want to add new segments.  
> Or teach objcopy to do it I suppose.  I can't think of any other program 
> offhand with this ability.

	We have such a utility for the MIPS implimentation of the kernel
in question. It packs the kernel and initial servers into one ELF file the
firmware loads, I'm just trying to avoid porting it to ARM, it seems that
this is whats required though :(

	Cheers Adam

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Tue Oct 12 21:56:40 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id VAA12555
	for <linux-arm-archive@lists.arm.linux.org.uk>; Tue, 12 Oct 1999 21:56:39 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 683B513F3A; Tue, 12 Oct 1999 22:56:17 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157092AbPJLUzK>;
	Tue, 12 Oct 1999 16:55:10 -0400
Received: by vger.rutgers.edu id <S157102AbPJLUvd>;
	Tue, 12 Oct 1999 16:51:33 -0400
Received: from note.orchestra.cse.unsw.EDU.AU ([129.94.242.29]:1214 "HELO
        note.orchestra.cse.unsw.EDU.AU") by vger.rutgers.edu with SMTP
	id <S157178AbPJLUqH>; Tue, 12 Oct 1999 16:46:07 -0400
Received: From paulaner With LocalMail ; Wed, 13 Oct 99 06:24:00 +1000 
From: "Adam 'WeirdArms' Wiggins" <awiggins@cse.unsw.EDU.AU>
To: Philip Blundell <Philip.Blundell@pobox.com>
Date:   Wed, 13 Oct 1999 06:24:00 +1000 (EST)
X-Sender: awiggins@paulaner.disy.cse.unsw.EDU.AU
Cc: linux-arm@vger.rutgers.edu
Subject: Re: More joyous binutils questions 
In-Reply-To: <E11b6sj-0000HI-00@kings-cross.london.uk.eu.org>
Message-ID: <Pine.OSF.3.95.991013062038.6033A-100000@paulaner.disy.cse.unsw.EDU.AU>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

On Tue, 12 Oct 1999, Philip Blundell wrote:

> >QUESTION: I've got a kernel I'm developing and I'd like to add the initial
> >server to the kernel's elf file (this makes loading easier for me because
> >its hard to deal with more then one elf file with my firmware) by adding
> >it to its own section with its own segment description. I tried using
> >objcopy but it doesn't give you any way of adding a new segment
> >descriptor! When I try to set the section flag to loadable it complains
> >the section is not assosiated with any segment.
> >	I want to add the initial server as a binary file to the kernel
> >elf executable AFTER the kernel executable is linked. 
> 
> Adding a new section to an executable is not a particularly meaningful thing 
> to do.  In the execution view of ELF it is mostly segments that matter, which 
> is probably why objcopy is complaining.
> 
> Could you explain what you want to do with this new section?

	The firmward loads a single ELF file into the address specified by
the lma for each program segment. I want to add a program segment (and
acompanying section) which is the initial server (init) to the kernel ELF
executable and set its lma to the address it will be loaded to (it
executes in place in a one-one PA/VA mapped address space). So the net
effect is I want one ELF file containning the kernel segments and the
initial server binary.
	If you need more detail I can post the code.

	Cheers Adam

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Tue Oct 12 22:44:43 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id WAA13893
	for <linux-arm-archive@lists.arm.linux.org.uk>; Tue, 12 Oct 1999 22:44:43 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id C572013F8F; Tue, 12 Oct 1999 23:44:20 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157118AbPJLVkN>;
	Tue, 12 Oct 1999 17:40:13 -0400
Received: by vger.rutgers.edu id <S157013AbPJLVj4>;
	Tue, 12 Oct 1999 17:39:56 -0400
Received: from tazenda.demon.co.uk ([158.152.220.239]:1174 "EHLO
        kings-cross.london.uk.eu.org") by vger.rutgers.edu with ESMTP
	id <S157025AbPJLVfa>; Tue, 12 Oct 1999 17:35:30 -0400
Received: from localhost
	([127.0.0.1] helo=kings-cross.london.uk.eu.org ident=phil)
	by kings-cross.london.uk.eu.org with esmtp (Exim 2.05 #1)
	id 11b9Zm-0000Xw-00; Tue, 12 Oct 1999 22:35:18 +0100
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: "Adam 'WeirdArms' Wiggins" <awiggins@cse.unsw.EDU.AU>
Cc: linux-arm@vger.rutgers.edu
Subject: Re: More joyous binutils questions 
In-Reply-To: Message from Adam 'WeirdArms' Wiggins <awiggins@cse.unsw.EDU.AU> 
   of "Wed, 13 Oct 1999 06:26:58 +1000." <Pine.OSF.3.95.991013062552.6033B-100000@paulaner.disy.cse.unsw.EDU.AU> 
References: <Pine.OSF.3.95.991013062552.6033B-100000@paulaner.disy.cse.unsw.EDU.AU> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date:   Tue, 12 Oct 1999 22:35:18 +0100
From: Philip Blundell <Philip.Blundell@pobox.com>
Message-Id: <E11b9Zm-0000Xw-00@kings-cross.london.uk.eu.org>
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

>	We have such a utility for the MIPS implimentation of the kernel
>in question. It packs the kernel and initial servers into one ELF file the
>firmware loads, I'm just trying to avoid porting it to ARM, it seems that
>this is whats required though :(

Actually I wonder if GNU ld could be persuaded to do what you need using a 
suitable linker script, kind of:

PHDRS
{
  headers PT_PHDR PHDRS ;
  interp PT_INTERP ;
  text PT_LOAD FILEHDR PHDRS ;
  data PT_LOAD ;
  dynamic PT_DYNAMIC ;
  server PT_LOAD ;
}

SECTIONS
{
  .text :
  {
    *(.text)
  }
  .data :
  {
    *(.data)
  }
  .bss :
  {
   *(.bss)
  }
  .server :
  {
   /sbin/init
  }
}

... you get the idea.  I haven't actually tried this but it should stand a 
reasonable chance.

p.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Wed Oct 13 01:13:52 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id BAA18497
	for <linux-arm-archive@lists.arm.linux.org.uk>; Wed, 13 Oct 1999 01:13:51 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id B48C913F38; Wed, 13 Oct 1999 02:13:50 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157012AbPJMANS>;
	Tue, 12 Oct 1999 20:13:18 -0400
Received: by vger.rutgers.edu id <S157121AbPJMAKP>;
	Tue, 12 Oct 1999 20:10:15 -0400
Received: from [209.69.145.41] ([209.69.145.41]:4308 "EHLO larry.ztnet.com")
	by vger.rutgers.edu with ESMTP id <S157085AbPJMAJT>;
	Tue, 12 Oct 1999 20:09:19 -0400
Received: from leviatha (lev@nic-c16-161.mw.mediaone.net [24.131.16.161])
	by larry.ztnet.com (8.9.3/8.9.3/Debian/GNU) with SMTP id UAA28768
	for <linux-arm@vger.rutgers.edu>; Tue, 12 Oct 1999 20:09:18 -0400
Message-ID: <000f01bf150e$a7bbee60$a1108318@mw.mediaone.net>
Reply-To: "Zachary Williams" <admin@ztnet.com>
From: "Zachary Williams" <admin@ztnet.com>
To: "netwinder" <linux-arm@vger.rutgers.edu>
Subject: Clustering
Date:   Tue, 12 Oct 1999 20:05:27 -0400
Organization: ZTNet, L.L.C.
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_000C_01BF14ED.20672AE0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

This is a multi-part message in MIME format.

------=_NextPart_000_000C_01BF14ED.20672AE0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I work for a small ISP, and we are looking to implement a clustering =
solution.  The Netwinders have caught my eye, and I am curious to what =
other folks think.  We don't plan on running any CGI's from these, they =
are STRICTLY webservers.

Our topology would basically be a Foundry Networks ServerIorn for load =
balancing and health-checks.  The webservers would be connected to a =
netapp Filer for the storage solution.  Each netwinder will be =
configured exactly the same, with access to the directory structure on =
the Netapp.  Does this sound like a reasonable solution?  It seems to be =
the best one, and all I am worried about is stability.  I think the =
netwinders can handle the load, as I can add additional servers as =
needed, and then balance them with the ServerIron.

Thanks,=20
Zachary WIlliams
ZTNet, L.L.C.

------=_NextPart_000_000C_01BF14ED.20672AE0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2614.3401" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>I work for a small ISP, and we are =
looking to=20
implement a clustering solution.&nbsp; The Netwinders have caught my =
eye, and I=20
am curious to what other folks think.&nbsp; We don't plan on running any =
CGI's=20
from these, they are STRICTLY webservers.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Our topology would basically be a =
Foundry Networks=20
ServerIorn for load balancing and health-checks.&nbsp; The webservers =
would be=20
connected to a netapp Filer for the storage solution.&nbsp; Each =
netwinder will=20
be configured exactly the same, with access to the directory structure =
on the=20
Netapp.&nbsp; Does this sound like a reasonable solution?&nbsp; It seems =
to be=20
the best one, and all I am worried about is stability.&nbsp; I think the =

netwinders can handle the load, as I can add additional servers as =
needed, and=20
then balance them with the ServerIron.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Thanks, </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Zachary WIlliams</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>ZTNet, =
L.L.C.</FONT></DIV></BODY></HTML>

------=_NextPart_000_000C_01BF14ED.20672AE0--

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Wed Oct 13 09:36:01 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id JAA01114
	for <linux-arm-archive@lists.arm.linux.org.uk>; Wed, 13 Oct 1999 09:35:59 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 23BE013F3A; Wed, 13 Oct 1999 08:51:41 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157042AbPJMGvH>;
	Wed, 13 Oct 1999 02:51:07 -0400
Received: by vger.rutgers.edu id <S156970AbPJMGuj>;
	Wed, 13 Oct 1999 02:50:39 -0400
Received: from oskar.nanoteq.co.za ([196.37.91.10]:3999 "EHLO
        oskar.nanoteq.co.za") by vger.rutgers.edu with ESMTP
	id <S156967AbPJMGue>; Wed, 13 Oct 1999 02:50:34 -0400
Received: from craul.nanoteq.co.za (IDENT:chris@craul.nanoteq.co.za [196.37.91.24])
	by oskar.nanoteq.co.za (8.9.0/8.9.0) with ESMTP id IAA10402
	for <linux-arm@vger.rutgers.edu>; Wed, 13 Oct 1999 08:52:51 +0200 (SAT)
Message-ID: <380463DA.F0D9F72B@craul.nanoteq.co.za>
Date:   Wed, 13 Oct 1999 08:50:02 -0200
From: Chris Bohme <chris@craul.nanoteq.co.za>
Reply-To: cbo@nanoteq.co.za
Organization: Nanoteq
X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.2.10 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: linux-arm <linux-arm@vger.rutgers.edu>
Subject: Re: TFTP bootloader with dec21041
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Benjamin Herrenschmidt wrote:

> No, he's not using the Linux kernel, but Russel's bootloader, which
runs
> with data cache disabled, so this should not be an issue. I should put

> your hand on the chip's documentation, you probably lack some kind of
> initialisation (do you have a PROM providing the hw eth adress for
> example ? If you don't you'll probably have to set it up manually from

> the driver).

The hardware address is actually configured from the driver. Does anyone
have
some pointers to the chip's docs ? I seem to get lost on intel's site.

Greets,
Chris



unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Wed Oct 13 12:19:11 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id MAA15423
	for <linux-arm-archive@lists.arm.linux.org.uk>; Wed, 13 Oct 1999 12:19:10 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 579E313FD8; Wed, 13 Oct 1999 13:19:04 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157308AbPJMLSY>;
	Wed, 13 Oct 1999 07:18:24 -0400
Received: by vger.rutgers.edu id <S157295AbPJMLN2>;
	Wed, 13 Oct 1999 07:13:28 -0400
Received: from [195.89.188.122] ([195.89.188.122]:2295 "HELO linuxhacker.org")
	by vger.rutgers.edu with SMTP id <S157199AbPJMLMW>;
	Wed, 13 Oct 1999 07:12:22 -0400
Received: (qmail 20607 invoked by uid 0); 13 Oct 1999 11:18:53 -0000
Received: from localhost (alex@127.0.0.1)
  by linuxhacker.org with SMTP; 13 Oct 1999 11:18:53 -0000
Date:   Wed, 13 Oct 1999 12:18:52 +0100 (GMT)
From: Alex Holden <alex@linuxhacker.org>
To: Zachary Williams <admin@ztnet.com>
Cc: netwinder <linux-arm@vger.rutgers.edu>
Subject: Re: Clustering
In-Reply-To: <000f01bf150e$a7bbee60$a1108318@mw.mediaone.net>
Message-ID: <Pine.LNX.4.04.9910131212350.20555-100000@www.linuxhacker.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

On Tue, 12 Oct 1999, Zachary Williams wrote:
> and all I am worried about is stability.

With the IDE disk rackmount units, the 2.2.12 kernel, and a distribution
such as Titan-VI, I don't think you should have any problems.

--------------- Linux- the choice of a GNU generation. --------------
: Alex Holden (M1CJD)- Caver, Programmer, Land Rover nut, Radio Ham :
-------------------- http://www.linuxhacker.org/ --------------------

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Wed Oct 13 15:08:50 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id PAA25962
	for <linux-arm-archive@lists.arm.linux.org.uk>; Wed, 13 Oct 1999 15:08:49 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id BD0E414045; Wed, 13 Oct 1999 16:08:48 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156973AbPJMOHs>;
	Wed, 13 Oct 1999 10:07:48 -0400
Received: by vger.rutgers.edu id <S156992AbPJMOEX>;
	Wed, 13 Oct 1999 10:04:23 -0400
Received: from sparkle.Generation.NET ([205.205.119.4]:33023 "EHLO
        sparkle.Generation.NET") by vger.rutgers.edu with ESMTP
	id <S157001AbPJMOAT>; Wed, 13 Oct 1999 10:00:19 -0400
Received: from dual (generic253.197.205.205.IN-ADDR.ARPA [205.205.197.253] (may be forged))
	by sparkle.Generation.NET (8.9.3/8.9.3) with SMTP id KAA00175
	for <linux-arm@vger.rutgers.edu>; Wed, 13 Oct 1999 10:00:32 -0400 (EDT)
From: Francois Desloges <fd@vipswitch.com>
To: linux-arm@vger.rutgers.edu
Subject: How do one uses the bios? 
Date:   Fri, 8 Oct 1999 16:37:25 -0400
Content-Type: text/plain
MIME-Version: 1.0
Message-Id: <99101309592003.14975@dual>
Content-Transfer-Encoding: 8bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

I've now, got that bios-1.05 buit for my EBSA and a built 2.2.12 kernel all in
elf format.  How do I use them?
Is there some "theory of operation" document or guide to the bios?

What would be usefull to know:
What is the relation between angel, the bios, the kernel, an initrd (I guess?)
and the flash structure?
Do I need angel, FMU at all?

On Thu, 28 Jan 1999, Nicolas Pitre wrote:
>On Thu, 28 Jan 1999, Sandeep Chatterjee wrote:
>> Are there any tools out there that allow us to query the SA1100 and find
>> out what's going on (e.g., through the JTAG interface)? Any other
>> suggestions? Is there some other component that I need on our board to
>> make Angel and Linux work???
>
>My suggestion is: get rid of Angel.
>The only thing you need is to copy the kernel from ROM to 0xc0008000
>physical and jump into it.  You don't have to bother with the MMU at all
>--the kernel will enable it the right way.

The PrimaryBootLoader (PBL) that is in the same block as Angel, initalizes a lot
of things:
1-       Disable the flash ROM alias at address 0
2-       Disable all interrupt
3-       Initialize SDRAM
4-       Setup Exceptions Vectors
5-       Determine the board configuration (PCI arbiter or X-Bus)
6-       Initialize PCI Arbiter
7-       Configure 21285 UART (option)
8-       Configure PCI Interface
9-       Configure the SA-110 MMU etc.

Are all these things normally performed by the kernel or the bios?
And by hte way, what would be the equivalent of Brutus address 0xc0008000 on
the EBSA285 ?

Thanks!
--
François Desloges
fd@vipswitch.com
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Wed Oct 13 15:16:30 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id PAA26908
	for <linux-arm-archive@lists.arm.linux.org.uk>; Wed, 13 Oct 1999 15:16:29 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 7F1EF14057; Wed, 13 Oct 1999 16:16:28 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157037AbPJMOM3>;
	Wed, 13 Oct 1999 10:12:29 -0400
Received: by vger.rutgers.edu id <S156852AbPJMOIH>;
	Wed, 13 Oct 1999 10:08:07 -0400
Received: from relay3.mail.uk.psi.net ([154.32.109.6]:52435 "EHLO
        relay3.mail.uk.psi.net") by vger.rutgers.edu with ESMTP
	id <S156972AbPJMOHW>; Wed, 13 Oct 1999 10:07:22 -0400
Received: from morrison.empeg.co.uk ([193.119.19.130] helo=empeg.com)
	by relay3.mail.uk.psi.net with esmtp (Exim 2.12 #2)
	id 11bP3h-0007Ys-00
	for linux-arm@vger.rutgers.edu; Wed, 13 Oct 1999 15:07:13 +0100
Received: from deneb (deneb.internal.empeg.com [10.1.1.42])
	by empeg.com (8.8.7/8.8.7) with SMTP id PAA03522
	for <linux-arm@vger.rutgers.edu>; Wed, 13 Oct 1999 15:07:33 +0100
Message-ID: <0b2e01bf1584$99aa6290$2a01010a@internal.empeg.com>
From: "Mike Crowe" <mac@empeg.com>
To: <linux-arm@vger.rutgers.edu>
References: <37ECE91E.7ADED48@msoe.edu> <093e01bf14b1$a301bbf0$2a01010a@internal.empeg.com> <E11b3y7-0006eF-00@fountain.nexus.co.uk>  <0a0201bf14cd$1b8d9ce0$2a01010a@internal.empeg.com>  <E11b4yz-0006nP-00@fountain.nexus.co.uk>
Subject: Re: Problem with gcc (building full toolchain) 
Date:   Wed, 13 Oct 1999 15:09:42 +0100
Organization: empeg ltd
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 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

> There is a "#if 0" somewhere near the top of gcc/config/arm/linux-elf.h.
> Change it to "#if 1", or vice versa, and you should be in business.

Ah, thanks. I remember reading about that. It's so difficult remembering
to do everything when you need to rebuild the compiler so many times :-)

> >Alternatively, is there a CVS snapshot available as a tar I should try
> >instead?
>
> Yes, see <http://gcc.gnu.org/> for details of how to get snapshots.

I've found the snapshots there - I assume they're still called egcs.

--
Mike Crowe
empeg ltd

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Wed Oct 13 16:17:31 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id QAA31124
	for <linux-arm-archive@lists.arm.linux.org.uk>; Wed, 13 Oct 1999 16:17:30 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 4B98A13FD7; Wed, 13 Oct 1999 17:17:29 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156929AbPJMPQ7>;
	Wed, 13 Oct 1999 11:16:59 -0400
Received: by vger.rutgers.edu id <S156839AbPJMPQm>;
	Wed, 13 Oct 1999 11:16:42 -0400
Received: from oskar.nanoteq.co.za ([196.37.91.10]:2478 "EHLO
        oskar.nanoteq.co.za") by vger.rutgers.edu with ESMTP
	id <S156946AbPJMPQ1>; Wed, 13 Oct 1999 11:16:27 -0400
Received: from craul.nanoteq.co.za (IDENT:chris@craul.nanoteq.co.za [196.37.91.24])
	by oskar.nanoteq.co.za (8.9.0/8.9.0) with ESMTP id RAA11486;
	Wed, 13 Oct 1999 17:17:46 +0200 (SAT)
Message-ID: <3804DA30.10E23245@craul.nanoteq.co.za>
Date:   Wed, 13 Oct 1999 17:14:56 -0200
From: Chris Bohme <chris@craul.nanoteq.co.za>
Reply-To: cbo@nanoteq.co.za
Organization: Nanoteq
X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.2.10 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Francois Desloges <fd@vipswitch.com>
Cc: linux-arm <linux-arm@vger.rutgers.edu>
Subject: Re: How do one uses the bios?
References: <99101309592003.14975@dual>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Hi Francois,

Francois Desloges wrote:

> I've now, got that bios-1.05 buit for my EBSA and a built 2.2.12 kernel all in
> elf format.  How do I use them?
> Is there some "theory of operation" document or guide to the bios?
>
> What would be usefull to know:
> What is the relation between angel, the bios, the kernel, an initrd (I guess?)
> and the flash structure?
> Do I need angel, FMU at all?

I left angel in image 0 in the flash, and let it load the bios from another flash
image pointed to by the selector switch (that's why the bios is in AIF format).
It was necessary to link the bios at a address different the one specified in the
readme file  (TEXTADDR = 0x410000C0 + bank * 0x00040000 rather than 0x410000A0).

Also note that if you are using a pci-only backplane, the ISA initialization code
will hang the bios. I tried boot the kernel via the network, but the bios hangs
during opening of the network card. Haven't had time to play with it since.

Regards,
Chris

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Wed Oct 13 16:48:18 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id QAA01582
	for <linux-arm-archive@lists.arm.linux.org.uk>; Wed, 13 Oct 1999 16:48:17 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id B031913F9C; Wed, 13 Oct 1999 17:48:01 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156826AbPJMPrc>;
	Wed, 13 Oct 1999 11:47:32 -0400
Received: by vger.rutgers.edu id <S156791AbPJMPrW>;
	Wed, 13 Oct 1999 11:47:22 -0400
Received: from visuaide.colba.net ([207.107.152.244]:64987 "EHLO
        xanadu.visuaide.com") by vger.rutgers.edu with ESMTP
	id <S156937AbPJMPrJ>; Wed, 13 Oct 1999 11:47:09 -0400
Received: from localhost (nico@localhost)
	by xanadu.visuaide.com (8.9.3/8.9.3) with ESMTP id LAA20726;
	Wed, 13 Oct 1999 11:47:13 -0400
X-Authentication-Warning: xanadu.visuaide.com: nico owned process doing -bs
Date:   Wed, 13 Oct 1999 11:47:13 -0400 (EDT)
From: Nicolas Pitre <nico@visuaide.com>
To: "Adam 'WeirdArms' Wiggins" <awiggins@cse.unsw.EDU.AU>
Cc: linux-arm <linux-arm@vger.rutgers.edu>
Subject: Re: SA-1100 cache clean
In-Reply-To: <Pine.OSF.3.95.991012222031.13114A-100000@paulaner.disy.cse.unsw.EDU.AU>
Message-ID: <Pine.LNX.4.10.9910131143330.20724-100000@xanadu.visuaide.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing



On Tue, 12 Oct 1999, Adam 'WeirdArms' Wiggins wrote:

> 	Can anyone point me out to the bit of code that cleans the DCache
> for the SA-1100, how many cycles does it take?

It's in linux/arch/arm/mm/proc-sa110.S.  You'll probably need to apply a
patch from ftp.netwinder.org/users/n/nico to have the SA1100 specifics.


Nicolas

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Wed Oct 13 21:40:18 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id VAA11426
	for <linux-arm-archive@lists.arm.linux.org.uk>; Wed, 13 Oct 1999 21:40:18 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id B108D13FE7; Wed, 13 Oct 1999 22:40:16 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156793AbPJMUjp>;
	Wed, 13 Oct 1999 16:39:45 -0400
Received: by vger.rutgers.edu id <S156791AbPJMUj1>;
	Wed, 13 Oct 1999 16:39:27 -0400
Received: from mail-gw2.pacbell.net ([206.13.28.53]:35817 "EHLO
        mail-gw2.pacbell.net") by vger.rutgers.edu with ESMTP
	id <S156905AbPJMUg5>; Wed, 13 Oct 1999 16:36:57 -0400
Received: from java (adsl-216-101-151-82.dsl.snfc21.pacbell.net [216.101.151.82])
	by mail-gw2.pacbell.net (8.9.3/8.9.3) with SMTP id NAA28442
	for <linux-arm@vger.rutgers.edu>; Wed, 13 Oct 1999 13:36:54 -0700 (PDT)
Message-ID: <024f01bf15bb$ff03f3e0$529765d8@java>
From: "Dave Borja" <dave_bb@pacbell.net>
To: "linux-arm" <linux-arm@vger.rutgers.edu>
Subject: some niave questions on moving to sa110 box
Date:   Wed, 13 Oct 1999 13:46:16 -0700
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.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Now that we have linux going on the brutus, we are trying to get tcp/ip
stack
and PPP working as a sort of exercise in climbing the learning curve.

Ultimately, we need to get Linux going on an sa110 based box. This one
has only 8mb dram, 4mb flash. Mouse/keyboard internface, 2 serial
ports, an eithernet interface and a tl750 video graphics chip (plus support
chips).

What would be the issues on bringing up linux on this box? We should be able
to use the same process as we did with the sa1100 (download via angelboot
over
the serial port). Address map is different of course so we need to tweek the
kernel there as
well as recompiling for the sa110. Also, would we need to recompile c
library and
other utilities that go on the ramdisk? The ramdisk was built with the
brutus in mind but
I feel that the binaries should run on a sa110 based box.

I'm not sure what to do about the video graphics chip. There are some low
level
board support routines in C that are OS independent. We may need to have our
application talk direcltly to these instead of trying to write a driver for
Linux. After
all, we don't expect to be running X applications on our box.

Any insights would be appreciated.
  thanks
 Dave Borja

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Wed Oct 13 22:29:27 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id WAA12781
	for <linux-arm-archive@lists.arm.linux.org.uk>; Wed, 13 Oct 1999 22:29:22 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id B0627140A9; Wed, 13 Oct 1999 23:29:20 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156929AbPJMV2u>;
	Wed, 13 Oct 1999 17:28:50 -0400
Received: by vger.rutgers.edu id <S156901AbPJMVZg>;
	Wed, 13 Oct 1999 17:25:36 -0400
Received: from tazenda.demon.co.uk ([158.152.220.239]:1292 "EHLO
        kings-cross.london.uk.eu.org") by vger.rutgers.edu with ESMTP
	id <S156979AbPJMVUn>; Wed, 13 Oct 1999 17:20:43 -0400
Received: from localhost
	([127.0.0.1] helo=kings-cross.london.uk.eu.org ident=phil)
	by kings-cross.london.uk.eu.org with esmtp (Exim 2.05 #1)
	id 11bVp0-0001FI-00; Wed, 13 Oct 1999 22:20:30 +0100
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: "Dave Borja" <dave_bb@pacbell.net>
Cc: "linux-arm" <linux-arm@vger.rutgers.edu>
Subject: Re: some niave questions on moving to sa110 box 
In-Reply-To: Message from "Dave Borja" <dave_bb@pacbell.net> 
   of "Wed, 13 Oct 1999 13:46:16 PDT." <024f01bf15bb$ff03f3e0$529765d8@java> 
References: <024f01bf15bb$ff03f3e0$529765d8@java> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date:   Wed, 13 Oct 1999 22:20:30 +0100
From: Philip Blundell <Philip.Blundell@pobox.com>
Message-Id: <E11bVp0-0001FI-00@kings-cross.london.uk.eu.org>
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

>Also, would we need to recompile c library and
>other utilities that go on the ramdisk?

No.  The SA-1100 and SA-110 are entirely compatible as regards user space.

>I'm not sure what to do about the video graphics chip. There are some low
>level board support routines in C that are OS independent.  We may need to 
>have our application talk direcltly to these instead of trying to write a 
>driver for Linux. After all, we don't expect to be running X applications 
>on our box.

You could write an fbcon driver which would give you a reasonable abstraction, 
so long as your video hardware isn't too weird.  Alternatively yes a 
completely custom approach might be easier if you are happy to homebrew 
everything.

p.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Thu Oct 14 13:33:32 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id NAA10176
	for <linux-arm-archive@lists.arm.linux.org.uk>; Thu, 14 Oct 1999 13:33:29 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id E08F013DF2; Thu, 14 Oct 1999 14:33:22 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156840AbPJNMdA>;
	Thu, 14 Oct 1999 08:33:00 -0400
Received: by vger.rutgers.edu id <S156833AbPJNMcl>;
	Thu, 14 Oct 1999 08:32:41 -0400
Received: from yorktown.msoe.edu ([155.92.194.37]:4542 "EHLO yorktown.msoe.edu")
	by vger.rutgers.edu with ESMTP id <S156814AbPJNMcc>;
	Thu, 14 Oct 1999 08:32:32 -0400
Received: from msoe.edu (sleepchamber.msoe.edu [155.92.180.200]) by yorktown.msoe.edu with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0)
	id 4RB30K5Q; Thu, 14 Oct 1999 07:32:25 -0500
Message-ID: <3805CF0C.B742A402@msoe.edu>
Date:   Thu, 14 Oct 1999 12:39:40 +0000
From: Benjamin Stocks <stocksb@msoe.edu>
X-Mailer: Mozilla 4.61 [en] (X11; U; Linux 2.2.11 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: linux-arm@vger.rutgers.edu, debian-arm@lists.debian.org
Subject: arm-linux-ld: target elf32-arm not found
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

While cross compiling a kernel with Mark van Doesburg's patches for the
EBSA285 the make exited with this error:

arm-linux-ld -T /mnt/research/ben2.2.9/linux/arch/arm/vmlinux-armv.lds
-e stext -Ttext 0x60008000 arch/arm/kernel/head-armv.o
arch/arm/kernel/init_task.o init/main.o init/version.o \
--start-group \
arch/arm/kernel/kernel.o arch/arm/mm/mm.o kernel/kernel.o mm/mm.o
fs/fs.o ipc/ipc.o \
fs/filesystems.a \
net/network.a \
drivers/block/block.a drivers/char/char.a drivers/misc/misc.a
drivers/net/net.a drivers/pcimsg/pcimsg.a arch/arm/special/special.a
arch/arm/nwfpe/math-emu.a drivers/pcimsg/pcimsg.a \
arch/arm/lib/lib.a /mnt/research/ben2.2.9/linux/lib/lib.a `arm-linux-gcc
-D__KERNEL__ -I/mnt/research/ben2.2.9/linux/include  -mapcs-32
-mshort-load-bytes -mcpu=strongarm110 --print-libgcc-file-name` \
        --end-group \
        -o vmlinux
arm-linux-ld: target elf32-arm not found
make: *** [vmlinux] Error 1

I found where the target for the kernel build was set,
arch/arm/vmlinux-armo.lds and arch/arm/vmlinux-armv.lds, and through
trial and error found that target 'elf32-littlearm' would build the
kernel. I am using kernel 2.2.9 and binutils 2.9.5.0.13. Is there
something eles I needed to change? or was there something that I broke
earlier when I build my cross compiler. 
-- 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Benjamin Stocks
Computer Engineering
Milwaukee School of Engineering
email: stocksb@msoe.edu
http://www.msoe.edu/~stocksb
voice: 414.220.9683

"Don't Panic"
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Thu Oct 14 14:39:34 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id OAA12156
	for <linux-arm-archive@lists.arm.linux.org.uk>; Thu, 14 Oct 1999 14:39:28 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id AA628140D1; Thu, 14 Oct 1999 15:39:21 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156910AbPJNNiv>;
	Thu, 14 Oct 1999 09:38:51 -0400
Received: by vger.rutgers.edu id <S156901AbPJNNim>;
	Thu, 14 Oct 1999 09:38:42 -0400
Received: from nexusel.demon.co.uk ([158.152.30.195]:16791 "EHLO
        globe.nexus.co.uk") by vger.rutgers.edu with ESMTP
	id <S156814AbPJNNi2>; Thu, 14 Oct 1999 09:38:28 -0400
Received: from [192.0.0.21] (helo=fountain.nexus.co.uk ident=mail)
	by globe.nexus.co.uk with smtp (Exim 2.12 #1)
	id 11bl1J-000301-00; Thu, 14 Oct 1999 14:34:13 +0100
Received: from [127.0.0.1] (helo=fountain ident=pb)
	by fountain.nexus.co.uk with esmtp (Exim 3.03 #1)
	id 11bl1J-00079m-00; Thu, 14 Oct 1999 14:34:13 +0100
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: Benjamin Stocks <stocksb@msoe.edu>
Cc: linux-arm@vger.rutgers.edu, debian-arm@lists.debian.org
Subject: Re: arm-linux-ld: target elf32-arm not found 
In-Reply-To: Message from Benjamin Stocks <stocksb@msoe.edu> 
   of "Thu, 14 Oct 1999 12:39:40 -0000." <3805CF0C.B742A402@msoe.edu> 
References: <3805CF0C.B742A402@msoe.edu> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date:   Thu, 14 Oct 1999 14:34:12 +0100
From: Philip Blundell <pb@nexus.co.uk>
Message-Id: <E11bl1J-00079m-00@fountain.nexus.co.uk>
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

>I found where the target for the kernel build was set,
>arch/arm/vmlinux-armo.lds and arch/arm/vmlinux-armv.lds, and through
>trial and error found that target 'elf32-littlearm' would build the
>kernel. I am using kernel 2.2.9 and binutils 2.9.5.0.13. Is there
>something eles I needed to change? or was there something that I broke
>earlier when I build my cross compiler. 

Neither, this is just an incompatibility between old kernels and new binutils.
Your fix is OK; alternatively you can just remove the OUTPUT_FORMAT line.  I 
think this has been discussed several times before, see the mailing list 
archives for linux-arm.

p.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Thu Oct 14 20:19:42 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id UAA23842
	for <linux-arm-archive@lists.arm.linux.org.uk>; Thu, 14 Oct 1999 20:19:42 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 2AE091411C; Thu, 14 Oct 1999 21:19:41 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156965AbPJNTTM>;
	Thu, 14 Oct 1999 15:19:12 -0400
Received: by vger.rutgers.edu id <S156903AbPJNTSZ>;
	Thu, 14 Oct 1999 15:18:25 -0400
Received: from mail-gw2.pacbell.net ([206.13.28.53]:58957 "EHLO
        mail-gw2.pacbell.net") by vger.rutgers.edu with ESMTP
	id <S156953AbPJNTSR>; Thu, 14 Oct 1999 15:18:17 -0400
Received: from java (adsl-216-101-151-82.dsl.snfc21.pacbell.net [216.101.151.82])
	by mail-gw2.pacbell.net (8.9.3/8.9.3) with SMTP id MAA20629
	for <linux-arm@vger.rutgers.edu>; Thu, 14 Oct 1999 12:18:07 -0700 (PDT)
Message-ID: <03fd01bf167a$2861ea30$529765d8@java>
From: "Dave Borja" <dave_bb@pacbell.net>
To: "linux-arm" <linux-arm@vger.rutgers.edu>
Subject: More  naive questions 
Date:   Thu, 14 Oct 1999 12:27:26 -0700
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.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

After completing the process for booting linux on brutus,
I was wondering how the paramters for angelboot for entry point,
kernel load address and address to load the ramdisk were
chosen? We want to try this on an SA110 based board. It has
the same angel monitor in ROM, but only 8mb ram and the
address map is somewhat different. How to choose the
addresses to pass to angelboot??
  Thanks,
 Dave

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Fri Oct 15 09:55:26 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id JAA15093
	for <linux-arm-archive@lists.arm.linux.org.uk>; Fri, 15 Oct 1999 09:55:25 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 6420513E58; Fri, 15 Oct 1999 10:55:14 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156905AbPJOIy1>;
	Fri, 15 Oct 1999 04:54:27 -0400
Received: by vger.rutgers.edu id <S157001AbPJOIyM>;
	Fri, 15 Oct 1999 04:54:12 -0400
Received: from ns0.utdallas.edu ([129.110.10.1]:57486 "HELO ns0.utdallas.edu")
	by vger.rutgers.edu with SMTP id <S156970AbPJOIxz>;
	Fri, 15 Oct 1999 04:53:55 -0400
Received: from apache.utdallas.edu (apache.utdallas.edu [129.110.16.9])
	by ns0.utdallas.edu (Postfix) with ESMTP id 93E4D1A002A
	for <linux-arm@vger.rutgers.edu>; Fri, 15 Oct 1999 03:53:56 -0500 (CDT)
Received: from localhost (vasantr@localhost)
	by apache.utdallas.edu (8.9.1/8.9.1) with SMTP id DAA06659
	for <linux-arm@vger.rutgers.edu>; Fri, 15 Oct 1999 03:54:06 -0500 (CDT)
X-Authentication-Warning: apache.utdallas.edu: vasantr owned process doing -bs
Date:   Fri, 15 Oct 1999 03:54:06 -0500 (CDT)
From: Vasant Ramasubramanian <vasantr@utdallas.edu>
To: linux-arm@vger.rutgers.edu
Subject: Can't setup GNU tool chain properly
In-Reply-To: <03fd01bf167a$2861ea30$529765d8@java>
Message-ID: <Pine.GSO.3.96.991015032946.6343A-100000@apache.utdallas.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Hello all!

I am trying to setup the GNU tool chain (again) under Linux for use with
my Brutus board only I've run into a few snags.

I am running a relatively clean installation of RedHat 6.1...

I've been following the directions's from Inte's site:
developer.intel.com/design/strong/applnots/sa11001x/getstart.htm#1001539
(alternativly just goto developer.intel.com choose StrongARM for products
and choose application notes then choose Linux...).

The only real difference between what I've done and what's on the Intel
site as far as GNU packages is that I'm using EGCS 1.1.2 and the
apropriate ARM patch from Phil. B as opposed to EGCS 1.1.1 and a patch.

At anyrate, I get to "Building the EGCS C++ Compiler" and everything seems
to execute fine (I do get an error message when building EGCS that when it
tested it to compile a program it failed; the last step of the make).

None the less I drudged through, and wrote the hello world progarm
(exactly as Intel has it, no crazy stuff here) and when I tried to compile
it failed.

This is the output from arm-linux-gcc:

[root@c1007135-a egcs-1.1.2]# arm-linux-gcc -v -o helloarm hello.c
Reading specs from /usr/local/arm/lib/gcc-lib/arm-linux/egcs-2.91.66/specs
gcc version egcs-2.91.66 19990325/philb (egcs-1.1.2 release)
 /usr/local/arm/lib/gcc-lib/arm-linux/egcs-2.91.66/cpp -lang-c -v -undef
-D__GNUC__=2 -D__GNUC_MINOR__=91 -Dunix -Darm -Dlinux -D__ELF__ -D__unix__
-D__arm__ -D__linux__ -D__ELF__ -D__unix -D__arm -D__linux -Asystem(unix)
-Asystem(posix) -Acpu(arm) -Amachine(arm) -D__CHAR_UNSIGNED__
-D__ARM_ARCH_3__ -D__APCS_32__ hello.c /tmp/cc2dn0Yd.i
GNU CPP version egcs-2.91.66 19990325/philb (egcs-1.1.2 release) (ARM
GNU/Linux with ELF)
#include "..." search starts here:
#include <...> search starts here:
 /usr/local/arm/lib/gcc-lib/arm-linux/egcs-2.91.66/include
 /usr/local/arm/arm-linux/sys-include
 /usr/local/arm/arm-linux/include
End of search list.
 /usr/local/arm/lib/gcc-lib/arm-linux/egcs-2.91.66/cc1 /tmp/cc2dn0Yd.i
-quiet -dumpbase hello.c -version -o /tmp/ccoDhfwp.s
GNU C version egcs-2.91.66 19990325/philb (egcs-1.1.2 release) (arm-linux)
compiled by GNU C version egcs-2.91.66 19990314/Linux (egcs-1.1.2
release).
 /usr/local/arm/arm-linux/bin/as -o /tmp/ccQRaJvG.o /tmp/ccoDhfwp.s
 /usr/local/arm/lib/gcc-lib/arm-linux/egcs-2.91.66/collect2
-dynamic-linker /lib/ld-linux.so.2 -X -m elf32arm -o helloarm crt1.o
crti.o /usr/local/arm/lib/gcc-lib/arm-linux/egcs-2.91.66/crtbegin.o
-L/usr/local/arm/lib/gcc-lib/arm-linux/egcs-2.91.66
-L/usr/local/arm/arm-linux/lib /tmp/ccQRaJvG.o -lgcc -lc -lgcc
/usr/local/arm/lib/gcc-lib/arm-linux/egcs-2.91.66/crtend.o crtn.o
/usr/local/arm/arm-linux/bin/ld: cannot open crt1.o: No such file or
directory
collect2: ld returned 1 exit status

The binutils are in my path (permanently as executed by my bash_profile).

I followed Intel's directoy conventions to the letter (I changed nothing).
Furthermore, I've tried re-doing the EGCS compile, GLIBC etc. all from
scratch and no such luck. (I've removed the armbuild directory and the
Linux kernel source 2.2.2 entirely and started over, that didn't help).

I was told that I need to use "ldconfig" but running that under /sbin/
(/sbin/./ldconfig) didn't help. I read the man page but that didn't give
me any real direction.

FYI: searching for crt1.o, I found it in (using whereis) /usr/lib

I'd appreciate any suggestions/pointers to getting the GNU stuff properly
setup. Should I use newer versions of BinUtils and EGCS? If so what
patches will I need to apply? My current target is Brutus (SA-1100).

I've gotten the ARM SDT 2.5 tools to "work"  on Win95 (if you call having
to exit and re-start everytime you wanna load a new image) so I know
Brutus is ready to boot Linux!

If I wanted the output "console" (Linux login, etc) to appear on the LCD
would I have to write the LCD driver or is there something I can use to
get basic text on the screen? Anything for the keyboard IC (USAR
SPICoder)? 

Thanks for the help and sorry if this is too "newbeish." 

Vasant.

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Fri Oct 15 11:06:23 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id LAA17864
	for <linux-arm-archive@lists.arm.linux.org.uk>; Fri, 15 Oct 1999 11:06:23 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 681AE14130; Fri, 15 Oct 1999 12:06:21 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156919AbPJOKFv>;
	Fri, 15 Oct 1999 06:05:51 -0400
Received: by vger.rutgers.edu id <S156833AbPJOKFj>;
	Fri, 15 Oct 1999 06:05:39 -0400
Received: from nexusel.demon.co.uk ([158.152.30.195]:17829 "EHLO
        globe.nexus.co.uk") by vger.rutgers.edu with ESMTP
	id <S156840AbPJOKBA>; Fri, 15 Oct 1999 06:01:00 -0400
Received: from [192.0.0.21] (helo=fountain.nexus.co.uk ident=mail)
	by globe.nexus.co.uk with smtp (Exim 2.12 #1)
	id 11c3rO-0003nl-00; Fri, 15 Oct 1999 10:41:14 +0100
Received: from [127.0.0.1] (helo=fountain ident=pb)
	by fountain.nexus.co.uk with esmtp (Exim 3.03 #1)
	id 11c3rN-0004FG-00; Fri, 15 Oct 1999 10:41:13 +0100
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: Vasant Ramasubramanian <vasantr@utdallas.edu>
Cc: linux-arm@vger.rutgers.edu
Subject: Re: Can't setup GNU tool chain properly 
In-Reply-To: Message from Vasant Ramasubramanian <vasantr@utdallas.edu> 
   of "Fri, 15 Oct 1999 03:54:06 CDT." <Pine.GSO.3.96.991015032946.6343A-100000@apache.utdallas.edu> 
References: <Pine.GSO.3.96.991015032946.6343A-100000@apache.utdallas.edu> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date:   Fri, 15 Oct 1999 10:41:12 +0100
From: Philip Blundell <pb@nexus.co.uk>
Message-Id: <E11c3rN-0004FG-00@fountain.nexus.co.uk>
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

>The only real difference between what I've done and what's on the Intel
>site as far as GNU packages is that I'm using EGCS 1.1.2 and the
>apropriate ARM patch from Phil. B as opposed to EGCS 1.1.1 and a patch.

You should probably consider using gcc 2.95.1 now.

>I followed Intel's directoy conventions to the letter (I changed nothing).

I think Intel's instructions are wrong; this has been discussed here recently.
See the mailing list archives.

>If I wanted the output "console" (Linux login, etc) to appear on the LCD
>would I have to write the LCD driver or is there something I can use to
>get basic text on the screen? Anything for the keyboard IC (USAR
>SPICoder)? 

I think there is a Brutus framebuffer driver now.  Nico can probably give a 
more definite answer.

p.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Fri Oct 15 15:36:02 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id PAA30055
	for <linux-arm-archive@lists.arm.linux.org.uk>; Fri, 15 Oct 1999 15:36:01 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 4CCE4141C2; Fri, 15 Oct 1999 16:36:00 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157020AbPJOOfL>;
	Fri, 15 Oct 1999 10:35:11 -0400
Received: by vger.rutgers.edu id <S156993AbPJOOdp>;
	Fri, 15 Oct 1999 10:33:45 -0400
Received: from modemcable233.137-200-24.mtl.mc.videotron.net ([24.200.137.233]:61728
        "EHLO xanadu.gn.com") by vger.rutgers.edu with ESMTP
	id <S156938AbPJOOdI>; Fri, 15 Oct 1999 10:33:08 -0400
Received: from localhost (nico@localhost)
	by xanadu.gn.com (8.9.3/8.9.3) with ESMTP id KAA03307;
	Fri, 15 Oct 1999 10:27:09 -0400
X-Authentication-Warning: xanadu.gn.com: nico owned process doing -bs
Date:   Fri, 15 Oct 1999 10:27:09 -0400 (EDT)
From: Nicolas Pitre <nico@cam.org>
X-Sender: nico@xanadu.gn.com
To: Philip Blundell <pb@nexus.co.uk>
Cc: Vasant Ramasubramanian <vasantr@utdallas.edu>, linux-arm@vger.rutgers.edu
Subject: Re: Can't setup GNU tool chain properly 
In-Reply-To: <E11c3rN-0004FG-00@fountain.nexus.co.uk>
Message-ID: <Pine.LNX.4.10.9910151010560.3292-100000@xanadu.gn.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing



On Fri, 15 Oct 1999, Philip Blundell wrote:

> >The only real difference between what I've done and what's on the Intel
> >site as far as GNU packages is that I'm using EGCS 1.1.2 and the
> >apropriate ARM patch from Phil. B as opposed to EGCS 1.1.1 and a patch.
> 
> You should probably consider using gcc 2.95.1 now.

The problem is that my kernels crash quite rapidly if compiled with
gcc-2.95.x and I didn't got around to find the problem yet.  No problem
with user space apps though.

> >I followed Intel's directoy conventions to the letter (I changed nothing).
> 
> I think Intel's instructions are wrong; this has been discussed here recently.
> See the mailing list archives.

I have a tarball with my current working toolset binaries which is a
30-meg file.
I'll try to upload it to ftp.netwinder.org (don't know if I'm allowed to 
however, anybody knows?).  This contains egcs, glibc and all.  This might
help starters...

> >If I wanted the output "console" (Linux login, etc) to appear on the LCD
> >would I have to write the LCD driver or is there something I can use to
> >get basic text on the screen? Anything for the keyboard IC (USAR
> >SPICoder)? 
> 
> I think there is a Brutus framebuffer driver now.  Nico can probably give a 
> more definite answer.

Yes there is.


Nicolas


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Fri Oct 15 15:41:55 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id PAA30240
	for <linux-arm-archive@lists.arm.linux.org.uk>; Fri, 15 Oct 1999 15:41:54 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id B57CE140C8; Fri, 15 Oct 1999 16:41:52 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156912AbPJOOlW>;
	Fri, 15 Oct 1999 10:41:22 -0400
Received: by vger.rutgers.edu id <S156905AbPJOOlP>;
	Fri, 15 Oct 1999 10:41:15 -0400
Received: from nexusel.demon.co.uk ([158.152.30.195]:19123 "EHLO
        globe.nexus.co.uk") by vger.rutgers.edu with ESMTP
	id <S156806AbPJOOk5>; Fri, 15 Oct 1999 10:40:57 -0400
Received: from [192.0.0.21] (helo=fountain.nexus.co.uk ident=mail)
	by globe.nexus.co.uk with smtp (Exim 2.12 #1)
	id 11c8Rx-0004C4-00; Fri, 15 Oct 1999 15:35:17 +0100
Received: from [127.0.0.1] (helo=fountain ident=pb)
	by fountain.nexus.co.uk with esmtp (Exim 3.03 #1)
	id 11c8Rw-0005eV-00; Fri, 15 Oct 1999 15:35:16 +0100
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: Nicolas Pitre <nico@cam.org>
Cc: Vasant Ramasubramanian <vasantr@utdallas.edu>, linux-arm@vger.rutgers.edu
Subject: Re: Can't setup GNU tool chain properly 
In-Reply-To: Message from Nicolas Pitre <nico@cam.org> 
   of "Fri, 15 Oct 1999 10:27:09 EDT." <Pine.LNX.4.10.9910151010560.3292-100000@xanadu.gn.com> 
References: <Pine.LNX.4.10.9910151010560.3292-100000@xanadu.gn.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date:   Fri, 15 Oct 1999 15:35:15 +0100
From: Philip Blundell <pb@nexus.co.uk>
Message-Id: <E11c8Rw-0005eV-00@fountain.nexus.co.uk>
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

>The problem is that my kernels crash quite rapidly if compiled with
>gcc-2.95.x and I didn't got around to find the problem yet.  No problem
>with user space apps though.

Yes, I remember you mentioning this.  Nobody else has reported it so I guess 
it is some SA-1100 specific issue - could be a bug in either the kernel or the 
compiler.

p.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Fri Oct 15 17:29:16 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id RAA02250
	for <linux-arm-archive@lists.arm.linux.org.uk>; Fri, 15 Oct 1999 17:29:15 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id E582213ED6; Fri, 15 Oct 1999 18:27:36 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156944AbPJOQ1E>;
	Fri, 15 Oct 1999 12:27:04 -0400
Received: by vger.rutgers.edu id <S156903AbPJOQ0Q>;
	Fri, 15 Oct 1999 12:26:16 -0400
Received: from [194.201.77.34] ([194.201.77.34]:34324 "HELO
        fw-maid.maidenhead.arm.com") by vger.rutgers.edu with SMTP
	id <S156833AbPJOQ0L>; Fri, 15 Oct 1999 12:26:11 -0400
Received: by fw-maid.maidenhead.arm.com; id SAA12935; Fri, 15 Oct 1999 18:26:34 +0100
Received: from unknown(192.168.2.10) by fw-maid.maidenhead.arm.com via smap (V5.0)
	id xma012931; Fri, 15 Oct 99 18:26:30 +0100
Received: from arm.com (dhcp14 [192.168.2.174])
	by mhsun1.maidenhead.arm.com (8.9.3/8.9.3) with ESMTP id RAA23377;
	Fri, 15 Oct 1999 17:25:32 +0100 (BST)
Message-ID: <380759A9.755BBBE0@arm.com>
Date:   Fri, 15 Oct 1999 17:43:22 +0100
From: David Rusling <david.rusling@arm.com>
X-Mailer: Mozilla 4.5 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Philip Blundell <Philip.Blundell@pobox.com>
Cc: linux-arm@vger.rutgers.edu
Subject: Re: init process/program
References: <199910032348.BAA26576@poekie.test>  <37FA1715.95C48D23@arm.com> <E11YY32-0003f4-00@kings-cross.london.uk.eu.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Philip (et al),

    I have made further progress.   Whilst my statically  linked ash does barf,
nothing else (ie /bin/ls) does.   I ended up writing a sort-of-shell myself as
I tried/tested various things.   I can execute a fair range of commands, including

enough to mount and read an NCR PCI SCSI connected CD drive.  I can
read the files off of it, which is kinda-cool.  Thanks for the hints and tips,
there's
still a way to go but I'm certainly exercising the processor and PCI
subsystem...

Dave

Philip Blundell wrote:

> >I'm using init/inittab etc to start up the system.  Unfortunately, init
> >wants to create files and my file system is read only (very read only).
> >So, for example, it cannot create /dev/initctl and it gets upset.  I'm
> >also seeing some shared library wierdnesses and so I've moved to
> >a staticly  built image.  Oh, and the serial driver is half written.
> >
> >OK, the question.   Is there a brain dead easy init that I can use to
> >get the system off its knees.  I guess the answer is to use a command
>
> Sounds like your best bet is to get the source to sysvinit and chop out the
> bits you don't want.  What sort of problem did you have with shared libraries?
>
> p.
>
> unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

--
----------------------------------------------------------------------
David A Rusling   Consulting Engineer
    ARM Limited
    Liberty House,
    Moorbridge Road,
    Maidenhead, SL6 8LT

    Tel: UK-(0)1628-427754
    Fax: UK-(0)1628-780551
    e-mail: david.rusling@arm.com
----------------------------------------------------------------------


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Fri Oct 15 18:22:03 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id SAA05080
	for <linux-arm-archive@lists.arm.linux.org.uk>; Fri, 15 Oct 1999 18:22:03 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 51BE813EC9; Fri, 15 Oct 1999 19:22:02 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156934AbPJORV2>;
	Fri, 15 Oct 1999 13:21:28 -0400
Received: by vger.rutgers.edu id <S156912AbPJORPn>;
	Fri, 15 Oct 1999 13:15:43 -0400
Received: from mail-gw2.pacbell.net ([206.13.28.53]:37352 "EHLO
        mail-gw2.pacbell.net") by vger.rutgers.edu with ESMTP
	id <S156993AbPJORLz>; Fri, 15 Oct 1999 13:11:55 -0400
Received: from java (adsl-216-101-151-82.dsl.snfc21.pacbell.net [216.101.151.82])
	by mail-gw2.pacbell.net (8.9.3/8.9.3) with SMTP id KAA03005
	for <linux-arm@vger.rutgers.edu>; Fri, 15 Oct 1999 10:11:53 -0700 (PDT)
Message-ID: <04bd01bf1731$adfae2c0$529765d8@java>
From: "Dave Borja" <dave_bb@pacbell.net>
To: "linux-arm" <linux-arm@vger.rutgers.edu>
Subject: Re: Can't setup GNU tool chain properly
Date:   Fri, 15 Oct 1999 10:21:12 -0700
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.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

I agree, the intel site is wrong on how to set the prefix
when making glibc. I had the same problem with the compiler
but it went away when I set  --prefix=/usr/local/arm/arm-linux
(/usr/ocal/arm is where I put all the arm cross development
stuff)....


>>The only real difference between what I've done and what's on the Intel
>>site as far as GNU packages is that I'm using EGCS 1.1.2 and the
>>apropriate ARM patch from Phil. B as opposed to EGCS 1.1.1 and a patch.
>
>You should probably consider using gcc 2.95.1 now.
>
>>I followed Intel's directoy conventions to the letter (I changed nothing).
>
>I think Intel's instructions are wrong; this has been discussed here
recently.
>See the mailing list archives.
>
>>If I wanted the output "console" (Linux login, etc) to appear on the LCD
>>would I have to write the LCD driver or is there something I can use to
>>get basic text on the screen? Anything for the keyboard IC (USAR
>>SPICoder)?
>
>I think there is a Brutus framebuffer driver now.  Nico can probably give a
>more definite answer.
>
>p.
>
>
>unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu
>

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Fri Oct 15 19:56:05 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id TAA08451
	for <linux-arm-archive@lists.arm.linux.org.uk>; Fri, 15 Oct 1999 19:56:05 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 95DB1141A8; Fri, 15 Oct 1999 20:55:22 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157012AbPJOSyM>;
	Fri, 15 Oct 1999 14:54:12 -0400
Received: by vger.rutgers.edu id <S157008AbPJOSfp>;
	Fri, 15 Oct 1999 14:35:45 -0400
Received: from sparkle.Generation.NET ([205.205.119.4]:48787 "EHLO
        sparkle.Generation.NET") by vger.rutgers.edu with ESMTP
	id <S157104AbPJOScE>; Fri, 15 Oct 1999 14:32:04 -0400
Received: from dual (generic253.197.205.205.IN-ADDR.ARPA [205.205.197.253] (may be forged))
	by sparkle.Generation.NET (8.9.3/8.9.3) with SMTP id OAA15916
	for <linux-arm@vger.rutgers.edu>; Fri, 15 Oct 1999 14:32:15 -0400 (EDT)
From: Francois Desloges <fd@vipswitch.com>
To: linux-arm@vger.rutgers.edu
Subject: Creating a toolchain package
Date:   Fri, 15 Oct 1999 14:14:52 -0400
Content-Type: text/plain
MIME-Version: 1.0
Message-Id: <99101514293400.01094@dual>
Content-Transfer-Encoding: 8bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

I want to create a ARM-Linux toolchain package with the i386/ARM cross-compile
toolchain I've built.

I plan to include in it:
- the complete /usr/arm-linux directory (wich is the TARGET-PREFIX directory I
used when I built the toolchain according to Chris Rutter's guide terminology) -
- all /usr/bin/arm-linux-* binaries
- the /usr/lib/gcc-lib/arm-linux directory

Do I forget something?

Thanks in advance for the answers

-- 
François Desloges
fd@vipswitch.com
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Fri Oct 15 20:26:58 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id UAA09345
	for <linux-arm-archive@lists.arm.linux.org.uk>; Fri, 15 Oct 1999 20:26:57 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 36F0C141D2; Fri, 15 Oct 1999 21:26:56 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157275AbPJOTJM>;
	Fri, 15 Oct 1999 15:09:12 -0400
Received: by vger.rutgers.edu id <S157046AbPJOSyT>;
	Fri, 15 Oct 1999 14:54:19 -0400
Received: from [212.219.8.163] ([212.219.8.163]:1046 "HELO inkvine.fluff.org")
	by vger.rutgers.edu with SMTP id <S157274AbPJOSvW>;
	Fri, 15 Oct 1999 14:51:22 -0400
Received: from localhost (localhost [127.0.0.1])
	by inkvine.fluff.org (Postfix) with ESMTP id 16A5046887
	for <linux-arm@vger.rutgers.edu>; Fri, 15 Oct 1999 19:51:20 +0100 (BST)
Date:   Fri, 15 Oct 1999 19:51:20 +0100 (BST)
From: Chris Rutter <chris@fluff.org>
Reply-To: chris@fluff.org
To: ARM Linux mailing list <linux-arm@vger.rutgers.edu>
Subject: Kernel auto-builder
Message-ID: <Pine.LNX.4.10.9910151950090.22086-100000@inkvine.fluff.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

I've got a kernel auto-builder going on inkvine, now.  You can
take a look at its example output:

  ftp.inkvine.fluff.org:/users/chris/lkab/kernels/

I want as many .config files for as much different hardware as
possible, please!  Just mail'em to me.

-- 
Chris <chris@fluff.org>                         ( http://www.fluff.org/chris )

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Fri Oct 15 22:16:54 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id WAA12686
	for <linux-arm-archive@lists.arm.linux.org.uk>; Fri, 15 Oct 1999 22:16:54 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id C20F11419E; Fri, 15 Oct 1999 23:16:52 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156883AbPJOVQN>;
	Fri, 15 Oct 1999 17:16:13 -0400
Received: by vger.rutgers.edu id <S156806AbPJOVP5>;
	Fri, 15 Oct 1999 17:15:57 -0400
Received: from duteinh.et.tudelft.nl ([130.161.42.1]:2090 "HELO
        duteinh.et.tudelft.nl") by vger.rutgers.edu with SMTP
	id <S157039AbPJOVPp>; Fri, 15 Oct 1999 17:15:45 -0400
Received: from dutein75 (dutein75.et.tudelft.nl) by duteinh.et.tudelft.nl (4.1/BB-2.0)
	id AA26840; Fri, 15 Oct 99 23:15:29 +0200
Date:   Fri, 15 Oct 99 23:15:29 +0200
Message-Id: <9910152115.AA26840@duteinh.et.tudelft.nl>
From: Erik Mouw <J.A.K.Mouw@its.tudelft.nl>
To: fd@vipswitch.com
Cc: linux-arm@vger.rutgers.edu
Subject: Re: Creating a toolchain package
In-Reply-To: <99101514293400.01094@dual>
Organization: Eric conspiracy secret labs
X-Face: "!Z|1XjFg!3Iw)BwM^M\k)J5KHiPddz}#/Zw%?$&Q!xqob"OA|})3_@&BTTiQERo?/^g[Z<9P4R8:5C:aqq.cw!hotLc=+u-"+1rq@9$V^8PbOUlodyi_sejt+D`iqkLpx$>.aXl%vnfPIt"LK|/%>94_Zrm8jy?`_[RKt'TuoxUxfk(gMhY(n|DBBl~c$dhO>G%6}R4+DGX3|idBm4oU&UM/XUP4I9aoN{]`ax%B?rgD(I3OJ<62Y6L
X-Mailer: XCmail 0.99.6 - with PGP support, PGP engine version 0.5
X-Mailerorigin: http://www.fsai.fh-trier.de/~schmitzj/Xclasses/XCmail/
X-Eric-Conspiracy: There is no conspiracy!
X-Loop: erik@it.et.tudelft.nl
Mime-Version: 1.0
Content-Type: 	text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

On Fri, 15 Oct 1999 14:14:52 -0400, Francois Desloges wrote:
> I want to create a ARM-Linux toolchain package with the i386/ARM cross-compile
> toolchain I've built.
> 
> I plan to include in it:
> - the complete /usr/arm-linux directory (wich is the TARGET-PREFIX directory I
> used when I built the toolchain according to Chris Rutter's guide terminology)
> -
> - all /usr/bin/arm-linux-* binaries
> - the /usr/lib/gcc-lib/arm-linux directory
> 
> Do I forget something?

Could you install it in /usr/local instead of /usr? In that way the
toolchain won't mess with the distribution's package manager (be it rpm,
dpkg or whatever).


Erik

-- 
J.A.K. (Erik) Mouw, Information and Communication Theory Group, Department
of Electrical Engineering, Faculty of Information Technology and Systems,
Delft University of Technology, PO BOX 5031,  2600 GA Delft, The Netherlands
Phone: +31-15-2785859  Fax: +31-15-2781843  Email J.A.K.Mouw@its.tudelft.nl
WWW: http://www-ict.its.tudelft.nl/~erik/


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Fri Oct 15 23:06:33 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id XAA14205
	for <linux-arm-archive@lists.arm.linux.org.uk>; Fri, 15 Oct 1999 23:06:32 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 618EE13EAF; Sat, 16 Oct 1999 00:06:31 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156903AbPJOWGA>;
	Fri, 15 Oct 1999 18:06:00 -0400
Received: by vger.rutgers.edu id <S156814AbPJOWFt>;
	Fri, 15 Oct 1999 18:05:49 -0400
Received: from proxy2.ba.best.com ([206.184.139.14]:2634 "EHLO
        proxy2.ba.best.com") by vger.rutgers.edu with ESMTP
	id <S156910AbPJOWEI>; Fri, 15 Oct 1999 18:04:08 -0400
Received: from mmtdave (ppp-207-214-213-132.sntc01.pacbell.net [207.214.213.132])
	by proxy2.ba.best.com (8.9.3/8.9.2/best.out) with SMTP id PAA15166;
	Fri, 15 Oct 1999 15:01:02 -0700 (PDT)
Message-ID: <005101bf1758$553d39e0$4df63cd1@mmtdave>
From: "Dave Borja" <daveb@millentek.com>
To: <chris@fluff.org>, "ARM Linux mailing list" <linux-arm@vger.rutgers.edu>
Subject: Re: Kernel auto-builder
Date:   Fri, 15 Oct 1999 14:57:47 -0700
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.3110.1
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Well, I tried the ftp site but there's no permission to
get into lkab dir as anonymous. Is this site just
for the elite?
  Dave Borja
-----Original Message-----
From: Chris Rutter <chris@fluff.org>
To: ARM Linux mailing list <linux-arm@vger.rutgers.edu>
Date: Friday, October 15, 1999 12:30 PM
Subject: Kernel auto-builder


>I've got a kernel auto-builder going on inkvine, now.  You can
>take a look at its example output:
>
>  ftp.inkvine.fluff.org:/users/chris/lkab/kernels/
>
>I want as many .config files for as much different hardware as
>possible, please!  Just mail'em to me.
>
>--
>Chris <chris@fluff.org>
 http://www.fluff.org/chris )
>
>unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu
>

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sat Oct 16 00:24:32 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id AAA16729
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sat, 16 Oct 1999 00:24:32 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 5F473141F3; Sat, 16 Oct 1999 01:23:19 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156929AbPJOXWu>;
	Fri, 15 Oct 1999 19:22:50 -0400
Received: by vger.rutgers.edu id <S156814AbPJOXWp>;
	Fri, 15 Oct 1999 19:22:45 -0400
Received: from m49-nsv3-trogon.tch.cableol.net ([194.168.16.199]:1328 "EHLO
        caramon.armlinux.org.uk") by vger.rutgers.edu with ESMTP
	id <S156929AbPJOXUJ>; Fri, 15 Oct 1999 19:20:09 -0400
Received: from raistlin.armlinux.org.uk (linux@raistlin [192.168.0.3])
	by caramon.armlinux.org.uk (8.8.7/8.8.7) with ESMTP id XAA28514;
	Fri, 15 Oct 1999 23:55:29 +0100
From: linux@arm.linux.org.uk
Received: (from linux@localhost) by raistlin.armlinux.org.uk (8.7.4/8.7.3) id XAA31279; Fri, 15 Oct 1999 23:53:53 +0100
Message-Id: <199910152253.XAA31279@raistlin.armlinux.org.uk>
Subject: Re: init process/program
To: david.rusling@arm.com (David Rusling)
Date:   Fri, 15 Oct 1999 23:53:51 +0100 (BST)
Cc: linux-arm@vger.rutgers.edu
In-Reply-To: <380759A9.755BBBE0@arm.com> from "David Rusling" at Oct 15, 99 05:43:22 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

David Rusling writes:
> > >I'm using init/inittab etc to start up the system.  Unfortunately, init
> > >wants to create files and my file system is read only (very read only).
> > >So, for example, it cannot create /dev/initctl and it gets upset.  I'm
> > >also seeing some shared library wierdnesses and so I've moved to
> > >a staticly  built image.  Oh, and the serial driver is half written.
> > >
> > >OK, the question.   Is there a brain dead easy init that I can use to
> > >get the system off its knees.  I guess the answer is to use a command
> >
> > Sounds like your best bet is to get the source to sysvinit and chop out the
> > bits you don't want.  What sort of problem did you have with shared libraries?

I think I wrote this before, but can't remember (too long ago, too much been
happening, and I've been out on business up to Preston)...

If init is trying to create /dev/initctl and such like, it sounds like
something is going very wrong.  Since the root filesystem is normally
mounted read only when any Linux system comes up, init can't create
/dev/initctl immediately, or indeed write to any part of the filesystem.

When do you get this error?
   _____
  |_____| ------------------------------------------------- ---+---+-
  |   |        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' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sat Oct 16 00:24:58 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id AAA16755
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sat, 16 Oct 1999 00:24:58 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 00E7A14229; Sat, 16 Oct 1999 01:23:38 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156946AbPJOXXT>;
	Fri, 15 Oct 1999 19:23:19 -0400
Received: by vger.rutgers.edu id <S156814AbPJOXWw>;
	Fri, 15 Oct 1999 19:22:52 -0400
Received: from m49-nsv3-trogon.tch.cableol.net ([194.168.16.199]:1328 "EHLO
        caramon.armlinux.org.uk") by vger.rutgers.edu with ESMTP
	id <S156937AbPJOXUW>; Fri, 15 Oct 1999 19:20:22 -0400
Received: from raistlin.armlinux.org.uk (linux@raistlin [192.168.0.3])
	by caramon.armlinux.org.uk (8.8.7/8.8.7) with ESMTP id XAA28458;
	Fri, 15 Oct 1999 23:39:19 +0100
From: linux@arm.linux.org.uk
Received: (from linux@localhost) by raistlin.armlinux.org.uk (8.7.4/8.7.3) id XAA30773; Fri, 15 Oct 1999 23:37:43 +0100
Message-Id: <199910152237.XAA30773@raistlin.armlinux.org.uk>
Subject: Re: TFTP bootloader with dec21041
To: jon@quackware.com (Jonathan Kliegman)
Date:   Fri, 15 Oct 1999 23:37:42 +0100 (BST)
Cc: cbo@nanoteq.co.za, linux-arm@vger.rutgers.edu
In-Reply-To: <38027EA7.8F83BA7D@quackware.com> from "Jonathan Kliegman" at Oct 11, 99 05:19:51 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Jonathan Kliegman writes:
> Chris Bohme wrote:
> > I have tried to boot linux with russell's bootloader via tftp using the
> > DEC 21041 card.
> 
> Try using the tulip.c driver instead.  It is written to take into
> account the cache coherency (or lack of) on the StrongARM.  The 'while
> (transdesc[0] & 0x80000000);' line looks like it will not work unless
> the region of RAM it's reading from is marked uncacheable (which isn't
> likely).

This is unlikely to help - Chris doesn't have the kernel running yet!
Also, the EBSA BIOS runs without D-cache, write buffer, or MMU.
   _____
  |_____| ------------------------------------------------- ---+---+-
  |   |        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' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sat Oct 16 00:27:34 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id AAA16977
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sat, 16 Oct 1999 00:27:33 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id BE8C413E22; Sat, 16 Oct 1999 01:27:31 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156918AbPJOX1B>;
	Fri, 15 Oct 1999 19:27:01 -0400
Received: by vger.rutgers.edu id <S156814AbPJOX0n>;
	Fri, 15 Oct 1999 19:26:43 -0400
Received: from m49-nsv3-trogon.tch.cableol.net ([194.168.16.199]:1331 "EHLO
        caramon.armlinux.org.uk") by vger.rutgers.edu with ESMTP
	id <S156918AbPJOX0b>; Fri, 15 Oct 1999 19:26:31 -0400
Received: from raistlin.armlinux.org.uk (linux@raistlin [192.168.0.3])
	by caramon.armlinux.org.uk (8.8.7/8.8.7) with ESMTP id XAA28480;
	Fri, 15 Oct 1999 23:44:23 +0100
From: linux@arm.linux.org.uk
Received: (from linux@localhost) by raistlin.armlinux.org.uk (8.7.4/8.7.3) id XAA30885; Fri, 15 Oct 1999 23:42:47 +0100
Message-Id: <199910152242.XAA30885@raistlin.armlinux.org.uk>
Subject: Re: Re(2): TFTP bootloader with dec21041
To: benh@mipsys.com (Benjamin Herrenschmidt)
Date:   Fri, 15 Oct 1999 23:42:46 +0100 (BST)
Cc: jon@quackware.com, linux-arm@vger.rutgers.edu
In-Reply-To: <19991012101434.012096@mailhost.mipsys.com> from "Benjamin Herrenschmidt" at Oct 12, 99 10:14:34 am
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Benjamin Herrenschmidt writes:
> No, he's not using the Linux kernel, but Russel's bootloader, which runs
> with data cache disabled, so this should not be an issue. I should put
> your hand on the chip's documentation, you probably lack some kind of
> initialisation (do you have a PROM providing the hw eth adress for
> example ? If you don't you'll probably have to set it up manually from
> the driver).

>From what I remember reading in the tulip driver, isn't the method by
which the media interface is selected very card specific and involves
magic numbers being poked into several registers?

I have seen some ethernet cards behave dead if the wrong type of media
is selected, and it sounds like this tulip is behaving in a similar way.
   _____
  |_____| ------------------------------------------------- ---+---+-
  |   |        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' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sat Oct 16 00:39:15 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id AAA17452
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sat, 16 Oct 1999 00:39:14 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 8A35B13E91; Sat, 16 Oct 1999 01:38:44 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156927AbPJOXiO>;
	Fri, 15 Oct 1999 19:38:14 -0400
Received: by vger.rutgers.edu id <S156903AbPJOXhz>;
	Fri, 15 Oct 1999 19:37:55 -0400
Received: from ns0.utdallas.edu ([129.110.10.1]:47283 "HELO ns0.utdallas.edu")
	by vger.rutgers.edu with SMTP id <S156934AbPJOXhj>;
	Fri, 15 Oct 1999 19:37:39 -0400
Received: from apache.utdallas.edu (apache.utdallas.edu [129.110.16.9])
	by ns0.utdallas.edu (Postfix) with ESMTP
	id 567461A0011; Fri, 15 Oct 1999 18:37:38 -0500 (CDT)
Received: from localhost (vasantr@localhost)
	by apache.utdallas.edu (8.9.1/8.9.1) with SMTP id SAA18164;
	Fri, 15 Oct 1999 18:37:49 -0500 (CDT)
X-Authentication-Warning: apache.utdallas.edu: vasantr owned process doing -bs
Date:   Fri, 15 Oct 1999 18:37:49 -0500 (CDT)
From: Vasant Ramasubramanian <vasantr@utdallas.edu>
To: Dave Borja <dave_bb@pacbell.net>
Cc: linux-arm <linux-arm@vger.rutgers.edu>
Subject: Re: Can't setup GNU tool chain properly
In-Reply-To: <04bd01bf1731$adfae2c0$529765d8@java>
Message-ID: <Pine.GSO.3.96.991015183550.15397B-100000@apache.utdallas.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing



On Fri, 15 Oct 1999, Dave Borja wrote:

> I agree, the intel site is wrong on how to set the prefix
> when making glibc. I had the same problem with the compiler
> but it went away when I set  --prefix=/usr/local/arm/arm-linux
> (/usr/ocal/arm is where I put all the arm cross development
> stuff)....

Thanks Dave! That did the trick! It compiled my hello world program.

I'll inform Intel of the mistake in the documentation (unless it's
already been done?).

Now how does one add framebuffer support to Brutus? (do I do this when
compiling the 2.2.2 kernel with the patches or do I need to obtain another
patch/file?)

Thanks for the help!

Vasant.


> 
> 
> >>The only real difference between what I've done and what's on the Intel
> >>site as far as GNU packages is that I'm using EGCS 1.1.2 and the
> >>apropriate ARM patch from Phil. B as opposed to EGCS 1.1.1 and a patch.
> >
> >You should probably consider using gcc 2.95.1 now.
> >
> >>I followed Intel's directoy conventions to the letter (I changed nothing).
> >
> >I think Intel's instructions are wrong; this has been discussed here
> recently.
> >See the mailing list archives.
> >
> >>If I wanted the output "console" (Linux login, etc) to appear on the LCD
> >>would I have to write the LCD driver or is there something I can use to
> >>get basic text on the screen? Anything for the keyboard IC (USAR
> >>SPICoder)?
> >
> >I think there is a Brutus framebuffer driver now.  Nico can probably give a
> >more definite answer.
> >
> >p.
> >
> >
> >unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu
> >
> 
> unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu
> 

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sat Oct 16 02:01:52 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id CAA21422
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sat, 16 Oct 1999 02:01:51 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id BC26213E4F; Sat, 16 Oct 1999 03:01:27 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156982AbPJPBAv>;
	Fri, 15 Oct 1999 21:00:51 -0400
Received: by vger.rutgers.edu id <S156948AbPJPBAe>;
	Fri, 15 Oct 1999 21:00:34 -0400
Received: from [212.219.8.163] ([212.219.8.163]:1137 "HELO inkvine.fluff.org")
	by vger.rutgers.edu with SMTP id <S156903AbPJPBAJ>;
	Fri, 15 Oct 1999 21:00:09 -0400
Received: from localhost (localhost [127.0.0.1])
	by inkvine.fluff.org (Postfix) with ESMTP id D413D46887
	for <linux-arm@vger.rutgers.edu>; Sat, 16 Oct 1999 02:00:02 +0100 (BST)
Date:   Sat, 16 Oct 1999 02:00:02 +0100 (BST)
From: Chris Rutter <chris@fluff.org>
Reply-To: chris@fluff.org
To: ARM Linux mailing list <linux-arm@vger.rutgers.edu>
Subject: lkab: Oops.
Message-ID: <Pine.LNX.4.10.9910160159060.22086-100000@inkvine.fluff.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Sorry for the permissions boo-boo.  All fixed now.

Would peope be on, perhaps, for a `submit your config file and have
a kernel built with the latest tools immediately' sort of jaunt?

With the new scripts I've done, that would be absolutely trivial...

-- 
Chris <chris@fluff.org>                         ( http://www.fluff.org/chris )

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sat Oct 16 03:28:58 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id DAA23598
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sat, 16 Oct 1999 03:28:57 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 29A7213D8F; Sat, 16 Oct 1999 04:28:56 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156924AbPJPC2b>;
	Fri, 15 Oct 1999 22:28:31 -0400
Received: by vger.rutgers.edu id <S156917AbPJPC2M>;
	Fri, 15 Oct 1999 22:28:12 -0400
Received: from nexus.carleton.ca ([134.117.76.10]:1108 "EHLO nexus.carleton.ca")
	by vger.rutgers.edu with ESMTP id <S156814AbPJPC2B>;
	Fri, 15 Oct 1999 22:28:01 -0400
Received: from localhost (stewart@localhost)
	by nexus.carleton.ca (8.9.3/8.9.3) with ESMTP id WAA04699
	for <linux-arm@vger.rutgers.edu>; Fri, 15 Oct 1999 22:27:41 -0400
Date:   Fri, 15 Oct 1999 22:27:40 -0400 (EDT)
From: Rod Stewart <stewart@nexus.carleton.ca>
To: ARM Linux mailing list <linux-arm@vger.rutgers.edu>
Subject: which modutils is working?
Message-ID: <Pine.LNX.4.10.9910152155090.4350-100000@nexus.carleton.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing


Q:  Which version of modutils is safe to use?

I currenlty have modutils 2.3.5 from
	ftp://ftp.ocs.com.au/pub/modutils/v2.3/
And:
  [root@brakiri SRPMS]# rpm -q glibc  gcc binutils modutils 
  glibc-2.1.2-0.titan.f
  gcc-2.95.1-0.titan.f
  binutils-2.9.5.0.14-1.titan.f
  modutils-2.3.5-1.titan.a

My problem is it dies with:
	modprobe ne2k-pci
in create_module("ne2k-pci", 4868) with a seg fault.

It installs the 8390.o module fine, but has trouble with the 
ne2k-pci one.  If I now "rmmod ne2k-pci" module, and insmod it
again (without removing the 8390 one) it works fine.

Anyone else having trouble with modprobe when using binutils 2.9.5?
Did I miss a patch somewhere?

Thanks,
-Rms


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sat Oct 16 10:45:03 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id KAA02755
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sat, 16 Oct 1999 10:45:02 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 32B0513F34; Sat, 16 Oct 1999 11:45:01 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156918AbPJPJob>;
	Sat, 16 Oct 1999 05:44:31 -0400
Received: by vger.rutgers.edu id <S156973AbPJPJoU>;
	Sat, 16 Oct 1999 05:44:20 -0400
Received: from m54-nsv3-trogon.tch.cableol.net ([194.168.16.204]:1444 "EHLO
        caramon.armlinux.org.uk") by vger.rutgers.edu with ESMTP
	id <S156918AbPJPJls>; Sat, 16 Oct 1999 05:41:48 -0400
Received: from raistlin.armlinux.org.uk (linux@raistlin [192.168.0.3])
	by caramon.armlinux.org.uk (8.8.7/8.8.7) with ESMTP id KAA30279;
	Sat, 16 Oct 1999 10:26:24 +0100
From: linux@arm.linux.org.uk
Received: (from linux@localhost) by raistlin.armlinux.org.uk (8.7.4/8.7.3) id KAA01557; Sat, 16 Oct 1999 10:24:46 +0100
Message-Id: <199910160924.KAA01557@raistlin.armlinux.org.uk>
Subject: Re: lkab: Oops.
To: chris@fluff.org
Date:   Sat, 16 Oct 1999 10:24:45 +0100 (BST)
Cc: linux-arm@vger.rutgers.edu
In-Reply-To: <Pine.LNX.4.10.9910160159060.22086-100000@inkvine.fluff.org> from "Chris Rutter" at Oct 16, 99 02:00:02 am
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Chris Rutter writes:
> Would peope be on, perhaps, for a `submit your config file and have
> a kernel built with the latest tools immediately' sort of jaunt?

Define "latest tools".  Past history suggests that this will lead to
unstable kernels.  Also, with each kernel you should supply the
toolchain version information so that when a problem does occur,
people know which versions of what to blame.
   _____
  |_____| ------------------------------------------------- ---+---+-
  |   |        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' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sat Oct 16 11:10:38 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id LAA03475
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sat, 16 Oct 1999 11:10:38 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 07D4513F35; Sat, 16 Oct 1999 12:10:37 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156918AbPJPKKP>;
	Sat, 16 Oct 1999 06:10:15 -0400
Received: by vger.rutgers.edu id <S156917AbPJPKKH>;
	Sat, 16 Oct 1999 06:10:07 -0400
Received: from tazenda.demon.co.uk ([158.152.220.239]:1676 "EHLO
        kings-cross.london.uk.eu.org") by vger.rutgers.edu with ESMTP
	id <S156903AbPJPKJu>; Sat, 16 Oct 1999 06:09:50 -0400
Received: from localhost
	([127.0.0.1] helo=kings-cross.london.uk.eu.org ident=phil)
	by kings-cross.london.uk.eu.org with esmtp (Exim 2.05 #1)
	id 11cIFR-0007Oe-00; Sat, 16 Oct 1999 02:03:01 +0100
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: Erik Mouw <J.A.K.Mouw@its.tudelft.nl>
Cc: fd@vipswitch.com, linux-arm@vger.rutgers.edu
Subject: Re: Creating a toolchain package 
In-Reply-To: Message from Erik Mouw <J.A.K.Mouw@its.tudelft.nl> 
   of "Fri, 15 Oct 1999 23:15:29 +0200." <9910152115.AA26840@duteinh.et.tudelft.nl> 
References: <9910152115.AA26840@duteinh.et.tudelft.nl> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date:   Sat, 16 Oct 1999 02:03:01 +0100
From: Philip Blundell <Philip.Blundell@pobox.com>
Message-Id: <E11cIFR-0007Oe-00@kings-cross.london.uk.eu.org>
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

>Could you install it in /usr/local instead of /usr? In that way the
>toolchain won't mess with the distribution's package manager (be it rpm,
>dpkg or whatever).

It won't do any harm anyway.  Neither dpkg nor RPM care if you install extra 
files in /usr.

p.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sat Oct 16 17:34:24 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id RAA14705
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sat, 16 Oct 1999 17:34:23 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 96C8713F1B; Sat, 16 Oct 1999 18:34:10 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156970AbPJPQdl>;
	Sat, 16 Oct 1999 12:33:41 -0400
Received: by vger.rutgers.edu id <S156918AbPJPQdR>;
	Sat, 16 Oct 1999 12:33:17 -0400
Received: from tazenda.demon.co.uk ([158.152.220.239]:1813 "EHLO
        kings-cross.london.uk.eu.org") by vger.rutgers.edu with ESMTP
	id <S157014AbPJPQdF>; Sat, 16 Oct 1999 12:33:05 -0400
Received: from localhost
	([127.0.0.1] helo=kings-cross.london.uk.eu.org ident=phil)
	by kings-cross.london.uk.eu.org with esmtp (Exim 2.05 #1)
	id 11cVm8-0008Hg-00; Sat, 16 Oct 1999 16:29:40 +0100
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: Rod Stewart <stewart@nexus.carleton.ca>
Cc: ARM Linux mailing list <linux-arm@vger.rutgers.edu>
Subject: Re: which modutils is working? 
In-Reply-To: Message from Rod Stewart <stewart@nexus.carleton.ca> 
   of "Fri, 15 Oct 1999 22:27:40 EDT." <Pine.LNX.4.10.9910152155090.4350-100000@nexus.carleton.ca> 
References: <Pine.LNX.4.10.9910152155090.4350-100000@nexus.carleton.ca> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date:   Sat, 16 Oct 1999 16:29:40 +0100
From: Philip Blundell <Philip.Blundell@pobox.com>
Message-Id: <E11cVm8-0008Hg-00@kings-cross.london.uk.eu.org>
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

>Anyone else having trouble with modprobe when using binutils 2.9.5?
>Did I miss a patch somewhere?

No, it should be fine.  I have also seen this problem from time to time, I'll 
try to track it down.

p.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sat Oct 16 17:38:13 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id RAA14839
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sat, 16 Oct 1999 17:38:13 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id A28F313FB5; Sat, 16 Oct 1999 18:36:31 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157020AbPJPQdn>;
	Sat, 16 Oct 1999 12:33:43 -0400
Received: by vger.rutgers.edu id <S156950AbPJPQdX>;
	Sat, 16 Oct 1999 12:33:23 -0400
Received: from modemcable233.137-200-24.mtl.mc.videotron.net ([24.200.137.233]:61899
        "EHLO xanadu.gn.com") by vger.rutgers.edu with ESMTP
	id <S156948AbPJPQdL>; Sat, 16 Oct 1999 12:33:11 -0400
Received: from localhost (nico@localhost)
	by xanadu.gn.com (8.9.3/8.9.3) with ESMTP id MAA04646;
	Sat, 16 Oct 1999 12:27:40 -0400
X-Authentication-Warning: xanadu.gn.com: nico owned process doing -bs
Date:   Sat, 16 Oct 1999 12:27:40 -0400 (EDT)
From: Nicolas Pitre <nico@cam.org>
X-Sender: nico@xanadu.gn.com
To: Vasant Ramasubramanian <vasantr@utdallas.edu>
Cc: Dave Borja <dave_bb@PACBELL.NET>, linux-arm <linux-arm@vger.rutgers.edu>
Subject: Re: Can't setup GNU tool chain properly
In-Reply-To: <Pine.GSO.3.96.991015183550.15397B-100000@apache.utdallas.edu>
Message-ID: <Pine.LNX.4.10.9910161222320.4639-100000@xanadu.gn.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing



On Fri, 15 Oct 1999, Vasant Ramasubramanian wrote:

> Now how does one add framebuffer support to Brutus? (do I do this when
> compiling the 2.2.2 kernel with the patches or do I need to obtain another
> patch/file?)

I'll suggest you use a more recent kernel, like 2.2.12, with my latest
patch from ftp.netwinder.org/users/n/nico.  Then issue a "make
brutus_config" before "make config".  This will set up all defaults for
Brutus which should include frame buffer support.



Nicolas

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sun Oct 17 12:11:18 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id MAA19298
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sun, 17 Oct 1999 12:11:17 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 6361013E16; Sun, 17 Oct 1999 13:11:09 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156966AbPJQLKi>;
	Sun, 17 Oct 1999 07:10:38 -0400
Received: by vger.rutgers.edu id <S156951AbPJQLK0>;
	Sun, 17 Oct 1999 07:10:26 -0400
Received: from tazenda.demon.co.uk ([158.152.220.239]:1105 "EHLO
        kings-cross.london.uk.eu.org") by vger.rutgers.edu with ESMTP
	id <S157042AbPJQLHD>; Sun, 17 Oct 1999 07:07:03 -0400
Received: from localhost
	([127.0.0.1] helo=kings-cross.london.uk.eu.org ident=phil)
	by kings-cross.london.uk.eu.org with esmtp (Exim 2.05 #1)
	id 11co8u-0005ZN-00
	for linux-arm@vger.rutgers.edu; Sun, 17 Oct 1999 12:06:24 +0100
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: linux-arm@vger.rutgers.edu
Subject: memset benchmarks
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date:   Sun, 17 Oct 1999 12:06:24 +0100
From: Philip Blundell <Philip.Blundell@pobox.com>
Message-Id: <E11co8u-0005ZN-00@kings-cross.london.uk.eu.org>
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Russell asked me to try some benchmarks on some of the "memset" optimizations 
in recent kernels.  I thought I'd post them here in case others are 
interested.

I ran lmbench (version 2alpha10 as it happens) twice in quick succession on 
each kernel.  All the kernels were, I hope, identical other than the memset 
thing.  The machine I used was my CATS.

The "a" kernel is 2.3.19 with Russell's unmodified `memset' macro.
The "b" kernel has the `memset' macro removed from <asm/string.h>, which 
should restore things to how they were in older kernels.
The "c" kernel has the slightly modified `memset' macro that is currently 
in CVS.

p.

Processor, Processes - times in microseconds - smaller is better
----------------------------------------------------------------
Host                 OS  Mhz null null      open selct sig  sig  fork exec sh  
                             call  I/O stat clos       inst hndl proc proc proc
--------- ------------- ---- ---- ---- ---- ---- ----- ---- ---- ---- ---- ----
armv4l-li Linux 2.3.19a  233  0.6  1.3   10   12 0.13K  4.7    4 2.9K  11K  49K
armv4l-li Linux 2.3.19a  233  0.6  1.3    9   12 0.13K  4.7    4 2.9K  11K  49K
armv4l-li Linux 2.3.19b  233  0.6  1.3   10   12 0.13K  4.6    4 2.9K  11K  49K
armv4l-li Linux 2.3.19b  233  0.6  1.3   10   12 0.13K  4.6    4 2.9K  11K  49K
armv4l-li Linux 2.3.19c  233  0.6  1.3   10   12 0.13K  4.6    4 2.9K  11K  49K
armv4l-li Linux 2.3.19c  233  0.6  1.3   10   12 0.13K  4.7    4 2.9K  11K  49K

Context switching - times in microseconds - smaller is better
-------------------------------------------------------------
Host                 OS 2p/0K 2p/16K 2p/64K 8p/16K 8p/64K 16p/16K 16p/64K
                        ctxsw  ctxsw  ctxsw ctxsw  ctxsw   ctxsw   ctxsw
--------- ------------- ----- ------ ------ ------ ------ ------- -------
armv4l-li Linux 2.3.19a  208    425    912   443    926     454     952
armv4l-li Linux 2.3.19a  210    425    917   443    921     460     934
armv4l-li Linux 2.3.19b  206    420    911   423    918     455     939
armv4l-li Linux 2.3.19b  206    420    915   447    958     446     936
armv4l-li Linux 2.3.19c  212    416    909   423    972     444     959
armv4l-li Linux 2.3.19c  207    419    911   451    918     445     941

*Local* Communication latencies in microseconds - smaller is better
-------------------------------------------------------------------
Host                 OS 2p/0K  Pipe AF     UDP  RPC/   TCP  RPC/ TCP
                        ctxsw       UNIX         UDP         TCP conn
--------- ------------- ----- ----- ---- ----- ----- ----- ----- ----
armv4l-li Linux 2.3.19a   208   418 1115   764         983       2204
armv4l-li Linux 2.3.19a   210   429 1031   759         986       2188
armv4l-li Linux 2.3.19b   206   417 1147   765         973       2215
armv4l-li Linux 2.3.19b   206   421 1096   761         988       2199
armv4l-li Linux 2.3.19c   212   422 1196   764         983       2207
armv4l-li Linux 2.3.19c   207   428 1027   759         987       2195

File & VM system latencies in microseconds - smaller is better
--------------------------------------------------------------
Host                 OS   0K File      10K File      Mmap    Prot    Page	
                        Create Delete Create Delete  Latency Fault   Fault 
--------- ------------- ------ ------ ------ ------  ------- -----   ----- 
armv4l-li Linux 2.3.19a                                 5053     2    0.0K
armv4l-li Linux 2.3.19a                                 5017     2    0.0K
armv4l-li Linux 2.3.19b                                 5022     2    0.0K
armv4l-li Linux 2.3.19b                                 5055     2    0.0K
armv4l-li Linux 2.3.19c                                 5009     2    0.0K
armv4l-li Linux 2.3.19c                                 5013     2    0.0K


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sun Oct 17 17:52:36 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id RAA29603
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sun, 17 Oct 1999 17:52:36 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 2572613DC3; Sun, 17 Oct 1999 18:52:34 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157010AbPJQQwI>;
	Sun, 17 Oct 1999 12:52:08 -0400
Received: by vger.rutgers.edu id <S156983AbPJQQvv>;
	Sun, 17 Oct 1999 12:51:51 -0400
Received: from tazenda.demon.co.uk ([158.152.220.239]:1238 "EHLO
        kings-cross.london.uk.eu.org") by vger.rutgers.edu with ESMTP
	id <S156974AbPJQQve>; Sun, 17 Oct 1999 12:51:34 -0400
Received: from localhost
	([127.0.0.1] helo=kings-cross.london.uk.eu.org ident=phil)
	by kings-cross.london.uk.eu.org with esmtp (Exim 2.05 #1)
	id 11ctVn-0006tt-00; Sun, 17 Oct 1999 17:50:23 +0100
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: Rod Stewart <stewart@nexus.carleton.ca>
Cc: ARM Linux mailing list <linux-arm@vger.rutgers.edu>
Subject: Re: which modutils is working? 
In-Reply-To: Message from Rod Stewart <stewart@nexus.carleton.ca> 
   of "Fri, 15 Oct 1999 22:27:40 EDT." <Pine.LNX.4.10.9910152155090.4350-100000@nexus.carleton.ca> 
References: <Pine.LNX.4.10.9910152155090.4350-100000@nexus.carleton.ca> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date:   Sun, 17 Oct 1999 17:50:23 +0100
From: Philip Blundell <Philip.Blundell@pobox.com>
Message-Id: <E11ctVn-0006tt-00@kings-cross.london.uk.eu.org>
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Can you try this patch and see if it helps at all?  It seems to fix a similar 
problem I was having with NFS.

p.

1999-10-17  Philip Blundell  <philb@gnu.org>

	* obj/obj_arm.c (arch_new_symbol): Zero the PLT entry too.
	(arch_apply_relocation): Remove useless assertion.

--- clean/modutils-2.3.5/obj/obj_arm.c	Wed Aug 25 07:26:49 1999
+++ modutils-2.3.5/obj/obj_arm.c	Sun Oct 17 17:20:17 1999
@@ -85,6 +85,7 @@
   struct arm_symbol *sym;
   sym = xmalloc(sizeof(*sym));
   memset(&sym->gotent, 0, sizeof(sym->gotent));
+  memset(&sym->pltent, 0, sizeof(sym->pltent));
   return &sym->root;
 }
 
@@ -151,7 +152,6 @@
       /* find the plt entry and initialize it if necessary */
       assert(asym != NULL);
       pe = (struct arm_plt_entry*) &asym->pltent;
-      assert(pe != NULL);
       if (! pe->inited)
 	{
 	  ip = (unsigned long *) (afile->plt->contents + pe->offset);


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sun Oct 17 21:29:23 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id VAA04193
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sun, 17 Oct 1999 21:29:22 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 0042A13DB5; Sun, 17 Oct 1999 22:29:20 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156978AbPJQU2p>;
	Sun, 17 Oct 1999 16:28:45 -0400
Received: by vger.rutgers.edu id <S156974AbPJQU22>;
	Sun, 17 Oct 1999 16:28:28 -0400
Received: from nexus.carleton.ca ([134.117.76.10]:1857 "EHLO nexus.carleton.ca")
	by vger.rutgers.edu with ESMTP id <S156966AbPJQU2O>;
	Sun, 17 Oct 1999 16:28:14 -0400
Received: from localhost (stewart@localhost)
	by nexus.carleton.ca (8.9.3/8.9.3) with ESMTP id QAA31043;
	Sun, 17 Oct 1999 16:28:07 -0400
Date:   Sun, 17 Oct 1999 16:28:07 -0400 (EDT)
From: Rod Stewart <stewart@nexus.carleton.ca>
To: Philip Blundell <Philip.Blundell@pobox.com>
Cc: ARM Linux mailing list <linux-arm@vger.rutgers.edu>
Subject: Re: which modutils is working? 
In-Reply-To: <E11ctVn-0006tt-00@kings-cross.london.uk.eu.org>
Message-ID: <Pine.LNX.4.10.9910171617390.30817-100000@nexus.carleton.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing


On Sun, 17 Oct 1999, Philip Blundell wrote:

> Can you try this patch and see if it helps at all?  It seems to fix a similar 
> problem I was having with NFS.

Fixes it, thanks.  I can now compile ne2k-pci as a module again.

-Rms

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sun Oct 17 21:48:11 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id VAA05232
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sun, 17 Oct 1999 21:48:05 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 6777A13DFB; Sun, 17 Oct 1999 22:48:04 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156974AbPJQUre>;
	Sun, 17 Oct 1999 16:47:34 -0400
Received: by vger.rutgers.edu id <S156983AbPJQUrU>;
	Sun, 17 Oct 1999 16:47:20 -0400
Received: from [212.219.8.163] ([212.219.8.163]:1496 "HELO inkvine.fluff.org")
	by vger.rutgers.edu with SMTP id <S156966AbPJQUrD>;
	Sun, 17 Oct 1999 16:47:03 -0400
Received: from localhost (localhost [127.0.0.1])
	by inkvine.fluff.org (Postfix) with ESMTP id E132046887
	for <linux-arm@vger.rutgers.edu>; Sun, 17 Oct 1999 21:46:57 +0100 (BST)
Delivered-To: chris@inkvine.fluff.org
X-Received: from relay.is4b.net (peach.oaktree.net.uk [193.82.129.13])
	by inkvine.fluff.org (Postfix) with ESMTP id 7A41946887
	for <chris@inkvine.fluff.org>; Sat, 16 Oct 1999 10:41:53 +0100 (BST)
X-Received: from chalk.oaktree.net.uk (chalk.oaktree.net.uk [193.82.129.19])
	by relay.is4b.net (Postfix) with ESMTP id 2C37D1DC05
	for <chris@inkvine.fluff.org>; Sat, 16 Oct 1999 10:41:53 +0100 (BST)
X-Received: from black.oaktree.co.uk (IDENT:root@black.oaktree.co.uk [193.82.129.7])
	by chalk.oaktree.net.uk (8.9.3/8.9.3) with ESMTP id KAA12555
	for <chris@chalk.oaktree.net.uk>; Sat, 16 Oct 1999 10:41:52 +0100 (BST)
From: linux@arm.linux.org.uk
X-Received: from caramon.armlinux.org.uk (root@m54-nsv3-trogon.tch.cableol.net [194.168.16.204])
	by black.oaktree.co.uk (8.8.8/8.8.8) with ESMTP id KAA12290
	for <chris@fluff.org>; Sat, 16 Oct 1999 10:41:51 +0100 (BST)
X-Received: from raistlin.armlinux.org.uk (linux@raistlin [192.168.0.3])
	by caramon.armlinux.org.uk (8.8.7/8.8.7) with ESMTP id KAA30279;
	Sat, 16 Oct 1999 10:26:24 +0100
X-Received: (from linux@localhost) by raistlin.armlinux.org.uk (8.7.4/8.7.3) id KAA01557; Sat, 16 Oct 1999 10:24:46 +0100
Message-Id: <199910160924.KAA01557@raistlin.armlinux.org.uk>
Subject: Re: lkab: Oops.
To: chris@fluff.org
Date:   Sat, 16 Oct 1999 10:24:45 +0100 (BST)
Cc: linux-arm@vger.rutgers.edu
In-Reply-To: <Pine.LNX.4.10.9910160159060.22086-100000@inkvine.fluff.org> from "Chris Rutter" at Oct 16, 99 02:00:02 am
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Chris Rutter writes:
> Would peope be on, perhaps, for a `submit your config file and have
> a kernel built with the latest tools immediately' sort of jaunt?

Define "latest tools".  Past history suggests that this will lead to
unstable kernels.  Also, with each kernel you should supply the
toolchain version information so that when a problem does occur,
people know which versions of what to blame.
   _____
  |_____| ------------------------------------------------- ---+---+-
  |   |        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' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Mon Oct 18 14:29:12 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id OAA07706
	for <linux-arm-archive@lists.arm.linux.org.uk>; Mon, 18 Oct 1999 14:29:05 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 16AC813DEA; Mon, 18 Oct 1999 15:29:04 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157288AbPJRN2e>;
	Mon, 18 Oct 1999 09:28:34 -0400
Received: by vger.rutgers.edu id <S157189AbPJRN2P>;
	Mon, 18 Oct 1999 09:28:15 -0400
Received: from [212.219.8.163] ([212.219.8.163]:1648 "HELO inkvine.fluff.org")
	by vger.rutgers.edu with SMTP id <S157072AbPJRN2F>;
	Mon, 18 Oct 1999 09:28:05 -0400
Received: from localhost (localhost [127.0.0.1])
	by inkvine.fluff.org (Postfix) with ESMTP id 74D4E46887
	for <linux-arm@vger.rutgers.edu>; Mon, 18 Oct 1999 14:28:00 +0100 (BST)
Date:   Mon, 18 Oct 1999 14:28:00 +0100 (BST)
From: Chris Rutter <chris@fluff.org>
Reply-To: chris@fluff.org
To: ARM Linux mailing list <linux-arm@vger.rutgers.edu>
Subject: Re: lkab: Oops.
Message-ID: <Pine.LNX.4.10.9910181427310.6947-100000@inkvine.fluff.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

[This didn't seem to get through last time.]

On Sat, 16 Oct 1999 linux@arm.linux.org.uk wrote:

> Define "latest tools".  Past history suggests that this will lead to
> unstable kernels.  Also, with each kernel you should supply the
> toolchain version information so that when a problem does occur,
> people know which versions of what to blame.

My casual definition of `latest tools' would the latest versions
of binutils and gcc that had been used by the standard ARM hackers
with any success.

I don't see why it should lead to any more unstable kernels than
everyone is using at the moment.  Most people who I catch building
their own kernels these days seem to be using binutils 2.9.5 and
gcc 2.95 -- I think those could fairly be called the `latest tools',
and I haven't noticed any widespread complaints of instability?

I think the one about the kernels failing if you build them with a
gcc later than 2.3 or whatever it was actually was fixed three or
four years ago or something.

Maybe if you followed my toolchain guide you might get a set of
tools which built kernels okay. ;-)

However, if you like, I'll happily output toolchain version data
for each kernel built.  Fair enough?

-- 
Chris <chris@fluff.org>                         ( http://www.fluff.org/chris )


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Mon Oct 18 16:17:53 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id QAA10907
	for <linux-arm-archive@lists.arm.linux.org.uk>; Mon, 18 Oct 1999 16:17:52 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 7E45113DAC; Mon, 18 Oct 1999 17:17:50 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157356AbPJRPRR>;
	Mon, 18 Oct 1999 11:17:17 -0400
Received: by vger.rutgers.edu id <S157222AbPJRPQ6>;
	Mon, 18 Oct 1999 11:16:58 -0400
Received: from tazenda.demon.co.uk ([158.152.220.239]:1112 "EHLO
        kings-cross.london.uk.eu.org") by vger.rutgers.edu with ESMTP
	id <S157330AbPJRPQh>; Mon, 18 Oct 1999 11:16:37 -0400
Received: from localhost
	([127.0.0.1] helo=kings-cross.london.uk.eu.org ident=phil)
	by kings-cross.london.uk.eu.org with esmtp (Exim 2.05 #1)
	id 11dEVz-0004SZ-00
	for linux-arm@vger.rutgers.edu; Mon, 18 Oct 1999 16:15:59 +0100
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: ARM Linux mailing list <linux-arm@vger.rutgers.edu>
Subject: Re: lkab: Oops. 
In-Reply-To: Message from Chris Rutter <chris@fluff.org> 
   of "Mon, 18 Oct 1999 14:28:00 BST." <Pine.LNX.4.10.9910181427310.6947-100000@inkvine.fluff.org> 
References: <Pine.LNX.4.10.9910181427310.6947-100000@inkvine.fluff.org> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date:   Mon, 18 Oct 1999 16:15:59 +0100
From: Philip Blundell <Philip.Blundell@pobox.com>
Message-Id: <E11dEVz-0004SZ-00@kings-cross.london.uk.eu.org>
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Chris Rutter wrote:

>I don't see why it should lead to any more unstable kernels than
>everyone is using at the moment.  Most people who I catch building
>their own kernels these days seem to be using binutils 2.9.5 and
>gcc 2.95 -- I think those could fairly be called the `latest tools',
>and I haven't noticed any widespread complaints of instability?

I believe that pretty much all the distribution builders are using these tools 
to build their kernels these days.  So if there are problems we ought to hear 
about them fairly quickly.

The only issue I'm aware of with the "new" tools, as opposed to say GCC 2.8, 
is this business with the (2.2-derived) SA-1100 kernels apparently not 
working, which nobody has yet found time to debug.

p.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Tue Oct 19 16:54:37 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id QAA15593
	for <linux-arm-archive@lists.arm.linux.org.uk>; Tue, 19 Oct 1999 16:54:36 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id C6E9613F17; Tue, 19 Oct 1999 17:54:34 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S160060AbPJSPxY>;
	Tue, 19 Oct 1999 11:53:24 -0400
Received: by vger.rutgers.edu id <S160040AbPJSPri>;
	Tue, 19 Oct 1999 11:47:38 -0400
Received: from sparkle.Generation.NET ([205.205.119.4]:33132 "EHLO
        sparkle.Generation.NET") by vger.rutgers.edu with ESMTP
	id <S160094AbPJSPnZ>; Tue, 19 Oct 1999 11:43:25 -0400
Received: from dual (generic253.197.205.205.IN-ADDR.ARPA [205.205.197.253] (may be forged))
	by sparkle.Generation.NET (8.9.3/8.9.3) with SMTP id LAA24422
	for <linux-arm@vger.rutgers.edu>; Tue, 19 Oct 1999 11:43:36 -0400 (EDT)
From: Francois Desloges <fd@vipswitch.com>
To: linux-arm@vger.rutgers.edu
Subject: 3c905B NIC + EBSA?
Date:   Tue, 19 Oct 1999 11:35:48 -0400
Content-Type: text/plain
MIME-Version: 1.0
Message-Id: <99101911404801.00780@dual>
Content-Transfer-Encoding: 8bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

I'v read somewhere in the july Mailing List Archive that people were having
problems with 3Com 3c905B NIC on the EBSA285?
Anybody knows the recent status of success/failure with 3c905B + EBSA285 ?

Thank you :)

-- 
François Desloges
fd@vipswitch.com
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Tue Oct 19 19:17:40 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id TAA24940
	for <linux-arm-archive@lists.arm.linux.org.uk>; Tue, 19 Oct 1999 19:17:40 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id E0FB413F9A; Tue, 19 Oct 1999 20:17:38 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S160154AbPJSSJo>;
	Tue, 19 Oct 1999 14:09:44 -0400
Received: by vger.rutgers.edu id <S160163AbPJSSCU>;
	Tue, 19 Oct 1999 14:02:20 -0400
Received: from tazenda.demon.co.uk ([158.152.220.239]:1282 "EHLO
        kings-cross.london.uk.eu.org") by vger.rutgers.edu with ESMTP
	id <S157380AbPJSSAm>; Tue, 19 Oct 1999 14:00:42 -0400
Received: from localhost
	([127.0.0.1] helo=kings-cross.london.uk.eu.org ident=phil)
	by kings-cross.london.uk.eu.org with esmtp (Exim 2.05 #1)
	id 11ddYl-0005PF-00; Tue, 19 Oct 1999 19:00:31 +0100
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: Francois Desloges <fd@vipswitch.com>
Cc: linux-arm@vger.rutgers.edu
Subject: Re: 3c905B NIC + EBSA? 
In-Reply-To: Message from Francois Desloges <fd@vipswitch.com> 
   of "Tue, 19 Oct 1999 11:35:48 EDT." <99101911404801.00780@dual> 
References: <99101911404801.00780@dual> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date:   Tue, 19 Oct 1999 19:00:31 +0100
From: Philip Blundell <Philip.Blundell@pobox.com>
Message-Id: <E11ddYl-0005PF-00@kings-cross.london.uk.eu.org>
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

>I'v read somewhere in the july Mailing List Archive that people were having
>problems with 3Com 3c905B NIC on the EBSA285?
>Anybody knows the recent status of success/failure with 3c905B + EBSA285 ?

I think the cache coherency stuff was missing at the time.  It seems to be 
present now so I guess it should work, though I haven't tried it myself.

Are you having trouble?

p.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Tue Oct 19 20:43:47 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id UAA27489
	for <linux-arm-archive@lists.arm.linux.org.uk>; Tue, 19 Oct 1999 20:43:47 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 937DC13DA2; Tue, 19 Oct 1999 21:43:45 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S160130AbPJSTil>;
	Tue, 19 Oct 1999 15:38:41 -0400
Received: by vger.rutgers.edu id <S160064AbPJSTht>;
	Tue, 19 Oct 1999 15:37:49 -0400
Received: from lwaxana.cistron.net ([195.64.68.26]:30143 "EHLO
        lwaxana.cistron.net") by vger.rutgers.edu with ESMTP
	id <S160133AbPJST3V>; Tue, 19 Oct 1999 15:29:21 -0400
Received: from bvthul.cistron.nl (cs2p08.dial.cistron.nl [62.216.3.73])
	by lwaxana.cistron.net (8.9.3/8.9.3/Debian/GNU) with SMTP id VAA26723
	for <linux-arm@vger.rutgers.edu>; Tue, 19 Oct 1999 21:29:19 +0200
Date:   Tue, 19 Oct 1999 21:26:34 +0200 (BST)
From: "Beert Chris van 't Hul" <bvthul@cistron.nl>
Subject: linux arm question
To: linux-arm@vger.rutgers.edu
Message-ID: <Marcel-1.46-1019192634-3132CZ8@bvthul.cistron.nl>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
X-Organization: Organisation name, location. Telephone/Fax?
X-Mailer: ANT RISCOS Marcel [ver 1.46]
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Will EtherM be supported for ARM linux.

If not, why.

If yes but unknown when I can I assist.

Thanks,

Beert Chris

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Tue Oct 19 21:20:52 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id VAA28816
	for <linux-arm-archive@lists.arm.linux.org.uk>; Tue, 19 Oct 1999 21:20:51 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 616B913DDC; Tue, 19 Oct 1999 22:20:50 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S160127AbPJSUOs>;
	Tue, 19 Oct 1999 16:14:48 -0400
Received: by vger.rutgers.edu id <S160176AbPJSUJ4>;
	Tue, 19 Oct 1999 16:09:56 -0400
Received: from sparkle.Generation.NET ([205.205.119.4]:46216 "EHLO
        sparkle.Generation.NET") by vger.rutgers.edu with ESMTP
	id <S160064AbPJSUJW>; Tue, 19 Oct 1999 16:09:22 -0400
Received: from dual (generic253.197.205.205.IN-ADDR.ARPA [205.205.197.253] (may be forged))
	by sparkle.Generation.NET (8.9.3/8.9.3) with SMTP id QAA19580
	for <linux-arm@vger.rutgers.edu>; Tue, 19 Oct 1999 16:09:17 -0400 (EDT)
From: Francois Desloges <fd@vipswitch.com>
To: linux-arm@vger.rutgers.edu
Subject: ARM MailingList Threading
Date:   Tue, 19 Oct 1999 15:58:55 -0400
Content-Type: text/plain
MIME-Version: 1.0
Message-Id: <99101916063104.00780@dual>
Content-Transfer-Encoding: 8bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

This is quite off topic but anyway:
Does anybody know if there is an application that can take the ARM Mailing List
Archive files (readable with Pine) and generate html threads of mail like
the one we can find on typical mail archive web sites, which are so great to
navigate trough?

Thanks :-)
-- 
François Desloges
fd@vipswitch.com
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Tue Oct 19 22:12:28 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id WAA30363
	for <linux-arm-archive@lists.arm.linux.org.uk>; Tue, 19 Oct 1999 22:12:27 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 0271613F86; Tue, 19 Oct 1999 23:12:26 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S160131AbPJSUPv>;
	Tue, 19 Oct 1999 16:15:51 -0400
Received: by vger.rutgers.edu id <S160161AbPJSUOR>;
	Tue, 19 Oct 1999 16:14:17 -0400
Received: from tazenda.demon.co.uk ([158.152.220.239]:1436 "EHLO
        kings-cross.london.uk.eu.org") by vger.rutgers.edu with ESMTP
	id <S160160AbPJSUGb>; Tue, 19 Oct 1999 16:06:31 -0400
Received: from localhost
	([127.0.0.1] helo=kings-cross.london.uk.eu.org ident=phil)
	by kings-cross.london.uk.eu.org with esmtp (Exim 2.05 #1)
	id 11dfWX-0005dc-00; Tue, 19 Oct 1999 21:06:21 +0100
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: "Beert Chris van 't Hul" <bvthul@cistron.nl>
Cc: linux-arm@vger.rutgers.edu
Subject: Re: linux arm question 
In-Reply-To: Message from "Beert Chris van 't Hul" <bvthul@cistron.nl> 
   of "Tue, 19 Oct 1999 21:26:34 +0200." <Marcel-1.46-1019192634-3132CZ8@bvthul.cistron.nl> 
References: <Marcel-1.46-1019192634-3132CZ8@bvthul.cistron.nl> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date:   Tue, 19 Oct 1999 21:06:21 +0100
From: Philip Blundell <Philip.Blundell@pobox.com>
Message-Id: <E11dfWX-0005dc-00@kings-cross.london.uk.eu.org>
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

>Will EtherM be supported for ARM linux.

Yes, if and when someone contributes a driver.  This has been discussed 
before; see the mailing list archives.  Writing a driver is not all that hard; 
if you want to have a go you can always post questions here.

p.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Tue Oct 19 23:37:40 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id XAA00631
	for <linux-arm-archive@lists.arm.linux.org.uk>; Tue, 19 Oct 1999 23:37:40 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 74A7A13FB7; Wed, 20 Oct 1999 00:37:28 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S160226AbPJSW2i>;
	Tue, 19 Oct 1999 18:28:38 -0400
Received: by vger.rutgers.edu id <S160130AbPJSWHw>;
	Tue, 19 Oct 1999 18:07:52 -0400
Received: from sparkle.Generation.NET ([205.205.119.4]:50264 "EHLO
        sparkle.Generation.NET") by vger.rutgers.edu with ESMTP
	id <S160162AbPJSVlH>; Tue, 19 Oct 1999 17:41:07 -0400
Received: from dual (generic253.197.205.205.IN-ADDR.ARPA [205.205.197.253] (may be forged))
	by sparkle.Generation.NET (8.9.3/8.9.3) with SMTP id RAA16374
	for <linux-arm@vger.rutgers.edu>; Tue, 19 Oct 1999 17:41:22 -0400 (EDT)
From: Francois Desloges <fd@vipswitch.com>
To: linux-arm@vger.rutgers.edu
Subject: Fwd: Re: 3c905B NIC + EBSA?
Date:   Tue, 19 Oct 1999 17:38:08 -0400
Content-Type: text/plain
MIME-Version: 1.0
Message-Id: <99101917383606.00780@dual>
Content-Transfer-Encoding: 8bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

On Tue, 19 Oct 1999, you wrote:
> Are you having trouble?

Definitely :-) 
But I now doubt that it has anything to do with the NIC card.
I'm trying to get some feedback from the Russel's BIOS I've downloaded in Bank
#3 of my EBSA-285 with a JTAG utility from Intel (binary only :-().

Built as an 1.05 ELF bios with
TEXTADDR	= 0x410c00c0
and -DDEBUG tailed to the definiton of CFLAGS in the Makefile

The POST test from ARM, downloaded in any of the banks with the same JTAG
utility, works perfectly. And generate fabulous printf on the terminal.

With the BIOS, we don't even get at the point where we can read the first
>printf("EBSA285 Linux BIOS v"VERSION" (c) 1998-1999 Russell King
>(rmk@arm.linux.org.uk)\n\n");
in start_main.
Not even the little custom printf we've added on the first line of start_main
get outputed to terminal.

Sometimes, the bios resulting from mkaif bios.elf is smaller than bios.elf
itself, sometimes it is bigger.  Without any pods on the EBSA to plug a logic
analyser on, I wonder how we can understand what is happening...

I guess I'll have to dig even further in the BIOS code and the resulting
disassembly, oh, and use the Force, of course, though my midi-chlorian count
has been quite low recently ...

Unless somebody has an idea ? ;-)

-- 
François Desloges
fd@vipswitch.com
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Tue Oct 19 23:43:33 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id XAA00812
	for <linux-arm-archive@lists.arm.linux.org.uk>; Tue, 19 Oct 1999 23:43:33 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id D2ADA13ED4; Wed, 20 Oct 1999 00:43:31 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S160119AbPJSWbB>;
	Tue, 19 Oct 1999 18:31:01 -0400
Received: by vger.rutgers.edu id <S160139AbPJSWar>;
	Tue, 19 Oct 1999 18:30:47 -0400
Received: from m74-nsv3-trogon.tch.cableol.net ([194.168.16.224]:1362 "EHLO
        caramon.armlinux.org.uk") by vger.rutgers.edu with ESMTP
	id <S160235AbPJSWRd>; Tue, 19 Oct 1999 18:17:33 -0400
Received: from raistlin.armlinux.org.uk (linux@raistlin [192.168.0.3])
	by caramon.armlinux.org.uk (8.8.7/8.8.7) with ESMTP id XAA01469
	for <linux-arm@vger.rutgers.edu>; Tue, 19 Oct 1999 23:17:11 +0100
From: linux@arm.linux.org.uk
Received: (from linux@localhost) by raistlin.armlinux.org.uk (8.7.4/8.7.3) id XAA06875 for linux-arm@vger.rutgers.edu; Tue, 19 Oct 1999 23:16:03 +0100
Message-Id: <199910192216.XAA06875@raistlin.armlinux.org.uk>
Subject: Olde install stuff on the FTP site
To: linux-arm@vger.rutgers.edu
Date:   Tue, 19 Oct 1999 23:16:02 +0100 (BST)
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Hi All,

FTP site reorganisation
-----------------------

  For all of those of you who are trying to install the stuff from the FTP
  site, I've just finished re-organising the site.

  The location of a lot of directories and files has changed, hopefully for
  the better.

  Various packages in the old libc4 distribution have been updated, eg,
  patch 2.5, and a few others.  Also included this time are the kernel,
  kernel-headers and kernel-source packages.

  As a bonus, the second stage installer has been re-written.  This
  installer is only intended as a preliminary release, and has the
  following "features":

  1. direct FTP install is currently broken.
  2. when installing from hard drive, the packages can now reside in
     multiple directories on an ADFS disk.
  3. root password dialogue boxes are currently missing.  On a newly
     installed system, the root password will be blank.
  4. apparantly, fdisk fails for disks > 8GB, and therefore the
     installer may not work correctly.  (the installer uses fdisk).

Web site update
---------------

  The web pages have also been updated to use the new FTP site structure,
  and an installation guide for Acorn machines has been added.  The guide
  is not yet complete, but has all the pictures there!  Please note
  that although it infers that the method can be used with the A5000,
  it has not been tested.  Certainly, the A5000 will not like the RiscPC
  modules or kernel!

Problems
--------

  Could people let me know ASAP if:

  1. there are any broken links from the web site to the ftp site
     (I am aware that some links in the web site are broken at the moment;
      I am not concerned about these at the present time).
  2. the installer fails to perform for you.
   _____
  |_____| ------------------------------------------------- ---+---+-
  |   |        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' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Wed Oct 20 02:53:12 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id CAA10431
	for <linux-arm-archive@lists.arm.linux.org.uk>; Wed, 20 Oct 1999 02:53:12 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 9617313FBE; Wed, 20 Oct 1999 03:53:05 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S160133AbPJTBwb>;
	Tue, 19 Oct 1999 21:52:31 -0400
Received: by vger.rutgers.edu id <S160149AbPJTBwO>;
	Tue, 19 Oct 1999 21:52:14 -0400
Received: from [216.50.211.108] ([216.50.211.108]:4116 "EHLO
        mail.quackware.com") by vger.rutgers.edu with ESMTP
	id <S160068AbPJTBwE>; Tue, 19 Oct 1999 21:52:04 -0400
Received: from quackware.com (IDENT:jon@anyprice.com [216.50.211.108])
	by mail.quackware.com (8.9.3/8.9.3) with ESMTP id SAA00607;
	Tue, 19 Oct 1999 18:51:52 -0700
Message-ID: <380D2034.5862511C@quackware.com>
Date:   Tue, 19 Oct 1999 18:51:48 -0700
From: Jonathan Kliegman <jon@quackware.com>
Organization: Quackware
X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.12 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Philip Blundell <Philip.Blundell@pobox.com>
Cc: Francois Desloges <fd@vipswitch.com>, linux-arm@vger.rutgers.edu
Subject: Re: 3c905B NIC + EBSA?
References: <99101911404801.00780@dual> <E11ddYl-0005PF-00@kings-cross.london.uk.eu.org>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms8399105ECC1988B9D68D0CDA"
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

This is a cryptographically signed message in MIME format.

--------------ms8399105ECC1988B9D68D0CDA
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Philip Blundell wrote:
> 
> >I'v read somewhere in the july Mailing List Archive that people were having
> >problems with 3Com 3c905B NIC on the EBSA285?
> >Anybody knows the recent status of success/failure with 3c905B + EBSA285 ?
> 
> I think the cache coherency stuff was missing at the time.  It seems to be
> present now so I guess it should work, though I haven't tried it myself.
> 
> Are you having trouble?
> 
> p.
> 
> unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

We managed to get the 3c95x.c driver working at CMU a while back.  The
driver we were working with (2.2.10 release) had cache-coherence
statements in for only half the driver if I recall correctly.  We got
the driver working for the Vortex 3com chipset (I don't recall the model
number for that).  I don't believe we sent the patch back to Russel when
I was there because we were still refining/debugging it.  If the current
model isn't working I can grab the version we were using and ship that
to you. 

-Jon
--------------ms8399105ECC1988B9D68D0CDA
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIIIygYJKoZIhvcNAQcCoIIIuzCCCLcCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
BnYwggM1MIICnqADAgECAgMBXxcwDQYJKoZIhvcNAQEEBQAwgbkxCzAJBgNVBAYTAlpBMRUw
EwYDVQQIEwxXZXN0ZXJuIENhcGUxFDASBgNVBAcTC0R1cmJhbnZpbGxlMRowGAYDVQQKExFU
aGF3dGUgQ29uc3VsdGluZzEpMCcGA1UECxMgVGhhd3RlIFBGIFJTQSBJSyAxOTk4LjkuMTYg
MTc6NTUxNjA0BgNVBAMTLVRoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBSU0EgSXNzdWVyIDE5
OTguOS4xNjAeFw05OTA5MTEwMzE2MTdaFw0wMDA5MTAwMzE2MTdaMIGKMR8wHQYDVQQDExZU
aGF3dGUgRnJlZW1haWwgTWVtYmVyMSAwHgYJKoZIhvcNAQkBFhFqb25AcXVhY2t3YXJlLmNv
bTEiMCAGCSqGSIb3DQEJARYTams4cUBhbmRyZXcuY211LmVkdTEhMB8GCSqGSIb3DQEJARYS
aHVleUBxdWFja3dhcmUuY29tMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCaNU1M9alS
1OeXmlLwchR08PElNEhVnyx1NaifsEqPaSpi2jTQNJtGDjVFxY9dUss2n7MMkvQeapA4+qP+
tNcA9bjoRbUzNHv1NubI2IqNexhSGCnkw2rKpwg/K0fvmOerW9OsUk1k6xj5bVcgaQSahBAI
ERwnqNOb0iFGVLqqNwIDAQABo3gwdjBFBgNVHREEPjA8gRFqb25AcXVhY2t3YXJlLmNvbYET
ams4cUBhbmRyZXcuY211LmVkdYESaHVleUBxdWFja3dhcmUuY29tMAwGA1UdEwEB/wQCMAAw
HwYDVR0jBBgwFoAU/j5gnGuMD7DYM8bKxh5YsHE4teAwDQYJKoZIhvcNAQEEBQADgYEAWbao
tABBnGq4TD+Xo+2HK/IDSLi1RpQ3nqwvzkx9Us9ToAxfQmzUudICzR/ZzK9U/4fjPM4QSQLN
qIDNvg1ocZg5GLtgXyYNPmmpaXIdq9DbSa9kKpsan6uv7vKhVXj+tYH1T9iiugc4OL0oMXuI
Zm+xBsql505m8PuoKjH1i/8wggM5MIICoqADAgECAgEKMA0GCSqGSIb3DQEBBAUAMIHRMQsw
CQYDVQQGEwJaQTEVMBMGA1UECBMMV2VzdGVybiBDYXBlMRIwEAYDVQQHEwlDYXBlIFRvd24x
GjAYBgNVBAoTEVRoYXd0ZSBDb25zdWx0aW5nMSgwJgYDVQQLEx9DZXJ0aWZpY2F0aW9uIFNl
cnZpY2VzIERpdmlzaW9uMSQwIgYDVQQDExtUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgQ0Ex
KzApBgkqhkiG9w0BCQEWHHBlcnNvbmFsLWZyZWVtYWlsQHRoYXd0ZS5jb20wHhcNOTgwOTE2
MTc1NTM0WhcNMDAwOTE1MTc1NTM0WjCBuTELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rl
cm4gQ2FwZTEUMBIGA1UEBxMLRHVyYmFudmlsbGUxGjAYBgNVBAoTEVRoYXd0ZSBDb25zdWx0
aW5nMSkwJwYDVQQLEyBUaGF3dGUgUEYgUlNBIElLIDE5OTguOS4xNiAxNzo1NTE2MDQGA1UE
AxMtVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIFJTQSBJc3N1ZXIgMTk5OC45LjE2MIGfMA0G
CSqGSIb3DQEBAQUAA4GNADCBiQKBgQDEpeXU1NBfCALuByF9JL+ra44e6yAHAhWEa4/QkyQf
G53uaLK5LE/pk2cXEBceoflDQSO5MKp2l7vz5/2BwLUxi/amUCZU8pUo6xmkHpcesOK4m8EE
mjLQPAlsT+Q1T/B2vwATA09FCGDz/LTQkAGKEsmcun9S6iqTNTY8POQ1LwIDAQABozcwNTAS
BgNVHRMBAf8ECDAGAQH/AgEAMB8GA1UdIwQYMBaAFHJJwnM0xlX0C3ZygX539IfnxrIOMA0G
CSqGSIb3DQEBBAUAA4GBACzHgh8BQz4Hj+5pXKlkgvjAlq2TK8ubUNdAmoHCuqZ2nTyVQNxV
weFVgnmrCimm1QzhVyg+j/m71d8Nk1iqWy2LjzPk3VgVNXZyFSm9QvRakgt3X50n25otThuC
Bo7SjVa7ld7bDGUF3pWeAt1TF76+/GvDGiJ6FCthvcKfXnpaMYICHDCCAhgCAQEwgcEwgbkx
CzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxFDASBgNVBAcTC0R1cmJhbnZp
bGxlMRowGAYDVQQKExFUaGF3dGUgQ29uc3VsdGluZzEpMCcGA1UECxMgVGhhd3RlIFBGIFJT
QSBJSyAxOTk4LjkuMTYgMTc6NTUxNjA0BgNVBAMTLVRoYXd0ZSBQZXJzb25hbCBGcmVlbWFp
bCBSU0EgSXNzdWVyIDE5OTguOS4xNgIDAV8XMAkGBSsOAwIaBQCggbEwGAYJKoZIhvcNAQkD
MQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNOTkxMDIwMDE1MTUwWjAjBgkqhkiG9w0B
CQQxFgQUSDJUfiXZLsb1NJb5Az3l8hwSBfAwUgYJKoZIhvcNAQkPMUUwQzAKBggqhkiG9w0D
BzAOBggqhkiG9w0DAgICAIAwBwYFKw4DAgcwDQYIKoZIhvcNAwICAUAwDQYIKoZIhvcNAwIC
ASgwDQYJKoZIhvcNAQEBBQAEgYCQOwjoZzRodVhlJ7Vpb911PljijEeCaX/p5deKB4y1+CFx
j6fCcF1ohid89bvPO+s7BmGm50kZJMtFW/YQD7mTNV9b9uHrYDrGY3mJvEnOH9j1k2cEsCrZ
Aui4rAQ4rfKRWe6pDnop6X67M4bWj0cSPKeF54nnrO/4k3uMbdDogg==
--------------ms8399105ECC1988B9D68D0CDA--

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Wed Oct 20 03:52:04 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id DAA12029
	for <linux-arm-archive@lists.arm.linux.org.uk>; Wed, 20 Oct 1999 03:52:04 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id E04C513E1F; Wed, 20 Oct 1999 04:51:42 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S160031AbPJTCu6>;
	Tue, 19 Oct 1999 22:50:58 -0400
Received: by vger.rutgers.edu id <S160108AbPJTCuq>;
	Tue, 19 Oct 1999 22:50:46 -0400
Received: from PO9.ANDREW.CMU.EDU ([128.2.10.109]:39654 "EHLO
        po9.andrew.cmu.edu") by vger.rutgers.edu with ESMTP
	id <S160021AbPJTCuW>; Tue, 19 Oct 1999 22:50:22 -0400
Received: (from postman@localhost)
	by po9.andrew.cmu.edu (8.9.3/8.9.3) id WAA15595;
	Tue, 19 Oct 1999 22:50:16 -0400 (EDT)
Received: via switchmail; Tue, 19 Oct 1999 22:50:16 -0400 (EDT)
Received: from unix10.andrew.cmu.edu via qmail
          ID </afs/andrew.cmu.edu/service/mailqs/q006/QF.ws3GqqC00UwC01Uog0>;
          Tue, 19 Oct 1999 22:49:26 -0400 (EDT)
Received: from unix10.andrew.cmu.edu via qmail
          ID </afs/andrew.cmu.edu/usr23/dsf/.Outgoing/QF.os3Gqpe00UwC0J6UI0>;
          Tue, 19 Oct 1999 22:49:25 -0400 (EDT)
Received: from mms.4.60.Jun.27.1996.03.02.53.sun4.51.EzMail.2.0.CUILIB.3.45.SNAP.NOT.LINKED.unix10.andrew.cmu.edu.sun4m.54
          via MS.5.6.unix10.andrew.cmu.edu.sun4_51;
          Tue, 19 Oct 1999 22:49:25 -0400 (EDT)
Message-ID: <Is3Gqpe00UwC0J6UA0@andrew.cmu.edu>
Date:   Tue, 19 Oct 1999 22:49:25 -0400 (EDT)
From: David Sean Friedman <dsf+@andrew.cmu.edu>
To: Philip Blundell <Philip.Blundell@pobox.com>,
        Jonathan Kliegman <jon@quackware.com>
Subject: Re: 3c905B NIC + EBSA?
Cc: Francois Desloges <fd@vipswitch.com>, linux-arm@vger.rutgers.edu
In-Reply-To: <380D2034.5862511C@quackware.com>
References: <99101911404801.00780@dual> <E11ddYl-0005PF-00@kings-cross.london.uk.eu.org>
	<380D2034.5862511C@quackware.com>
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Excerpts from arm-linux: 19-Oct-99 Re: 3c905B NIC + EBSA? by Jonathan
Kliegman@quackw 
> We managed to get the 3c95x.c driver working at CMU a while back.  The
> driver we were working with (2.2.10 release) had cache-coherence
> statements in for only half the driver if I recall correctly.  We got
> the driver working for the Vortex 3com chipset (I don't recall the model
> number for that).  I don't believe we sent the patch back to Russel when
> I was there because we were still refining/debugging it.  If the current
> model isn't working I can grab the version we were using and ship that
> to you. 
The driver we have here is mostly functional, but we noticed that it was
very prone to causing random kernel lockups, much more so than the tulip
driver. 

I also have ported the new driver from 3com (not Donald Becker) to ARM.
The driver has very good performance on receiving data, but transmitting
has problems. I've stopped working on it after I found a few bugs,
because 3com still considers it beta quality.

All of the work on these drivers was done on the 3c905B.

We also did some work on the eepro100 driver a while ago. It worked
pretty well, but that driver had "transmit timeout" problems on both ARM
and x86 platforms. There are rumors that the newest eepro100 driver
fixes this, but I haven't tested it.

Our group doesn't expect to do any more work on these drivers, so if
anyone is interested, let me know.


David Friedman 
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Wed Oct 20 10:43:58 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id KAA29760
	for <linux-arm-archive@lists.arm.linux.org.uk>; Wed, 20 Oct 1999 10:43:57 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id B4B9C13F64; Wed, 20 Oct 1999 11:43:55 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S160259AbPJTJng>;
	Wed, 20 Oct 1999 05:43:36 -0400
Received: by vger.rutgers.edu id <S160240AbPJTJnR>;
	Wed, 20 Oct 1999 05:43:17 -0400
Received: from duteinh.et.tudelft.nl ([130.161.42.1]:2622 "HELO
        duteinh.et.tudelft.nl") by vger.rutgers.edu with SMTP
	id <S160216AbPJTJnC>; Wed, 20 Oct 1999 05:43:02 -0400
Received: from dutein71 (dutein71.et.tudelft.nl) by duteinh.et.tudelft.nl (4.1/BB-2.0)
	id AA12440; Wed, 20 Oct 99 11:42:53 +0200
Date:   Wed, 20 Oct 99 11:42:53 +0200
Message-Id: <9910200942.AA12440@duteinh.et.tudelft.nl>
From: Erik Mouw <erik@it.et.tudelft.nl>
To: fd@vipswitch.com
Cc: linux-arm@vger.rutgers.edu
Reply-To: J.A.K.Mouw@its.tudelft.nl
Subject: Re: ARM MailingList Threading
In-Reply-To: <99101916063104.00780@dual>
Organization: Eric conspiracy secret labs
X-Face: "!Z|1XjFg!3Iw)BwM^M\k)J5KHiPddz}#/Zw%?$&Q!xqob"OA|})3_@&BTTiQERo?/^g[Z<9P4R8:5C:aqq.cw!hotLc=+u-"+1rq@9$V^8PbOUlodyi_sejt+D`iqkLpx$>.aXl%vnfPIt"LK|/%>94_Zrm8jy?`_[RKt'TuoxUxfk(gMhY(n|DBBl~c$dhO>G%6}R4+DGX3|idBm4oU&UM/XUP4I9aoN{]`ax%B?rgD(I3OJ<62Y6L
X-Mailer: XCmail 0.99.6 - with PGP support, PGP engine version 0.5
X-Mailerorigin: http://www.fsai.fh-trier.de/~schmitzj/Xclasses/XCmail/
X-Eric-Conspiracy: There is no conspiracy!
X-Loop: erik@it.et.tudelft.nl
Mime-Version: 1.0
Content-Type: 	text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

On Tue, 19 Oct 1999 15:58:55 -0400, Francois Desloges wrote:
> This is quite off topic but anyway:
> Does anybody know if there is an application that can take the ARM Mailing List
> Archive files (readable with Pine) and generate html threads of mail like
> the one we can find on typical mail archive web sites, which are so great to
> navigate trough?

Try MHonArc: http://www.oac.uci.edu/indiv/ehood/mhonarc.html


Erik

-- 
J.A.K. (Erik) Mouw, Information and Communication Theory Group, Department
of Electrical Engineering, Faculty of Information Technology and Systems,
Delft University of Technology, PO BOX 5031,  2600 GA Delft, The Netherlands
Phone: +31-15-2785859  Fax: +31-15-2781843  Email J.A.K.Mouw@its.tudelft.nl
WWW: http://www-ict.its.tudelft.nl/~erik/


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Wed Oct 20 15:43:18 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id PAA13890
	for <linux-arm-archive@lists.arm.linux.org.uk>; Wed, 20 Oct 1999 15:43:18 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 6679A14253; Wed, 20 Oct 1999 16:43:16 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S160376AbPJTOi1>;
	Wed, 20 Oct 1999 10:38:27 -0400
Received: by vger.rutgers.edu id <S160456AbPJTOgj>;
	Wed, 20 Oct 1999 10:36:39 -0400
Received: from m9-nsv1-trogon.tch.cableol.net ([194.168.16.9]:1829 "EHLO
        caramon.armlinux.org.uk") by vger.rutgers.edu with ESMTP
	id <S160376AbPJTOUD>; Wed, 20 Oct 1999 10:20:03 -0400
Received: from raistlin.armlinux.org.uk (linux@raistlin [192.168.0.3])
	by caramon.armlinux.org.uk (8.8.7/8.8.7) with ESMTP id PAA04354;
	Wed, 20 Oct 1999 15:19:54 +0100
From: linux@arm.linux.org.uk
Received: (from linux@localhost) by raistlin.armlinux.org.uk (8.7.4/8.7.3) id PAA11636; Wed, 20 Oct 1999 15:18:44 +0100
Message-Id: <199910201418.PAA11636@raistlin.armlinux.org.uk>
Subject: Testing - please ignore
To: chris@fluff.org
Date:   Wed, 20 Oct 1999 15:18:43 +0100 (BST)
Cc: linux-arm@vger.rutgers.edu
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

This mail is to help chris@fluff.org track down some oddities in the
configuration of his mail system.
   _____
  |_____| ------------------------------------------------- ---+---+-
  |   |        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' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Wed Oct 20 18:38:20 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id SAA31004
	for <linux-arm-archive@lists.arm.linux.org.uk>; Wed, 20 Oct 1999 18:38:19 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 3468513DA4; Wed, 20 Oct 1999 19:38:18 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S160623AbPJTRf1>;
	Wed, 20 Oct 1999 13:35:27 -0400
Received: by vger.rutgers.edu id <S160594AbPJTRTB>;
	Wed, 20 Oct 1999 13:19:01 -0400
Received: from EVELAKE.PDL.CS.CMU.EDU ([128.2.189.75]:1602 "HELO
        evelake.pdl.cs.cmu.edu") by vger.rutgers.edu with SMTP
	id <S160628AbPJTRHh>; Wed, 20 Oct 1999 13:07:37 -0400
To: linux-arm@vger.rutgers.edu
Subject: PDC20262 Controller with an EBSA285?
Mime-Version: 1.0 (generated by tm-edit 7.108)
Content-Type: text/plain; charset=US-ASCII
From: Nat Lanza <magus@cs.cmu.edu>
Date:   20 Oct 1999 13:07:14 -0400
Message-ID: <uoc4sfm9d19.fsf@evelake.pdl.cs.cmu.edu>
Lines:  31
X-Mailer: Gnus v5.6.31/XEmacs 20.4 - "Emerald"
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

I have some development boards based on the EBSA285 with integrated
Promise 20262 IDE controllers and 13GB Quantum Fireball CR
disks. Currently, they're running a slightly patched version of
2.2.7-rmk4, and the disk performance is horrible -- peaks at a bit
over 6MB/sec while chewing up all of the CPU. Since I want to use them 
as servers, this isn't really good enough.

What's my best option for getting this to work? I've tried running
2.2.12-rmk1, but I get weird scheduler crashes and stack corruption
right after the kernel starts up init. I've also tried 2.3.19-rmk1,
but it completely fails to boot -- no console messages at all.

I've had to apply some patches to 2.2.12 to get the machine to boot as 
far as it does; when I separate them out I'll either post them or make 
them web/ftp available.

Oh -- I'm building my kernels with gcc and binutils from the
gcc-2.95.1-1nw5 and binutils-2.9.1.0.25-1nw2 RPMs from
ftp.netwinder.org. Is this fine, or should I be using something else?
I'm fairly new to Linux on the ARM platform, so I'm still not entirely 
sure what the best way to go about this is.

Any suggestions?


--nat

-- 
nat lanza --------------------- research programmer, parallel data lab, cmu scs
magus@cs.cmu.edu -------------------------------- http://www.cs.cmu.edu/~magus/
there are no whole truths; all truths are half-truths -- alfred north whitehead
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Wed Oct 20 19:09:04 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id TAA00542
	for <linux-arm-archive@lists.arm.linux.org.uk>; Wed, 20 Oct 1999 19:09:03 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 4544A13ED4; Wed, 20 Oct 1999 20:09:02 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S160428AbPJTR7V>;
	Wed, 20 Oct 1999 13:59:21 -0400
Received: by vger.rutgers.edu id <S160380AbPJTRvM>;
	Wed, 20 Oct 1999 13:51:12 -0400
Received: from mailhost.mipsys.com ([62.161.177.33]:8001 "EHLO [62.161.177.33]")
	by vger.rutgers.edu with ESMTP id <S160548AbPJTRoc>;
	Wed, 20 Oct 1999 13:44:32 -0400
Received: from [192.168.1.10] by [192.168.1.2]
     with SMTP (QuickMail Pro Server for Mac 2.0); 20 OCT 99 19:52:14 UT
In-Reply-To: <99101917383606.00780@dual>
X-Mailer: CTM PowerMail 2.4v7 <http://www.ctmdev.com>
Date:   Wed, 20 Oct 1999 19:43:58 +0200
To: Francois Desloges <fd@vipswitch.com>, linux-arm@vger.rutgers.edu
From: Benjamin Herrenschmidt <benh@mipsys.com>
Subject: Re: Fwd: Re: 3c905B NIC + EBSA?
Message-Id: <19991020194358.027991@mailhost.mipsys.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

On Tue, Oct 19, 1999, Francois Desloges <fd@vipswitch.com> wrote:

>Definitely :-) 
>But I now doubt that it has anything to do with the NIC card.
>I'm trying to get some feedback from the Russel's BIOS I've downloaded
in Bank
>#3 of my EBSA-285 with a JTAG utility from Intel (binary only :-().
>
>Built as an 1.05 ELF bios with
>TEXTADDR	= 0x410c00c0
>and -DDEBUG tailed to the definiton of CFLAGS in the Makefile

I use TEXTADDR	= 0x41000080

(the AIF header is 128 bytes)

>The POST test from ARM, downloaded in any of the banks with the same JTAG
>utility, works perfectly. And generate fabulous printf on the terminal.
>
>With the BIOS, we don't even get at the point where we can read the first
>>printf("EBSA285 Linux BIOS v"VERSION" (c) 1998-1999 Russell King
>>(rmk@arm.linux.org.uk)\n\n");
>in start_main.
>Not even the little custom printf we've added on the first line of start_main
>get outputed to terminal.
>
>Sometimes, the bios resulting from mkaif bios.elf is smaller than bios.elf
>itself, sometimes it is bigger.  Without any pods on the EBSA to plug a logic
>analyser on, I wonder how we can understand what is happening...

It's possible that there is a bug in the ELF version of mkaif since I
made it ;)
I'll try to upload the version I use here (I beleive it's the same as the
one in Russel's 1.05 version, but I'm not sure I didn't change anything
so I'll double check, ping me if you don't hear from me by Friday).

One thing you can do for debugging is to add some serial output in the
assembly entry code (crt0.S). I had to make some changes to the RAM
detection code for it to work on my board, but I can't tell now if the
failure of Russel code was due to a change in the 285, or tue a HW bug we
had with RAM which was fixed in our latest prototype.

Anyway, here's my version of the code (the beginning of crt0.S, I didn't
copy the whole file, all the rest didn't change). Notice the debugging
serial output (yes, I know, I could have used strings ;)

#include "bios/linkage.h"
#include "bios/config.h"

#define CSR_BASE	0x42000000
#define SDRAM_TIMING	0x10c
#define SDRAM_ADDR_SZ0	0x110
#define SDRAM_ADDR_SZ1	0x114
#define SDRAM_ADDR_SZ2	0x118
#define SDRAM_ADDR_SZ3	0x11c

#define SDRAM_BASE	0x40000000
#define SDRAM_NRARRAYS	4
#define SDRAM_ARRAYOFF	0x00004000
#define FLUSH_BASE	SDRAM_BASE

#define XBUS_CYCLE	0x148
#define XBUS_STROBE	0x14C
#define SA_CONTROL	0x13C

#define UARTDR		0x160

#define BAUD_RATE_DIVISOR 	19/*40*/

#define MAX_AREA_SIZE	32768

#define SDRAM_BURST_LEN		2	/* Burst size is 4 */
#define SDRAM_BURST_TYPE	0	/* Linear burst */
#define SDRAM_CAS_LAT		2	/* CAS latency (2 or 3 supported) */
#define SDRAM_RASTOCAS_LAT	2	/* RAS-to-CAS latency (2 or 3 supported) */
#define SDRAM_MODE			((SDRAM_BURST_LEN<<2)|(SDRAM_BURST_TYPE<<5)| \
							 (SDRAM_CAS_LAT<<6))


/* Init values for XBus */
#if 0
#define INIT_XBUS_CYCLE		0x000016DB /* 0001-011 0-11 01-1 011 */
#define INIT_XBUS_STROBE	0xfcfcfcfc /* fc: __-- (1100) */	
#else
#define INIT_XBUS_CYCLE		0x00003FFF /* 0011-111 1-11 11-1 111 */
#define INIT_XBUS_STROBE	0xe3e3e3e3 /* fc: --___-- (1110 0011) */
#endif
#define XCS_2				0x40000000
#define XCS_1				0x20000000
#define XCS_0				0x10000000
#define XBUS_INIT			(XCS_2 | XCS_1 | XCS_0)
#define SA_CTL_INIT			(XBUS_INIT | ROM_SETUP)
#define ROM_TIMING			0x0fff0000
#define ROM_SETUP			0x00000000 /* Everything 16 cycles */

#define XBUS_0_BASE			0x40010000
#define XBUS_1_BASE			0x40011000
#define XBUS_2_BASE			0x40012000


	.text

@ Entry
	.globl	_entry
_entry:
	bic	r11, lr, #3
	mrs	r0, cpsr
	bic	r0, r0, #0x1f
	orr	r0, r0, #0xd3
	msr	cpsr, r0
	ldr	sp, [r11, #8]

/*
 * switch the ROM memory map
 * so that we can access the SDRAM
 */

	ldr	pc, 1f
1:	.word	switch
switch:

	mov	r0, #0
	mcr	p15, 0, r0, c15, c1, 2	@ enable clock switching	
	mov	r0, #0
	mcr	p15, 0, r0, c7, c7, 0	@ flush all caches

	mrc	p15, 0, r0, c1, c0	@ Control reg
	bic	r0, r0, #0x0d		@ D-cache, wback & MMU off
	bic	r0, r0, #1 << 12	@ I-cache off
	mcr	p15, 0, r0, c1, c0	@ Control reg

#ifdef CONFIG_INIT_XBUS
	/* Init X-Bus */
	mov	r0, #CSR_BASE
	ldr	r1, =SA_CTL_INIT
	str	r1, [r0, #SA_CONTROL]

	ldr	r1, =INIT_XBUS_CYCLE
	str	r1, [r0, #XBUS_CYCLE]

	ldr	r1, =INIT_XBUS_STROBE
	str	r1, [r0, #XBUS_STROBE]
	
	/* Set leds to OFF */
	ldr	r0, =XBUS_1_BASE
	mov	r1, #0xff
	str	r1, [r0]
#endif

	/* Init serial */
	bl	ser_init

	mov	r0, #'H'
	bl	ser_printc
	mov	r0, #'E'
	bl	ser_printc
	mov	r0, #'L'
	bl	ser_printc
	mov	r0, #'L'
	bl	ser_printc
	mov	r0, #'O'
	bl	ser_printc
	mov	r0, #10
	bl	ser_printc

/*
 * Initialise SDRAM.  This copes with the SDRAM in any state -
 * it does a complete initialisation and allocation of all
 * banks.
 *
 * Turn off SDRAM refresh
 */
	mov	r0, #0
	mov	ip, #CSR_BASE
	str	r0, [ip, #SDRAM_TIMING]
/* 
 * Wait for any refresh cycles to complete
 */
	mov	r0, #64
1:	subs	r0, r0, #1
	bgt	1b
/*
 * All-banks precharge SDRAM arrays
 */
	mov	r0, #SDRAM_BASE
	mov	r1, #SDRAM_NRARRAYS
1:	ldr	r2, [r0]
	ldr	r2, [r0]
	add	r0, r0, #SDRAM_ARRAYOFF
	subs	r1, r1, #1
	bgt	1b
/*
 * Write mode registers
 */
	mov	r0, #SDRAM_BASE
	orr	r0, r0, #SDRAM_MODE/*#0x84*//*#0x88*/		@ Tcas
	mov	r1, #SDRAM_NRARRAYS
1:	str	r0, [r0]
	add	r0, r0, #SDRAM_ARRAYOFF
	subs	r1, r1, #1
	bgt	1b
/*
 * Turn on minimum SDRAM refresh
 */
	mov	r0, #0x00010000
	orr	r0, r0, #0x00000b00
	orr	r0, r0, #(0x00000005|(SDRAM_CAS_LAT<<6)|(SDRAM_RASTOCAS_LAT<<4))
	str	r0, [ip, #SDRAM_TIMING]
/*
 * Set size to maximum
 */
	mov	r1, #SDRAM_NRARRAYS
	add	r2, ip, #SDRAM_ADDR_SZ0
	mov	r0, #0x2f	/* We begin with mode 2 ! */
1:	str	r0, [r2], #4
	add	r0, r0, #64*1024*1024
	subs	r1, r1, #1
	bgt	1b
/*
 * Wait for banks to be refreshed
 */
	mov	r0, #10
	mov	r1, #0
1:	subs	r1, r1, #2
	bgt	1b
	subs	r0, r0, #1
	bgt	1b
/*
 * Set SDRAM refresh to normal
 */
	mov	r0, #0x001a0000
	orr	r0, r0, #0x00000b00
	orr	r0, r0, #0x000000a5
	str	r0, [ip, #SDRAM_TIMING]

	mov	r4, #0x00000000
1:	mov	r5, #0
/*
 * Detect RAM multiplexer settings
 */
	mov	r0, #10
	bl	ser_printc
	mov	r0, #'R'
	bl	ser_printc
	mov	r0, #'4'
	bl	ser_printc
	mov	r0, #':'
	bl	ser_printc
	mov	r0, r4
	bl	ser_printhex

	mov	r0, r4			@ check for presence
	add	r1, r4, #64
	bl	testram
	bne	4f

	mov	r0, #'P'
	bl	ser_printc

	/* Check for mode 0 if aliased on 21 */
	mov	r0, r4			@ check bit 21
	orr	r1, r0, #1 << 21
	bl	testram
	orreq	r5, r5, #8
	moveq r0, #'N'
	movne r0, #'A'
	bl ser_printc

	/* Check for mode 2 if !aliased on bit 23 */
	mov	r0, r4			@ check bit 23
	orr	r1, r0, #1 << 23
	bl	testram
	orrne	r5, r5, #4
	moveq r0, #'N'
	movne r0, #'A'
	bl ser_printc

	/* Check for mode 4 if !aliased on bit 22 */
	mov	r0, r4			@ check bit 22
	orr	r1, r0, #1 << 22
	bl	testram
	orrne	r5, r5, #2
	moveq r0, #'N'
	movne r0, #'A'
	bl ser_printc

	/* Now catch most mode 1 via bit 24 */
	mov	r0, r4			@ check bit 24
	orr	r1, r0, #1 << 24
	bl	testram
	orrne	r5, r5, #1
	moveq r0, #'N'
	movne r0, #'A'
	bl ser_printc
	
	adr	r1, ram_modes		@ convert test -> mux
	ldrb	r6, [r1, r5]

	mov	r0, #'M'
	bl	ser_printc
	mov	r0, r6
	bl	ser_printhex

	orr	r6, r6, r4

	add	r0, ip, #SDRAM_ADDR_SZ0	@ set mux correctly
	orr	r5, r6, #7		@ leave size at 64MB
	str	r5, [r0, r4, lsr #24]
/*
 * Detect RAM array size
 */
	mov	r5, #1 << 20
	mov	r7, #0

2:	add	r0, r4, r5
	add	r1, r4, r5, lsr #1
	bl	testram
	bne	3f
	mov	r5, r5, lsl #1
	cmp	r7, #7
	addne	r7, r7, #1
	bne	2b

3:	orr	r5, r6, r7

	mov	r0, #'S'
	bl	ser_printc
	mov	r0, r7
	bl	ser_printhex

4:	add	r0, ip, #SDRAM_ADDR_SZ0
	str	r5, [r0, r4, lsr #24]	@ set array size
	add	r4, r4, #0x04000000
	teq	r4, #0x10000000
	bne	1b

	mov	r0, #10
	bl	ser_printc
/*
 * Allocate RAM addresses
 */
	mov	r3, #7			@ start at largest size
	mov	r4, #0x00000000
1:	mov	r5, #SDRAM_NRARRAYS
	add	r2, ip, #SDRAM_ADDR_SZ0
2:	ldr	r0, [r2], #4		@ Read SDRAM size & addr
	and	r1, r0, #7
	teq	r1, r3
	bne	3f

	and	r0, r0, #127		@ Preserve size etc
	orr	r0, r0, r4		@ Add base address
	str	r0, [r2, #-4]		@ Write SDRAM size & addr

	mov	r0, #524288
	add	r4, r4, r0, lsl r1	@ Next address

3:	subs	r5, r5, #1
	bgt	2b
	subs	r3, r3, #1
	bgt	1b

	/* Print out detected amount of RAM */
	mov	r0, #'R'
	bl	ser_printc
	mov	r0, #'A'
	bl	ser_printc
	mov	r0, #'M'
	bl	ser_printc
	mov	r0, #':'
	bl	ser_printc
	mov	r0, r4
	bl	ser_printhex
	mov	r0, #10
	bl	ser_printc
	
	mrc	p15, 0, r0, c1, c0	@ Control reg
	bic	r0, r0, #0x0d		@ D-cache, wback & MMU off
	orr	r0, r0, #1 << 12	@ I-cache on
	mcr	p15, 0, r0, c1, c0	@ Control reg

	mov	r0, #'C'
	bl	ser_printc

	/* At this point, sp contains the size of the datas. Those
	   are copied to RAM address 0x1000 */
	mov	r1, #0x1000
	ldr	r2, =SYMBOL_NAME(_etext)
1:	ldr	r0, [r2], #4
	str	r0, [r1], #4
	subs	sp, sp, #4
	bgt	1b

	mov	r0, #'D'
	bl	ser_printc

	/* BSS is initialized */
	mov	r0, #0
	ldr	r1, =SYMBOL_NAME(_bss_start)
	ldr	r2, =SYMBOL_NAME(_end)
1:	str	r0, [r1], #4
	cmp	r1, r2
	blt	1b
	
	mov	r0, #'B'
	bl	ser_printc

	/* Set stack to top of RAM -1Mb */
	sub	sp, r4, #1048576

	bl	vec_init

	ldr	r0, =SYMBOL_NAME(ram_size)
	str	r4, [r0]

	mov	r0, #'J'
	bl	ser_printc

	bl	SYMBOL_NAME(start_main)
l:	b	l

ram_modes:
	.byte	0x00
	.byte	0x00
	.byte	0x00
	.byte	0x00
	.byte	0x00
	.byte	0x00
	.byte	0x00
	.byte	0x00
	.byte	0x20
	.byte	0x20
	.byte	0x20
	.byte	0x20
	.byte	0x40
	.byte	0x40
	.byte	0x10
	.byte	0x30

	.align	4
	


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Wed Oct 20 19:09:43 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id TAA00555
	for <linux-arm-archive@lists.arm.linux.org.uk>; Wed, 20 Oct 1999 19:09:43 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 0081B13DA7; Wed, 20 Oct 1999 20:09:41 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S160608AbPJTR6m>;
	Wed, 20 Oct 1999 13:58:42 -0400
Received: by vger.rutgers.edu id <S160626AbPJTRuc>;
	Wed, 20 Oct 1999 13:50:32 -0400
Received: from sparkle.Generation.NET ([205.205.119.4]:54604 "EHLO
        sparkle.Generation.NET") by vger.rutgers.edu with ESMTP
	id <S160357AbPJTRgu>; Wed, 20 Oct 1999 13:36:50 -0400
Received: from dual (generic253.197.205.205.IN-ADDR.ARPA [205.205.197.253] (may be forged))
	by sparkle.Generation.NET (8.9.3/8.9.3) with SMTP id NAA19098
	for <linux-arm@vger.rutgers.edu>; Wed, 20 Oct 1999 13:37:04 -0400 (EDT)
From: Francois Desloges <fd@vipswitch.com>
To: linux-arm@vger.rutgers.edu
Subject: Fwd: Re: How do one uses the bios?
Date:   Wed, 20 Oct 1999 13:33:56 -0400
Content-Type: text/plain
MIME-Version: 1.0
Message-Id: <99102013342009.00780@dual>
Content-Transfer-Encoding: 8bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

On Wed, 13 Oct 1999, you wrote:
> I left angel in image 0 in the flash, and let it load the bios from another flash
> image pointed to by the selector switch (that's why the bios is in AIF format).
> It was necessary to link the bios at a address different the one specified in the
> readme file  (TEXTADDR = 0x410000C0 + bank * 0x00040000 rather than 0x410000A0).
> 
> Also note that if you are using a pci-only backplane, the ISA initialization code
> will hang the bios. I tried boot the kernel via the network, but the bios hangs
> during opening of the network card. Haven't had time to play with it since.
> 
> Regards,
> Chris

Did you use FMU to upload the bios?

Is that why you need that extra 0x40 bytes at the beginning, for the FMU
header?

This header is used by the Angel-PBL to load/run the content of the bank, right?

What about shortcutting the PBL and burning th BIOS in Bank 0, without the FMU
header and with TEXTADDR = 0x410000a0?

Wouldn't the BIOS own crt0.S initialization be enough to replace the PBL?

There was a big discussion in the Mail Archive around February/Mars 1999 about 
the different intialization role of the BIOS and the kernel respectively. I
never found the definitive conclusions.
What initialisation should be under the control of BIOS and what should be
under kernel's control?

-- 
François Desloges
fd@vipswitch.com
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Wed Oct 20 19:29:28 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id TAA01702
	for <linux-arm-archive@lists.arm.linux.org.uk>; Wed, 20 Oct 1999 19:29:28 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 0F9CE13F02; Wed, 20 Oct 1999 20:27:36 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S160574AbPJTS0i>;
	Wed, 20 Oct 1999 14:26:38 -0400
Received: by vger.rutgers.edu id <S160330AbPJTSUO>;
	Wed, 20 Oct 1999 14:20:14 -0400
Received: from mailhost.mipsys.com ([62.161.177.33]:8010 "EHLO [62.161.177.33]")
	by vger.rutgers.edu with ESMTP id <S160538AbPJTSTA>;
	Wed, 20 Oct 1999 14:19:00 -0400
Received: from [192.168.1.10] by [192.168.1.2]
     with SMTP (QuickMail Pro Server for Mac 2.0); 20 OCT 99 20:26:56 UT
In-Reply-To: <19991020194358.027991>
X-Mailer: CTM PowerMail 2.4v7 <http://www.ctmdev.com>
Date:   Wed, 20 Oct 1999 20:18:44 +0200
To: Francois Desloges <fd@vipswitch.com>, linux-arm@vger.rutgers.edu
From: Benjamin Herrenschmidt <benh@mipsys.com>
Subject: Re: Fwd: Re: 3c905B NIC + EBSA?
Message-Id: <19991020201844.028219@mailhost.mipsys.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

On Wed, Oct 20, 1999, Benjamin Herrenschmidt <benh@mipsys.com> wrote:

>I use TEXTADDR	= 0x41000080
>
>(the AIF header is 128 bytes)

Correcting myself: You need 0x41000080 when flashing directly without the
FMU header (JTAG). When using FMU, 0x410000C0 is the correct value.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Wed Oct 20 19:29:31 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id TAA01708
	for <linux-arm-archive@lists.arm.linux.org.uk>; Wed, 20 Oct 1999 19:29:31 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 6125F1400D; Wed, 20 Oct 1999 20:28:15 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S160424AbPJTS1F>;
	Wed, 20 Oct 1999 14:27:05 -0400
Received: by vger.rutgers.edu id <S160244AbPJTS0t>;
	Wed, 20 Oct 1999 14:26:49 -0400
Received: from mailhost.mipsys.com ([62.161.177.33]:8001 "EHLO [62.161.177.33]")
	by vger.rutgers.edu with ESMTP id <S160559AbPJTSXB>;
	Wed, 20 Oct 1999 14:23:01 -0400
Received: from [192.168.1.10] by [192.168.1.2]
     with SMTP (QuickMail Pro Server for Mac 2.0); 20 OCT 99 20:30:54 UT
In-Reply-To: <99102013342009.00780@dual>
X-Mailer: CTM PowerMail 2.4v7 <http://www.ctmdev.com>
Date:   Wed, 20 Oct 1999 20:22:40 +0200
To: Francois Desloges <fd@vipswitch.com>, linux-arm@vger.rutgers.edu
From: Benjamin Herrenschmidt <benh@mipsys.com>
Subject: Re: Fwd: Re: How do one uses the bios?
Message-Id: <19991020202240.016321@mailhost.mipsys.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

On Wed, Oct 20, 1999, Francois Desloges <fd@vipswitch.com> wrote:


>There was a big discussion in the Mail Archive around February/Mars 1999
about
>
>the different intialization role of the BIOS and the kernel respectively. I
>never found the definitive conclusions.
>What initialisation should be under the control of BIOS and what should be
>under kernel's control?

In an perfect world, the bios should initialize the 285 completely, the
PCI arbitrer (may not be in the 285, depending if you use the xbus or
not), assign all the PCI base addresses and interrupts, and
pre-initialize some hardware devices (like setting video chipset clocks,
setting IDE PIO/DMA mode). In practice, the kernel will re-do some of
those since lots of bioses are broken. Also, pieces of the kernel rely on
the ISA base beeing 0. That means that if you have a PCI south bridge,
you should assign it's ISA port iobase to 0.




 


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Wed Oct 20 20:52:42 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id UAA05587
	for <linux-arm-archive@lists.arm.linux.org.uk>; Wed, 20 Oct 1999 20:52:42 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 39F1813FEC; Wed, 20 Oct 1999 21:52:16 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S160551AbPJTTrH>;
	Wed, 20 Oct 1999 15:47:07 -0400
Received: by vger.rutgers.edu id <S160526AbPJTTj1>;
	Wed, 20 Oct 1999 15:39:27 -0400
Received: from mta4.snfc21.pbi.net ([206.13.28.142]:61467 "EHLO
        mta4.snfc21.pbi.net") by vger.rutgers.edu with ESMTP
	id <S160618AbPJTTgH>; Wed, 20 Oct 1999 15:36:07 -0400
Received: from java ([216.101.151.82])
 by mta4.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8)
 with SMTP id <0FJX00EWU2C8E6@mta4.snfc21.pbi.net> for
 linux-arm@vger.rutgers.edu; Wed, 20 Oct 1999 12:33:44 -0700 (PDT)
Date:   Wed, 20 Oct 1999 12:42:58 -0700
From: Dave Borja <dave_bb@pacbell.net>
Subject: newbe angelboot questions
To: linux-arm@vger.rutgers.edu
Message-id: <049301bf1b33$4fba6180$529765d8@java>
MIME-version: 1.0
X-Mailer: Microsoft Outlook Express 4.72.3110.5
Content-type: text/plain; charset="iso-8859-1"
Content-transfer-encoding: 7bit
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
X-Priority: 3
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

We got the brutus running with a linux kernel, now we are trying
to figure out how to do the same thing with another board based on
the ebsa110 + some extra chips. It has only 8mb and a different address map
obviously. We can download angel based apps using the ARM sdt
(which also works with the brutus) so I was wondering if angelboot
would work with our smaller board. I know I need to relink the kernel
for a different load address but I'm not sure what to use (or where exactly
to make the changes in the kernel source tree make files).  

I am also wondering where the angelboot options are documented/explained.
The one that comes in the angelboot tarball has the parms preset for
brutus, i.e.

base 0x8000
entry 0xc0008020
device /dev/ttyS0
options "9600 8N1" 
baud 115200
otherfile ramdisk.gz
otherbase 0x800000 

I took a guess at changing some of these (e.g. engry, base) so that
things would end up in one of the dram banks on our board and
cranked up angelboot. It looks like it makes a connection, but then
gets lost. This may be due to wrong options in opts or the zImage not
being linked correctly?....in any case I get the following when invoking
the angelboot:
:
%./angelboot  -f opts linux/arch/arm/boot/zImage
Initializing execution environment....
Downloading Image size 0x70576 to 0x8000

ERROR: Recieved 1d when expecting start packet character....
(the above repeats until I kill it w/cntl-c)

Any insights/hints on what to try/change are greatly appreciated
   thanks
 Dave Borja

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Wed Oct 20 22:56:32 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id WAA09469
	for <linux-arm-archive@lists.arm.linux.org.uk>; Wed, 20 Oct 1999 22:56:31 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 4C24D13F07; Wed, 20 Oct 1999 23:56:30 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S160617AbPJTVx3>;
	Wed, 20 Oct 1999 17:53:29 -0400
Received: by vger.rutgers.edu id <S160613AbPJTVxG>;
	Wed, 20 Oct 1999 17:53:06 -0400
Received: from tazenda.demon.co.uk ([158.152.220.239]:1594 "EHLO
        kings-cross.london.uk.eu.org") by vger.rutgers.edu with ESMTP
	id <S160622AbPJTVfR>; Wed, 20 Oct 1999 17:35:17 -0400
Received: from localhost
	([127.0.0.1] helo=kings-cross.london.uk.eu.org ident=phil)
	by kings-cross.london.uk.eu.org with esmtp (Exim 2.05 #1)
	id 11e3Nz-0006Ug-00; Wed, 20 Oct 1999 22:35:07 +0100
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: Nat Lanza <magus@cs.cmu.edu>
Cc: linux-arm@vger.rutgers.edu
Subject: Re: PDC20262 Controller with an EBSA285? 
In-Reply-To: Message from Nat Lanza <magus@cs.cmu.edu> 
   of "20 Oct 1999 17:29:00 EDT." <uocln8x90wz.fsf@evelake.pdl.cs.cmu.edu> 
References: <uoc4sfm9d19.fsf@evelake.pdl.cs.cmu.edu> <E11e3DF-0006R6-00@kings-cross.london.uk.eu.org>  <uocln8x90wz.fsf@evelake.pdl.cs.cmu.edu> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date:   Wed, 20 Oct 1999 22:35:07 +0100
From: Philip Blundell <Philip.Blundell@pobox.com>
Message-Id: <E11e3Nz-0006Ug-00@kings-cross.london.uk.eu.org>
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

>I get the same slow disk performance though, which I pretty
>much expected.

I think I actually have a PDC20262 sitting unused in one of my machines.  If I 
find time I will have a go at plugging into an ARM box and see if I get any 
sort of respectable disk throughput.

>2.3.19-rmk1 built with the cross-compiler still utterly fails to boot -- I
>don't even get as far as 'Uncompressing Linux...'. Any suggestions on
>what might be going on?

Not really.  I had some strange problem with recent 2.3 kernels that seemed to 
go away when I added a NOP to the front of head-armv.S, though I didn't debug 
it any further.  I know at least one other person has reported that 2.3.19 
fails to boot when 2.3.18 was OK.  It's weird.

You could try enabling the `low-level debugging' stuff, sprinkling calls to it 
through the early initialisation code and seeing if you can work out where it 
crashes.  If you currently use a zImage then you could see if uncompressed 
kernels are any better to eliminate one potential point of failure.

p.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Wed Oct 20 23:01:49 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id XAA09614
	for <linux-arm-archive@lists.arm.linux.org.uk>; Wed, 20 Oct 1999 23:01:48 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 35F0913DA7; Thu, 21 Oct 1999 00:01:32 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S160673AbPJTVz2>;
	Wed, 20 Oct 1999 17:55:28 -0400
Received: by vger.rutgers.edu id <S160765AbPJTVpL>;
	Wed, 20 Oct 1999 17:45:11 -0400
Received: from EVELAKE.PDL.CS.CMU.EDU ([128.2.189.75]:1634 "HELO
        evelake.pdl.cs.cmu.edu") by vger.rutgers.edu with SMTP
	id <S160470AbPJTV3i>; Wed, 20 Oct 1999 17:29:38 -0400
To: Philip Blundell <Philip.Blundell@pobox.com>
Cc: linux-arm@vger.rutgers.edu
Subject: Re: PDC20262 Controller with an EBSA285?
References: <uoc4sfm9d19.fsf@evelake.pdl.cs.cmu.edu> <E11e3DF-0006R6-00@kings-cross.london.uk.eu.org>
Mime-Version: 1.0 (generated by tm-edit 7.108)
Content-Type: text/plain; charset=US-ASCII
From: Nat Lanza <magus@cs.cmu.edu>
Date:   20 Oct 1999 17:29:00 -0400
In-Reply-To: Philip Blundell's message of "Wed, 20 Oct 1999 22:24:01 +0100"
Message-ID: <uocln8x90wz.fsf@evelake.pdl.cs.cmu.edu>
Lines:  24
X-Mailer: Gnus v5.6.31/XEmacs 20.4 - "Emerald"
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Philip Blundell <Philip.Blundell@pobox.com> writes:

> That should be OK, though newer versions do exist and that binutils in 
> particular has some nasty bugs.

I tried doing a crosscompile with an egcs-2.91.60 toolchain I have,
and that produced a 2.2.12 that works much better; the only patches I
needed were to add an entry for the PDC20262 to ide-pci.c and pci.h,
and to change serial_21285.c to handle the wacky serial setup on my
boards. I get the same slow disk performance though, which I pretty
much expected.

2.3.19-rmk1 built with the cross-compiler still utterly fails to boot -- I
don't even get as far as 'Uncompressing Linux...'. Any suggestions on
what might be going on?


--nat


-- 
nat lanza --------------------- research programmer, parallel data lab, cmu scs
magus@cs.cmu.edu -------------------------------- http://www.cs.cmu.edu/~magus/
there are no whole truths; all truths are half-truths -- alfred north whitehead
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Wed Oct 20 23:09:15 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id XAA09797
	for <linux-arm-archive@lists.arm.linux.org.uk>; Wed, 20 Oct 1999 23:09:14 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 7C93713E98; Thu, 21 Oct 1999 00:09:13 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S160663AbPJTVzv>;
	Wed, 20 Oct 1999 17:55:51 -0400
Received: by vger.rutgers.edu id <S160534AbPJTVuY>;
	Wed, 20 Oct 1999 17:50:24 -0400
Received: from tazenda.demon.co.uk ([158.152.220.239]:1549 "EHLO
        kings-cross.london.uk.eu.org") by vger.rutgers.edu with ESMTP
	id <S160744AbPJTVZ6>; Wed, 20 Oct 1999 17:25:58 -0400
Received: from localhost
	([127.0.0.1] helo=kings-cross.london.uk.eu.org ident=phil)
	by kings-cross.london.uk.eu.org with esmtp (Exim 2.05 #1)
	id 11e3DF-0006R6-00; Wed, 20 Oct 1999 22:24:01 +0100
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: Nat Lanza <magus@cs.cmu.edu>
Cc: linux-arm@vger.rutgers.edu
Subject: Re: PDC20262 Controller with an EBSA285? 
In-Reply-To: Message from Nat Lanza <magus@cs.cmu.edu> 
   of "20 Oct 1999 13:07:14 EDT." <uoc4sfm9d19.fsf@evelake.pdl.cs.cmu.edu> 
References: <uoc4sfm9d19.fsf@evelake.pdl.cs.cmu.edu> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date:   Wed, 20 Oct 1999 22:24:01 +0100
From: Philip Blundell <Philip.Blundell@pobox.com>
Message-Id: <E11e3DF-0006R6-00@kings-cross.london.uk.eu.org>
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

>I have some development boards based on the EBSA285 with integrated
>Promise 20262 IDE controllers and 13GB Quantum Fireball CR
>disks. Currently, they're running a slightly patched version of
>2.2.7-rmk4, and the disk performance is horrible -- peaks at a bit
>over 6MB/sec while chewing up all of the CPU. Since I want to use them 
>as servers, this isn't really good enough.

If the 20262 is the UDMA66 version, I have a feeling it is only properly 
supported by 2.3 kernels.

>Oh -- I'm building my kernels with gcc and binutils from the
>gcc-2.95.1-1nw5 and binutils-2.9.1.0.25-1nw2 RPMs from
>ftp.netwinder.org. Is this fine, or should I be using something else?

That should be OK, though newer versions do exist and that binutils in 
particular has some nasty bugs.

p.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Thu Oct 21 00:41:53 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id AAA12811
	for <linux-arm-archive@lists.arm.linux.org.uk>; Thu, 21 Oct 1999 00:41:53 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id DAAC713FD3; Thu, 21 Oct 1999 01:41:03 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S160995AbPJTWph>;
	Wed, 20 Oct 1999 18:45:37 -0400
Received: by vger.rutgers.edu id <S160644AbPJTWXH>;
	Wed, 20 Oct 1999 18:23:07 -0400
Received: from m67-nsv1-trogon.tch.cableol.net ([194.168.16.67]:2520 "EHLO
        caramon.armlinux.org.uk") by vger.rutgers.edu with ESMTP
	id <S160727AbPJTWS6>; Wed, 20 Oct 1999 18:18:58 -0400
Received: from raistlin.armlinux.org.uk (linux@raistlin [192.168.0.3])
	by caramon.armlinux.org.uk (8.8.7/8.8.7) with ESMTP id XAA06207;
	Wed, 20 Oct 1999 23:18:51 +0100
From: linux@arm.linux.org.uk
Received: (from linux@localhost) by raistlin.armlinux.org.uk (8.7.4/8.7.3) id XAA14039; Wed, 20 Oct 1999 23:17:38 +0100
Message-Id: <199910202217.XAA14039@raistlin.armlinux.org.uk>
Subject: Re: PDC20262 Controller with an EBSA285?
To: Philip.Blundell@pobox.com (Philip Blundell)
Date:   Wed, 20 Oct 1999 23:17:38 +0100 (BST)
Cc: magus@cs.cmu.edu, linux-arm@vger.rutgers.edu
In-Reply-To: <E11e3Nz-0006Ug-00@kings-cross.london.uk.eu.org> from "Philip Blundell" at Oct 20, 99 10:35:07 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Philip Blundell writes:
> >2.3.19-rmk1 built with the cross-compiler still utterly fails to boot -- I
> >don't even get as far as 'Uncompressing Linux...'. Any suggestions on
> >what might be going on?
> 
> Not really.  I had some strange problem with recent 2.3 kernels that seemed to 
> go away when I added a NOP to the front of head-armv.S, though I didn't debug 
> it any further.  I know at least one other person has reported that 2.3.19 
> fails to boot when 2.3.18 was OK.  It's weird.

I have not had any problems with 2.3.19 failing to boot.  There was a problem with
NOPs and the positioning of code in head-armv.S, but that is now fixed.  Permanently.
(usual disclaimers apply, free software, no warranty and all that).

> You could try enabling the `low-level debugging' stuff, sprinkling calls to it 
> through the early initialisation code and seeing if you can work out where it 
> crashes.  If you currently use a zImage then you could see if uncompressed 
> kernels are any better to eliminate one potential point of failure.

Indeed.  If you are seeing the 'Uncompressing Linux... done Now booting kernel'
messages, then the zImage is probably not the problem, and you should be better
off using the zImage method - at least you can have reasonable confidence that
the kernel image in memory is complete and whole.
   _____
  |_____| ------------------------------------------------- ---+---+-
  |   |        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' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Thu Oct 21 03:50:39 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id DAA17748
	for <linux-arm-archive@lists.arm.linux.org.uk>; Thu, 21 Oct 1999 03:50:38 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 555501407C; Thu, 21 Oct 1999 04:50:37 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S160757AbPJUCiZ>;
	Wed, 20 Oct 1999 22:38:25 -0400
Received: by vger.rutgers.edu id <S160683AbPJUCZN>;
	Wed, 20 Oct 1999 22:25:13 -0400
Received: from mta4.snfc21.pbi.net ([206.13.28.142]:54754 "EHLO
        mta4.snfc21.pbi.net") by vger.rutgers.edu with ESMTP
	id <S160323AbPJUCKC>; Wed, 20 Oct 1999 22:10:02 -0400
Received: from java ([216.101.151.82])
 by mta4.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8)
 with SMTP id <0FJX001GFKIWR1@mta4.snfc21.pbi.net> for
 linux-arm@vger.rutgers.edu; Wed, 20 Oct 1999 19:06:32 -0700 (PDT)
Date:   Wed, 20 Oct 1999 19:15:45 -0700
From: Dave Borja <dave_bb@pacbell.net>
Subject: broken links on ebsa110 page on arn  porject site
To: linux@arm.linux.org.uk, linux-arm@vger.rutgers.edu
Message-id: <04d101bf1b6a$2f3ca490$529765d8@java>
MIME-version: 1.0
X-Mailer: Microsoft Outlook Express 4.72.3110.5
Content-type: text/plain; charset="iso-8859-1"
Content-transfer-encoding: 7bit
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
X-Priority: 3
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

While nosing about on the www.arm.linux.org.uk, I looked into the
ebsa110 page. All the ftp links to the goodies seem to be broken. Is
this stuff all obsolete? I was hoping perhaps to make it work with
our ebsa110 derivitive. Anyone know what's what?
  thanks,
 Dave Borja


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Thu Oct 21 09:24:14 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id JAA27906
	for <linux-arm-archive@lists.arm.linux.org.uk>; Thu, 21 Oct 1999 09:24:03 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 09B5D13DBA; Thu, 21 Oct 1999 10:23:46 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157019AbPJUIW6>;
	Thu, 21 Oct 1999 04:22:58 -0400
Received: by vger.rutgers.edu id <S157008AbPJUIWe>;
	Thu, 21 Oct 1999 04:22:34 -0400
Received: from m42-nsv3-trogon.tch.cableol.net ([194.168.16.192]:2715 "EHLO
        caramon.armlinux.org.uk") by vger.rutgers.edu with ESMTP
	id <S160525AbPJUIWI>; Thu, 21 Oct 1999 04:22:08 -0400
Received: from raistlin.armlinux.org.uk (linux@raistlin [192.168.0.3])
	by caramon.armlinux.org.uk (8.8.7/8.8.7) with ESMTP id JAA08055;
	Thu, 21 Oct 1999 09:22:01 +0100
From: linux@arm.linux.org.uk
Received: (from linux@localhost) by raistlin.armlinux.org.uk (8.7.4/8.7.3) id JAA15674; Thu, 21 Oct 1999 09:20:47 +0100
Message-Id: <199910210820.JAA15674@raistlin.armlinux.org.uk>
Subject: Re: broken links on ebsa110 page on arn  porject site
To: dave_bb@pacbell.net (Dave Borja)
Date:   Thu, 21 Oct 1999 09:20:46 +0100 (BST)
Cc: linux-arm@vger.rutgers.edu
In-Reply-To: <04d101bf1b6a$2f3ca490$529765d8@java> from "Dave Borja" at Oct 20, 99 07:15:45 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Dave Borja writes:
> While nosing about on the www.arm.linux.org.uk, I looked into the
> ebsa110 page. All the ftp links to the goodies seem to be broken. Is
> this stuff all obsolete? I was hoping perhaps to make it work with
> our ebsa110 derivitive. Anyone know what's what?

Nope, I've just got to go through the web site and update all the links
(I re-organised the FTP site yesterday).
   _____
  |_____| ------------------------------------------------- ---+---+-
  |   |        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' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Thu Oct 21 09:54:06 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id JAA30312
	for <linux-arm-archive@lists.arm.linux.org.uk>; Thu, 21 Oct 1999 09:54:05 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 02C1A13F07; Thu, 21 Oct 1999 10:53:59 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156978AbPJUIx0>;
	Thu, 21 Oct 1999 04:53:26 -0400
Received: by vger.rutgers.edu id <S157039AbPJUIxF>;
	Thu, 21 Oct 1999 04:53:05 -0400
Received: from p78.nas1.is5.u-net.net ([195.102.200.78]:16595 "EHLO
        bastion.power-x.co.uk") by vger.rutgers.edu with ESMTP
	id <S156978AbPJUIo2>; Thu, 21 Oct 1999 04:44:28 -0400
Received: from springhead.px.uk.com (IDENT:dg@springhead.px.uk.com [172.16.17.15])
	by bastion.power-x.co.uk (8.9.3/8.9.3) with ESMTP id JAA05474;
	Thu, 21 Oct 1999 09:44:12 +0100
Date:   Thu, 21 Oct 1999 09:44:04 +0100 (BST)
From: "Dr. David Gilbert" <gilbertd@treblig.org>
X-Sender: dg@springhead.px.uk.com
To: Nat Lanza <magus@cs.cmu.edu>
Cc: linux-arm@vger.rutgers.edu
Subject: Re: PDC20262 Controller with an EBSA285?
In-Reply-To: <uoc4sfm9d19.fsf@evelake.pdl.cs.cmu.edu>
Message-ID: <Pine.LNX.4.10.9910210941410.13675-100000@springhead.px.uk.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

On 20 Oct 1999, Nat Lanza wrote:

> I have some development boards based on the EBSA285 with integrated
> Promise 20262 IDE controllers and 13GB Quantum Fireball CR
> disks. Currently, they're running a slightly patched version of
> 2.2.7-rmk4, and the disk performance is horrible -- peaks at a bit
> over 6MB/sec while chewing up all of the CPU. Since I want to use them 
> as servers, this isn't really good enough.

I have the 20262 in my Alpha; I've currently given up using it due to two
problems:
   1) The Linux driver seems to be unstable on my Alpha.
   2) I'm getting worse performance than with the non-UDMA controller on
my motherboard (a CMD646).
(I'd probably try and figure out why if it wasn't for the fact that it is
the only hard drive on my main machine)

Off the top of my head I seem to remember I was getting around 12MB/s from
my IBM 7200 RPM, UDMA66 drive using the CMD and about 9 with the 20262.

Dave

/------------------------------------------------------------------\
| Dr. David Alan Gilbert | Work: dg@px.uk.com (+44-161-286-2000)   |
| -------- G7FHJ --------|---------------------------------------- |
| Home: dave@treblig.org   http://www.treblig.clara.net            |
\------------------------------------------------------------------/

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Thu Oct 21 14:37:54 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id OAA15706
	for <linux-arm-archive@lists.arm.linux.org.uk>; Thu, 21 Oct 1999 14:37:48 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 0FBDF13DB8; Thu, 21 Oct 1999 15:33:16 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S156999AbPJUNcw>;
	Thu, 21 Oct 1999 09:32:52 -0400
Received: by vger.rutgers.edu id <S157057AbPJUNcd>;
	Thu, 21 Oct 1999 09:32:33 -0400
Received: from nt4.el.utwente.nl ([130.89.33.14]:1801 "EHLO nt4.el.utwente.nl")
	by vger.rutgers.edu with ESMTP id <S157014AbPJUNbj>;
	Thu, 21 Oct 1999 09:31:39 -0400
Received: (from mark@localhost)
	by nt4.el.utwente.nl (8.9.3/8.9.1) id PAA11867
	for linux-arm@vger.rutgers.edu; Thu, 21 Oct 1999 15:31:35 +0200
Date:   Thu, 21 Oct 1999 15:31:35 +0200
From: Mark van Doesburg <m.j.s.vandoesburg@student.utwente.nl>
Message-Id: <199910211331.PAA11867@nt4.el.utwente.nl>
To: linux-arm@vger.rutgers.edu
Subject: linking with binutils-2.9.5
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

I've just upgraded all my tools to:
	binutils-2.9.5.0.16
	gcc-2.95.1
	glibc-2.1.2

Unfortunately there seems to be some problem when linking the kernel. If I
have a look at System.map the addresses do not seem correct. I've edited
arch/arm/vmlinux-armv.lds and removed the OUTPUT_FORMAT line.

Here's the tail from System.map:

0014ed6c B userRegisters
0014ed70 B fpa11
0014ed74 B errno
0014ed78 A _end
c0004000 A swapper_pg_dir
c0008000 A __init_begin

Any suggestions ?

greetings,

Mark.
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Thu Oct 21 15:27:52 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id PAA20056
	for <linux-arm-archive@lists.arm.linux.org.uk>; Thu, 21 Oct 1999 15:27:31 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 3682813DCD; Thu, 21 Oct 1999 16:21:22 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S160740AbPJUOTE>;
	Thu, 21 Oct 1999 10:19:04 -0400
Received: by vger.rutgers.edu id <S157224AbPJUOQu>;
	Thu, 21 Oct 1999 10:16:50 -0400
Received: from sparkle.Generation.NET ([205.205.119.4]:35411 "EHLO
        sparkle.Generation.NET") by vger.rutgers.edu with ESMTP
	id <S157238AbPJUONI>; Thu, 21 Oct 1999 10:13:08 -0400
Received: from dual (generic253.197.205.205.IN-ADDR.ARPA [205.205.197.253] (may be forged))
	by sparkle.Generation.NET (8.9.3/8.9.3) with SMTP id KAA21448;
	Thu, 21 Oct 1999 10:13:17 -0400 (EDT)
From: Francois Desloges <fd@vipswitch.com>
To: Benjamin Herrenschmidt <benh@mipsys.com>
Subject: Re: Fwd: Re: 3c905B NIC + EBSA?
Date:   Thu, 21 Oct 1999 10:03:46 -0400
Content-Type: text/plain
References: <19991020201844.028219@mailhost.mipsys.com>
In-Reply-To: <19991020201844.028219@mailhost.mipsys.com>
Cc: linux-arm@vger.rutgers.edu
MIME-Version: 1.0
Message-Id: <9910211010330F.00780@dual>
Content-Transfer-Encoding: 8bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

On Wed, Oct 20, 1999, Benjamin Herrenschmidt <benh@mipsys.com> wrote:
> Correcting myself: You need 0x41000080 when flashing directly without the
> FMU header (JTAG). When using FMU, 0x410000C0 is the correct value.

I thought the FMU header was always needed by the EBSA-285 PBL?
Should I conclude that you uploaded the BIOS in Bank 0, and you didn't use the
PBL to start it up?
In which case why use the AIF header as well ?

-- 
François Desloges
fd@vipswitch.com
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Thu Oct 21 16:33:57 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id QAA24774
	for <linux-arm-archive@lists.arm.linux.org.uk>; Thu, 21 Oct 1999 16:33:56 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 84B7113D9F; Thu, 21 Oct 1999 17:29:25 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S160557AbPJUPSx>;
	Thu, 21 Oct 1999 11:18:53 -0400
Received: by vger.rutgers.edu id <S157228AbPJUPIy>;
	Thu, 21 Oct 1999 11:08:54 -0400
Received: from mailhost.mipsys.com ([62.161.177.33]:8003 "EHLO [62.161.177.33]")
	by vger.rutgers.edu with ESMTP id <S160640AbPJUOzB>;
	Thu, 21 Oct 1999 10:55:01 -0400
Received: from [192.168.1.10] by [192.168.1.2]
     with SMTP (QuickMail Pro Server for Mac 2.0); 21 OCT 99 17:02:58 UT
In-Reply-To: <9910211010330F.00780@dual>
X-Mailer: CTM PowerMail 2.4v7 <http://www.ctmdev.com>
Date:   Thu, 21 Oct 1999 16:54:46 +0200
To: Francois Desloges <fd@vipswitch.com>, linux-arm@vger.rutgers.edu
From: Benjamin Herrenschmidt <benh@mipsys.com>
Subject: Re(2): Fwd: Re: 3c905B NIC + EBSA?
Message-Id: <19991021165446.015410@mailhost.mipsys.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

On Thu, Oct 21, 1999, Francois Desloges <fd@vipswitch.com> wrote:

>I thought the FMU header was always needed by the EBSA-285 PBL?
>Should I conclude that you uploaded the BIOS in Bank 0, and you didn't
use the
>PBL to start it up?
>In which case why use the AIF header as well ?

You are right, the FMU header is needed when using the angel boot
selector. In my case, I'm directly flashing the bios at 0. 

I still use the AIF header because the bios relies on some infos beeing
in this header (the size of the data section). All this could probably be
changed via linker tricks in the ld script (and we could get rid of the
mkaif as well except for calculating the checksum).


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Thu Oct 21 17:05:28 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id RAA29248
	for <linux-arm-archive@lists.arm.linux.org.uk>; Thu, 21 Oct 1999 17:05:28 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 5708013D93; Thu, 21 Oct 1999 18:05:26 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S160961AbPJUPuB>;
	Thu, 21 Oct 1999 11:50:01 -0400
Received: by vger.rutgers.edu id <S160676AbPJUPVy>;
	Thu, 21 Oct 1999 11:21:54 -0400
Received: from tazenda.demon.co.uk ([158.152.220.239]:1040 "EHLO
        kings-cross.london.uk.eu.org") by vger.rutgers.edu with ESMTP
	id <S160675AbPJUPOM>; Thu, 21 Oct 1999 11:14:12 -0400
Received: from localhost
	([127.0.0.1] helo=kings-cross.london.uk.eu.org ident=phil)
	by kings-cross.london.uk.eu.org with esmtp (Exim 2.05 #1)
	id 11eJub-00009N-00; Thu, 21 Oct 1999 16:13:53 +0100
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: Mark van Doesburg <m.j.s.vandoesburg@student.utwente.nl>
Cc: linux-arm@vger.rutgers.edu
Subject: Re: linking with binutils-2.9.5 
In-Reply-To: Message from Mark van Doesburg <m.j.s.vandoesburg@student.utwente.nl> 
   of "Thu, 21 Oct 1999 15:31:35 +0200." <199910211331.PAA11867@nt4.el.utwente.nl> 
References: <199910211331.PAA11867@nt4.el.utwente.nl> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date:   Thu, 21 Oct 1999 16:13:53 +0100
From: Philip Blundell <Philip.Blundell@pobox.com>
Message-Id: <E11eJub-00009N-00@kings-cross.london.uk.eu.org>
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

>Unfortunately there seems to be some problem when linking the kernel. If I
>have a look at System.map the addresses do not seem correct. I've edited
>arch/arm/vmlinux-armv.lds and removed the OUTPUT_FORMAT line.

What kernel source are you using?  Removing that line is not enough to get an 
old kernel to build properly.  You also need to set the base address in the 
linker script rather than with -Ttext, as is done in recent kernels (both 2.2 
and 2.3 in CVS, and also I think Russell's latest 2.3).

p.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Thu Oct 21 19:11:38 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id TAA12146
	for <linux-arm-archive@lists.arm.linux.org.uk>; Thu, 21 Oct 1999 19:11:38 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 0B2EB13DD0; Thu, 21 Oct 1999 20:11:37 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S160801AbPJURws>;
	Thu, 21 Oct 1999 13:52:48 -0400
Received: by vger.rutgers.edu id <S160782AbPJUROD>;
	Thu, 21 Oct 1999 13:14:03 -0400
Received: from sparkle.Generation.NET ([205.205.119.4]:43991 "EHLO
        sparkle.Generation.NET") by vger.rutgers.edu with ESMTP
	id <S157424AbPJURDT>; Thu, 21 Oct 1999 13:03:19 -0400
Received: from dual (generic253.197.205.205.IN-ADDR.ARPA [205.205.197.253] (may be forged))
	by sparkle.Generation.NET (8.9.3/8.9.3) with SMTP id NAA15617
	for <linux-arm@vger.rutgers.edu>; Thu, 21 Oct 1999 13:03:34 -0400 (EDT)
From: Francois Desloges <fd@vipswitch.com>
To: linux-arm@vger.rutgers.edu
Subject: Fwd: Re: Fwd: Re: How do one uses the bios?
Date:   Thu, 21 Oct 1999 13:00:31 -0400
Content-Type: text/plain
MIME-Version: 1.0
Message-Id: <9910211300510J.00780@dual>
Content-Transfer-Encoding: 8bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing


On Wed, 20 Oct 1999, Benjamin Herrenschmidt <benh@mipsys.com> wrote:
> In an perfect world, the bios should initialize the 285 completely, the
> PCI arbitrer (may not be in the 285, depending if you use the xbus or
> not), assign all the PCI base addresses and interrupts, and
> pre-initialize some hardware devices (like setting video chipset clocks,
> setting IDE PIO/DMA mode). In practice, the kernel will re-do some of
> those since lots of bioses are broken. Also, pieces of the kernel rely on
> the ISA base beeing 0. That means that if you have a PCI south bridge,
> you should assign it's ISA port iobase to 0.

Is the low-level initalization performed by the kernel platform dependent
(depending of the quality of their usual BIOSes?) or is it the same for all the
different famillies of CPU/Platform?

And, hum... regardless of if it is the same for all Platform, (that would only
be generally interesting) are there two lists defined somewhere, describing:

A) List of things that (ARM-)Linux BIOS _must_ initalize before kernel loading:

B) List of things the  (ARM-)Linux kernel _will_ initialize anyway:


-- 
François Desloges
fd@vipswitch.com
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Fri Oct 22 08:38:06 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id IAA08742
	for <linux-arm-archive@lists.arm.linux.org.uk>; Fri, 22 Oct 1999 08:38:06 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id F414B13DA6; Fri, 22 Oct 1999 09:38:03 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157077AbPJVHh3>;
	Fri, 22 Oct 1999 03:37:29 -0400
Received: by vger.rutgers.edu id <S157070AbPJVHhL>;
	Fri, 22 Oct 1999 03:37:11 -0400
Received: from studict.student.utwente.nl ([130.89.220.2]:2612 "EHLO
        studict.student.utwente.nl") by vger.rutgers.edu with ESMTP
	id <S156999AbPJVHhB>; Fri, 22 Oct 1999 03:37:01 -0400
Received: from poekie.test (ut125204.inbel.utwente.nl [130.89.125.204])
          by studict.student.utwente.nl (8.8.6/MQT) with ESMTP id JAA04705;
          Fri, 22 Oct 1999 09:36:57 +0200 (METDST)
Received: (from mark@localhost)
	by poekie.test (8.9.1/8.9.1) id JAA14036;
	Fri, 22 Oct 1999 09:12:27 +0200
Date:   Fri, 22 Oct 1999 09:12:27 +0200
From: Mark van Doesburg <mark@nt4.el.utwente.nl>
Message-Id: <199910220712.JAA14036@poekie.test>
To: Philip.Blundell@pobox.com
Subject: Re: linking with binutils-2.9.5
Cc: linux-arm@vger.rutgers.edu
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

	What kernel source are you using?  Removing that line is not
	enough to get an old kernel to build properly.  You also need to
	set the base address in the linker script rather than with
	-Ttext, as is done in recent kernels (both 2.2 and 2.3 in CVS,
	and also I think Russell's latest 2.3).

Oops, I'm using linux-2.2.12-rmk1. I should be able to fix it now.

Thanks,

Mark.
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Fri Oct 22 09:46:54 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id JAA10735
	for <linux-arm-archive@lists.arm.linux.org.uk>; Fri, 22 Oct 1999 09:46:53 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 20D2613E5F; Fri, 22 Oct 1999 10:44:26 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157219AbPJVImb>;
	Fri, 22 Oct 1999 04:42:31 -0400
Received: by vger.rutgers.edu id <S157063AbPJVIlH>;
	Fri, 22 Oct 1999 04:41:07 -0400
Received: from ns.dvico.co.kr ([203.231.37.1]:3909 "EHLO rose.dvico.com")
	by vger.rutgers.edu with ESMTP id <S157397AbPJVIkF>;
	Fri, 22 Oct 1999 04:40:05 -0400
Received: by www.dvico.co.kr with Internet Mail Service (5.5.2448.0)
	id <VD1W0H86>; Fri, 22 Oct 1999 17:39:52 +0900
Message-ID: <1143B682B6F7D111BCA30060979D42CF0290C3@www.dvico.co.kr>
From: "James Kim(Jin-Soo)" <JamesKim@dvico.com>
To: linux-arm@vger.rutgers.edu
Subject: EBSA285 Schematic or Gerber file Request
Date:   Fri, 22 Oct 1999 17:39:51 +0900
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="KS_C_5601-1987"
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Hi!
Is there anybody who can give me EBSA285 evaluation schematic & Gerber
file? (Schematic only is also O.K.)
I'm trying to involve strong arm linux project from now on. I'd like to set
up some environment for it.
Please help me.


James KIM
Senior Engineer, DViCO Corp.

Tel: +82-342-703-9199
Fax: +82-342-703-9599
H.P: +82-16-333-8663
Email: jameskim@dvico.com


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Fri Oct 22 13:30:45 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id NAA24954
	for <linux-arm-archive@lists.arm.linux.org.uk>; Fri, 22 Oct 1999 13:30:44 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 78ACA13EBF; Fri, 22 Oct 1999 14:30:42 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157155AbPJVMaJ>;
	Fri, 22 Oct 1999 08:30:09 -0400
Received: by vger.rutgers.edu id <S157070AbPJVM3v>;
	Fri, 22 Oct 1999 08:29:51 -0400
Received: from mail.uni-greifswald.de ([141.53.8.33]:3776 "EHLO
        mail.uni-greifswald.de") by vger.rutgers.edu with ESMTP
	id <S157077AbPJVM3b>; Fri, 22 Oct 1999 08:29:31 -0400
Received: from localhost (sh990154@localhost)
	by mail.uni-greifswald.de (8.9.2/8.9.2) with SMTP id OAA29010
	for <linux-arm@vger.rutgers.edu>; Fri, 22 Oct 1999 14:29:24 +0200 (METDST)
Date:   Fri, 22 Oct 1999 14:29:23 +0200 (METDST)
From: "Hanske;Stefan" <sh990154@mail.uni-greifswald.de>
To: linux-arm@vger.rutgers.edu
Subject: gcc-2.95.2
Message-ID: <Pine.GHP.4.02.9910221424560.28698-100000@mail.uni-greifswald.de>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing


Hi,

I've had some problems with gcc-2.95.2. When applying the
gcc-2_95-diff-990730.gz-patch from Phils netwinder ftp space, the build
fails with memory violations from the newly build compiler.

If I do not apply this patch, I get the old 

Internal compiler error in `purge_addressof_1', at function.c:3173

sometimes.

What patches are actually required for gcc-2.95.x ??

TIA.

Stefan


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Fri Oct 22 16:27:41 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id QAA31407
	for <linux-arm-archive@lists.arm.linux.org.uk>; Fri, 22 Oct 1999 16:27:41 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 80E4213EE1; Fri, 22 Oct 1999 17:27:39 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157330AbPJVPSQ>;
	Fri, 22 Oct 1999 11:18:16 -0400
Received: by vger.rutgers.edu id <S157287AbPJVPSF>;
	Fri, 22 Oct 1999 11:18:05 -0400
Received: from dfw7-1.relay.mail.uu.net ([199.171.54.106]:61156 "EHLO
        dfw7-1.relay.mail.uu.net") by vger.rutgers.edu with ESMTP
	id <S157401AbPJVPOB>; Fri, 22 Oct 1999 11:14:01 -0400
Received: from xedia.com by dfw7sosrv11.alter.net with SMTP 
	(peer crosschecked as: madway.xedia.com [198.202.232.199])
	id QQhmau02472;
	Fri, 22 Oct 1999 15:13:52 GMT
Received: from tonga.xedia.com by xedia.com (4.1/SMI-4.1)
	id AA00194; Fri, 22 Oct 99 11:11:55 EDT
Received: by tonga.xedia.com (SMI-8.6/SMI-SVR4)
	id LAA26231; Fri, 22 Oct 1999 11:13:46 -0400
Date:   Fri, 22 Oct 1999 11:13:46 -0400
Message-Id: <199910221513.LAA26231@tonga.xedia.com>
From: Paul Koning <pkoning@xedia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: JamesKim@dvico.com
Cc: linux-arm@vger.rutgers.edu
Subject: Re: EBSA285 Schematic or Gerber file Request
References: <1143B682B6F7D111BCA30060979D42CF0290C3@www.dvico.co.kr>
X-Mailer: VM 6.34 under 20.3 "Vatican City" XEmacs  Lucid
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

I remember finding them somewhere on the DEC/Intel Strongarm web
server.  They certainly are included with the eval board (on
floppies).  But I had them before then.

	paul
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Fri Oct 22 18:16:35 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id SAA07843
	for <linux-arm-archive@lists.arm.linux.org.uk>; Fri, 22 Oct 1999 18:16:34 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id D348B13EEC; Fri, 22 Oct 1999 19:16:32 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157254AbPJVRPW>;
	Fri, 22 Oct 1999 13:15:22 -0400
Received: by vger.rutgers.edu id <S157401AbPJVQq7>;
	Fri, 22 Oct 1999 12:46:59 -0400
Received: from littleblue.ftech.net ([195.200.12.27]:5289 "EHLO
        relay5.ftech.net") by vger.rutgers.edu with ESMTP
	id <S157628AbPJVQoU>; Fri, 22 Oct 1999 12:44:20 -0400
Received: from ibm9.ftech.net ([212.32.16.79] helo=prunus.localnet)
	by relay5.ftech.net with smtp (Exim 3.03-ftechp4 #4)
	id 11ehky-00059W-00
	for linux-arm@vger.rutgers.edu; Fri, 22 Oct 1999 17:41:33 +0100
From: Toby Bryans <toby@navaho.co.uk>
Date:   Fri, 22 Oct 1999 17:43:20 BST
To: linux-arm@vger.rutgers.edu
Subject: 2.0.36 to 2.2.12
Content-Type: text/plain
Message-ID: <Navaho-2.3.18-940610600.80000@an4group.com>
X-Mailer: Navaho Server Suite v2.3.18 [Linux/i486]
X-User-Agent: Mozilla/4.7 [en] (X11; I; Linux 2.2.12-20 i686)
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Hello,

I apologise in advance if these questions have been asked before,
and are stupid: I must confess to being a complete arm-linux newbie, although
I have had five years experience with ix86 linux.

I have installed the version of RedHat ArmLinux from 
ftp.arm.uk.linux.org, which has kernel 2.0.36 and uses a.out on my
StrongARM RPC.  I would now like to move the whole lot up to 
kernel 2.2.12 and the latest binutils and tool chain.  AFAICT from
the documentation this requires me to build a cross-compiler on
an ix86 box, and then compile everything from there (in effect
rebuilding the whole system).  As well from the speed issues and the
whole 12Mb max of a.out are there any ways of redoing the whole lot
on the SARPC?  I suspect not.

Is there an alternative source for a 2.2 installation (I notice that
there is talk of a debian install for example) to save me from doing
all of this?

Many thanks in advance,

Toby Bryans

-- 
Project Manager, Navaho Internet Ltd       http://www.navaho.co.uk/
CTO, Cygnet Computer Solutions Ltd & Chairman, Empire Retailing Ltd
Technical Support, an4 group Ltd         'Phone: +44 (0)7970 422053
http://homepages.tcp.co.uk/~elesoc/         Fax: +44 (0)7970 127058



unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Fri Oct 22 19:47:54 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id TAA14684
	for <linux-arm-archive@lists.arm.linux.org.uk>; Fri, 22 Oct 1999 19:47:54 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 0490E13F10; Fri, 22 Oct 1999 20:44:13 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157406AbPJVSlD>;
	Fri, 22 Oct 1999 14:41:03 -0400
Received: by vger.rutgers.edu id <S157077AbPJVSWS>;
	Fri, 22 Oct 1999 14:22:18 -0400
Received: from EVELAKE.PDL.CS.CMU.EDU ([128.2.189.75]:1761 "HELO
        evelake.pdl.cs.cmu.edu") by vger.rutgers.edu with SMTP
	id <S157571AbPJVSG3>; Fri, 22 Oct 1999 14:06:29 -0400
To: linux-arm@vger.rutgers.edu
Subject: PDC20262 redux
Mime-Version: 1.0 (generated by tm-edit 7.108)
Content-Type: text/plain; charset=US-ASCII
From: Nat Lanza <magus@cs.cmu.edu>
Date:   22 Oct 1999 14:06:00 -0400
Message-ID: <uoc4sfj8e47.fsf@evelake.pdl.cs.cmu.edu>
Lines:  34
X-Mailer: Gnus v5.6.31/XEmacs 20.4 - "Emerald"
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

I've gotten 2.3.18-rmk1-cvs991006 to boot on my hardware, but there's
a problem with the PDC20262 support -- 

Uniform Multi-Platform E-IDE driver Revision: 6.20
PDC20262: IDE controller on PCI bus 00 dev a0     
PDC20262: not 100% native mode: will probe irqs later
PDC20262: ROM enabled at 0x02400000                  
PDC20262: (U)DMA Burst Bit DISABLED Primary PCI Mode Secondary PCI Mode.
PDC20262: neither IDE port enabled (BIOS)

leading, of course, to

VFS: Cannot open root device 03:01                              
Kernel panic: VFS: Unable to mount root fs on 03:01


The 'neither IDE port enabled' bit surprises me; it boots fine under
2.2.7 and 2.2.12, so clearly some port has to be active.

Can anyone shed any light on this?

For a little extra info, this is on a modified EBSA285 board, and my
kernels are cross-compiled from a gcc-2.95.1/binutils-2.9.5.0.14
toolchain that I've built.

Neither 2.3.19-rmk1 nor 2.3.18-rmk2 boots on this machine, btw.


--nat

-- 
nat lanza --------------------- research programmer, parallel data lab, cmu scs
magus@cs.cmu.edu -------------------------------- http://www.cs.cmu.edu/~magus/
there are no whole truths; all truths are half-truths -- alfred north whitehead
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Fri Oct 22 23:24:26 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id XAA21169
	for <linux-arm-archive@lists.arm.linux.org.uk>; Fri, 22 Oct 1999 23:24:25 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 75A3D13F11; Sat, 23 Oct 1999 00:24:00 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157296AbPJVWEj>;
	Fri, 22 Oct 1999 18:04:39 -0400
Received: by vger.rutgers.edu id <S157576AbPJVVzl>;
	Fri, 22 Oct 1999 17:55:41 -0400
Received: from tazenda.demon.co.uk ([158.152.220.239]:1065 "EHLO
        kings-cross.london.uk.eu.org") by vger.rutgers.edu with ESMTP
	id <S157655AbPJVV0n>; Fri, 22 Oct 1999 17:26:43 -0400
Received: from localhost
	([127.0.0.1] helo=kings-cross.london.uk.eu.org ident=phil)
	by kings-cross.london.uk.eu.org with esmtp (Exim 2.05 #1)
	id 11emCC-0000Ld-00; Fri, 22 Oct 1999 22:25:56 +0100
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: Toby Bryans <toby@navaho.co.uk>
Cc: linux-arm@vger.rutgers.edu
Subject: Re: 2.0.36 to 2.2.12 
In-Reply-To: Message from Toby Bryans <toby@navaho.co.uk> 
   of "Fri, 22 Oct 1999 17:43:20 -0000." <Navaho-2.3.18-940610600.80000@an4group.com> 
References: <Navaho-2.3.18-940610600.80000@an4group.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date:   Fri, 22 Oct 1999 22:25:56 +0100
From: Philip Blundell <Philip.Blundell@pobox.com>
Message-Id: <E11emCC-0000Ld-00@kings-cross.london.uk.eu.org>
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

>StrongARM RPC.  I would now like to move the whole lot up to 
>kernel 2.2.12 and the latest binutils and tool chain.

You have three options:

1. Install a binary distribution from (e.g.) Debian.
2. Cross-build an ELF toolchain from another machine and use it to install the 
latest kernel and so on.
3. Natively bootstrap a modern toolchain on the RiscPC.

These are pretty much in ascending order of difficulty, though all are 
possible.  If you have specific questions feel free to post them here.

p.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sat Oct 23 18:58:11 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id SAA06946
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sat, 23 Oct 1999 18:58:11 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id EAA8213F6F; Sat, 23 Oct 1999 19:58:09 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157438AbPJWRsq>;
	Sat, 23 Oct 1999 13:48:46 -0400
Received: by vger.rutgers.edu id <S157427AbPJWRNF>;
	Sat, 23 Oct 1999 13:13:05 -0400
Received: from p34-cordelia-gui.tch.enablis.net ([212.250.233.34]:1155 "EHLO
        caramon.armlinux.org.uk") by vger.rutgers.edu with ESMTP
	id <S160014AbPJWRCQ>; Sat, 23 Oct 1999 13:02:16 -0400
Received: from raistlin.armlinux.org.uk (linux@raistlin [192.168.0.3])
	by caramon.armlinux.org.uk (8.8.7/8.8.7) with ESMTP id SAA19075
	for <linux-arm@vger.rutgers.edu>; Sat, 23 Oct 1999 18:02:07 +0100
From: linux@arm.linux.org.uk
Received: (from linux@localhost) by raistlin.armlinux.org.uk (8.7.4/8.7.3) id SAA00809 for linux-arm@vger.rutgers.edu; Sat, 23 Oct 1999 18:01:08 +0100
Message-Id: <199910231701.SAA00809@raistlin.armlinux.org.uk>
Subject: binutils 2.9.1 ld changes instruction opcodes incorrectly with kernel 2.3.xx
To: linux-arm@vger.rutgers.edu
Date:   Sat, 23 Oct 1999 18:01:07 +0100 (BST)
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Hi,

I've just been trying to debug a kernel problem that someone reported
against 2.3.18 on the latest kernel (2.3.22), but hit a rather major
snag.

binutils 2.9.1.0.19a and 2.9.1.0.25 suffer from a case of the random
changing opcode syndrome.  I've checked the surface of the machine for
bacteria and viruses ;)

Anyway, what seems to be happening is that certain 'b' instructions get
converted to 'bl', since it appears that for PC_ARM_24 relocations in
a relocatable link just have the correction added to them.  ie,

	eafffffe -> eb000043 instead of ea000043

This oddity seems to be fixed in binutils 2.9.5.0.16.

If you intend to build 2.3.xx kernels, please do not use binutils 2.9.1.
   _____
  |_____| ------------------------------------------------- ---+---+-
  |   |        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' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sat Oct 23 20:35:21 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id UAA12850
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sat, 23 Oct 1999 20:35:21 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 7678413EA1; Sat, 23 Oct 1999 21:35:19 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157212AbPJWTbY>;
	Sat, 23 Oct 1999 15:31:24 -0400
Received: by vger.rutgers.edu id <S157428AbPJWTHK>;
	Sat, 23 Oct 1999 15:07:10 -0400
Received: from tazenda.demon.co.uk ([158.152.220.239]:1184 "EHLO
        kings-cross.london.uk.eu.org") by vger.rutgers.edu with ESMTP
	id <S157212AbPJWSvl>; Sat, 23 Oct 1999 14:51:41 -0400
Received: from localhost
	([127.0.0.1] helo=kings-cross.london.uk.eu.org ident=phil)
	by kings-cross.london.uk.eu.org with esmtp (Exim 2.05 #1)
	id 11f6GK-0000Mg-00; Sat, 23 Oct 1999 19:51:32 +0100
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: linux@arm.linux.org.uk
Cc: linux-arm@vger.rutgers.edu
Subject: Re: binutils 2.9.1 ld changes instruction opcodes incorrectly with kernel 2.3.xx 
In-Reply-To: Message from linux@arm.linux.org.uk 
   of "Sat, 23 Oct 1999 18:01:07 BST." <199910231701.SAA00809@raistlin.armlinux.org.uk> 
References: <199910231701.SAA00809@raistlin.armlinux.org.uk> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date:   Sat, 23 Oct 1999 19:51:32 +0100
From: Philip Blundell <Philip.Blundell@pobox.com>
Message-Id: <E11f6GK-0000Mg-00@kings-cross.london.uk.eu.org>
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

>binutils 2.9.1.0.19a and 2.9.1.0.25 suffer from a case of the random
>changing opcode syndrome.  I've checked the surface of the machine for
>bacteria and viruses ;)
>
>Anyway, what seems to be happening is that certain 'b' instructions get
>converted to 'bl', since it appears that for PC_ARM_24 relocations in
>a relocatable link just have the correction added to them.  ie,
>
>	eafffffe -> eb000043 instead of ea000043
>
>This oddity seems to be fixed in binutils 2.9.5.0.16.

Yes, this is an old and fairly common problem.  From what I remember it
occurs mainly with inter-section branches; this is one of the reasons the 
.text.init thing didn't use to work too well.  There is a patch in my 
directory on netwinder.org that helps a bit with this but as you have 
observed a better solution is just to use the newer tools.

p.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sun Oct 24 04:32:42 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id EAA27351
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sun, 24 Oct 1999 04:32:41 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id CE5D813FE9; Sun, 24 Oct 1999 05:32:38 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157100AbPJXDby>;
	Sat, 23 Oct 1999 23:31:54 -0400
Received: by vger.rutgers.edu id <S157099AbPJXDbZ>;
	Sat, 23 Oct 1999 23:31:25 -0400
Received: from [212.219.8.163] ([212.219.8.163]:2756 "HELO inkvine.fluff.org")
	by vger.rutgers.edu with SMTP id <S157087AbPJXDbN>;
	Sat, 23 Oct 1999 23:31:13 -0400
Received: from localhost (localhost [127.0.0.1])
	by inkvine.fluff.org (Postfix) with ESMTP id B41D74688B
	for <linux-arm@vger.rutgers.edu>; Sun, 24 Oct 1999 04:30:58 +0100 (BST)
Date:   Sun, 24 Oct 1999 04:30:58 +0100 (BST)
From: Chris Rutter <chris@fluff.org>
Reply-To: chris@fluff.org
To: ARM Linux mailing list <linux-arm@vger.rutgers.edu>
Subject: 2.3 build problem
Message-ID: <Pine.LNX.4.10.9910240429550.2661-100000@inkvine.fluff.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

ds2400.c refers to |system_serial_number|, but looking at setup.[ch],
they contain only |system_serial_{low,high}| -- what's the fix?

(This stops 2.3-from-CVS kernels building, that is.)

-- 
Chris <chris@fluff.org>                         ( http://www.fluff.org/chris )

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sun Oct 24 10:51:37 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id KAA09081
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sun, 24 Oct 1999 10:51:36 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id AC8ED14007; Sun, 24 Oct 1999 11:51:34 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157019AbPJXJvG>;
	Sun, 24 Oct 1999 05:51:06 -0400
Received: by vger.rutgers.edu id <S157011AbPJXJur>;
	Sun, 24 Oct 1999 05:50:47 -0400
Received: from tazenda.demon.co.uk ([158.152.220.239]:1274 "EHLO
        kings-cross.london.uk.eu.org") by vger.rutgers.edu with ESMTP
	id <S156978AbPJXJuk>; Sun, 24 Oct 1999 05:50:40 -0400
Received: from localhost
	([127.0.0.1] helo=kings-cross.london.uk.eu.org ident=phil)
	by kings-cross.london.uk.eu.org with esmtp (Exim 2.05 #1)
	id 11fKII-0004cT-00; Sun, 24 Oct 1999 10:50:30 +0100
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: chris@fluff.org
Cc: ARM Linux mailing list <linux-arm@vger.rutgers.edu>
Subject: Re: 2.3 build problem 
In-Reply-To: Message from Chris Rutter <chris@fluff.org> 
   of "Sun, 24 Oct 1999 04:30:58 BST." <Pine.LNX.4.10.9910240429550.2661-100000@inkvine.fluff.org> 
References: <Pine.LNX.4.10.9910240429550.2661-100000@inkvine.fluff.org> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date:   Sun, 24 Oct 1999 10:50:30 +0100
From: Philip Blundell <Philip.Blundell@pobox.com>
Message-Id: <E11fKII-0004cT-00@kings-cross.london.uk.eu.org>
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

>ds2400.c refers to |system_serial_number|, but looking at setup.[ch],
>they contain only |system_serial_{low,high}| -- what's the fix?

Change ds2400.c to use the new-style serial number.  Rather than being a 
single 64-bit value it's now two 32-bit values.  I'll do that shortly.  
Sorry.

p.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sun Oct 24 11:08:51 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id LAA09471
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sun, 24 Oct 1999 11:08:51 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 2E51413F88; Sun, 24 Oct 1999 12:08:30 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157039AbPJXKH6>;
	Sun, 24 Oct 1999 06:07:58 -0400
Received: by vger.rutgers.edu id <S156978AbPJXKHj>;
	Sun, 24 Oct 1999 06:07:39 -0400
Received: from p05-magpie-gui.tch.enablis.net ([194.168.180.5]:1382 "EHLO
        caramon.armlinux.org.uk") by vger.rutgers.edu with ESMTP
	id <S157011AbPJXKHZ>; Sun, 24 Oct 1999 06:07:25 -0400
Received: from raistlin.armlinux.org.uk (linux@raistlin [192.168.0.3])
	by caramon.armlinux.org.uk (8.8.7/8.8.7) with ESMTP id LAA22206;
	Sun, 24 Oct 1999 11:07:19 +0100
From: linux@arm.linux.org.uk
Received: (from linux@localhost) by raistlin.armlinux.org.uk (8.7.4/8.7.3) id LAA31327; Sun, 24 Oct 1999 11:06:16 +0100
Message-Id: <199910241006.LAA31327@raistlin.armlinux.org.uk>
Subject: Re: 2.3 build problem
To: chris@fluff.org
Date:   Sun, 24 Oct 1999 11:06:16 +0100 (BST)
Cc: linux-arm@vger.rutgers.edu
In-Reply-To: <Pine.LNX.4.10.9910240429550.2661-100000@inkvine.fluff.org> from "Chris Rutter" at Oct 24, 99 04:30:58 am
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Chris Rutter writes:
> ds2400.c refers to |system_serial_number|, but looking at setup.[ch],
> they contain only |system_serial_{low,high}| -- what's the fix?
> 
> (This stops 2.3-from-CVS kernels building, that is.)

ds2400.c is not in my kernel tree so I can't comment.
   _____
  |_____| ------------------------------------------------- ---+---+-
  |   |        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' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Tue Oct 26 02:53:10 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id CAA22168
	for <linux-arm-archive@lists.arm.linux.org.uk>; Tue, 26 Oct 1999 02:53:10 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 5541A13DA7; Tue, 26 Oct 1999 03:53:07 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157160AbPJZBwn>;
	Mon, 25 Oct 1999 21:52:43 -0400
Received: by vger.rutgers.edu id <S157089AbPJZBwY>;
	Mon, 25 Oct 1999 21:52:24 -0400
Received: from [212.219.8.163] ([212.219.8.163]:3217 "HELO inkvine.fluff.org")
	by vger.rutgers.edu with SMTP id <S157039AbPJZBwJ>;
	Mon, 25 Oct 1999 21:52:09 -0400
Received: from localhost (localhost [127.0.0.1])
	by inkvine.fluff.org (Postfix) with ESMTP
	id 6A69B46890; Tue, 26 Oct 1999 02:52:15 +0100 (BST)
Date:   Tue, 26 Oct 1999 02:52:15 +0100 (BST)
From: Chris Rutter <chris@fluff.org>
Reply-To: chris@fluff.org
To: Toby Bryans <toby@navaho.co.uk>
Cc: linux-arm@vger.rutgers.edu
Subject: Re: 2.0.36 to 2.2.12
In-Reply-To: <Navaho-2.3.18-940610600.80000@an4group.com>
Message-ID: <Pine.LNX.4.10.9910260235370.13525-100000@inkvine.fluff.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

On Fri, 22 Oct 1999, Toby Bryans wrote:

> StrongARM RPC.  I would now like to move the whole lot up to 
> kernel 2.2.12 and the latest binutils and tool chain.  AFAICT from
> the documentation this requires me to build a cross-compiler on
> an ix86 box, and then compile everything from there (in effect
> rebuilding the whole system).

You seem to be with-it on the issues here, so this should be fairly
painless. :)

The easiest thing you can do is install the partial port of RedHat 6.
Go to ftp.inkvine.fluff.org:/pub/armlinux/people/chris/misc/a.out+libc4/
and follow the instructions, and then you can install the RPMs stored
at the same location -- this includes binary RPMs of binutils and egcs
from about six months ago.

Unfortunately (ish) I'm not actively working on supporting this any
longer, however.  Stefan Hanske is still active in this area, though,
I believe.

> As well from the speed issues and the
> whole 12Mb max of a.out are there any ways of redoing the whole lot
> on the SARPC?  I suspect not.

Certainly.  Follow http://www.inkvine.fluff.org/~chris/arm-tools.html
to build yourself an up-to-date toolchain on your RiscPC, and then
compile whatever you want to (so long as you're savvy enough to
hack the bits and pieces that fall off under ARM).

Unless you're desperately keen to go down this route, I wouldn't
recommend it -- try one of the binary distributions.

> Is there an alternative source for a 2.2 installation (I notice that
> there is talk of a debian install for example) to save me from doing
> all of this?

The slightly less easy, but ultimately probably more profitable
route is to install Debian.  You'll need to fetch the binary image
from ftp.jimpick.com:/pub/debian/arm/image/, and un-tar it as
your new root filesystem.  There's a list of small things you'll
need to patch (a couple of duff permissions) to make it happy on the
RiscPC, but once you've done that and got it booted, you can then
use apt/dpkg to install the binary-arm packages on the Debian FTP
servers.

Think about which route you would best like to go down, and then ask
for some more specific help.

-- 
Chris <chris@fluff.org>                         ( http://www.fluff.org/chris )

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Tue Oct 26 05:26:22 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id FAA25926
	for <linux-arm-archive@lists.arm.linux.org.uk>; Tue, 26 Oct 1999 05:26:22 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id B310713E05; Tue, 26 Oct 1999 06:26:19 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157089AbPJZEZz>;
	Tue, 26 Oct 1999 00:25:55 -0400
Received: by vger.rutgers.edu id <S157020AbPJZEZf>;
	Tue, 26 Oct 1999 00:25:35 -0400
Received: from ns.dvico.co.kr ([203.231.37.1]:1099 "EHLO rose.dvico.com")
	by vger.rutgers.edu with ESMTP id <S157019AbPJZEZY>;
	Tue, 26 Oct 1999 00:25:24 -0400
Received: by www.dvico.co.kr with Internet Mail Service (5.5.2448.0)
	id <V4QR9QQF>; Tue, 26 Oct 1999 13:25:14 +0900
Message-ID: <1143B682B6F7D111BCA30060979D42CF0290C8@www.dvico.co.kr>
From: "James Kim(Jin-Soo)" <JamesKim@dvico.com>
To: linux-arm@vger.rutgers.edu
Subject: Ebsa285 develpopment environment
Date:   Mon, 25 Oct 1999 09:56:46 +0900
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="KS_C_5601-1987"
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

I'm newbie to Ebsa285 cross platform development environment. 
Is there anybody to have some information about installation package step
by step? or RPM files is better.

Please help me.


James KIM
Senior Engineer, DViCO Corp.

Tel: +82-342-703-9199
Fax: +82-342-703-9599
H.P: +82-16-333-8663
Email: jameskim@dvico.com


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Tue Oct 26 22:11:36 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id WAA03918
	for <linux-arm-archive@lists.arm.linux.org.uk>; Tue, 26 Oct 1999 22:11:35 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id EC7C71417A; Tue, 26 Oct 1999 23:07:40 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157260AbPJZVGk>;
	Tue, 26 Oct 1999 17:06:40 -0400
Received: by vger.rutgers.edu id <S157358AbPJZUv3>;
	Tue, 26 Oct 1999 16:51:29 -0400
Received: from mta3.snfc21.pbi.net ([206.13.28.141]:35551 "EHLO
        mta3.snfc21.pbi.net") by vger.rutgers.edu with ESMTP
	id <S157461AbPJZUh1>; Tue, 26 Oct 1999 16:37:27 -0400
Received: from java ([216.101.151.82])
 by mta3.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8)
 with SMTP id <0FK800JXB9A3L0@mta3.snfc21.pbi.net> for
 linux-arm@vger.rutgers.edu; Tue, 26 Oct 1999 13:37:16 -0700 (PDT)
Date:   Tue, 26 Oct 1999 13:46:18 -0700
From: Dave Borja <dave_bb@pacbell.net>
Subject: driver for cs8900 ethernet chip
To: linux-arm <linux-arm@vger.rutgers.edu>, alan@cymru.net
Message-id: <02b201bf1ff3$27bf84c0$529765d8@java>
MIME-version: 1.0
X-Mailer: Microsoft Outlook Express 4.72.3110.5
Content-type: text/plain; charset="iso-8859-1"
Content-transfer-encoding: 7bit
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
X-Priority: 3
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Hi, a few months ago someone mentioned that there
was a driver available for this ethernet chip? I belive
Russ Nelson was supposed to have written one- anyone
know where I can obtain source to cross compile for
sa110? 
   Thanks, 
 Dave Borja

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Tue Oct 26 23:19:01 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id XAA07365
	for <linux-arm-archive@lists.arm.linux.org.uk>; Tue, 26 Oct 1999 23:19:00 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id EDA98141D5; Wed, 27 Oct 1999 00:05:10 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157109AbPJZWEn>;
	Tue, 26 Oct 1999 18:04:43 -0400
Received: by vger.rutgers.edu id <S157150AbPJZWE2>;
	Tue, 26 Oct 1999 18:04:28 -0400
Received: from tazenda.demon.co.uk ([158.152.220.239]:1472 "EHLO
        kings-cross.london.uk.eu.org") by vger.rutgers.edu with ESMTP
	id <S157119AbPJZWD4>; Tue, 26 Oct 1999 18:03:56 -0400
Received: from localhost
	([127.0.0.1] helo=kings-cross.london.uk.eu.org ident=phil)
	by kings-cross.london.uk.eu.org with esmtp (Exim 2.05 #1)
	id 11gEgj-0004H1-00; Tue, 26 Oct 1999 23:03:29 +0100
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: Dave Borja <dave_bb@pacbell.net>
Cc: linux-arm <linux-arm@vger.rutgers.edu>, alan@cymru.net
Subject: Re: driver for cs8900 ethernet chip 
In-Reply-To: Message from Dave Borja <dave_bb@pacbell.net> 
   of "Tue, 26 Oct 1999 13:46:18 PDT." <02b201bf1ff3$27bf84c0$529765d8@java> 
References: <02b201bf1ff3$27bf84c0$529765d8@java> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date:   Tue, 26 Oct 1999 23:03:29 +0100
From: Philip Blundell <Philip.Blundell@pobox.com>
Message-Id: <E11gEgj-0004H1-00@kings-cross.london.uk.eu.org>
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

>Hi, a few months ago someone mentioned that there
>was a driver available for this ethernet chip? I belive
>Russ Nelson was supposed to have written one- anyone
>know where I can obtain source to cross compile for
>sa110? 

drivers/net/cs89x0.c?  It works for me.

p.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Wed Oct 27 00:40:12 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id AAA09794
	for <linux-arm-archive@lists.arm.linux.org.uk>; Wed, 27 Oct 1999 00:40:12 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id D2B6713FE5; Wed, 27 Oct 1999 01:27:30 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157100AbPJZX1C>;
	Tue, 26 Oct 1999 19:27:02 -0400
Received: by vger.rutgers.edu id <S157134AbPJZX0a>;
	Tue, 26 Oct 1999 19:26:30 -0400
Received: from mta3.snfc21.pbi.net ([206.13.28.141]:43176 "EHLO
        mta3.snfc21.pbi.net") by vger.rutgers.edu with ESMTP
	id <S156978AbPJZX0I>; Tue, 26 Oct 1999 19:26:08 -0400
Received: from java ([216.101.151.82])
 by mta3.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8)
 with SMTP id <0FK800J11H0P52@mta3.snfc21.pbi.net> for
 linux-arm@vger.rutgers.edu; Tue, 26 Oct 1999 16:24:26 -0700 (PDT)
Date:   Tue, 26 Oct 1999 16:33:29 -0700
From: Dave Borja <dave_bb@pacbell.net>
Subject: Re: driver for cs8900 ethernet chip
To: linux-arm <linux-arm@vger.rutgers.edu>
Message-id: <02eb01bf200a$824decd0$529765d8@java>
MIME-version: 1.0
X-Mailer: Microsoft Outlook Express 4.72.3110.5
Content-type: text/plain; charset="iso-8859-1"
Content-transfer-encoding: 7bit
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
X-Priority: 3
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing





>>Hi, a few months ago someone mentioned that there
>>was a driver available for this ethernet chip? I belive
>>Russ Nelson was supposed to have written one- anyone
>>know where I can obtain source to cross compile for
>>sa110?
>
>drivers/net/cs89x0.c?  It works for me.
>
>p.
>
>

Hmmm- yes, thanks, that looks like it'll do it. As I've posted before,
we're trying to get an sa110 based (actually, ebsa110 based) board
going w/Linux. We are having trouble w/getting angelboot to talk to
it, so I was hoping to go the tftp loader route. Set up a bootp, tftp server
on a host, kick off a tftp loader on the sa110 board and boot the
kernel from there. Then mount an NFS root file system.  Hence the need
for cs8900 driver.

Which reminds me, has anyone tried the loader Russell King once had
posted to the arm-linux stie? It's not there anymore.
  Thanks,
 Dave Borja


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Wed Oct 27 10:07:04 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id KAA28578
	for <linux-arm-archive@lists.arm.linux.org.uk>; Wed, 27 Oct 1999 10:07:04 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 3CA6F13D97; Wed, 27 Oct 1999 11:06:58 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157166AbPJ0JG0>;
	Wed, 27 Oct 1999 05:06:26 -0400
Received: by vger.rutgers.edu id <S157165AbPJ0JGM>;
	Wed, 27 Oct 1999 05:06:12 -0400
Received: from p58-cordelia-gui.tch.enablis.net ([212.250.233.58]:4618 "EHLO
        caramon.arm.linux.org.uk") by vger.rutgers.edu with ESMTP
	id <S157166AbPJ0JFz>; Wed, 27 Oct 1999 05:05:55 -0400
Received: from raistlin.arm.linux.org.uk (linux@raistlin.arm.linux.org.uk [192.168.0.3])
	by caramon.arm.linux.org.uk (8.8.7/8.8.7) with ESMTP id JAA02618;
	Wed, 27 Oct 1999 09:10:59 +0100
From: linux@arm.linux.org.uk
Received: (from linux@localhost) by raistlin.arm.linux.org.uk (8.7.4/8.7.3) id JAA01911; Wed, 27 Oct 1999 09:10:01 +0100
Message-Id: <199910270810.JAA01911@raistlin.arm.linux.org.uk>
Subject: Re: driver for cs8900 ethernet chip
To: dave_bb@pacbell.net (Dave Borja)
Date:   Wed, 27 Oct 1999 09:10:00 +0100 (BST)
Cc: linux-arm@vger.rutgers.edu
In-Reply-To: <02eb01bf200a$824decd0$529765d8@java> from "Dave Borja" at Oct 26, 99 04:33:29 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Dave Borja writes:
> Which reminds me, has anyone tried the loader Russell King once had
> posted to the arm-linux stie? It's not there anymore.

Ergh, it should be there, somewhere.  I'll look into it.  Maybe it's
sitting in the "Old" tree.
   _____
  |_____| ------------------------------------------------- ---+---+-
  |   |        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' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Wed Oct 27 10:07:40 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id KAA28633
	for <linux-arm-archive@lists.arm.linux.org.uk>; Wed, 27 Oct 1999 10:07:39 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 41E3D13E88; Wed, 27 Oct 1999 11:07:38 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157164AbPJ0JG6>;
	Wed, 27 Oct 1999 05:06:58 -0400
Received: by vger.rutgers.edu id <S157165AbPJ0JG3>;
	Wed, 27 Oct 1999 05:06:29 -0400
Received: from p58-cordelia-gui.tch.enablis.net ([212.250.233.58]:4618 "EHLO
        caramon.arm.linux.org.uk") by vger.rutgers.edu with ESMTP
	id <S157164AbPJ0JGE>; Wed, 27 Oct 1999 05:06:04 -0400
Received: from raistlin.arm.linux.org.uk (linux@raistlin.arm.linux.org.uk [192.168.0.3])
	by caramon.arm.linux.org.uk (8.8.7/8.8.7) with ESMTP id JAA02738;
	Wed, 27 Oct 1999 09:55:31 +0100
From: linux@arm.linux.org.uk
Received: (from linux@localhost) by raistlin.arm.linux.org.uk (8.7.4/8.7.3) id JAA02693; Wed, 27 Oct 1999 09:54:32 +0100
Message-Id: <199910270854.JAA02693@raistlin.arm.linux.org.uk>
Subject: Re: PDC20262 redux
To: magus@cs.cmu.edu (Nat Lanza)
Date:   Wed, 27 Oct 1999 09:54:32 +0100 (BST)
Cc: linux-arm@vger.rutgers.edu
In-Reply-To: <uoc4sfj8e47.fsf@evelake.pdl.cs.cmu.edu> from "Nat Lanza" at Oct 22, 99 02:06:00 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Nat Lanza writes:
> I've gotten 2.3.18-rmk1-cvs991006 to boot on my hardware, but there's
> a problem with the PDC20262 support -- 
> 
> Uniform Multi-Platform E-IDE driver Revision: 6.20
> PDC20262: IDE controller on PCI bus 00 dev a0     
> PDC20262: not 100% native mode: will probe irqs later
> PDC20262: ROM enabled at 0x02400000                  
> PDC20262: (U)DMA Burst Bit DISABLED Primary PCI Mode Secondary PCI Mode.
> PDC20262: neither IDE port enabled (BIOS)
> 
> leading, of course, to
> 
> VFS: Cannot open root device 03:01                              
> Kernel panic: VFS: Unable to mount root fs on 03:01

Can you add some debugging code to ide-pci.c, specifically around the
"Set up the IDE ports" code?  I think you will find that the IDE enable
bits are not being set.

Note that 2.2.12 does not directly support the PDC20262 interface, so
these enable bits would have been missed.  The enable bits are at:

 PCI config offset 0x50, bit masks 0x02 (primary) 0x04 (secondary)

and should be set by the BIOS or kernel loader.
   _____
  |_____| ------------------------------------------------- ---+---+-
  |   |        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' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Wed Oct 27 15:40:28 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id PAA13928
	for <linux-arm-archive@lists.arm.linux.org.uk>; Wed, 27 Oct 1999 15:39:59 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 54DE614051; Wed, 27 Oct 1999 16:28:25 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157187AbPJ0OUi>;
	Wed, 27 Oct 1999 10:20:38 -0400
Received: by vger.rutgers.edu id <S157227AbPJ0OQJ>;
	Wed, 27 Oct 1999 10:16:09 -0400
Received: from sparkle.Generation.NET ([205.205.119.4]:44580 "EHLO
        sparkle.Generation.NET") by vger.rutgers.edu with ESMTP
	id <S157407AbPJ0OKM>; Wed, 27 Oct 1999 10:10:12 -0400
Received: from dual (generic253.197.205.205.IN-ADDR.ARPA [205.205.197.253] (may be forged))
	by sparkle.Generation.NET (8.9.3/8.9.3) with SMTP id KAA13290
	for <linux-arm@vger.rutgers.edu>; Wed, 27 Oct 1999 10:10:24 -0400 (EDT)
From: Francois Desloges <fd@vipswitch.com>
To: linux-arm@vger.rutgers.edu
Subject: BIOS initialization questions
Date:   Wed, 27 Oct 1999 09:50:37 -0400
Content-Type: text/plain
MIME-Version: 1.0
Message-Id: <99102710074905.04182@dual>
Content-Transfer-Encoding: 8bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

As I can easily program EBSA-285 Flash Bank 0. I wish to be able to run the
Russell's BIOS 1.05 in this initial bank. The BIOS entry code look like this
(the comments are from me) :

>	bic	r11, lr, #3	@  r11 = LinkRegister & 0xFFFFFFFC;
>	mrs	r0, cpsr		@ Change to supervisor mode with IRQ
and >	bic	r0, r0, #0x1f	@    FIQ disabled
>	orr	r0, r0, #0xd3
>	msr	cpsr, r0
>	ldr	sp, [r11, #8]	@ StackPointer= *((LinkRegister & 0xFFFFFFFC)+8)

I don't have PBL source code. What's 8 bytes after the bl to Bank #3?
And is there another stack space I can use into the BIOS if I eliminate the PBL?
Oh and why clear the last two bits of lr, doesn't ARM alignment force them at
0 anyway?

-- 
François Desloges
fd@vipswitch.com
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Wed Oct 27 16:18:41 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id QAA16014
	for <linux-arm-archive@lists.arm.linux.org.uk>; Wed, 27 Oct 1999 16:18:40 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 693381409E; Wed, 27 Oct 1999 17:13:14 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157205AbPJ0PDl>;
	Wed, 27 Oct 1999 11:03:41 -0400
Received: by vger.rutgers.edu id <S157233AbPJ0O4W>;
	Wed, 27 Oct 1999 10:56:22 -0400
Received: from sparkle.Generation.NET ([205.205.119.4]:46761 "EHLO
        sparkle.Generation.NET") by vger.rutgers.edu with ESMTP
	id <S157446AbPJ0OxU>; Wed, 27 Oct 1999 10:53:20 -0400
Received: from dual (generic253.197.205.205.IN-ADDR.ARPA [205.205.197.253] (may be forged))
	by sparkle.Generation.NET (8.9.3/8.9.3) with SMTP id KAA27003
	for <linux-arm@vger.rutgers.edu>; Wed, 27 Oct 1999 10:53:33 -0400 (EDT)
From: Francois Desloges <fd@vipswitch.com>
To: linux-arm@vger.rutgers.edu
Subject: Re: BIOS initialization questions
Date:   Wed, 27 Oct 1999 10:48:07 -0400
Content-Type: text/plain
References: <99102710074905.04182@dual>
In-Reply-To: <99102710074905.04182@dual>
MIME-Version: 1.0
Message-Id: <99102710505806.04182@dual>
Content-Transfer-Encoding: 8bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

On Wed, 27 Oct 1999, Francois Desloges wrote:
> As I can easily program EBSA-285 Flash Bank 0. I wish to be able to run the
> Russell's BIOS 1.05 in this initial bank. The BIOS entry code look like this
> (the comments are from me) :
> 
> >	bic	r11, lr, #3	@  r11 = LinkRegister & 0xFFFFFFFC;
> >	mrs	r0, cpsr		@ Change to supervisor mode with IRQ
> and >	bic	r0, r0, #0x1f	@    FIQ disabled
> >	orr	r0, r0, #0xd3
> >	msr	cpsr, r0
> >	ldr	sp, [r11, #8]	@ StackPointer= *((LinkRegister & 0xFFFFFFFC)+8)
> 
> I don't have PBL source code. What's 8 bytes after the bl to Bank #3?
> And is there another stack space I can use into the BIOS if I eliminate the PBL?
> Oh and why clear the last two bits of lr, doesn't ARM alignment force them at
> 0 anyway?

OK! I've just fallen on the ARM Procedure Call Standard (APCS) from the ARM
Software Developement Toolkit Reference Guide. Is that what is used in the
BIOS & ARM-Linux project?
 -- 
François Desloges
fd@vipswitch.com
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Wed Oct 27 17:17:41 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id RAA20991
	for <linux-arm-archive@lists.arm.linux.org.uk>; Wed, 27 Oct 1999 17:17:40 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 547C013F7D; Wed, 27 Oct 1999 18:05:53 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157226AbPJ0QBc>;
	Wed, 27 Oct 1999 12:01:32 -0400
Received: by vger.rutgers.edu id <S157160AbPJ0PvW>;
	Wed, 27 Oct 1999 11:51:22 -0400
Received: from p33-magpie-gui.tch.enablis.net ([194.168.180.33]:4826 "EHLO
        caramon.arm.linux.org.uk") by vger.rutgers.edu with ESMTP
	id <S157287AbPJ0PkG>; Wed, 27 Oct 1999 11:40:06 -0400
Received: from raistlin.arm.linux.org.uk (linux@raistlin.arm.linux.org.uk [192.168.0.3])
	by caramon.arm.linux.org.uk (8.8.7/8.8.7) with ESMTP id QAA04708;
	Wed, 27 Oct 1999 16:34:04 +0100
From: linux@arm.linux.org.uk
Received: (from linux@localhost) by raistlin.arm.linux.org.uk (8.7.4/8.7.3) id QAA07073; Wed, 27 Oct 1999 16:33:04 +0100
Message-Id: <199910271533.QAA07073@raistlin.arm.linux.org.uk>
Subject: Re: BIOS initialization questions
To: fd@vipswitch.com (Francois Desloges)
Date:   Wed, 27 Oct 1999 16:33:04 +0100 (BST)
Cc: linux-arm@vger.rutgers.edu
In-Reply-To: <99102710505806.04182@dual> from "Francois Desloges" at Oct 27, 99 10:48:07 am
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Francois Desloges writes:
> OK! I've just fallen on the ARM Procedure Call Standard (APCS) from the ARM
> Software Developement Toolkit Reference Guide. Is that what is used in the
> BIOS & ARM-Linux project?

The SDK is not used.  Please have a closer look at the build system for the
BIOS.
   _____
  |_____| ------------------------------------------------- ---+---+-
  |   |        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' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Wed Oct 27 17:40:37 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id RAA21627
	for <linux-arm-archive@lists.arm.linux.org.uk>; Wed, 27 Oct 1999 17:40:35 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 2865114019; Wed, 27 Oct 1999 18:32:29 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157226AbPJ0Q0y>;
	Wed, 27 Oct 1999 12:26:54 -0400
Received: by vger.rutgers.edu id <S157188AbPJ0QNZ>;
	Wed, 27 Oct 1999 12:13:25 -0400
Received: from kauket.visi.com ([209.98.98.22]:36312 "HELO mail-out.visi.com")
	by vger.rutgers.edu with SMTP id <S157403AbPJ0P4p>;
	Wed, 27 Oct 1999 11:56:45 -0400
Received: from isis.visi.com (isis.visi.com [209.98.98.8])
	by mail-out.visi.com (Postfix) with ESMTP id 70F263808
	for <linux-arm@vger.rutgers.edu>; Wed, 27 Oct 1999 10:56:40 -0500 (CDT)
Received: from localhost (mestery@localhost)
	by isis.visi.com (8.8.8/8.8.8) with ESMTP id KAA27439
	for <linux-arm@vger.rutgers.edu>; Wed, 27 Oct 1999 10:56:40 -0500 (CDT)
X-Authentication-Warning: isis.visi.com: mestery owned process doing -bs
Date:   Wed, 27 Oct 1999 10:56:40 -0500 (CDT)
From: <mestery@visi.com>
To: linux-arm@vger.rutgers.edu
Subject: Versioning in the latest netwinder image
Message-ID: <Pine.GSO.4.10.9910271054130.27254-100000@isis.visi.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Hi,

I'm not sure if this is the proper place to ask this, but I'm going to
ask anyways.:)

I have downloaded the latest netwinder disk image
(dm-3.0-15-public4.tar.gz), and the libraries appear to have been
compiled without versioning.  When I try and run some of my code that I
had been using with my previous distribution (the debian one), the code
doesn't run and complains as follows:

./node.exe: /lib/libm.so.6: no version information available (required by ./node.exe)

Why are the libraries compiled without versioning?  And, can I fix this
by continuing to use dm-3.0.15 and just recompiling glibc?  Thanks for
the help.

--
Kyle Mestery			| StorageTek's Storage Networking Group
mestery@visi.com		| http://www.freebsd.org/
mestery@netwinder.org		| http://www.netwinder.org/
	Protect your right to privacy: www.freecrypto.org

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Wed Oct 27 18:13:56 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id SAA22485
	for <linux-arm-archive@lists.arm.linux.org.uk>; Wed, 27 Oct 1999 18:13:56 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 04A031415C; Wed, 27 Oct 1999 19:06:25 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157454AbPJ0RE4>;
	Wed, 27 Oct 1999 13:04:56 -0400
Received: by vger.rutgers.edu id <S157214AbPJ0Qtx>;
	Wed, 27 Oct 1999 12:49:53 -0400
Received: from nexusel.demon.co.uk ([158.152.30.195]:17876 "EHLO
        globe.nexus.co.uk") by vger.rutgers.edu with ESMTP
	id <S157495AbPJ0QlT>; Wed, 27 Oct 1999 12:41:19 -0400
Received: from [192.0.0.21] (helo=fountain.nexus.co.uk ident=mail)
	by globe.nexus.co.uk with smtp (Exim 2.12 #1)
	id 11gW5F-0000ut-00; Wed, 27 Oct 1999 16:37:57 +0000
Received: from [127.0.0.1] (helo=fountain ident=pb)
	by fountain.nexus.co.uk with esmtp (Exim 3.03 #1)
	id 11gW5E-0003Cx-00; Wed, 27 Oct 1999 17:37:56 +0100
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: mestery@visi.com
Cc: linux-arm@vger.rutgers.edu
Subject: Re: Versioning in the latest netwinder image 
In-Reply-To: Message from <mestery@visi.com> 
   of "Wed, 27 Oct 1999 10:56:40 CDT." <Pine.GSO.4.10.9910271054130.27254-100000@isis.visi.com> 
References: <Pine.GSO.4.10.9910271054130.27254-100000@isis.visi.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date:   Wed, 27 Oct 1999 17:37:56 +0100
From: Philip Blundell <pb@nexus.co.uk>
Message-Id: <E11gW5E-0003Cx-00@fountain.nexus.co.uk>
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

>Why are the libraries compiled without versioning?

Historical reasons.  When the NetWinder guys started out, the ARM tools didn't 
support versioning properly.  Although Jim Pick later fixed this and it's now 
fine, the NetWinder images kept using --disable-versioning to maintain binary 
compatibility with the systems that were in the field.

The Titan and Debian distributions both use versioned libraries.

>And, can I fix this by continuing to use dm-3.0.15 and just 
>recompiling glibc? 

You can try, but there is quite a large risk that not all programs will go on 
working if you do.  It would probably be better to relink your application, or 
if this is not an option install a versioned glibc in some special place where 
only your application will find it.

p.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Wed Oct 27 18:26:34 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id SAA22911
	for <linux-arm-archive@lists.arm.linux.org.uk>; Wed, 27 Oct 1999 18:26:28 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 343881417A; Wed, 27 Oct 1999 19:22:30 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157508AbPJ0QzC>;
	Wed, 27 Oct 1999 12:55:02 -0400
Received: by vger.rutgers.edu id <S157189AbPJ0Qym>;
	Wed, 27 Oct 1999 12:54:42 -0400
Received: from mailhost.mipsys.com ([62.161.177.33]:8002 "EHLO [62.161.177.33]")
	by vger.rutgers.edu with ESMTP id <S157226AbPJ0QeF>;
	Wed, 27 Oct 1999 12:34:05 -0400
Received: from [192.168.1.10] by [192.168.1.2]
     with SMTP (QuickMail Pro Server for Mac 2.0); 27 OCT 99 18:42:09 UT
In-Reply-To: <99102710074905.04182@dual>
X-Mailer: CTM PowerMail 2.4v7 <http://www.ctmdev.com>
Date:   Wed, 27 Oct 1999 18:33:44 +0200
To: Francois Desloges <fd@vipswitch.com>, linux-arm@vger.rutgers.edu
From: Benjamin Herrenschmidt <benh@mipsys.com>
Subject: Re: BIOS initialization questions
Message-Id: <19991027183344.021398@mailhost.mipsys.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

On Wed, Oct 27, 1999, Francois Desloges <fd@vipswitch.com> wrote:

>As I can easily program EBSA-285 Flash Bank 0. I wish to be able to run the
>Russell's BIOS 1.05 in this initial bank. The BIOS entry code look like this
>(the comments are from me) :
>
>>	bic	r11, lr, #3	@  r11 = LinkRegister & 0xFFFFFFFC;
>>	mrs	r0, cpsr		@ Change to supervisor mode with IRQ
>and >	bic	r0, r0, #0x1f	@    FIQ disabled
>>	orr	r0, r0, #0xd3
>>	msr	cpsr, r0
>>	ldr	sp, [r11, #8]	@ StackPointer= *((LinkRegister & 0xFFFFFFFC)+8)
>
>I don't have PBL source code. What's 8 bytes after the bl to Bank #3?
>And is there another stack space I can use into the BIOS if I eliminate the
>PBL?
>Oh and why clear the last two bits of lr, doesn't ARM alignment force them at
>0 anyway?

At this point of boot, there is no stack (and possibly no RAM).

r11 contains the link (aligned) and in sp is stored the value at 8(r11).
This is because the BIOS entry expects to be called by the AIF header's
code which does basically a "bl entry". This header contains, after this
bl, a field with the size of the data section (stored here by mkaif).
This size is stored in sp and is used later, after the RAM detection,
when copying the datas to RAM.

I beleive this could be improved by using linker tricks to have the
linker store this size in a place where the code can fetch it via
pc-relative access, but I don't know ld well enough to write such a script.



unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Wed Oct 27 18:46:23 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id SAA23433
	for <linux-arm-archive@lists.arm.linux.org.uk>; Wed, 27 Oct 1999 18:46:23 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 5C1CB1407A; Wed, 27 Oct 1999 19:34:24 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157475AbPJ0RIH>;
	Wed, 27 Oct 1999 13:08:07 -0400
Received: by vger.rutgers.edu id <S157598AbPJ0QxG>;
	Wed, 27 Oct 1999 12:53:06 -0400
Received: from aleph1.demon.co.uk ([158.152.9.127]:28763 "EHLO
        court2.aleph1.co.uk") by vger.rutgers.edu with ESMTP
	id <S157422AbPJ0Qbj>; Wed, 27 Oct 1999 12:31:39 -0400
Received: from chewy.aleph1.co.uk ([194.70.44.163])
	by court2.aleph1.co.uk with smtp (Exim 2.05 #1)
	id 11gVyt-0005JQ-00
	for linux-arm@vger.rutgers.edu; Wed, 27 Oct 1999 17:31:23 +0100
Date:   Wed, 27 Oct 1999 17:31:25 +0100 (BST)
From: Wookey <wookey@aleph1.co.uk>
Subject: Re: 2.0.36 to 2.2.12
To: armlinux list <linux-arm@vger.rutgers.edu>
In-Reply-To: <Navaho-2.3.18-940610600.80000@an4group.com>
Message-ID: <Marcel-1.50-1027163125-868h+Ty@chewy.aleph1.co.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
X-Organization: Aleph One,Cambridge, UK. Tel +44 1223 811679
X-Mailer: ANT RISCOS Marcel [ver 1.50]
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

On Fri 22 Oct, Toby Bryans wrote:

> Is there an alternative source for a 2.2 installation (I notice that
> there is talk of a debian install for example) to save me from doing
> all of this?

Not yet - see previous replies for details, but Aleph One are working on
tidying up the existing stuff to make a reasonably painless distribution
for RISCOS machines. Once we've got something working and documented
we'll get it more up to date. This should provide what you are looking
for, but it'll be a while yet before we have a 2.2 kernel release with
toochain so it depends how much of a hurry you are in...

Wookey
-- 
Aleph One Ltd, Bottisham, CAMBRIDGE, CB5 9BA, UK  Tel (00 44) 1223 811679
work: http://www.aleph1.co.uk/     play: http://www.chaos.org.uk/~wookey/

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Wed Oct 27 18:48:34 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id SAA23447
	for <linux-arm-archive@lists.arm.linux.org.uk>; Wed, 27 Oct 1999 18:48:33 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 6305114188; Wed, 27 Oct 1999 19:40:08 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157424AbPJ0RS7>;
	Wed, 27 Oct 1999 13:18:59 -0400
Received: by vger.rutgers.edu id <S157164AbPJ0Qwy>;
	Wed, 27 Oct 1999 12:52:54 -0400
Received: from nexusel.demon.co.uk ([158.152.30.195]:17888 "EHLO
        globe.nexus.co.uk") by vger.rutgers.edu with ESMTP
	id <S157439AbPJ0Qnt>; Wed, 27 Oct 1999 12:43:49 -0400
Received: from [192.0.0.21] (helo=fountain.nexus.co.uk ident=mail)
	by globe.nexus.co.uk with smtp (Exim 2.12 #1)
	id 11gW9Z-0000vI-00; Wed, 27 Oct 1999 16:42:25 +0000
Received: from [127.0.0.1] (helo=fountain ident=pb)
	by fountain.nexus.co.uk with esmtp (Exim 3.03 #1)
	id 11gW9Y-0003Dh-00; Wed, 27 Oct 1999 17:42:24 +0100
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: Francois Desloges <fd@vipswitch.com>
Cc: linux-arm@vger.rutgers.edu
Subject: Re: BIOS initialization questions 
In-Reply-To: Message from Francois Desloges <fd@vipswitch.com> 
   of "Wed, 27 Oct 1999 10:48:07 EDT." <99102710505806.04182@dual> 
References: <99102710074905.04182@dual>  <99102710505806.04182@dual> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date:   Wed, 27 Oct 1999 17:42:24 +0100
From: Philip Blundell <pb@nexus.co.uk>
Message-Id: <E11gW9Y-0003Dh-00@fountain.nexus.co.uk>
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

>OK! I've just fallen on the ARM Procedure Call Standard (APCS) from the ARM
>Software Developement Toolkit Reference Guide. Is that what is used in the
>BIOS & ARM-Linux project?

By `that', do you mean the SDK or the APCS?  If the former, the answer is no.  
If the latter, the answer is basically yes.  This is for the kernel and user 
applications, I can't speak for the BIOS.

The APCS per se is somewhat outdated now; the latest procedure call standard 
is the ATPCS.  GCC does not currently have full support for ATPCS, though.

p.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Wed Oct 27 18:52:56 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id SAA23583
	for <linux-arm-archive@lists.arm.linux.org.uk>; Wed, 27 Oct 1999 18:52:56 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id ECB9A14190; Wed, 27 Oct 1999 19:43:39 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157198AbPJ0R1k>;
	Wed, 27 Oct 1999 13:27:40 -0400
Received: by vger.rutgers.edu id <S157563AbPJ0REc>;
	Wed, 27 Oct 1999 13:04:32 -0400
Received: from netwinder.org ([207.245.35.202]:4704 "EHLO www.netwinder.org")
	by vger.rutgers.edu with ESMTP id <S157415AbPJ0Qov>;
	Wed, 27 Oct 1999 12:44:51 -0400
Received: from gw.rebel.com (gate.rebel.com [207.245.35.200])
	by www.netwinder.org (8.8.7/8.8.7) with SMTP id MAA08180;
	Wed, 27 Oct 1999 12:44:14 -0400
Message-ID: <38172B09.5B81617F@netwinder.org>
Received: from dhcp111.isa.ott.rebel.com by gw.rebel.com
          via smtpd (for netwinder.org [207.245.35.202]) with SMTP; 27 Oct 1999 16:44:11 UT
Date:   Wed, 27 Oct 1999 12:40:41 -0400
From: Scott Bambrough <scottb@netwinder.org>
Organization: Rebel.com
X-Mailer: Mozilla 4.7 [en] (Win95; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Francois Desloges <fd@vipswitch.com>
Cc: linux-arm@vger.rutgers.edu
Subject: Re: BIOS initialization questions
References: <99102710074905.04182@dual> <99102710505806.04182@dual>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Francois Desloges wrote:

> OK! I've just fallen on the ARM Procedure Call Standard (APCS) from the ARM
> Software Developement Toolkit Reference Guide. Is that what is used in the
> BIOS & ARM-Linux project?

This is what the compiler (GCC) follows when generating code.

Scott
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Wed Oct 27 19:12:53 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id TAA24130
	for <linux-arm-archive@lists.arm.linux.org.uk>; Wed, 27 Oct 1999 19:12:52 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 14F8D14097; Wed, 27 Oct 1999 20:02:51 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157440AbPJ0Rpd>;
	Wed, 27 Oct 1999 13:45:33 -0400
Received: by vger.rutgers.edu id <S157347AbPJ0Rgf>;
	Wed, 27 Oct 1999 13:36:35 -0400
Received: from calliope1.fm.intel.com ([132.233.247.10]:2452 "EHLO
        calliope1.fm.intel.com") by vger.rutgers.edu with ESMTP
	id <S160025AbPJ0Raa> convert rfc822-to-8bit; Wed, 27 Oct 1999 13:30:30 -0400
Received: from fmsmsx17.intel.com (fmsmsx17.fm.intel.com [132.233.58.209])
	by calliope1.fm.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.10 1999/10/20 18:19:05 spurcell Exp $) with ESMTP id KAA00587
	for <linux-arm@vger.rutgers.edu>; Wed, 27 Oct 1999 10:30:13 -0700 (PDT)
Received: by fmsmsx17.fm.intel.com with Internet Mail Service (5.5.2448.0)
	id <VJQSZMYJ>; Wed, 27 Oct 1999 10:30:13 -0700
Message-ID: <F55E82FBFFFBD111AC3E00A0C9B8DB7002D315DC@hdsmsx32.hd.intel.com>
From: "Chagas, Jason" <jason.chagas@intel.com>
To: "'linux-arm@vger.rutgers.edu'" <linux-arm@vger.rutgers.edu>
Cc: "Chagas, Jason" <jason.chagas@intel.com>
Subject: Free* boards!!
Date:   Wed, 27 Oct 1999 10:30:07 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8BIT
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Attention ARM-Linux enthusiasts!!

The StrongARM Product Line group
(http://developer.intel.com/design/strong/index.htm
<http://developer.intel.com/design/strong/index.htm>  ) is considering
giving away a few SA1110 boards to ARM-Linux developers.

The StrongARM PL group is expected to soon make available a new reference
design. This development board is _currently_ (and internally) code-named
"Assabet".

These are some of its main features:

*	Up to 32MB socketed fast page mode Intel ® StrataFlash(tm) memory
*	Up to 64MB 100MHz SDRAM
*	Un-buffered main memory interface allows highest possible SDRAM
memory bandwidth
*	Small form factor 3.5" x 5" x 0.5" (same size as the Philips Nino*)
*	UCB1300 codec supports microphone, speaker, POTS line soft modem DAA
connections and touch screen
*	UDA1341 stereo codec supports high quality 16 bit stereo audio
record and playback
*	Infrared interface for IrDA data links up to 4Mb
*	Battery powered, using high efficiency DC-DC converters and a single
Lithium ion (Li-ion) cell
*	Smart battery technology development platform and reference design
when used with smart battery packs
*	Integrated 3.9" reflective color TFT LCD and touch screen
*	Optional 8" color passive LCD for use with GFX companion chip
*	Two expansion headers for the SA-1111 development board, the
graphics accelerator board, or other boards
*	Built in mini speaker and two microphones
*	Built in quiet alert vibration motor
*	One type II Compact Flash socket (available only when the SA-1111
development and graphics accelerator boards are not present)
*	USB slave port for PC synchronization and battery trickle charge
*	RF module interface connector for CDMA, GSM and Bluetooth modules up
to 4 Watts


The SA1110 development board also comes with a the companion SA-1111
development board that has the following main features:

*	Expansion Flash bank. Up to 32MB socketed fast page mode StrataFlash
memory
*	Expansion SDRAM bank (up to 64MB 50MHz SDRAM)
*	Supports UDA1341 stereo codec for high quality 16 bit stereo audio
record and playback
*	Supports AC97 stereo codec for high quality 16 bit stereo audio
record and playback
*	Built in microphone
*	One type II PCMCIA socket
*	One type II Compact Flash socket
*	USB host port
*	Two PS2 ports
*	Logic analyzer pods
*	32 LEDs to display program debug data


Please let me know if you would like to be one of the very few people to get
a free* SA board by sending me e-mail (jason.chagas@intel.com). Tell us
about yourself and how you are planning to help ARM-Linux to run well on
this device, drivers you will write, cool projects/applications, maintain
patches, etc. Note our decision will be subjective.

Regards,

Jason

*Shipping/handling costs may(or may not) apply.
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Wed Oct 27 19:17:20 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id TAA24252
	for <linux-arm-archive@lists.arm.linux.org.uk>; Wed, 27 Oct 1999 19:17:19 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id DF3D3141BB; Wed, 27 Oct 1999 20:11:33 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157262AbPJ0SKn>;
	Wed, 27 Oct 1999 14:10:43 -0400
Received: by vger.rutgers.edu id <S157379AbPJ0Ryv>;
	Wed, 27 Oct 1999 13:54:51 -0400
Received: from netwinder.org ([207.245.35.202]:6714 "EHLO www.netwinder.org")
	by vger.rutgers.edu with ESMTP id <S157629AbPJ0RvZ>;
	Wed, 27 Oct 1999 13:51:25 -0400
Received: from gw.rebel.com (gate.rebel.com [207.245.35.200])
	by www.netwinder.org (8.8.7/8.8.7) with SMTP id NAA10762
	for <linux-arm@vger.rutgers.edu>; Wed, 27 Oct 1999 13:51:23 -0400
Message-ID: <38173AC6.33E0A946@netwinder.org>
Received: from dhcp111.isa.ott.rebel.com by gw.rebel.com
          via smtpd (for netwinder.org [207.245.35.202]) with SMTP; 27 Oct 1999 17:51:21 UT
Date:   Wed, 27 Oct 1999 13:47:50 -0400
From: Scott Bambrough <scottb@netwinder.org>
Organization: Rebel.com
X-Mailer: Mozilla 4.7 [en] (Win95; I)
X-Accept-Language: en
MIME-Version: 1.0
Cc: linux-arm@vger.rutgers.edu
Subject: Re: BIOS initialization questions
References: <99102710074905.04182@dual>  <99102710505806.04182@dual> <E11gW9Y-0003Dh-00@fountain.nexus.co.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: unlisted-recipients: ; (no To-header on input)
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Philip Blundell wrote:
> 
> The APCS per se is somewhat outdated now; the latest procedure call standard
> is the ATPCS.  GCC does not currently have full support for ATPCS, though.
> 
GCC doesn't support all variants of the APCS either.

Scott
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Wed Oct 27 19:39:12 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id TAA24718
	for <linux-arm-archive@lists.arm.linux.org.uk>; Wed, 27 Oct 1999 19:39:11 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id B8EEA141D9; Wed, 27 Oct 1999 20:35:41 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157319AbPJ0SW4>;
	Wed, 27 Oct 1999 14:22:56 -0400
Received: by vger.rutgers.edu id <S157413AbPJ0SDF>;
	Wed, 27 Oct 1999 14:03:05 -0400
Received: from netwinder.org ([207.245.35.202]:6420 "EHLO www.netwinder.org")
	by vger.rutgers.edu with ESMTP id <S157419AbPJ0Rsj>;
	Wed, 27 Oct 1999 13:48:39 -0400
Received: from gw.rebel.com (gate.rebel.com [207.245.35.200])
	by www.netwinder.org (8.8.7/8.8.7) with SMTP id NAA10703;
	Wed, 27 Oct 1999 13:48:08 -0400
Message-ID: <38173A04.BAE85F96@netwinder.org>
Received: from dhcp111.isa.ott.rebel.com by gw.rebel.com
          via smtpd (for netwinder.org [207.245.35.202]) with SMTP; 27 Oct 1999 17:48:06 UT
Date:   Wed, 27 Oct 1999 13:44:36 -0400
From: Scott Bambrough <scottb@netwinder.org>
Organization: Rebel.com
X-Mailer: Mozilla 4.7 [en] (Win95; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Philip Blundell <pb@nexus.co.uk>
Cc: mestery@visi.com, linux-arm@vger.rutgers.edu
Subject: Re: Versioning in the latest netwinder image
References: <Pine.GSO.4.10.9910271054130.27254-100000@isis.visi.com> <E11gW5E-0003Cx-00@fountain.nexus.co.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Philip Blundell wrote:
> 
> >Why are the libraries compiled without versioning?
> 
> Historical reasons.  When the NetWinder guys started out, the ARM tools didn't
> support versioning properly.  Although Jim Pick later fixed this and it's now
> fine, the NetWinder images kept using --disable-versioning to maintain binary
> compatibility with the systems that were in the field.
> 
> The Titan and Debian distributions both use versioned libraries.

I hope to make the next disk image versioned.  There has been a lot of
resistance to going versioned due to deadlines.  The amount of work is
immense; it requires rebuilding everything against the versioned
libraries.  Build 15 gets everything into RPM format, there is now no
software installed that isn't in RPM form.

I expect we will turn on versioning, and switch to the newest binutils
at the same time.

> >And, can I fix this by continuing to use dm-3.0.15 and just
> >recompiling glibc?
>
 
No. If you install versioned libs on build 15, nothing will run. 
Nothing.  You would be better off rebuilding your app on build 15.  

Scott
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Wed Oct 27 19:53:40 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id TAA25081
	for <linux-arm-archive@lists.arm.linux.org.uk>; Wed, 27 Oct 1999 19:53:40 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id C7E19141E4; Wed, 27 Oct 1999 20:44:56 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157395AbPJ0Sfv>;
	Wed, 27 Oct 1999 14:35:51 -0400
Received: by vger.rutgers.edu id <S157405AbPJ0SXg>;
	Wed, 27 Oct 1999 14:23:36 -0400
Received: from tazenda.demon.co.uk ([158.152.220.239]:1501 "EHLO
        kings-cross.london.uk.eu.org") by vger.rutgers.edu with ESMTP
	id <S157570AbPJ0SH2>; Wed, 27 Oct 1999 14:07:28 -0400
Received: from localhost
	([127.0.0.1] helo=kings-cross.london.uk.eu.org ident=phil)
	by kings-cross.london.uk.eu.org with esmtp (Exim 2.05 #1)
	id 11gXTW-0004qf-00; Wed, 27 Oct 1999 19:07:06 +0100
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: Benjamin Herrenschmidt <benh@mipsys.com>
Cc: Francois Desloges <fd@vipswitch.com>, linux-arm@vger.rutgers.edu
Subject: Re: BIOS initialization questions 
In-Reply-To: Message from Benjamin Herrenschmidt <benh@mipsys.com> 
   of "Wed, 27 Oct 1999 18:33:44 +0200." <19991027183344.021398@mailhost.mipsys.com> 
References: <19991027183344.021398@mailhost.mipsys.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date:   Wed, 27 Oct 1999 19:07:06 +0100
From: Philip Blundell <Philip.Blundell@pobox.com>
Message-Id: <E11gXTW-0004qf-00@kings-cross.london.uk.eu.org>
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

>I beleive this could be improved by using linker tricks to have the
>linker store this size in a place where the code can fetch it via
>pc-relative access, but I don't know ld well enough to write such a script.

Actually (assuming I've understood correctly) something like this would 
stand a good chance:

int sizeof_data()
{
  extern void __data_start, __data_end;
  return &__data_end - &__data_start;
}

I think the linker already defines __data_end (though it might be called 
_edata or some such) but I'm less sure about __data_start.  It would be 
trivial to add though.

p.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Wed Oct 27 20:02:32 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id UAA25346
	for <linux-arm-archive@lists.arm.linux.org.uk>; Wed, 27 Oct 1999 20:02:32 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id BB94C141EE; Wed, 27 Oct 1999 20:49:05 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157457AbPJ0Slg>;
	Wed, 27 Oct 1999 14:41:36 -0400
Received: by vger.rutgers.edu id <S157199AbPJ0S2q>;
	Wed, 27 Oct 1999 14:28:46 -0400
Received: from kauket.visi.com ([209.98.98.22]:50773 "HELO mail-out.visi.com")
	by vger.rutgers.edu with SMTP id <S157676AbPJ0STv>;
	Wed, 27 Oct 1999 14:19:51 -0400
Received: from isis.visi.com (isis.visi.com [209.98.98.8])
	by mail-out.visi.com (Postfix) with ESMTP
	id 99F253864; Wed, 27 Oct 1999 13:19:23 -0500 (CDT)
Received: from localhost (mestery@localhost)
	by isis.visi.com (8.8.8/8.8.8) with ESMTP id NAA07043;
	Wed, 27 Oct 1999 13:19:23 -0500 (CDT)
X-Authentication-Warning: isis.visi.com: mestery owned process doing -bs
Date:   Wed, 27 Oct 1999 13:19:23 -0500 (CDT)
From: <mestery@visi.com>
To: Philip Blundell <pb@nexus.co.uk>
Cc: linux-arm@vger.rutgers.edu
Subject: Re: Versioning in the latest netwinder image 
In-Reply-To: <E11gW5E-0003Cx-00@fountain.nexus.co.uk>
Message-ID: <Pine.GSO.4.10.9910271318170.6936-100000@isis.visi.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Hi,

On Wed, 27 Oct 1999, Philip Blundell wrote:

> Historical reasons.  When the NetWinder guys started out, the ARM tools didn't
> support versioning properly.  Although Jim Pick later fixed this and it's now
> fine, the NetWinder images kept using --disable-versioning to maintain binary
> compatibility with the systems that were in the field.
> 
This makes sense.

> The Titan and Debian distributions both use versioned libraries.
> 
Okay, I just looked, and there's a newer Debian distribution I'll try
out.  Thanks for the answers.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Wed Oct 27 20:16:41 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id UAA25713
	for <linux-arm-archive@lists.arm.linux.org.uk>; Wed, 27 Oct 1999 20:16:40 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 49B20140BA; Wed, 27 Oct 1999 21:09:50 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157451AbPJ0TEJ>;
	Wed, 27 Oct 1999 15:04:09 -0400
Received: by vger.rutgers.edu id <S157262AbPJ0S5R>;
	Wed, 27 Oct 1999 14:57:17 -0400
Received: from mail.cis.fu-berlin.de ([160.45.11.138]:19010 "EHLO
        Mail.CIS.FU-Berlin.DE") by vger.rutgers.edu with ESMTP
	id <S157290AbPJ0Sxn>; Wed, 27 Oct 1999 14:53:43 -0400
Received: by Mail.CIS.FU-Berlin.DE (Smail3.2.0.98)
	  from Python.CIS.FU-Berlin.DE (160.45.11.158) with esmtp
	  id <m11gYCM-018TqRC>; Wed, 27 Oct 1999 20:53:26 +0200 (MEST)
Received: by Python.CIS.FU-Berlin.DE (Smail3.2.0.98)
	  id <m11gYCL-00BsgaC>; Wed, 27 Oct 1999 20:53:25 +0200 (MEST)
Date:   Wed, 27 Oct 1999 20:53:25 +0200
From: Philipp Grau <phgrau@ZEDAT.FU-Berlin.DE>
To: linux-arm@vger.rutgers.edu
Subject: Re: Versioning in the latest netwinder image
Message-ID: <19991027205325.C115535@CIS.FU-Berlin.DE>
Mail-Followup-To: linux-arm@vger.rutgers.edu
References: <Pine.GSO.4.10.9910271054130.27254-100000@isis.visi.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <Pine.GSO.4.10.9910271054130.27254-100000@isis.visi.com>; from mestery@visi.com on Wed, Oct 27, 1999 at 10:56:40AM -0500
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

On Wed, Oct 27, 1999 at 10:56:40AM -0500, mestery@visi.com wrote:
> (dm-3.0-15-public4.tar.gz), and the libraries appear to have been
> compiled without versioning.  When I try and run some of my code that I
> had been using with my previous distribution (the debian one), the code
> doesn't run and complains as follows:

Why not recompile your programs/code?

Regards

Philipp

-- 
 Philipp Grau               | Freie Universitaet Berlin 
 phgrau@zedat.fu-berlin.de  | Zentraleinrichtung fuer Datenverarbeitung
    We had joy, we had fun, | we had Pacman on the sun...      
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Wed Oct 27 20:44:48 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id UAA26366
	for <linux-arm-archive@lists.arm.linux.org.uk>; Wed, 27 Oct 1999 20:44:47 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id AE99914043; Wed, 27 Oct 1999 21:42:52 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157170AbPJ0TmW>;
	Wed, 27 Oct 1999 15:42:22 -0400
Received: by vger.rutgers.edu id <S157167AbPJ0TmO>;
	Wed, 27 Oct 1999 15:42:14 -0400
Received: from kauket.visi.com ([209.98.98.22]:59048 "HELO mail-out.visi.com")
	by vger.rutgers.edu with SMTP id <S157160AbPJ0Tl7>;
	Wed, 27 Oct 1999 15:41:59 -0400
Received: from isis.visi.com (isis.visi.com [209.98.98.8])
	by mail-out.visi.com (Postfix) with ESMTP
	id B2BB33700; Wed, 27 Oct 1999 14:41:58 -0500 (CDT)
Received: from localhost (mestery@localhost)
	by isis.visi.com (8.8.8/8.8.8) with ESMTP id OAA12277;
	Wed, 27 Oct 1999 14:41:58 -0500 (CDT)
X-Authentication-Warning: isis.visi.com: mestery owned process doing -bs
Date:   Wed, 27 Oct 1999 14:41:58 -0500 (CDT)
From: <mestery@visi.com>
To: Philipp Grau <phgrau@ZEDAT.FU-Berlin.DE>
Cc: linux-arm@vger.rutgers.edu
Subject: Re: Versioning in the latest netwinder image
In-Reply-To: <19991027205325.C115535@CIS.FU-Berlin.DE>
Message-ID: <Pine.GSO.4.10.9910271441230.12227-100000@isis.visi.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Hi,

On Wed, 27 Oct 1999, Philipp Grau wrote:

> On Wed, Oct 27, 1999 at 10:56:40AM -0500, mestery@visi.com wrote:
> > (dm-3.0-15-public4.tar.gz), and the libraries appear to have been
> > compiled without versioning.  When I try and run some of my code that I
> > had been using with my previous distribution (the debian one), the code
> > doesn't run and complains as follows:
> 
> Why not recompile your programs/code?
> 
Because I am cross-compiling all of my code from a Solaris box, and I
don't want to have to rebuild a non-versioned glibc for this purpose.

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Wed Oct 27 22:05:44 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id WAA28589
	for <linux-arm-archive@lists.arm.linux.org.uk>; Wed, 27 Oct 1999 22:05:43 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 57CB313DF0; Wed, 27 Oct 1999 23:00:55 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157187AbPJ0VAZ>;
	Wed, 27 Oct 1999 17:00:25 -0400
Received: by vger.rutgers.edu id <S157170AbPJ0VAQ>;
	Wed, 27 Oct 1999 17:00:16 -0400
Received: from tazenda.demon.co.uk ([158.152.220.239]:1568 "EHLO
        kings-cross.london.uk.eu.org") by vger.rutgers.edu with ESMTP
	id <S157186AbPJ0VAE>; Wed, 27 Oct 1999 17:00:04 -0400
Received: from localhost
	([127.0.0.1] helo=kings-cross.london.uk.eu.org ident=phil)
	by kings-cross.london.uk.eu.org with esmtp (Exim 2.05 #1)
	id 11gaA0-00053i-00; Wed, 27 Oct 1999 21:59:08 +0100
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: mestery@visi.com
Cc: Philipp Grau <phgrau@ZEDAT.FU-Berlin.DE>, linux-arm@vger.rutgers.edu
Subject: Re: Versioning in the latest netwinder image 
In-Reply-To: Message from <mestery@visi.com> 
   of "Wed, 27 Oct 1999 14:41:58 CDT." <Pine.GSO.4.10.9910271441230.12227-100000@isis.visi.com> 
References: <Pine.GSO.4.10.9910271441230.12227-100000@isis.visi.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date:   Wed, 27 Oct 1999 21:59:08 +0100
From: Philip Blundell <Philip.Blundell@pobox.com>
Message-Id: <E11gaA0-00053i-00@kings-cross.london.uk.eu.org>
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

>Because I am cross-compiling all of my code from a Solaris box, and I
>don't want to have to rebuild a non-versioned glibc for this purpose.

You could always just copy libc.so from the Netwinder onto your Solaris box.

p.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Wed Oct 27 22:19:23 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id WAA28880
	for <linux-arm-archive@lists.arm.linux.org.uk>; Wed, 27 Oct 1999 22:19:22 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 706BD14099; Wed, 27 Oct 1999 23:13:10 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157228AbPJ0VMl>;
	Wed, 27 Oct 1999 17:12:41 -0400
Received: by vger.rutgers.edu id <S157258AbPJ0VLP>;
	Wed, 27 Oct 1999 17:11:15 -0400
Received: from p15-magpie-gui.tch.enablis.net ([194.168.180.15]:1233 "EHLO
        caramon.arm.linux.org.uk") by vger.rutgers.edu with ESMTP
	id <S157240AbPJ0VKy>; Wed, 27 Oct 1999 17:10:54 -0400
Received: from raistlin.arm.linux.org.uk (linux@raistlin.arm.linux.org.uk [192.168.0.3])
	by caramon.arm.linux.org.uk (8.8.7/8.8.7) with ESMTP id WAA01592;
	Wed, 27 Oct 1999 22:10:06 +0100
From: linux@arm.linux.org.uk
Received: (from linux@localhost) by raistlin.arm.linux.org.uk (8.7.4/8.7.3) id WAA08106; Wed, 27 Oct 1999 22:09:05 +0100
Message-Id: <199910272109.WAA08106@raistlin.arm.linux.org.uk>
Subject: Re: Versioning in the latest netwinder image
To: Philip.Blundell@pobox.com (Philip Blundell)
Date:   Wed, 27 Oct 1999 22:09:05 +0100 (BST)
Cc: mestery@visi.com, phgrau@ZEDAT.FU-Berlin.DE, linux-arm@vger.rutgers.edu
In-Reply-To: <E11gaA0-00053i-00@kings-cross.london.uk.eu.org> from "Philip Blundell" at Oct 27, 99 09:59:08 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Philip Blundell writes:
> >Because I am cross-compiling all of my code from a Solaris box, and I
> >don't want to have to rebuild a non-versioned glibc for this purpose.
> 
> You could always just copy libc.so from the Netwinder onto your Solaris box.

Or build it on the NetWinder.
   _____
  |_____| ------------------------------------------------- ---+---+-
  |   |        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' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Wed Oct 27 22:32:46 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id WAA29271
	for <linux-arm-archive@lists.arm.linux.org.uk>; Wed, 27 Oct 1999 22:32:45 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 5EF4713FBD; Wed, 27 Oct 1999 23:24:09 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157181AbPJ0VXi>;
	Wed, 27 Oct 1999 17:23:38 -0400
Received: by vger.rutgers.edu id <S157164AbPJ0VXa>;
	Wed, 27 Oct 1999 17:23:30 -0400
Received: from netwinder.org ([207.245.35.202]:14402 "EHLO www.netwinder.org")
	by vger.rutgers.edu with ESMTP id <S157317AbPJ0VWY>;
	Wed, 27 Oct 1999 17:22:24 -0400
Received: from gw.rebel.com (gate.rebel.com [207.245.35.200])
	by www.netwinder.org (8.8.7/8.8.7) with SMTP id RAA22885
	for <linux-arm@vger.rutgers.edu>; Wed, 27 Oct 1999 17:22:22 -0400
Message-ID: <38176C3A.7731E044@netwinder.org>
Received: from dhcp111.isa.ott.rebel.com by gw.rebel.com
          via smtpd (for netwinder.org [207.245.35.202]) with SMTP; 27 Oct 1999 21:22:20 UT
Date:   Wed, 27 Oct 1999 17:18:50 -0400
From: Scott Bambrough <scottb@netwinder.org>
Organization: Rebel.com
X-Mailer: Mozilla 4.7 [en] (Win95; I)
X-Accept-Language: en
MIME-Version: 1.0
To: linux-arm@vger.rutgers.edu
Subject: Re: Versioning in the latest netwinder image
References: <Pine.GSO.4.10.9910271441230.12227-100000@isis.visi.com> <E11gaA0-00053i-00@kings-cross.london.uk.eu.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Philip Blundell wrote:
>
> You could always just copy libc.so from the Netwinder onto your Solaris box.
> 

libc.so is just a text file.  You would have to copy /lib/libc-2.1.2.so
and /usr/lib/libc_nonshared.a as well.  This doesn't help with any other
libraries you might have compiled against the versioned libs.  They
would have to be relinked as well.

Scott
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Wed Oct 27 22:45:03 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id WAA29658
	for <linux-arm-archive@lists.arm.linux.org.uk>; Wed, 27 Oct 1999 22:45:03 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id DC41A13FCE; Wed, 27 Oct 1999 23:40:06 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157417AbPJ0Vfy>;
	Wed, 27 Oct 1999 17:35:54 -0400
Received: by vger.rutgers.edu id <S157334AbPJ0Vfc>;
	Wed, 27 Oct 1999 17:35:32 -0400
Received: from tazenda.demon.co.uk ([158.152.220.239]:1615 "EHLO
        kings-cross.london.uk.eu.org") by vger.rutgers.edu with ESMTP
	id <S157333AbPJ0VbE>; Wed, 27 Oct 1999 17:31:04 -0400
Received: from localhost
	([127.0.0.1] helo=kings-cross.london.uk.eu.org ident=phil)
	by kings-cross.london.uk.eu.org with esmtp (Exim 2.05 #1)
	id 11gaem-0005Be-00; Wed, 27 Oct 1999 22:30:56 +0100
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: Scott Bambrough <scottb@netwinder.org>
Cc: linux-arm@vger.rutgers.edu
Subject: Re: Versioning in the latest netwinder image 
In-Reply-To: Message from Scott Bambrough <scottb@netwinder.org> 
   of "Wed, 27 Oct 1999 17:18:50 EDT." <38176C3A.7731E044@netwinder.org> 
References: <Pine.GSO.4.10.9910271441230.12227-100000@isis.visi.com> <E11gaA0-00053i-00@kings-cross.london.uk.eu.org>  <38176C3A.7731E044@netwinder.org> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date:   Wed, 27 Oct 1999 22:30:56 +0100
From: Philip Blundell <Philip.Blundell@pobox.com>
Message-Id: <E11gaem-0005Be-00@kings-cross.london.uk.eu.org>
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Scott Bambrough wrote:
>Philip Blundell wrote:
>> You could always just copy libc.so from the Netwinder onto your Solaris box.
>
>libc.so is just a text file.  You would have to copy /lib/libc-2.1.2.so
>and /usr/lib/libc_nonshared.a as well.

In fact static libraries don't (can't) contain versioning information, so 
libc_nonshared.a is probably the same.  But otherwise yes, you're quite 
right.

p.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Wed Oct 27 23:17:14 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id XAA30876
	for <linux-arm-archive@lists.arm.linux.org.uk>; Wed, 27 Oct 1999 23:17:13 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 05FCD14102; Thu, 28 Oct 1999 00:09:26 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157291AbPJ0WJF>;
	Wed, 27 Oct 1999 18:09:05 -0400
Received: by vger.rutgers.edu id <S157226AbPJ0WI5>;
	Wed, 27 Oct 1999 18:08:57 -0400
Received: from sparkle.Generation.NET ([205.205.119.4]:34379 "EHLO
        sparkle.Generation.NET") by vger.rutgers.edu with ESMTP
	id <S157155AbPJ0WIw>; Wed, 27 Oct 1999 18:08:52 -0400
Received: from dual (generic253.197.205.205.IN-ADDR.ARPA [205.205.197.253] (may be forged))
	by sparkle.Generation.NET (8.9.3/8.9.3) with SMTP id SAA16010
	for <linux-arm@vger.rutgers.edu>; Wed, 27 Oct 1999 18:09:08 -0400 (EDT)
From: Francois Desloges <fd@vipswitch.com>
To: linux-arm@vger.rutgers.edu
Subject: BIOS errors
Date:   Wed, 27 Oct 1999 17:54:06 -0400
Content-Type: text/plain
MIME-Version: 1.0
Message-Id: <99102718062108.04182@dual>
Content-Transfer-Encoding: 8bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

OK with a Logic Analyser plugged on the EBSA, we discovered that the PLB
is not in agrement whit the checksum we add in our home made FMU header
generator. We suspect that we might have problem with the last bytes of the
images in FLASH (we assumed unwritten FLASH bytes were at 0xFF values).

Indeed, both the bios and bios.elf images have sizes that are not word aligned,
due to sections that are not word aligned themselves:

>[root@dual bios]# arm-linux-objdump -h bios.elf
> 
>bios.elf:     file format elf32-littlearm
> 
>Sections:
>Idx Name          Size      VMA       LMA       File off  Algn
>   0 .text         00006b9f  410c00c0  410c00c0  00000350  2**2
>                  CONTENTS, ALLOC, LOAD, CODE
>  1 .data         000002c4  00001000  00001000  00000080  2**2
>                  CONTENTS, ALLOC, LOAD, DATA
>  2 .glue_7t      00000000  000012c4  000012c4  00000344  2**2
>                  CONTENTS, ALLOC, LOAD, DATA
>  3 .glue_7       00000000  000012c4  000012c4  00000344  2**2
>                  CONTENTS, ALLOC, LOAD, DATA
>  4 .bss          000013e0  000012d0  000012d0  00000350  2**4
>                  ALLOC
>  5 .comment      00000390  000026b0  000026b0  00006eef  2**0
>                  CONTENTS, READONLY  

I feel especially suspicioud about a .text section of size 6b9f!
Isn't this supposed to be code always aligned?
(I may be totally wrong here i'm not familiar with these sections stuff)

Anybody has an idea?

-- 
François Desloges
fd@vipswitch.com
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Wed Oct 27 23:30:49 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id XAA31224
	for <linux-arm-archive@lists.arm.linux.org.uk>; Wed, 27 Oct 1999 23:30:48 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id CAD3814174; Thu, 28 Oct 1999 00:24:59 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157265AbPJ0WY2>;
	Wed, 27 Oct 1999 18:24:28 -0400
Received: by vger.rutgers.edu id <S157170AbPJ0WYW>;
	Wed, 27 Oct 1999 18:24:22 -0400
Received: from sparkle.Generation.NET ([205.205.119.4]:34837 "EHLO
        sparkle.Generation.NET") by vger.rutgers.edu with ESMTP
	id <S157199AbPJ0WX3>; Wed, 27 Oct 1999 18:23:29 -0400
Received: from dual (generic253.197.205.205.IN-ADDR.ARPA [205.205.197.253] (may be forged))
	by sparkle.Generation.NET (8.9.3/8.9.3) with SMTP id SAA19555
	for <linux-arm@vger.rutgers.edu>; Wed, 27 Oct 1999 18:23:33 -0400 (EDT)
From: Francois Desloges <fd@vipswitch.com>
To: linux-arm@vger.rutgers.edu
Subject: Fwd: BIOS errors
Date:   Wed, 27 Oct 1999 18:09:04 -0400
Content-Type: text/plain
MIME-Version: 1.0
Message-Id: <99102718205809.04182@dual>
Content-Transfer-Encoding: 8bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Oh and by the way along with my prior mail:

>[root@dual bios]# arm-linux-objdump -h bios.elf
> 
>bios.elf:     file format elf32-littlearm
> 
>Sections:
>Idx Name          Size      VMA       LMA       File off  Algn
>   0 .text         00006b9f  410c00c0  410c00c0  00000350  2**2
>                  CONTENTS, ALLOC, LOAD, CODE
>  1 .data         000002c4  00001000  00001000  00000080  2**2
>                  CONTENTS, ALLOC, LOAD, DATA
>  2 .glue_7t      00000000  000012c4  000012c4  00000344  2**2
>                  CONTENTS, ALLOC, LOAD, DATA
>  3 .glue_7       00000000  000012c4  000012c4  00000344  2**2
>                  CONTENTS, ALLOC, LOAD, DATA
>  4 .bss          000013e0  000012d0  000012d0  00000350  2**4
>                  ALLOC
>  5 .comment      00000390  000026b0  000026b0  00006eef  2**0
>                  CONTENTS, READONLY  

The disassembly give me something like this for the end of the .text section:

>410c6c54:	69732070 	ldmvsdb	r3!, {r4, r5, r6, sp}^
>410c6c58:	2520657a 	strcs	r6, [r0, -#1402]!
>410c6c5c:	Address 0x410c6c5c is out of bounds.
>
>Disassembly of section .data:
>
>00001000 <cmdline>:

And of course,  0x410c00c0 + 0x6b9f = 0x410c6c5f
Although I don't know what what a "File off" of 350 is suppose to mean here for
the .text section.



-- 
François Desloges
fd@vipswitch.com
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Thu Oct 28 00:00:44 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id AAA31983
	for <linux-arm-archive@lists.arm.linux.org.uk>; Thu, 28 Oct 1999 00:00:44 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 0672613FFB; Thu, 28 Oct 1999 00:49:43 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157297AbPJ0WtN>;
	Wed, 27 Oct 1999 18:49:13 -0400
Received: by vger.rutgers.edu id <S157181AbPJ0WtF>;
	Wed, 27 Oct 1999 18:49:05 -0400
Received: from p15-magpie-gui.tch.enablis.net ([194.168.180.15]:1570 "EHLO
        caramon.arm.linux.org.uk") by vger.rutgers.edu with ESMTP
	id <S157179AbPJ0Wsq>; Wed, 27 Oct 1999 18:48:46 -0400
Received: from raistlin.arm.linux.org.uk (linux@raistlin.arm.linux.org.uk [192.168.0.3])
	by caramon.arm.linux.org.uk (8.8.7/8.8.7) with ESMTP id XAA01893;
	Wed, 27 Oct 1999 23:48:33 +0100
From: linux@arm.linux.org.uk
Received: (from linux@localhost) by raistlin.arm.linux.org.uk (8.7.4/8.7.3) id XAA08434; Wed, 27 Oct 1999 23:47:32 +0100
Message-Id: <199910272247.XAA08434@raistlin.arm.linux.org.uk>
Subject: Re: BIOS errors
To: fd@vipswitch.com (Francois Desloges)
Date:   Wed, 27 Oct 1999 23:47:31 +0100 (BST)
Cc: linux-arm@vger.rutgers.edu
In-Reply-To: <99102718062108.04182@dual> from "Francois Desloges" at Oct 27, 99 05:54:06 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Francois Desloges writes:
> I feel especially suspicioud about a .text section of size 6b9f!
> Isn't this supposed to be code always aligned?
> (I may be totally wrong here i'm not familiar with these sections stuff)

The alignment is appled before the objects it refers to, not after.  This
means that the size of the text section may not be word aligned if there
is a string or similar structure at the end of the text section.
   _____
  |_____| ------------------------------------------------- ---+---+-
  |   |        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' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Thu Oct 28 00:04:16 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id AAA32001
	for <linux-arm-archive@lists.arm.linux.org.uk>; Thu, 28 Oct 1999 00:04:15 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 94807140CD; Thu, 28 Oct 1999 00:51:34 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157224AbPJ0WvE>;
	Wed, 27 Oct 1999 18:51:04 -0400
Received: by vger.rutgers.edu id <S157210AbPJ0Wup>;
	Wed, 27 Oct 1999 18:50:45 -0400
Received: from p15-magpie-gui.tch.enablis.net ([194.168.180.15]:1573 "EHLO
        caramon.arm.linux.org.uk") by vger.rutgers.edu with ESMTP
	id <S157181AbPJ0Wuk>; Wed, 27 Oct 1999 18:50:40 -0400
Received: from raistlin.arm.linux.org.uk (linux@raistlin.arm.linux.org.uk [192.168.0.3])
	by caramon.arm.linux.org.uk (8.8.7/8.8.7) with ESMTP id XAA01903;
	Wed, 27 Oct 1999 23:50:27 +0100
From: linux@arm.linux.org.uk
Received: (from linux@localhost) by raistlin.arm.linux.org.uk (8.7.4/8.7.3) id XAA08447; Wed, 27 Oct 1999 23:49:26 +0100
Message-Id: <199910272249.XAA08447@raistlin.arm.linux.org.uk>
Subject: Re: Fwd: BIOS errors
To: fd@vipswitch.com (Francois Desloges)
Date:   Wed, 27 Oct 1999 23:49:25 +0100 (BST)
Cc: linux-arm@vger.rutgers.edu
In-Reply-To: <99102718205809.04182@dual> from "Francois Desloges" at Oct 27, 99 06:09:04 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Francois Desloges writes:
> >410c6c54:	69732070 	ldmvsdb	r3!, {r4, r5, r6, sp}^
> >410c6c58:	2520657a 	strcs	r6, [r0, -#1402]!
> >410c6c5c:	Address 0x410c6c5c is out of bounds.

Yep, it's a string. "p size%"

> And of course,  0x410c00c0 + 0x6b9f = 0x410c6c5f
> Although I don't know what what a "File off" of 350 is suppose to mean here for
> the .text section.

File off is the offset of the data into the ELF file.
   _____
  |_____| ------------------------------------------------- ---+---+-
  |   |        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' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Thu Oct 28 00:39:57 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id AAA00378
	for <linux-arm-archive@lists.arm.linux.org.uk>; Thu, 28 Oct 1999 00:39:52 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 8997A140D7; Thu, 28 Oct 1999 01:33:09 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157219AbPJ0XcZ>;
	Wed, 27 Oct 1999 19:32:25 -0400
Received: by vger.rutgers.edu id <S157275AbPJ0XcD>;
	Wed, 27 Oct 1999 19:32:03 -0400
Received: from nexus.carleton.ca ([134.117.76.10]:4774 "EHLO nexus.carleton.ca")
	by vger.rutgers.edu with ESMTP id <S157343AbPJ0X2q>;
	Wed, 27 Oct 1999 19:28:46 -0400
Received: from localhost (stewart@localhost)
	by nexus.carleton.ca (8.9.3/8.9.3) with ESMTP id TAA23575;
	Wed, 27 Oct 1999 19:28:02 -0400
Date:   Wed, 27 Oct 1999 19:28:02 -0400 (EDT)
From: Rod Stewart <stewart@nexus.carleton.ca>
To: mestery@visi.com
Cc: linux-arm@vger.rutgers.edu
Subject: Re: Versioning in the latest netwinder image 
In-Reply-To: <Pine.GSO.4.10.9910271318170.6936-100000@isis.visi.com>
Message-ID: <Pine.LNX.4.10.9910271906490.22544-100000@nexus.carleton.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing


On Wed, 27 Oct 1999 mestery@visi.com wrote:
> On Wed, 27 Oct 1999, Philip Blundell wrote:
> 
> > The Titan and Debian distributions both use versioned libraries.
> > 
> Okay, I just looked, and there's a newer Debian distribution I'll try
> out.  Thanks for the answers.

If you're willing to wait til Sunday, I'm putting up the next release of
Titan (release VI) in the afternoon.  I'm starting the final rebuild
tonight, which takes about 3.3 days for a complete build.

Titan VI is based off Red Hat 6.0 with all security updates applied
(excluding the XFree86 updates).  It has a few other items updated, namely
GCC 2.95.1, glibc 2.1.2, binutils 2.9.5.0.14.  Completely rpm based, and
has always had versioned glibc.

Titan VI will be available from (on Sunday Oct. 31):
	ftp://ftp.nw.carleton.ca/winder/titanVI/
The last pre release is at:
	ftp://ftp.nw.carleton.ca/new/pre3_titanVI/

-Rms

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Thu Oct 28 13:07:48 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id NAA27520
	for <linux-arm-archive@lists.arm.linux.org.uk>; Thu, 28 Oct 1999 13:07:47 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id DC7F513F38; Thu, 28 Oct 1999 14:06:48 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157483AbPJ1MGL>;
	Thu, 28 Oct 1999 08:06:11 -0400
Received: by vger.rutgers.edu id <S157476AbPJ1MEu>;
	Thu, 28 Oct 1999 08:04:50 -0400
Received: from kauket.visi.com ([209.98.98.22]:53833 "HELO mail-out.visi.com")
	by vger.rutgers.edu with SMTP id <S157445AbPJ1Lzd>;
	Thu, 28 Oct 1999 07:55:33 -0400
Received: from isis.visi.com (isis.visi.com [209.98.98.8])
	by mail-out.visi.com (Postfix) with ESMTP
	id DFA8F37E7; Thu, 28 Oct 1999 06:55:31 -0500 (CDT)
Received: from localhost (mestery@localhost)
	by isis.visi.com (8.8.8/8.8.8) with ESMTP id GAA08250;
	Thu, 28 Oct 1999 06:55:31 -0500 (CDT)
X-Authentication-Warning: isis.visi.com: mestery owned process doing -bs
Date:   Thu, 28 Oct 1999 06:55:31 -0500 (CDT)
From: <mestery@visi.com>
To: Rod Stewart <stewart@nexus.carleton.ca>
Cc: linux-arm@vger.rutgers.edu
Subject: Re: Versioning in the latest netwinder image 
In-Reply-To: <Pine.LNX.4.10.9910271906490.22544-100000@nexus.carleton.ca>
Message-ID: <Pine.GSO.4.10.9910280653210.7805-100000@isis.visi.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Hi,

On Wed, 27 Oct 1999, Rod Stewart wrote:

> If you're willing to wait til Sunday, I'm putting up the next release of
> Titan (release VI) in the afternoon.  I'm starting the final rebuild
> tonight, which takes about 3.3 days for a complete build.
> 
I can wait and give that a try this weekend.  I'll play around with the
new Debian distro for now.  Thanks.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Thu Oct 28 18:06:57 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id SAA03667
	for <linux-arm-archive@lists.arm.linux.org.uk>; Thu, 28 Oct 1999 18:06:56 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 99C9214151; Thu, 28 Oct 1999 19:01:11 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S160052AbPJ1Q6i>;
	Thu, 28 Oct 1999 12:58:38 -0400
Received: by vger.rutgers.edu id <S157591AbPJ1Q5P>;
	Thu, 28 Oct 1999 12:57:15 -0400
Received: from mta3.snfc21.pbi.net ([206.13.28.141]:38082 "EHLO
        mta3.snfc21.pbi.net") by vger.rutgers.edu with ESMTP
	id <S159990AbPJ1Qxm>; Thu, 28 Oct 1999 12:53:42 -0400
Received: from java ([216.101.151.82])
 by mta3.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8)
 with SMTP id <0FKB00NBFO8E3G@mta3.snfc21.pbi.net> for
 linux-arm@vger.rutgers.edu; Thu, 28 Oct 1999 09:53:10 -0700 (PDT)
Date:   Thu, 28 Oct 1999 10:02:02 -0700
From: Dave Borja <dave_bb@pacbell.net>
Subject: browsing on brutus
To: linux-arm <linux-arm@vger.rutgers.edu>
Message-id: <07af01bf2166$2cf3a8d0$529765d8@java>
MIME-version: 1.0
X-Mailer: Microsoft Outlook Express 4.72.3110.5
Content-type: text/plain; charset="iso-8859-1"
Content-transfer-encoding: 7bit
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
X-Priority: 3
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Has anyone gotten a web browser (e.g. lynx) to
work on the brutus? The lcd should support at
least a line oriented browser functionality and 
connect to the outside world via ppp and the serial 
port.
  Thanks,
 Dave Borja

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Thu Oct 28 19:18:00 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id TAA06751
	for <linux-arm-archive@lists.arm.linux.org.uk>; Thu, 28 Oct 1999 19:18:00 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id CA10113E9B; Thu, 28 Oct 1999 20:16:41 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157591AbPJ1SMv>;
	Thu, 28 Oct 1999 14:12:51 -0400
Received: by vger.rutgers.edu id <S157333AbPJ1SMS>;
	Thu, 28 Oct 1999 14:12:18 -0400
Received: from modemcable233.137-200-24.mtl.mc.videotron.net ([24.200.137.233]:62271
        "EHLO xanadu.gn.com") by vger.rutgers.edu with ESMTP
	id <S157639AbPJ1SLx>; Thu, 28 Oct 1999 14:11:53 -0400
Received: from localhost (nico@localhost)
	by xanadu.gn.com (8.9.3/8.9.3) with ESMTP id OAA02303;
	Thu, 28 Oct 1999 14:12:08 -0400
X-Authentication-Warning: xanadu.gn.com: nico owned process doing -bs
Date:   Thu, 28 Oct 1999 14:12:08 -0400 (EDT)
From: Nicolas Pitre <nico@cam.org>
X-Sender: nico@xanadu.gn.com
To: Dave Borja <dave_bb@pacbell.net>
Cc: linux-arm <linux-arm@vger.rutgers.edu>
Subject: Re: browsing on brutus
In-Reply-To: <07af01bf2166$2cf3a8d0$529765d8@java>
Message-ID: <Pine.LNX.4.10.9910281408580.2299-100000@xanadu.gn.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing



On Thu, 28 Oct 1999, Dave Borja wrote:

> Has anyone gotten a web browser (e.g. lynx) to
> work on the brutus? The lcd should support at
> least a line oriented browser functionality and 
> connect to the outside world via ppp and the serial 
> port.

I never got that far with the Brutus but there isn't any reason why it
couldn't work.  Some people already had PPP running over the serial port,
and lynx runs happily on my test board with local files.



Nicolas

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Fri Oct 29 17:56:47 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id RAA26630
	for <linux-arm-archive@lists.arm.linux.org.uk>; Fri, 29 Oct 1999 17:56:47 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id CB63013E85; Fri, 29 Oct 1999 18:56:45 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157507AbPJ2O6v>;
	Fri, 29 Oct 1999 10:58:51 -0400
Received: by vger.rutgers.edu id <S157543AbPJ2O6g>;
	Fri, 29 Oct 1999 10:58:36 -0400
Received: from fwsrv2.itt.com ([151.190.254.230]:4995 "HELO fwsrv2.itt.com")
	by vger.rutgers.edu with SMTP id <S157611AbPJ2OfO>;
	Fri, 29 Oct 1999 10:35:14 -0400
Received: by fwsrv2.itt.com; (5.65v4.0/1.3/10May95) id AA23125; Fri, 29 Oct 1999 09:35:11 -0500
Received: by fwemail2.de.ittind.com with Internet Mail Service (5.5.2448.0)
	id <VVZ1DN7S>; Fri, 29 Oct 1999 09:35:09 -0500
Message-Id: <CBB2C281DA4DD3119ECE00A0C9EBCEB0066C2A@acdnjmail1.acdnj.itt.com>
From: "Latham, Steve" <SLatham@acdnj.itt.com>
To: linux-arm@vger.rutgers.edu
Subject: Throw a Newbie a bone - How Can I interface to the FPE?
Date:   Fri, 29 Oct 1999 09:35:08 -0500
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@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

I using a netwinder with linux 2.2.12 and gcc 2.95 -
How do I interface with the FPE to get floats? Is there a compiler switch?

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Fri Oct 29 18:58:54 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id SAA28549
	for <linux-arm-archive@lists.arm.linux.org.uk>; Fri, 29 Oct 1999 18:58:53 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 834D313E75; Fri, 29 Oct 1999 19:58:52 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S160185AbPJ2R6N>;
	Fri, 29 Oct 1999 13:58:13 -0400
Received: by vger.rutgers.edu id <S160233AbPJ2RLw>;
	Fri, 29 Oct 1999 13:11:52 -0400
Received: from sparkle.Generation.NET ([205.205.119.4]:47800 "EHLO
        sparkle.Generation.NET") by vger.rutgers.edu with ESMTP
	id <S160929AbPJ2P5l>; Fri, 29 Oct 1999 11:57:41 -0400
Received: from dual (generic253.197.205.205.IN-ADDR.ARPA [205.205.197.253] (may be forged))
	by sparkle.Generation.NET (8.9.3/8.9.3) with SMTP id LAA24109;
	Fri, 29 Oct 1999 11:57:42 -0400 (EDT)
From: Francois Desloges <fd@vipswitch.com>
To: Benjamin Herrenschmidt <benh@mipsys.com>
Subject: Re: BIOS initialization questions
Date:   Fri, 29 Oct 1999 09:54:37 -0400
Content-Type: text/plain
References: <19991027183344.021398@mailhost.mipsys.com>
In-Reply-To: <19991027183344.021398@mailhost.mipsys.com>
Cc: linux-arm@vger.rutgers.edu
MIME-Version: 1.0
Message-Id: <9910291155080E.04182@dual>
Content-Transfer-Encoding: 8bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

On Wed, 27 Oct 1999, Benjamin Herrenschmidt wrote:
> I beleive this could be improved by using linker tricks to have the
> linker store this size in a place where the code can fetch it via
> pc-relative access, but I don't know ld well enough to write such a script.

Excuse me for the delay, I just read the ld documentation last night.
(http://www.gnu.org/manual/ld-2.9.1/html_mono/ld.html)

Hey the elfbios.lds script is already there, almost good!

There are errors in it however:
>SECTIONS
>{
>  _text = .;			/* Text and read-only data      */
>  .text : {
>        *(.text)
>        *(.fixup)
>        *(.gnu.warning)
>        *(.rodata)
>  }
>  _etext = .;			/* End of text section          */
>
>  _data = .;
>  .data : {			/* Data                         */
>        *(.data)
>        }
>
>  _edata = .;			/* End of data section          */
>
>  _bss_start = .;		/* BSS                          */
>  .bss : {
>        *(.bss)
>        }
>  _end = . ;
>}

_text and _data (_etext and _edata as well for aesthetic reasons) should
be _inside_ .text et .data sections definitions because .text et .data value
are forced by Makefile variables TEXTADDR and DATAADDR.
So right now _text is 0,
.text is forced by Makefile to 0x41000C0 (providing I use bank 0), 
_etext= 0x4100xxxx
Therefore _etext - _text = 4100xxxx instead of xxxx.

Same thing with _data = 0x4100xxxx , 
.data is force by Makefile to 0x1000
_edata 0x1xxx and
_edata - data = BEFFxxxx
A really Bad Thing! 

We can even calculate the size value at link time by creating new symbols like
_sz_data = _edata - _data;
or even
_sz_data = SIZEOF(.data)
which are equivalent.

I therefore propose the corrected following  elfbios.lds:
>SECTIONS
>{
> 			/* Text and read-only data      */
>  .text : {
>        _text = .;
>        *(.text)
>        *(.fixup)
>        *(.gnu.warning)
>        *(.rodata)
>         _etext = .;	/* End of text section          */
>  }
>  _sz_text = SIZEOF(.text) ;
>
>  _data = .;
>  .data : {			/* Data                         */
>        *(.data)
>        }
>
>  _edata = .;			/* End of data section          */
> _sz_data = SIZEOF(.data) ;
>
>  		/* BSS                          */
>  .bss : {
>       _bss_start = .;  
>      *(.bss)
>       _end = . ;
>        }
>  _sz_bss = SIZEOF(.bss)
>}

What do we think?
-- 
François Desloges
fd@vipswitch.com
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Fri Oct 29 21:10:34 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id VAA31966
	for <linux-arm-archive@lists.arm.linux.org.uk>; Fri, 29 Oct 1999 21:10:34 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 3D79713DB7; Fri, 29 Oct 1999 22:10:31 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S157202AbPJ2TNS>;
	Fri, 29 Oct 1999 15:13:18 -0400
Received: by vger.rutgers.edu id <S157445AbPJ2RtR>;
	Fri, 29 Oct 1999 13:49:17 -0400
Received: from sparkle.Generation.NET ([205.205.119.4]:50665 "EHLO
        sparkle.Generation.NET") by vger.rutgers.edu with ESMTP
	id <S160993AbPJ2RAl>; Fri, 29 Oct 1999 13:00:41 -0400
Received: from dual (generic253.197.205.205.IN-ADDR.ARPA [205.205.197.253] (may be forged))
	by sparkle.Generation.NET (8.9.3/8.9.3) with SMTP id NAA13363;
	Fri, 29 Oct 1999 13:00:47 -0400 (EDT)
From: Francois Desloges <fd@vipswitch.com>
To: linux-arm@vger.rutgers.edu
Subject: BIOS-1.05 mkaif.c Error?
Date:   Fri, 29 Oct 1999 12:48:31 -0400
Content-Type: text/plain
Cc: benh@mipsys.com
MIME-Version: 1.0
Message-Id: <9910291258150F.04182@dual>
Content-Transfer-Encoding: 8bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Here is some code from mkaif.c from BIOS-1.05:

>aifhdr.decomp_code      = SWAP32(0xe1a00000);   /* nop */
>aifhdr.reloc_code          = SWAP32(0xe1a00000);   /* nop*/
>aifhdr.init_code             = SWAP32(0xe1a00000);   /* nop*/
>aifhdr.entry_code          = SWAP32(0xeb00001b);   /* bl entry */ 	
>aifhdr.exit_code            = SWAP32(0xeafffffe);
>aifhdr.text_size  = p_head[text_phead].p_memsz; /* Mem size since
>						 we append stuffs */
>aifhdr.data_size = p_head[data_phead].p_memsz;	/* Mem size (excludes bss) */ 
>aifhdr.bss_size 	= SWAP32(SWAP32(p_head[data_phead].p_memsz) -        
>                         SWAP32(p_head[data_phead].p_filesz));
>aifhdr.image_base = SWAP32(SWAP32(p_head[text_phead].p_vaddr) - 128);

Although I know almost _nothing_ about ELF format, I highly suspect there's a
Cut-&-Paste error here:
>aifhdr.data_size = p_head[data_phead].p_memsz; /* Mem size (excludes bss) */ 

Shouldn't it indeed be:
>aifhdr.data_size = p_head[data_phead].p_filesz; /* Mem size (excludes bss) */ 

?
-- 
François Desloges
fd@vipswitch.com
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Fri Oct 29 21:11:30 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id VAA31973
	for <linux-arm-archive@lists.arm.linux.org.uk>; Fri, 29 Oct 1999 21:11:24 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 1DFAD13DDC; Fri, 29 Oct 1999 22:11:23 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S153960AbPJ2TkB>;
	Fri, 29 Oct 1999 15:40:01 -0400
Received: by vger.rutgers.edu id <S157234AbPJ2SUH>;
	Fri, 29 Oct 1999 14:20:07 -0400
Received: from p16-robin-gui.tch.enablis.net ([194.168.180.76]:3486 "EHLO
        caramon.arm.linux.org.uk") by vger.rutgers.edu with ESMTP
	id <S160660AbPJ2RWt>; Fri, 29 Oct 1999 13:22:49 -0400
Received: from flint.arm.linux.org.uk (root@flint [192.168.0.4])
	by caramon.arm.linux.org.uk (8.8.7/8.8.7) with ESMTP id SAA11211
	for <linux-arm@vger.rutgers.edu>; Fri, 29 Oct 1999 18:22:47 +0100
Received: (from linux@localhost)
	by flint.arm.linux.org.uk (8.8.7/8.8.7) id SAA14070
	for linux-arm@vger.rutgers.edu; Fri, 29 Oct 1999 18:21:38 +0100
From: Russell King - ARM Linux Admin <linux@arm.linux.org.uk>
Message-Id: <199910291721.SAA14070@flint.arm.linux.org.uk>
Subject: Re: Throw a Newbie a bone - How Can I interface to the FPE?
To: SLatham@acdnj.itt.com (Latham Steve)
Date:   Fri, 29 Oct 1999 18:13:35 +0100 (BST)
Cc: linux-arm@vger.rutgers.edu
In-Reply-To: <CBB2C281DA4DD3119ECE00A0C9EBCEB0066C2A@acdnjmail1.acdnj.itt.com> from "Latham, Steve" at Oct 29, 99 09:35:08 am
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Latham, Steve writes:
> I using a netwinder with linux 2.2.12 and gcc 2.95 -
> How do I interface with the FPE to get floats? Is there a compiler switch?

You don't.  The FPE is an emulator, which emulates the floating point
instructions.  Therefore a program containing floating point code will
work without any extra linking or compiler switches.
   _____
  |_____| ------------------------------------------------- ---+---+-
  |   |        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' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Fri Oct 29 21:11:46 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id VAA31980
	for <linux-arm-archive@lists.arm.linux.org.uk>; Fri, 29 Oct 1999 21:11:45 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 92C9F13DF9; Fri, 29 Oct 1999 22:11:44 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S153979AbPJ2TkD>;
	Fri, 29 Oct 1999 15:40:03 -0400
Received: by vger.rutgers.edu id <S157214AbPJ2SLO>;
	Fri, 29 Oct 1999 14:11:14 -0400
Received: from tazenda.demon.co.uk ([158.152.220.239]:1063 "EHLO
        kings-cross.london.uk.eu.org") by vger.rutgers.edu with ESMTP
	id <S157178AbPJ2RTS>; Fri, 29 Oct 1999 13:19:18 -0400
Received: from localhost
	([127.0.0.1] helo=kings-cross.london.uk.eu.org ident=phil)
	by kings-cross.london.uk.eu.org with esmtp (Exim 2.05 #1)
	id 11hFfm-0000GZ-00; Fri, 29 Oct 1999 18:18:42 +0100
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: "Latham, Steve" <SLatham@acdnj.itt.com>
Cc: linux-arm@vger.rutgers.edu
Subject: Re: Throw a Newbie a bone - How Can I interface to the FPE? 
In-Reply-To: Message from "Latham, Steve" <SLatham@acdnj.itt.com> 
   of "Fri, 29 Oct 1999 09:35:08 CDT." <CBB2C281DA4DD3119ECE00A0C9EBCEB0066C2A@acdnjmail1.acdnj.itt.com> 
References: <CBB2C281DA4DD3119ECE00A0C9EBCEB0066C2A@acdnjmail1.acdnj.itt.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date:   Fri, 29 Oct 1999 18:18:42 +0100
From: Philip Blundell <Philip.Blundell@pobox.com>
Message-Id: <E11hFfm-0000GZ-00@kings-cross.london.uk.eu.org>
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

>I using a netwinder with linux 2.2.12 and gcc 2.95 -
>How do I interface with the FPE to get floats? Is there a compiler switch?

What do you mean by `interface to the FPE'?  If you just write your code as 
normal the FPE will automatically pick up on floating point operations.

p.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Fri Oct 29 22:41:08 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id WAA02216
	for <linux-arm-archive@lists.arm.linux.org.uk>; Fri, 29 Oct 1999 22:41:08 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 4A27113DB4; Fri, 29 Oct 1999 23:41:07 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S154137AbPJ2VJI>;
	Fri, 29 Oct 1999 17:09:08 -0400
Received: by vger.rutgers.edu id <S154348AbPJ2UdY>;
	Fri, 29 Oct 1999 16:33:24 -0400
Received: from [208.193.202.3] ([208.193.202.3]:34481 "HELO
        fw-losgatos.losgatos.arm.com") by vger.rutgers.edu with SMTP
	id <S154345AbPJ2Uc6>; Fri, 29 Oct 1999 16:32:58 -0400
Received: by fw-losgatos.losgatos.arm.com; id NAA24171; Fri, 29 Oct 1999 13:33:19 -0700
Received: from unknown(194.202.50.2) by fw-losgatos.losgatos.arm.com via smap (V5.0)
	id xma024162; Fri, 29 Oct 99 13:32:39 -0700
Received: from pobox.com (dhcp47 [194.202.50.238])
	by incsun1.losgatos.arm.com (8.9.1a/8.9.1) with ESMTP id NAA11385
	for <linux-arm@vger.rutgers.edu>; Fri, 29 Oct 1999 13:30:02 -0700 (PDT)
Message-ID: <3819E6F1.721CCC55@pobox.com>
Date:   Fri, 29 Oct 1999 13:26:57 -0500
From: Ian Field <ianfield@pobox.com>
X-Mailer: Mozilla 4.51 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: linux-arm@vger.rutgers.edu
Subject: Re: Throw a Newbie a bone - How Can I interface to the FPE?
References: <CBB2C281DA4DD3119ECE00A0C9EBCEB0066C2A@acdnjmail1.acdnj.itt.com> <E11hFfm-0000GZ-00@kings-cross.london.uk.eu.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

> >I using a netwinder with linux 2.2.12 and gcc 2.95 -
> >How do I interface with the FPE to get floats? Is there a compiler switch?
>
> What do you mean by `interface to the FPE'?  If you just write your code as
> normal the FPE will automatically pick up on floating point operations.

what kind of performance differences would someone see with say, mpg123 or
xamp, if you just compiled it and caught the floating point instructions with
exceptions, versus compiling with floating point emulation from the start?

Cheers, IAN



unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Fri Oct 29 23:28:40 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id XAA04446
	for <linux-arm-archive@lists.arm.linux.org.uk>; Fri, 29 Oct 1999 23:28:40 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id CB46E13DA7; Sat, 30 Oct 1999 00:28:38 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S154467AbPJ2VWn>;
	Fri, 29 Oct 1999 17:22:43 -0400
Received: by vger.rutgers.edu id <S154057AbPJ2Upy>;
	Fri, 29 Oct 1999 16:45:54 -0400
Received: from littleblue.ftech.net ([195.200.12.27]:7785 "EHLO
        relay5.ftech.net") by vger.rutgers.edu with ESMTP
	id <S153865AbPJ2Tmh>; Fri, 29 Oct 1999 15:42:37 -0400
Received: from ibm9.ftech.net ([212.32.16.79] helo=prunus.localnet)
	by relay5.ftech.net with smtp (Exim 3.03-ftechp4 #4)
	id 11hGVA-0006C5-00
	for linux-arm@vger.rutgers.edu; Fri, 29 Oct 1999 19:11:48 +0100
From: Toby Bryans <toby@navaho.co.uk>
Date:   Fri, 29 Oct 1999 19:13:54 BST
To: linux-arm@vger.rutgers.edu
Subject: Re: 2.0.36 to 2.2.12
Content-Type: text/plain
Message-ID: <Navaho-2.3.18-941220834.110000@an4group.com>
X-Mailer: Navaho Server Suite v2.3.18 [Linux/i486]
X-User-Agent: Mozilla/4.7 [en] (X11; I; Linux 2.2.12-20 i686)
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Many thanks for your kind replies.  They have been stored to think about,
however, we have decided to wait a while until we can get other risc
architectures that we can port a certain piece of software to at the
same time.  So, there isn't as much of a hurry as originally thought.

On Wed, 27 Oct, Wookey  wrote:
> Not yet - see previous replies for details, but Aleph One are working on
> tidying up the existing stuff to make a reasonably painless distribution
> for RISCOS machines. Once we've got something working and documented
> we'll get it more up to date. This should provide what you are looking
> for, but it'll be a while yet before we have a 2.2 kernel release with
> toochain so it depends how much of a hurry you are in...

It really depends on your definition on "a while yet" :-).  The plan at
the moment is to keep up to date with the developments on this list,
lurk for a while longer, and then see what the state of affairs is like
when we have Alpha and SPARC boxes to play with as well as the RPC.

Once again, thanks for your replies.

Yours,

Toby Bryans

-- 
Project Manager, Navaho Internet Ltd       http://www.navaho.co.uk/
CTO, Cygnet Computer Solutions Ltd & Chairman, Empire Retailing Ltd
Technical Support, an4 group Ltd         'Phone: +44 (0)7970 422053
http://homepages.tcp.co.uk/~elesoc/         Fax: +44 (0)7970 127058


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sat Oct 30 03:14:13 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id DAA10157
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sat, 30 Oct 1999 03:14:13 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 8CE7713D87; Sat, 30 Oct 1999 04:14:10 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S154463AbPJ3B5i>;
	Fri, 29 Oct 1999 21:57:38 -0400
Received: by vger.rutgers.edu id <S153891AbPJ2V7c>;
	Fri, 29 Oct 1999 17:59:32 -0400
Received: from fwsrv2.itt.com ([151.190.254.230]:2406 "HELO fwsrv2.itt.com")
	by vger.rutgers.edu with SMTP id <S153984AbPJ2Vai>;
	Fri, 29 Oct 1999 17:30:38 -0400
Received: by fwsrv2.itt.com; (5.65v4.0/1.3/10May95) id AA10290; Fri, 29 Oct 1999 16:30:37 -0500
Received: by fwemail2.de.ittind.com with Internet Mail Service (5.5.2448.0)
	id <VVZ1D49H>; Fri, 29 Oct 1999 16:30:35 -0500
Message-Id: <CBB2C281DA4DD3119ECE00A0C9EBCEB0066C2C@acdnjmail1.acdnj.itt.com>
From: "Latham, Steve" <SLatham@acdnj.itt.com>
To: "'Philip Blundell'" <Philip.Blundell@pobox.com>
Cc: "'linux-arm@vger.rutgers.edu'" <linux-arm@vger.rutgers.edu>
Subject: RE: Throw a Newbie a bone - How Can I interface to the FPE? 
Date:   Fri, 29 Oct 1999 16:30:34 -0500
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@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Thanks I had originally tried compiling the omniORB without defining NO
FLOAT using an older version of linux and gcc and it had failed on
definitions of floats and doubles. So I had made some lingering assumptions
after it compilied with NO FLOAT defined. I just tried a small test program
and DOH! you're right no problem now. So, I'll retry the omniORB. Thanks
again to all.

-----Original Message-----
From: Philip Blundell [mailto:Philip.Blundell@pobox.com]
Sent: Friday, October 29, 1999 1:19 PM
To: Latham, Steve
Cc: linux-arm@vger.rutgers.edu
Subject: Re: Throw a Newbie a bone - How Can I interface to the FPE? 


>I using a netwinder with linux 2.2.12 and gcc 2.95 -
>How do I interface with the FPE to get floats? Is there a compiler switch?

What do you mean by `interface to the FPE'?  If you just write your code as 
normal the FPE will automatically pick up on floating point operations.

p.


unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sat Oct 30 03:14:40 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id DAA10163
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sat, 30 Oct 1999 03:14:40 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 112E113D88; Sat, 30 Oct 1999 04:14:39 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S154466AbPJ3B5j>;
	Fri, 29 Oct 1999 21:57:39 -0400
Received: by vger.rutgers.edu id <S154986AbPJ2VgQ>;
	Fri, 29 Oct 1999 17:36:16 -0400
Received: from sparkle.Generation.NET ([205.205.119.4]:61407 "EHLO
        sparkle.Generation.NET") by vger.rutgers.edu with ESMTP
	id <S154369AbPJ2Ug5>; Fri, 29 Oct 1999 16:36:57 -0400
Received: from dual (generic253.197.205.205.IN-ADDR.ARPA [205.205.197.253] (may be forged))
	by sparkle.Generation.NET (8.9.3/8.9.3) with SMTP id QAA22127
	for <linux-arm@vger.rutgers.edu>; Fri, 29 Oct 1999 16:37:07 -0400 (EDT)
From: Francois Desloges <fd@vipswitch.com>
To: linux-arm@vger.rutgers.edu
Subject: Re: BIOS initialization questions
Date:   Fri, 29 Oct 1999 16:16:30 -0400
Content-Type: text/plain
References: <19991027183344.021398@mailhost.mipsys.com> <9910291155080E.04182@dual>
In-Reply-To: <9910291155080E.04182@dual>
MIME-Version: 1.0
Message-Id: <9910291634340J.04182@dual>
Content-Transfer-Encoding: 8bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Sorry I did a mistake myself:
The appropriate elfbios.lds SECTIONS part should read as:
>SECTIONS
>{
> 			/* Text and read-only data      */
>  .text : {
>        _text = .;
>        *(.text)
>        *(.fixup)
>        *(.gnu.warning)
>        *(.rodata)
>         _etext = .;	/* End of text section          */
>  }
>  _sz_text = SIZEOF(.text) ;
>
>  .data : {                        /* Data                         */
>         _data = .;
>        *(.data)
>         _edata = .;             /* End of data section          */  
>      }
> _sz_data = SIZEOF(.data) ;
>
>  		/* BSS                          */
>  .bss : {
>       _bss_start = .;  
>      *(.bss)
>       _end = . ;
>        }
>  _sz_bss = SIZEOF(.bss)
>}

and the crt0.S associated code should read as:

>/*
> * Copy .data section in RAM
> */	
>	mov	r1, #0x1000
>	ldr	r2, =SYMBOL_NAME(_data)
>	ldr	r3, =SYMBOL_NAME(_sz_data)
>1:	ldr	r0, [r2], #4
>	str	r0, [r1], #4
>	subs	r3, r3, #4
>	bgt	1b

And we can get rid of the two lines at the entry defining sp:
_entry:
/*
 *Choose supervisor mode and disable IRQ & IFQ interrupts
 */
	mrs	r0, cpsr
	bic	r0, r0, #0x1f
	orr	r0, r0, #0xd3
	msr	cpsr, r0
...

Am I totally wrong here?

-- 
François Desloges
fd@vipswitch.com
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sat Oct 30 03:15:42 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id DAA10278
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sat, 30 Oct 1999 03:15:41 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 9AB6013D89; Sat, 30 Oct 1999 04:15:40 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S154470AbPJ3B5l>;
	Fri, 29 Oct 1999 21:57:41 -0400
Received: by vger.rutgers.edu id <S153680AbPJ2V6a>;
	Fri, 29 Oct 1999 17:58:30 -0400
Received: from mta3.snfc21.pbi.net ([206.13.28.141]:46781 "EHLO
        mta3.snfc21.pbi.net") by vger.rutgers.edu with ESMTP
	id <S153890AbPJ2VKw>; Fri, 29 Oct 1999 17:10:52 -0400
Received: from java ([216.101.151.82])
 by mta3.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8)
 with SMTP id <0FKD00BP5M8FTP@mta3.snfc21.pbi.net> for
 linux-arm@vger.rutgers.edu; Fri, 29 Oct 1999 11:05:04 -0700 (PDT)
Date:   Fri, 29 Oct 1999 11:14:03 -0700
From: Dave Borja <dave_bb@pacbell.net>
Subject: Got angleboot to work
To: linux-arm <linux-arm@vger.rutgers.edu>
Message-id: <00b401bf2239$618e9e00$529765d8@java>
MIME-version: 1.0
X-Mailer: Microsoft Outlook Express 4.72.3110.5
Content-type: text/plain; charset="iso-8859-1"
Content-transfer-encoding: 7bit
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
X-Priority: 3
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

I posted a while ago about angleboot problems with our
ebsa110 type board. Turns out I was able to get it to work
by cutting down the size of the data packet sent for the image
download. This was hardcoded at 2016. Cutting it in half gets
the download to work. 

Getting things to boot is another matter. I compiled a kernel
(based on 2.2.12) with  arm and brutus/sa1100 patches. Tried
building with the ebsa110 option and with minimal support (basically
just the serial ports, ram disk as initd, etc). We plunk this down
into base address 0x8000 and put the ram disk up there in 0x00100000.
Since we only have 8mb of memory and the ram disk is a little over 6mb
uncompressed, things are tight. 
   Dave Borja

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sat Oct 30 03:40:35 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id DAA10868
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sat, 30 Oct 1999 03:40:34 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 6BCF813DBF; Sat, 30 Oct 1999 04:40:33 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S154277AbPJ3CNV>;
	Fri, 29 Oct 1999 22:13:21 -0400
Received: by vger.rutgers.edu id <S154198AbPJ3CLT>;
	Fri, 29 Oct 1999 22:11:19 -0400
Received: from [208.193.202.3] ([208.193.202.3]:42636 "HELO
        fw-losgatos.losgatos.arm.com") by vger.rutgers.edu with SMTP
	id <S154361AbPJ3B4h>; Fri, 29 Oct 1999 21:56:37 -0400
Received: by fw-losgatos.losgatos.arm.com; id PAA26030; Fri, 29 Oct 1999 15:28:49 -0700
Received: from unknown(194.202.50.2) by fw-losgatos.losgatos.arm.com via smap (V5.0)
	id xma026019; Fri, 29 Oct 99 15:28:03 -0700
Received: from pobox.com (dhcp47 [194.202.50.238])
	by incsun1.losgatos.arm.com (8.9.1a/8.9.1) with ESMTP id PAA17912
	for <linux-arm@vger.rutgers.edu>; Fri, 29 Oct 1999 15:25:26 -0700 (PDT)
Message-ID: <381A01FE.FB1A61A4@pobox.com>
Date:   Fri, 29 Oct 1999 15:22:22 -0500
From: Ian Field <ianfield@pobox.com>
X-Mailer: Mozilla 4.51 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: linux-arm@vger.rutgers.edu
Subject: Re: Throw a Newbie a bone - How Can I interface to the FPE?
References: <CBB2C281DA4DD3119ECE00A0C9EBCEB0066C2A@acdnjmail1.acdnj.itt.com>
	 <E11hFfm-0000GZ-00@kings-cross.london.uk.eu.org> <3819E6F1.721CCC55@pobox.com> <E11hJvZ-0000Ia-00@kings-cross.london.uk.eu.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

> I don't quite understand the question.

sorry ... I appreciate the response. I meant the kernel nw_float undefined
instruction exception handler.

> If you're asking about the difference between -mhard-float and -msoft-float,
> it's measureable but not staggering.

Thanks, that's what I wanted to know.


Cheers, IAN



unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sat Oct 30 05:13:45 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id FAA13169
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sat, 30 Oct 1999 05:13:44 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id C11F013DA5; Sat, 30 Oct 1999 06:13:43 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S153899AbPJ3EAE>;
	Sat, 30 Oct 1999 00:00:04 -0400
Received: by vger.rutgers.edu id <S154197AbPJ3Dfv>;
	Fri, 29 Oct 1999 23:35:51 -0400
Received: from modemcable233.137-200-24.mtl.mc.videotron.net ([24.200.137.233]:63059
        "EHLO xanadu.gn.com") by vger.rutgers.edu with ESMTP
	id <S154307AbPJ3DFf>; Fri, 29 Oct 1999 23:05:35 -0400
Received: from localhost (nico@localhost)
	by xanadu.gn.com (8.9.3/8.9.3) with ESMTP id XAA01898;
	Fri, 29 Oct 1999 23:05:46 -0400
X-Authentication-Warning: xanadu.gn.com: nico owned process doing -bs
Date:   Fri, 29 Oct 1999 23:05:46 -0400 (EDT)
From: Nicolas Pitre <nico@cam.org>
X-Sender: nico@xanadu.gn.com
To: Ian Field <ianfield@pobox.com>
Cc: linux-arm@vger.rutgers.edu
Subject: Re: Throw a Newbie a bone - How Can I interface to the FPE?
In-Reply-To: <3819E6F1.721CCC55@pobox.com>
Message-ID: <Pine.LNX.4.10.9910292302450.1896-100000@xanadu.gn.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing



On Fri, 29 Oct 1999, Ian Field wrote:

> > >I using a netwinder with linux 2.2.12 and gcc 2.95 -
> > >How do I interface with the FPE to get floats? Is there a compiler switch?
> >
> > What do you mean by `interface to the FPE'?  If you just write your code as
> > normal the FPE will automatically pick up on floating point operations.
> 
> what kind of performance differences would someone see with say, mpg123 or
> xamp, if you just compiled it and caught the floating point instructions with
> exceptions, versus compiling with floating point emulation from the start?

Both won't run real-time anyway.  You need to convert everything to fixed
point math if you need performance.  I have a version of splay on
ftp.netwinder.org/users/n/nico that I converted to fixed point math if
interested.


Nicolas

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sat Oct 30 12:25:36 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id MAA23576
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sat, 30 Oct 1999 12:25:35 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 7441D13DAD; Sat, 30 Oct 1999 13:25:29 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S153957AbPJ3LYc>;
	Sat, 30 Oct 1999 07:24:32 -0400
Received: by vger.rutgers.edu id <S153981AbPJ3LX7>;
	Sat, 30 Oct 1999 07:23:59 -0400
Received: from p10-magpie-gui.tch.enablis.net ([194.168.180.10]:3778 "EHLO
        caramon.arm.linux.org.uk") by vger.rutgers.edu with ESMTP
	id <S153962AbPJ3LWL>; Sat, 30 Oct 1999 07:22:11 -0400
Received: from raistlin.arm.linux.org.uk (linux@raistlin [192.168.0.3])
	by caramon.arm.linux.org.uk (8.8.7/8.8.7) with ESMTP id JAA14104;
	Sat, 30 Oct 1999 09:29:57 +0100
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 JAA19021;
	Sat, 30 Oct 1999 09:28:46 +0100
Message-Id: <199910300828.JAA19021@raistlin.arm.linux.org.uk>
Subject: Re: Got angleboot to work
To: dave_bb@pacbell.net (Dave Borja)
Date:   Sat, 30 Oct 1999 09:28:45 +0100 (BST)
Cc: linux-arm@vger.rutgers.edu
In-Reply-To: <00b401bf2239$618e9e00$529765d8@java> from "Dave Borja" at Oct 29, 99 11:14:03 am
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Dave Borja writes:
> I posted a while ago about angleboot problems with our
> ebsa110 type board. Turns out I was able to get it to work
> by cutting down the size of the data packet sent for the image
> download. This was hardcoded at 2016. Cutting it in half gets
> the download to work. 

This sounds like a problem with something not being able to fragment
packets on ethernet correctly.

> Getting things to boot is another matter. I compiled a kernel
> (based on 2.2.12) with  arm and brutus/sa1100 patches. Tried
> building with the ebsa110 option and with minimal support (basically
> just the serial ports, ram disk as initd, etc). We plunk this down
> into base address 0x8000 and put the ram disk up there in 0x00100000.
> Since we only have 8mb of memory and the ram disk is a little over 6mb
> uncompressed, things are tight. 

I hope you're using either the Image or zImage files?  Also, a 6MB ramdisk
in 8MB isn't really going to leave much room at all for the user-mode.
Do you get any kernel messages from the serial port?  (and you did
specify "console=ttyS0,19200n8" or similar during the build?  Also,
check that r0 and r1 are being passed the correct values.
   _____
  |_____| ------------------------------------------------- ---+---+-
  |   |        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' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sat Oct 30 17:22:34 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id RAA31767
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sat, 30 Oct 1999 17:22:34 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id C314313D95; Sat, 30 Oct 1999 18:22:32 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S153874AbPJ3QWC>;
	Sat, 30 Oct 1999 12:22:02 -0400
Received: by vger.rutgers.edu id <S153872AbPJ3QVm>;
	Sat, 30 Oct 1999 12:21:42 -0400
Received: from note.orchestra.cse.unsw.EDU.AU ([129.94.242.29]:2304 "HELO
        note.orchestra.cse.unsw.EDU.AU") by vger.rutgers.edu with SMTP
	id <S153859AbPJ3QV0>; Sat, 30 Oct 1999 12:21:26 -0400
Received: From paulaner With LocalMail ; Sun, 31 Oct 99 03:20:45 +1100 
From: "Adam 'WeirdArms' Wiggins" <awiggins@cse.unsw.EDU.AU>
To: linux-arm@vger.rutgers.edu
Date:   Sun, 31 Oct 1999 03:20:45 +1100 (EST)
X-Sender: awiggins@paulaner.disy.cse.unsw.EDU.AU
Subject: ARM920 cores
Message-ID: <Pine.OSF.3.95.991031031925.17207A-100000@paulaner.disy.cse.unsw.EDU.AU>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

	Anyone know where to get a cheap machine based on a ARM920 core,
evaluation board or otherwise. Alternatively does anyone know what
companies manufacture ARM920 based processors?

	Cheers Adam

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sat Oct 30 19:11:42 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id TAA03888
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sat, 30 Oct 1999 19:11:42 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id C2D9713DB9; Sat, 30 Oct 1999 20:11:40 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S153897AbPJ3SLL>;
	Sat, 30 Oct 1999 14:11:11 -0400
Received: by vger.rutgers.edu id <S153892AbPJ3SKx>;
	Sat, 30 Oct 1999 14:10:53 -0400
Received: from adsl-63-192-134-89.dsl.snfc21.pacbell.net ([63.192.134.89]:1029
        "EHLO tsuenwan.causality.com") by vger.rutgers.edu with ESMTP
	id <S153966AbPJ3SHl>; Sat, 30 Oct 1999 14:07:41 -0400
Received: from causality.com (localhost [127.0.0.1])
	by tsuenwan.causality.com (8.9.3/8.9.2) with ESMTP id LAA00284;
	Sat, 30 Oct 1999 11:02:23 -0700 (PDT)
	(envelope-from neil@causality.com)
Message-ID: <381B32AF.D0935130@causality.com>
Date:   Sat, 30 Oct 1999 11:02:23 -0700
From: "Neil A. Carson" <neil@causality.com>
Organization: Causality Limited
X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 3.2-RELEASE i386)
X-Accept-Language: en-GB
MIME-Version: 1.0
To: Nicolas Pitre <nico@cam.org>
Cc: Ian Field <ianfield@pobox.com>, linux-arm@vger.rutgers.edu
Subject: Re: Throw a Newbie a bone - How Can I interface to the FPE?
References: <Pine.LNX.4.10.9910292302450.1896-100000@xanadu.gn.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Also, the NetBSD packages collection has a version of mpg123 in fixed
point.

	Neil
unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sat Oct 30 20:28:33 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id UAA05694
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sat, 30 Oct 1999 20:28:33 +0100
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id E545913DF0; Sat, 30 Oct 1999 21:28:31 +0200 (CEST)
Received: by vger.rutgers.edu via listexpand id <S153891AbPJ3T2I>;
	Sat, 30 Oct 1999 15:28:08 -0400
Received: by vger.rutgers.edu id <S153892AbPJ3T1t>;
	Sat, 30 Oct 1999 15:27:49 -0400
Received: from nas01-200.119.thefree.net ([195.34.200.119]:1525 "EHLO
        hyperspace.linuxhacker.org") by vger.rutgers.edu with ESMTP
	id <S153889AbPJ3T1j>; Sat, 30 Oct 1999 15:27:39 -0400
Received: from localhost (alex@localhost [127.0.0.1])
	by hyperspace.linuxhacker.org (8.8.7/8.8.7) with ESMTP id UAA01404;
	Sat, 30 Oct 1999 20:18:53 +0100
Date:   Sat, 30 Oct 1999 20:18:53 +0100 (GMT)
From: Alex Holden <alex@linuxhacker.org>
X-Sender: alex@hyperspace
To: "Adam 'WeirdArms' Wiggins" <awiggins@cse.unsw.EDU.AU>
Cc: linux-arm@vger.rutgers.edu
Subject: Re: ARM920 cores
In-Reply-To: <Pine.OSF.3.95.991031031925.17207A-100000@paulaner.disy.cse.unsw.EDU.AU>
Message-ID: <Pine.LNX.4.04.9910302009040.512-100000@hyperspace>
X-Subliminal-Message: Use Linux!
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

On Sun, 31 Oct 1999, Adam 'WeirdArms' Wiggins wrote:
> 	Anyone know where to get a cheap machine based on a ARM920 core,
> evaluation board or otherwise. Alternatively does anyone know what
> companies manufacture ARM920 based processors?

I haven't heard of any processors being released yet, however NetSilicon's
next device, the NET+150, will have a 920 core in it:
http://www.netsilicon.com/1prod%5Fset/ia/iapresentation/tsld022.htm

They might produce a devel board, if you're prepared to wait a few
months...

--------------- Linux- the choice of a GNU generation. --------------
: Alex Holden (M1CJD)- Caver, Programmer, Land Rover nut, Radio Ham :
-------------------- http://www.linuxhacker.org/ --------------------

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sun Oct 31 03:07:10 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id DAA17510
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sun, 31 Oct 1999 03:07:09 GMT
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 8554C13E06; Sun, 31 Oct 1999 04:07:07 +0100 (CET)
Received: by vger.rutgers.edu via listexpand id <S153944AbPJaDGh>;
	Sat, 30 Oct 1999 23:06:37 -0400
Received: by vger.rutgers.edu id <S153909AbPJaDGU>;
	Sat, 30 Oct 1999 23:06:20 -0400
Received: from [208.176.26.203] ([208.176.26.203]:4197 "EHLO mail.enjoyweb.com")
	by vger.rutgers.edu with ESMTP id <S153897AbPJaDGC>;
	Sat, 30 Oct 1999 23:06:02 -0400
Received: from thinking ([192.168.20.48])
	by mail.enjoyweb.com (8.9.3/8.8.7) with SMTP id UAA02299
	for <linux-arm@vger.rutgers.edu>; Sat, 30 Oct 1999 20:02:14 -0400
Message-ID: <00ef01bf234c$c8464bc0$3014a8c0@enjoyweb>
From: "Yangbin Wang" <y.wang@computer.org>
To: <linux-arm@vger.rutgers.edu>
Subject: Linux kernel images for EBSA-285
Date:   Sat, 30 Oct 1999 20:05:23 -0700
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 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Anyone can kindly point me a pre-built Linux kernel images for EBSA-285
which I can download and run using Angelboot? Thanks.

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sun Oct 31 07:16:36 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id HAA23509
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sun, 31 Oct 1999 07:16:35 GMT
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 9849C13E5E; Sun, 31 Oct 1999 08:16:33 +0100 (CET)
Received: by vger.rutgers.edu via listexpand id <S153889AbPJaHQC>;
	Sun, 31 Oct 1999 02:16:02 -0500
Received: by vger.rutgers.edu id <S153898AbPJaHPe>;
	Sun, 31 Oct 1999 02:15:34 -0500
Received: from [212.219.8.163] ([212.219.8.163]:4885 "HELO inkvine.fluff.org")
	by vger.rutgers.edu with SMTP id <S153890AbPJaHO7>;
	Sun, 31 Oct 1999 02:14:59 -0500
Received: from localhost (localhost [127.0.0.1])
	by inkvine.fluff.org (Postfix) with ESMTP
	id 240D646807; Sun, 31 Oct 1999 07:14:52 +0000 (GMT)
Date:   Sun, 31 Oct 1999 07:14:52 +0000 (GMT)
From: Chris Rutter <chris@fluff.org>
Reply-To: chris@fluff.org
To: Yangbin Wang <y.wang@computer.org>
Cc: linux-arm@vger.rutgers.edu
Subject: Re: Linux kernel images for EBSA-285
In-Reply-To: <00ef01bf234c$c8464bc0$3014a8c0@enjoyweb>
Message-ID: <Pine.LNX.4.10.9910310714230.2007-100000@inkvine.fluff.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

On Sat, 30 Oct 1999, Yangbin Wang wrote:

> Anyone can kindly point me a pre-built Linux kernel images for EBSA-285
> which I can download and run using Angelboot? Thanks.

Er, try ftp.inkvine.fluff.org:/pub/lkab/kernels/

I think the `footbridge' one should work fine.

-- 
Chris <chris@fluff.org>                         ( http://www.fluff.org/chris )

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sun Oct 31 17:17:24 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id RAA05775
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sun, 31 Oct 1999 17:17:23 GMT
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 8C78513E92; Sun, 31 Oct 1999 18:17:22 +0100 (CET)
Received: by vger.rutgers.edu via listexpand id <S154009AbPJaRJF>;
	Sun, 31 Oct 1999 12:09:05 -0500
Received: by vger.rutgers.edu id <S153909AbPJaRIk>;
	Sun, 31 Oct 1999 12:08:40 -0500
Received: from p53-cordelia-gui.tch.enablis.net ([212.250.233.53]:4303 "EHLO
        caramon.arm.linux.org.uk") by vger.rutgers.edu with ESMTP
	id <S154051AbPJaQ5a>; Sun, 31 Oct 1999 11:57:30 -0500
Received: from raistlin.arm.linux.org.uk (linux@raistlin [192.168.0.3])
	by caramon.arm.linux.org.uk (8.8.7/8.8.7) with ESMTP id QAA19628
	for <linux-arm@vger.rutgers.edu>; Sun, 31 Oct 1999 16:57:19 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 QAA28855
	for linux-arm@vger.rutgers.edu; Sun, 31 Oct 1999 16:56:01 GMT
Message-Id: <199910311656.QAA28855@raistlin.arm.linux.org.uk>
Subject: Acorn Community: Reporting Bugs and Other Gripes
To: linux-arm@vger.rutgers.edu
Date:   Sun, 31 Oct 1999 16:56:00 +0000 (GMT)
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

Hi,

After visiting the Acorn Show today and talking to various people, some
interesting points have been raised:

1. Confusion about where problems should be reported.

   In general, the manufacturers of the hardware interfaces for network
   cards, SCSI cards and IDE cards do not maintain the Linux drivers.
   This means that they are not able to help with problems arising from
   using Linux with their hardware.

   ---> For this reason, I ask that people please contact the mailing    <---
   ---> list with problems with the use of these interfaces under Linux, <---
   ---> rather than with the manufacturers directly.                     <---

   In particular, I would be very interested to hear from the person who
   reported the following:

   a) Plain Filecore drive formatted on the motherboard interface, when
      connected to an ICS/APDL IDEFS interface is not able to be used with
      the RISC OS Linux tools.

   b) An ICS/APDL-formatted drive connected to the motherboard also can not
      be used in some way with the RISC OS tools.

   Could they contact me ASAP, so that I know the details of the problem.

2. From time to time, I have been asking a certain well-known magazine
   publisher in the old Acorn market about their interest in Linux.  It
   appears that they do not see ARM Linux as something that is worthy
   of their magazine.  They said that Linux was just "a small minority
   of people making a lot of noise."  Does the ARM Linux (Acorn)
   community have any reaction to that?

   The reaction should take into account whether you think that there
   should be some sort of magazine article about Linux, and if so, who
   should write it up.  I'll say "Not Me" now, before anyone gets any
   ideas. ;)

PS, how should the old "Acorn" community be referred to now?
   _____
  |_____| ------------------------------------------------- ---+---+-
  |   |        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' to majordomo@vger.rutgers.edu

From owner-linux-arm-outgoing@vger.rutgers.edu  Sun Oct 31 17:52:28 1999
Received: from source.rfc822.org (source.rfc822.org [193.189.224.13])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id RAA06617
	for <linux-arm-archive@lists.arm.linux.org.uk>; Sun, 31 Oct 1999 17:52:28 GMT
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
	by source.rfc822.org (Postfix) with ESMTP
	id 7A0A213E7A; Sun, 31 Oct 1999 18:52:26 +0100 (CET)
Received: by vger.rutgers.edu via listexpand id <S154008AbPJaRmL>;
	Sun, 31 Oct 1999 12:42:11 -0500
Received: by vger.rutgers.edu id <S153909AbPJaRli>;
	Sun, 31 Oct 1999 12:41:38 -0500
Received: from nas01-200.240.thefree.net ([195.34.200.240]:1519 "EHLO
        hyperspace.linuxhacker.org") by vger.rutgers.edu with ESMTP
	id <S154066AbPJaRjy>; Sun, 31 Oct 1999 12:39:54 -0500
Received: from localhost (alex@localhost [127.0.0.1])
	by hyperspace.linuxhacker.org (8.8.7/8.8.7) with ESMTP id RAA01085
	for <linux-arm@vger.rutgers.edu>; Sun, 31 Oct 1999 17:31:14 GMT
Date:   Sun, 31 Oct 1999 17:31:14 +0000 (GMT)
From: Alex Holden <alex@linuxhacker.org>
X-Sender: alex@hyperspace
To: linux-arm@vger.rutgers.edu
Subject: Re: Acorn Community: Reporting Bugs and Other Gripes
In-Reply-To: <199910311656.QAA28855@raistlin.arm.linux.org.uk>
Message-ID: <Pine.LNX.4.04.9910311724330.517-100000@hyperspace>
X-Subliminal-Message: Use Linux!
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-arm@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-arm-outgoing

On Sun, 31 Oct 1999, Russell King - ARM Linux Admin wrote:
>    of their magazine.  They said that Linux was just "a small minority
>    of people making a lot of noise."  Does the ARM Linux (Acorn)
>    community have any reaction to that?

_We're_ a minority? ROFL!

--------------- Linux- the choice of a GNU generation. --------------
: Alex Holden (M1CJD)- Caver, Programmer, Land Rover nut, Radio Ham :
-------------------- http://www.linuxhacker.org/ --------------------

unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu