From owner-linux-arm@zen.ics.uwe.ac.uk  Thu May 27 21:01:00 1999
Received: (from majordomo@localhost)
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) id VAA27761
	for linux-arm-outgoing; Thu, 27 May 1999 21:01:00 +0100
Received: from caramon.armlinux.org.uk (root@du-004-0179.freeuk.com [212.126.149.179])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id VAA27755
	for <linux-arm@zen.ics.uwe.ac.uk>; Thu, 27 May 1999 21:00:56 +0100
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 VAA19480
	for <linux-arm@zen.ics.uwe.ac.uk>; Thu, 27 May 1999 21:01:09 +0100
From: Russell King - ARM Linux Admin <linux@arm.linux.org.uk>
Received: (from linux@localhost) by raistlin.armlinux.org.uk (8.7.4/8.7.3) id UAA00725 for linux-arm@zen.ics.uwe.ac.uk; Thu, 27 May 1999 20:59:52 +0100
Message-Id: <199905271959.UAA00725@raistlin.armlinux.org.uk>
Subject: New mailing list
To: linux-arm@zen.ics.uwe.ac.uk
Date: Thu, 27 May 1999 20:59:51 +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@zen.ics.uwe.ac.uk
Precedence: bulk

Hi All,

My postings between the two lists are the wrong way round, but never mind...

There is now a (temporary) linux-arm list set up here, which should
significantly cut down on the time taken for mail to propagate.  I'm
not sure what's up with vger, but from the looks of it, vger's running
very slowly with a light load average.

Anyway, to cut a long story short, the new mailing lists are almost
ready.  HOWEVER:

  Please do not send mail through the new lists yet!  The official
  address will be linux-arm@lists.arm.linux.org.uk, once the DNS
  is sorted.

  Please do not send mail to both vger.rutgers.edu and the new
  linux-arm list - you will mail everyone twice, which will make
  you very unpopular.  This includes when you are responding to
  a mail on either list.

There will be the following lists available here:

  linux-arm		(temporary)
  linux-arm-kernel	(for kernel-only discussions)
  linux-arm-announce	(moderated)

As a special offer (everything new has to include one), you may advance-
subscribe to linux-arm-kernel and linux-arm-announce using the following
address:

  majordomo@zen.ics.uwe.ac.uk

Once the DNS is sorted, all mail should be addressed using
lists.arm.linux.org.uk.  You will be notified when this has happened.

Depending on how zen takes the strain, these lists may become permanent
or be removed.

PS, if you received this posting, then you are subscribed to linux-arm.
   _____
  |_____| ------------------------------------------------- ---+---+-
  |   |        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@lists.arm.linux.org.uk

From owner-linux-arm@zen.ics.uwe.ac.uk  Sat May 29 23:04:21 1999
Received: (from majordomo@localhost)
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) id XAA23087
	for linux-arm-outgoing; Sat, 29 May 1999 23:04:21 +0100
Received: from caramon.armlinux.org.uk (root@du-003-0050.freeuk.com [212.126.148.50])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id XAA23082;
	Sat, 29 May 1999 23:04:17 +0100
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 XAA01174;
	Sat, 29 May 1999 23:03:34 +0100
From: Russell King - ARM Linux Admin <linux@arm.linux.org.uk>
Received: (from linux@localhost) by raistlin.armlinux.org.uk (8.7.4/8.7.3) id XAA03282; Sat, 29 May 1999 23:03:12 +0100
Message-Id: <199905292203.XAA03282@raistlin.armlinux.org.uk>
Subject: Release of new 2.0.36 stuff
To: linux-announce@zen.ics.uwe.ac.uk, linux-arm@zen.ics.uwe.ac.uk
Date: Sat, 29 May 1999 23:03:11 +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@zen.ics.uwe.ac.uk
Precedence: bulk

Hi,

For the moment, I'm going to use both linux-announce and linux-arm for
now, since there's very few people on linux-announce yet.

I've just finished uploading what I hope will be the final 2.0.36
kernel for the RiscPC, along with it's root disks.  Could people please
give me some feedback on this and let me know if it works for them?

Thanks.
   _____
  |_____| ------------------------------------------------- ---+---+-
  |   |        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@lists.arm.linux.org.uk

From owner-linux-arm@zen.ics.uwe.ac.uk  Sun May 30 12:50:26 1999
Received: (from majordomo@localhost)
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) id MAA30751
	for linux-arm-outgoing; Sun, 30 May 1999 12:50:26 +0100
Received: from caramon.armlinux.org.uk (root@du-003-0023.freeuk.com [212.126.148.23])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id MAA30745
	for <linux-arm@zen.ics.uwe.ac.uk>; Sun, 30 May 1999 12:50:22 +0100
Received: from raistlin.armlinux.org.uk (root@raistlin [192.168.0.3])
	by caramon.armlinux.org.uk (8.8.7/8.8.7) with ESMTP id MAA03272;
	Sun, 30 May 1999 12:50:44 +0100
From: Russell King - ARM Linux Admin <linux@arm.linux.org.uk>
Received: (from linux@localhost) by raistlin.armlinux.org.uk (8.7.4/8.7.3) id MAA01167; Sun, 30 May 1999 12:49:07 +0100
Message-Id: <199905301149.MAA01167@raistlin.armlinux.org.uk>
Subject: Re: 2.2.8-rmk on a netwinder
To: sh990154@mail.uni-greifswald.de (Hanske;Stefan)
Date: Sun, 30 May 1999 12:49:06 +0100 (BST)
Cc: mpanetta@realminfo.com, linux-arm@zen.ics.uwe.ac.uk
In-Reply-To: <Pine.GHP.4.02.9905281441220.26784-100000@mail.uni-greifswald.de> from "Hanske;Stefan" at May 28, 99 02:44:28 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@zen.ics.uwe.ac.uk
Precedence: bulk

Hanske;Stefan writes:
> When the monitor goes to suspend mode after some time it can also mean
> that it's unable to sync the current mode. Try to have a look at the
> framebuffer driver you use and try changing the initial screen mode
> parameters.

The NetWinders do a hard reset after loading the kernel, so the VGA
shuts down until the kernel boots.

Unfortunately, like all Linux kernels now, the console is initialised
rather late, so if something goes wrong, you don't get to know about it.
This is a limitation of the way the kernel handles PCI, and it is
unlikely to change.

If you can't get the kernel to boot and suspect that the kernel is
panicing, my suggestion is to drop in my debugging code into
kernel/printk.c (after va_end, add printascii(buf+3);) and
enable low level debugging for the NetWinder.  You should then
get kernel messages out of the serial port.
   _____
  |_____| ------------------------------------------------- ---+---+-
  |   |        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@lists.arm.linux.org.uk

From owner-linux-arm@zen.ics.uwe.ac.uk  Sun May 30 16:09:03 1999
Received: (from majordomo@localhost)
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) id QAA32465
	for linux-arm-outgoing; Sun, 30 May 1999 16:09:03 +0100
Received: from mail.netwave.de (IDENT:root@smaug.netwave.de [194.162.128.45])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id QAA32455
	for <linux-arm@zen.ics.uwe.ac.uk>; Sun, 30 May 1999 16:08:50 +0100
Received: from 195.185.99.152 (root@as-line47.hb.netwave.de [195.185.99.174])
	by mail.netwave.de (8.9.1/8.8.5) with ESMTP id QAA16523
	for <linux-arm@zen.ics.uwe.ac.uk>; Sun, 30 May 1999 16:08:48 +0200
Received: (qmail 3179 invoked by uid 1000); 30 May 1999 15:08:24 -0000
Date: Sun, 30 May 1999 17:08:24 +0200
From: Jan-Uwe Finck <ju_finck@mail.netwave.de>
To: linux-arm@zen.ics.uwe.ac.uk
Subject: Eh0 not running after ftp-install
Message-ID: <19990530170824.A2700@mail.netwave.de>
Reply-To: Jan-Uwe.Finck@bigfoot.de
Mail-Followup-To: linux-arm@zen.ics.uwe.ac.uk
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.4i
Sender: owner-linux-arm@zen.ics.uwe.ac.uk
Precedence: bulk

hi,

after installing my ARM-Linux via ftp using my x86-Linux box as a gateway
I found out that my eth0-card isn't up anymore after rebooting.
/proc/devices doesn't show any sign of a network-card although it is detected 
at bootup.

The card itself is a brandnew upgraded i-cubed etherlan 600 now 600ax.
Booting up reports a "delaying eth0 initialization", but no more concerning
the network.
Everryting else works fine.

Besides I haven't been succesful with ifconfig, trying eh0 or eth0 as device.

Any hints ?
-- 
CU	
	Jan-Uwe
-------------------------------------------------
PGP-Public-Key on Request.

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

From owner-linux-arm@zen.ics.uwe.ac.uk  Sun May 30 16:09:04 1999
Received: (from majordomo@localhost)
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) id QAA32463
	for linux-arm-outgoing; Sun, 30 May 1999 16:09:04 +0100
Received: from mail.netwave.de (IDENT:root@smaug.netwave.de [194.162.128.45])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id QAA32456
	for <linux-arm@zen.ics.uwe.ac.uk>; Sun, 30 May 1999 16:08:50 +0100
Received: from as-line47.hb.netwave.de (root@as-line47.hb.netwave.de [195.185.99.174])
	by mail.netwave.de (8.9.1/8.8.5) with ESMTP id QAA16524
	for <linux-arm@zen.ics.uwe.ac.uk>; Sun, 30 May 1999 16:08:48 +0200
Received: (qmail 3179 invoked by uid 1000); 30 May 1999 15:08:24 -0000
Date: Sun, 30 May 1999 17:08:24 +0200
From: Jan-Uwe Finck <ju_finck@mail.netwave.de>
To: linux-arm@zen.ics.uwe.ac.uk
Subject: Eh0 not running after ftp-install
Message-ID: <19990530170824.A2700@mail.netwave.de>
Reply-To: Jan-Uwe.Finck@bigfoot.de
Mail-Followup-To: linux-arm@zen.ics.uwe.ac.uk
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.4i
Sender: owner-linux-arm@zen.ics.uwe.ac.uk
Precedence: bulk

hi,

after installing my ARM-Linux via ftp using my x86-Linux box as a gateway
I found out that my eth0-card isn't up anymore after rebooting.
/proc/devices doesn't show any sign of a network-card although it is detected 
at bootup.

The card itself is a brandnew upgraded i-cubed etherlan 600 now 600ax.
Booting up reports a "delaying eth0 initialization", but no more concerning
the network.
Everryting else works fine.

Besides I haven't been succesful with ifconfig, trying eh0 or eth0 as device.

Any hints ?
-- 
CU	
	Jan-Uwe
-------------------------------------------------
PGP-Public-Key on Request.

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

From owner-linux-arm@zen.ics.uwe.ac.uk  Sun May 30 16:24:01 1999
Received: (from majordomo@localhost)
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) id QAA32599
	for linux-arm-outgoing; Sun, 30 May 1999 16:24:01 +0100
Received: from mail.core.genedata.com (mentolat-e0.core.genedata.com [157.161.173.16])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id QAA32595
	for <linux-arm@zen.ics.uwe.ac.uk>; Sun, 30 May 1999 16:23:59 +0100
Received: from relay.ch.genedata.com (pinatubo-e0.ch.genedata.com [157.161.173.48])
	by mail.core.genedata.com (8.9.3/8.9.3) with ESMTP id RAA18239
	for <linux-arm@zen.ics.uwe.ac.uk>; Sun, 30 May 1999 17:23:58 +0200
Received: from mencheca.ch.genedata.com (root@mencheca.ch.genedata.com [157.161.173.82])
	by relay.ch.genedata.com (8.9.3/8.9.3) with ESMTP id RAA527122
	for <linux-arm@zen.ics.uwe.ac.uk>; Sun, 30 May 1999 17:23:57 +0200 (CEST)
Received: by genedata.com
	via sendmail from stdin
	id <m10o7RN-00025gC@mencheca.ch.genedata.com> (Debian Smail3.2.0.102)
	for linux-arm@zen.ics.uwe.ac.uk; Sun, 30 May 1999 17:23:57 +0200 (CEST) 
Date: Sun, 30 May 1999 17:23:57 +0200
From: Matthew Wilcox <Matthew.Wilcox@genedata.com>
To: linux-arm@zen.ics.uwe.ac.uk
Subject: Re: Eh0 not running after ftp-install
Message-ID: <19990530172357.K1410@mencheca.ch.genedata.com>
References: <19990530170824.A2700@mail.netwave.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.3i
In-Reply-To: <19990530170824.A2700@mail.netwave.de>; from Jan-Uwe Finck on Sun, May 30, 1999 at 05:08:24PM +0200
Sender: owner-linux-arm@zen.ics.uwe.ac.uk
Precedence: bulk

On Sun, May 30, 1999 at 05:08:24PM +0200, Jan-Uwe Finck wrote:
> after installing my ARM-Linux via ftp using my x86-Linux box as a gateway
> I found out that my eth0-card isn't up anymore after rebooting.
> /proc/devices doesn't show any sign of a network-card although it is detected 
> at bootup.

No, it's not detected at bootup.  That's just the kernel reading the
podule bus.  In any case, ethernet devices aren't reported within
/proc/devices.  You should `insmod etherh.o' somewhere in your boot
scripts, preferably before it attempts to initialise the ethernet.

> The card itself is a brandnew upgraded i-cubed etherlan 600 now 600ax.
> Booting up reports a "delaying eth0 initialization", but no more concerning
> the network.

that indicates the driver isn't loaded.

> Everryting else works fine.
> 
> Besides I haven't been succesful with ifconfig, trying eh0 or eth0 as device.

Linux uses eth0 irrespective of the card manufacturer.

-- 
Matthew Wilcox <willy@bofh.ai>
"Windows and MacOS are products, contrived by engineers in the service of
specific companies. Unix, by contrast, is not so much a product as it is a
painstakingly compiled oral history of the hacker subculture." - N Stephenson

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

From owner-linux-arm@zen.ics.uwe.ac.uk  Mon May 31 12:35:31 1999
Received: (from majordomo@localhost)
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) id MAA08844
	for linux-arm-outgoing; Mon, 31 May 1999 12:35:31 +0100
Received: from ntx.itri.org.tw (extmx.itri.org.tw [140.96.158.1])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with SMTP id MAA08840
	for <linux-arm@zen.ics.uwe.ac.uk>; Mon, 31 May 1999 12:35:26 +0100
Received: by ntx.itri.org.tw; (5.65v4.0/1.3/10May95) id AA15736; Mon, 31 May 1999 19:36:38 +0800
Received: from oax2.CCL.ITRI.Org.tw (oax2.ccl.itri.org.tw [140.96.110.211])
	by nti.itri.org.tw (8.8.8/8.8.8) with ESMTP id TAA12972
	for <linux-arm@zen.ics.uwe.ac.uk>; Mon, 31 May 1999 19:35:41 +0800 (CST)
Received: from xserver.ccl.itri.org.tw (xserver.ccl.itri.org.tw [140.96.120.200])
	by oax2.CCL.ITRI.Org.tw (8.8.5/8.8.5) with SMTP id TAA12226
	for <linux-arm@zen.ics.uwe.ac.uk>; Mon, 31 May 1999 19:36:24 +0800 (CST)
Received: from csie.nctu.edu.tw by xserver.ccl.itri.org.tw (SMI-8.6/SMI-SVR4)
	id TAA15904; Mon, 31 May 1999 19:26:48 +0800
Message-Id: <3752750D.1683E1DB@csie.nctu.edu.tw>
Date: Mon, 31 May 1999 19:39:57 +0800
From: Min-Shong Lin <minslin@csie.nctu.edu.tw>
Organization: X100 CCL ITRI
X-Mailer: Mozilla 4.5 [en] (WinNT; I)
X-Accept-Language: en
Mime-Version: 1.0
To: linux-arm@zen.ics.uwe.ac.uk
Subject: about BRUTUS(SA1100) 64-bit Floating Point
Content-Type: text/plain; charset=iso-8859-1
X-Mime-Autoconverted: from 8bit to quoted-printable by nti.itri.org.tw id TAA12972
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by zen.ics.uwe.ac.uk id MAA08841
Sender: owner-linux-arm@zen.ics.uwe.ac.uk
Precedence: bulk


	Hi,
	I am porting PersonalJava to Linux on Brutus(SA1100).
	I found that the 64-bit floating-point operations are weird.
	The 64-bit floating-point byte-order seems different from the 64-bit
integer.
	Does anyone encounter such problem when porting JDKs or Linux ??


-- 
Min-Shong Lin (ªL±Ó¶¯)
minslin@csie.nctu.edu.tw	http://www.csie.nctu.edu.tw/~minslin
X100, CCL, ITRI, Taiwan		Phone: 886-3-5914611

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

From owner-linux-arm@zen.ics.uwe.ac.uk  Mon May 31 14:17:42 1999
Received: (from majordomo@localhost)
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) id OAA09608
	for linux-arm-outgoing; Mon, 31 May 1999 14:17:42 +0100
Received: from finch-post-12.mail.demon.net (finch-post-12.mail.demon.net [194.217.242.41])
	by zen.ics.uwe.ac.uk (8.9.3/8.8.7) with ESMTP id OAA09604
	for <linux-arm@zen.ics.uwe.ac.uk>; Mon, 31 May 1999 14:17:39 +0100
Received: from [158.152.220.239] (helo=kings-cross.london.uk.eu.org)
	by finch-post-12.mail.demon.net with esmtp (Exim 2.12 #1)
	id 10oRwf-000DWx-0C; Mon, 31 May 1999 13:17:38 +0000
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 10oRU7-0005g1-00; Mon, 31 May 1999 13:48:07 +0100
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: Min-Shong Lin <minslin@csie.nctu.edu.tw>
cc: linux-arm@zen.ics.uwe.ac.uk
Subject: Re: about BRUTUS(SA1100) 64-bit Floating Point 
In-Reply-To: Message from Min-Shong Lin <minslin@csie.nctu.edu.tw> 
   of "Mon, 31 May 1999 19:39:57 +0800." <3752750D.1683E1DB@csie.nctu.edu.tw> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 31 May 1999 13:48:06 +0100
From: Philip Blundell <philb@gnu.org>
Message-Id: <E10oRU7-0005g1-00@kings-cross.london.uk.eu.org>
Sender: owner-linux-arm@zen.ics.uwe.ac.uk
Precedence: bulk

>	I found that the 64-bit floating-point operations are weird.
>	The 64-bit floating-point byte-order seems different from the 64-bit
>integer.

It is.  ARMs use a peculiar hybrid big/little-endian format for floating point 
values; the bytes are laid out as big endian but the words are laid out as 
little endian.  This is the result of a historical accident and unfortunately 
we are now pretty much stuck with it.

If you used -msoft-float you could theoretically choose whatever format you 
like, but in practice compatibility with libc and so on means you would 
probably end up going along with the standard ARM format again.

p.



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

