From owner-linux-arm-kernel@lists.arm.linux.org.uk Mon Mar 6 21:05:48 2000 Received: (from majordomo@localhost) by parcelfarce.linux.theplanet.co.uk (8.9.3/8.9.3) id VAA11101 for linux-arm-kernel-outgoing; Mon, 6 Mar 2000 21:05:48 GMT Received: from crl.dec.com (crl.dec.com [192.58.206.2]) by parcelfarce.linux.theplanet.co.uk (8.9.3/8.9.3) with ESMTP id VAA11097 for ; Mon, 6 Mar 2000 21:05:46 GMT Received: from ims.crl.dec.com (ims.crl.dec.com [16.11.0.11]) by crl.dec.com (8.8.8/RWD-1.2) with ESMTP id QAA11418 for ; Mon, 6 Mar 2000 16:04:22 -0500 (EST) Received: by ims.crl.dec.com with Internet Mail Service (5.5.2650.21) id ; Mon, 6 Mar 2000 16:07:51 -0500 Message-ID: From: George France To: "'linux-arm-kernel@lists.arm.linux.org.uk'" Subject: Configuration menus Date: Mon, 6 Mar 2000 16:04:32 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-linux-arm-kernel@lists.arm.linux.org.uk Precedence: bulk In the kernel Configuration menus under: System and processor type: There are two (2) ARM system types: EBSA-110 FootBridge-based Under both system types there is support for: EBSA-285 CATS NetWinder Compaq Personal Server Should there just be one system type for the SA-110, with the FootBridge as an option underneath instead of its own section?? I would like to change the two(2) ARM systems types to one (1): SA-110 and then place the EBSA-110 and the FootBridge-based systems types under the SA-110 system type. Is there any reason why I should not modify the menus, to work this way?? Thank you in advance. --George George France, france@crl.dec.com Cambridge Research Laboratory, Compaq Computer Corporation One Kendall Square, Building 700 MS: CRL Cambridge, MA 02139 USA unsubscribe: body of `unsubscribe linux-arm-kernel' to majordomo@lists.arm.linux.org.uk From owner-linux-arm-kernel@lists.arm.linux.org.uk Mon Mar 6 21:52:20 2000 Received: (from majordomo@localhost) by parcelfarce.linux.theplanet.co.uk (8.9.3/8.9.3) id VAA11657 for linux-arm-kernel-outgoing; Mon, 6 Mar 2000 21:52:20 GMT Received: from caramon.arm.linux.org.uk (root@p45-magpie-gui.tch.enablis.net [194.168.180.45]) by parcelfarce.linux.theplanet.co.uk (8.9.3/8.9.3) with ESMTP id VAA11653 for ; Mon, 6 Mar 2000 21:52:18 GMT Received: from raistlin.arm.linux.org.uk (root@raistlin [192.168.0.3]) by caramon.arm.linux.org.uk (8.9.3/8.9.3) with ESMTP id VAA29718; Mon, 6 Mar 2000 21:50:49 GMT From: Russell King - ARM Linux Admin Received: (from linux@localhost) by raistlin.arm.linux.org.uk (8.7.4/8.7.3) id VAA01025; Mon, 6 Mar 2000 21:50:10 GMT Message-Id: <200003062150.VAA01025@raistlin.arm.linux.org.uk> Subject: Re: Configuration menus To: france@crl.dec.com (George France) Date: Mon, 6 Mar 2000 21:50:10 +0000 (GMT) Cc: linux-arm-kernel@lists.arm.linux.org.uk ('linux-arm-kernel@lists.arm.linux.org.uk') In-Reply-To: from "George France" at Mar 06, 2000 04:04:32 PM X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-arm-kernel@lists.arm.linux.org.uk Precedence: bulk George France writes: > Is there any reason why I should not modify the menus, to work this way?? Yes. SA-110 is not a system type. There are clearly three different SA-110 systems out there, each with its own unique properties: 1. Acorn RiscPC 2. EBSA-110 3. Footbridge-based PCI Don't forget that in some cases, machines may have a SA-110 in, or they may have an ARM610 or ARM710. Therefore, there is no such thing as a generic "SA-110" machine. _____ |_____| ------------------------------------------------- ---+---+- | | Russell King linux@arm.linux.org.uk --- --- | | | | http://www.arm.linux.org.uk/~rmk/armlinux.html / / | | +-+-+ --- -+- / | THE developer of ARM Linux |+| /|\ / | | | --- | +-+-+ ------------------------------------------------- /\\\ | unsubscribe: body of `unsubscribe linux-arm-kernel' to majordomo@lists.arm.linux.org.uk From owner-linux-arm-kernel@lists.arm.linux.org.uk Tue Mar 7 15:10:39 2000 Received: (from majordomo@localhost) by parcelfarce.linux.theplanet.co.uk (8.9.3/8.9.3) id PAA25153 for linux-arm-kernel-outgoing; Tue, 7 Mar 2000 15:10:39 GMT Received: from ice.ar51.net (IDENT:root@ice.ar51.net [208.225.80.11] (may be forged)) by parcelfarce.linux.theplanet.co.uk (8.9.3/8.9.3) with ESMTP id PAA25149 for ; Tue, 7 Mar 2000 15:10:37 GMT Received: from server01.asi (akron-80-155.ar51.net [208.225.80.155]) by ice.ar51.net (8.9.3/8.8.7) with ESMTP id KAA24056 for ; Tue, 7 Mar 2000 10:09:23 -0500 Received: by SERVER01 with Internet Mail Service (5.5.2448.0) id ; Tue, 7 Mar 2000 10:09:14 -0500 Message-ID: From: Jeff Sutherland To: "Linux ARM kernel mailing list (E-mail)" Subject: Choice of development kernel version... Date: Tue, 7 Mar 2000 10:09:08 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-linux-arm-kernel@lists.arm.linux.org.uk Precedence: bulk I managed to (apparently) successfully build a cross platform development toolchain using binutils-2.9.5.0.27, gcc-2.95.2 (patched) and glibc-2.1.3, using headers from a patched 2.2.13 kernel. What would be the most appropriate kernel version and patches to begin development with for a SA1110 processor? (We have several Intel eval boards, Assabet and Zilker, floating around). Regards, //Jeff Sutherland Accelent Systems, Inc. unsubscribe: body of `unsubscribe linux-arm-kernel' to majordomo@lists.arm.linux.org.uk From owner-linux-arm-kernel@lists.arm.linux.org.uk Tue Mar 7 15:31:32 2000 Received: (from majordomo@localhost) by parcelfarce.linux.theplanet.co.uk (8.9.3/8.9.3) id PAA25446 for linux-arm-kernel-outgoing; Tue, 7 Mar 2000 15:31:32 GMT Received: from xanadu.vipswitch.com (generic199.197.205.205.in-addr.arpa [205.205.197.199] (may be forged)) by parcelfarce.linux.theplanet.co.uk (8.9.3/8.9.3) with ESMTP id PAA25442 for ; Tue, 7 Mar 2000 15:31:30 GMT Date: Tue, 7 Mar 2000 10:22:32 -0500 (EST) From: Nicolas Pitre To: Jeff Sutherland cc: "Linux ARM kernel mailing list (E-mail)" Subject: Re: Choice of development kernel version... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-arm-kernel@lists.arm.linux.org.uk Precedence: bulk On Tue, 7 Mar 2000, Jeff Sutherland wrote: > What would be the most > appropriate kernel version and patches to begin development with for a > SA1110 processor? (We have several Intel eval boards, Assabet and Zilker, > floating around). Clearly you should start from my latest 2.3.x patch that you could find on ftp.netwinder.org/users/n/nico. Also subscribe to the SA1100 Linux mailing list which address is sa1100-linux@pa.dec.com. Nicolas unsubscribe: body of `unsubscribe linux-arm-kernel' to majordomo@lists.arm.linux.org.uk From owner-linux-arm-kernel@lists.arm.linux.org.uk Wed Mar 8 22:07:27 2000 Received: (from majordomo@localhost) by parcelfarce.linux.theplanet.co.uk (8.9.3/8.9.3) id WAA17256 for linux-arm-kernel-outgoing; Wed, 8 Mar 2000 22:07:27 GMT Received: from caramon.arm.linux.org.uk (root@p60-cordelia-gui.tch.enablis.net [212.250.233.60]) by parcelfarce.linux.theplanet.co.uk (8.9.3/8.9.3) with ESMTP id WAA17252 for ; Wed, 8 Mar 2000 22:07:24 GMT Received: from flint.arm.linux.org.uk (root@flint [192.168.0.4]) by caramon.arm.linux.org.uk (8.9.3/8.9.3) with ESMTP id WAA06650 for ; Wed, 8 Mar 2000 22:05:57 GMT Received: (from rmk@localhost) by flint.arm.linux.org.uk (8.9.3/8.9.3) id WAA14735 for linux-arm-kernel@lists.arm.linux.org.uk; Wed, 8 Mar 2000 22:05:06 GMT Received: from davinci.artisan.calpoly.edu (root@davinci.artisan.calpoly.edu [129.65.60.31]) by parcelfarce.linux.theplanet.co.uk (8.9.3/8.9.3) with ESMTP id TAA15467 for ; Wed, 8 Mar 2000 19:43:30 GMT From: bowu@calpoly.edu Received: from localhost (root@localhost) by davinci.artisan.calpoly.edu (8.8.6 (PHNE_17135)/8.8.6) with SMTP id LAA14589 for linux-arm-kernel@lists.arm.linux.org.uk; Wed, 8 Mar 2000 11:41:55 -0800 (PST) X-OpenMail-Hops: 1 Date: Wed, 8 Mar 2000 11:41:13 -0800 Message-Id: Subject: help for cross-compiler MIME-Version: 1.0 TO: linux-arm-kernel@lists.arm.linux.org.uk Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: 7bit Sender: owner-linux-arm-kernel@lists.arm.linux.org.uk Precedence: bulk Hi,all: Where is the instruction for how to cross-compile the ARM kernel on the Intel machine? On the armlinux website, I can only find instructions about compiling a kernel for ARM machines on the target platform. Thank you very much for your help. Bo unsubscribe: body of `unsubscribe linux-arm-kernel' to majordomo@lists.arm.linux.org.uk From owner-linux-arm-kernel@lists.arm.linux.org.uk Wed Mar 8 22:15:53 2000 Received: (from majordomo@localhost) by parcelfarce.linux.theplanet.co.uk (8.9.3/8.9.3) id WAA17421 for linux-arm-kernel-outgoing; Wed, 8 Mar 2000 22:15:53 GMT Received: from crl.dec.com (crl.dec.com [192.58.206.2]) by parcelfarce.linux.theplanet.co.uk (8.9.3/8.9.3) with ESMTP id WAA17416 for ; Wed, 8 Mar 2000 22:15:52 GMT Received: from crlwebmail.crl.dec.com (crlwebmail.crl.dec.com [16.11.0.2]) by crl.dec.com (8.8.8/RWD-1.2) with ESMTP id RAA02671; Wed, 8 Mar 2000 17:14:30 -0500 (EST) Received: by crlwebmail.crl.dec.com with Internet Mail Service (5.5.2650.21) id ; Wed, 8 Mar 2000 17:18:13 -0500 Message-ID: From: George France To: "'bowu@calpoly.edu'" , linux-arm-kernel@lists.arm.linux.org.uk Subject: RE: help for cross-compiler Date: Wed, 8 Mar 2000 17:14:50 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-linux-arm-kernel@lists.arm.linux.org.uk Precedence: bulk Have you read the README file in /usr/src/linux/Documentation/arm????? --George George France, france@crl.dec.com Cambridge Research Laboratory, Compaq Computer Corporation One Kendall Square, Building 700 MS: CRL Cambridge, MA 02139 USA -----Original Message----- From: bowu@calpoly.edu [mailto:bowu@calpoly.edu] Sent: Wednesday, March 08, 2000 2:41 PM To: linux-arm-kernel@lists.arm.linux.org.uk Subject: help for cross-compiler Hi,all: Where is the instruction for how to cross-compile the ARM kernel on the Intel machine? On the armlinux website, I can only find instructions about compiling a kernel for ARM machines on the target platform. Thank you very much for your help. Bo unsubscribe: body of `unsubscribe linux-arm-kernel' to majordomo@lists.arm.linux.org.uk unsubscribe: body of `unsubscribe linux-arm-kernel' to majordomo@lists.arm.linux.org.uk From owner-linux-arm-kernel@lists.arm.linux.org.uk Thu Mar 9 19:25:09 2000 Received: (from majordomo@localhost) by parcelfarce.linux.theplanet.co.uk (8.9.3/8.9.3) id TAA10143 for linux-arm-kernel-outgoing; Thu, 9 Mar 2000 19:25:09 GMT Received: from hp06.postech.ac.kr (smtp.postech.ac.kr [141.223.2.1]) by parcelfarce.linux.theplanet.co.uk (8.9.3/8.9.3) with ESMTP id TAA10139 for ; Thu, 9 Mar 2000 19:25:05 GMT Received: from chakiris (MDOM17302-2.postech.ac.kr [141.223.213.68]) by hp06.postech.ac.kr (8.9.3/8.9.3) with SMTP id EAA22666 for ; Fri, 10 Mar 2000 04:24:47 +0900 (KST) Message-ID: <00a701bf89fc$d12a7dd0$44d5df8d@chakiris> From: =?ks_c_5601-1987?B?wvfH9sHY?= To: Subject: Hello. I have a question about dev. tool target name. Date: Fri, 10 Mar 2000 04:22:32 +0900 MIME-Version: 1.0 Content-Type: text/plain; charset="ks_c_5601-1987" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by parcelfarce.linux.theplanet.co.uk id TAA10140 Sender: owner-linux-arm-kernel@lists.arm.linux.org.uk Precedence: bulk Hello, all. I'm a newbie Korean linuxer - specifically to arm linux. Since I'm working on the embedded linux project for ARM, I have to build cross toolchains. After lots of trouble I've built it successfully with many advices from http://inkvine.fluff.org/~chris/arm-tools.html Yes. I could build the Linux kernel 2.2.14 with patch-rmk4 successfully. But the vmlinux image was elf-32littlearm format and the evaluation board engineer said that I have to build a big-endian image. So I've fiddled out Makefiles and Rules.make to add -mbig-endian switch to gcc and -EB switch to ld. And finally got error about arch/arm/lib/extractconstants.pl with objdump output of big-endian compiled objects. I've been reaching big-endian kernel image ( Yes, It's the goal ) ... But I had a doubt that "Is this kind of things right? If I have a toolchain configured to support big-endian default?" So I returned to web-life, finding any information... then I've got information from the web page mentioned at the beginning. It's the target name. In "Picking a target name" section from the web page... Not only arm, but armv4l and armv4b are also target names. I've tried it on binutils-2.9.5.0.29 first, but got errors like this. ----------------------------------------------------------- [root@fraser binutils-2.9.5.0.29]# pwd /home/cross-compiler/object_dir/binutils-2.9.5.0.29 [root@fraser binutils-2.9.5.0.29]# /home/cross-compiler/source_dir/binutils-2.9 .5.0.29/configure --target=armv4b-linux --prefix=/usr/cross-compiler/tool_dir/h ost/sparc-sun-solaris-for-arm/ Configuring for a sparc-sun-solaris2.6 host. Invalid configuration `armv4b-linux': machine `armv4b' not recognized Unrecognized target system name armv4b-linux. ------------------------------------------------------------ What's the point of problem? Are there any patches to support armv4b? Is the word "armv4b" badly located? Please answer. Thanks in advance. Have a nice day. unsubscribe: body of `unsubscribe linux-arm-kernel' to majordomo@lists.arm.linux.org.uk From owner-linux-arm-kernel@lists.arm.linux.org.uk Thu Mar 9 20:46:46 2000 Received: (from majordomo@localhost) by parcelfarce.linux.theplanet.co.uk (8.9.3/8.9.3) id UAA13235 for linux-arm-kernel-outgoing; Thu, 9 Mar 2000 20:46:46 GMT Received: from duteinh.et.tudelft.nl (duteinh.et.tudelft.nl [130.161.42.1]) by parcelfarce.linux.theplanet.co.uk (8.9.3/8.9.3) with ESMTP id UAA13230 for ; Thu, 9 Mar 2000 20:46:45 GMT Received: from kalman by duteinh.et.tudelft.nl (8.9.3/BB-2.0) id VAA01703; Thu, 9 Mar 2000 21:45:10 +0100 (MET) Date: Thu, 9 Mar 2000 21:45:10 +0100 (MET) Message-Id: <200003092045.VAA01703@duteinh.et.tudelft.nl> From: Erik Mouw To: tachyon@postech.ac.kr Cc: linux-arm-kernel@lists.arm.linux.org.uk Subject: Re: Hello. I have a question about dev. tool target name. In-Reply-To: <00a701bf89fc$d12a7dd0$44d5df8d@chakiris> Organization: Eric conspiracy secret labs X-Face: "!Z|1XjFg!3Iw)BwM^M\k)J5KHiPddz}#/Zw%?$&Q!xqob"OA|})3_@&BTTiQERo?/^g[Z<9P4R8:5C:aqq.cw!hotLc=+u-"+1rq@9$V^8PbOUlodyi_sejt+D`iqkLpx$>.aXl%vnfPIt"LK|/%>94_Zrm8jy?`_[RKt'TuoxUxfk(gMhY(n|DBBl~c$dhO>G%6}R4+DGX3|idBm4oU&UM/XUP4I9aoN{]`ax%B?rgD(I3OJ<62Y6L X-Mailer: XCmail 1.0.0 - with PGP support, PGP engine version 0.5 (Linux) X-Mailerorigin: http://www.fsai.fh-trier.de/~schmitzj/Xclasses/XCmail/ X-Eric-Conspiracy: There is no conspiracy! X-Loop: erik@it.et.tudelft.nl MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-linux-arm-kernel@lists.arm.linux.org.uk Precedence: bulk On Fri, 10 Mar 2000 04:22:32 +0900, wvfH9sHY wrote: > Since I'm working on the embedded linux project for ARM, I have to build cross > toolchains. > > After lots of trouble I've built it successfully with many advices from > > http://inkvine.fluff.org/~chris/arm-tools.html > > Yes. I could build the Linux kernel 2.2.14 with patch-rmk4 successfully. > > But the vmlinux image was elf-32littlearm format and the evaluation board > engineer said that I have to build a big-endian image. [...] > It's the target name. > > In "Picking a target name" section from the web page... > > Not only arm, but armv4l and armv4b are also target names. > > I've tried it on binutils-2.9.5.0.29 first, but got errors like this. > > ----------------------------------------------------------- > [root@fraser binutils-2.9.5.0.29]# pwd It's bad practice to use the root account for such silly things as compiling a toolchain. Use the root account as less as possible. > /home/cross-compiler/object_dir/binutils-2.9.5.0.29 > [root@fraser binutils-2.9.5.0.29]# /home/cross-compiler/source_dir/binutils-2.9 > .5.0.29/configure --target=armv4b-linux --prefix=/usr/cross-compiler/tool_dir/h > ost/sparc-sun-solaris-for-arm/ > Configuring for a sparc-sun-solaris2.6 host. > Invalid configuration `armv4b-linux': machine `armv4b' not recognized > Unrecognized target system name armv4b-linux. > ------------------------------------------------------------ > > What's the point of problem? Are there any patches to support armv4b? Is the > word "armv4b" badly located? Chris' webpage is not completely correct: if you want to use a big endian system, you have to specify a _complete_ system name, not an alias. The target name "arm-linux" is an aliasfor "arm-unknown-linux-gnu". The configure script feeds the target name through config.sub to find out the complete name. If the config.sub script doesn't know the alias, it will issue the error you encountered: erikm@thorgal:~/build/binutils-2.9.5.0.22 >./config.sub armv4b-linux Invalid configuration `armv4b-linux': machine `armv4b' not recognized So you'll have to help it a bit. First find out the "default" alias: erikm@thorgal:~/build/binutils-2.9.5.0.22 >./config.sub arm-linux arm-unknown-linux-gnu Now modify this to see if it recognizes the big-endian part: erikm@thorgal:~/build/binutils-2.9.5.0.22 >./config.sub armv4b-unknown-linux-gnu armv4b-unknown-linux-gnu Yes, it does. Try to build everything with target name "armv4b-unknown-linux-gnu". BTW: AFAIK all ARM CPUs support little-endian. Is there a specific reason that you have to use big-endian? Choosing for big-endian will most certainly give you a lot of problems, because the configure script used by many packages doesn't seem to support the idea of a big-endian ARM system (it does for PowerPC CPUs). Otherwise just do what all others do and use little-endian. (Someone please correct me if I'm wrong) Erik -- J.A.K. (Erik) Mouw, Information and Communication Theory Group, Department of Electrical Engineering, Faculty of Information Technology and Systems, Delft University of Technology, PO BOX 5031, 2600 GA Delft, The Netherlands Phone: +31-15-2785859 Fax: +31-15-2781843 Email J.A.K.Mouw@its.tudelft.nl WWW: http://www-ict.its.tudelft.nl/~erik/ unsubscribe: body of `unsubscribe linux-arm-kernel' to majordomo@lists.arm.linux.org.uk From owner-linux-arm-kernel@lists.arm.linux.org.uk Thu Mar 9 21:25:26 2000 Received: (from majordomo@localhost) by parcelfarce.linux.theplanet.co.uk (8.9.3/8.9.3) id VAA13902 for linux-arm-kernel-outgoing; Thu, 9 Mar 2000 21:25:26 GMT Received: from www.netwinder.org (IDENT:root@netwinder.org [207.245.35.202]) by parcelfarce.linux.theplanet.co.uk (8.9.3/8.9.3) with ESMTP id VAA13898 for ; Thu, 9 Mar 2000 21:25:24 GMT Received: from gw.rebel.com (gate.rebel.com [207.245.35.200]) by www.netwinder.org (8.9.3/8.9.3) with SMTP id QAA14423; Thu, 9 Mar 2000 16:23:06 -0500 Message-ID: <38C81510.45E833D0@netwinder.org> Received: from dhcp111.isa.ott.rebel.com by gw.rebel.com via smtpd (for netwinder.org [207.245.35.202]) with SMTP; 9 Mar 2000 21:21:25 UT Date: Thu, 09 Mar 2000 16:18:08 -0500 From: Scott Bambrough Organization: Rebel.com X-Mailer: Mozilla 4.7 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: Erik Mouw CC: tachyon@postech.ac.kr, linux-arm-kernel@lists.arm.linux.org.uk Subject: Re: Hello. I have a question about dev. tool target name. References: <200003092045.VAA01703@duteinh.et.tudelft.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-arm-kernel@lists.arm.linux.org.uk Precedence: bulk Erik Mouw wrote: > > BTW: AFAIK all ARM CPUs support little-endian. Is there a specific reason > that you have to use big-endian? Choosing for big-endian will most > certainly give you a lot of problems, because the configure script used by > many packages doesn't seem to support the idea of a big-endian ARM system > (it does for PowerPC CPUs). Otherwise just do what all others do and use > little-endian. (Someone please correct me if I'm wrong) Are there big endian ARM Linux systems. I thought the kernel required little endian. If it doesn't we may have to revisit the tools, as I am not sure they will all function correctly. GDB will need some work for sure. -- Scott Bambrough - Software Engineer REBEL.COM http://www.rebel.com NetWinder http://www.netwinder.org unsubscribe: body of `unsubscribe linux-arm-kernel' to majordomo@lists.arm.linux.org.uk From owner-linux-arm-kernel@lists.arm.linux.org.uk Thu Mar 9 23:06:56 2000 Received: (from majordomo@localhost) by parcelfarce.linux.theplanet.co.uk (8.9.3/8.9.3) id XAA15060 for linux-arm-kernel-outgoing; Thu, 9 Mar 2000 23:06:56 GMT Received: from ns-inetext.inet.com (ns-inetext.inet.com [199.171.211.140]) by parcelfarce.linux.theplanet.co.uk (8.9.3/8.9.3) with ESMTP id XAA15051 for ; Thu, 9 Mar 2000 23:06:49 GMT Received: from harpo.inetint.com (harpo [172.16.99.60]) by ns-inetext.inet.com (8.9.2/8.9.2) with ESMTP id RAA17309 for ; Thu, 9 Mar 2000 17:04:12 -0600 (CST) Received: from inet.com ([172.16.13.118]) by harpo.inetint.com (Netscape Messaging Server 3.6) with ESMTP id AAAF85; Thu, 9 Mar 2000 17:09:43 -0600 Message-ID: <38C82E35.11B4BE33@inet.com> Date: Thu, 09 Mar 2000 17:05:25 -0600 From: ejc X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5-15 i686) X-Accept-Language: en MIME-Version: 1.0 To: David Winchell CC: Raphael Manfredi , linux-kernel , linux-arm-kernel@lists.arm.linux.org.uk Subject: Re: Kernel debugger, other debugging tools References: <38C80A08.2A63CA14@mclinux.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-arm-kernel@lists.arm.linux.org.uk Precedence: bulk David Winchell wrote: > > Raphael, > > SGI and Mission Critical Linux have kernel crash tools that might be of interest. > The MCL ones can be found at http://www.missioncriticallinux.com/download and > the SGI ones at http://oss.sgi.com/projects/lkcd/download/. SGI's is for ix86 only, right? What about tools for platforms other than ix86 & Alpha? (Say ARM?) Is anyone working on a kernel debugger (or port of one) for the ARM family? TIA, Eli -- Eli Carter eli.carter@inet.com unsubscribe: body of `unsubscribe linux-arm-kernel' to majordomo@lists.arm.linux.org.uk From owner-linux-arm-kernel@lists.arm.linux.org.uk Thu Mar 9 23:42:04 2000 Received: (from majordomo@localhost) by parcelfarce.linux.theplanet.co.uk (8.9.3/8.9.3) id XAA15468 for linux-arm-kernel-outgoing; Thu, 9 Mar 2000 23:42:04 GMT Received: from mail.turbolinux.com (IDENT:root@mail.turbolinux.com [38.170.88.25]) by parcelfarce.linux.theplanet.co.uk (8.9.3/8.9.3) with ESMTP id XAA15464 for ; Thu, 9 Mar 2000 23:42:02 GMT Received: from localhost (yakker@localhost) by mail.turbolinux.com (8.9.3/8.9.3) with ESMTP id PAA32263; Thu, 9 Mar 2000 15:39:55 -0800 Date: Thu, 9 Mar 2000 15:39:54 -0800 (PST) From: "Matt D. Robinson" To: ejc cc: yakker@turbolinux.com, tjm@sgi.com, David Winchell , Raphael Manfredi , linux-kernel , linux-arm-kernel@lists.arm.linux.org.uk Subject: Re: Kernel debugger, other debugging tools In-Reply-To: <38C82E35.11B4BE33@inet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-arm-kernel@lists.arm.linux.org.uk Precedence: bulk Nothing regarding LKCD is being done on ARM at the moment; most of the efforts are concentrated on the Alpha 2.2.X port, moving to a 2.3.X base, and eventually a IA64 port. There are some individuals looking at the analyzer portion for S/390 at the moment. --Matt On Thu, 9 Mar 2000, ejc wrote: |>David Winchell wrote: |>> [ ... ] |>> the SGI ones at http://oss.sgi.com/projects/lkcd/download/. |> |>SGI's is for ix86 only, right? |>What about tools for platforms other than ix86 & Alpha? (Say ARM?) |> |>Is anyone working on a kernel debugger (or port of one) for the ARM |>family? |> |>TIA, unsubscribe: body of `unsubscribe linux-arm-kernel' to majordomo@lists.arm.linux.org.uk From owner-linux-arm-kernel@lists.arm.linux.org.uk Fri Mar 10 06:36:35 2000 Received: (from majordomo@localhost) by parcelfarce.linux.theplanet.co.uk (8.9.3/8.9.3) id GAA20583 for linux-arm-kernel-outgoing; Fri, 10 Mar 2000 06:36:35 GMT Received: from mail2000.com.tw (mail2000.com.tw [139.175.250.58]) by parcelfarce.linux.theplanet.co.uk (8.9.3/8.9.3) with SMTP id GAA20579 for ; Fri, 10 Mar 2000 06:36:33 GMT Message-ID: <38C8980B.000BF54F.openmail@mail2000.com.tw> Received: By OpenMail Mailer;Fri Mar 10 14:36:59 CST 2000 From: "李建民" To: linux-arm-kernel@lists.arm.linux.org.uk Date: Fri, 10 Mar 2000 14:36:59 +0800 (CST) Subject: as syntax for arm MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=941943188_1768335847_1507769254" Sender: owner-linux-arm-kernel@lists.arm.linux.org.uk Precedence: bulk ------=941943188_1768335847_1507769254 Content-Type: text/plain Content-Transfer-Encoding: 8bit Dear All: I am looking forward as manual. Could any one tell me how to get or make the manual of gcc and binutils?? I mean the .ps or .pdf format one not the online one. Also, I am wondering that the directives of as, like [, ], CODE ...etc are same with ARM SDT assembler?? Have a nice day!! kirk -- ----== Mailed via Openfind ==----- http://mail2000.com.tw/ 提供免費的 e-mail 信箱服務 ------=941943188_1768335847_1507769254-- unsubscribe: body of `unsubscribe linux-arm-kernel' to majordomo@lists.arm.linux.org.uk From owner-linux-arm-kernel@lists.arm.linux.org.uk Fri Mar 10 09:19:52 2000 Received: (from majordomo@localhost) by parcelfarce.linux.theplanet.co.uk (8.9.3/8.9.3) id JAA22018 for linux-arm-kernel-outgoing; Fri, 10 Mar 2000 09:19:52 GMT Received: from duteinh.et.tudelft.nl (duteinh.et.tudelft.nl [130.161.42.1]) by parcelfarce.linux.theplanet.co.uk (8.9.3/8.9.3) with ESMTP id JAA22014 for ; Fri, 10 Mar 2000 09:19:52 GMT Received: from kalman by duteinh.et.tudelft.nl (8.9.3/BB-2.0) id KAA04887; Fri, 10 Mar 2000 10:18:22 +0100 (MET) Date: Fri, 10 Mar 2000 10:18:22 +0100 (MET) Message-Id: <200003100918.KAA04887@duteinh.et.tudelft.nl> From: Erik Mouw To: cm_lee@mail2000.com.tw Cc: linux-arm-kernel@lists.arm.linux.org.uk Subject: Re: as syntax for arm In-Reply-To: <38C8980B.000BF54F.openmail@mail2000.com.tw> Organization: Eric conspiracy secret labs X-Face: "!Z|1XjFg!3Iw)BwM^M\k)J5KHiPddz}#/Zw%?$&Q!xqob"OA|})3_@&BTTiQERo?/^g[Z<9P4R8:5C:aqq.cw!hotLc=+u-"+1rq@9$V^8PbOUlodyi_sejt+D`iqkLpx$>.aXl%vnfPIt"LK|/%>94_Zrm8jy?`_[RKt'TuoxUxfk(gMhY(n|DBBl~c$dhO>G%6}R4+DGX3|idBm4oU&UM/XUP4I9aoN{]`ax%B?rgD(I3OJ<62Y6L X-Mailer: XCmail 1.0.0 - with PGP support, PGP engine version 0.5 (Linux) X-Mailerorigin: http://www.fsai.fh-trier.de/~schmitzj/Xclasses/XCmail/ X-Eric-Conspiracy: There is no conspiracy! X-Loop: erik@it.et.tudelft.nl MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-linux-arm-kernel@lists.arm.linux.org.uk Precedence: bulk On Fri, 10 Mar 2000 14:36:59 +0800 (CST), 李建民 wrote: > I am looking forward as manual. > Could any one tell me how to get or make the manual of gcc and binutils?? > I mean the .ps or .pdf format one not the online one. You can make the PostScript files yourself. The gcc and binutils manuals are written in texinfo, from which you can generate info file, PostScript or HTML output. "make dvi" in a configured gcc or binutils build tree will make all documentation in dvi, from which you can generate PostScript with the dvips utility. > Also, I am wondering that the directives of as, like [, ], CODE ...etc > are same with ARM SDT assembler?? I can't tell, I don't use the ARM SDT assembler. Have a look at the assembly files in th Linux kernel tree for inspiration. Erik -- J.A.K. (Erik) Mouw, Information and Communication Theory Group, Department of Electrical Engineering, Faculty of Information Technology and Systems, Delft University of Technology, PO BOX 5031, 2600 GA Delft, The Netherlands Phone: +31-15-2785859 Fax: +31-15-2781843 Email J.A.K.Mouw@its.tudelft.nl WWW: http://www-ict.its.tudelft.nl/~erik/ unsubscribe: body of `unsubscribe linux-arm-kernel' to majordomo@lists.arm.linux.org.uk From owner-linux-arm-kernel@lists.arm.linux.org.uk Sat Mar 11 15:19:27 2000 Received: (from majordomo@localhost) by parcelfarce.linux.theplanet.co.uk (8.9.3/8.9.3) id PAA13185 for linux-arm-kernel-outgoing; Sat, 11 Mar 2000 15:19:27 GMT Received: from caramon.arm.linux.org.uk (root@p27-magpie-gui.tch.enablis.net [194.168.180.27]) by parcelfarce.linux.theplanet.co.uk (8.9.3/8.9.3) with ESMTP id PAA13181 for ; Sat, 11 Mar 2000 15:19:25 GMT Received: from raistlin.arm.linux.org.uk (root@raistlin [192.168.0.3]) by caramon.arm.linux.org.uk (8.9.3/8.9.3) with ESMTP id PAA18627; Sat, 11 Mar 2000 15:17:59 GMT From: Russell King - ARM Linux Admin Received: (from linux@localhost) by raistlin.arm.linux.org.uk (8.7.4/8.7.3) id PAA06419; Sat, 11 Mar 2000 15:17:06 GMT Message-Id: <200003111517.PAA06419@raistlin.arm.linux.org.uk> Subject: Re: Discussion on ARM kernel command line boot options. To: sjhill@cotw.com (Steven J. Hill) Date: Sat, 11 Mar 2000 15:17:05 +0000 (GMT) Cc: linux-arm-kernel@lists.arm.linux.org.uk In-Reply-To: <38CA504A.EB0C887C@cotw.com> from "Steven J. Hill" at Mar 11, 2000 08:55:22 AM X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-arm-kernel@lists.arm.linux.org.uk Precedence: bulk Please discuss this on linux-arm-kernel. Steven J. Hill writes: > It appears from my digging in the code that then only way to send any options > to the kernel is to put them in at compile time. 'arch/arm/kernel/setup.c' > contains the static character array 'default_command_line' which is set equal > to the string hard coded during kernel configuration. I have two possible > suggestions for passing options: There is already a defined structure to pass arguments/data to the kernel. Please look in include/asm-arm/setup.h and arch/arm/kernel/setup.c In fact, many architectures use this: NetWinder Archimedes A5000 RiscPC EBSA110 EBSA285 and probably more. _____ |_____| ------------------------------------------------- ---+---+- | | Russell King linux@arm.linux.org.uk --- --- | | | | http://www.arm.linux.org.uk/ / / | | +-+-+ --- -+- / | THE developer of ARM Linux |+| /|\ / | | | --- | +-+-+ ------------------------------------------------- /\\\ | unsubscribe: body of `unsubscribe linux-arm-kernel' to majordomo@lists.arm.linux.org.uk From owner-linux-arm-kernel@lists.arm.linux.org.uk Mon Mar 13 14:50:32 2000 Received: (from majordomo@localhost) by parcelfarce.linux.theplanet.co.uk (8.9.3/8.9.3) id OAA09677 for linux-arm-kernel-outgoing; Mon, 13 Mar 2000 14:50:32 GMT Received: from cvsftp.cotw.com (cvsftp.cotw.com [205.216.126.161]) by parcelfarce.linux.theplanet.co.uk (8.9.3/8.9.3) with ESMTP id OAA09670 for ; Mon, 13 Mar 2000 14:50:26 GMT Received: from cotw.com (pteclap.plutonium.net [205.216.126.78]) by cvsftp.cotw.com (8.9.3/8.9.3) with ESMTP id CAA02300 for ; Mon, 13 Mar 2000 02:47:40 -0600 Message-ID: <38CCF1E2.14CC2299@cotw.com> Date: Mon, 13 Mar 2000 08:49:22 -0500 From: "Steven J. Hill" X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.3.47 i686) X-Accept-Language: en MIME-Version: 1.0 To: linux-arm-kernel@lists.arm.linux.org.uk Subject: Understanding 'bootmem'. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-arm-kernel@lists.arm.linux.org.uk Precedence: bulk I am trying to better understand 'bootmem'. From the comments in the file 'mm/bootmem.c', it appears that bootmem is used in dealing with reserved system memory and holes. Essentially, does the bootmem family of functions deal with systems where all RAM is not contiguous? It also seems to prevent allocation of memory that is being used by the INITRD if the kernel is configured for one. Is there any additional funcionality of the 'bootmem' stuff that I am missing? Also, with respect to the 'meminfo' structure defined in 'setup.h'. When we speak of NR_BANKS which I assumed stands for "number of RAM banks", are we talking about physical memory devices (chips) or the number of regions in the memory map where RAM is located? In my case of the LinkUpSys L7200SDB, I only have RAM located at physical address 0xf0000000 and it is a contiguous 32MB region. I would therefore have 'meminfo.nr_banks = 1' and 'meminfo.bank[0].size = 32*1024*1024'. Am I understanding this properly? Thanks. -Steve -- Steven J. Hill - Embedded SW Engineer Public Key: 'finger sjhill@mail.cotw.com' FPR1: E124 6E1C AF8E 7802 A815 FPR2: 7D72 829C 3386 4C4A E17D unsubscribe: body of `unsubscribe linux-arm-kernel' to majordomo@lists.arm.linux.org.uk From owner-linux-arm-kernel@lists.arm.linux.org.uk Mon Mar 13 15:56:23 2000 Received: (from majordomo@localhost) by parcelfarce.linux.theplanet.co.uk (8.9.3/8.9.3) id PAA10453 for linux-arm-kernel-outgoing; Mon, 13 Mar 2000 15:56:23 GMT Received: from gmate_home.gmate.co.kr (IDENT:root@[210.205.11.243]) by parcelfarce.linux.theplanet.co.uk (8.9.3/8.9.3) with ESMTP id PAA10448 for ; Mon, 13 Mar 2000 15:56:20 GMT Received: from ultima ([210.223.111.20]) by gmate_home.gmate.co.kr (8.9.3/8.8.7) with SMTP id BAA29342 for ; Tue, 14 Mar 2000 01:00:14 +0900 From: Tred Lim Reply-To: trlim@gmate.co.kr To: linux-arm-kernel@lists.arm.linux.org.uk Subject: DMA Problem. Help me. Date: Tue, 14 Mar 2000 00:11:53 +0900 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <00031400550302.19417@ultima> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by parcelfarce.linux.theplanet.co.uk id PAA10449 Sender: owner-linux-arm-kernel@lists.arm.linux.org.uk Precedence: bulk Hi, My name is Tred Lim. I'm poring ARM Linux 2.2.14-rmk1 to our SA-1110 based platform. It seems that current kernel has a problem with DMA buffer on SA-1100/1110. Although DMA controller finished read transfer successfully, DMA buffer doesn't contain valid data. I could solve this by inserting flush_cache_all() or flush_page_to_ram() before accessing DMA buffer. There han been no such kind of of problem with DMA write transfer. I guess DMA buffer should be non-cacheable and non-bufferable. If so, how can I do this? I have two choices. I have no idea if these are right way to solve this. 1. Just use flush_cache_all() or flush_page_to_ram(). 2. Modify mem_init() to mark all or some DMA pages as non-cacheable and non-bufferable. I will be waiting for any suggestions. Is there anybody who can write a fix for this? Regards, Tred Lim unsubscribe: body of `unsubscribe linux-arm-kernel' to majordomo@lists.arm.linux.org.uk From owner-linux-arm-kernel@lists.arm.linux.org.uk Mon Mar 13 16:17:21 2000 Received: (from majordomo@localhost) by parcelfarce.linux.theplanet.co.uk (8.9.3/8.9.3) id QAA10862 for linux-arm-kernel-outgoing; Mon, 13 Mar 2000 16:17:21 GMT Received: from xanadu.vipswitch.com (generic199.197.205.205.in-addr.arpa [205.205.197.199] (may be forged)) by parcelfarce.linux.theplanet.co.uk (8.9.3/8.9.3) with ESMTP id QAA10858 for ; Mon, 13 Mar 2000 16:17:20 GMT Date: Mon, 13 Mar 2000 11:08:51 -0500 (EST) From: Nicolas Pitre To: Tred Lim cc: linux-arm-kernel@lists.arm.linux.org.uk Subject: Re: DMA Problem. Help me. In-Reply-To: <00031400550302.19417@ultima> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-arm-kernel@lists.arm.linux.org.uk Precedence: bulk On Tue, 14 Mar 2000, Tred Lim wrote: > Hi, > > My name is Tred Lim. > I'm poring ARM Linux 2.2.14-rmk1 to our SA-1110 based platform. Did you use my SA1100 patches from ftp.netwinder.org/users/n/nico/ ? > It seems that current kernel has a problem with DMA buffer on SA-1100/1110. > Although DMA controller finished read transfer successfully, DMA buffer doesn't > contain valid data. You have a classique cache coherency problem which affects the ARM processors. > I could solve this by inserting flush_cache_all() or flush_page_to_ram() before > accessing DMA buffer. > There han been no such kind of of problem with DMA write transfer. > > I guess DMA buffer should be non-cacheable and non-bufferable. If so, how > can I do this? You could use ioremap() to get a non-cacheable virtual address for some memory. See sa1100fb.c in the above mentionned patch for an example. PS: netwinder.org is scheduled to be down for few hours today. Nicolas unsubscribe: body of `unsubscribe linux-arm-kernel' to majordomo@lists.arm.linux.org.uk From owner-linux-arm-kernel@lists.arm.linux.org.uk Tue Mar 14 07:19:15 2000 Received: (from majordomo@localhost) by parcelfarce.linux.theplanet.co.uk (8.9.3/8.9.3) id HAA21490 for linux-arm-kernel-outgoing; Tue, 14 Mar 2000 07:19:15 GMT Received: from caramon.arm.linux.org.uk (root@p44-magpie-gui.tch.enablis.net [194.168.180.44]) by parcelfarce.linux.theplanet.co.uk (8.9.3/8.9.3) with ESMTP id HAA21486 for ; Tue, 14 Mar 2000 07:19:12 GMT Received: from flint.arm.linux.org.uk (root@flint [192.168.0.4]) by caramon.arm.linux.org.uk (8.9.3/8.9.3) with ESMTP id HAA31841 for ; Tue, 14 Mar 2000 07:13:33 GMT Received: (from linux@localhost) by flint.arm.linux.org.uk (8.9.3/8.9.3) id HAA18791 for linux-arm-kernel@lists.arm.linux.org.uk; Tue, 14 Mar 2000 07:12:17 GMT From: Russell King - ARM Linux Admin Message-Id: <200003140712.HAA18791@flint.arm.linux.org.uk> Subject: New ports for the ARM kernel To: linux-arm-kernel@lists.arm.linux.org.uk Date: Mon, 13 Mar 2000 22:38:56 +0000 (GMT) X-Mailer: ELM [version 2.5 PL1] Sender: owner-linux-arm-kernel@lists.arm.linux.org.uk Precedence: bulk Hi, Well, Linux kernel 2.4 is imminent, and I'm still seeing talk on the mailing list about using 2.2.14 to start a new port. While 2.2.14 has been around for some time, it is feature-lacking to put it mildly compared with the current state of the 2.3 kernels. One feature which seems to be appearing recently is about uncacheable DMA areas. This area has been dealt with in 2.3 kernels, and is becoming an integral part of most PCI device drivers. However, the solution is not limited to just PCI device drivers, but any device driver you happen to think of. It is now my belief that any new port should follow the 2.3 kernels (if there are any more to be released, it looks like we may just have a 2.3.52) which will then lead into 2.4. In fact, I'd suggest the following when doing the initial port: 1. Use a stable kernel (eg, 2.2.14) to get the basic functionality going (ie boots, keyboard/display works whatever it may be). 2. Move to a development kernel as soon as possible, especially if you have some weird hardware which needs features present in these kernels, but not present in the older stable kernel. This should make your life easier, since you don't have to implement things twice. You may also come up with a better way of doing something which hasn't been thought of - the development kernels are the right place for these things to happen. I shall be putting something to this effect up on the ARM Linux developer site shortly. The aim behind the developer site is to collect useful hints and tips about developing ARM Linux. Feel free to contribute if you have any suggestions. _____ |_____| ------------------------------------------------- ---+---+- | | Russell King linux@arm.linux.org.uk --- --- | | | | http://www.arm.linux.org.uk/ / / | | +-+-+ --- -+- / | THE developer of ARM Linux |+| /|\ / | | | --- | +-+-+ ------------------------------------------------- /\\\ | unsubscribe: body of `unsubscribe linux-arm-kernel' to majordomo@lists.arm.linux.org.uk --------------------------------------------------------------------------------------------------- *** sorry, missing articles, archive broke -- rmk ***