From hub-fue!alpha.franken.de!tsbogend@rachael.franken.de Sun Jun 1 10:06:08 1997 Received-Date: Sun, 1 Jun 1997 10:06:07 +0200 (MET DST) Received: from hub-fue by rachael.franken.de with uucp (Smail3.1.29.1 #8) id m0wY5eP-000obYC; Sun, 1 Jun 97 10:06 MET DST Received: by hub-fue.franken.de (Smail3.1.29.1 #35) id m0wY5eI-002Ob2C; Sun, 1 Jun 97 10:05 MET DST Received: (from tsbogend@localhost) by alpha.franken.de (8.8.5/8.8.5) id KAA00355 for linux-mips@fnet.fr; Sun, 1 Jun 1997 10:00:50 +0200 From: Thomas Bogendoerfer Message-Id: <199706010800.KAA00355@alpha.franken.de> Subject: working 2.1.36 on magnum/m700 ? To: linux-mips@fnet.fr Date: Sun, 1 Jun 1997 10:00:49 +0200 (MEST) X-Mailer: ELM [version 2.4ME+ PL27 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 469 Lines: 11 Before I'll start to find the problem with 2.1.36, I want to know, if anybody has a working 2.1.36 kernel for Mips Magnum boards or Olivetti M700. When I try to boot 2.1.36 it stops after milo printed "Launching kernel", no console initialisation, nothing. Any hints ? Thomas. -- See, you not only have to be a good coder to create a system like Linux, you have to be a sneaky bastard too ;-) [Linus Torvalds in <4rikft$7g5@linux.cs.Helsinki.FI>] From hub-fue!alpha.franken.de!tsbogend@rachael.franken.de Sun Jun 1 11:24:45 1997 Received-Date: Sun, 1 Jun 1997 11:24:44 +0200 (MET DST) Received: from hub-fue by rachael.franken.de with uucp (Smail3.1.29.1 #8) id m0wY6sS-000oHdC; Sun, 1 Jun 97 11:24 MET DST Received: by hub-fue.franken.de (Smail3.1.29.1 #35) id m0wY6sM-002Ob2C; Sun, 1 Jun 97 11:24 MET DST Received: (from tsbogend@localhost) by alpha.franken.de (8.8.5/8.8.5) id LAA01041 for linux-mips@fnet.fr; Sun, 1 Jun 1997 11:19:30 +0200 From: Thomas Bogendoerfer Message-Id: <199706010919.LAA01041@alpha.franken.de> Subject: Re: working 2.1.36 on magnum/m700 ? In-Reply-To: <199706010800.KAA00355@alpha.franken.de> from Thomas Bogendoerfer at "Jun 1, 97 10:00:49 am" To: linux-mips@fnet.fr Date: Sun, 1 Jun 1997 11:19:30 +0200 (MEST) X-Mailer: ELM [version 2.4ME+ PL27 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 648 Lines: 15 > Before I'll start to find the problem with 2.1.36, I want to know, if > anybody has a working 2.1.36 kernel for Mips Magnum boards or Olivetti M700. > When I try to boot 2.1.36 it stops after milo printed "Launching kernel", > no console initialisation, nothing. Any hints ? small update: One thing missing in 2.1.36 is the define CONFIG_VIDEO_G364. But defining it and fixing g364.c (missing con_type_init_finish() ), doesn't bring up my M700. Thomas. -- See, you not only have to be a good coder to create a system like Linux, you have to be a sneaky bastard too ;-) [Linus Torvalds in <4rikft$7g5@linux.cs.Helsinki.FI>] From linux@informatik.uni-koblenz.de Sun Jun 1 17:51:46 1997 Received-Date: Sun, 1 Jun 1997 17:51:38 +0200 (MET DST) Received: from grass (linux@grass.uni-koblenz.de [141.26.4.65]) by informatik.uni-koblenz.de (8.8.5/8.6.9) with SMTP id RAA11510 for ; Sun, 1 Jun 1997 17:51:28 +0200 (MEST) From: Systemkennung Linux Message-Id: <199706011551.RAA11510@informatik.uni-koblenz.de> Received: by grass (SMI-8.6/KO-2.0) id RAA13314; Sun, 1 Jun 1997 17:51:26 +0200 Subject: Re: working 2.1.36 on magnum/m700 ? To: linux-mips@fnet.fr Date: Sun, 1 Jun 1997 17:51:25 +0200 (MET DST) In-Reply-To: <199706010800.KAA00355@alpha.franken.de> from "Thomas Bogendoerfer" at Jun 1, 97 10:00:49 am MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Length: 374 Lines: 9 > Before I'll start to find the problem with 2.1.36, I want to know, if > anybody has a working 2.1.36 kernel for Mips Magnum boards or Olivetti M700. > When I try to boot 2.1.36 it stops after milo printed "Launching kernel", > no console initialisation, nothing. Any hints ? There is something wrong with Milo on M700 only as it looks. My guess is the malloc(). Ralf From hub-fue!alpha.franken.de!tsbogend@rachael.franken.de Sun Jun 1 21:28:48 1997 Received-Date: Sun, 1 Jun 1997 21:28:47 +0200 (MET DST) Received: from hub-fue by rachael.franken.de with uucp (Smail3.1.29.1 #8) id m0wYGJ3-000oQBC; Sun, 1 Jun 97 21:28 MET DST Received: by hub-fue.franken.de (Smail3.1.29.1 #35) id m0wYGIy-002Ob9C; Sun, 1 Jun 97 21:28 MET DST Received: (from tsbogend@localhost) by alpha.franken.de (8.8.5/8.8.5) id VAA00747 for linux-mips@fnet.fr; Sun, 1 Jun 1997 21:23:27 +0200 From: Thomas Bogendoerfer Message-Id: <199706011923.VAA00747@alpha.franken.de> Subject: Re: working 2.1.36 on magnum/m700 ? In-Reply-To: <199706011551.RAA11510@informatik.uni-koblenz.de> from Systemkennung Linux at "Jun 1, 97 05:51:25 pm" To: linux-mips@fnet.fr Date: Sun, 1 Jun 1997 21:23:27 +0200 (MEST) X-Mailer: ELM [version 2.4ME+ PL27 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 828 Lines: 19 > > Before I'll start to find the problem with 2.1.36, I want to know, if > > anybody has a working 2.1.36 kernel for Mips Magnum boards or Olivetti M700. > > When I try to boot 2.1.36 it stops after milo printed "Launching kernel", > > no console initialisation, nothing. Any hints ? > > There is something wrong with Milo on M700 only as it looks. My guess is > the malloc(). I tried 0.27 and 0.27.1 both failed, but they didn't crash. 0.27 still works for me with an older kernel (2.1.1). Running milo -d also indicates that it is a kernel problem not a milo problem. I guess it's related to the console changes in 2.1.x. Thomas. -- See, you not only have to be a good coder to create a system like Linux, you have to be a sneaky bastard too ;-) [Linus Torvalds in <4rikft$7g5@linux.cs.Helsinki.FI>] From hub-fue!alpha.franken.de!tsbogend@rachael.franken.de Sun Jun 1 23:16:24 1997 Received-Date: Sun, 1 Jun 1997 23:16:23 +0200 (MET DST) Received: from hub-fue by rachael.franken.de with uucp (Smail3.1.29.1 #8) id m0wYHzB-000oKBC; Sun, 1 Jun 97 23:16 MET DST Received: by hub-fue.franken.de (Smail3.1.29.1 #35) id m0wYHz6-002Ob2C; Sun, 1 Jun 97 23:16 MET DST Received: (from tsbogend@localhost) by alpha.franken.de (8.8.5/8.8.5) id XAA03491 for linux-mips@fnet.fr; Sun, 1 Jun 1997 23:11:15 +0200 From: Thomas Bogendoerfer Message-Id: <199706012111.XAA03491@alpha.franken.de> Subject: Re: working 2.1.36 on magnum/m700 ? In-Reply-To: <199706011923.VAA00747@alpha.franken.de> from Thomas Bogendoerfer at "Jun 1, 97 09:23:27 pm" To: linux-mips@fnet.fr Date: Sun, 1 Jun 1997 23:11:15 +0200 (MEST) X-Mailer: ELM [version 2.4ME+ PL27 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 467 Lines: 14 more info: milo 0.27.1 with kernel-2.1.14 works. milo 0.27.1 (and 0.27) with kernel-2.1.36 stops after launching kernel and crashes after pressing one key with a NMI. The faulting instruction is in function r4k_handle_tbls(), the faulting address is 0x1ffff000. Thomas. -- See, you not only have to be a good coder to create a system like Linux, you have to be a sneaky bastard too ;-) [Linus Torvalds in <4rikft$7g5@linux.cs.Helsinki.FI>] From linux@informatik.uni-koblenz.de Mon Jun 2 08:53:34 1997 Received-Date: Mon, 2 Jun 1997 08:53:26 +0200 (MET DST) Received: from zaphod (linux@zaphod.uni-koblenz.de [141.26.4.13]) by informatik.uni-koblenz.de (8.8.5/8.6.9) with SMTP id IAA05034 for ; Mon, 2 Jun 1997 08:53:14 +0200 (MEST) From: Systemkennung Linux Message-Id: <199706020653.IAA05034@informatik.uni-koblenz.de> Received: by zaphod (SMI-8.6/KO-2.0) id IAA06488; Mon, 2 Jun 1997 08:53:13 +0200 Subject: Re: working 2.1.36 on magnum/m700 ? To: linux-mips@fnet.fr Date: Mon, 2 Jun 1997 08:53:12 +0200 (MET DST) In-Reply-To: <199706012111.XAA03491@alpha.franken.de> from "Thomas Bogendoerfer" at Jun 1, 97 11:11:15 pm MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Length: 515 Lines: 15 Hi, > milo 0.27.1 with kernel-2.1.14 works. > > milo 0.27.1 (and 0.27) with kernel-2.1.36 stops after launching kernel > and crashes after pressing one key with a NMI. The faulting instruction > is in function r4k_handle_tbls(), the faulting address is 0x1ffff000. The code which loads the wired entries into the tlb is borken. Somewhen during the startup the c0_wired register is set again to zero. Maybe a got time to get rid of those entries? 48 entries is just not enough to wire many of them. Ralf From linux@informatik.uni-koblenz.de Mon Jun 2 08:58:17 1997 Received-Date: Mon, 2 Jun 1997 08:57:30 +0200 (MET DST) Received: from zaphod (linux@zaphod.uni-koblenz.de [141.26.4.13]) by informatik.uni-koblenz.de (8.8.5/8.6.9) with SMTP id IAA05221 for ; Mon, 2 Jun 1997 08:56:08 +0200 (MEST) From: Systemkennung Linux Message-Id: <199706020656.IAA05221@informatik.uni-koblenz.de> Received: by zaphod (SMI-8.6/KO-2.0) id IAA06614; Mon, 2 Jun 1997 08:56:06 +0200 Subject: Re: working 2.1.36 on magnum/m700 ? To: linux-mips@fnet.fr Date: Mon, 2 Jun 1997 08:56:06 +0200 (MET DST) In-Reply-To: <199706011923.VAA00747@alpha.franken.de> from "Thomas Bogendoerfer" at Jun 1, 97 09:23:27 pm MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Length: 783 Lines: 17 > > > Before I'll start to find the problem with 2.1.36, I want to know, if > > > anybody has a working 2.1.36 kernel for Mips Magnum boards or Olivetti M700. > > > When I try to boot 2.1.36 it stops after milo printed "Launching kernel", > > > no console initialisation, nothing. Any hints ? > > > > There is something wrong with Milo on M700 only as it looks. My guess is > > the malloc(). > > I tried 0.27 and 0.27.1 both failed, but they didn't crash. 0.27 still works > for me with an older kernel (2.1.1). Running milo -d also indicates that it > is a kernel problem not a milo problem. I guess it's related to the > console changes in 2.1.x. There is still some real bug in Milo. Adding the right number of printf() statements will make the bug showup sometimes. Ralf From ralf@informatik.uni-koblenz.de Mon Jun 2 09:48:32 1997 Received-Date: Mon, 2 Jun 1997 09:48:21 +0200 (MET DST) Received: from zaphod (ralf@zaphod.uni-koblenz.de [141.26.4.13]) by informatik.uni-koblenz.de (8.8.5/8.6.9) with SMTP id JAA12680; Mon, 2 Jun 1997 09:47:55 +0200 (MEST) From: Ralf Baechle Message-Id: <199706020747.JAA12680@informatik.uni-koblenz.de> Received: by zaphod (SMI-8.6/KO-2.0) id JAA08937; Mon, 2 Jun 1997 09:47:54 +0200 Subject: New GCC patches uploaded Date: Mon, 2 Jun 1997 09:47:54 +0200 (MET DST) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Length: 787 Lines: 24 -----BEGIN PGP SIGNED MESSAGE----- Hi all, I've uploaded a new GCC patch gcc-2.7.2-4.diff.gz to kernel.panic.julia.de and ftp.fnet.fr. The patches fixes bug that the big endian targets had different predefined preprocessor symbols. It also reduces the a little bit excessive alignments that were used for trampolines. There is no real need to upgrade to this version if you're already running GCC 2.7.2-3 and can ignore some warnings. Ralf 77e6b058dae70d4d1cc6d970bbc30afa gcc-2.7.2-4.gz -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAgUBM5J6pkckbl6vezDBAQF2dgQAqT7Z+y/X5pDgLqy+AvkFXS4rsNwSoGFI dvdN1SwZMJsNctH4FYZYY02OSwzlpmlvbKr6hbrFEKapL6NvaQfkxrONQAk+9or0 vegnDwvqmqHbd/mxiQbdpVpIc7FCdYfwihUWMtVjP2yQZ7woVYbdXd/g+c4L0uuW 9/Bbu/Jcwz8= =3h+R -----END PGP SIGNATURE----- From hub-fue!alpha.franken.de!tsbogend@rachael.franken.de Tue Jun 3 00:07:46 1997 Received-Date: Tue, 3 Jun 1997 00:07:45 +0200 (MET DST) Received: from hub-fue by rachael.franken.de with uucp (Smail3.1.29.1 #8) id m0wYfGQ-000oL6C; Tue, 3 Jun 97 00:07 MET DST Received: by hub-fue.franken.de (Smail3.1.29.1 #35) id m0wYfGH-002ObUC; Tue, 3 Jun 97 00:07 MET DST Received: (from tsbogend@localhost) by alpha.franken.de (8.8.5/8.8.5) id AAA01985 for linux-mips@fnet.fr; Tue, 3 Jun 1997 00:02:09 +0200 From: Thomas Bogendoerfer Message-Id: <199706022202.AAA01985@alpha.franken.de> Subject: Re: working 2.1.36 on magnum/m700 ? In-Reply-To: <199706020653.IAA05034@informatik.uni-koblenz.de> from Systemkennung Linux at "Jun 2, 97 08:53:12 am" To: linux-mips@fnet.fr Date: Tue, 3 Jun 1997 00:02:09 +0200 (MEST) X-Mailer: ELM [version 2.4ME+ PL27 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 774 Lines: 19 > The code which loads the wired entries into the tlb is borken. Somewhen > during the startup the c0_wired register is set again to zero. does this mean, that there are no wired entries installed for Magnum boards (the code looks like this) ? How will such a kernel work ? > Maybe a got time to get rid of those entries? 48 entries is just not enough > to wire many of them. sorry, I don't quite understand that. Do you want to get rid of the wired entries, because 48 TLBs aren't enough for normal usage ? Do you want to use page faults to map hardware registers ? Thomas. -- See, you not only have to be a good coder to create a system like Linux, you have to be a sneaky bastard too ;-) [Linus Torvalds in <4rikft$7g5@linux.cs.Helsinki.FI>] From C-FitzgMatt@mail.dec.com Tue Jun 3 07:41:50 1997 Received-Date: Tue, 3 Jun 1997 07:41:49 +0200 (MET DST) Received: from snoexc2.dhcp.sno.dec.com by mail13.digital.com (8.7.5/UNX 1.5/1.0/WV) id BAA14029; Tue, 3 Jun 1997 01:37:00 -0400 (EDT) Received: by snoexc2.dhcp.sno.dec.com with SMTP (Microsoft Exchange Server Internet Mail Connector Version 4.0.995.52) id <01BC7034.32489880@snoexc2.dhcp.sno.dec.com>; Tue, 3 Jun 1997 15:38:34 +1000 Message-ID: From: Matthew Fitzgerald -WPO To: "'linux-mips@fnet.fr'" Subject: DECstation 5xxx Date: Tue, 3 Jun 1997 15:38:33 +1000 X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.995.52 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Length: 708 Lines: 24 Hiya, Hmm, I am very impressed that someone has attempted to port Linux to the DECstation 5000 series... I read the MIPS FAQ today, is there anything updated that isn't on the FAQ yet? I'll just tell you my config: DECstation 5000-240 128MB RAM 24bit Z-buffer 3D graphics card (TURBOchannel) (and some disks and stuff....) Is there any support for these options??? Please let me know, I am a programmer, so if you want any more development, let me know!!! Regards, -Matt ------------------------------------------ Matt Fitzgerald, Digital TSMC West Perth Email: c-fitzgmatt@mail.dec.com Ph: +61(08)94833324 Fax: +61(08)93225004 -------------------oOo-------------------- From dom@gladsmuir.algor.co.uk Tue Jun 3 10:44:12 1997 Received-Date: Tue, 3 Jun 1997 10:44:10 +0200 (MET DST) Received: from gladsmuir.algor.co.uk (dom@[193.117.190.129]) by embankment.algor.co.uk (8.8.5/8.8.5) with ESMTP id IAA15378; Tue, 3 Jun 1997 08:49:57 +0100 (BST) Received: (from dom@localhost) by gladsmuir.algor.co.uk (8.7.3/8.7.3) id IAA00252; Tue, 3 Jun 1997 08:52:00 +0100 (BST) Date: Tue, 3 Jun 1997 08:52:00 +0100 (BST) From: Dom Sweetman Message-Id: <199706030752.IAA00252@gladsmuir.algor.co.uk> To: linux-mips@fnet.fr Subject: Re: working 2.1.36 on magnum/m700 ? In-Reply-To: <199706022202.AAA01985@alpha.franken.de> References: <199706020653.IAA05034@informatik.uni-koblenz.de> <199706022202.AAA01985@alpha.franken.de> Content-Length: 1600 Lines: 42 You probably mostly know this, but... Ralf wrote: > > Maybe a got time to get rid of those entries? 48 entries is just > > not enough to wire many of them. And Thomas said: > sorry, I don't quite understand that. Do you want to get rid of the > wired entries, because 48 TLBs aren't enough for normal usage ? > Do you want to use page faults to map hardware registers ? Most MIPS systems reach hardware registers through the fixed kseg1 uncached window (onto physical memory from 0 to 512Mbytes). The kernel works mostly in kseg0, the fixed cached window onto the same address range. If your system is bizarre enough to put hardware registers outside this easily-accessible physical address range, you would indeed need either special TLB entries (or real 64-bit pointers on an R4x00). In this case not even Ralf would disagree with wiring those entries; but a better solution would be to fire the hardware designer and incinerate the hardware. A few permanent "wired" TLB entries are typically used for some critical kernel resources which must for some reason be mapped, but where you can't tolerate a TLB-miss exception. MIPS note: a TLB miss is not a page fault. TLB misses just reload the TLB from some memory-resident data structure. On a CISC CPU this would be handled 'invisibly' by microcode, and it really doesn't make much difference to have it done by an exception. A page fault is where the data you want is not valid in memory, and the OS needs to be invoked to find what data is appropriate, find it (perhaps on disk) and map it. Dominic Sweetman dom@algor.co.uk From davem@caipfs.rutgers.edu Tue Jun 3 11:03:04 1997 Received-Date: Tue, 3 Jun 1997 11:03:02 +0200 (MET DST) Received: from jenolan.caipgeneral (jenolan.rutgers.edu [128.6.111.5]) by caipfs.rutgers.edu (8.8.5/8.8.5) with SMTP id FAA23230 for ; Tue, 3 Jun 1997 05:02:54 -0400 (EDT) Received: by jenolan.caipgeneral (SMI-8.6/SMI-SVR4) id FAA01703; Tue, 3 Jun 1997 05:00:51 -0400 Date: Tue, 3 Jun 1997 05:00:51 -0400 Message-Id: <199706030900.FAA01703@jenolan.caipgeneral> From: "David S. Miller" To: linux-mips@fnet.fr In-reply-to: <199706030752.IAA00252@gladsmuir.algor.co.uk> (message from Dom Sweetman on Tue, 3 Jun 1997 08:52:00 +0100 (BST)) Subject: Re: working 2.1.36 on magnum/m700 ? Content-Length: 1390 Lines: 29 Date: Tue, 3 Jun 1997 08:52:00 +0100 (BST) From: Dom Sweetman If your system is bizarre enough to put hardware registers outside this easily-accessible physical address range, you would indeed need either special TLB entries (or real 64-bit pointers on an R4x00). In this case not even Ralf would disagree with wiring those entries; but a better solution would be to fire the hardware designer and incinerate the hardware. I don't see what the big deal is. Just use tlb entries for the memory mapped I/O registers, and let them tlb miss in. I remember my tlb miss code is around 12 instructions or so. I use dynamic tlb replacable entries for memory mapped I/O on the UltraSparc and those misses can cost around 20 instructions or so for a kernel miss. It pays off to do this really, when I/O registers aren't being accessed, the tlb entires become available for the user, if they are being often accessed the tend to sit "hot" in the tlb and don't get kicked out much. There is no gain to be had by locked them down. ---------------------------------------------//// Yow! 11.26 MB/s remote host TCP bandwidth & //// 199 usec remote TCP latency over 100Mb/s //// ethernet. Beat that! //// -----------------------------------------////__________ o David S. Miller, davem@caip.rutgers.edu /_____________/ / // /_/ >< From linux@informatik.uni-koblenz.de Wed Jun 4 19:05:59 1997 Received-Date: Wed, 4 Jun 1997 19:05:12 +0200 (MET DST) Received: from thoma (root@thoma.uni-koblenz.de [141.26.4.61]) by informatik.uni-koblenz.de (8.8.5/8.6.9) with SMTP id TAA02748 for ; Wed, 4 Jun 1997 19:05:01 +0200 (MEST) From: Systemkennung Linux Message-Id: <199706041705.TAA02748@informatik.uni-koblenz.de> Received: by thoma (SMI-8.6/KO-2.0) id PAA00312; Tue, 3 Jun 1997 15:32:22 +0200 Subject: Re: working 2.1.36 on magnum/m700 ? To: linux-mips@fnet.fr Date: Tue, 3 Jun 1997 15:32:19 +0200 (MET DST) In-Reply-To: <199706030752.IAA00252@gladsmuir.algor.co.uk> from "Dom Sweetman" at Jun 3, 97 08:52:00 am MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Length: 556 Lines: 12 > If your system is bizarre enough to put hardware registers outside > this easily-accessible physical address range, you would indeed need > either special TLB entries (or real 64-bit pointers on an R4x00). In > this case not even Ralf would disagree with wiring those entries; but > a better solution would be to fire the hardware designer and > incinerate the hardware. The Jazz design (hint: Microsoft designed the machine, not Mips ...) made the machine bizarre enough. The kernel uses 7 rsp. 8 wired TLB entries which I consider too many. Ralf From linux@informatik.uni-koblenz.de Wed Jun 4 19:05:40 1997 Received-Date: Wed, 4 Jun 1997 19:05:23 +0200 (MET DST) Received: from thoma (root@thoma.uni-koblenz.de [141.26.4.61]) by informatik.uni-koblenz.de (8.8.5/8.6.9) with SMTP id TAA02763 for ; Wed, 4 Jun 1997 19:05:03 +0200 (MEST) From: Systemkennung Linux Message-Id: <199706041705.TAA02763@informatik.uni-koblenz.de> Received: by thoma (SMI-8.6/KO-2.0) id PAA00575; Tue, 3 Jun 1997 15:50:02 +0200 Subject: Re: working 2.1.36 on magnum/m700 ? To: linux-mips@fnet.fr Date: Tue, 3 Jun 1997 15:50:00 +0200 (MET DST) In-Reply-To: <199706022202.AAA01985@alpha.franken.de> from "Thomas Bogendoerfer" at Jun 3, 97 00:02:09 am MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Length: 1231 Lines: 25 > > The code which loads the wired entries into the tlb is borken. Somewhen > > during the startup the c0_wired register is set again to zero. > > does this mean, that there are no wired entries installed for Magnum boards > (the code looks like this) ? How will such a kernel work ? Well, the code *should* install them. For the SGI port David shreddered the code that loads the wired TLB entries and I did´t fix that so far. > sorry, I don't quite understand that. Do you want to get rid of the wired > entries, because 48 TLBs aren't enough for normal usage ? Do you want to > use page faults to map hardware registers ? Using TLB misses would be the right thing to use. But in case of the Jazz machines and the current kernel this won´t work. The current page table format has the limit that it can only map to physical addresses in the 0 <= x < 512mb range. These addresses are also accessible through KSEG0 and KSEG1, so we never need to use the TLB. For everything outside the lowest 512mb address space we have the options to use wired TLB entries or 64 bit pointers. If we extend the size of a page table entry to 64 bit we will also have the preferable option of using the normal TLB faults at hand. Ralf From ralf@informatik.uni-koblenz.de Tue Jun 3 21:39:09 1997 Received-Date: Tue, 3 Jun 1997 21:38:53 +0200 (MET DST) Received: from flake (ralf@flake.uni-koblenz.de [141.26.4.37]) by informatik.uni-koblenz.de (8.8.5/8.6.9) with SMTP id VAA11936 for ; Tue, 3 Jun 1997 21:38:43 +0200 (MEST) From: Ralf Baechle Message-Id: <199706031938.VAA11936@informatik.uni-koblenz.de> Received: by flake (SMI-8.6/KO-2.0) id VAA04327; Tue, 3 Jun 1997 21:38:39 +0200 Subject: Recently ... To: linux-mips@fnet.fr Date: Tue, 3 Jun 1997 21:38:38 +0200 (MET DST) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Length: 75 Lines: 7 on a R5000 nearby: http://bogomips.ingenia.com Surf and enjoy. Ralf From hub-fue!alpha.franken.de!tsbogend@rachael.franken.de Wed Jun 4 00:00:45 1997 Received-Date: Wed, 4 Jun 1997 00:00:41 +0200 (MET DST) Received: from hub-fue by rachael.franken.de with uucp (Smail3.1.29.1 #8) id m0wZ1d6-000oSzC; Wed, 4 Jun 97 00:00 MET DST Received: by hub-fue.franken.de (Smail3.1.29.1 #35) id m0wZ1cq-002ObWC; Wed, 4 Jun 97 00:00 MET DST Received: (from tsbogend@localhost) by alpha.franken.de (8.8.5/8.8.5) id XAA01445 for linux-mips@fnet.fr; Tue, 3 Jun 1997 23:54:49 +0200 From: Thomas Bogendoerfer Message-Id: <199706032154.XAA01445@alpha.franken.de> Subject: Re: working 2.1.36 on magnum/m700 ? In-Reply-To: <199706030752.IAA00252@gladsmuir.algor.co.uk> from Dom Sweetman at "Jun 3, 97 08:52:00 am" To: linux-mips@fnet.fr Date: Tue, 3 Jun 1997 23:54:48 +0200 (MEST) X-Mailer: ELM [version 2.4ME+ PL27 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 825 Lines: 20 > If your system is bizarre enough to put hardware registers outside > this easily-accessible physical address range, you would indeed need most (all ?) of the hardware registers of the Magnum boards are out of KSEG1 area:-( They start from physical address 0x80000000. And there are memory and register for the video card in another address range. > either special TLB entries (or real 64-bit pointers on an R4x00). In > this case not even Ralf would disagree with wiring those entries; but > a better solution would be to fire the hardware designer and > incinerate the hardware. it's probably too late to fire them:-) Thomas. -- See, you not only have to be a good coder to create a system like Linux, you have to be a sneaky bastard too ;-) [Linus Torvalds in <4rikft$7g5@linux.cs.Helsinki.FI>] From khp@imladris.dolphinics.no Wed Jun 4 09:33:34 1997 Received-Date: Wed, 4 Jun 1997 09:33:32 +0200 (MET DST) Received: from imladris.dolphinics.no (pcbob.dolphinics.no) by scimitar.dolphinics.no (4.1/SMI-4.1) id AA21682; Wed, 4 Jun 97 08:43:12 +0200 Received: (from khp@localhost) by imladris.dolphinics.no (8.7.5/8.7.3) id IAA11738 for linux-mips@fnet.fr; Wed, 4 Jun 1997 08:44:52 +0200 Message-Id: <199706040644.IAA11738@imladris.dolphinics.no> Subject: Re: Recently ... In-Reply-To: <199706031938.VAA11936@informatik.uni-koblenz.de> from Ralf Baechle at "Jun 3, 97 09:38:38 pm" To: linux-mips@fnet.fr Date: Wed, 4 Jun 1997 08:44:52 +0200 (MET DST) From: Kai Harrekilde-Petersen X-Mailer: ELM [version 2.4ME+ PL27 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 297 Lines: 13 Ralf Baechle writes: > on a R5000 nearby: > > http://bogomips.ingenia.com > > Surf and enjoy. _Very_ cute. I suppose it's Dave's box? Kai -- Kai Harrekilde-Petersen #include http://www.dolphinics.no/~khp/ Remove the obvious part when replying From linux@informatik.uni-koblenz.de Wed Jun 4 19:05:33 1997 Received-Date: Wed, 4 Jun 1997 19:05:07 +0200 (MET DST) Received: from thoma (root@thoma.uni-koblenz.de [141.26.4.61]) by informatik.uni-koblenz.de (8.8.5/8.6.9) with SMTP id TAA02706 for ; Wed, 4 Jun 1997 19:04:49 +0200 (MEST) From: Systemkennung Linux Message-Id: <199706041704.TAA02706@informatik.uni-koblenz.de> Received: by thoma (SMI-8.6/KO-2.0) id KAA03317; Wed, 4 Jun 1997 10:39:44 +0200 Subject: Re: Recently ... To: linux-mips@fnet.fr Date: Wed, 4 Jun 1997 10:39:40 +0200 (MET DST) In-Reply-To: <199706040644.IAA11738@imladris.dolphinics.no> from "Kai Harrekilde-Petersen" at Jun 4, 97 08:44:52 am MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Length: 519 Lines: 19 > Ralf Baechle writes: > > on a R5000 nearby: > > > > http://bogomips.ingenia.com > > > > Surf and enjoy. > > _Very_ cute. I suppose it's Dave's box? Nope. It's Mike Shaver's Indy running Apache. He borrowed an Indy to work on the SGI port. Miguel de Icaza will also rsn get an Indy. At least I'm satisfied to see we have the R5k working as well. Btw, if there are any artists on this list - we need a Linux/MIPS edition of the Penguin. Take a look at the above URL and make a even better Penguin! Ralf From miguel@athena.nuclecu.unam.mx Wed Jun 4 19:44:34 1997 Received-Date: Wed, 4 Jun 1997 19:44:32 +0200 (MET DST) Received: (from miguel@localhost) by athena.nuclecu.unam.mx (8.8.5/8.8.5) id MAA24121; Wed, 4 Jun 1997 12:35:25 -0500 Date: Wed, 4 Jun 1997 12:35:25 -0500 Message-Id: <199706041735.MAA24121@athena.nuclecu.unam.mx> From: Miguel de Icaza To: linux-mips@fnet.fr CC: federico@nuclecu.unam.mx In-reply-to: <199706041704.TAA02706@informatik.uni-koblenz.de> (message from Systemkennung Linux on Wed, 4 Jun 1997 10:39:40 +0200 (MET DST)) Subject: Re: Recently ... X-Windows: You'll envy the dead. Content-Length: 315 Lines: 10 > > > http://bogomips.ingenia.com > > Btw, if there are any artists on this list - we need a Linux/MIPS edition > of the Penguin. Take a look at the above URL and make a even better > Penguin! I have no choice but to force brutally Federico to make us a logo this afternoon with his new gimp scripts. Miguel. From dom@gladsmuir.algor.co.uk Wed Jun 4 23:24:32 1997 Received-Date: Wed, 4 Jun 1997 23:24:30 +0200 (MET DST) Received: from gladsmuir.algor.co.uk (dom@gladsmuir.algor.co.uk [193.117.190.129]) by embankment.algor.co.uk (8.8.5/8.8.5) with ESMTP id WAA22929; Wed, 4 Jun 1997 22:24:25 +0100 (BST) Received: (from dom@localhost) by gladsmuir.algor.co.uk (8.7.3/8.7.3) id WAA00515; Wed, 4 Jun 1997 22:27:29 +0100 (BST) Date: Wed, 4 Jun 1997 22:27:29 +0100 (BST) From: Dom Sweetman Message-Id: <199706042127.WAA00515@gladsmuir.algor.co.uk> To: linux-mips@fnet.fr Subject: Re: Compiler bug? In-Reply-To: References: Content-Length: 1337 Lines: 44 Tim, > I've got a possible compiler bug I was wondering you could help me with. > Here's what I'm seeing in two places in the code (and who knows where else): > > In fork.c there is: > > if (copy_mm(clone_flags,p)) > goto bad_fork_cleanup_sighand; > > On entering this line of code, my "p" is valid (0x80fdb810) on exit from > the code it is invalid (0xFFFFFFF). There ain't no compiler bug until the program does something wrong. My guess is that what you've got here is that the compiler is allocating the value 'p' to a register (which may well be a good thing to do). The debugger then has to have its best shot at digging out the value 'p' based on hints the compiler leaves around. It's not reasonable to expect the compiler/debugger to report a value correctly when it's no longer needed; the compiler may have recycled that register for something else, or the debugger lost track of it. > If I put the following code immediately > after the call: > > p = *(&p); > > My pointer magically reappears. If you take the address of something (pretty much anywhere in the function) the compiler will most likely refuse to keep the value in a register - if you took the address someone else might be keeping a pointer and changing the value through it. Dominic Sweetman dom@algor.co.uk From tim@cobaltmicro.com Wed Jun 4 22:46:26 1997 Received-Date: Wed, 4 Jun 1997 22:46:24 +0200 (MET DST) Received: from [205.179.228.26] by viavision.com with ESMTP (Apple Internet Mail Server 1.1.1); Wed, 4 Jun 1997 12:57:00 -0800 X-Sender: tim@mail.cobaltmicro.com (Unverified) Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 4 Jun 1997 13:56:43 -0800 To: linux-mips@fnet.fr From: Timothy Stonis Subject: Compiler bug? Content-Length: 840 Lines: 27 Hi All, I've got a possible compiler bug I was wondering you could help me with. Here's what I'm seeing in two places in the code (and who knows where else): In fork.c there is: if (copy_mm(clone_flags,p)) goto bad_fork_cleanup_sighand; On entering this line of code, my "p" is valid (0x80fdb810) on exit from the code it is invalid (0xFFFFFFF). If I put the following code immediately after the call: p = *(&p); My pointer magically reappears. I get the same fun behavior in dup_mmap() surrounding the flush_tlb_mm() call (this is a 2.1.36 kernel). Maybe the two are related? I'm running this on a RM5230. I thought it might be a cache problem, but I've run the code with caches off and get the same behavior. I'm compiling with the default CFLAGS... and using gcc 2.7.2-3 and binutils 2.7. Does anyone have any ideas? _Tim From ryan@ravage.labs.gmu.edu Thu Jun 5 00:50:02 1997 Received-Date: Thu, 5 Jun 1997 00:50:01 +0200 (MET DST) Received: from localhost (ryan@localhost) by ravage.labs.gmu.edu (8.8.3/8.8.3) with SMTP id SAA07897 for ; Wed, 4 Jun 1997 18:50:39 -0400 Date: Wed, 4 Jun 1997 18:50:39 -0400 (EDT) From: Ryan Rafferty To: linux-mips@fnet.fr Subject: libc In-Reply-To: <199706022202.AAA01985@alpha.franken.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 918 Lines: 20 Since the TLB code for the Magnum is fubar, I'm sticking with the much-outdated 2.0.21 kernel until either I or someone else can figure out how to fix 2.1.36. With that in mind, I'm looking for the version of libc that will work with the '.21 kernel. On fnet, I found that the latest libc in the archive was released on 06/19/96 (June 19, 1996) but I haven't unpacked it yet to see which version it is. If I recompile the userland packages against libc-960619, will the 2.0.21 kernel be able to boot to a shell? PS--when I received the free AUI->10b2 transceiver that Lantronix so nicely gave away, I recompiled a kernel to include support for the Sonic ethernet controller, but the kernel couldn't find it on my Magnum. I suppose this may be a discrepency between the Magnums and the Olivetti, or because I'm using an outdated kernel. In any case, the ne2000 driver works well. Is mise le meas, Ryan Rafferty From ralf@Julia.DE Thu Jun 5 01:11:17 1997 Received-Date: Thu, 5 Jun 1997 01:11:15 +0200 (MET DST) Received: from kernel.panic.julia.de (kernel.panic.julia.de [194.221.49.153]) by alles.intern.julia.de (8.8.5/8.8.5) with ESMTP id AAA21003 for ; Thu, 5 Jun 1997 00:05:19 +0200 From: Ralf Baechle Received: (from ralf@localhost) by kernel.panic.julia.de (8.8.4/8.8.4) id BAA14654 for linux-mips@fnet.fr; Thu, 5 Jun 1997 01:03:22 +0200 Message-Id: <199706042303.BAA14654@kernel.panic.julia.de> Subject: Re: libc To: linux-mips@fnet.fr Date: Thu, 5 Jun 1997 01:03:21 +0200 (MET DST) In-Reply-To: from "Ryan Rafferty" at Jun 4, 97 06:50:39 pm MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Length: 1358 Lines: 30 > Since the TLB code for the Magnum is fubar, I'm sticking with the > much-outdated 2.0.21 kernel until either I or someone else can figure out > how to fix 2.1.36. With that in mind, I'm looking for the version of libc > that will work with the '.21 kernel. On fnet, I found that the latest > libc in the archive was released on 06/19/96 (June 19, 1996) but I haven't > unpacked it yet to see which version it is. libc-960619 says that it is a libc snapshot. The source are not related to any particular version. > If I recompile the userland packages against libc-960619, will the 2.0.21 > kernel be able to boot to a shell? Most programs will run at least somehow. Note that between libc-960619 and GNU libc 2.0.x are worlds in term of reliability. There are as well some incompatibilities. I've uploaded Sources of GNU libc 2.0.1 which should be available at fnet and kernel.panic as libc-2.0.1.targ.gz. > PS--when I received the free AUI->10b2 transceiver that Lantronix so > nicely gave away, I recompiled a kernel to include support for the Sonic > ethernet controller, but the kernel couldn't find it on my Magnum. I > suppose this may be a discrepency between the Magnums and the Olivetti, or > because I'm using an outdated kernel. In any case, the ne2000 driver > works well. Yuck. It works just great on both Acer and M700. Ralf From engel@numerik.math.uni-siegen.de Thu Jun 5 11:21:06 1997 Received-Date: Thu, 5 Jun 1997 11:21:05 +0200 (MET DST) Received: from hilbert.numerik.math.uni-siegen.de (hilbert.numerik.math.uni-siegen.de [141.99.112.8]) by bernoulli.numerik.math.uni-siegen.de (Mailhost) with SMTP id LAA01105 for ; Thu, 5 Jun 1997 11:17:39 +0200 (MET DST) From: Michael Engel Message-Id: <9706050925.AA22069@hilbert.numerik.math.uni-siegen.de> Received: by hilbert.numerik.math.uni-siegen.de id AA22069; Thu, 5 Jun 97 11:25:01 +0200 Subject: Cross compiling To: linux-mips@fnet.fr Date: Thu, 5 Jun 1997 11:25:01 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1082 Lines: 26 Hi, I'm trying to setup cross-compilation tools on Solaris 2.5.1 and/or Digital Unix 4.0. Building the cross-compiler and binutils worked so far (though the 2.7.2 patches from fnet are not cleanly applicable ???). When I try to compile the 2.1.14-dec kernel, however, the compiler complains: In file included from init/main.c:13: /local/3/engel/cross/linux-2.1.14.2.dec/include/linux/types.h:31: warning: redef inition of `size_t' /usr/local/lib/gcc-lib/mips-dec-ultrix/2.7.2.1/include/stddef.h:17: warning: `si ze_t' previously declared here /local/3/engel/cross/linux-2.1.14.2.dec/include/linux/types.h:35: parse error be fore `ssize_t' /local/3/engel/cross/linux-2.1.14.2.dec/include/linux/types.h:35: warning: data definition has no type or storage class /local/3/engel/cross/linux-2.1.14.2.dec/include/linux/types.h:39: warning: redef inition of `ptrdiff_t' /usr/local/lib/gcc-lib/mips-dec-ultrix/2.7.2.1/include/stddef.h:14: warning: `pt rdiff_t' previously declared here So, there seems to be something wrong with the include files ... Any hints ??? regards, Michael From linux@informatik.uni-koblenz.de Thu Jun 5 12:21:06 1997 Received-Date: Thu, 5 Jun 1997 12:21:05 +0200 (MET DST) Received: from thoma (linux@thoma.uni-koblenz.de [141.26.4.61]) by informatik.uni-koblenz.de (8.8.5/8.6.9) with SMTP id MAA02051 for ; Thu, 5 Jun 1997 12:14:18 +0200 (MEST) From: Systemkennung Linux Message-Id: <199706051014.MAA02051@informatik.uni-koblenz.de> Received: by thoma (SMI-8.6/KO-2.0) id MAA03679; Thu, 5 Jun 1997 12:14:16 +0200 Subject: Re: Cross compiling To: linux-mips@fnet.fr Date: Thu, 5 Jun 1997 12:14:15 +0200 (MET DST) In-Reply-To: <9706050925.AA22069@hilbert.numerik.math.uni-siegen.de> from "Michael Engel" at Jun 5, 97 11:25:01 am MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Length: 1153 Lines: 28 > > > Hi, > > I'm trying to setup cross-compilation tools on Solaris 2.5.1 and/or Digital > Unix 4.0. Building the cross-compiler and binutils worked so far (though the > 2.7.2 patches from fnet are not cleanly applicable ???). When I try to compile > the 2.1.14-dec kernel, however, the compiler complains: > > In file included from init/main.c:13: > /local/3/engel/cross/linux-2.1.14.2.dec/include/linux/types.h:31: warning: redef > inition of `size_t' > /usr/local/lib/gcc-lib/mips-dec-ultrix/2.7.2.1/include/stddef.h:17: warning: `si > ze_t' previously declared here > /local/3/engel/cross/linux-2.1.14.2.dec/include/linux/types.h:35: parse error be > fore `ssize_t' > /local/3/engel/cross/linux-2.1.14.2.dec/include/linux/types.h:35: warning: data > definition has no type or storage class > /local/3/engel/cross/linux-2.1.14.2.dec/include/linux/types.h:39: warning: redef > inition of `ptrdiff_t' > /usr/local/lib/gcc-lib/mips-dec-ultrix/2.7.2.1/include/stddef.h:14: warning: `pt > rdiff_t' previously declared here > > So, there seems to be something wrong with the include files ... Any hints ??? You´re using the Ultrix GCC ... Ralf From engel@numerik.math.uni-siegen.de Thu Jun 5 15:36:15 1997 Received-Date: Thu, 5 Jun 1997 15:36:15 +0200 (MET DST) Received: from hilbert.numerik.math.uni-siegen.de (hilbert.numerik.math.uni-siegen.de [141.99.112.8]) by bernoulli.numerik.math.uni-siegen.de (Mailhost) with SMTP id NAA01132 for ; Thu, 5 Jun 1997 13:55:34 +0200 (MET DST) From: Michael Engel Message-Id: <9706051202.AA22327@hilbert.numerik.math.uni-siegen.de> Received: by hilbert.numerik.math.uni-siegen.de id AA22327; Thu, 5 Jun 97 14:02:57 +0200 Subject: Re: Cross compiling To: linux-mips@fnet.fr Date: Thu, 5 Jun 1997 14:02:56 +0200 (MET DST) In-Reply-To: <199706051014.MAA02051@informatik.uni-koblenz.de> from "Systemkennung Linux" at Jun 5, 97 12:14:15 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 361 Lines: 10 > > You´re using the Ultrix GCC ... > Ugh, yes, _that_ was a cross-compiler setup for Ultrix ;), but the effect was the same when I configured gcc for mips-mipsel-linux ... I wasn't able to apply the gcc patches from ftp.fnet.fr correctly, that _may_ cause the problems. Do you have a tar file with the patched gcc sources anywhere, Ralf ? regards, Michael From linux@informatik.uni-koblenz.de Thu Jun 5 16:10:04 1997 Received-Date: Thu, 5 Jun 1997 16:09:29 +0200 (MET DST) Received: from thoma (linux@thoma.uni-koblenz.de [141.26.4.61]) by informatik.uni-koblenz.de (8.8.5/8.6.9) with SMTP id QAA10678 for ; Thu, 5 Jun 1997 16:08:01 +0200 (MEST) From: Systemkennung Linux Message-Id: <199706051408.QAA10678@informatik.uni-koblenz.de> Received: by thoma (SMI-8.6/KO-2.0) id QAA07485; Thu, 5 Jun 1997 16:07:58 +0200 Subject: Re: Cross compiling To: linux-mips@fnet.fr Date: Thu, 5 Jun 1997 16:07:57 +0200 (MET DST) In-Reply-To: <9706051202.AA22327@hilbert.numerik.math.uni-siegen.de> from "Michael Engel" at Jun 5, 97 02:02:56 pm MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Length: 638 Lines: 17 > Ugh, yes, _that_ was a cross-compiler setup for Ultrix ;), but the effect was > the same when I configured gcc for mips-mipsel-linux ... I wasn't able to apply > the gcc patches from ftp.fnet.fr correctly, that _may_ cause the problems. > Do you have a tar file with the patched gcc sources anywhere, Ralf ? Oh, yes, I can make a tar archive. Wanna download it: --- ftp.funet.fi ping statistics --- 662 packets transmitted, 400 packets received, 39% packet loss round-trip min/avg/max = 773.2/2337.6/5191.5 ms I guess no ... If the patch doesn´t apply it´s probably because You´ve did not pass the -p option to patch? Ralf From engel@numerik.math.uni-siegen.de Mon Jun 9 15:05:29 1997 Received-Date: Mon, 9 Jun 1997 15:05:27 +0200 (MET DST) Received: from hilbert.numerik.math.uni-siegen.de (hilbert.numerik.math.uni-siegen.de [141.99.112.8]) by bernoulli.numerik.math.uni-siegen.de (Mailhost) with SMTP id PAA01927 for ; Mon, 9 Jun 1997 15:01:58 +0200 (MET DST) From: Michael Engel Message-Id: <9706091309.AA25234@hilbert.numerik.math.uni-siegen.de> Received: by hilbert.numerik.math.uni-siegen.de id AA25234; Mon, 9 Jun 97 15:09:26 +0200 Subject: Re: Cross compiling To: linux-mips@fnet.fr Date: Mon, 9 Jun 1997 15:09:26 +0200 (MET DST) In-Reply-To: <199706051408.QAA10678@informatik.uni-koblenz.de> from "Systemkennung Linux" at Jun 5, 97 04:07:57 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 313 Lines: 12 Hi Ralf, > If the patch doesn´t apply it´s probably because You´ve did not pass the > -p option to patch? Problem solved ... I did use the -p option, but I did _not_ use gnu patch, but rather the Solaris one. These seem to have different opinions about how a diff file has to look ... regards, Michael From linux@informatik.uni-koblenz.de Mon Jun 9 16:36:14 1997 Received-Date: Mon, 9 Jun 1997 16:36:12 +0200 (MET DST) Received: from thoma (linux@thoma.uni-koblenz.de [141.26.4.61]) by informatik.uni-koblenz.de (8.8.5/8.6.9) with SMTP id QAA16684 for ; Mon, 9 Jun 1997 16:33:29 +0200 (MEST) From: Systemkennung Linux Message-Id: <199706091433.QAA16684@informatik.uni-koblenz.de> Received: by thoma (SMI-8.6/KO-2.0) id QAA17111; Mon, 9 Jun 1997 16:33:27 +0200 Subject: Re: Cross compiling To: linux-mips@fnet.fr Date: Mon, 9 Jun 1997 16:33:26 +0200 (MET DST) In-Reply-To: <9706091309.AA25234@hilbert.numerik.math.uni-siegen.de> from "Michael Engel" at Jun 9, 97 03:09:26 pm MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Length: 783 Lines: 21 > > > Hi Ralf, > > > If the patch doesn´t apply it´s probably because You´ve did not pass the > > -p option to patch? > > Problem solved ... I did use the -p option, but I did _not_ use gnu patch, > but rather the Solaris one. These seem to have different opinions about > how a diff file has to look ... (I now can see The ExSolarinator grin once again :-) There is a couple more of vendor utilities that you should exchange if you want to use the Linux etc. sources with least possible changes. Among them the findutils, bash (install bash as /bin/bash), diff (Stun's diff / patch doen't know about unified context diff; diff has bugs that can turn your live into hell), GNU M4, gawk and some more. In fact, do yourself a favour and install all the GNU stuff. Ralf From engel@numerik.math.uni-siegen.de Mon Jun 9 22:19:50 1997 Received-Date: Mon, 9 Jun 1997 22:19:48 +0200 (MET DST) Received: from hilbert.numerik.math.uni-siegen.de (hilbert.numerik.math.uni-siegen.de [141.99.112.8]) by bernoulli.numerik.math.uni-siegen.de (Mailhost) with SMTP id WAA02102 for ; Mon, 9 Jun 1997 22:16:20 +0200 (MET DST) From: Michael Engel Message-Id: <9706092023.AA25522@hilbert.numerik.math.uni-siegen.de> Received: by hilbert.numerik.math.uni-siegen.de id AA25522; Mon, 9 Jun 97 22:23:48 +0200 Subject: DS2100 woes ... To: linux-mips@fnet.fr Date: Mon, 9 Jun 1997 22:23:48 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 2001 Lines: 44 Hi all, first the good news: Dave Voth, the former chief developer of the DECstation 5000/120,125,133 has found some documentation on these machines and is willing to send it to me (hmmm, I didn't tell him I'm living in Germany - perhaps he better sends it to Maddog ???). I finally have a DECstation 2100 of my own here - 24 MB RAM, mono frame buffer and a HUGE RZ23 hard disk ;) (about 100MB, I think) - thanks to my programming languages professor here (who is also using Linux at home ;-)) which I'm trying to set up now. I tried to run the 2.1.14.2 kernel on a DS3100 at University this afternoon. The kernel loads and then does some _very_ funny things: - No output whatsoever is made - I can press return several times. All characters I type in are echoed. After pressing return several times, I get part of the output of the printk of the cache sizes. After that, the machine crashes. I _think_ the number of returns I have to press is related to the number of printk statements that were executed before that cache probing line. (I removed one of the printk's and had to press return one time less - this was reproducable). I yet have to reproduce this on the 2100 here - on this machine, the kernel hangs completely. This may be related to the fact that I use a self-built cross compiler on Solaris 2.5.1 at University and my intel Linux box with Ralf's cross-compile envrionment at home. So, I tried to load the 2.1.1 kernel which worked fine. (I got a defective DS2100 before, so I was suspicious ;-)). I added a call to a routine which simply clears the screen immediately after dec_entry - this routine is not executed ... _Very_ funny ... What may go wrong there ??? I'm totally confused ... On the subject of the defective DS2100 - this machine loads the kernel via tftp and then crashes somewhere in the boot ROM (address 0xbc....). That DECstation has a V7.00 PROM, the one I'm using now has a 7.01 PROM. May that cause the problems ??? regards, Michael From steven@pmc-sierra.bc.ca Tue Jun 10 00:06:39 1997 Received-Date: Tue, 10 Jun 1997 00:06:35 +0200 (MET DST) Received: from zephyr.pdx.pmc-sierra.bc.ca (root@zephyr.pdx.pmc-sierra.bc.ca [134.87.165.130]) by procyon.pmc-sierra.bc.ca (8.7.5/8.7.3) with ESMTP id PAA29251 for ; Mon, 9 Jun 1997 15:06:21 -0700 (PDT) Received: from rogue.pdx.pmc-sierra.bc.ca (rogue.pdx.pmc-sierra.bc.ca [134.87.165.172]) by zephyr.pdx.pmc-sierra.bc.ca (8.8.0/8.8.5) with ESMTP id PAA12919 for ; Mon, 9 Jun 1997 15:06:00 -0700 (PDT) Received: from rogue (localhost.pdx.pmc-sierra.bc.ca [127.0.0.1]) by rogue.pdx.pmc-sierra.bc.ca (8.8.0/8.8.5) with ESMTP id PAA03132 for ; Mon, 9 Jun 1997 15:05:58 -0700 (PDT) Sender: steven@pmc-sierra.bc.ca Message-ID: <339C7E45.6FE35942@pdx.pmc-sierra.bc.ca> Date: Mon, 09 Jun 1997 15:05:57 -0700 From: Steven Ringwald Organization: PMC-Sierra, Inc X-Mailer: Mozilla 4.0b5C (X11; I; SunOS 4.1.4 sun4m) MIME-Version: 1.0 To: linux-mips@fnet.fr Subject: Direction X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 226 Lines: 6 I have a MIPS Magnum 3300 box, and I was wondering if Linux/Mips has support for this processor yet, or if there are plans to support it in the near future. I am willing to help out in the porting process. Thank you! Steve From elias@scruznet.com Thu Jun 12 00:52:27 1997 Received-Date: Thu, 12 Jun 1997 00:52:26 +0200 (MET DST) Received: from [205.179.228.11] ([205.179.228.11]) by scruz.net (8.8.5/1.34) with SMTP id PAA27459 for ; Wed, 11 Jun 1997 15:52:23 -0700 (PDT) Message-Id: <199706112252.PAA27459@scruz.net> Subject: Re: Recently ... Date: Wed, 11 Jun 97 15:52:21 -0700 x-mailer: Claris Emailer 2.0, March 15, 1997 From: Elias Kesh To: Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Length: 324 Lines: 12 Great, we are trying to get Apache running on our R5230 based board and we are running into filesystem trouble. What filesystem are you using ? The only one I know of is the root-0.01 and we have been grabbing sources from everywhere and recompiling them but it's getting to be a long process. Elias Elias@Kesh.com From linux@hotel.uni-koblenz.de Thu Jun 12 13:47:30 1997 Received-Date: Thu, 12 Jun 1997 13:30:04 +0200 (MET DST) Received: (from linux@localhost) by hotel.uni-koblenz.de (8.8.3/8.8.3) id NAA04830 for linux-mips@fnet.fr; Thu, 12 Jun 1997 13:28:12 +0200 From: Linux Support Message-Id: <199706121128.NAA04830@hotel.uni-koblenz.de> Subject: Re: Recently ... To: linux-mips@fnet.fr Date: Thu, 12 Jun 1997 13:28:10 +0200 (MEST) In-Reply-To: <199706112252.PAA27459@scruz.net> from "Elias Kesh" at Jun 11, 97 03:52:21 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 510 Lines: 11 > Great, we are trying to get Apache running on our R5230 based board and > we are running into filesystem trouble. What filesystem are you using ? > The only one I know of is the root-0.01 and we have been grabbing sources > from everywhere and recompiling them but it's getting to be a long > process. The filesystem he is using is based on what David Miller produced for the Indy port. It's consists only of big endian binaries and has never been published except to a number of Indy hackers. Ralf From ralf@informatik.uni-koblenz.de Mon Jun 16 16:34:58 1997 Received-Date: Mon, 16 Jun 1997 16:33:31 +0200 (MET DST) Received: from thoma (ralf@thoma.uni-koblenz.de [141.26.4.61]) by informatik.uni-koblenz.de (8.8.5/8.6.9) with SMTP id QAA03690; Mon, 16 Jun 1997 16:28:22 +0200 (MEST) From: Ralf Baechle Message-Id: <199706161428.QAA03690@informatik.uni-koblenz.de> Received: by thoma (SMI-8.6/KO-2.0) id QAA20906; Mon, 16 Jun 1997 16:28:18 +0200 Subject: GCC 2.7.2-4 Date: Mon, 16 Jun 1997 16:28:16 +0200 (MET DST) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Length: 151 Lines: 6 Hi all, GCC 2.7.2 does not build and install the files crtbegin{S}.o / crtend{S}.o that GNU libc 2.0.4 needs. I'll post a new GCC patch rsn. Ralf From klynn@santacruz.org Wed Jun 18 21:50:01 1997 Received-Date: Wed, 18 Jun 1997 21:49:58 +0200 (MET DST) Received: by surfwall.surfsoft.com; id NAA07692; Wed, 18 Jun 1997 13:00:38 -0700 Received: from surfdog-nts.surfsoft.com(165.227.30.3) by surfwall.surfsoft.com via smap (V3.1.1) id xma007685; Wed, 18 Jun 97 13:00:27 -0700 Received: from edu by surfdog-nts.surfsoft.com (5.x/SMI-SVR4) id AA12692; Wed, 18 Jun 1997 12:49:39 -0700 Sender: klynn@santacruz.org Message-Id: <33A83B6F.659F@santacruz.org> Date: Wed, 18 Jun 1997 12:47:59 -0700 From: Kevin Lynn Reply-To: wayhigh@santacruz.org X-Mailer: Mozilla 3.0 (X11; I; SunOS 5.5.1 sun4u) Mime-Version: 1.0 To: linux-mips@fnet.fr Subject: Olivetti M700-10 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 580 Lines: 14 WOW! I just checked this because it had been awhile since I looked to see if the Olivetti M700-10 is supported by any linux and I just saw that it is! I'm completely amazed.. I managed to procure a large amount of them (56 of them) back in '95 for $25/each for my at the time employer.. I still happen to have one of them that I decided to keep for myself. Just thought I'd ask how many people actually run MIPS linux with the olivetti M700-10, and if there's anyone out there that would be interested in giving me some help in getting it installed on my old olivetti. Wayhigh From sayer@eclipse.nsp Fri Jun 20 17:52:50 1997 Received-Date: Fri, 20 Jun 1997 17:52:49 +0200 (MET DST) Received: from imaginet.fr by moria.imaginet.fr via ESMTP (950215.SGI.8.6.10/911001.SGI) for id RAA11376; Fri, 20 Jun 1997 17:53:49 +0200 Received: from eclipse.nsp (cyber98-3.paris.imaginet.fr [195.68.3.98]) by imaginet.fr (8.7.5/8.7.31) with ESMTP id RAA22975 for ; Fri, 20 Jun 1997 17:52:34 +0200 (METDST) Received: from eclipse (localhost [127.0.0.1]) by eclipse.nsp (8.8.4/8.8.4) with ESMTP id RAA27457 for ; Fri, 20 Jun 1997 17:51:41 +0200 Message-Id: <199706201551.RAA27457@eclipse.nsp> X-Mailer: exmh version 1.6.7 05/05/96 To: linux-mips@fnet.fr Subject: LinuxMips on SNI RM200 From: Nicolas.Sayer@inria.fr Reply-To: Nicolas.Sayer@inria.fr Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 20 Jun 1997 17:51:41 +0200 Sender: sayer@eclipse.nsp Content-Length: 600 Lines: 15 I've spent two weeks trying to install a cross-compiler on my Linux-i486, no luck... Would anyone have a kernel, some info, or anything on this type of architecture ? thanks -=- Nicolas Sayer -=- _ _ - Computer Scientist - Paris - Tel: 33 1.45.20.56.90 ( )_( ) e-mails: sayer@imaginet.fr Fax: 33 1.45.25.10.39 \. ./ \ Nicolas.Sayer@inria.fr Cell: 33 6.60.42.42.45____=.=__ \___http://www.imaginet.fr/~sayer m " m _/ Linux & clones / LaTeX / C / TCP/IP / HTML / Roger Waters K.Kieslowski / Cigs / Guiness... & NOTHING else! From cdemps@lsumc.edu Fri Jun 20 18:32:32 1997 Received-Date: Fri, 20 Jun 1997 18:32:16 +0200 (MET DST) Received: from [155.58.112.211] by sarah.ocs.lsumc.edu (post.office MTA v2.0 0813 ID# 0-11395) with SMTP id AAA114 for ; Fri, 20 Jun 1997 11:32:03 -0500 Message-ID: <33AAB216.5CBB@lsumc.edu> Date: Fri, 20 Jun 1997 11:38:46 -0500 From: cdemps@lsumc.edu (Dempsey, Charles) Reply-To: cdemps@lsumc.edu Organization: Dept Pharmacology, LSUMC-S X-Mailer: Mozilla 2.02 (Macintosh; I; PPC) MIME-Version: 1.0 To: linux-mips@fnet.fr Subject: Re: LinuxMips on SNI RM200 References: <199706201551.RAA27457@eclipse.nsp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 407 Lines: 13 Nicolas.Sayer@inria.fr wrote: > > I've spent two weeks trying to install a cross-compiler on my Linux-i486, no > luck... > Would anyone have a kernel, some info, or anything on this type of > architecture ? I'm showing my ignorance here but, is a SNI RM200 an Intel machine? We should publish that crossdevelopment tools HOWTO, Ralf. I found a couple of typos in it, but I think nothing fatal. Charles From ralf@Julia.DE Fri Jun 20 21:30:31 1997 Received-Date: Fri, 20 Jun 1997 21:30:26 +0200 (MET DST) Received: from kernel.panic.julia.de (kernel.panic.julia.de [194.221.49.153]) by alles.intern.julia.de (8.8.5/8.8.5) with ESMTP id UAA27412; Fri, 20 Jun 1997 20:19:05 +0200 From: Ralf Baechle Received: (from ralf@localhost) by kernel.panic.julia.de (8.8.4/8.8.4) id VAA31096; Fri, 20 Jun 1997 21:18:53 +0200 Message-Id: <199706201918.VAA31096@kernel.panic.julia.de> Subject: Re: LINUX MIPS To: linux-mips@fnet.fr, traxtek@geocities.com Date: Fri, 20 Jun 1997 21:18:53 +0200 (MET DST) In-Reply-To: <33AB7E85.14D3@geocities.com> from "Darien Lambert" at Jun 21, 97 00:11:01 am MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Length: 354 Lines: 8 > hey i want to know how to get on the linux mips mailing list. And i > would like further information regarding LINUX for N64, if u can provide > me with a homepage for the info or something else i would apreciate it The N64 is not supported yet but someone is taking a stab at it. So if Nitendo-Linux ever happens it will still take a while. Ralf From ralf@Julia.DE Fri Jun 20 21:34:56 1997 Received-Date: Fri, 20 Jun 1997 21:34:51 +0200 (MET DST) Received: from kernel.panic.julia.de (kernel.panic.julia.de [194.221.49.153]) by alles.intern.julia.de (8.8.5/8.8.5) with ESMTP id UAA27527 for ; Fri, 20 Jun 1997 20:24:51 +0200 From: Ralf Baechle Received: (from ralf@localhost) by kernel.panic.julia.de (8.8.4/8.8.4) id VAA31107 for linux-mips@fnet.fr; Fri, 20 Jun 1997 21:24:39 +0200 Message-Id: <199706201924.VAA31107@kernel.panic.julia.de> Subject: Re: LinuxMips on SNI RM200 To: linux-mips@fnet.fr Date: Fri, 20 Jun 1997 21:24:39 +0200 (MET DST) In-Reply-To: <33AAB216.5CBB@lsumc.edu> from "Dempsey, Charles" at Jun 20, 97 11:38:46 am MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Length: 549 Lines: 18 Hi, > > I've spent two weeks trying to install a cross-compiler on my Linux-i486, no > > luck... > > Would anyone have a kernel, some info, or anything on this type of > > architecture ? > > I'm showing my ignorance here but, is a SNI RM200 an Intel machine? Of course not. It's a quite nice machine from SNI. I've got one and I'm very satisfied with it. > We should publish that crossdevelopment tools HOWTO, Ralf. I found a couple of > typos in it, but I think nothing fatal. Yes, you're right. I'm just a bit time handicaped ... Ralf From imp@village.org Fri Jun 20 21:41:51 1997 Received-Date: Fri, 20 Jun 1997 21:41:46 +0200 (MET DST) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0wf9Yz-0005yZ-00; Fri, 20 Jun 1997 13:41:41 -0600 To: linux-mips@fnet.fr Subject: Re: LINUX MIPS Cc: traxtek@geocities.com In-reply-to: Your message of "Fri, 20 Jun 1997 21:18:53 +0200." <199706201918.VAA31096@kernel.panic.julia.de> References: <199706201918.VAA31096@kernel.panic.julia.de> Date: Fri, 20 Jun 1997 13:41:41 -0600 From: Warner Losh Message-Id: Content-Length: 390 Lines: 9 In message <199706201918.VAA31096@kernel.panic.julia.de> Ralf Baechle writes: : The N64 is not supported yet but someone is taking a stab at it. So if : Nitendo-Linux ever happens it will still take a while. Would you need the special developer's kit to run Linux on the N64? Or would it run somehow off a cdrom or something. How would disk/network devices fit into the picture? Warner From ralf@Julia.DE Fri Jun 20 21:55:03 1997 Received-Date: Fri, 20 Jun 1997 21:54:58 +0200 (MET DST) Received: from kernel.panic.julia.de (kernel.panic.julia.de [194.221.49.153]) by alles.intern.julia.de (8.8.5/8.8.5) with ESMTP id UAA27769 for ; Fri, 20 Jun 1997 20:44:56 +0200 From: Ralf Baechle Received: (from ralf@localhost) by kernel.panic.julia.de (8.8.4/8.8.4) id VAA31137 for linux-mips@fnet.fr; Fri, 20 Jun 1997 21:44:44 +0200 Message-Id: <199706201944.VAA31137@kernel.panic.julia.de> Subject: Re: LINUX MIPS To: linux-mips@fnet.fr Date: Fri, 20 Jun 1997 21:44:44 +0200 (MET DST) In-Reply-To: from "Warner Losh" at Jun 20, 97 01:41:41 pm MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Length: 763 Lines: 17 Hi, > In message <199706201918.VAA31096@kernel.panic.julia.de> Ralf Baechle writes: > : The N64 is not supported yet but someone is taking a stab at it. So if > : Nitendo-Linux ever happens it will still take a while. > > Would you need the special developer's kit to run Linux on the N64? > Or would it run somehow off a cdrom or something. How would > disk/network devices fit into the picture? A lot of unanswered questions. I'm in mail contact with someone who is trying to figure all the things involved with a N64 port. But forgive, as long as there is nothing available I'll treat such a project as vaporware. The N64 btw. has some extension capabilites, so the project is not as impossible as it may sound; we also support it's processor. Ralf From ryan@ravage.labs.gmu.edu Fri Jun 20 22:16:02 1997 Received-Date: Fri, 20 Jun 1997 22:16:01 +0200 (MET DST) Received: from localhost (ryan@localhost) by ravage.labs.gmu.edu (8.8.3/8.8.3) with SMTP id QAA08453 for ; Fri, 20 Jun 1997 16:17:25 -0400 Date: Fri, 20 Jun 1997 16:17:25 -0400 (EDT) From: Ryan Rafferty To: linux-mips@fnet.fr Subject: Re: LINUX MIPS In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 1100 Lines: 25 On Fri, 20 Jun 1997, Warner Losh wrote: > In message <199706201918.VAA31096@kernel.panic.julia.de> Ralf Baechle writes: > : The N64 is not supported yet but someone is taking a stab at it. So if > : Nitendo-Linux ever happens it will still take a while. > > Would you need the special developer's kit to run Linux on the N64? > Or would it run somehow off a cdrom or something. How would > disk/network devices fit into the picture? Funny thing is, I believe that the developer's kit is composed mostly of FSF software--gcc, gas, etc. However, getting the compiled code onto a cartridge may well be proprietary until someone reverse engineers them. It didn't take long for people to reverse engineer many components of the Super Nintendo, though, so I wouldn't be surprised if information regarding the N64's peripheral interface becomes availible. Then, if you're industrious enough, you could throw together your own periphs--ethernet, SCSI, whatever you have too much time for, if you have an EE degree =). When the bulky drive comes out, it could act much like a small hard disk. Ryan From miguel@athena.nuclecu.unam.mx Fri Jun 20 22:59:33 1997 Received-Date: Fri, 20 Jun 1997 22:59:29 +0200 (MET DST) Received: (from miguel@localhost) by athena.nuclecu.unam.mx (8.8.5/8.8.5) id PAA16988; Fri, 20 Jun 1997 15:47:01 -0500 Date: Fri, 20 Jun 1997 15:47:01 -0500 Message-Id: <199706202047.PAA16988@athena.nuclecu.unam.mx> From: Miguel de Icaza To: linux-mips@fnet.fr CC: traxtek@geocities.com In-reply-to: (message from Warner Losh on Fri, 20 Jun 1997 13:41:41 -0600) Subject: Re: LINUX MIPS X-Quote: If at first you don't succeed, redefine success. Content-Length: 244 Lines: 8 > Or would it run somehow off a cdrom or something. How would > disk/network devices fit into the picture? You can buy hard disk expansions or plug scsi devices to it. Or so I am told by Todd (who is attempting the port as of now). Miguel From ryan@ravage.labs.gmu.edu Sat Jun 21 00:37:20 1997 Received-Date: Sat, 21 Jun 1997 00:37:19 +0200 (MET DST) Received: from localhost (ryan@localhost) by ravage.labs.gmu.edu (8.8.3/8.8.3) with SMTP id SAA09214 for ; Fri, 20 Jun 1997 18:38:44 -0400 Date: Fri, 20 Jun 1997 18:38:44 -0400 (EDT) From: Ryan Rafferty Reply-To: Ryan Rafferty To: linux-mips@fnet.fr Subject: glibc In-Reply-To: <199706201918.VAA31096@kernel.panic.julia.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 753 Lines: 19 Having been frustrated in my last attempt to recompile a working Linux/MIPS filesystem, I nuked my Linux/i386 system, reinstalled Debian from scratch, and decided to get back on to the bull's back. I grabbed the precompiled binutils and cross-compiler, and untarred them from the root directory. Then I untarred glibc-2.0.1 (again, from ftp.fnet.fr) in my home directory. Now configure seems to be confused; I made a file "configparms" and put the definitions for CC=mipsel-linux-gcc, etc in it. Then I typed "configure mipsel-linux" but it doesn't appear to be incorporating the configparms definitions. Instead, it tries to use plain old gcc, ar, as, etc, instead of mipsel-linux-gcc, mipsel-linux-as, etc. Am I doing something wrong? Ryan From ralf@Julia.DE Sat Jun 21 00:54:56 1997 Received-Date: Sat, 21 Jun 1997 00:54:53 +0200 (MET DST) Received: from kernel.panic.julia.de (kernel.panic.julia.de [194.221.49.153]) by alles.intern.julia.de (8.8.5/8.8.5) with ESMTP id XAA29830 for ; Fri, 20 Jun 1997 23:44:53 +0200 From: Ralf Baechle Received: (from ralf@localhost) by kernel.panic.julia.de (8.8.4/8.8.4) id AAA31499 for linux-mips@fnet.fr; Sat, 21 Jun 1997 00:44:42 +0200 Message-Id: <199706202244.AAA31499@kernel.panic.julia.de> Subject: Networking in 2.1.36 To: linux-mips@fnet.fr Date: Sat, 21 Jun 1997 00:44:42 +0200 (MET DST) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Length: 560 Lines: 17 Here a little patch for whoever it was who reported the telnet lockups. Ralf Index: linux/arch/mips/kernel/syscalls.h diff -u linux/arch/mips/kernel/syscalls.h:1.2 linux/arch/mips/kernel/syscalls.h:1.3 --- linux/arch/mips/kernel/syscalls.h:1.2 Sun Jun 8 09:02:55 1997 +++ linux/arch/mips/kernel/syscalls.h Thu Jun 19 20:59:55 1997 @@ -174,7 +174,6 @@ SYS(sys_munlock, 2) /* 4155 */ SYS(sys_mlockall, 1) SYS(sys_munlockall, 0) -SYS(sys_nfsservctl, 3) SYS(sys_sched_setparam,2) SYS(sys_sched_getparam,2) SYS(sys_sched_setscheduler,3) /* 4160 */ From linux@informatik.uni-koblenz.de Sat Jun 21 03:07:42 1997 Received-Date: Sat, 21 Jun 1997 03:07:33 +0200 (MET DST) Received: from thoma (linux@thoma.uni-koblenz.de [141.26.4.61]) by informatik.uni-koblenz.de (8.8.5/8.6.9) with SMTP id DAA07865 for ; Sat, 21 Jun 1997 03:07:20 +0200 (MEST) From: Systemkennung Linux Message-Id: <199706210107.DAA07865@informatik.uni-koblenz.de> Received: by thoma (SMI-8.6/KO-2.0) id DAA06283; Sat, 21 Jun 1997 03:07:20 +0200 Subject: Re: glibc To: linux-mips@fnet.fr Date: Sat, 21 Jun 1997 03:07:19 +0200 (MET DST) In-Reply-To: from "Ryan Rafferty" at Jun 20, 97 06:38:44 pm MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Length: 4113 Lines: 79 > Having been frustrated in my last attempt to recompile a working > Linux/MIPS filesystem, I nuked my Linux/i386 system, reinstalled Debian > from scratch, and decided to get back on to the bull's back. > > I grabbed the precompiled binutils and cross-compiler, and untarred them > from the root directory. Then I untarred glibc-2.0.1 (again, from > ftp.fnet.fr) in my home directory. Now configure seems to be confused; I > made a file "configparms" and put the definitions for CC=mipsel-linux-gcc, > etc in it. Then I typed "configure mipsel-linux" but it doesn't appear to > be incorporating the configparms definitions. Instead, it tries to use > plain old gcc, ar, as, etc, instead of mipsel-linux-gcc, mipsel-linux-as, > etc. The command "configure mipsel-linux" configures the library for native compilation _ON_ a mipsel-linux host _FOR_ a mipsel-linux host. Which is not what you wanted to do. Appended is my configparms file. Far more complicated than necessary and full of old stuff. Put the file in the directory in which you want to compile glibc. Then configure libc with some variation of the following command: mkdir objects; cd objects ( setenv CC "mipsel-linux-gcc -pipe" && setenv BUILD_CC gcc && ../configure --prefix=/usr --enable-shared --enable-profile=no --enable-omitfp --enable-add-ons=crypt,linuxthreads,localedata --build=mips-mips-irix6.2 mipsel-linux ) (This command assumes that you're using tcsh. Bash users of course know how to do this themselfes ...) This says libc to use mipsel-linux-gcc as the compiler and gcc for native compiles, then runs configure. I always build both byteorder flavours of libc, so I compile in a subdirectory of the libc sources. This also enables full optimization of the library. You don't compile under IRIX, so replace "mips-mips-irix6.2" by the configuration name that you're using to build libc on, that's i486-linux in your case. Configured as above a build takes about 90min on a 133MHz Indy, so when you've enter the make command it's time to have a good cup of coffee ... When building is finished you have to install the library into the NFS root directory of your MIPS box. In order to do that type something (as root) like "make install_root=/tftpboot/ install". This commands takes another 10min on a 133MHz Indy, so it's the time to refill you coffee cup ... Warning: take care of what you type when you install the library or you might overinstall you Intel libc binaries with MIPS binaries! Have fun, Ralf begin 644 configparms.gz M'XL("$TAJS,"`V-O;F9I9W!AL7WS!;SUI4B@,#D^\^$S,]ENMO17 M+:TD;TAIYT73X'&SW?`_66=EJ1[I9@/#EOZH)77"UV1*\OQL365%BW->6D#Q MEX0GVVNO6KG#&>N;HE"6;NBR4?L92^15CBY[9VDO<]$[2*X?)1Y[\6^D6Y'=.O/'&GC8SPGA+YAU^9!6JN*T?T- MO3F?I7G!LRT>9*9--M2FD9FP>:T>)$(Z2!>IX^T)OL&:"Y4W M/8Z5J)JCTJ"VQGCGK>@ZI:N/?`0!)UBZ&J1]F2S_^14EAZE"[&TLRG/=P:V6 M`Z&^5EB%!+SYR-4K`R1C`CB7;>XS1S:YQ+P0BOC'Y+!GQV4(Y#"M&- M)$.M\II:5=4>B46_IP! MXLOO1154OQV%$TH[*O]G0*ZGL*"*@B0$T7WL!^ZM2WLJ&XUP`GC?\#*X+5:9^ MG95N?B-%C(RE>=0[>6$KB0[&L9`L'*&CC3V$L(&'X83H9>=XC?Z(('H-Y")J M[**,$?3ZM/D3VBI[A&\Z#&+U%.Z.,BYQ8?29AQJ0"<+/0[7WID?48.[=XT1Y)IF.][U129JU$8YM)FLWJ%G<>S-;X+^7T^`H(8\&N[ MO))Z3`-)8G!^>$U+Z#K3-T4L]V#L/>&N0IOQ9O&R356GWXV/_(T4!5]487J, M6*PIX>JP"KF!'J3VO$PPGT-IA??]8"'*>C5JMK8F:N_(H](F9;OG-E=092<&:DR(2JC-<:$Q5V"*NJGQ6!4>\2"21:%NDT$&<)R MW`,WM+O:3%$Z7T"*NYH_<,)W0^;-]>;D.YG7AD[3!CS^<+^E5CO]<'+R]^8D MPGC;?9VP#)N9EM@TS^>4T;2$N26.8>XEW&RT3O=; Fri, 20 Jun 1997 12:13:49 -0700 (PDT) Message-ID: <33AB7E85.14D3@geocities.com> Date: Sat, 21 Jun 1997 00:11:01 -0700 From: Darien Lambert Reply-To: traxtek@geocities.com Organization: Trax X-Mailer: Mozilla 3.01Gold (Win16; I) MIME-Version: 1.0 To: linux-mips@fnet.fr Subject: LINUX MIPS Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 220 Lines: 5 hey i want to know how to get on the linux mips mailing list. And i would like further information regarding LINUX for N64, if u can provide me with a homepage for the info or something else i would apreciate it Jeff K From ryan@ravage.labs.gmu.edu Sun Jun 22 00:27:32 1997 Received-Date: Sun, 22 Jun 1997 00:27:31 +0200 (MET DST) Received: from localhost (ryan@localhost) by ravage.labs.gmu.edu (8.8.3/8.8.3) with SMTP id SAA19726 for ; Sat, 21 Jun 1997 18:29:04 -0400 Date: Sat, 21 Jun 1997 18:29:04 -0400 (EDT) From: Ryan Rafferty To: linux-mips@fnet.fr Subject: Re: glibc In-Reply-To: <199706210107.DAA07865@informatik.uni-koblenz.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 392 Lines: 12 I followed your instructions for building glibc, at least the configure part. Configure almost gets everything right, but then it dies, giving the following message: >checking for assembler global-symbol directive... UNKNOWN >configure: error: cannot determine asm global directive Is this a problem with the command line, or my local Linux configuration? Is mise le meas, Ryan Rafferty From linux@informatik.uni-koblenz.de Sun Jun 22 00:49:13 1997 Received-Date: Sun, 22 Jun 1997 00:48:54 +0200 (MET DST) Received: from thoma (linux@thoma.uni-koblenz.de [141.26.4.61]) by informatik.uni-koblenz.de (8.8.5/8.6.9) with SMTP id AAA18219 for ; Sun, 22 Jun 1997 00:48:26 +0200 (MEST) From: Systemkennung Linux Message-Id: <199706212248.AAA18219@informatik.uni-koblenz.de> Received: by thoma (SMI-8.6/KO-2.0) id AAA07054; Sun, 22 Jun 1997 00:48:23 +0200 Subject: Re: glibc To: linux-mips@fnet.fr Date: Sun, 22 Jun 1997 00:48:23 +0200 (MET DST) In-Reply-To: from "Ryan Rafferty" at Jun 21, 97 06:29:04 pm MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Length: 721 Lines: 20 Hi, > I followed your instructions for building glibc, at least the configure > part. Configure almost gets everything right, but then it dies, giving > the following message: > > >checking for assembler global-symbol directive... UNKNOWN > >configure: error: cannot determine asm global directive > > Is this a problem with the command line, or my local Linux configuration? It must be something with your local Linux configuration. Normally it should detect .globl as the asm global directive. Check the output of configure in the file config.log, maybe that helps. If not have fun ripping the configure script apart and see what goes wrong. Can you compile (not link!) a tiny program like "foo(){}"? Ralf From alfonso@borak.es Sun Jun 22 00:57:42 1997 Received-Date: Sun, 22 Jun 1997 00:57:33 +0200 (MET DST) Received: from ebro.borak.es by borak.es (SMI-8.6/SMI-SVR4) id BAA15414; Sun, 22 Jun 1997 01:01:26 +0200 Message-ID: <33AC5D4D.C82@borak.es> Date: Sun, 22 Jun 1997 01:01:33 +0200 From: Alfonso X-Mailer: Mozilla 3.01Gold (Win95; I) MIME-Version: 1.0 To: linux-mips@fnet.fr Subject: An Indy box Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 46 Lines: 2 I have an Indy box, how can i help???? thanks From ryan@ravage.labs.gmu.edu Sun Jun 22 02:11:11 1997 Received-Date: Sun, 22 Jun 1997 02:11:10 +0200 (MET DST) Received: from localhost (ryan@localhost) by ravage.labs.gmu.edu (8.8.3/8.8.3) with SMTP id UAA19893 for ; Sat, 21 Jun 1997 20:12:46 -0400 Date: Sat, 21 Jun 1997 20:12:46 -0400 (EDT) From: Ryan Rafferty To: linux-mips@fnet.fr Subject: Re: glibc In-Reply-To: <199706212248.AAA18219@informatik.uni-koblenz.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 666 Lines: 20 On Sun, 22 Jun 1997, Systemkennung Linux wrote: > > >checking for assembler global-symbol directive... UNKNOWN > > >configure: error: cannot determine asm global directive > > It must be something with your local Linux configuration. Normally > it should detect .globl as the asm global directive. Check the output > of configure in the file config.log, maybe that helps. If not have > fun ripping the configure script apart and see what goes wrong. Been there, done that =). I just, er, fudged that part by deleting the offending line. Now, at least, it gets past that part. > Can you compile (not link!) a tiny program like "foo(){}"? Yes. > Ralf > From lahaye@europe.far.cea.fr Tue Jun 24 13:46:33 1997 Received: from nenuphar.saclay.cea.fr (nenuphar.saclay.cea.fr [132.166.192.7]) by guadalquivir.fnet.fr with ESMTP (8.8.5/97.02.12/Guadalquivir); id NAA27695; Tue, 24 Jun 1997 13:46:31 +0200 (MET DST) Received-Date: Tue, 24 Jun 1997 13:46:31 +0200 (MET DST) From: lahaye@europe.far.cea.fr Received: from suisse.far.cea.fr by nenuphar.saclay.cea.fr (8.8.5/ CEANET-ROUTER-3.0) with SMTP id NAA03256 for ; Tue, 24 Jun 1997 13:46:27 +0200 (MET DST) Received: from europe.far.cea.fr by suisse.far.cea.fr (5.x/CEANET.2.0.1) id AA21557; Tue, 24 Jun 1997 13:44:58 +0200 Received: by europe.far.cea.fr (950413.SGI.8.6.12/PROTO-CEANET-3.0) id LAA27293 for linux-mips@fnet.fr; Tue, 24 Jun 1997 11:39:49 GMT Date: Tue, 24 Jun 1997 11:39:49 GMT Message-Id: <199706241139.LAA27293@europe.far.cea.fr> To: linux-mips@fnet.fr Subject: Linux MIPS RC3330 8MB Content-Length: 476 Lines: 15 Hello, A fez time ago I've heard about work being made on a loader for the MIPS RC3330 Box. Is there any thing I can beta test? I only have 8MB int it, so I can't do much more than tests. Thanks for answers. -- LAHAYE Olivier, Athésa - Ph.: 01.46.54.72.34 Fax: 01.46.54.75.80 mailto:olivier.lahaye@cea.fr [Sys Administrator CEA Fontenay FRANCE] mailto:olivier.lahaye@ramses.fdn.org [At Home] http://www.mygale.org/~lahaye/index.html (SORRY:only French at this time) From mhines@maas.net Thu Jun 26 07:27:57 1997 Received: from sun.maas.net (sun.maas.net [204.254.252.10]) by guadalquivir.fnet.fr with ESMTP (8.8.5/97.02.12/Guadalquivir); id HAA14037; Thu, 26 Jun 1997 07:27:57 +0200 (MET DST) Received-Date: Thu, 26 Jun 1997 07:27:57 +0200 (MET DST) Received: from juan.home.com ([128.194.136.75]) by sun.maas.net (Netscape Mail Server v2.02) with SMTP id AAA15528 for ; Thu, 26 Jun 1997 00:25:41 -0500 Message-Id: <3.0.1.32.19970626003053.0068a658@mail.maas.net> X-Sender: mhines@mail.maas.net X-Mailer: Windows Eudora Light Version 3.0.1 (32) Date: Thu, 26 Jun 1997 00:30:53 -0500 To: linux-mips@fnet.fr From: Marcus Hines Subject: Re: Linux MIPS RC3330 8MB In-Reply-To: <199706241139.LAA27293@europe.far.cea.fr> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Length: 354 Lines: 16 I have an ArcSystem Mips Magnum r4000sc with 16 megs of RAM 1 gig HD 19" SGI monitor sound card video with z-buffering AUI for 10baseT for sell $1000 neg. also i have an extra motherboard for it with processor but the bios chip is bad according to the guy who gave me the board has r4000 processor but no cards or ram in it anyone interested?????? From ryan@ravage.labs.gmu.edu Fri Jun 27 00:10:49 1997 Received: from ravage.labs.gmu.edu ([129.174.166.55]) by guadalquivir.fnet.fr with ESMTP (8.8.5/97.02.12/Guadalquivir); id AAA19535; Fri, 27 Jun 1997 00:10:48 +0200 (MET DST) Received-Date: Fri, 27 Jun 1997 00:10:48 +0200 (MET DST) Received: from localhost (ryan@localhost) by ravage.labs.gmu.edu (8.8.3/8.8.3) with SMTP id SAA00869 for ; Thu, 26 Jun 1997 18:11:10 -0400 Date: Thu, 26 Jun 1997 18:11:10 -0400 (EDT) From: Ryan Rafferty To: linux-mips@fnet.fr Subject: Re: Linux MIPS RC3330 8MB In-Reply-To: <3.0.1.32.19970626003053.0068a658@mail.maas.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 848 Lines: 31 I know this is an irritating question, but I'd like to know if you're willing to part out the system. For example, I'd love to buy the chassis (case, motherboard, chip) with the RAM, sound card, and video card, but I have no need for the monitor or hard disk. If you cannot part out the system, I would be interested in buying the non-functioning motherboard for $50, possibly higher. Thanks for your time, Ryan On Thu, 26 Jun 1997, Marcus Hines wrote: > I have an ArcSystem Mips Magnum r4000sc with > > 16 megs of RAM > 1 gig HD > 19" SGI monitor > sound card > video with z-buffering > AUI for 10baseT > > for sell $1000 neg. > > also i have an extra motherboard for it with processor but the > bios chip is bad according to the guy who gave me the board > has r4000 processor but no cards or ram in it > > anyone interested?????? > From dmills@noao.edu Sat Jun 28 03:40:35 1997 Received: from noao.edu (root@noao.edu [140.252.1.54]) by guadalquivir.fnet.fr with ESMTP (8.8.5/97.02.12/Guadalquivir); id DAA00479; Sat, 28 Jun 1997 03:40:33 +0200 (MET DST) Received-Date: Sat, 28 Jun 1997 03:40:33 +0200 (MET DST) Received: from plum (plum.tuc.noao.edu [140.252.1.95]) by noao.edu (8.8.5/8.8.5/SAG-14May97) with SMTP id SAA21226 for ; Fri, 27 Jun 1997 18:40:27 -0700 (MST) Sender: dmills@noao.edu Message-ID: <33B46B1A.41C67EA6@noao.edu> Date: Fri, 27 Jun 1997 18:38:34 -0700 From: Dave Mills Organization: NOAO (AURA) X-Mailer: Mozilla 3.0Gold (X11; I; SunOS 4.1.3_U1 sun4m) MIME-Version: 1.0 To: linux-mips@fnet.fr Subject: Linux on R3000 Decstations Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 555 Lines: 22 Hi there, Please add me to the linux-mips list. I have access to a Dec 5000/125 and 3100 that I would like to use Linux-Mips on. I have experience with Linux-x86 and SparcLinux and would like to assist the port. QUESTION 1 : Can we use code from NetBSD, as I beleive it already runs on pmax machines. Cheers, Dave Mills -- ------------------------------------- Dave Mills (NOAO, CCS) 950 N Cherry Ave, Tucson AZ 85719 USA Telephone : +1 (520) 318 8293 Fax : +1 (520) 318 8360 Office # : 105 ------------------------------------- From jofo@widow.enefecto.es Sat Jun 28 19:39:10 1997 Received: from widow.enefecto.es (widow.enefecto.es [194.140.166.2]) by guadalquivir.fnet.fr with SMTP (8.8.5/97.02.12/Guadalquivir); id TAA04614; Sat, 28 Jun 1997 19:39:09 +0200 (MET DST) Received-Date: Sat, 28 Jun 1997 19:39:09 +0200 (MET DST) Received: by widow.enefecto.es (950413.SGI.8.6.12/940406.SGI) for linux-mips@fnet.fr id TAA02828; Sat, 28 Jun 1997 19:39:07 +0200 From: "Jordi Fornes" Message-Id: <9706281939.ZM2826@widow.enefecto.es> Date: Sat, 28 Jun 1997 19:39:06 -0600 X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: linux-mips@fnet.fr Subject: can I help? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Length: 383 Lines: 13 Hi! I am very interesting in the Linux-Mips porting project, I administrate several SGI boxes, one of them is a Indigo R3000 . Let me know how can I help you, testing or programming. CU -- Jordi Fornes (jofo@enefecto.es) System manager VIDEO EFECTO, S.A. http://www.enefecto.es C/ALEGRE DE DALT, 86 tel. (+34 3) 213 56 16 08024 BARCELONA fax (+34 3) 219 77 59