From owner-linux-arm-outgoing@vger.rutgers.edu Sat Jul 01 19:43:30 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 138SEk-0001gS-00 for linux-arm-archive@lists.arm.linux.org.uk; Sat, 01 Jul 2000 19:43:30 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 53A5915F41; Sat, 1 Jul 2000 20:37:29 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Sat, 1 Jul 2000 14:28:25 -0400 Received: by vger.rutgers.edu id ; Sat, 1 Jul 2000 14:28:19 -0400 Received: from [12.38.17.9] ([12.38.17.9]:4406 "EHLO mail.aeptec.com") by vger.rutgers.edu with ESMTP id ; Sat, 1 Jul 2000 14:13:49 -0400 Received: by MAIL with Internet Mail Service (5.5.2650.21) id ; Sat, 1 Jul 2000 14:13:07 -0400 Message-ID: <32CC5B62AF0BD2119E4C00A0C9663E221F3B76@MAIL> From: "Sun, Lei" To: "'linux-arm@vger.rutgers.edu'" Subject: Help!!! Date: Sat, 1 Jul 2000 14:13:06 -0400 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@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Lei Sun Software Engineer AEPTEC Microsystems, Inc. Rockville, MD 20877 unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 03 02:11:24 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 138ulg-0004Nz-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 03 Jul 2000 02:11:24 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 1692715FC7; Mon, 3 Jul 2000 02:54:22 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Sun, 2 Jul 2000 20:45:00 -0400 Received: by vger.rutgers.edu id ; Sun, 2 Jul 2000 20:43:30 -0400 Received: from smtppop1pub.gte.net ([206.46.170.20]:21320 "EHLO smtppop1.gte.net") by vger.rutgers.edu with ESMTP id ; Sun, 2 Jul 2000 20:43:00 -0400 Received: from gte.net (2Cust241.tnt1.bothell.wa.da.uu.net [63.28.30.241]) by smtppop1.gte.net with ESMTP for ; id TAA9773843 Sun, 2 Jul 2000 19:49:23 -0500 (CDT) Message-ID: <395F7DE5.90A5534B@gte.net> Date: Sun, 02 Jul 2000 10:37:41 -0700 From: Mike Coburn X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.5-15 i586) X-Accept-Language: en MIME-Version: 1.0 To: linux-arm@vger.rutgers.edu Subject: Tool stuff - binutils Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu I get very confused trying to get started. I have several different X86 machines and several different linux distributions and several different versions of gcc or egcs or whatever and all I really want to know is: Where is everyone else launching from these days and what is the best way to build myself a cross compiler for an arm system (I realize there are several different chips and such). I found Intel's site which said to get binutils-1.0.9 something and build it on Red Hat 5.2 but there is no binutils at the place such a thing is supposed to be found. So I can't use the cook book stuff from the Intel site. So where would I get the basic ingredients for this pizza? It seems that binutils is now 2.x and the compiler is newer and the whole thing is jumping around all over. I have built gcc and g++ and such before and I build kernels all the time, but I am not a CS grad , or a an architecture guru. Will it be possible to locate the basic pieces that actually work and play well together? It would seem that I would need these things before I can build a kernel and such that will run on this arm thing. That is the objective: To run a linux system as the primary os on an ARM system, probably a StrongArm rig if that helps any. I see that I can say ./configure --cross arm to build a "arm" cross compiler in gcc 2.7.2.3 which is the gcc I happen to have the source for right now. Should I start there or get some other version? -- Mike Coburn "These are _MY_ opinions and you can't have em" -- Bart Simpson unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 03 04:42:08 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 138x7Y-0005xt-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 03 Jul 2000 04:42:08 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id A922616089; Mon, 3 Jul 2000 05:32:30 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Sun, 2 Jul 2000 23:22:55 -0400 Received: by vger.rutgers.edu id ; Sun, 2 Jul 2000 23:22:46 -0400 Received: from [63.192.220.206] ([63.192.220.206]:61739 "EHLO pbdan.netx4.com") by vger.rutgers.edu with ESMTP id ; Sun, 2 Jul 2000 23:18:47 -0400 Received: from netx4.com (dan@localhost [127.0.0.1]) by pbdan.netx4.com (8.8.8/8.6.12) with ESMTP id XAA03601; Sun, 2 Jul 2000 23:39:54 -0400 Message-ID: <39600B08.7FF5F87B@netx4.com> Date: Sun, 02 Jul 2000 23:39:52 -0400 From: Dan Malek Organization: NETx4, LLC X-Mailer: Mozilla 4.05 [en] (X11; I; Linux 2.1.130 ppc) MIME-Version: 1.0 To: Mike Coburn Cc: linux-arm@vger.rutgers.edu Subject: Re: Tool stuff - binutils References: <395F7DE5.90A5534B@gte.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Mike Coburn wrote: > > I get very confused trying to get started. I have several different X86 > machines > and several different linux distributions MontaVista Software is creating a CDK for various StrongARM boards. You can find the compilers, libraries, and a kernel on ftp://ftp.mvista.com/pub/CDK/wip/arm_sa110/RPMS This will be maturing over the next few weeks as more applications are added, documentation is written, and board configurations are created. The current tools are hosted on Linux/x86 RedHat 6.2, and PowerPC Linux Yellowdog 1.2. -- Dan unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 03 05:35:32 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 138xxE-0006X8-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 03 Jul 2000 05:35:32 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 3208315ED2; Mon, 3 Jul 2000 03:38:06 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Sun, 2 Jul 2000 21:28:51 -0400 Received: by vger.rutgers.edu id ; Sun, 2 Jul 2000 21:28:42 -0400 Received: from mail.isa.com.hk ([203.85.156.65]:3611 "EHLO ns.isa.com.hk") by vger.rutgers.edu with ESMTP id ; Sun, 2 Jul 2000 21:28:33 -0400 Received: from localhost (ho@localhost) by ns.isa.com.hk (8.9.3/8.9.3) with ESMTP id JAA12807; Mon, 3 Jul 2000 09:41:57 +0800 (EAT) Date: Mon, 3 Jul 2000 09:41:52 +0800 (EAT) From: Ho Tat Leung To: Mike Coburn Cc: linux-arm@vger.rutgers.edu Subject: Re: Tool stuff - binutils In-Reply-To: <395F7DE5.90A5534B@gte.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Have a look at the site below. It has instruction on how to build a cross compiler. http://www.bluewaternz.com/startoff/armlinux.htm On Sun, 2 Jul 2000, Mike Coburn wrote: > I get very confused trying to get started. I have several different X86 > machines > and several different linux distributions and several different versions > of gcc > or egcs or whatever and all I really want to know is: Where is everyone > else > launching from these days and what is the best way to build myself a > cross > compiler for an arm system (I realize there are several different chips > and > such). I found Intel's site which said to get binutils-1.0.9 something > and > build it on Red Hat 5.2 but there is no binutils at the place such a > thing is > supposed to be found. So I can't use the cook book stuff from the Intel > > site. So where would I get the basic ingredients for this pizza? It > seems > that binutils is now 2.x and the compiler is newer and the whole thing > is > jumping around all over. I have built gcc and g++ and such before and I > > build kernels all the time, but I am not a CS grad , or a an > architecture > guru. Will it be possible to locate the basic pieces that actually work > and > play well together? It would seem that I would need these things before > > I can build a kernel and such that will run on this arm thing. That is > the > objective: To run a linux system as the primary os on an ARM system, > probably a StrongArm rig if that helps any. > > I see that I can say ./configure --cross arm to build a "arm" cross > compiler > in gcc 2.7.2.3 which is the gcc I happen to have the source for right > now. > Should I start there or get some other version? > > > -- > > Mike Coburn > > "These are _MY_ opinions and you can't have em" -- Bart Simpson > > > > > unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu > ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ > ++ kernel-related discussions. ++ > unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm@lists.arm.linux.org.uk Mon Jul 03 11:11:24 2000 Received: from majordomo by www.linux.org.uk with local (Exim 3.13 #1) id 13937C-0001Xi-00 for linux-arm-outgoingx@www.linux.org.uk; Mon, 03 Jul 2000 11:06:10 +0100 Received: from [206.111.156.6] (helo=smtphost.smartm.com) by www.linux.org.uk with smtp (Exim 3.13 #1) id 13937A-0001Xc-00 for linux-arm@lists.arm.linux.org.uk; Mon, 03 Jul 2000 11:06:09 +0100 Received: by smtphost.smartm.com(Lotus SMTP MTA v4.6.7 (934.1 12-30-1999)) id 88256911.0038EEFF ; Mon, 3 Jul 2000 03:21:51 -0700 X-Lotus-FromDomain: SMART MODULAR@APEX DATA INC From: iain.grant@smartm.com To: linux-arm@lists.arm.linux.org.uk Message-ID: <88256911.0038E4A3.00@smtphost.smartm.com> Date: Mon, 3 Jul 2000 11:04:44 +0100 Subject: registration Sender: owner-linux-arm@lists.arm.linux.org.uk Precedence: bulk unsubscribe: body of `unsubscribe linux-arm' to majordomo@lists.arm.linux.org.uk This is a backup list for linux-arm@vger.rutgers.edu, and the subscription list is regularly synchronised. From owner-linux-arm@lists.arm.linux.org.uk Mon Jul 03 11:11:24 2000 Received: from majordomo by www.linux.org.uk with local (Exim 3.13 #1) id 13937C-0001Xi-00 for linux-arm-outgoingx@www.linux.org.uk; Mon, 03 Jul 2000 11:06:10 +0100 Received: from [206.111.156.6] (helo=smtphost.smartm.com) by www.linux.org.uk with smtp (Exim 3.13 #1) id 13937A-0001Xc-00 for linux-arm@lists.arm.linux.org.uk; Mon, 03 Jul 2000 11:06:09 +0100 Received: by smtphost.smartm.com(Lotus SMTP MTA v4.6.7 (934.1 12-30-1999)) id 88256911.0038EEFF ; Mon, 3 Jul 2000 03:21:51 -0700 X-Lotus-FromDomain: SMART MODULAR@APEX DATA INC From: iain.grant@smartm.com To: linux-arm@lists.arm.linux.org.uk Message-ID: <88256911.0038E4A3.00@smtphost.smartm.com> Date: Mon, 3 Jul 2000 11:04:44 +0100 Subject: registration Sender: owner-linux-arm@lists.arm.linux.org.uk Precedence: bulk unsubscribe: body of `unsubscribe linux-arm' to majordomo@lists.arm.linux.org.uk This is a backup list for linux-arm@vger.rutgers.edu, and the subscription list is regularly synchronised. From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 03 14:35:44 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 1396O0-0003nP-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 03 Jul 2000 14:35:44 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id BE7AC15D8B; Mon, 3 Jul 2000 15:34:58 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Mon, 3 Jul 2000 09:21:14 -0400 Received: by vger.rutgers.edu id ; Mon, 3 Jul 2000 09:19:42 -0400 Received: from leonardo.telscom.ch ([193.247.121.34]:3391 "EHLO leonardo.telscom.ch") by vger.rutgers.edu with ESMTP id ; Mon, 3 Jul 2000 09:18:11 -0400 Received: from telscom.ch ([193.247.121.35]) by leonardo.telscom.ch (Post.Office MTA v3.1.2 release (PO205-101c) ID# 0-0U10L2S100) with ESMTP id AAA214 for ; Mon, 3 Jul 2000 15:20:12 +0200 Message-ID: <396096BB.E69C5102@telscom.ch> Date: Mon, 03 Jul 2000 15:35:55 +0200 From: Mathias Teikari Organization: Telscom AG X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.15 i686) X-Accept-Language: en MIME-Version: 1.0 To: linux-arm Subject: Help!!! Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu "Sun, Lei" wrote: > I was trying to port linux to strong arm SA-1110 development board. I use > linux kernel 2.2.2 , I have successfuly( at least I think it is, since I > didn't see error when I build the file)built the bin utility, arm-linux > compiler, glibc, and kernel image. > The Problem is that after I downloaded the image into my target using > nico's angel boot utility ( the downloading process seems fine also) and > start minicom, I can't see any message on teh screen. seems like either the > linux didn't run in my target or the serial port is not configured properly. > My question is how I should find the problem and fix that? I don't even > know what's going on in the target since I can't see and info on minicom > screen. > Thank you very much!! > > Regards > > lei sun unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 03 23:26:12 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 139EfM-0002AY-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 03 Jul 2000 23:26:12 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 75AB615D5C; Tue, 4 Jul 2000 00:26:27 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Mon, 3 Jul 2000 18:15:09 -0400 Received: by vger.rutgers.edu id ; Mon, 3 Jul 2000 18:12:28 -0400 Received: from thalia.fm.intel.com ([132.233.247.11]:2147 "EHLO thalia.fm.intel.com") by vger.rutgers.edu with ESMTP id ; Mon, 3 Jul 2000 18:10:07 -0400 Received: from SMTP (fmsmsxvs05-1.fm.intel.com [132.233.42.205]) by thalia.fm.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.30 2000/06/08 18:25:35 dmccart Exp $) with SMTP id WAA15055 for ; Mon, 3 Jul 2000 22:20:08 GMT Received: from fmsmsx28.FM.INTEL.COM ([132.233.48.28]) by 132.233.48.205 (Norton AntiVirus for Internet Email Gateways 1.0) ; Mon, 03 Jul 2000 22:19:13 0000 (GMT) Received: by fmsmsx28.fm.intel.com with Internet Mail Service (5.5.2650.21) id ; Mon, 3 Jul 2000 15:19:12 -0700 Message-ID: From: "Naik, Uday" To: linux-arm@vger.rutgers.edu Subject: Problem with toolchain Date: Mon, 3 Jul 2000 15:19:10 -0700 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@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Hi, I am not sure if this is the right forum for this question. But ... I have the IXP1200 arm linux kernel working in big endian mode with statically linked binaries. Most utilities bash, busybox etc seem to work fine. I have the following problems though. a) Dynamically linked executables crash with a memory violation in ld-linux-so.2. I narrowed it down to the point where I know it crashes in _dl_start() when it tries to access the variable at _DYNAMIC, which for some reason does not seem to be getting relocated. b) Floating point does not seem to work. 10.0 + 10.0 seems to return 0.0. I found an endianess bug where the kernel calls nwfpe and fixed that. But it did not seem to help. c) tinylogin has a problem because the glibc function getpwnam() does not work correctly for some reason and always returns NULL. I will debug it more. I looked at all the sysdep files for asm and only strlen.S was broken and I fixed that. But I will dig deeper. Any hints would be very greatly appreciated. Thanks Uday unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Tue Jul 04 01:14:28 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 139GM8-00048P-00 for linux-arm-archive@lists.arm.linux.org.uk; Tue, 04 Jul 2000 01:14:28 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id A220915D55; Tue, 4 Jul 2000 02:14:43 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Mon, 3 Jul 2000 20:04:04 -0400 Received: by vger.rutgers.edu id ; Mon, 3 Jul 2000 20:01:56 -0400 Received: from cogeco-29-65.cgocable.net ([24.141.29.65]:64757 "EHLO embeddedobjects.org") by vger.rutgers.edu with ESMTP id ; Mon, 3 Jul 2000 20:01:39 -0400 Received: from cgocable.net (softdnserr [::ffff:192.168.0.2]) (IDENT: hbelange) by embeddedobjects.org with esmtp; Mon, 03 Jul 2000 20:10:56 -0400 Message-ID: <39612C56.8B5D2412@cgocable.net> Date: Mon, 03 Jul 2000 20:14:14 -0400 From: Hugues Belanger X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i586) X-Accept-Language: en MIME-Version: 1.0 To: Dan Malek , linux-arm@vger.rutgers.edu Subject: Re: Tool stuff - binutils References: <395F7DE5.90A5534B@gte.net> <39600B08.7FF5F87B@netx4.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Hi I've been looking around for a solide development environement and so far their is not a lot of choises available. If you are familiar with hard hat can you elaborate on it's features and maybe do a little sales pitch... Thanks Hugues Belanger Dan Malek wrote: > Mike Coburn wrote: > > > > I get very confused trying to get started. I have several different X86 > > machines > > and several different linux distributions > > MontaVista Software is creating a CDK for various StrongARM boards. > You can find the compilers, libraries, and a kernel on > > ftp://ftp.mvista.com/pub/CDK/wip/arm_sa110/RPMS > > This will be maturing over the next few weeks as more applications > are added, documentation is written, and board configurations are > created. > > The current tools are hosted on Linux/x86 RedHat 6.2, and PowerPC > Linux Yellowdog 1.2. > > -- Dan > > unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu > ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ > ++ kernel-related discussions. ++ unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Tue Jul 04 07:42:32 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 139MPg-0006yy-00 for linux-arm-archive@lists.arm.linux.org.uk; Tue, 04 Jul 2000 07:42:32 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 7200F15D82; Tue, 4 Jul 2000 08:42:48 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 4 Jul 2000 02:32:47 -0400 Received: by vger.rutgers.edu id ; Tue, 4 Jul 2000 02:32:38 -0400 Received: from [206.103.12.152] ([206.103.12.152]:8758 "EHLO nimbus.ee.iitm.ernet.in") by vger.rutgers.edu with ESMTP id ; Tue, 4 Jul 2000 02:32:28 -0400 Received: from astra.ee.iitm.ernet.in (root@astra [144.16.244.8]) by nimbus.ee.iitm.ernet.in (8.8.7/8.8.7) with ESMTP id MAA09522 for ; Tue, 4 Jul 2000 12:14:30 +0530 Received: from localhost (saran@localhost) by astra.ee.iitm.ernet.in (8.9.3/8.8.7) with ESMTP id MAA06151 for ; Tue, 4 Jul 2000 12:13:58 +0530 Date: Tue, 4 Jul 2000 12:13:58 +0530 (IST) From: "J.Saravanan" To: arm processor Subject: Cl ps 7500fe.. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Hello all, I've been working on a test board with Cirrus logic (cl ps 7500fe) processor having minimum peripheral chips( 8 mb ram,boot flash super io chip and a cpld).Boot flash is loaded with angel boot image with com1 communication is enabled.When I try to open sdt tool( debugger) from my host pc the board remains silent.Only When I press reset,It(the host)reads some bytes from the test board.No writting operation is going on.That too it reads Half the way and then hangs. Is there anyone who has experienced similar kind of problem? What could've went wrong? Thanks, J.SARAVANAN India unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Tue Jul 04 15:54:04 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 139U5M-0000Rg-00 for linux-arm-archive@lists.arm.linux.org.uk; Tue, 04 Jul 2000 15:54:04 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 2054215D76; Tue, 4 Jul 2000 16:23:32 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 4 Jul 2000 10:13:08 -0400 Received: by vger.rutgers.edu id ; Tue, 4 Jul 2000 10:12:59 -0400 Received: from 176NA8.sdn.net.za ([216.2.176.8]:6974 "EHLO conlognt.conlog.co.za") by vger.rutgers.edu with ESMTP id ; Tue, 4 Jul 2000 10:12:42 -0400 Received: by intranet.hq.conlog.co.za with Internet Mail Service (5.5.2650.21) id ; Tue, 4 Jul 2000 16:23:18 +0200 Message-ID: <640F9ED3CD2DD211A28600A0C982788CB1EA39@intranet.hq.conlog.co.za> From: Thomas Page To: "Linux ARM (E-mail)" Subject: Newbie test Date: Tue, 4 Jul 2000 16:23:18 +0200 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@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Sorry if I have inconvenienced anyone, just want to see if I am properly subscibed. Thomas Page, CONLOG Phone +27 31 268 1150 Fax 268 1357 email: paget@conlog.co.za unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Tue Jul 04 16:43:14 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 139Uqw-0000ut-00 for linux-arm-archive@lists.arm.linux.org.uk; Tue, 04 Jul 2000 16:43:14 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id BF0A915DD1; Tue, 4 Jul 2000 17:41:58 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 4 Jul 2000 11:31:31 -0400 Received: by vger.rutgers.edu id ; Tue, 4 Jul 2000 11:31:29 -0400 Received: from beamer.mchh.siemens.de ([194.138.158.163]:58054 "EHLO beamer.mchh.siemens.de") by vger.rutgers.edu with ESMTP id ; Tue, 4 Jul 2000 11:30:49 -0400 Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226]) by beamer.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id RAA01986 for ; Tue, 4 Jul 2000 17:39:53 +0200 (MET DST) Received: from mchh201e.demchh201e.icn.siemens.de ([218.1.68.104]) by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id RAA23954 for ; Tue, 4 Jul 2000 17:40:02 +0200 (MET DST) Received: by MCHH201E with Internet Mail Service (5.5.2448.0) id ; Tue, 4 Jul 2000 17:43:12 +0200 Message-ID: From: ICN TR ON DA 1 Werkstudent1 To: "'linux-arm@vger.rutgers.edu'" Subject: Faster FP emulation for Linux Date: Tue, 4 Jul 2000 17:43:08 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Hi, from porting Quake to the RiscPC I have some quite fast single precision floating point routines, they reach between 3 and 5 MFlops on a SA RiscPC. I thought that it would be a nice option to have them available as in Linux. I recognized that there are two options, one is the FP emulator, and another one is the softfloat library for GCC. Which of these is used in our days? And what is a good starting point for this work? Peter Teichmann unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Tue Jul 04 21:02:30 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 139Ytq-0004nL-00 for linux-arm-archive@lists.arm.linux.org.uk; Tue, 04 Jul 2000 21:02:30 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id A496015DE4; Tue, 4 Jul 2000 22:02:27 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 4 Jul 2000 15:51:45 -0400 Received: by vger.rutgers.edu id ; Tue, 4 Jul 2000 15:51:01 -0400 Received: from tazenda.demon.co.uk ([158.152.220.239]:1668 "EHLO tazenda.demon.co.uk") by vger.rutgers.edu with ESMTP id ; Tue, 4 Jul 2000 15:50:19 -0400 Received: from kings-cross.london.uk.eu.org [::ffff:192.168.2.83] by tazenda.demon.co.uk with esmtp (Exim 3.11 #1 (Debian)) id 139YR9-0000Kw-00; Tue, 04 Jul 2000 20:32:51 +0100 Received: from localhost ([::ffff:127.0.0.1] helo=kings-cross.london.uk.eu.org ident=phil) by kings-cross.london.uk.eu.org with esmtp (Exim 3.12 #1) id 139YR6-00010q-00; Tue, 04 Jul 2000 20:32:48 +0100 X-Mailer: exmh version 2.1.1 10/15/1999 (debian) To: Mike Coburn Cc: linux-arm@vger.rutgers.edu Subject: Re: Tool stuff - binutils In-Reply-To: Message from Mike Coburn of "Sun, 02 Jul 2000 10:37:41 PDT." <395F7DE5.90A5534B@gte.net> References: <395F7DE5.90A5534B@gte.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 04 Jul 2000 20:32:48 +0100 From: Philip Blundell Message-Id: Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu > found Intel's site which said to get binutils-1.0.9 something Get binutils 2.10 from ftp.gnu.org or your favourite mirror. >I see that I can say ./configure --cross arm to build a "arm" cross >compiler >in gcc 2.7.2.3 which is the gcc I happen to have the source for right >now. >Should I start there or get some other version? You probably want gcc 2.95.2 plus the patch from ftp.netwinder.org:/users/p/philb. p. unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Wed Jul 05 09:04:30 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 139kAY-0006b4-00 for linux-arm-archive@lists.arm.linux.org.uk; Wed, 05 Jul 2000 09:04:30 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 1ACFE15E58; Wed, 5 Jul 2000 10:04:29 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Wed, 5 Jul 2000 03:52:05 -0400 Received: by vger.rutgers.edu id ; Wed, 5 Jul 2000 03:51:21 -0400 Received: from zmamail05.zma.compaq.com ([161.114.64.105]:2333 "HELO zmamail05.zma.compaq.com") by vger.rutgers.edu with SMTP id ; Wed, 5 Jul 2000 03:50:35 -0400 Received: by zmamail05.zma.compaq.com (Postfix, from userid 12345) id 6DF8B5913; Wed, 5 Jul 2000 04:00:08 -0400 (EDT) Received: from oils.ozy.dec.com (oils.ozy.dec.com [16.153.192.1]) by zmamail05.zma.compaq.com (Postfix) with ESMTP id 428A758D7 for ; Wed, 5 Jul 2000 04:00:06 -0400 (EDT) Received: from ozy.dec.com by oils.ozy.dec.com (8.8.8/1.1.10.5/12Oct99-0148PM) id SAA0000006916; Wed, 5 Jul 2000 18:00:03 +1000 (EST) Message-ID: <3962EAD8.E4DE217B@ozy.dec.com> Date: Wed, 05 Jul 2000 17:59:20 +1000 From: Charlie Flynn X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: linux-arm@vger.rutgers.edu Subject: Touch Screen Driver Generic Interface for all Linux SA11x0 platforms. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Hello, My name is Charlie Flynn and I have just completed V1.0 of a touch screen driver for the Compaq iPAQ H3600 running Linux 2.4.0-test1. I was thinking it would be a good idea if we had a generic interface to the touch screen drivers of all Linux SA11x0 platforms. This would allow clients ( such as the X windows device dependent layer ) to work, without modification, with all Linux SA11x0 touch screen drivers. I know it's a bit late to ask this ;-) but is there already a document describing a generic TSD interface for these platforms? Assuming there isn't such a document and also assuming people think it's worth pursuing I can start the ball rolling by posting a draft spec to the linux-arm-kernel mailing list which I assume would be the most appropriate place to discuss this issue. Regards --Charlie unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Wed Jul 05 10:49:06 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 139lnm-00089i-00 for linux-arm-archive@lists.arm.linux.org.uk; Wed, 05 Jul 2000 10:49:06 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 7828C15E5E; Wed, 5 Jul 2000 11:49:02 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Wed, 5 Jul 2000 05:38:36 -0400 Received: by vger.rutgers.edu id ; Wed, 5 Jul 2000 05:38:17 -0400 Received: from [159.226.21.134] ([159.226.21.134]:1277 "EHLO hw.ia.ac.cn") by vger.rutgers.edu with ESMTP id ; Wed, 5 Jul 2000 05:37:55 -0400 Received: from hw.ia.ac.cn ([159.226.21.171]) by hw.ia.ac.cn (8.9.3/8.8.7) with ESMTP id RAA15887; Wed, 5 Jul 2000 17:33:57 -0800 Message-ID: <396303C3.B97F77C4@hw.ia.ac.cn> Date: Wed, 05 Jul 2000 17:45:39 +0800 From: dai X-Mailer: Mozilla 4.7 [zh_CN] (X11; I; Linux 2.2.13 i686) X-Accept-Language: zh-CN, en MIME-Version: 1.0 To: nico@CAM.ORG, sa1100-linux@pa.dec.com, linux-arm@vger.rutgers.edu Subject: power management for Assabet? Content-Type: text/plain; charset=gb2312 Content-Transfer-Encoding: 7bit Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu nico, we seems to have fix UDA1341 driver.now itcan play 44.1k to 8k sound without noise,if you didnt fix it yet,i will mail it to you. is there anybody working on power management for Assabet?if not, could you give me some advice how to implement one? regards /dai unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Wed Jul 05 12:35:52 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 139nT6-0001IO-00 for linux-arm-archive@lists.arm.linux.org.uk; Wed, 05 Jul 2000 12:35:52 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id E242A15E67; Wed, 5 Jul 2000 13:35:50 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Wed, 5 Jul 2000 07:25:04 -0400 Received: by vger.rutgers.edu id ; Wed, 5 Jul 2000 07:24:46 -0400 Received: from p13-cordelia-gui.tch.enablis.net ([212.250.233.13]:1179 "EHLO caramon.arm.linux.org.uk") by vger.rutgers.edu with ESMTP id ; Wed, 5 Jul 2000 07:24:30 -0400 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 JAA02549; Wed, 5 Jul 2000 09:46:05 +0100 Received: (from linux@localhost) by flint.arm.linux.org.uk (8.9.3/8.9.3) id JAA01902; Wed, 5 Jul 2000 09:43:18 +0100 From: Russell King - ARM Linux Admin Message-Id: <200007050843.JAA01902@flint.arm.linux.org.uk> Subject: Re: Touch Screen Driver Generic Interface for all Linux SA11x0 platforms. To: flynn@ozy.dec.com (Charlie Flynn) Date: Wed, 5 Jul 2000 09:43:17 +0100 (BST) Cc: linux-arm@vger.rutgers.edu In-Reply-To: <3962EAD8.E4DE217B@ozy.dec.com> from "Charlie Flynn" at Jul 05, 2000 05:59:20 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@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Charlie Flynn writes: > I was thinking it would be a good idea if we had a generic interface to > the touch screen drivers of all Linux SA11x0 platforms. Indeed, or all Linux platforms if possible. You might try to find out about the following device, listed in linux/Documentation/devices.txt: 10 char Non-serial mice, misc features 11 = /dev/vrtpanel Vr41xx embedded touch panel > I know it's a bit late to ask this ;-) but is there already a document > describing a generic TSD interface for these platforms? Yes, there is a driver for the touchscreen on the assabet/graphicsclient, but it is written to be specific to the hardware on those machines. _____ |_____| ------------------------------------------------- ---+---+- | | Russell King linux@arm.linux.org.uk --- --- | | | | http://www.arm.linux.org.uk/ / / | | +-+-+ --- -+- / | THE developer of ARM Linux |+| /|\ / | | | --- | +-+-+ ------------------------------------------------- /\\\ | unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Wed Jul 05 14:15:36 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 139p1c-0002hP-00 for linux-arm-archive@lists.arm.linux.org.uk; Wed, 05 Jul 2000 14:15:36 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id D4CF315E5A; Wed, 5 Jul 2000 15:15:34 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Wed, 5 Jul 2000 09:05:03 -0400 Received: by vger.rutgers.edu id ; Wed, 5 Jul 2000 09:04:44 -0400 Received: from p16-robin-gui.tch.enablis.net ([194.168.180.76]:1224 "EHLO caramon.arm.linux.org.uk") by vger.rutgers.edu with ESMTP id ; Wed, 5 Jul 2000 09:04:38 -0400 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 MAA03145; Wed, 5 Jul 2000 12:51:56 +0100 Received: (from linux@localhost) by flint.arm.linux.org.uk (8.9.3/8.9.3) id MAA02524; Wed, 5 Jul 2000 12:49:08 +0100 From: Russell King - ARM Linux Admin Message-Id: <200007051149.MAA02524@flint.arm.linux.org.uk> Subject: Re: power management for Assabet? To: dai@hw.ia.ac.cn (dai) Date: Wed, 5 Jul 2000 12:49:08 +0100 (BST) Cc: nico@CAM.ORG, sa1100-linux@pa.dec.com, linux-arm@vger.rutgers.edu In-Reply-To: <396303C3.B97F77C4@hw.ia.ac.cn> from "dai" at Jul 05, 2000 05:45:39 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@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu dai writes: > is there anybody working on power management for Assabet? if not, > could you give me some advice how to implement one? Don't know if we've got proper power management yet, but I've added the "bare essentials" to the latest 2.4.0 ARM kernel. I have noticed that there may be a power management scheme in existance (to do with the mcp stuff?) already which does not use the 2.4.0 power management stuff. This appears to be incomplete in Nicos kernel. I'd like to persuade people to use the existing powermanagement APIs in the kernel, rather than re-inventing the square wheel. _____ |_____| ------------------------------------------------- ---+---+- | | Russell King linux@arm.linux.org.uk --- --- | | | | http://www.arm.linux.org.uk/ / / | | +-+-+ --- -+- / | THE developer of ARM Linux |+| /|\ / | | | --- | +-+-+ ------------------------------------------------- /\\\ | unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Wed Jul 05 14:43:08 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 139pSG-000386-00 for linux-arm-archive@lists.arm.linux.org.uk; Wed, 05 Jul 2000 14:43:08 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id A2EFD15E5A; Wed, 5 Jul 2000 15:43:07 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Wed, 5 Jul 2000 09:32:36 -0400 Received: by vger.rutgers.edu id ; Wed, 5 Jul 2000 09:32:18 -0400 Received: from h0000c06cf87e.ne.mediaone.net ([24.147.212.45]:1114 "EHLO compaq.parker.boston.ma.us") by vger.rutgers.edu with ESMTP id ; Wed, 5 Jul 2000 09:31:58 -0400 Received: from p2.parker.boston.ma.us (p2 [192.245.5.16]) by compaq.parker.boston.ma.us (8.8.5/8.8.5) with ESMTP id KAA26235; Wed, 5 Jul 2000 10:27:00 -0400 Received: from p2.parker.boston.ma.us (localhost [127.0.0.1]) by p2.parker.boston.ma.us (8.9.3/8.8.8) with ESMTP id JAA36192; Wed, 5 Jul 2000 09:39:27 -0400 (EDT) (envelope-from brad@p2.parker.boston.ma.us) Message-Id: <200007051339.JAA36192@p2.parker.boston.ma.us> To: sa1100-linux@pa.dec.com, linux-arm@vger.rutgers.edu Subject: Assabet dma & SA-1111.h GPIO defs Date: Wed, 05 Jul 2000 09:39:27 -0400 From: Brad Parker Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Hi, I've added basic dma support for the SA-1100, mostly to support the internal USB function controller. Does anyone want this? Is there a BK tree somewhere to add things to? Also, are the GPIO defines in arch-sa1000/SA-1111.h correct? They look wrong to me. Specifically, shouldn't #define _PA_DDR _SA1111( 0x1000 ) ... be #define _PA_DDR _SA1111( 0x0e00 ) ... ? All the other defines match up with my docs correct, but the GPIO one maps to A12:9=8 and my docs say it should A12:9=7 (or 0x0e00). -brad unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Wed Jul 05 15:10:32 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 139psm-0003a1-00 for linux-arm-archive@lists.arm.linux.org.uk; Wed, 05 Jul 2000 15:10:32 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 2B25515E7E; Wed, 5 Jul 2000 16:10:21 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Wed, 5 Jul 2000 09:55:41 -0400 Received: by vger.rutgers.edu id ; Wed, 5 Jul 2000 09:55:32 -0400 Received: from SMTP1.ANDREW.CMU.EDU ([128.2.10.81]:34654 "EHLO smtp1.andrew.cmu.edu") by vger.rutgers.edu with ESMTP id ; Wed, 5 Jul 2000 09:55:19 -0400 Received: from unix10.andrew.cmu.edu (UNIX10.ANDREW.CMU.EDU [128.2.15.14]) by smtp1.andrew.cmu.edu (8.9.3/8.9.3) with SMTP id KAA09213; Wed, 5 Jul 2000 10:01:45 -0400 (EDT) Date: Wed, 5 Jul 2000 10:01:46 -0400 (EDT) From: John G Dorsey To: Brad Parker Cc: sa1100-linux@pa.dec.com, linux-arm@vger.rutgers.edu Subject: Re: Assabet dma & SA-1111.h GPIO defs In-Reply-To: <200007051339.JAA36192@p2.parker.boston.ma.us> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu On Wed, 5 Jul 2000, Brad Parker wrote: > #define _PA_DDR _SA1111( 0x1000 ) ... > > ? All the other defines match up with my docs correct, but the GPIO > one maps to A12:9=8 and my docs say it should A12:9=7 (or 0x0e00). These came from section 10.3.6 ("Memory Map") of the SA-1111 developer's manual; this section doesn't seem to have been modified in the manual update. Since the block A GPIO drives the MAX1600 on Neponset, and that actually appears to work with the current definitions, I've felt comfortable believing that these macros were correct (at least in the patch I submitted to Nicolas; I haven't looked at the last few -np releases). Which part of the documentation seems in conflict? -jd unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Wed Jul 05 18:46:53 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 139tG9-0007IM-00 for linux-arm-archive@lists.arm.linux.org.uk; Wed, 05 Jul 2000 18:46:53 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id CDD6515DD5; Wed, 5 Jul 2000 19:46:52 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Wed, 5 Jul 2000 13:36:11 -0400 Received: by vger.rutgers.edu id ; Wed, 5 Jul 2000 13:36:06 -0400 Received: from h0000c06cf87e.ne.mediaone.net ([24.147.212.45]:1711 "EHLO compaq.parker.boston.ma.us") by vger.rutgers.edu with ESMTP id ; Wed, 5 Jul 2000 13:35:50 -0400 Received: from p2.parker.boston.ma.us (p2 [192.245.5.16]) by compaq.parker.boston.ma.us (8.8.5/8.8.5) with ESMTP id OAA26662; Wed, 5 Jul 2000 14:30:54 -0400 Received: from p2.parker.boston.ma.us (localhost [127.0.0.1]) by p2.parker.boston.ma.us (8.9.3/8.8.8) with ESMTP id NAA36934; Wed, 5 Jul 2000 13:46:21 -0400 (EDT) (envelope-from brad@p2.parker.boston.ma.us) Message-Id: <200007051746.NAA36934@p2.parker.boston.ma.us> To: John G Dorsey Cc: sa1100-linux@pa.dec.com, linux-arm@vger.rutgers.edu Subject: Re: Assabet dma & SA-1111.h GPIO defs In-reply-to: Your message of "Wed, 05 Jul 2000 10:01:46 EDT." Date: Wed, 05 Jul 2000 13:46:21 -0400 From: Brad Parker Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu John G Dorsey wrote: >On Wed, 5 Jul 2000, Brad Parker wrote: >> #define _PA_DDR _SA1111( 0x1000 ) >... >> >> ? All the other defines match up with my docs correct, but the GPIO >> one maps to A12:9=8 and my docs say it should A12:9=7 (or 0x0e00). > >These came from section 10.3.6 ("Memory Map") of the SA-1111 developer's >manual; this section doesn't seem to have been modified in the manual >update. Since the block A GPIO drives the MAX1600 on Neponset, and that >actually appears to work with the current definitions, I've felt >comfortable believing that these macros were correct (at least in the >patch I submitted to Nicolas; I haven't looked at the last few -np >releases). > >Which part of the documentation seems in conflict? Well, looking back at the docs now I'm totally confused. Yes, you are correct, 10.3.6 does say it should be at 0x1000. However, The SA-1111 developer's manual, pg 3-4 shows the GPIO at 0x1000-0x11ff (it also shows the OHCI controller at 0x400, which is what I really wanted) Page 4-2, however ("RAB Target Blocks/Address Assignment") shows a table where "Address A<12:9>" is 2 for the USB (this makes 0x400, which seems right) and 7 for the GPIO (which makes 0x0e00, *not* 0x1000). Further, it shows 8 (which makes 0x1000) as "reserved". In the "Specification Update October 1999", page 21, Figure 4-1 is updated and matches the "RAB Target Blocks/Address Assignment" table... I'll go with 10.3.6 :-) -brad unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Thu Jul 06 15:42:46 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13ACrW-0008Bm-00 for linux-arm-archive@lists.arm.linux.org.uk; Thu, 06 Jul 2000 15:42:46 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 9863315F6D; Thu, 6 Jul 2000 16:39:18 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Thu, 6 Jul 2000 10:28:22 -0400 Received: by vger.rutgers.edu id ; Thu, 6 Jul 2000 10:27:00 -0400 Received: from netwinder.org ([207.245.35.202]:63992 "EHLO kei.netwinder.org") by vger.rutgers.edu with ESMTP id ; Thu, 6 Jul 2000 10:26:04 -0400 Received: from netwinder.org ([10.1.19.121]) by kei.netwinder.org (8.9.3/8.9.3) with ESMTP id KAA26751; Thu, 6 Jul 2000 10:33:59 -0400 Message-ID: <3964978E.C6A94709@netwinder.org> Date: Thu, 06 Jul 2000 10:28:30 -0400 From: Scott Bambrough Organization: Rebel.com X-Mailer: Mozilla 4.7 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: ICN TR ON DA 1 Werkstudent1 Cc: "'linux-arm@vger.rutgers.edu'" Subject: Re: Faster FP emulation for Linux References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Hi Peter, I would start with the emulator. I'd wait and see what shakes out in soft-float in the next release of gcc. I'm afraid you would do all the work in libfloat, only to find the ARM switched to use floating point routines compiled into libgcc.a. Scott ICN TR ON DA 1 Werkstudent1 wrote: > > Hi, > > from porting Quake to the RiscPC I have some quite fast single precision floating > point routines, they reach between 3 and 5 MFlops on a SA RiscPC. I thought that > it would be a nice option to have them available as in Linux. > > I recognized that there are two options, one is the FP emulator, and another one > is the softfloat library for GCC. Which of these is used in our days? And what is a good starting point for this work? > > Peter Teichmann > > unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu > ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ > ++ kernel-related discussions. ++ -- Scott Bambrough - Software Engineer REBEL.COM http://www.rebel.com NetWinder http://www.netwinder.org unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Thu Jul 06 19:06:12 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13AG2O-0003FX-00 for linux-arm-archive@lists.arm.linux.org.uk; Thu, 06 Jul 2000 19:06:12 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 7DCB815F10; Thu, 6 Jul 2000 20:06:10 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Thu, 6 Jul 2000 13:54:30 -0400 Received: by vger.rutgers.edu id ; Thu, 6 Jul 2000 13:52:19 -0400 Received: from flatpanels.com ([207.196.69.66]:1829 "EHLO ADSServer.flatpanels.com") by vger.rutgers.edu with ESMTP id ; Thu, 6 Jul 2000 13:51:44 -0400 Received: by flatpanels.com with Internet Mail Service (5.5.2650.21) id <3MSHLR80>; Thu, 6 Jul 2000 13:53:59 -0400 Message-ID: <91B07CA588CED3118CFE00105AC97594026F93@flatpanels.com> From: "Huh, Woojung" To: "'linux-arm@vger.rutgers.edu'" Subject: Question about 2.4.0-test2-ac1-rmk2-np3 Date: Thu, 6 Jul 2000 13:53:50 -0400 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@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu All; I upgraded to 2.4.0-test2-ac1-rmk2-np3 from 2.3.35. I had some problems. Some are fixed but some are not. I use ADS graphics client. 1. after booting, I execute "df" command. It displays Filesystem 1k-blocks Used Available Use% Mounted on none 5947 4886 754 87% / pipe:: No such file or directory none 5947 4886 754 87% / none 5947 4886 754 87% / /dev/root 5947 4886 754 87% / 2. I can not use flash file system. Errors are follows EXT2-fs error (device flash(60,2)): ext2_new_block: Allocating block in system zone - block = 8384 Flash driver: programming voltage error! end_request: I/O error, dev 3c:02 (flash), sector 2 3. Ethernet seems not to work. It displays wrong MAC address. Thanks in advance. Woojung Huh unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Thu Jul 06 19:49:10 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13AGhy-0003u6-00 for linux-arm-archive@lists.arm.linux.org.uk; Thu, 06 Jul 2000 19:49:10 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 450B715F69; Thu, 6 Jul 2000 20:45:59 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Thu, 6 Jul 2000 14:33:40 -0400 Received: by vger.rutgers.edu id ; Thu, 6 Jul 2000 14:33:21 -0400 Received: from duteinh.et.tudelft.nl ([130.161.42.1]:3575 "EHLO duteinh.et.tudelft.nl") by vger.rutgers.edu with ESMTP id ; Thu, 6 Jul 2000 14:17:44 -0400 Received: from lumiere by duteinh.et.tudelft.nl (8.9.3/BB-2.0) id UAA10348; Thu, 6 Jul 2000 20:26:27 +0200 (MET DST) Message-Id: <200007061826.UAA10348@duteinh.et.tudelft.nl> From: Erik Mouw To: linux@arm.linux.org.uk Cc: dai@hw.ia.ac.cn, nico@CAM.ORG, sa1100-linux@pa.dec.com, linux-arm@vger.rutgers.edu Subject: Re: power management for Assabet? In-Reply-To: <200007051149.MAA02524@flint.arm.linux.org.uk> Organization: Eric conspiracy secret labs Date: Thu 06 Jul 2000 20:26:26 +0100 (MDT) 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.2devel - with PGP support, PGP engine version 0.5 (IRIX64) X-Mailerorigin: http://www.fsai.fh-trier.de/~schmitzj/Xclasses/XCmail/ X-Eric-Conspiracy: There is no conspiracy! X-Loop: erik@it.et.tudelft.nl MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu On Wed, 5 Jul 2000 12:49:08 +0100 (BST), Russell King - ARM Linux Admin wrote: > dai writes: >> is there anybody working on power management for Assabet? if not, >> could you give me some advice how to implement one? > > Don't know if we've got proper power management yet, but I've added the > "bare essentials" to the latest 2.4.0 ARM kernel. Yup, I noticed, thanks. > I have noticed that there may be a power management scheme in existance > (to do with the mcp stuff?) already which does not use the 2.4.0 power > management stuff. This appears to be incomplete in Nicos kernel. The power management in the MCP audio is still from the old Itsy driver. I just ported the driver to linux-2.3.xx but didn't remove the cruft. > I'd like to persuade people to use the existing powermanagement APIs in > the kernel, rather than re-inventing the square wheel. That's actually my plan, too. Being compatible with the standard tools is a nice thing. 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-2783635 Fax: +31-15-2781843 Email: J.A.K.Mouw@its.tudelft.nl WWW: http://www-ict.its.tudelft.nl/~erik/ unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Thu Jul 06 21:12:22 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13AI0U-0005BF-00 for linux-arm-archive@lists.arm.linux.org.uk; Thu, 06 Jul 2000 21:12:22 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 0EDF115F77; Thu, 6 Jul 2000 22:05:43 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Thu, 6 Jul 2000 15:51:07 -0400 Received: by vger.rutgers.edu id ; Thu, 6 Jul 2000 15:50:53 -0400 Received: from p16-robin-gui.tch.enablis.net ([194.168.180.76]:2829 "EHLO caramon.arm.linux.org.uk") by vger.rutgers.edu with ESMTP id ; Thu, 6 Jul 2000 15:49:19 -0400 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 UAA10158; Thu, 6 Jul 2000 20:59:35 +0100 Received: (from linux@localhost) by flint.arm.linux.org.uk (8.9.3/8.9.3) id UAA12549; Thu, 6 Jul 2000 20:56:45 +0100 From: Russell King - ARM Linux Admin Message-Id: <200007061956.UAA12549@flint.arm.linux.org.uk> Subject: Re: Question about 2.4.0-test2-ac1-rmk2-np3 To: WHuh@flatpanels.com (Huh, Woojung) Date: Thu, 6 Jul 2000 20:56:44 +0100 (BST) Cc: linux-arm@vger.rutgers.edu ('linux-arm@vger.rutgers.edu') In-Reply-To: <91B07CA588CED3118CFE00105AC97594026F93@flatpanels.com> from "Huh, Woojung" at Jul 06, 2000 01:53:50 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@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Huh, Woojung writes: > 1. after booting, I execute "df" command. It displays > Filesystem 1k-blocks Used Available Use% Mounted on > none 5947 4886 754 87% / > pipe:: No such file or directory > none 5947 4886 754 87% / > none 5947 4886 754 87% / > /dev/root 5947 4886 754 87% / This is not a bug - the kernel now mounts certain filesystems internally, which means that /proc/mounts will contain this information. If your /etc/mtab is symlinked to this "virtual" file, then this is the output I'd expect. _____ |_____| ------------------------------------------------- ---+---+- | | Russell King linux@arm.linux.org.uk --- --- | | | | http://www.arm.linux.org.uk/ / / | | +-+-+ --- -+- / | THE developer of ARM Linux |+| /|\ / | | | --- | +-+-+ ------------------------------------------------- /\\\ | unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Fri Jul 07 16:06:55 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13AZiR-0005bP-00 for linux-arm-archive@lists.arm.linux.org.uk; Fri, 07 Jul 2000 16:06:55 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 637B515FF2; Fri, 7 Jul 2000 17:04:48 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Fri, 7 Jul 2000 10:53:19 -0400 Received: by vger.rutgers.edu id ; Fri, 7 Jul 2000 10:51:14 -0400 Received: from [194.201.77.34] ([194.201.77.34]:60123 "HELO fw-maid.maidenhead.arm.com") by vger.rutgers.edu with SMTP id ; Fri, 7 Jul 2000 10:50:32 -0400 Received: by fw-maid.maidenhead.arm.com; id PAA10581; Fri, 7 Jul 2000 15:58:26 +0100 Received: from unknown(192.168.2.10) by fw-maid.maidenhead.arm.com via smap (V5.0) id xma010578; Fri, 7 Jul 00 15:57:35 +0100 Received: from arm.com (dhcp2 [192.168.2.232]) by mhsun1.maidenhead.arm.com (8.9.3/8.9.3) with ESMTP id QAA27251 for ; Fri, 7 Jul 2000 16:00:17 +0100 (BST) Message-ID: <3965FBD3.65402A14@arm.com> Date: Fri, 07 Jul 2000 16:48:35 +0100 From: David Rusling X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: linux-arm Subject: Building cross libraries Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu All, I've been 'playing' with cross-tools. Using the various helpful help files (Phil Blundell and Chris Rutter) I can now build binutils-2.9.5 and gcc-2.95.1 every which way. However, I cannot build glibc-2.1 or newlib-1.8.2. Configuring newlib fail's 'cos it cannot compile/link a test image. (I'm assuming arm-linux as the build variant). It fails with unsupported emulations. I'm guessing that the kernel builds 'cos it uses steering files for this stuff. Following Chris's instructions, glibc-2.1 fails because gcc 2.95.1 is not the correct version. I hacked the configure file but it fails as it builds it later on. So, help! Dave ---------------------------------------------------------------------- David A Rusling Consulting Engineer ARM Limited Liberty House, Moorbridge Road, Maidenhead, SL6 8LT Tel: UK-(0)1628-427754 Fax: UK-(0)1628-780551 e-mail: david.rusling@arm.com ---------------------------------------------------------------------- unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Fri Jul 07 18:39:45 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13Ac6L-0007aC-00 for linux-arm-archive@lists.arm.linux.org.uk; Fri, 07 Jul 2000 18:39:45 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 3698116070; Fri, 7 Jul 2000 19:32:11 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Fri, 7 Jul 2000 13:19:01 -0400 Received: by vger.rutgers.edu id ; Fri, 7 Jul 2000 13:18:23 -0400 Received: from [63.192.220.206] ([63.192.220.206]:62589 "EHLO hermes.mvista.com") by vger.rutgers.edu with ESMTP id ; Fri, 7 Jul 2000 13:17:34 -0400 Received: from mvista.com (IDENT:mhatle@gemini.mvista.com [10.0.0.101]) by hermes.mvista.com (8.9.3/8.9.3) with ESMTP id KAA24947; Fri, 7 Jul 2000 10:27:42 -0700 Message-ID: <3966136A.E2C8A672@mvista.com> Date: Fri, 07 Jul 2000 10:29:14 -0700 From: Mark Hatle Organization: MontaVista Software, Inc. X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.4.0-test2 i686) X-Accept-Language: en MIME-Version: 1.0 To: David Rusling Cc: linux-arm Subject: Re: Building cross libraries References: <3965FBD3.65402A14@arm.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu For our cross tools, we are currently using gcc-2.95.2 (with some back patches + my softfloat patch), glibc-2.1.3 and the latest binutils. If you would like a snap-shot let me know.. (I have them on my personal server, otherwise I'd post the URL for them. If there is enough demand, I may see about getting the current tool chain up on the MontaVista ftp site.) --Mark David Rusling wrote: > > All, > > I've been 'playing' with cross-tools. Using the various helpful help > files (Phil Blundell and Chris Rutter) I can now build binutils-2.9.5 > and gcc-2.95.1 every which way. However, I cannot build glibc-2.1 > or newlib-1.8.2. > > Configuring newlib fail's 'cos it cannot compile/link a test image. > (I'm assuming arm-linux as the build variant). It fails with unsupported > emulations. I'm guessing that the kernel builds 'cos it uses steering files > for this stuff. > > Following Chris's instructions, glibc-2.1 fails because gcc 2.95.1 > is not the correct version. I hacked the configure file but it fails > as it builds it later on. > > So, help! Dave > > ---------------------------------------------------------------------- > David A Rusling Consulting Engineer > ARM Limited > Liberty House, > Moorbridge Road, > Maidenhead, SL6 8LT > > Tel: UK-(0)1628-427754 > Fax: UK-(0)1628-780551 > e-mail: david.rusling@arm.com > ---------------------------------------------------------------------- > > unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu > ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ > ++ kernel-related discussions. ++ unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Fri Jul 07 23:43:51 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13Agqc-0004wY-00 for linux-arm-archive@lists.arm.linux.org.uk; Fri, 07 Jul 2000 23:43:51 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 6F43D16073; Sat, 8 Jul 2000 00:38:45 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Fri, 7 Jul 2000 18:22:53 -0400 Received: by vger.rutgers.edu id ; Fri, 7 Jul 2000 18:21:23 -0400 Received: from ganymede.or.intel.com ([134.134.248.3]:3538 "EHLO ganymede.or.intel.com") by vger.rutgers.edu with ESMTP id ; Fri, 7 Jul 2000 18:20:19 -0400 Received: from SMTP (orsmsxvs01-1.jf.intel.com [192.168.65.200]) by ganymede.or.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.30 2000/06/08 18:25:35 dmccart Exp $) with SMTP id PAA06367 for ; Fri, 7 Jul 2000 15:31:01 -0700 (PDT) Received: from orsmsx28.jf.intel.com ([192.168.70.28]) by 192.168.70.200 (Norton AntiVirus for Internet Email Gateways 1.0) ; Fri, 07 Jul 2000 22:31:00 0000 (GMT) Received: by orsmsx28.jf.intel.com with Internet Mail Service (5.5.2650.21) id <3KFJ8YZ7>; Fri, 7 Jul 2000 15:30:59 -0700 Message-ID: From: "Rao, Ram R" To: "'linux-arm@vger.rutgers.edu'" Subject: using pcmcia on assabet Date: Fri, 7 Jul 2000 15:30:51 -0700 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@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Hi, Could someone give me an overview as to how to use compact flash on the assabet? I've got 32 meg compact flash cards (from viking and kinsgton), and the socket comm ethernet card. I'm running the 2.4.0-test1-ac7-rmk1-np4. (I accepted all defaults after running make assabet_config which included pcmcia support, and ide and ethernet support). I downloaded the ramdisk from CMU's website, and by using cardctl, it appears that power is applied to the card, and it can read the vendor information. However, it doesn't appear that any driver gets loaded for the compact flash card. I would expect to see an ide device in /proc/devices, but I don't. How do you go about mounting a compact flash card? Likewise, what steps are necessary to get the ethernet working? Thanks for your help, Ram Rao unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Sat Jul 08 03:23:12 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13AkGu-00078G-00 for linux-arm-archive@lists.arm.linux.org.uk; Sat, 08 Jul 2000 03:23:12 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id F0B5315FFF; Sat, 8 Jul 2000 04:23:11 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Fri, 7 Jul 2000 22:11:41 -0400 Received: by vger.rutgers.edu id ; Fri, 7 Jul 2000 22:11:21 -0400 Received: from cogeco-29-65.cgocable.net ([24.141.29.65]:64916 "EHLO embeddedobjects.org") by vger.rutgers.edu with ESMTP id ; Fri, 7 Jul 2000 22:11:08 -0400 Received: from cgocable.net (softdnserr [::ffff:192.168.0.2]) (IDENT: hbelange) by embeddedobjects.org with esmtp; Fri, 07 Jul 2000 22:21:55 -0400 Message-ID: <39669101.E8D7A74A@cgocable.net> Date: Fri, 07 Jul 2000 22:25:05 -0400 From: Hugues Belanger X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i586) X-Accept-Language: en MIME-Version: 1.0 Cc: "'linux-arm@vger.rutgers.edu'" Subject: Compiling apps with toolchain References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: unlisted-recipients: ;(no To-header on input) Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu I have a new found respect and admiration for developers now...! I've been trying to port my favorite firewall/router distribution the the Arm platform only to find that man I need to know so much before I can get their..! I've got compaq's tool chain, I've patch and compile the kernel and modules, I've got all the libs I need (I cheated here a little and objcopy from skiff ramdrive). now I have to port user space apps ??????????? Were do i start ? Thanks Hugues unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Sat Jul 08 03:31:24 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13AkOq-0007FY-00 for linux-arm-archive@lists.arm.linux.org.uk; Sat, 08 Jul 2000 03:31:24 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id C016515F87; Sat, 8 Jul 2000 04:31:23 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Fri, 7 Jul 2000 22:20:17 -0400 Received: by vger.rutgers.edu id ; Fri, 7 Jul 2000 22:19:59 -0400 Received: from modemcable248.137-200-24.mtl.mc.videotron.net ([24.200.137.248]:61307 "EHLO xanadu.gn.com") by vger.rutgers.edu with ESMTP id ; Fri, 7 Jul 2000 22:19:48 -0400 Received: from localhost (nico@localhost) by xanadu.gn.com (8.9.3/8.9.3) with ESMTP id WAA28035; Fri, 7 Jul 2000 22:29:29 -0400 X-Authentication-Warning: xanadu.gn.com: nico owned process doing -bs Date: Fri, 7 Jul 2000 22:29:29 -0400 (EDT) From: Nicolas Pitre X-Sender: nico@xanadu.gn.com To: "Rao, Ram R" Cc: "'linux-arm@vger.rutgers.edu'" Subject: Re: using pcmcia on assabet In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu On Fri, 7 Jul 2000, Rao, Ram R wrote: > Hi, > Could someone give me an overview as to how to use compact flash on > the assabet? I've got 32 meg compact flash cards (from viking and kinsgton), > and the socket comm ethernet card. I'm running the 2.4.0-test1-ac7-rmk1-np4. You should consider moving to a more recent patch since PCMCIA wasn't fully working with older patches. Nicolas unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Sat Jul 08 14:23:26 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13AuZq-0006TD-00 for linux-arm-archive@lists.arm.linux.org.uk; Sat, 08 Jul 2000 14:23:26 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 6CB8C16092; Sat, 8 Jul 2000 15:23:23 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Sat, 8 Jul 2000 09:10:59 -0400 Received: by vger.rutgers.edu id ; Sat, 8 Jul 2000 09:10:33 -0400 Received: from [194.201.77.34] ([194.201.77.34]:60326 "HELO fw-maid.maidenhead.arm.com") by vger.rutgers.edu with SMTP id ; Sat, 8 Jul 2000 09:08:20 -0400 Received: by fw-maid.maidenhead.arm.com; id OAA12809; Sat, 8 Jul 2000 14:16:28 +0100 Received: from dhcp3.maidenhead.arm.com(192.168.2.173) by fw-maid.maidenhead.arm.com via smap (V5.0) id xma012805; Sat, 8 Jul 00 14:15:53 +0100 Received: from localhost (localhost [[UNIX: localhost]]) by idoru.maidenhead.arm.com (8.9.3/8.9.3) id OAA00823; Sat, 8 Jul 2000 14:27:53 +0100 From: David A Rusling To: Mark Hatle , David Rusling Subject: Re: Building cross libraries Date: Sat, 8 Jul 2000 14:27:52 +0100 X-Mailer: KMail [version 1.1.41.10] Content-Type: text/plain; charset=US-ASCII Cc: linux-arm References: <3965FBD3.65402A14@arm.com> <3966136A.E2C8A672@mvista.com> In-Reply-To: <3966136A.E2C8A672@mvista.com> MIME-Version: 1.0 Message-Id: <00070814275200.00816@idoru> Content-Transfer-Encoding: 7BIT Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu On Fri, 07 Jul 2000, Mark Hatle wrote: > For our cross tools, we are currently using gcc-2.95.2 (with some back > patches + my softfloat patch), glibc-2.1.3 and the latest binutils. > > If you would like a snap-shot let me know.. (I have them on my personal > server, otherwise I'd post the URL for them. If there is enough demand, > I may see about getting the current tool chain up on the MontaVista ftp > site.) > I'll give it a shot but I would like your stuff to compare against. As of now I have a set of cross tools that can build Linux and eCOS/GDB. That means that I can port the kernel and play with the GNU tools, next step is be able to cross build (ARM) applications. Basically, the ARM embedded Linux space is about to explode and I see the abilty to cross-develop on Intel Linux the quickest way forwards for most... Dave > --Mark > > David Rusling wrote: > > All, > > > > I've been 'playing' with cross-tools. Using the various helpful > > help files (Phil Blundell and Chris Rutter) I can now build > > binutils-2.9.5 and gcc-2.95.1 every which way. However, I cannot build > > glibc-2.1 or newlib-1.8.2. > > > > Configuring newlib fail's 'cos it cannot compile/link a test image. > > (I'm assuming arm-linux as the build variant). It fails with > > unsupported emulations. I'm guessing that the kernel builds 'cos it uses > > steering files for this stuff. > > > > Following Chris's instructions, glibc-2.1 fails because gcc 2.95.1 > > is not the correct version. I hacked the configure file but it fails > > as it builds it later on. > > > > So, help! Dave > > > > ---------------------------------------------------------------------- > > David A Rusling Consulting Engineer > > ARM Limited > > Liberty House, > > Moorbridge Road, > > Maidenhead, SL6 8LT > > > > Tel: UK-(0)1628-427754 > > Fax: UK-(0)1628-780551 > > e-mail: david.rusling@arm.com > > ---------------------------------------------------------------------- > > > > unsubscribe: body of `unsubscribe linux-arm' to > > majordomo@vger.rutgers.edu ++ Please use > > linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ > > kernel-related discussions. ++ unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Sat Jul 08 16:34:49 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13Awcz-0008F7-00 for linux-arm-archive@lists.arm.linux.org.uk; Sat, 08 Jul 2000 16:34:49 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 6A01516083; Sat, 8 Jul 2000 17:34:37 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Sat, 8 Jul 2000 11:22:58 -0400 Received: by vger.rutgers.edu id ; Sat, 8 Jul 2000 11:22:39 -0400 Received: from crl.dec.com ([192.58.206.2]:4480 "EHLO crl.dec.com") by vger.rutgers.edu with ESMTP id ; Sat, 8 Jul 2000 11:22:35 -0400 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 LAA26506; Sat, 8 Jul 2000 11:33:14 -0400 (EDT) Received: by crlwebmail.crl.dec.com with Internet Mail Service (5.5.2650.21) id ; Sat, 8 Jul 2000 11:38:05 -0400 Message-ID: From: George France To: "'Hugues Belanger'" , unlisted-recipients Cc: "'linux-arm@vger.rutgers.edu'" Subject: RE: Compiling apps with toolchain Date: Sat, 8 Jul 2000 11:33:11 -0400 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@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu This should give you a good start. ftp.handhelds.org/pub/linux/arm/carleton-winder-rpms --George George France, france@crl.dec.com Cambridge Research Laboratory, Compaq Computer Corporation One Cambridgecenter MS: CRL Cambridge, MA 02142 USA -----Original Message----- From: Hugues Belanger [mailto:hbelange@cgocable.net] Sent: Friday, July 07, 2000 10:25 PM To: unlisted-recipients Cc: 'linux-arm@vger.rutgers.edu' Subject: Compiling apps with toolchain I have a new found respect and admiration for developers now...! I've been trying to port my favorite firewall/router distribution the the Arm platform only to find that man I need to know so much before I can get their..! I've got compaq's tool chain, I've patch and compile the kernel and modules, I've got all the libs I need (I cheated here a little and objcopy from skiff ramdrive). now I have to port user space apps ??????????? Were do i start ? Thanks Hugues unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Sun Jul 09 00:36:06 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13B48k-00061D-00 for linux-arm-archive@lists.arm.linux.org.uk; Sun, 09 Jul 2000 00:36:06 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 3C9701607E; Sat, 8 Jul 2000 22:11:34 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Sat, 8 Jul 2000 15:59:44 -0400 Received: by vger.rutgers.edu id ; Sat, 8 Jul 2000 15:59:31 -0400 Received: from tazenda.demon.co.uk ([158.152.220.239]:4247 "EHLO tazenda.demon.co.uk") by vger.rutgers.edu with ESMTP id ; Sat, 8 Jul 2000 15:57:57 -0400 Received: from kings-cross.london.uk.eu.org [::ffff:192.168.2.83] by tazenda.demon.co.uk with esmtp (Exim 3.11 #1 (Debian)) id 13Ax7D-0002oP-00; Sat, 08 Jul 2000 17:06:03 +0100 Received: from localhost ([::ffff:127.0.0.1] helo=kings-cross.london.uk.eu.org ident=phil) by kings-cross.london.uk.eu.org with esmtp (Exim 3.12 #1) id 13Ax7A-0005Iz-00; Sat, 08 Jul 2000 17:06:00 +0100 X-Mailer: exmh version 2.1.1 10/15/1999 (debian) To: David Rusling Cc: linux-arm Subject: Re: Building cross libraries In-Reply-To: Message from David Rusling of "Fri, 07 Jul 2000 16:48:35 BST." <3965FBD3.65402A14@arm.com> References: <3965FBD3.65402A14@arm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 08 Jul 2000 17:05:59 +0100 From: Philip Blundell Message-Id: Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu > I've been 'playing' with cross-tools. Using the various helpful help >files (Phil Blundell and Chris Rutter) I can now build binutils-2.9.5 >and gcc-2.95.1 every which way. However, I cannot build glibc-2.1 >or newlib-1.8.2. You might like to get binutils 2.10 and gcc "2.95.3" (ie the latest from the 2.95 branch in CVS). > Following Chris's instructions, glibc-2.1 fails because gcc 2.95.1 >is not the correct version. I hacked the configure file but it fails >as it builds it later on. What failure are you seeing during the compile? I used to cross-build glibc all the time, though I haven't done it recently. p. unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Sun Jul 09 01:09:42 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13B4fG-0006Tf-00 for linux-arm-archive@lists.arm.linux.org.uk; Sun, 09 Jul 2000 01:09:42 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 3EF64160A5; Sun, 9 Jul 2000 00:05:18 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Sat, 8 Jul 2000 17:53:47 -0400 Received: by vger.rutgers.edu id ; Sat, 8 Jul 2000 17:53:29 -0400 Received: from btamail.net.cn ([202.106.196.131]:64597 "HELO btamail.net.cn") by vger.rutgers.edu with SMTP id ; Sat, 8 Jul 2000 17:53:21 -0400 Received: from eadsmobile([202.106.214.232]) by btamail.net.cn(JetMail 2.3.1.0) with SMTP id /m0/jmail.rcv/1/jmc3967a7fa; Sat, 8 Jul 2000 22:04:12 -0000 Message-ID: <018e01bfe928$f33195e0$2e7777de@eadsmobile> From: "Eads Sun" To: "Arm-Linux" Subject: How to create Ramdisk step by step for Cirrus Logic EP7212? Date: Sun, 9 Jul 2000 06:07:46 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4131.1600 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4131.1600 Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Dear All, Excuse me, i'm rather unfamiliar with the Linux boot procedure. i wonder where i can obtain a RAMdisk image for Cirrus Logic EP7212, how to create a RAMdisk image for the CL-EP7212, Only i can find a sample of Ramdisk , The WWW link in: http://developer.intel.com/design/strong/applnots/sa1100lx/download.htm#1001 846 however, ftp://ssdl-redstone.stanford.edu/pub/ramdisk.gz is broken. Best Regards, _____________________________________________________ Eads Sun Teh EOS of Unitop Corp. E-mail: yzhsun@btamail.net.cn Mobile: +86-13801124332 Office Tel. +86-10-69498555 ext 13 unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Sun Jul 09 09:41:35 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13BCed-0004vH-00 for linux-arm-archive@lists.arm.linux.org.uk; Sun, 09 Jul 2000 09:41:35 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id DE61E15D4F; Sun, 9 Jul 2000 10:41:36 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Sun, 9 Jul 2000 04:29:53 -0400 Received: by vger.rutgers.edu id ; Sun, 9 Jul 2000 04:29:44 -0400 Received: from ns0.utdallas.edu ([129.110.10.1]:40231 "HELO ns0.utdallas.edu") by vger.rutgers.edu with SMTP id ; Sun, 9 Jul 2000 04:29:26 -0400 Received: from apache.utdallas.edu (apache.utdallas.edu [129.110.16.9]) by ns0.utdallas.edu (Postfix) with ESMTP id EE09C1A0228; Sun, 9 Jul 2000 03:40:22 -0500 (CDT) Received: from localhost (vasantr@localhost) by apache.utdallas.edu (8.9.1/8.9.1) with ESMTP id DAA00528; Sun, 9 Jul 2000 03:40:34 -0500 (CDT) X-Authentication-Warning: apache.utdallas.edu: vasantr owned process doing -bs Date: Sun, 9 Jul 2000 03:40:34 -0500 (CDT) From: Vasant Ramasubramanian To: sa1100-linux@pa.dec.com, linux-arm@vger.rutgers.edu Subject: Brutus/SA1100 Issues Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Hello all; I am having difficulty getting my Brutus to work after it was sent in for repair and I'm not sure what the problem is yet... When I use Nico's brutustest kernel+ramdisk+angel on the debugging console I get some interesting startup messages. I get: ... Calibrating delay loop 194.15 BogoMIPS ... Starting kswapd 1.5 IRQ LOCK: IRQ 12 is locking the system, disabled Console: Switching to colour framebuffer device 40x30 and then it hangs. I notice that a few pixels on the Tux that appears on the LCD seem to be "blinking" after the hang. I poped open the CPU socket and apparently I have a "StrongARM SA-1100B" Anyone have any idea what speed grade this is? It wasn't listed in the SA1100 manual that I have. Any ideas? Thanks, Vasant. unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 10 01:43:29 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13BRfV-00080z-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 10 Jul 2000 01:43:29 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 0B6C815DE4; Mon, 10 Jul 2000 02:43:29 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Sun, 9 Jul 2000 20:31:40 -0400 Received: by vger.rutgers.edu id ; Sun, 9 Jul 2000 20:31:31 -0400 Received: from whistler.artisan.calpoly.edu ([129.65.2.41]:3747 "EHLO rubens.artisan.calpoly.edu") by vger.rutgers.edu with ESMTP id ; Sun, 9 Jul 2000 20:31:22 -0400 Received: from synthis (synthis.ee.calpoly.edu [129.65.26.204]) by rubens.artisan.calpoly.edu (8.8.6 (PHNE_17135)/8.8.6) with SMTP id RAA10909 for ; Sun, 9 Jul 2000 17:42:20 -0700 (PDT) Message-ID: <008401bfea07$28a90760$cc1a4181@synthis> From: "Jim Fischer" To: "ARM Linux" Subject: i686->StrongARM gcc/g++ cross compile problems Date: Sun, 9 Jul 2000 17:38:16 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu I'm in the process of creating an i686 to StrongARM (EBSA-285) cross compiler for both gcc and g++. I can successfully build the gcc cross compiler (using the components listed below) if I manually modify the top-level gcc Makefile by changing the, LANGUAGES="c c++" option to, LANGUAGES="c" ---------- Components: binutils-2.9.5.0.34-1.src.rpm gcc-core-2.95.2.tar.gz gcc-g++-2.95.2.tar.gz gcc-2.95.2-arm4.patch.gz kernel-2.2.14-5.0.src.rpm patch-2.2.14-rmk6.gz glibc-2.1.3.tar.gz glibc-crypt-2.1.tar.gz glibc-linuxthreads-2.1.3.tar.gz [Note: The ./configure step specifies 'LANGUAGES="c c++"' in the gcc Makefile whether the g++ sources are installed or not -- i.e., even when only the gcc-core sources are installed. --end note] [Note: When I do a gcc-only build, I'm able to build a linux 'zImage' kernel image using the gcc cross compiler. --end note] When I add the g++ sources to the mix and leave the LANGUAGES option set to "c c++" in the top-level Makefile, I get the following error messages at the (tail end of the) make process: <---start---> Running configure in multilib subdirs soft-float pwd: /usr/jdf/fornax/armtools/work/gcc-stage-1_/arm-ebsa285-linux-gnu/libio Running configure in multilib subdir soft-float pwd: /usr/jdf/fornax/armtools/work/gcc-stage-1_/arm-ebsa285-linux-gnu Appending /usr/src/redhat/BUILD/gcc-2.95.2/libio/config/linux.mt to target-mkfrag Appending /usr/src/redhat/BUILD/gcc-2.95.2/libio/config/mtsafe.mt to target-mkfrag Created "Makefile" in /usr/jdf/fornax/armtools/work/gcc-stage-1_/arm-ebsa285-linux-gnu/soft-float/ libio using "target-mkfrag" Adding multilib support to Makefile in /usr/src/redhat/BUILD/gcc-2.95.2/libio with_multisubdir=soft-float Configuring tests... Created "Makefile" in /usr/jdf/fornax/armtools/work/gcc-stage-1_/arm-ebsa285-linux-gnu/soft-float/ libio/tests Configuring dbz... Linked "rdbz.c" to "/usr/src/redhat/BUILD/gcc-2.95.2/libio/dbz/dbz.c". Linked "rdbzmain.c" to "/usr/src/redhat/BUILD/gcc-2.95.2/libio/dbz/dbzmain.c". Created "Makefile" in /usr/jdf/fornax/armtools/work/gcc-stage-1_/arm-ebsa285-linux-gnu/soft-float/ libio/dbz Configuring stdio... Created "Makefile" in /usr/jdf/fornax/armtools/work/gcc-stage-1_/arm-ebsa285-linux-gnu/soft-float/ libio/stdio Configuring testsuite... Created "Makefile" in /usr/jdf/fornax/armtools/work/gcc-stage-1_/arm-ebsa285-linux-gnu/soft-float/ libio/testsuite Configuring tests... Created "Makefile" in /usr/jdf/fornax/armtools/work/gcc-stage-1_/arm-ebsa285-linux-gnu/libio/tests Configuring dbz... Linked "rdbz.c" to "/usr/src/redhat/BUILD/gcc-2.95.2/libio/dbz/dbz.c". Linked "rdbzmain.c" to "/usr/src/redhat/BUILD/gcc-2.95.2/libio/dbz/dbzmain.c". Created "Makefile" in /usr/jdf/fornax/armtools/work/gcc-stage-1_/arm-ebsa285-linux-gnu/libio/dbz Configuring stdio... Created "Makefile" in /usr/jdf/fornax/armtools/work/gcc-stage-1_/arm-ebsa285-linux-gnu/libio/stdio Configuring testsuite... Created "Makefile" in /usr/jdf/fornax/armtools/work/gcc-stage-1_/arm-ebsa285-linux-gnu/libio/tests uite Configuring in arm-ebsa285-linux-gnu/libiberty creating cache ./config.cache checking host system type... arm-ebsa285-linux-gnu checking host system type... arm-ebsa285-linux-gnu checking build system type... i686-pc-linux-gnu checking for arm-ebsa285-linux-gnu-ar... arm-ebsa285-linux-gnu-ar checking for arm-ebsa285-linux-gnu-ranlib... arm-ebsa285-linux-gnu-ranlib checking for gcc... /usr/jdf/fornax/armtools/work/gcc-stage-1_/gcc/xgcc -B/usr/jdf/fornax/armtoo ls/work/gcc-stage-1_/gcc/ -B/usr/jdf/fornax/armtools/arm-ebsa285-linux-gnu/b in/ checking whether we are using GNU C... yes checking whether /usr/jdf/fornax/armtools/work/gcc-stage-1_/gcc/xgcc -B/usr/jdf/fornax/armtoo ls/work/gcc-stage-1_/gcc/ -B/usr/jdf/fornax/armtools/arm-ebsa285-linux-gnu/b in/ accepts -g... yes checking for POSIXized ISC... no checking for a BSD compatible install... /bin/sh /usr/src/redhat/BUILD/gcc-2.95.2/install-sh -c checking how to run the C preprocessor... /lib/cpp checking for sys/file.h... yes checking for sys/param.h... yes checking for stdlib.h... yes checking for string.h... yes checking for unistd.h... yes checking for strings.h... yes checking for sys/time.h... yes checking for sys/resource.h... yes checking for sys/wait.h that is POSIX.1 compatible... no checking whether the C compiler (/usr/jdf/fornax/armtools/work/gcc-stage-1_/gcc/xgcc -B/usr/jdf/fornax/armto ols/work/gcc-stage-1_/gcc/ -B/usr/jdf/fornax/armtools/arm-ebsa285-linux-gnu/ bin/ -g -O2 ) works... no configure: error: installation or configuration problem: C compiler cannot create executables. make[2]: Entering directory `/usr/jdf/fornax/armtools/work/gcc-stage-1_/arm-ebsa285-linux-gnu/libio' if [ x"no" = xyes ] && [ ! -d pic ]; then \ mkdir pic; \ else true; fi touch stamp-picdir test x"no" != xyes ||\ /usr/jdf/fornax/armtools/work/gcc-stage-1_/gcc/xgcc -B/usr/jdf/fornax/armtoo ls/work/gcc-stage-1_/gcc/ -B/usr/jdf/fornax/armtools/arm-ebsa285-linux-gnu/b in/ -c -g -O2 -I. -I/usr/src/redhat/BUILD/gcc-2.95.2/libio -D_IO_MTSAFE_IO /usr/src/redhat/BUILD/gcc-2.95.2/libio/iogetline.c -o pic/iogetline.o /usr/jdf/fornax/armtools/work/gcc-stage-1_/gcc/xgcc -B/usr/jdf/fornax/armtoo ls/work/gcc-stage-1_/gcc/ -B/usr/jdf/fornax/armtools/arm-ebsa285-linux-gnu/b in/ -c -g -O2 -I. -I/usr/src/redhat/BUILD/gcc-2.95.2/libio -D_IO_MTSAFE_IO /usr/src/redhat/BUILD/gcc-2.95.2/libio/iogetline.c In file included from /usr/src/redhat/BUILD/gcc-2.95.2/libio/iogetline.c:26: /usr/src/redhat/BUILD/gcc-2.95.2/libio/libioP.h:30: errno.h: No such file or directory In file included from /usr/src/redhat/BUILD/gcc-2.95.2/libio/iolibio.h:1, from /usr/src/redhat/BUILD/gcc-2.95.2/libio/libioP.h:47, from /usr/src/redhat/BUILD/gcc-2.95.2/libio/iogetline.c:26: /usr/src/redhat/BUILD/gcc-2.95.2/libio/libio.h:30: _G_config.h: No such file or directory /usr/src/redhat/BUILD/gcc-2.95.2/libio/iogetline.c:27: string.h: No such file or directory <---stop---> [Note: I've tried a number of variations on the 'target' name just to see what would happen. The code above shows the output when the target name was set to 'arm-ebsa285-linux-gnu', but target names of 'arm-linux' and 'arm-ebsa285-linux' produce the same set of error messages as shown above. --end note] Any ideas as to what's causing these errors ? Jim unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 10 02:30:34 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13BSP4-0008MK-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 10 Jul 2000 02:30:34 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 8B60A15E17; Mon, 10 Jul 2000 03:22:45 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Sun, 9 Jul 2000 21:09:12 -0400 Received: by vger.rutgers.edu id ; Sun, 9 Jul 2000 21:08:29 -0400 Received: from whistler.artisan.calpoly.edu ([129.65.2.41]:1098 "EHLO rubens.artisan.calpoly.edu") by vger.rutgers.edu with ESMTP id ; Sun, 9 Jul 2000 21:07:39 -0400 Received: from synthis (synthis.ee.calpoly.edu [129.65.26.204]) by rubens.artisan.calpoly.edu (8.8.6 (PHNE_17135)/8.8.6) with SMTP id SAA16227 for ; Sun, 9 Jul 2000 18:18:37 -0700 (PDT) Message-ID: <008c01bfea0c$3a57e850$cc1a4181@synthis> From: "Jim Fischer" To: "ARM Linux" Subject: glibc make problems (i686 -> StrongARM) Date: Sun, 9 Jul 2000 18:14:33 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Using the following components I am able to create an i686 to StrongARM (EBSA285) cross gcc compiler, and I can use that compiler to create a Linux 'zImage' kernel image: ---------- Components: binutils-2.9.5.0.34-1.src.rpm gcc-core-2.95.2.tar.gz gcc-g++-2.95.2.tar.gz gcc-2.95.2-arm4.patch.gz kernel-2.2.14-5.0.src.rpm patch-2.2.14-rmk6.gz glibc-2.1.3.tar.gz glibc-crypt-2.1.tar.gz glibc-linuxthreads-2.1.3.tar.gz After I create and install the binutils, the kernel sources, and the gcc cross-compiler, I install, patch, configure, and make the glibc sources. The glibc make process runs for about 15 minutes (generating about 10MB worth of log file entries in the process) before it dies with the following error messages: ---------- ... arm-linux-gcc -B/armtools/bin/ -shared -Wl,-O1 -o /armtools/work/glibc_/db2/libdb.so -Wl,-dynamic-linker=/armtools/arm-linux/l ib/ld-linux.so.2 -B/armtools/work/glibc_/csu/ -Wl,--version-script=/armtools /work/glibc_/libdb.map -Wl,-soname=libdb.so.3 -L/armtools/work/glibc_ -L/arm tools/work/glibc_/math -L/armtools/work/glibc_/elf -L/armtools/work/glibc_/n ss -L/armtools/work/glibc_/nis -L/armtools/work/glibc_/db2 -L/armtools/work/ glibc_/rt -L/armtools/work/glibc_/resolv -L/armtools/work/glibc_/linuxthread s -Wl,-rpath-link=/armtools/work/glibc_:/armtools/work/glibc_/math:/armtools /work/glibc_/elf:/armtools/work/glibc_/nss:/armtools/work/glibc_/nis:/armtoo ls/work/glibc_/db2:/armtools/work/glibc_/rt:/armtools/work/glibc_/resolv:/ar mtools/work/glibc_/linuxthreads -Wl,--whole-archive /armtools/work/glibc_/db2/libdb_pic.a /armtools/work/glibc_/elf/interp.os /armtools/work/glibc_/libc.so -Wl,--no-whole-archive rm -f /armtools/work/glibc_/db2/libdb.so.3.new /bin/sh ../scripts/rellns-sh /armtools/work/glibc_/db2/libdb.so /armtools/work/glibc_/db2/libdb.so.3.new mv -f /armtools/work/glibc_/db2/libdb.so.3.new /armtools/work/glibc_/db2/libdb.so.3 arm-linux-gcc -B/armtools/bin/ -nostdlib -nostartfiles -o /armtools/work/glibc_/db2/makedb -Wl,-dynamic-linker=/armtools/arm-linux/lib /ld-linux.so.2 /armtools/work/glibc_/csu/crt1.o /armtools/work/glibc_/csu/crti.o `arm-linux-gcc -B/armtools/bin/ --print-file-name=crtbegin.o` /armtools/work/glibc_/db2/makedb.o /armtools/work/glibc_/db2/libdb.so.3 -Wl,-rpath-link=/armtools/work/glibc_:/ armtools/work/glibc_/math:/armtools/work/glibc_/elf:/armtools/work/glibc_/ns s:/armtools/work/glibc_/nis:/armtools/work/glibc_/db2:/armtools/work/glibc_/ rt:/armtools/work/glibc_/resolv:/armtools/work/glibc_/linuxthreads /armtools/work/glibc_/libc.so.6 /armtools/work/glibc_/libc_nonshared.a -lgcc `arm-linux-gcc -B/armtools/bin/ --print-file-name=crtend.o` /armtools/work/glibc_/csu/crtn.o /armtools/work/glibc_/libc.so.6: undefined reference to `__dup' /armtools/work/glibc_/libc.so.6: undefined reference to `__getpid' /armtools/work/glibc_/libc.so.6: undefined reference to `__setsid' /armtools/work/glibc_/libc.so.6: undefined reference to `__select' /armtools/work/glibc_/libc.so.6: undefined reference to `utime' /armtools/work/glibc_/db2/libdb.so.3: undefined reference to `munmap' /armtools/work/glibc_/libc.so.6: undefined reference to `__wait4' /armtools/work/glibc_/libc.so.6: undefined reference to `__libc_fcntl' /armtools/work/glibc_/libc.so.6: undefined reference to `__ftruncate' /armtools/work/glibc_/libc.so.6: undefined reference to `__write' /armtools/work/glibc_/libc.so.6: undefined reference to `__mprotect' /armtools/work/glibc_/db2/libdb.so.3: undefined reference to `getpid' /armtools/work/glibc_/libc.so.6: undefined reference to `__dup2' /armtools/work/glibc_/libc.so.6: undefined reference to `truncate' /armtools/work/glibc_/libc.so.6: undefined reference to `__read' /armtools/work/glibc_/libc.so.6: undefined reference to `setitimer' /armtools/work/glibc_/libc.so.6: undefined reference to `__unlink' /armtools/work/glibc_/libc.so.6: undefined reference to `readlink' /armtools/work/glibc_/db2/libdb.so.3: undefined reference to `getuid' /armtools/work/glibc_/libc.so.6: undefined reference to `__open' /armtools/work/glibc_/libc.so.6: undefined reference to `__getrusage' /armtools/work/glibc_/libc.so.6: undefined reference to `__adjtimex' /armtools/work/glibc_/db2/libdb.so.3: undefined reference to `select' /armtools/work/glibc_/libc.so.6: undefined reference to `__getgid' /armtools/work/glibc_/libc.so.6: undefined reference to `__libc_read' /armtools/work/glibc_/db2/libdb.so.3: undefined reference to `lseek' /armtools/work/glibc_/libc.so.6: undefined reference to `__getpgid' /armtools/work/glibc_/libc.so.6: undefined reference to `alarm' /armtools/work/glibc_/libc.so.6: undefined reference to `__kill' /armtools/work/glibc_/libc.so.6: undefined reference to `uname' /armtools/work/glibc_/libc.so.6: undefined reference to `__personality' /armtools/work/glibc_/libc.so.6: undefined reference to `__setitimer' /armtools/work/glibc_/libc.so.6: undefined reference to `__chmod' /armtools/work/glibc_/libc.so.6: undefined reference to `setrlimit' /armtools/work/glibc_/db2/libdb.so.3: undefined reference to `write' /armtools/work/glibc_/libc.so.6: undefined reference to `__setpgid' /armtools/work/glibc_/libc.so.6: undefined reference to `__gettimeofday' /armtools/work/glibc_/libc.so.6: undefined reference to `__sigaltstack' /armtools/work/glibc_/libc.so.6: undefined reference to `__statfs' /armtools/work/glibc_/libc.so.6: undefined reference to `__getrlimit' /armtools/work/glibc_/libc.so.6: undefined reference to `__nanosleep' /armtools/work/glibc_/libc.so.6: undefined reference to `__chdir' /armtools/work/glibc_/db2/libdb.so.3: undefined reference to `read' /armtools/work/glibc_/libc.so.6: undefined reference to `__readlink' /armtools/work/glibc_/libc.so.6: undefined reference to `__ioctl' /armtools/work/glibc_/db2/libdb.so.3: undefined reference to `unlink' /armtools/work/glibc_/libc.so.6: undefined reference to `__getegid' /armtools/work/glibc_/libc.so.6: undefined reference to `fork' /armtools/work/glibc_/libc.so.6: undefined reference to `__pipe' /armtools/work/glibc_/libc.so.6: undefined reference to `__libc_open' /armtools/work/glibc_/libc.so.6: undefined reference to `getsid' /armtools/work/glibc_/libc.so.6: undefined reference to `__chown' /armtools/work/glibc_/db2/libdb.so.3: undefined reference to `time' /armtools/work/glibc_/libc.so.6: undefined reference to `__lseek' /armtools/work/glibc_/libc.so.6: undefined reference to `__fchdir' /armtools/work/glibc_/db2/libdb.so.3: undefined reference to `fsync' /armtools/work/glibc_/libc.so.6: undefined reference to `__libc_lseek' /armtools/work/glibc_/libc.so.6: undefined reference to `__rmdir' /armtools/work/glibc_/libc.so.6: undefined reference to `__fstatfs' /armtools/work/glibc_/libc.so.6: undefined reference to `__close' /armtools/work/glibc_/libc.so.6: undefined reference to `__getuid' /armtools/work/glibc_/libc.so.6: undefined reference to `__munmap' /armtools/work/glibc_/libc.so.6: undefined reference to `__times' /armtools/work/glibc_/db2/libdb.so.3: undefined reference to `open' /armtools/work/glibc_/libc.so.6: undefined reference to `__libc_write' /armtools/work/glibc_/libc.so.6: undefined reference to `__fcntl' /armtools/work/glibc_/libc.so.6: undefined reference to `__fork' /armtools/work/glibc_/libc.so.6: undefined reference to `__access' /armtools/work/glibc_/db2/libdb.so.3: undefined reference to `fcntl' /armtools/work/glibc_/db2/libdb.so.3: undefined reference to `close' /armtools/work/glibc_/libc.so.6: undefined reference to `__geteuid' collect2: ld returned 1 exit status arm-linux-gcc: file path prefix `/armtools/bin/' never used make[2]: *** [/armtools/work/glibc_/db2/makedb] Error 1 make[2]: Leaving directory `/usr/src/redhat/BUILD/glibc-2.1.3/db2' make[1]: *** [db2/others] Error 2 make[1]: Leaving directory `/usr/src/redhat/BUILD/glibc-2.1.3' make: *** [all] Error 2 ---------- Apparently, the build process is not generating object code for the kernel interface, and I haven't been able to figure out what's causing this. Any ideas ? Jim unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 10 02:33:36 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13BSS0-0008ND-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 10 Jul 2000 02:33:36 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id EEEF015E20; Mon, 10 Jul 2000 03:27:48 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Sun, 9 Jul 2000 21:15:08 -0400 Received: by vger.rutgers.edu id ; Sun, 9 Jul 2000 21:13:46 -0400 Received: from nanum.kaeri.re.kr ([147.43.15.12]:4821 "EHLO nanum.kaeri.re.kr") by vger.rutgers.edu with ESMTP id ; Sun, 9 Jul 2000 21:13:22 -0400 Received: from mail.robotics.co.kr ([147.43.73.178]) by nanum.kaeri.re.kr (8.9.1a-H1/8.9.3) with ESMTP id KAA20142 for ; Mon, 10 Jul 2000 10:33:18 +0900 (kst) Message-ID: <396925A4.DFDA3865@mail.robotics.co.kr> Date: Mon, 10 Jul 2000 10:23:48 +0900 From: Sun-Gi Hong Organization: Hanwool Robotics Corp. X-Mailer: Mozilla 4.61 [ko] (X11; I; Linux 2.2.12-20kr i686) X-Accept-Language: ko MIME-Version: 1.0 To: linux-arm@vger.rutgers.edu Subject: [Q] sound device driver Content-Type: text/plain; charset=EUC-KR Content-Transfer-Encoding: 8bit Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Greetings, I have some questions about the current stage for UDA1341 sound device driver for Assabet BD as follows. 1. Does the developed device driver support the sound recording? 2. If yes, are there some programs for testing it and where are they? Thank you in advance. unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 10 02:39:13 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13BSXR-0008Oe-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 10 Jul 2000 02:39:13 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id D19B615DE4; Mon, 10 Jul 2000 03:39:12 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Sun, 9 Jul 2000 21:26:54 -0400 Received: by vger.rutgers.edu id ; Sun, 9 Jul 2000 21:26:46 -0400 Received: from rodin.krdl.org.sg ([192.122.139.27]:2187 "EHLO krdl.org.sg") by vger.rutgers.edu with ESMTP id ; Sun, 9 Jul 2000 21:26:38 -0400 Received: from mailhost.krdl.org.sg (mailhost [192.122.134.30]) by krdl.org.sg (8.9.3/8.9.3) with ESMTP id JAA05636 for ; Mon, 10 Jul 2000 09:46:12 +0800 Received: from krdl.org.sg (QUNYING.krdl.org.sg [192.168.136.36]) by mailhost.krdl.org.sg (8.9.3/8.9.3) with ESMTP id JAA14312 for ; Mon, 10 Jul 2000 09:36:31 +0800 (SGT) Message-ID: <396928ED.7FF942B9@krdl.org.sg> Date: Mon, 10 Jul 2000 09:37:49 +0800 From: zhu qun ying Organization: KRDL X-Mailer: Mozilla 4.73 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: linux-arm Subject: anyone compiled newlib 1.8.2? Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Hi, I am trying to build a cross compiler with newlib 1.8.2. I have some problems to configure the linker. I have successfully build the cross compiler with gcc version 2.96 20000702, binutils 2.10, and glibc 2.1.3. But for newlib, I have problems. The linker is trying to link with crt1.o, crti.o, crtn.o and those are for glibc only. For newlib, I have only crt0.o. So the linker complains while linking a porgram. I don't know how to configure the linker to link with newlib? Anyone has an idea to solve this? -- (~._.~) Öì Ⱥ Ó¢ (Qun Ying) (65) 874-6743 ( O ) Kent Ridge Digital Labs (KRDL) ()~*~() 21 Heng Mui Keng Terrace, Singapore 119613 (_)-(_) qyzhu@krdl.org.sg * zhuqy@hotmail.com unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 10 03:11:09 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13BT2L-0000AD-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 10 Jul 2000 03:11:09 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 5C3D415D91; Mon, 10 Jul 2000 04:11:08 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Sun, 9 Jul 2000 21:54:43 -0400 Received: by vger.rutgers.edu id ; Sun, 9 Jul 2000 21:54:31 -0400 Received: from modemcable248.137-200-24.mtl.mc.videotron.net ([24.200.137.248]:61767 "EHLO xanadu.gn.com") by vger.rutgers.edu with ESMTP id ; Sun, 9 Jul 2000 21:53:11 -0400 Received: from localhost (nico@localhost) by xanadu.gn.com (8.9.3/8.9.3) with ESMTP id WAA00412; Sun, 9 Jul 2000 22:03:34 -0400 X-Authentication-Warning: xanadu.gn.com: nico owned process doing -bs Date: Sun, 9 Jul 2000 22:03:34 -0400 (EDT) From: Nicolas Pitre X-Sender: nico@xanadu.gn.com To: Sun-Gi Hong Cc: linux-arm@vger.rutgers.edu Subject: Re: [Q] sound device driver In-Reply-To: <396925A4.DFDA3865@mail.robotics.co.kr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu On Mon, 10 Jul 2000, Sun-Gi Hong wrote: > Greetings, > > I have some questions about the current stage for UDA1341 sound device > driver for Assabet BD as follows. > > 1. Does the developed device driver support the sound recording? Yes. > 2. If yes, are there some programs for testing it and where are they? The simpliest is: dd if=/dev/dsp of=/dev/dsp bs=8192 and listen to the result with headphones for best result. Nicolas unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 10 03:13:33 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13BT4f-0000B7-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 10 Jul 2000 03:13:33 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id A985215E12; Mon, 10 Jul 2000 04:13:34 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Sun, 9 Jul 2000 22:01:44 -0400 Received: by vger.rutgers.edu id ; Sun, 9 Jul 2000 22:01:36 -0400 Received: from modemcable248.137-200-24.mtl.mc.videotron.net ([24.200.137.248]:61789 "EHLO xanadu.gn.com") by vger.rutgers.edu with ESMTP id ; Sun, 9 Jul 2000 22:01:19 -0400 Received: from localhost (nico@localhost) by xanadu.gn.com (8.9.3/8.9.3) with ESMTP id WAA00421; Sun, 9 Jul 2000 22:11:47 -0400 X-Authentication-Warning: xanadu.gn.com: nico owned process doing -bs Date: Sun, 9 Jul 2000 22:11:47 -0400 (EDT) From: Nicolas Pitre X-Sender: nico@xanadu.gn.com To: Vasant Ramasubramanian Cc: sa1100-linux@pa.dec.com, linux-arm@vger.rutgers.edu Subject: Re: Brutus/SA1100 Issues In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu On Sun, 9 Jul 2000, Vasant Ramasubramanian wrote: > Hello all; > > I am having difficulty getting my Brutus to work after it was sent in for > repair and I'm not sure what the problem is yet... > > When I use Nico's brutustest kernel+ramdisk+angel on the debugging console > I get some interesting startup messages. > > I get: > > ... > Calibrating delay loop 194.15 BogoMIPS > ... > Starting kswapd 1.5 > IRQ LOCK: IRQ 12 is locking the system, disabled > Console: Switching to colour framebuffer device 40x30 IRQ 12 is attached to the SA1100 integrated LCD controller. Either your CPU is damaged or something on the board is wrong. Try replacing your CPU on your Brutus board and ensure the socket is perfectly clean while you're at it. Nicolas unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 10 04:38:19 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13BUOh-0000kL-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 10 Jul 2000 04:38:19 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id C659615DD4; Mon, 10 Jul 2000 05:38:17 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Sun, 9 Jul 2000 23:26:23 -0400 Received: by vger.rutgers.edu id ; Sun, 9 Jul 2000 23:26:14 -0400 Received: from [63.195.182.101] ([63.195.182.101]:4641 "EHLO barbados.bluemug.com") by vger.rutgers.edu with ESMTP id ; Sun, 9 Jul 2000 23:25:59 -0400 Received: from fiji.bluemug.com [192.168.50.32] (mail) by barbados.bluemug.com with esmtp (Exim 2.05 #1 (Debian)) id 13BUNb-0003Ve-00; Sun, 9 Jul 2000 20:37:11 -0700 Received: from miket by fiji.bluemug.com with local (Exim 2.05 #1 (Debian)) id 13BUNa-0005pv-00; Sun, 9 Jul 2000 20:37:10 -0700 Date: Sun, 9 Jul 2000 20:37:10 -0700 From: Mike Touloumtzis To: David Rusling Cc: linux-arm Subject: Re: Building cross libraries Message-ID: <20000709203710.A21694@fiji.bluemug.com> References: <3965FBD3.65402A14@arm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <3965FBD3.65402A14@arm.com>; from David Rusling on Fri, Jul 07, 2000 at 04:48:35PM +0100 Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu On Fri, Jul 07, 2000 at 04:48:35PM +0100, David Rusling wrote: > All, > > I've been 'playing' with cross-tools. Using the various helpful help > files (Phil Blundell and Chris Rutter) I can now build binutils-2.9.5 > and gcc-2.95.1 every which way. However, I cannot build glibc-2.1 > or newlib-1.8.2. > > Configuring newlib fail's 'cos it cannot compile/link a test image. > (I'm assuming arm-linux as the build variant). It fails with unsupported > emulations. I'm guessing that the kernel builds 'cos it uses steering files > for this stuff. > > Following Chris's instructions, glibc-2.1 fails because gcc 2.95.1 > is not the correct version. I hacked the configure file but it fails > as it builds it later on. > > So, help! Dave > Here's a notebook I wrote up as I went through the stuff you're doing. It's obviously directed at me (plus other people at my site who want to do this), but it has the advantage of being pretty recent. Haven't built newlib for ARM, so I can't help there. I built it for M32R a while ago, but don't remember what was involved. miket Building binutils ----------------- -- Grab safe binutils source. The current Debian version, 2.9.5.0.31, is claimed to be buggy on one of the ARM mailing lists. 2.9.5.0.14 is reported to be safe on Chris Rutter's ARM cross-compiler page, so I'm going to give that a try. According to Phil Blundell's page and FTP site, the 2.9.5.* series binutils don't require ARM patches (unlike 2.9.1.*). Here's the official site for binutils: ftp://ftp.varesearch.com/pub/support/hjl/binutils/ Actually, scratch the above version number stuff. The site contains 2.9.5.0.37, and I'm going to try that, because going back to a much older version looks like it will involve a heinous amount of reverse patching. If .37 doesn't work, I guess I'll try .14. -- Also grab current Debian binutils source, so that I can figure out how to package the cross-compiler one I'm building. Looks like the debian stuff is really complicated here (this source package produces four different .debs). I guess it's time I read the Debian packaging manual... These steps will install the ARM binutils under /usr/local/. The binaries will be named arm-linux-*. Binutils is the easy part of cross-gcc compilation. 1) Unpack tarball. 2) Make build dir 'binutils-build' parallel to source dir. 3) cd to build dir. 3) Run ../configure --help to see options. 4) Run ../configure --target=arm-linux 5) Typical make + make install. Building GCC ------------ Following instructions on: http://inkvine.fluff.org/~chris/arm-tools.html GCC requires the kernel header files. I'm going to try against a patched 2.4.0-test1-ac19. Steps to getting this kernel in the right state for building gcc: 1) Get 2.4.0-test1-ac19 source (from kernel.org). Have to download 2.4.0-test1 and apply the ac19 patch to it. Get the .sign files and check the signatures, too! This kernel can be found at ftp.us.kernel.org in: /pub/linux/kernel/v2.4/linux-2.4.0-test1.tar.gz /pub/linux/kernel/v2.4/linux-2.4.0-test1.tar.gz.sign and the -ac19 patch is in: /pub/linux/kerner/people/alan/2.4.0test/patch-2.4.0test1-ac19.bz2 (and corresponding .sign). To unpack and apply the patch (somewhere in your home directory): $ tar zxvf linux-2.4.0-test1.tar.gz $ mv linux linux-2.4.0-test1 $ cd linux-2.4.0-test1 $ bzcat ../patch-2.4.0test1-ac19.bz2 | patch -p1 -s -E 2) Get latest RMK (Russell M. King, linux-arm maintainer) patch from ftp://ftp.arm.linux.org.uk/pub/armlinux/source/kernel-patches/v2.4/ (it's against -ac19, that's why I chose that kernel version) and once again patch the kernel: $ zcat ../patch-2.4.0-test1-ac19-rmk1.gz | patch -p1 -s -E 3) In the top-level kernel Makefile, replace the line: ARCH := $(shell uname ... bunch of stuff ...) with ARCH := arm 4) Configure the kernel with 'make menuconfig'. Save the default configuration. I'm hoping this works OK, as we don't need to really build the kernel, we just need to get its headers into a state acceptable for building GCC. The closest thing in the Makefiles to the 7211 is probably the 7500 (although ARM710A, not 710TDMI), but that port is not fully merged and the option is commented out. 5) Run 'make dep' to build the dependency tree. 6) Create links in the arm-linux target include directory: $ cd /usr/local/arm-linux $ mkdir include; cd include $ ln -s your-linux-kernel-directory/include/asm-arm asm $ ln -s your-linux-kernel-directory/include/linux linux 7) Download gcc 2.95.2, plus Phil Blundell's add-on patch at: ftp://ftp.netwinder.org/users/p/philb/gcc-2.95.2-diff-991022.gz and the fold-const.c patch from Chris Rutter's page http://inkvine.fluff.org/~chris/arm-tools.html Read Chris's page top to bottom, as it has a bunch of information on what should be done next. 8) Commentary on Chris Rutter's page -- Phil Blundell's 2.95.2 gcc patch doesn't apply cleanly, but I looked at the patch, and the changes look reasonable (right direction, likely bug fixes, etc). The top-level stuff (ChangeLog, configure, configure.in) will get rejected; the other stuff patches cleanly, although I had to supply a path to each file. -- The fold-const.c patch looks like it's still needed (it hasn't been applied in 2.95.2). -- The instructions about changing #if 0 to #if 1 in gcc/config/arm/linux-elf.h look to be obsolete; there is no #if 0 in that file. -- I used the -Dinhibit_libc hack described in the page. 9) Configure and build, after the necessary patching. Command lines (from directory _above_ gcc-2.95.2): $ mkdir gcc-build $ cd gcc-build $ ../gcc-2.95.2/configure --target=arm-linux --disable-threads $ make LANGUAGES="c" cross My build failed with an error message in libio, but I looked at the binaries and found quite a lot of gcc stuff, so I did an impatient 'make install' without debugging the problem (looks to be lack of a target libc) and was able to compile a standalone boot loader with no libc dependencies. Glibc ----- 1) Download glibc-2.1.3 and the crypt and linuxthreads add-ons. $ mkdir glibc-build $ cd glibc-build $ export CC=arm-linux-gcc $ ../glibc-2.1.3/configure arm-linux --build=i586-linux \ --prefix=/usr/local/arm-linux/ --enable-add-ons $ make $ make install Gcc Revisited ------------- You can now go back and compile the full-on gcc. First, remove the -Dinhibit_libc hack from the sources. Delete your previous build directory, and: $ mkdir gcc-build $ cd gcc-build $ ../gcc-2.95.2/configure --target=arm-linux $ make $ make install Don't forget to unset CC if you set it above. Stripping Binaries ------------------ You now have an unholy amount of stuff in /usr/local. I went through and stripped some shared libraries. Make sure you use 'strip' for Intel tools and 'arm-linux-strip' for ARM binaries. Hopefully, I'll automate this process soon; if you don't know what you're doing, I recommend against this step. unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 10 04:45:22 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13BUVW-0000nb-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 10 Jul 2000 04:45:22 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 8AED515DEE; Mon, 10 Jul 2000 05:45:25 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Sun, 9 Jul 2000 23:33:30 -0400 Received: by vger.rutgers.edu id ; Sun, 9 Jul 2000 23:33:21 -0400 Received: from [63.195.182.101] ([63.195.182.101]:4652 "EHLO barbados.bluemug.com") by vger.rutgers.edu with ESMTP id ; Sun, 9 Jul 2000 23:33:16 -0400 Received: from fiji.bluemug.com [192.168.50.32] (mail) by barbados.bluemug.com with esmtp (Exim 2.05 #1 (Debian)) id 13BUUk-0003Vu-00; Sun, 9 Jul 2000 20:44:34 -0700 Received: from miket by fiji.bluemug.com with local (Exim 2.05 #1 (Debian)) id 13BUUk-0005qq-00; Sun, 9 Jul 2000 20:44:34 -0700 Date: Sun, 9 Jul 2000 20:44:34 -0700 From: Mike Touloumtzis To: Jim Fischer Cc: ARM Linux Subject: Re: i686->StrongARM gcc/g++ cross compile problems Message-ID: <20000709204434.C21694@fiji.bluemug.com> References: <008401bfea07$28a90760$cc1a4181@synthis> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <008401bfea07$28a90760$cc1a4181@synthis>; from Jim Fischer on Sun, Jul 09, 2000 at 05:38:16PM -0700 Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu On Sun, Jul 09, 2000 at 05:38:16PM -0700, Jim Fischer wrote: > > I'm in the process of creating an i686 to StrongARM (EBSA-285) cross > compiler for both gcc and g++. .... > > [Note: I've tried a number of variations on the 'target' name just > to see what would happen. The code above shows the output when the > target name was set to 'arm-ebsa285-linux-gnu', but target names of > 'arm-linux' and 'arm-ebsa285-linux' produce the same set of error > messages as shown above. --end note] > > Any ideas as to what's causing these errors ? > Jim, See the notes I just (a few minutes ago) posted to the list. To build languages other than C, first build C (you might get errors in libio; 'make install' anyway), then build and install glibc, then go back and do a full build of gcc. miket unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 10 13:48:56 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13BczY-00006C-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 10 Jul 2000 13:48:56 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 438D1162CB; Mon, 10 Jul 2000 14:46:29 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Mon, 10 Jul 2000 08:33:59 -0400 Received: by vger.rutgers.edu id ; Mon, 10 Jul 2000 08:33:53 -0400 Received: from zmamail03.zma.compaq.com ([161.114.64.103]:4521 "HELO zmamail03.zma.compaq.com") by vger.rutgers.edu with SMTP id ; Mon, 10 Jul 2000 08:33:22 -0400 Received: by zmamail03.zma.compaq.com (Postfix, from userid 12345) id 038B15EE3; Mon, 10 Jul 2000 08:44:40 -0400 (EDT) Received: from oils.ozy.dec.com (oils.ozy.dec.com [16.153.192.1]) by zmamail03.zma.compaq.com (Postfix) with ESMTP id 6EB955D06; Mon, 10 Jul 2000 08:44:36 -0400 (EDT) Received: from ozy.dec.com by oils.ozy.dec.com (8.8.8/1.1.10.5/12Oct99-0148PM) id WAA0000012346; Mon, 10 Jul 2000 22:44:31 +1000 (EST) Message-ID: <3969C50A.9E8C4BB6@ozy.dec.com> Date: Mon, 10 Jul 2000 22:43:55 +1000 From: Charlie Flynn X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: linux-arm@vger.rutgers.edu, handhelds@handhelds.org Subject: Re: Touch Screen Driver Generic Interface for all Linux SA11x0 platforms. References: <3962EAD8.E4DE217B@ozy.dec.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Hi, I attach my first cut of a generic touch screen driver specification as promised from my earlier email. This specification is based around my experience with the Compaq iPAQ H3600 touch screen driver, however I have tried to make it as generic as possible for all Linux platforms. If nothing else I hope it will at least start the ball rolling in the quest to gain consensus on what a generic touch screen driver will eventually look like. I will also put this spec in html format on the www.handhelds.org web site. Since there has also been some interest in the handhelds@handhelds.org mailing list I will post it in both lists for now with a view to maybe moving the discussion to one (which one?) of the lists. Regards --Charlie +++++++++++++++++++++++++++ MAJOR NUMBER -------------------- (TBD) A generic Touch Screen major number to be registered according to the procedure documented in../linux/Documentation/devices.txt. A major number 10 seems the most likely candidate. DEVICE NODES and MINOR NUMBERS ---------------------------------------------- /dev/ts - This is the device used to read calibrated touch screen events A generic Touch Screen device name (/dev/ts) and minor number (TBD) to be registered according to the procedure documented in ../linux/Documentation/devices.txt. TOUCH SCREEN EVENT STRUCTURE (TS_EVENT) ----------------------------------------------------------- This is the structure contains the X and Y pixel coordinates of a single touch screen event. It is passed from the driver to the user by the read() function. typedef struct { short pressure; /* used to determine if the touch screen pen is UP or DOWN (Note 1) */ short x; /* If pen is DOWN then this is the pixel X coordinate */ short y; /* If pen is DOWN then this is the pixel Y coordinate */ /* any more ? */ } TS_EVENT; USER LEVEL FILE OPERATIONS -------------------------------------- In addition to open(), close() and ioctl() functions, blocking and non-blocking reads and asynchronous notification (SIGIO) should be supported at the user level. The select/poll mechanism will be used for non-blocking reads. See the EXAMPLES section for pointers to example code on the above functions. KERNEL LEVEL FILE OPERATIONS ------------------------------------------ The following file operations pertain to device /dev/ts. _read() Blocking reads will block until a complete TS_EVENT structure (see below) can be returned. _fasync() Will send a SIGIO to user when there is an event to report. An event is defined as reception of a complete TS_EVENT structure. _poll() If there are 1 or more TS_EVENT structures to be read from the driver, then this function will return the (POLLIN | POLLRDNORM) flags otherwise a zero will be returned. _ioctl() The list of ioctls will depend on the hardware used to implement the touch screen (example UCB1200). Initialisation ioctls will be called by the driver’s init_module() or equivalent. The calibration application (if adopted in user space) will have it’s own ioctls (see CALIBRATION section). The ioctl command numbers should be ‘mangled’ using the _IO,_IOW,_IOR,_IOWR macros as defined in A ‘magic number’ of ‘?’ should be used (see CALIBRATION section) TOUCH SCREEN EXAMPLE CODE ------------------------------------------ The following example code can be found in the ../apps/h3600_test directory in the handhelds.org CVS tree. ts_poll.c - example of a non-blocking read using the poll/select mechanism. ts_read.c - example of a blocking read. fasynctst.c - example of how asynchronous notifications are handled in user space. The driver which implements most of this specification is called h3650_ts.c and can be found in the ../drivers/char directory in the handhelds.org CVS tree. CALIBRATION ------------------ (This section assumes the calibration mechanism will be an application) The (H3600) calibration parameters are calculated by a separate calibration application. It uses the Itsy calibration paradigm. The touch screen sensor is assumed linear, conforming to the equations of a straight line: Xcal = mxXraw + Cx Ycal = myYraw + Cy Calibration information is held in the TS_CAL structure and is passed to and from the driver using the TS_GET_CALIBRATE and TS_SET_CALIBRATE ioctls. #define TS_SET_CALIBRATE _IOW(IOC_MAGIC,2,TS_CAL); #define TS_GET_CALIBRATE _IOW(IOC_MAGIC,3,TS_CAL); The TS_CAL structure is used to convert RAW touch screen coordinates (Xraw and Yraw) to calibrated touch screen coordinates (Xcal and Ycal). typedef struct { int xscale; int xtrans; int yscale; int ytrans; int xyswap; } TS_CAL; The TS_SET_RAW_ON/OFF ioctl pair will switch between raw and calibrated data. The calibration application will instruct the driver to return only RAW events using the TS_SET_RAW_ON ioctl and when calibrated the calibration application will switch the driver back to returning calibrated events using the TS_SET_RAW_OFF (Note 2) #define TS_SET_RAW_ON _IO(IOC_MAGIC,0); #define TS_SET_RAW_OFF _IO(IOC_MAGIC,1); TOUCH SCREEN CALIBRATION APPLICATION EXAMPLE CODE ----------------------------------------------------------------------------- The H3600 calibration application can be found in ../apps/ts_calibrate.c in the handhelds.org CVS tree. This code is extensively commented and will explain how the Itsy calibration application works. Note is uses a device called /dev/h3600_tsraw to get raw data. This device may be superceded by the TS_SET_RAW_ON/OFF ioctls. Notes 1. Some systems return pressure as a value between 0 and xxxx which is used to determine the pen status (UP or DOWN). The Compaq iPAQ H3600 just returns pressure=0 (UP) or pressure=1 (DOWN). If UP then X and Y coordinates are set to –1. Should this member variable be called something else? 2. The Compaq H3600 driver does not use this mechanism at present. +++++++++++++++++++++++++++ Charlie Flynn wrote: > Hello, > > My name is Charlie Flynn and I have just completed V1.0 of a touch > screen driver for the Compaq iPAQ H3600 running Linux 2.4.0-test1. > > I was thinking it would be a good idea if we had a generic interface to > the touch screen drivers of all Linux SA11x0 platforms. > > This would allow clients ( such as the X windows device dependent layer > ) to work, without modification, with all Linux SA11x0 touch screen > drivers. > > I know it's a bit late to ask this ;-) but is there already a document > describing a generic TSD interface for these platforms? > > Assuming there isn't such a document and also assuming people think it's > worth pursuing I can start the ball rolling by posting a draft spec to > the linux-arm-kernel mailing list which I assume would be the most > appropriate place to discuss this issue. > > Regards > --Charlie > > unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu > ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ > ++ kernel-related discussions. ++ unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 10 13:56:47 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13Bd79-0000Ce-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 10 Jul 2000 13:56:47 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id B2012162CB; Mon, 10 Jul 2000 14:50:27 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Mon, 10 Jul 2000 08:37:22 -0400 Received: by vger.rutgers.edu id ; Mon, 10 Jul 2000 08:35:51 -0400 Received: from [194.201.77.34] ([194.201.77.34]:61584 "HELO fw-maid.maidenhead.arm.com") by vger.rutgers.edu with SMTP id ; Mon, 10 Jul 2000 08:35:03 -0400 Received: by fw-maid.maidenhead.arm.com; id NAA17491; Mon, 10 Jul 2000 13:43:44 +0100 Received: from unknown(192.168.2.10) by fw-maid.maidenhead.arm.com via smap (V5.0) id xma017486; Mon, 10 Jul 00 13:43:33 +0100 Received: from arm.com (dhcp2 [192.168.2.232]) by mhsun1.maidenhead.arm.com (8.9.3/8.9.3) with ESMTP id NAA08364; Mon, 10 Jul 2000 13:46:14 +0100 (BST) Message-ID: <3969D105.57A2AB72@arm.com> Date: Mon, 10 Jul 2000 14:35:01 +0100 From: David Rusling X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Mike Touloumtzis Cc: linux-arm Subject: Re: Building cross libraries References: <3965FBD3.65402A14@arm.com> <20000709203710.A21694@fiji.bluemug.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Mike, thank you very much. I think that what I was doing was not building the correct version of glibc, I had glibc-2.1, not 2.1.3. After a bit of fiddling I can now build static applications for my ARM Linux box. This is with gcc 2.95.2 but I think that gcc 2.95.1 would also work. I build all my stuff for /usr/local/gnu so I ended up having to create a link from /usr/local/gnu/lib to /usr/local/gnu/arm-linux/lib (I also have arm-elf for the eCOS work that I've been doing). All I have to do now is to figure out how to 'install' the shared libraries onto my pocket Linux system... Dave ---------------------------------------------------------------------- David A Rusling Consulting Engineer ARM Limited Liberty House, Moorbridge Road, Maidenhead, SL6 8LT Tel: UK-(0)1628-427754 Fax: UK-(0)1628-780551 e-mail: david.rusling@arm.com ---------------------------------------------------------------------- unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 10 14:06:44 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13BdGm-0000Q8-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 10 Jul 2000 14:06:44 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 4FEF3162E4; Mon, 10 Jul 2000 15:06:48 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Mon, 10 Jul 2000 08:54:49 -0400 Received: by vger.rutgers.edu id ; Mon, 10 Jul 2000 08:54:30 -0400 Received: from [208.242.241.39] ([208.242.241.39]:2651 "EHLO cvsftp.cotw.com") by vger.rutgers.edu with ESMTP id ; Mon, 10 Jul 2000 08:54:15 -0400 Received: from cotw.com (laptop1.ptec.com [192.168.10.10]) by cvsftp.cotw.com (8.9.3/8.9.3) with ESMTP id IAA18934; Mon, 10 Jul 2000 08:05:52 -0500 Message-ID: <3969C9DD.7ECE2AF1@cotw.com> Date: Mon, 10 Jul 2000 08:04:29 -0500 From: Steve Hill X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.3.47 i686) X-Accept-Language: en MIME-Version: 1.0 To: David Rusling Cc: Mike Touloumtzis , linux-arm Subject: Re: Building cross libraries References: <3965FBD3.65402A14@arm.com> <20000709203710.A21694@fiji.bluemug.com> <3969D105.57A2AB72@arm.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu David Rusling wrote: > > Mike, > > thank you very much. I think that what I was doing was not building > the correct version of glibc, I had glibc-2.1, not 2.1.3. After a bit of > fiddling I can now build static applications for my ARM Linux box. > This is with gcc 2.95.2 but I think that gcc 2.95.1 would also work. > > I build all my stuff for /usr/local/gnu so I ended up having to > create a link from /usr/local/gnu/lib to /usr/local/gnu/arm-linux/lib > (I also have arm-elf for the eCOS work that I've been doing). > > All I have to do now is to figure out how to 'install' the shared > libraries onto my pocket Linux system... > Well, now that you have a complete working toolchain, you can start building all the components for your disk image for your pocket Linux system. A good place to start would be to get ARM packages from the Debian site. If you want to build 'glibc' from scratch to put on your own disk image, here is one way of doing it. 1) Create a ramdisk using '/dev/ramX' or use the loopback device and format an 'ext2' filesystem on it. 2) Un-pack your 'glibc' sources again. 3) Put your cross-compilation environment in your path and run the configure script for 'glibc' only this time using '--prefix=/usr'. This will configure 'glibc' in a special way that will install the libraries in '/lib' like it is on a "normal" Linux system. (By telling it the prefix is /usr AND that the target is a Linux variant, glibc figures out that you are creating it to be the main C run time library on the system) 4) Go ahead and do a 'make' and let it finish. STOP THERE! 5) WARNING!!! Now that 'glibc' has been built you are now ready to install it. If you were to do a 'make install' it would overwrite your host PC libraries and you would be screwed. Instead you want to do the install using 'make install_root=[path-to-mounted-disk-image] install'. This will then install 'glibc' to your disk image. 6) Continue putting whatever else you want on your image. 7) Unmount disk image. Hurray, you are done. Hope this helps. -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' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 10 14:21:20 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13BdUu-0000dB-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 10 Jul 2000 14:21:20 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 19F9916300; Mon, 10 Jul 2000 15:21:06 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Mon, 10 Jul 2000 09:08:55 -0400 Received: by vger.rutgers.edu id ; Mon, 10 Jul 2000 09:08:50 -0400 Received: from bagdad.magic.fr ([195.115.17.10]:58263 "EHLO bagdad.magic.fr") by vger.rutgers.edu with ESMTP id ; Mon, 10 Jul 2000 09:08:25 -0400 Received: from mail.inventel.fr (gw.inventel.fr [195.115.113.35]) by bagdad.magic.fr (8.9.0/8.9.0) with ESMTP id PAA20875 for ; Mon, 10 Jul 2000 15:19:51 +0200 (CEST) Received: from inventel.fr (193.54.84.50) by mail.inventel.fr (NPlex 1.3.171); 10 Jul 2000 15:19:35 +0200 Message-ID: <3969EAE1.896587BB@inventel.fr> Date: Mon, 10 Jul 2000 15:25:21 +0000 From: Xavier DEBREUIL X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.12-32 i686) X-Accept-Language: en MIME-Version: 1.0 To: Philip Blundell Cc: David Rusling , linux-arm Subject: Re: Building cross libraries References: <3965FBD3.65402A14@arm.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Hello, I would like to know the state of the development for Cirrus mcu : cspl7500 ep7211 ep7212 Is the cspl7500 linux version able to run (with little modifications...) on ep7211 and ep7212 ? thank you. Xavier. Philip Blundell wrote: > > > I've been 'playing' with cross-tools. Using the various helpful help > >files (Phil Blundell and Chris Rutter) I can now build binutils-2.9.5 > >and gcc-2.95.1 every which way. However, I cannot build glibc-2.1 > >or newlib-1.8.2. > > You might like to get binutils 2.10 and gcc "2.95.3" (ie the latest from the > 2.95 branch in CVS). > > > Following Chris's instructions, glibc-2.1 fails because gcc 2.95.1 > >is not the correct version. I hacked the configure file but it fails > >as it builds it later on. > > What failure are you seeing during the compile? I used to cross-build glibc > all the time, though I haven't done it recently. > > p. > > unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu > ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ > ++ kernel-related discussions. ++ unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 10 14:26:15 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13BdZf-0000hs-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 10 Jul 2000 14:26:15 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 699A916307; Mon, 10 Jul 2000 15:26:15 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Mon, 10 Jul 2000 09:14:13 -0400 Received: by vger.rutgers.edu id ; Mon, 10 Jul 2000 09:14:05 -0400 Received: from p54-robin-gui.tch.enablis.net ([194.168.180.114]:3157 "EHLO caramon.arm.linux.org.uk") by vger.rutgers.edu with ESMTP id ; Mon, 10 Jul 2000 09:13:49 -0400 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 OAA07399; Mon, 10 Jul 2000 14:24:57 +0100 Received: (from linux@localhost) by flint.arm.linux.org.uk (8.9.3/8.9.3) id OAA07927; Mon, 10 Jul 2000 14:22:00 +0100 From: Russell King - ARM Linux Admin Message-Id: <200007101322.OAA07927@flint.arm.linux.org.uk> Subject: Re: Touch Screen Driver Generic Interface for all Linux SA11x0 To: flynn@ozy.dec.com (Charlie Flynn) Date: Mon, 10 Jul 2000 14:21:59 +0100 (BST) Cc: linux-arm@vger.rutgers.edu, handhelds@handhelds.org In-Reply-To: <3969C50A.9E8C4BB6@ozy.dec.com> from "Charlie Flynn" at Jul 10, 2000 10:43:55 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@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Charlie Flynn writes: > I will also put this spec in html format on the www.handhelds.org web site. It should also sit elsewhere as well. Some suggestions: 1. Main ARM Linux site 2. HPA should have a copy (since he admins the device database, and should be able to answer questions like "What is the API provided by major x minor y) 3. in the Documentation/ part of the kernel source tree. > Since there has also been some interest in the handhelds@handhelds.org > mailing list I will post it in both lists for now with a view to maybe > moving the discussion to one (which one?) of the lists. I don't mean to cause offence to those people at handhelds.org or any of the other mailing lists, but it strikes me that we're getting too many mailing lists covering the same sort of areas, which is ending up with a loss of clarity and greater confusion. We currently have: linux-arm-announce@lists.arm.linux.org.uk For announcements about new features/projects etc only (moderated) linux-arm-kernel@lists.arm.linux.org.uk For discussions about kernels/kernel APIs (unmoderated) linux-arm@lists.arm.linux.org.uk OR linux-arm@vger.rutgers.edu For anything that doesn't fall into the above categories. (unmoderated) handhelds@handhelds.org ? sa1100-linux@pa.dec.com StrongARM-1100 stuff ? linux-7110@redhat.com Linux on ARM7110 ? I would prefer to see all kernel stuff discussed on linux-arm-kernel, so that there is one central place where people can go to look for stuff, in much the same way as the main linux-kernel list. I'd also like these "other" mailing lists provide a clear definition of their purpose so that it can be documented and readily available to people. Please, don't loose sight that we're not huge community (yet)! _____ |_____| ------------------------------------------------- ---+---+- | | Russell King linux@arm.linux.org.uk --- --- | | | | http://www.arm.linux.org.uk/ / / | | +-+-+ --- -+- / | THE developer of ARM Linux |+| /|\ / | | | --- | +-+-+ ------------------------------------------------- /\\\ | unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 10 14:33:37 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13Bdgn-0000qM-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 10 Jul 2000 14:33:37 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id A0B3816323; Mon, 10 Jul 2000 15:33:40 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Mon, 10 Jul 2000 09:21:39 -0400 Received: by vger.rutgers.edu id ; Mon, 10 Jul 2000 09:21:19 -0400 Received: from [194.201.77.34] ([194.201.77.34]:65218 "HELO fw-maid.maidenhead.arm.com") by vger.rutgers.edu with SMTP id ; Mon, 10 Jul 2000 09:21:03 -0400 Received: by fw-maid.maidenhead.arm.com; id OAA17689; Mon, 10 Jul 2000 14:29:45 +0100 Received: from unknown(192.168.2.10) by fw-maid.maidenhead.arm.com via smap (V5.0) id xma017683; Mon, 10 Jul 00 14:29:28 +0100 Received: from arm.com (dhcp2 [192.168.2.232]) by mhsun1.maidenhead.arm.com (8.9.3/8.9.3) with ESMTP id OAA09529; Mon, 10 Jul 2000 14:32:12 +0100 (BST) Message-ID: <3969DBCB.DC30A907@arm.com> Date: Mon, 10 Jul 2000 15:20:59 +0100 From: David Rusling X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Steve Hill Cc: Mike Touloumtzis , linux-arm Subject: Re: Building cross libraries References: <3965FBD3.65402A14@arm.com> <20000709203710.A21694@fiji.bluemug.com> <3969D105.57A2AB72@arm.com> <3969C9DD.7ECE2AF1@cotw.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Steve, I have a pocket linux system (based around busybox) that I built on an ARM Linux system (a Corel box). I use ROM fs myself. Thanks for the tips though... Dave Steve Hill wrote: > David Rusling wrote: > > > > Mike, > > > > thank you very much. I think that what I was doing was not building > > the correct version of glibc, I had glibc-2.1, not 2.1.3. After a bit of > > fiddling I can now build static applications for my ARM Linux box. > > This is with gcc 2.95.2 but I think that gcc 2.95.1 would also work. > > > > I build all my stuff for /usr/local/gnu so I ended up having to > > create a link from /usr/local/gnu/lib to /usr/local/gnu/arm-linux/lib > > (I also have arm-elf for the eCOS work that I've been doing). > > > > All I have to do now is to figure out how to 'install' the shared > > libraries onto my pocket Linux system... > > > Well, now that you have a complete working toolchain, you can start building > all the components for your disk image for your pocket Linux system. A good > place to start would be to get ARM packages from the Debian site. If you want > to build 'glibc' from scratch to put on your own disk image, here is one way > of doing it. > > 1) Create a ramdisk using '/dev/ramX' or use the loopback device and format > an 'ext2' filesystem on it. > > 2) Un-pack your 'glibc' sources again. > > 3) Put your cross-compilation environment in your path and run the configure > script for 'glibc' only this time using '--prefix=/usr'. This will > configure 'glibc' in a special way that will install the libraries in > '/lib' like it is on a "normal" Linux system. (By telling it the prefix > is /usr AND that the target is a Linux variant, glibc figures out that > you are creating it to be the main C run time library on the system) > > 4) Go ahead and do a 'make' and let it finish. STOP THERE! > > 5) WARNING!!! Now that 'glibc' has been built you are now ready to install > it. If you were to do a 'make install' it would overwrite your host PC > libraries and you would be screwed. Instead you want to do the install > using 'make install_root=[path-to-mounted-disk-image] install'. This > will then install 'glibc' to your disk image. > > 6) Continue putting whatever else you want on your image. > > 7) Unmount disk image. Hurray, you are done. > > Hope this helps. > > -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' to majordomo@vger.rutgers.edu > ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ > ++ kernel-related discussions. ++ -- ---------------------------------------------------------------------- David A Rusling Consulting Engineer ARM Limited Liberty House, Moorbridge Road, Maidenhead, SL6 8LT Tel: UK-(0)1628-427754 Fax: UK-(0)1628-780551 e-mail: david.rusling@arm.com ---------------------------------------------------------------------- unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 10 16:00:55 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13Bf3H-00023y-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 10 Jul 2000 16:00:55 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 90F7E15E36; Mon, 10 Jul 2000 16:56:48 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Mon, 10 Jul 2000 10:36:57 -0400 Received: by vger.rutgers.edu id ; Mon, 10 Jul 2000 10:36:39 -0400 Received: from crl.dec.com ([192.58.206.2]:2410 "EHLO crl.dec.com") by vger.rutgers.edu with ESMTP id ; Mon, 10 Jul 2000 10:35:45 -0400 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 KAA28691; Mon, 10 Jul 2000 10:47:01 -0400 (EDT) Received: by ims.crl.dec.com with Internet Mail Service (5.5.2650.21) id ; Mon, 10 Jul 2000 10:52:13 -0400 Message-ID: From: George France To: "'Russell King - ARM Linux Admin'" , flynn@ozy.dec.com Cc: linux-arm@vger.rutgers.edu, handhelds@handhelds.org Subject: RE: Touch Screen Driver Generic Interface for all Linux SA11x0 Date: Mon, 10 Jul 2000 10:47:08 -0400 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@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Russell King writes: I don't mean to cause offence to those people at handhelds.org or any of the other mailing lists, but it strikes me that we're getting too many mailing lists covering the same sort of areas, which is ending up with a loss of clarity and greater confusion. We currently have: I would prefer to see all kernel stuff discussed on linux-arm-kernel, so that there is one central place where people can go to look for stuff, in much the same way as the main linux-kernel list. I'd also like these "other" mailing lists provide a clear definition of their purpose so that it can be documented and readily available to people. Please, don't loose sight that we're not huge community (yet)! ------------------------------------------------------------------------- Hello Russell; Although I believe that you are correct in wanting arm kernel stuff discussed on linux-arm-kernel. The touch screen API is an issue that crosses many platforms and Operating Systems. Since at this time is mostly handheld devices that need a touch screen API, I think handhelds.org is the most appropriate place. In the past, I would have agree with you, that the linux-kernel list should have been the appropriate forum, but, IMHO, the main linux-kernel mailing list is becoming over crowed and too busy with side discussions that do not effect the main stream kernel. I think it is good, that there are more separate mailing list which take some of the pressure off of the linux-kernel list. The best examples that comes to mind is the USB mailing list or the linix-arm list. I believe that Charlie should send a note to the linux-kernel list, BSD lists and the plan9 list, telling everybody whom is interested that, a touch screen API is being discussed at handhelds.org. This is not a Linux only issue. There are many applications that run on multiple OSs. This week, I hope to have time to have a more clear definition and purpose of the handhelds.org lists. In short is a place to discuss and solve the issues that effect handheld/wearable devices in the Open Source community across Operating Systems. with delusions of grandeur, --George George France, france@crl.dec.com Cambridge Research Laboratory, Compaq Computer Corporation One Cambridgecenter MS: CRL Cambridge, MA 02142 USA unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 10 17:59:22 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13Bgtu-0003zG-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 10 Jul 2000 17:59:22 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id BCFD615E27; Mon, 10 Jul 2000 18:59:25 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Mon, 10 Jul 2000 12:47:18 -0400 Received: by vger.rutgers.edu id ; Mon, 10 Jul 2000 12:47:10 -0400 Received: from [12.38.17.9] ([12.38.17.9]:3659 "EHLO mail.aeptec.com") by vger.rutgers.edu with ESMTP id ; Mon, 10 Jul 2000 12:46:57 -0400 Received: by MAIL with Internet Mail Service (5.5.2650.21) id ; Mon, 10 Jul 2000 12:49:32 -0400 Message-ID: <32CC5B62AF0BD2119E4C00A0C9663E221F3BA9@MAIL> From: "Sun, Lei" To: "'linux-arm@vger.rutgers.edu'" Subject: compact flash! Date: Mon, 10 Jul 2000 12:49:26 -0400 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@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Hi Nico: I built linux kernel running in my SA1110 assabet board. I used the following kernel: linux-2.4.0-test1.tar.gz patch-2.4.0-test1-ac7-rmk1.gz patch-2.4.0test1-ac7.gz diff-2.4.0-test1-ac7-rmk1-np6.gz However I can't use the ethernet card (socket comm. LP) which is installed on the compact flash slot. I downloaded the ramdisk from CMU website, the pcmcia service is running, but I still can't activate the ethernet. can anybody tell me which patch should I apply for my current kernel and what ramdisk I should use. Lei Sun unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 10 18:42:29 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13BhZd-0004gj-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 10 Jul 2000 18:42:29 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 09EA315E59; Mon, 10 Jul 2000 19:38:59 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Mon, 10 Jul 2000 13:25:38 -0400 Received: by vger.rutgers.edu id ; Mon, 10 Jul 2000 13:25:04 -0400 Received: from mail1.digital.com ([204.123.2.50]:3017 "EHLO mail1.digital.com") by vger.rutgers.edu with ESMTP id ; Mon, 10 Jul 2000 13:19:13 -0400 Received: from pobox1.pa.dec.com (pobox1.pa.dec.com [16.1.240.19]) by mail1.digital.com (8.9.2/8.9.3/WV2.0h) with SMTP id KAA10881; Mon, 10 Jul 2000 10:30:37 -0700 (PDT) Received: from stowe.pa.dec.com by pobox1.pa.dec.com (5.65v3.2/1.1.10.5/07Nov97-1157AM) id AA21457; Mon, 10 Jul 2000 10:30:37 -0700 Received: by stowe.pa.dec.com; (5.65v4.0/1.1.8.2/06Jun96-0357PM) id AA23679; Mon, 10 Jul 2000 10:30:28 -0700 Date: Mon, 10 Jul 2000 10:30:28 -0700 Message-Id: <200007101730.AA23679@stowe.pa.dec.com> From: Deborah Wallach To: linux@arm.linux.org.uk Cc: flynn@ozy.dec.com, linux-arm@vger.rutgers.edu, handhelds@handhelds.org In-Reply-To: <200007101322.OAA07927@flint.arm.linux.org.uk> (message from Russell King - ARM Linux Admin on Mon, 10 Jul 2000 14:21:59 +0100 (BST)) Subject: Re: Touch Screen Driver Generic Interface for all Linux SA11x0 Address: Compaq Computer Corporation; Western Research Laboratory; 250 University Avenue; Palo Alto, CA 94301; USA Phone: 650-617-3315 Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu sa1100-linux@pa.dec.com StrongARM-1100 stuff ? I created this list for sa1100-specific linux issues (back when the sa1100 port was less well-integrated with the general arm port). It's possible that it's no longer needed. Clearly, if it stays around it needs to have sa1100 as well as sa1110 in its charter. Nicolas, I'm willing to let you define the charter... what do you think? -Debby unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 10 18:49:11 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13Bhg6-0004mj-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 10 Jul 2000 18:49:10 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id EBA3415E47; Mon, 10 Jul 2000 19:44:08 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Mon, 10 Jul 2000 13:31:19 -0400 Received: by vger.rutgers.edu id ; Mon, 10 Jul 2000 13:29:37 -0400 Received: from [205.250.170.220] ([205.250.170.220]:2572 "EHLO xanadu.vip.ca") by vger.rutgers.edu with ESMTP id ; Mon, 10 Jul 2000 13:29:09 -0400 Date: Mon, 10 Jul 2000 13:38:40 -0400 (EDT) From: Nicolas Pitre To: "Sun, Lei" Cc: "'linux-arm@vger.rutgers.edu'" Subject: Re: compact flash! In-Reply-To: <32CC5B62AF0BD2119E4C00A0C9663E221F3BA9@MAIL> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu On Mon, 10 Jul 2000, Sun, Lei wrote: > Hi Nico: > I built linux kernel running in my SA1110 assabet board. I used the > following kernel: > linux-2.4.0-test1.tar.gz > patch-2.4.0-test1-ac7-rmk1.gz > patch-2.4.0test1-ac7.gz > diff-2.4.0-test1-ac7-rmk1-np6.gz > > However I can't use the ethernet card (socket comm. LP) which is > installed on the compact flash slot. I downloaded the ramdisk from CMU > website, the pcmcia service is running, but I still can't activate the > ethernet. > can anybody tell me which patch should I apply for my current kernel and > what ramdisk I should use. Make sure your ramdisk is using the same module version as the one you should have produced with the kernel you compiled. Also note that the /lib/modules/2.4.0-xyz directory name should match your kernel version. Nicolas unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 10 18:49:37 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13BhgX-0004n3-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 10 Jul 2000 18:49:37 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id ADFBF15E64; Mon, 10 Jul 2000 19:48:12 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Mon, 10 Jul 2000 13:36:09 -0400 Received: by vger.rutgers.edu id ; Mon, 10 Jul 2000 13:36:02 -0400 Received: from opal.haven.org ([205.161.40.31]:25449 "EHLO opal.haven.org") by vger.rutgers.edu with ESMTP id ; Mon, 10 Jul 2000 13:35:47 -0400 Received: (from dkap@localhost) by opal.haven.org (8.9.1a/8.9.1) id NAA24344; Mon, 10 Jul 2000 13:42:18 -0400 Date: Mon, 10 Jul 2000 13:42:18 -0400 Message-Id: <200007101742.NAA24344@opal.haven.org> To: handhelds@handhelds.org Cc: linux@arm.linux.org.uk, flynn@ozy.dec.com, linux-arm@vger.rutgers.edu, handhelds@handhelds.org In-reply-to: <200007101730.AA23679@stowe.pa.dec.com> (message from Deborah Wallach on Mon, 10 Jul 2000 10:30:28 -0700) Subject: Re: [Handhelds] Re: Touch Screen Driver Generic Interface for all Linux SA11x0 Reply-To: dkap-wearables@haven.org From: "A Page in the Life of ..." X-Microsoft: Just say perl -MIO::Socket -e 'IO::Socket::INET->new(PeerAddr=>"ftp.microsoft.com:139",Proto=>'tcp')->send("Die sucker", MSG_OOB)' Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu -=> I created this list for sa1100-specific linux issues (back when the sa1100 -=> port was less well-integrated with the general arm port). It's possible -=> that it's no longer needed. Clearly, if it stays around it needs to have -=> sa1100 as well as sa1110 in its charter. Nicolas, I'm willing to let you -=> define the charter... what do you think? If you don't redifine the charter ... is there anywhere that folks are talking about sa1110 -> CompactFlash/IBM microdrive direct driver issues in linux? I've found stuff on going through pcmcia, but nothing on the direct stuff ... is it because there isn't anything, or there aren't any wire specs or what? Dave K> unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 10 19:09:52 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13Bi08-000555-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 10 Jul 2000 19:09:52 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id B687615E3C; Mon, 10 Jul 2000 20:09:43 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Mon, 10 Jul 2000 13:56:31 -0400 Received: by vger.rutgers.edu id ; Mon, 10 Jul 2000 13:55:19 -0400 Received: from [205.250.170.220] ([205.250.170.220]:2600 "EHLO xanadu.vip.ca") by vger.rutgers.edu with ESMTP id ; Mon, 10 Jul 2000 13:54:59 -0400 Date: Mon, 10 Jul 2000 14:04:32 -0400 (EDT) From: Nicolas Pitre To: Deborah Wallach Cc: sa1100-linux@pa.dec.com, linux-arm@vger.rutgers.edu, handhelds@handhelds.org Subject: sa1100-linux@pa.dec.com mailing list In-Reply-To: <200007101730.AA23679@stowe.pa.dec.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu On Mon, 10 Jul 2000, Deborah Wallach wrote: > > sa1100-linux@pa.dec.com > > StrongARM-1100 stuff ? > > I created this list for sa1100-specific linux issues (back when the sa1100 > port was less well-integrated with the general arm port). It's possible > that it's no longer needed. Does anyone on the sa1100-linux@pa.dec.com feel that this list is still required? I used it for my patch announcements and though it would be a good place for very SA11x0-specific Linux support discussions. Maybe this list can stay with its focus, maybe all the other lists can already do the job. Maybe concerned people can tell what they think? In all cases I would like to see someone to host an web archive of that list with as many old messages as we can gather. There were a lot of useful informations that went through. Nicolas unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 10 19:36:42 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13BiQ5-0005W8-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 10 Jul 2000 19:36:42 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id BE8CD15E47; Mon, 10 Jul 2000 20:36:38 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Mon, 10 Jul 2000 14:24:35 -0400 Received: by vger.rutgers.edu id ; Mon, 10 Jul 2000 14:24:18 -0400 Received: from [205.250.170.220] ([205.250.170.220]:2640 "EHLO xanadu.vip.ca") by vger.rutgers.edu with ESMTP id ; Mon, 10 Jul 2000 14:23:58 -0400 Date: Mon, 10 Jul 2000 14:32:47 -0400 (EDT) From: Nicolas Pitre To: "A Page in the Life of ..." Cc: handhelds@handhelds.org, linux-arm@vger.rutgers.edu Subject: Re: [Handhelds] Re: Touch Screen Driver Generic Interface for all Linux SA11x0 In-Reply-To: <200007101742.NAA24344@opal.haven.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu On Mon, 10 Jul 2000, A Page in the Life of ... wrote: > If you don't redifine the charter ... is there anywhere that folks are > talking about sa1110 -> CompactFlash/IBM microdrive direct driver issues in > linux? I've found stuff on going through pcmcia, but nothing on the direct > stuff ... is it because there isn't anything, or there aren't any wire > specs or what? It's because it should just work already. CompactFlash works for me on Assabet and the IBM microdrive is working for someone else who own one. The current SA1100 PCMCIA with the standard IDE support in the kernel are the only drivers required. Nicolas unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 10 19:52:41 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13BifY-0005ke-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 10 Jul 2000 19:52:40 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 5235E15E58; Mon, 10 Jul 2000 20:52:43 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Mon, 10 Jul 2000 14:40:09 -0400 Received: by vger.rutgers.edu id ; Mon, 10 Jul 2000 14:39:55 -0400 Received: from web117.yahoomail.com ([205.180.60.91]:2083 "HELO web117.yahoomail.com") by vger.rutgers.edu with SMTP id ; Mon, 10 Jul 2000 14:38:30 -0400 Received: (qmail 19498 invoked by uid 60001); 10 Jul 2000 18:49:43 -0000 Message-ID: <20000710184943.19497.qmail@web117.yahoomail.com> Received: from [171.64.108.158] by web117.yahoomail.com; Mon, 10 Jul 2000 11:49:43 PDT Date: Mon, 10 Jul 2000 11:49:43 -0700 (PDT) From: Zsolt Kiraly Subject: Re: sa1100-linux@pa.dec.com mailing list To: Nicolas Pitre , Deborah Wallach Cc: sa1100-linux@pa.dec.com, linux-arm@vger.rutgers.edu, handhelds@handhelds.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Hi Nico, Debbi, I think this list is still very useful in separating the generic ARMlinux messages from the StrongArmLinux specific ones. If the list does not put unbearable strains on the pa.dec.com server, then by all means please continue the service. An archive would be nice though. In any case, I would like to thank Compaq (nee Digital) for hosting this list, and I hope they will continue hosting it in the future. Zsolt --- Nicolas Pitre wrote: > > > On Mon, 10 Jul 2000, Deborah Wallach wrote: > > > > > sa1100-linux@pa.dec.com > > > > StrongARM-1100 stuff ? > > > > I created this list for sa1100-specific linux > issues (back when the sa1100 > > port was less well-integrated with the general arm > port). It's possible > > that it's no longer needed. > > Does anyone on the sa1100-linux@pa.dec.com feel that > this list is still > required? I used it for my patch announcements and > though it would be a > good place for very SA11x0-specific Linux support > discussions. Maybe this > list can stay with its focus, maybe all the other > lists can already do the > job. > > Maybe concerned people can tell what they think? > > In all cases I would like to see someone to host an > web archive of that > list with > as many old messages as we can gather. There were a > lot of useful > informations that went through. > > > Nicolas > ===== Zsolt Kiraly zskiraly@yahoo.com __________________________________________________ Do You Yahoo!? Get Yahoo! Mail – Free email you can access from anywhere! http://mail.yahoo.com/ unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 10 21:11:55 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13BjuD-0006vN-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 10 Jul 2000 21:11:53 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id D844115E9E; Mon, 10 Jul 2000 22:11:45 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Mon, 10 Jul 2000 15:54:50 -0400 Received: by vger.rutgers.edu id ; Mon, 10 Jul 2000 15:54:23 -0400 Received: from crl.dec.com ([192.58.206.2]:1907 "EHLO crl.dec.com") by vger.rutgers.edu with ESMTP id ; Mon, 10 Jul 2000 15:53:26 -0400 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 QAA01050; Mon, 10 Jul 2000 16:04:46 -0400 (EDT) Received: by ims.crl.dec.com with Internet Mail Service (5.5.2650.21) id ; Mon, 10 Jul 2000 16:09:58 -0400 Message-ID: From: George France To: "'dkap-wearables@haven.org'" , handhelds@handhelds.org Cc: linux@arm.linux.org.uk, flynn@ozy.dec.com, linux-arm@vger.rutgers.edu Subject: RE: [Handhelds] Re: Touch Screen Driver Generic Interface for all Linux SA11x0 Date: Mon, 10 Jul 2000 16:04:43 -0400 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@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu linux@handhelds.org --George -----Original Message----- From: A Page in the Life of ... [mailto:dkap-wearables@haven.org] Sent: Monday, July 10, 2000 1:42 PM To: handhelds@handhelds.org Cc: linux@arm.linux.org.uk; flynn@ozy.dec.com; linux-arm@vger.rutgers.edu; handhelds@handhelds.org Subject: Re: [Handhelds] Re: Touch Screen Driver Generic Interface for all Linux SA11x0 -=> I created this list for sa1100-specific linux issues (back when the sa1100 -=> port was less well-integrated with the general arm port). It's possible -=> that it's no longer needed. Clearly, if it stays around it needs to have -=> sa1100 as well as sa1110 in its charter. Nicolas, I'm willing to let you -=> define the charter... what do you think? If you don't redifine the charter ... is there anywhere that folks are talking about sa1110 -> CompactFlash/IBM microdrive direct driver issues in linux? I've found stuff on going through pcmcia, but nothing on the direct stuff ... is it because there isn't anything, or there aren't any wire specs or what? Dave K> unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 10 21:50:58 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13BkW2-0007UW-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 10 Jul 2000 21:50:58 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 77E8B15E97; Mon, 10 Jul 2000 22:50:45 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Mon, 10 Jul 2000 16:37:50 -0400 Received: by vger.rutgers.edu id ; Mon, 10 Jul 2000 16:37:36 -0400 Received: from [63.195.182.101] ([63.195.182.101]:1658 "EHLO barbados.bluemug.com") by vger.rutgers.edu with ESMTP id ; Mon, 10 Jul 2000 16:36:02 -0400 Received: from fiji.bluemug.com [192.168.50.32] (mail) by barbados.bluemug.com with esmtp (Exim 2.05 #1 (Debian)) id 13BkSf-0003uq-00; Mon, 10 Jul 2000 13:47:29 -0700 Received: from miket by fiji.bluemug.com with local (Exim 2.05 #1 (Debian)) id 13BkSd-0007YE-00; Mon, 10 Jul 2000 13:47:27 -0700 Date: Mon, 10 Jul 2000 13:47:27 -0700 From: Mike Touloumtzis To: Charlie Flynn Cc: linux-arm@vger.rutgers.edu, handhelds@handhelds.org Subject: Re: Touch Screen Driver Generic Interface for all Linux SA11x0 platforms. Message-ID: <20000710134727.H21694@fiji.bluemug.com> References: <3962EAD8.E4DE217B@ozy.dec.com> <3969C50A.9E8C4BB6@ozy.dec.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <3969C50A.9E8C4BB6@ozy.dec.com>; from Charlie Flynn on Mon, Jul 10, 2000 at 10:43:55PM +1000 Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu On Mon, Jul 10, 2000 at 10:43:55PM +1000, Charlie Flynn wrote: > > This is the structure contains the X and Y pixel coordinates of a > single touch screen event. It is passed from the driver to the user by > the read() function. > Hi Charlie, Pixel coordinates won't be enough, in general. Digitizers used for handwriting recognition often have much higher resolution than the LCDs, and the extra information is vital for good handwriting recognition, particularly for Asian languages. I've integrated Asian handwriting recognition libraries into OSes which were not designed with this in mind, and I had to hack things up get digitizer-resolution coordinates. Plus, I think it'd be nice to decouple the digitizer API from a specific screen resolution. miket unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 10 22:09:28 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13Bknv-0007ly-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 10 Jul 2000 22:09:28 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 93A7915E97; Mon, 10 Jul 2000 23:09:26 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Mon, 10 Jul 2000 16:52:40 -0400 Received: by vger.rutgers.edu id ; Mon, 10 Jul 2000 16:52:37 -0400 Received: from crl.dec.com ([192.58.206.2]:2521 "EHLO crl.dec.com") by vger.rutgers.edu with ESMTP id ; Mon, 10 Jul 2000 16:52:19 -0400 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 RAA02166; Mon, 10 Jul 2000 17:03:46 -0400 (EDT) Received: by crlwebmail.crl.dec.com with Internet Mail Service (5.5.2650.21) id ; Mon, 10 Jul 2000 17:08:39 -0400 Message-ID: From: George France To: "'handhelds@handhelds.org'" , Deborah Wallach Cc: sa1100-linux@pa.dec.com, linux-arm@vger.rutgers.edu Subject: RE: [Handhelds] sa1100-linux@pa.dec.com mailing list Date: Mon, 10 Jul 2000 17:03:44 -0400 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@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu I suspect that the sa1100-linux list will still be useful for the next two or three months, as there are still some drivers to be completed. At that time we should re-evaluate. --George George France, france@crl.dec.com Cambridge Research Laboratory, Compaq Computer Corporation One Cambridgecenter MS: CRL Cambridge, MA 02142 USA -----Original Message----- From: Nicolas Pitre [mailto:nico@cam.org] Sent: Monday, July 10, 2000 2:05 PM To: Deborah Wallach Cc: sa1100-linux@pa.dec.com; linux-arm@vger.rutgers.edu; handhelds@handhelds.org Subject: [Handhelds] sa1100-linux@pa.dec.com mailing list On Mon, 10 Jul 2000, Deborah Wallach wrote: > > sa1100-linux@pa.dec.com > > StrongARM-1100 stuff ? > > I created this list for sa1100-specific linux issues (back when the sa1100 > port was less well-integrated with the general arm port). It's possible > that it's no longer needed. Does anyone on the sa1100-linux@pa.dec.com feel that this list is still required? I used it for my patch announcements and though it would be a good place for very SA11x0-specific Linux support discussions. Maybe this list can stay with its focus, maybe all the other lists can already do the job. Maybe concerned people can tell what they think? In all cases I would like to see someone to host an web archive of that list with as many old messages as we can gather. There were a lot of useful informations that went through. Nicolas _______________________________________________ Handhelds mailing list Handhelds@handhelds.org http://handhelds.org/mailman/listinfo/handhelds unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Tue Jul 11 06:10:55 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13BsJr-0005tV-00 for linux-arm-archive@lists.arm.linux.org.uk; Tue, 11 Jul 2000 06:10:55 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 18E7B15D64; Tue, 11 Jul 2000 07:11:00 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 11 Jul 2000 00:58:38 -0400 Received: by vger.rutgers.edu id ; Tue, 11 Jul 2000 00:58:29 -0400 Received: from [63.195.182.101] ([63.195.182.101]:2239 "EHLO barbados.bluemug.com") by vger.rutgers.edu with ESMTP id ; Tue, 11 Jul 2000 00:58:12 -0400 Received: from fiji.bluemug.com [192.168.50.32] (mail) by barbados.bluemug.com with esmtp (Exim 2.05 #1 (Debian)) id 13BsIh-000470-00; Mon, 10 Jul 2000 22:09:43 -0700 Received: from miket by fiji.bluemug.com with local (Exim 2.05 #1 (Debian)) id 13BsIg-0000At-00; Mon, 10 Jul 2000 22:09:42 -0700 Date: Mon, 10 Jul 2000 22:09:42 -0700 From: Mike Touloumtzis To: Xavier DEBREUIL Cc: Philip Blundell , David Rusling , linux-arm Subject: Re: Building cross libraries Message-ID: <20000710220942.P21694@fiji.bluemug.com> References: <3965FBD3.65402A14@arm.com> <3969EAE1.896587BB@inventel.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <3969EAE1.896587BB@inventel.fr>; from Xavier DEBREUIL on Mon, Jul 10, 2000 at 03:25:21PM +0000 Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu On Mon, Jul 10, 2000 at 03:25:21PM +0000, Xavier DEBREUIL wrote: > Hello, > I would like to know the state of the development for Cirrus mcu : > cspl7500 > ep7211 > ep7212 > Is the cspl7500 linux version able to run (with little modifications...) on > ep7211 and ep7212 ? > I have the (pretty ancient) 2.2.1 kernel booting and running on an EDB7211 evaluation board, as of Friday night :-). Here's a very terse set of instructions I wrote for myself: ===================================================================== Get the canonical 2.2.1 kernel from kernel.org and unpack it: wget ftp://ftp.us.kernel.org/pub/linux/kernel/v2.2/linux-2.2.1.tar.gz tar zxvf linux-2.2.1.tar.gz mv linux linux-2.2.1-ep7211 Go to the kernel directory and patch it: cd linux-2.2.1-ep7211 export PATCHDIR=/place/where/you/keep/your/patches # Russell King's official Linux/ARM patch: zcat $PATCHDIR/patch-2.2.1-rmk2.gz | patch -p1 # Phil Blundell's patch: zcat $PATCHDIR/linux-2.2.1-philb-990208.gz | patch -p1 # www.calcaria.net (linux-7110) "crash+burn" patch: zcat $PATCHDIR/crash+burn-26.patch.gz | patch -p1 # Ben Williamson's EP7211 port patch (NOTE -p2 instead of -p1!): zcat $PATCHDIR/cb26-benw3.gz | patch -p2 # my patch (-miket1): cat $PATCHDIR/patch-2.2.1-miket1 | patch -p1 Fixes in -miket1 patch: ==> include intermediate patches in EXTRAVERSION ==> in arch/arm/Makefile: elf32arm -> armelf_linux in $(LD) ==> in arch/arm/vmlinux-armv.lds: change top line to: OUTPUT_FORMAT("elf32-littlearm", "elf32-bigarm", "elf32-littlearm") ==> bandaid for Oops in serial bottom half ==> wrong TLB/cache flush coprocessor insns were being assembled (found this out the hard way :-). Gross fix included. Use Ben Williamson's 'shoehorn' boot loader to download the kernel over the serial port; first install my patch to set the DRAM refresh to 64kHz (patch also restores terminal settings when you kill shoehorn). ===================================================================== Patches (for kernel and shoehorn) attached. Note that both patches are quick fixes to get things working; I didn't fix the kernel correctly, and the shoehorn patch still uses the 'anvil' hardware type because I was in a hurry. I'm not going to concentrate much effort on 2.2.1; I'm looking to forward port the EDB7211 stuff to 2.4.0-test*, but I'm not sure how much time I'll have for that in the next couple of weeks (probably not much). Although I have the eval board for work, the Linux kernel stuff is strictly free-time hacking at this point. If anyone is already doing/has already done a 7211 port to 2.4, please let me know, I'm lazy! The version of the kernel I got working just has serial console support, no keyboard/LCD/touchscreen/ethernet/PCMCIA. There's a random little Linux distro called 'Royal Linux' that has a port which includes all this stuff, but when I tried it a while ago, it crashed a lot ('a lot' as in 'only made it to init one time in three'). Hopefully it works better for its authors and I was just missing some magic. I'm planning on getting my hands on it soon, so that I can use its drivers in the port to 2.4. miket unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Tue Jul 11 08:28:45 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13BuTE-0007mH-00 for linux-arm-archive@lists.arm.linux.org.uk; Tue, 11 Jul 2000 08:28:45 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id E231715F92; Tue, 11 Jul 2000 09:28:35 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 11 Jul 2000 03:12:04 -0400 Received: by vger.rutgers.edu id ; Tue, 11 Jul 2000 03:11:51 -0400 Received: from ns0.utdallas.edu ([129.110.10.1]:63973 "HELO ns0.utdallas.edu") by vger.rutgers.edu with SMTP id ; Tue, 11 Jul 2000 03:10:40 -0400 Received: from apache.utdallas.edu (apache.utdallas.edu [129.110.16.9]) by ns0.utdallas.edu (Postfix) with ESMTP id C64511A00AD; Tue, 11 Jul 2000 02:22:13 -0500 (CDT) Received: from localhost (vasantr@localhost) by apache.utdallas.edu (8.9.1/8.9.1) with ESMTP id CAA03075; Tue, 11 Jul 2000 02:22:27 -0500 (CDT) X-Authentication-Warning: apache.utdallas.edu: vasantr owned process doing -bs Date: Tue, 11 Jul 2000 02:22:27 -0500 (CDT) From: Vasant Ramasubramanian To: linux-arm@vger.rutgers.edu, sa1100-linux@pa.dec.com Subject: SDRAM Start-up code Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu I've spent the last few days trying very hard to get the SDRAM working on a custom SA1110 based board but have failed thus far. Does anyone (besides blob & Compaq/bootldr) have simple assembly code to "wake-up" the SDRAMs(follow through the state machine listed in the 1110 manual) and configure & enable them? At this point I am unable to read/write to SDRAM after trying my code; I do all my initalization after RESET so the MMU is unconfigured and caches are turned off. The hardware *looks* OK but I'm not rulling it out yet. Anyone know of good data sheets/SDRAM briefs that might show in detail waveforms expected to see during configuration and non-burst read/writes? We're using Micron 64Mbit x 16 SDRAMs; I have data sheets from both and IBM and both do a very crappy job of explaining terms and procedures to non-long time users of DRAM/SDRAM I'm at my wits end over here... Thanks, Vasant. unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Tue Jul 11 10:12:07 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13Bw5H-0000or-00 for linux-arm-archive@lists.arm.linux.org.uk; Tue, 11 Jul 2000 10:12:07 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 673BC15F99; Tue, 11 Jul 2000 11:07:55 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 11 Jul 2000 04:30:01 -0400 Received: by vger.rutgers.edu id ; Tue, 11 Jul 2000 04:28:34 -0400 Received: from leonardo.telscom.ch ([193.247.121.34]:2456 "EHLO leonardo.telscom.ch") by vger.rutgers.edu with ESMTP id ; Tue, 11 Jul 2000 04:27:03 -0400 Received: from telscom.ch ([193.247.121.35]) by leonardo.telscom.ch (Post.Office MTA v3.1.2 release (PO205-101c) ID# 0-0U10L2S100) with ESMTP id AAA140 for ; Tue, 11 Jul 2000 10:31:53 +0200 Message-ID: <396ADF3F.BDC59A4D@telscom.ch> Date: Tue, 11 Jul 2000 10:48:00 +0200 From: Mathias Teikari Organization: Telscom AG X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.15 i686) X-Accept-Language: en MIME-Version: 1.0 To: linux-arm Subject: EEPro100 NICs and EBSA285. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Hi all, Has anybody had a working EBSA-285 setup with Intel's EEPro100 NICs? I am using a 2.2.15 kernel patched with patch-2.2.15-rmk1 (because I need a 2.2 kernel at this point) and ebsa285-bios-1.06 w. diff2 patch. The eepro100 driver is compiled into the kernel because I want to mount an NFS root fs. Now, the problem.. The cards won't initialise properly, or at least that is what the kernel thinks. ... POSIX conformance testing by UNIFIX PCI: Probing PCI hardware pci_scan_bus for bus 0 PCI: 00:38 [8086/1229] PCI: pci_scan_bus returning with max=00 Linux NET4.0 for Linux 2.2 Based upon Swansea University Computer Society NET3.039 NET4: Unix domain sockets 1.0 for Linux NET4.0. NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP TCP: Hash tables configured (ehash 16384 bhash 16384) Starting kswapd v 1.5 RAM disk driver initialized: 1 RAM disks of 4096K size Found Intel i82557 PCI Speedo at I/O 0xe1800000, IRQ 22. PCI latency timer (CFLT) is 0x20. eepro100.c:v1.09j-t 9/29/99 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers /eepro100.html eepro100.c: $Revision: 1.20.2.3 $ 2000/03/02 Modified by Andrey V. Savochkin and others eth0: Intel PCI EtherExpress Pro100 at 0xe1800000, 00:90:27:8C:D8:6B, IRQ 22. Receiver lock-up bug exists -- enabling work-around. Board assembly 721383-006, Physical connectors present: RJ45 Primary interface chip i82555 PHY #1. Self test failed, status ffffffff: Failure to initialize the i82557. Verify that the card is in a bus-master capable slot. ... I know that the hardware is OK because it's running when using another OS (in house developed mini-OS). A thought that crossed my mind is address mapping problems (PCI-SDRAM et vice-versa) or some other setup of the CSRs. Any suggestions? Thanks, Mathias -- +---------------------------------------------------------+ .--. | Mathias Teikari mathias.teikari@telscom.ch | |o_o | | Ba. Sc. EE. Office Ph: +41 (0)31 376 2030 | |:_/ | | SW Development Engineer Mobile Ph: +41 (0)76 541 9449 | // \ \ | Telscom AG Sandrainstr. 17, CH-3007 Bern | (| | ) | | /'\_ _/`\ +---------------- http://www.telscom.ch ------------------+ \___)=(___/ unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Tue Jul 11 10:42:22 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13BwYY-0001Cn-00 for linux-arm-archive@lists.arm.linux.org.uk; Tue, 11 Jul 2000 10:42:22 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 56693160AA; Tue, 11 Jul 2000 11:38:24 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 11 Jul 2000 05:25:21 -0400 Received: by vger.rutgers.edu id ; Tue, 11 Jul 2000 05:20:14 -0400 Received: from [202.102.146.182] ([202.102.146.182]:2571 "EHLO hisense.qd.sd.cn") by vger.rutgers.edu with ESMTP id ; Tue, 11 Jul 2000 05:19:55 -0400 Received: from WANGKEQIANG ([192.137.33.168]) by hisense.qd.sd.cn with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3) id 3VVZ42X1; Tue, 11 Jul 2000 17:31:10 +0800 Date: Tue, 11 Jul 2000 17:29:6 +0800 From: joy To: linux-arm@vger.rutgers.edu Subject: cross compiler for arm X-mailer: FoxMail 3.0 beta 1 [cn] Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <20000711092000Z156768-26622+381@vger.rutgers.edu> Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu hi,i compiled cross compiler for arm.the kernel is 2.4.0-test2.i use binutils-2.9.5.0.42 ,gcc-2.95.2.tar.gz,gcc-2.95.2.diff-991022.gz and glibc2.1.3,glibc-linuxthreads-2.1.3.tar.gz,glibc-crypt-2.1.tar.gz. compiling the binutils-2.9.5.0.42 and gcc-2.95.2 is success,but when compiling glibc ,there are some errors as follows: ..... /usr/local/arm/lib/gcc-lib/arm-linux/2.95.2/libgcc.a(tinfo2.o):In function '_throw_type_match_rtti' gcc-2.95.2/gcc/./cp/tinfo2.cc:114:multi definition of 'signed char type_info node' /usr/local/arm/lib/gcc-lib/arm-linux/2.95.2/libgcc.a(tinfo2.o:gcc-2.95.2/gcc/./cp/tinfo2. cc:114:first defined here .... why? who can help me? best regards. unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Tue Jul 11 11:12:52 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13Bx24-0001uc-00 for linux-arm-archive@lists.arm.linux.org.uk; Tue, 11 Jul 2000 11:12:52 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 53748160B6; Tue, 11 Jul 2000 12:07:35 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 11 Jul 2000 05:45:52 -0400 Received: by vger.rutgers.edu id ; Tue, 11 Jul 2000 05:44:18 -0400 Received: from [202.104.32.241] ([202.104.32.241]:42837 "HELO 21cn.com") by vger.rutgers.edu with SMTP id ; Tue, 11 Jul 2000 05:43:47 -0400 Received: from =?ISO-8859-1?Q?=CB=E5=C1=A2=CC=CE([202.102.146.181]?=) by 21cn.com(JetMail 2.5.3.0) with SMTP id jm8396b6293; Tue, 11 Jul 2000 09:54:42 -0000 Date: Tue, 11 Jul 2000 17:57:46 +0800 From: huang To: linux-arm@vger.rutgers.edu Subject: mount NFS on assabet X-mailer: FoxMail 3.0 beta 2 [cn] Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <20000711094355Z156536-26621+383@vger.rutgers.edu> Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu I make the SOCKET LP-E PCMCIA ethernet card worked, so i want mount NFS through it,but when i run " mount -o rw, ... " i got error as this: nfs warning:mount wersion older than kernel RPC:sendmsg return error 101 the NFS server working well, i can mount NFS through other PC. Could anyone tell me why? thanks huang huang_ch@21cn.com unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Tue Jul 11 11:59:56 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13Bxlc-0002bA-00 for linux-arm-archive@lists.arm.linux.org.uk; Tue, 11 Jul 2000 11:59:56 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id EDB5B15E87; Tue, 11 Jul 2000 12:59:02 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 11 Jul 2000 06:44:43 -0400 Received: by vger.rutgers.edu id ; Tue, 11 Jul 2000 06:43:54 -0400 Received: from proxy.jakinternet.co.uk ([212.41.43.4]:1615 "HELO smtp2.jakinternet.co.uk") by vger.rutgers.edu with SMTP id ; Tue, 11 Jul 2000 06:42:47 -0400 Received: from smtp.jakinternet.co.uk (smtp.jakinternet.co.uk [212.41.41.61]) by smtp2.jakinternet.co.uk (Postfix) with SMTP id E12DFA76DD for ; Tue, 11 Jul 2000 11:53:17 +0100 (BST) Received: from moo ([212.41.39.15]) by smtp.jakinternet.co.uk ; Tue, 11 Jul 2000 11:54:10 -0100 Date: Tue, 11 Jul 2000 11:53:49 +0100 From: Peter Naulls To: linux-arm@vger.rutgers.edu Subject: Re: EEPro100 NICs and EBSA285. Message-ID: <122464dc49%peter@erble.freeserve.co.uk> In-Reply-To: <396ADF3F.BDC59A4D@telscom.ch> X-Mailer: Messenger v1.40f for RISC OS MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Posting-Agent: RISC OS Newsbase 0.60m User-Agent: POPstar/2.02 Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu In message <396ADF3F.BDC59A4D@telscom.ch> Mathias Teikari wrote: > Board assembly 721383-006, Physical connectors present: RJ45 > Primary interface chip i82555 PHY #1. > Self test failed, status ffffffff: > Failure to initialize the i82557. > Verify that the card is in a bus-master capable slot. > ... > > I know that the hardware is OK because it's running when using > another OS (in house developed mini-OS). > > A thought that crossed my mind is address mapping problems > (PCI-SDRAM et vice-versa) or some other setup of the CSRs. Mostly likely yes - it seems it's not finding some of its initial resources. There are a couple of compile options in this driver you might want to take a look at; and certainly the initilisation code - it's relatively simple. Peter -- ------------------------------------------------------------------------ Peter Naulls - peter@erble.freeserve.co.uk Homepage - http://free.prohosting.com/~chocky/ Java for RISC OS and ARM - http://free.prohosting.com/~chocky/java/ Debian Linux on RiscPCs - http://www.erble.freeserve.co.uk/ ------------------------------------------------------------------------ unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Tue Jul 11 14:58:51 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13C0Yl-0005AG-00 for linux-arm-archive@lists.arm.linux.org.uk; Tue, 11 Jul 2000 14:58:51 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 4E15C15EC9; Tue, 11 Jul 2000 15:58:53 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 11 Jul 2000 09:45:47 -0400 Received: by vger.rutgers.edu id ; Tue, 11 Jul 2000 09:41:53 -0400 Received: from ice.fiftyone.com ([208.225.80.11]:4711 "EHLO ice.ar51.net") by vger.rutgers.edu with ESMTP id ; Tue, 11 Jul 2000 09:41:02 -0400 Received: from server01.asi (akron-80-192.ar51.net [208.225.80.192]) by ice.ar51.net (8.9.3/8.8.7) with ESMTP id JAA19104; Tue, 11 Jul 2000 09:52:50 -0400 Received: by SERVER01 with Internet Mail Service (5.5.2448.0) id <3W4R04YH>; Tue, 11 Jul 2000 09:54:40 -0400 Message-ID: From: Jeff Sutherland To: "'huang'" , "'linux-arm@vger.rutgers.edu'" Subject: RE: mount NFS on assabet Date: Tue, 11 Jul 2000 09:54:38 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu I make the SOCKET LP-E PCMCIA ethernet card worked, so i want mount NFS through it,but when i run " mount -o rw, ... " i got error as this: nfs warning:mount wersion older than kernel RPC:sendmsg return error 101 the NFS server working well, i can mount NFS through other PC. Could anyone tell me why? thanks huang huang_ch@21cn.com A little more information about your setup would be helpful, such as kernel version and what you are mounting to. NFS mounting works fine. Looks like your server maybe doesn't like your Assabet. Check your server config, especially /etc/exports, /etc/hosts.allow, /etc/hosts, and maybe /etc/fstab on your Assabet's ramdisk. NFS on Assabet works well, including NFS mounting of root filesystem. //Jeff unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Tue Jul 11 15:29:11 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13C126-0005aH-00 for linux-arm-archive@lists.arm.linux.org.uk; Tue, 11 Jul 2000 15:29:10 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id A0C5215E95; Tue, 11 Jul 2000 16:29:15 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 11 Jul 2000 10:16:41 -0400 Received: by vger.rutgers.edu id ; Tue, 11 Jul 2000 10:16:25 -0400 Received: from zmamail03.zma.compaq.com ([161.114.64.103]:3884 "HELO zmamail03.zma.compaq.com") by vger.rutgers.edu with SMTP id ; Tue, 11 Jul 2000 10:16:08 -0400 Received: by zmamail03.zma.compaq.com (Postfix, from userid 12345) id 115655EBD; Tue, 11 Jul 2000 10:27:32 -0400 (EDT) Received: from oils.ozy.dec.com (oils.ozy.dec.com [16.153.192.1]) by zmamail03.zma.compaq.com (Postfix) with ESMTP id EBC285F57; Tue, 11 Jul 2000 10:27:27 -0400 (EDT) Received: from ozy.dec.com by oils.ozy.dec.com (8.8.8/1.1.10.5/12Oct99-0148PM) id AAA0000002390; Wed, 12 Jul 2000 00:27:24 +1000 (EST) Message-ID: <396B2E9D.BAAC754B@ozy.dec.com> Date: Wed, 12 Jul 2000 00:26:37 +1000 From: Charlie Flynn X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Mike Touloumtzis Cc: linux-arm@vger.rutgers.edu, handhelds@handhelds.org Subject: Re: Touch Screen Driver Generic Interface for all Linux SA11x0 platforms. References: <3962EAD8.E4DE217B@ozy.dec.com> <3969C50A.9E8C4BB6@ozy.dec.com> <20000710134727.H21694@fiji.bluemug.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Thanks for the reply Mike. I haven't come across a Digitizer before so are you saying that a simple redesign of the TS_EVENT structure is all that is needed to accommodate the Digitizer or does the Digitizer require other special considerations? In other words will this spec accommodate the Digitizer without too much modification? --Charlie Mike Touloumtzis wrote: > On Mon, Jul 10, 2000 at 10:43:55PM +1000, Charlie Flynn wrote: > > > > This is the structure contains the X and Y pixel coordinates of a > > single touch screen event. It is passed from the driver to the user by > > the read() function. > > > > Hi Charlie, > > Pixel coordinates won't be enough, in general. Digitizers used for > handwriting recognition often have much higher resolution than the > LCDs, and the extra information is vital for good handwriting > recognition, particularly for Asian languages. > > I've integrated Asian handwriting recognition libraries into OSes > which were not designed with this in mind, and I had to hack things > up get digitizer-resolution coordinates. > > Plus, I think it'd be nice to decouple the digitizer API from a > specific screen resolution. > > miket > > unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu > ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ > ++ kernel-related discussions. ++ unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Tue Jul 11 16:11:16 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13C1gq-0006HQ-00 for linux-arm-archive@lists.arm.linux.org.uk; Tue, 11 Jul 2000 16:11:16 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 7955315F17; Tue, 11 Jul 2000 17:04:37 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 11 Jul 2000 10:49:51 -0400 Received: by vger.rutgers.edu id ; Tue, 11 Jul 2000 10:45:19 -0400 Received: from mail.teklogix.com ([207.219.2.10]:2260 "EHLO tekincisnts-4.teklogix.com") by vger.rutgers.edu with ESMTP id ; Tue, 11 Jul 2000 10:44:35 -0400 Received: from DeadDuck (BILL [10.128.5.25]) by tekincisnts-4.teklogix.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id 3C08SN37; Tue, 11 Jul 2000 10:56:05 -0400 To: Vasant Ramasubramanian Cc: linux-arm@vger.rutgers.edu, sa1100-linux@pa.dec.com Subject: Re: SDRAM Start-up code References: From: Bill Pringlemeir Organization: noitazinagro X-Home-Page: http://www.wwonline.com/~bpringle/ Date: 11 Jul 2000 11:00:40 -0400 In-Reply-To: Vasant Ramasubramanian's message of "Tue, 11 Jul 2000 02:22:27 -0500 (CDT)" Message-ID: Lines: 114 User-Agent: Gnus/5.0803 (Gnus v5.8.3) Emacs/20.6 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu >>>>> "VR" == Vasant Ramasubramanian writes: VR> I've spent the last few days trying very hard to get the SDRAM VR> working on a custom SA1110 based board but have failed thus far. VR> Does anyone (besides blob & Compaq/bootldr) have simple assembly VR> code to "wake-up" the SDRAMs(follow through the state machine VR> listed in the 1110 manual) and configure & enable them? VR> At this point I am unable to read/write to SDRAM after trying my VR> code; I do all my initalization after RESET so the MMU is VR> unconfigured and caches are turned off. [snip] There are some problems with the SA1110 SDRAM controller. It only works at some speeds. I think that with a 1/4 speed bus, it will always work. However, using the 1/2 speed bus, it will work from 187-200Mhz and from 50-118Mhz depending on the CAS latency. I don't think this is mentioned in errata (or whatever they call it). Unfortunately, the SA1110 SDRAM controller doesn't give you control over the waveforms like say the UPM on an MPC860. This means that you have to work with the parameters that the SA1110 provides. Most SDRAM has the same state machine and commands. These are sent by three control lines (I forget which), so there are eight different commands (maybe more, one is an escape). Here are some 1/4 speed numbers. [start] ppcr_speed: .long 0x00000006 /* 147 Mhz */ mdcas00: .long 0xaaaaaa7f /* 1/4 speed */ mdrefr0: .long 0x00700321 /* 1/4 speed */ mdcas01: .long 0xaaaaaaaa mdcas02: .long 0xaaaaaaaa mdcnfg: .long 0x72547254 initSDRAM: ldr r0,memCfgAddr ldr r1,mdcas00 /* MDCAS00 value. */ str r1,[r0,#0x4] ldr r1,mdcas01 /* MDCAS01 value. */ str r1,[r0,#0x8] ldr r1,mdcas02 /* MDCAS02 value. */ str r1,[r0,#0xc] ldr r1,mdrefr0 /* MDREFR value. */ STR r1,[r0,#0x1c] ldr r1,mdcnfg /* turn on the DRAM */ STR r1,[r0] ldr r0,powCfgAddr mov r1,#0x08 /* clear the DRAM Hold bit */ STR r1,[r0,#0x4] /* Perform 8 reads from unenabled DRAM */ mov r1, #DRAM_PHYSICAL ldr r2, [r1] ldr r2, [r1] ldr r2, [r1] ldr r2, [r1] ldr r2, [r1] ldr r2, [r1] ldr r2, [r1] ldr r2, [r1] ldr r0,memCfgAddr ldr r1,mdcnfg /* enable the DRAM */ orr r1,r1,#1 STR r1,[r0] /* * Wait for DRAM to come up. */ MOV r1, #0x200 0: SUBS r1, r1, #1 BNE 0b mov pc,lr /* return to caller. */ [end] If 1/4 speed doesn't work, take a look at the hardware. If you are lucky enough to have the bus broken out, hook up a logic analyzer and take a look. Intel suggested added line traces/delay elements to get things working at 1/2 speed. If you have a large trace, then things might not work exactly like the Assabet, etc boards. This sucks and is frustrating to debug... hth, Bill -- CLICKED BY FIVE DESTROYERS. SINKING. U-829. unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Tue Jul 11 16:58:49 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13C2Qr-0006wj-00 for linux-arm-archive@lists.arm.linux.org.uk; Tue, 11 Jul 2000 16:58:49 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id A85DC15F3D; Tue, 11 Jul 2000 17:58:52 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 11 Jul 2000 11:45:07 -0400 Received: by vger.rutgers.edu id ; Tue, 11 Jul 2000 11:43:55 -0400 Received: from FORT-POINT-STATION.MIT.EDU ([18.72.0.53]:40366 "EHLO fort-point-station.mit.edu") by vger.rutgers.edu with ESMTP id ; Tue, 11 Jul 2000 11:32:55 -0400 Received: from grand-central-station.MIT.EDU (GRAND-CENTRAL-STATION.MIT.EDU [18.69.0.34]) by fort-point-station.mit.edu (8.9.2/8.9.2) with ESMTP id LAA23209 for ; Tue, 11 Jul 2000 11:44:48 -0400 (EDT) Received: from melbourne-city-street.MIT.EDU (MELBOURNE-CITY-STREET.MIT.EDU [18.69.0.45]) by grand-central-station.MIT.EDU (8.9.2/8.9.2) with ESMTP id LAA07532 for ; Tue, 11 Jul 2000 11:44:48 -0400 (EDT) Received: from baba-yaga.mit.edu (IDENT:root@BABA-YAGA.MIT.EDU [18.244.1.164]) by melbourne-city-street.MIT.EDU (8.9.3/8.9.2) with ESMTP id LAA04233 for ; Tue, 11 Jul 2000 11:44:48 -0400 (EDT) Received: by baba-yaga.mit.edu (8.9.3/4.7) id LAA16149; Tue, 11 Jul 2000 11:44:47 -0400 To: linux-arm@vger.rutgers.edu Subject: ebsa-285 network cards From: Jacob Strauss Date: 11 Jul 2000 11:44:47 -0400 Message-ID: Lines: 30 X-Mailer: Gnus v5.7/Emacs 20.5 Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu I'm trying to get a network card working with an ebsa-285 and backplane. I've tried a 3c905b, 3c905c, and eepro100, and all fail in a similar way. With 2.4.0-test3-pre7-rmk1, the 3c905's are detected and configured, but neither sends out any packets nor indicates any errors. Trying the 3Com driver instead, (and 2.2.16-rmk1) they die during configuration. The eepro100 fails as follows: eepro100.c:v1.09j-t 9/29/99 Donald Becker http://cesdis.gsfc.nasa.gov/linux/dril eepro100.c: $Revision: 1.33 $ 2000/05/24 Modified by Andrey V. Savochkin eepro100: wait_for_cmd_done timeout! .<1>eepro100: wait_for_cmd_done timeout! .<1>eepro100: wait_for_cmd_done timeout! Is there some board or backplane jumper setting that I'm missing that would cause this? -Jacob unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Tue Jul 11 19:07:45 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13C4Rc-0000fY-00 for linux-arm-archive@lists.arm.linux.org.uk; Tue, 11 Jul 2000 19:07:44 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 791FB1614F; Tue, 11 Jul 2000 20:02:47 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 11 Jul 2000 13:39:20 -0400 Received: by vger.rutgers.edu id ; Tue, 11 Jul 2000 13:39:04 -0400 Received: from aleph1.demon.co.uk ([158.152.9.127]:10255 "EHLO court2.aleph1.co.uk") by vger.rutgers.edu with ESMTP id ; Tue, 11 Jul 2000 13:38:28 -0400 Received: from chewy.aleph1.co.uk ([194.70.44.163]) by court2.aleph1.co.uk with smtp (Exim 2.05 #1) id 13C411-0006Ph-00 for linux-arm@vger.rutgers.edu; Tue, 11 Jul 2000 18:40:15 +0100 Date: Tue, 11 Jul 2000 18:40:18 +0100 (BST) From: Wookey Subject: re: Mailing lists To: armlinux list In-Reply-To: <200007101322.OAA07927@flint.arm.linux.org.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Organization: Aleph One,Cambridge, UK. Tel +44 1223 811679 X-Mailer: ANT RISCOS Marcel [ver 1.50] Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu On Mon 10 Jul, Russell King - ARM Linux Admin wrote: > I don't mean to cause offence to those people at handhelds.org or any > of the other mailing lists, but it strikes me that we're getting too > many mailing lists covering the same sort of areas > linux-7110@redhat.com > Linux on ARM7110 ? This is now basically the 'Linux on Psion PDAs' list > I'd also like these "other" mailing lists provide a clear definition of > their purpose so that it can be documented and readily available to people. I generated this description of the various lists (for our ARMlinux manual) a while back. If anyone has comments/disagrees etc please say so. It will go online shortly. Mailing lists: There are several, depending on your level of experience/area of interest. There is a mailing list specifically for people new to ARMLinux, where you are positively encouraged to ask 'stupid questions.' This is <[75]ARMLinux-newbie@lists.armlinux.org>. We recommend that all users join this list so that the community can help each other out and compare notes. To subscribe go to [file://localhost/websites/www.armlinux.org/cgi-bin/mailman/listinfo/index.html] the local copy of the site http://www.armlinux.org and fill in the form. When you have finished go on-line and submit it. Alternatively you can fill in the form directly on-line. There is also <[77]linux-arm@vger.rutgers.edu>. This is the 'main' ARMLinux list which covers ARMLinux topics not specific to ARMLinux-newbie or linux-arm-kernel. This covers all architectures that ARMLinux is used on. Users who have ceased to be 'newbies' will find this of interest. To subscribe send 'subscribe linux-arm' (in the body of the message) to <[78]majordomo@vger.rutgers.edu.> <[79]linux-arm-kernel@lists.arm.linux.org.uk> is for kernel-related discussions, generally of a technical nature. This normally covers the kernel, compilers, related tools and new hardware. If you are a Linux beginner you won't understand a word of what goes on here :-) This is the place for those interested in the grubby stuff. To subscribe send 'subscribe linux-arm-kernel' (in the body of the message) to <[80]majordomo@lists.arm.linux.org.uk> There are other lists not directly related to this distribution of ARMLinux that may nevertheless be of interest. <[81]debian-arm@lists.debian.org> relates to work on and discussion of the Debian port. In a similar vein, <[82]linux-7110@redhat.com> is concerned with the Psion 5 port of ARMLinux whilst <[83]sa1100-linux@pa.dec.com> is for those who are interested in the StrongARM 1100 Linux port (Itsy, LART, PLEB) I should of course now add handhelds.org and emdebian.org to this list, and linux-arm-announce, whose existence I had failed to notice (tut). I agree with Russell's fundamental point that too much splitting is not good, but equally I think that linux-arm and linux-arm-kernel are both quite busy. I suspect that the sa1100 list is perhaps the one that might be most appropriately re-integrated, and the linux-7110 list (which is very low traffic) could also perhaps benefit from talking more to the mainstream (eg a recent question there about a kernel oops didn't get useful resonse directly because the people who knew the answers don't read it). The other lists all have a well-enough defined purpose that I don't think integration would help. just my two pennorth. Wookey -- Aleph One Ltd, Bottisham, CAMBRIDGE, CB5 9BA, UK Tel (00 44) 1223 811679 work: http://www.aleph1.co.uk/ play: http://www.chaos.org.uk/~wookey/ unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Tue Jul 11 19:19:07 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13C4cb-0000rn-00 for linux-arm-archive@lists.arm.linux.org.uk; Tue, 11 Jul 2000 19:19:07 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 5E2941616D; Tue, 11 Jul 2000 20:11:32 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 11 Jul 2000 13:49:50 -0400 Received: by vger.rutgers.edu id ; Tue, 11 Jul 2000 13:47:35 -0400 Received: from [63.195.182.101] ([63.195.182.101]:2824 "EHLO barbados.bluemug.com") by vger.rutgers.edu with ESMTP id ; Tue, 11 Jul 2000 13:45:15 -0400 Received: from fiji.bluemug.com [192.168.50.32] (mail) by barbados.bluemug.com with esmtp (Exim 2.05 #1 (Debian)) id 13C4HM-0004Nv-00; Tue, 11 Jul 2000 10:57:08 -0700 Received: from miket by fiji.bluemug.com with local (Exim 2.05 #1 (Debian)) id 13C4HM-0001Pj-00; Tue, 11 Jul 2000 10:57:08 -0700 Date: Tue, 11 Jul 2000 10:57:08 -0700 From: Mike Touloumtzis To: Charlie Flynn Cc: Mike Touloumtzis , linux-arm@vger.rutgers.edu, handhelds@handhelds.org Subject: Re: Touch Screen Driver Generic Interface for all Linux SA11x0 platforms. Message-ID: <20000711105708.T21694@fiji.bluemug.com> References: <3962EAD8.E4DE217B@ozy.dec.com> <3969C50A.9E8C4BB6@ozy.dec.com> <20000710134727.H21694@fiji.bluemug.com> <396B2E9D.BAAC754B@ozy.dec.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <396B2E9D.BAAC754B@ozy.dec.com>; from Charlie Flynn on Wed, Jul 12, 2000 at 12:26:37AM +1000 Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu On Wed, Jul 12, 2000 at 12:26:37AM +1000, Charlie Flynn wrote: > Thanks for the reply Mike. > > I haven't come across a Digitizer before so are you saying that a > simple redesign of the TS_EVENT structure is all that is needed > to accommodate the Digitizer or does the Digitizer require other > special considerations? In other words will this spec accommodate the > Digitizer without too much modification? > A digitizer is just a touch screen input device. The Palm Pilot has a digitizer; so does the Psion Series 5. In the lingo I've been used to, digitizer + LCD == touch screen[1]. It sometimes connotes high resolution, especially WRT to the graphic artist market. My experience is mainly in Japanese consumer electronics; handwriting recognition is taken much more seriously there than in the U.S. and European markets, because everyone learns to write characters (even English ones) using a consistent stroke order, so vector handwriting recognition works very well. Unfortunately, the word "digitizer" is overloaded, and also refers to various forms of specialized A/D equipment, like ultra-high-resolution physical surface scanners, and optical scanners. But it's pretty unambiguous in the consumer electronics market; there's not a lot of overlap. The type of information you get out a digitizer varies from coarse worse-than-pixel resolution (this type might be used in a greasy-sceen supermarket kiosk) to a current peak of about 10,000 lines per inch (for high-end graphic artist drawing tablets). Handwriting recognition on consumer electronics devices is typically done using vector paths at digitizer resolution; in addition to X+Y coordinates, the following info might be available from the hardware: pressure, stylus angle, stylus height (mainly for RF devices like the Cross input pad, I think; I have no experience with this). The Jot HWR system stores a whole bunch of info per path: "The ink is stored in vectorized form (important for resizing and representation on higher resolution output devices) and currently may include the following attributes[35]: stroke order, bounding coordinates, groups of strokes, timing, pressure, stylus angle (in x and y directions), pen color (including opacity), scaling and offset, height over the digitizer surface, buttons on the pen, and pen tip type. Speed and pressure, for example, are important for signature verification, and color may be used for user identification in a multi-user environment."[2] Some of these attributes come from the hardware, while others are clearly plugged in by software and probably wouldn't play a role in a kernel API. Timing info is plugged in by software, but must be very high-precision and so should probably be handled by the kernel (by sticking a gettimeofday()-derived timestamp on input data points). Good ink display is also best done with a sub-pixel coordinate system, for the same reasons that sub-pixel sampling is good for antialiasing and other graphical effects. In writing a digitizer driver API, there are a few main things to keep in mind: -- Allow room for plenty of resolution, and don't assume pixel coords will equal digitizer coords. -- Timestamps are important because they allow pen velocity to be measured. -- Allow room for expansion to new data types in the API (for instance, pen pressure info). Translation: pad structures a little :-). I wouldn't want to try to overdesign this; that way lies X. I would at read a bunch of data sheets before trying to settle on a canonical API, though. -- Some digitizers have non-linear input systems and need input munging beyond the simple device-independant translation/rotation/deskew that calibration can provide. Most devices work fine with the equivalent of a single affine transform at most, but I know of at least one shipping touchscreen PDA/phone in Japan that essentially requires a system of linear equations to normalize coordinates, and also has two "dead zones" that must be worked around. A driver API should be clear about whether it normalizes coordinates (in which case it must be possible to feed it calibration points from a userspace app) or whether it passes raw digitizer input to higher layers (in which case those layers must have hardware-dependent code--this is the gpm approach). miket [1] Not quite--there are electromagnetic digitizers in addition to pressure sensitive ones; I wouldn't refer to them as "touch screens" even when used with an LCD. But handheld devices usually seem to be touch based. [2] http://www.amug.org/amug/sigs/newton/nanug/PenReport/Handwriting.html unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Tue Jul 11 20:11:35 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13C5RO-0001pp-00 for linux-arm-archive@lists.arm.linux.org.uk; Tue, 11 Jul 2000 20:11:34 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 6EE5F161DC; Tue, 11 Jul 2000 21:05:47 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 11 Jul 2000 14:50:24 -0400 Received: by vger.rutgers.edu id ; Tue, 11 Jul 2000 14:49:19 -0400 Received: from btamail.net.cn ([202.106.196.131]:54557 "HELO btamail.net.cn") by vger.rutgers.edu with SMTP id ; Tue, 11 Jul 2000 14:48:46 -0400 Received: from eadsmobile([202.106.211.235]) by btamail.net.cn(JetMail 2.3.1.0) with SMTP id /m0/jmail.rcv/8/jm85396ba7ec; Tue, 11 Jul 2000 19:00:21 -0000 Message-ID: <007901bfeb6a$cf3c9ce0$2e7777de@eadsmobile> From: "Eads Sun" To: , "Arm-Linux" , Subject: Again, Help on Initrd for CL-PE7212 Date: Wed, 12 Jul 2000 03:04:12 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4131.1600 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4131.1600 Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Platform: CL-EP7212, Redhat 6.2, bootloader for SA1100 & CL-EP7211 Project: porting arm-linux to CL-EP7212 Hi, Really i want to know how can i create a initrd.gz, which should download with the kernel image in order to boot the development board. The arm-linx kernel image for CL-EP7212, i have made it based on the following kernel and patch: "VERSION = 2 PATCHLEVEL = 2 SUBLEVEL = 1 EXTRAVERSION = -rmk2" ----from the main Makefile it seems healthy. i have been downloaded it via the bootloader, unfortunately, the board couldn't boot up because of without the initrd. A initrd.gz sample, i got from ftp://ftp.netwinder.org/user/b/benw/initrd.gz 35393 bytes however, it couldn't work with the arm-inux kernel image before. Well, i wonder how i can create the initrd.gz step by step. it's welcom for any other info about porting linux on CL-EP7212, thanks. Best Regards Eads Sun unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Tue Jul 11 21:04:46 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13C6Gr-0002cz-00 for linux-arm-archive@lists.arm.linux.org.uk; Tue, 11 Jul 2000 21:04:46 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 1F79116234; Tue, 11 Jul 2000 21:59:25 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 11 Jul 2000 15:45:04 -0400 Received: by vger.rutgers.edu id ; Tue, 11 Jul 2000 15:44:12 -0400 Received: from p12-robin-gui.tch.enablis.net ([194.168.180.72]:4517 "EHLO caramon.arm.linux.org.uk") by vger.rutgers.edu with ESMTP id ; Tue, 11 Jul 2000 15:42:31 -0400 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 UAA13633; Tue, 11 Jul 2000 20:53:58 +0100 Received: (from linux@localhost) by flint.arm.linux.org.uk (8.9.3/8.9.3) id UAA17293; Tue, 11 Jul 2000 20:50:58 +0100 From: Russell King - ARM Linux Admin Message-Id: <200007111950.UAA17293@flint.arm.linux.org.uk> Subject: Re: Mailing lists To: wookey@aleph1.co.uk (Wookey) Date: Tue, 11 Jul 2000 20:50:58 +0100 (BST) Cc: linux-arm@vger.rutgers.edu (armlinux list) In-Reply-To: from "Wookey" at Jul 11, 2000 06:40:18 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@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Wookey writes: > http://www.armlinux.org and fill in the form. When you have > finished go on-line and submit it. Alternatively you can fill > in the form directly on-line. Yet more splitting, that even I wasn't aware of. ;( > <[79]linux-arm-kernel@lists.arm.linux.org.uk> is for > kernel-related discussions, generally of a technical nature. > This normally covers the kernel, compilers, related tools and > new hardware. Not compilers I'm afraid. > I agree with Russell's fundamental point that too much splitting is not > good, but equally I think that linux-arm and linux-arm-kernel are both > quite busy. Please define "busy". From the linux-arm* lists combined, the maximum that I've had (not including my postings) from them in one month (April 2000) is 331 messages in 30 days. Of those, there were 161 messages on the linux-arm list. That's an total average of 11 messages a day, or 5 per day for linux-arm. Note that it normally averages 2 to 3 messages per day. This is "silent" compared with other lists such as "linux-kernel" who have 140+ messages a day, and the "mgetty" list which has about 4 per day. I just get very amused with people saying that the linux-arm* lists are busy. I'm not sure that the correct answer is to create parallel lists with the same subject area, but to have a clearly defined separation between the lists (eg, linux-arm and linux-arm-kernel). In general, the "right" splits are on subject matter, not machine type since many problems span most linux-arm machine types (eg, "how do I build a cross compiler" "does xxx work on ARM Linux" "building cross libraries" "angel boot loader" etc) and to fragment the community over these issues can only lead to poorer information. For instance, I believe that we have at least a third person announcing that they will create a site where an x86 ARM cross toolchain will be available from. However, because it is distributed across a wide number of hosts, it gets lost, and then someone else comes along and announces the same thing. Eventually we end up with some people going to one site, and someone else creating another toolchain. I have always offered to provide FTP space on the main site - in fact there has always been a set of cron scripts running which automagically mail me when stuff gets uploaded into /pub/linux/arm/incoming so that it can be moved into the appropriate area, but I've yet to see anyone take up on this. As it stands, the "community" is becoming very fragmented with little or even no communication between the parties, especially the 'armlinux.org' group who appear to keep themselves completely to themselves. This is BAD, since it will lead to decay of quality, not improvement. Oh, while we're on the subject of mailing lists, I'd like to table a motion to close down linux-arm@vger.rutgers.edu and move to linux-arm@lists.arm.linux.org.uk. The reasons for this is: 1. vger.rutgers.edu is rather overloaded now, to the point where the admins are refusing to setup new mailing lists. 2. Since Southampton Uni has finally closed my mail accounts (yay), I no longer get the administrivia mail from vger. 3. lists.arm.linux.org.uk is easier to administer, and is seen (I hope) as the central point for ARM Linux. 4. lists.arm.linux.org.uk has a faster response time than vger. That's my 2p's worth tonight. _____ |_____| ------------------------------------------------- ---+---+- | | Russell King linux@arm.linux.org.uk --- --- | | | | http://www.arm.linux.org.uk/ / / | | +-+-+ --- -+- / | THE developer of ARM Linux |+| /|\ / | | | --- | +-+-+ ------------------------------------------------- /\\\ | unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Tue Jul 11 21:11:14 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13C6N5-0002gK-00 for linux-arm-archive@lists.arm.linux.org.uk; Tue, 11 Jul 2000 21:11:13 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id C7CC91615E; Tue, 11 Jul 2000 22:05:16 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 11 Jul 2000 15:52:00 -0400 Received: by vger.rutgers.edu id ; Tue, 11 Jul 2000 15:49:54 -0400 Received: from mail.uni-greifswald.de ([141.53.8.33]:4432 "EHLO mail.uni-greifswald.de") by vger.rutgers.edu with ESMTP id ; Tue, 11 Jul 2000 15:49:30 -0400 Received: from localhost (sh990154@localhost) by mail.uni-greifswald.de (8.9.2/8.9.2) with SMTP id WAA02650; Tue, 11 Jul 2000 22:01:15 +0200 (METDST) Date: Tue, 11 Jul 2000 22:01:14 +0200 (METDST) From: "Hanske;Stefan" To: Vasant Ramasubramanian Cc: linux-arm@vger.rutgers.edu, sa1100-linux@pa.dec.com Subject: Re: SDRAM Start-up code In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu On Tue, 11 Jul 2000, Vasant Ramasubramanian wrote: > Anyone know of good data sheets/SDRAM briefs that might show in detail > waveforms expected to see during configuration and non-burst > read/writes? The processor manual should contain the pin descriptions and the hardware protokol (when which line is going high or low). At least it does in the <= ARM710 manual from ARM. unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Tue Jul 11 21:30:28 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13C6fj-0002t4-00 for linux-arm-archive@lists.arm.linux.org.uk; Tue, 11 Jul 2000 21:30:27 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id A3CCE16252; Tue, 11 Jul 2000 22:26:50 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 11 Jul 2000 16:12:49 -0400 Received: by vger.rutgers.edu id ; Tue, 11 Jul 2000 16:12:44 -0400 Received: from [38.149.17.171] ([38.149.17.171]:1927 "HELO ltc.com") by vger.rutgers.edu with SMTP id ; Tue, 11 Jul 2000 16:12:32 -0400 Received: from gw1.ltc.com (gw1.ltc.com [38.149.17.163]) by ltc.com (NTMail 3.03.0017/1.afdd) with ESMTP id ra313421 for ; Tue, 11 Jul 2000 16:28:25 -0400 Message-ID: <004b01bfeb76$36e29330$0701010a@ltc.com> From: "Bradley D. LaRonde" To: "Mike Touloumtzis" , "Charlie Flynn" Cc: "Mike Touloumtzis" , , References: <3962EAD8.E4DE217B@ozy.dec.com> <3969C50A.9E8C4BB6@ozy.dec.com> <20000710134727.H21694@fiji.bluemug.com> <396B2E9D.BAAC754B@ozy.dec.com> <20000711105708.T21694@fiji.bluemug.com> Subject: Re: [Handhelds] Re: Touch Screen Driver Generic Interface for all Linux SA11x0 platforms. Date: Tue, 11 Jul 2000 16:25:54 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu ----- Original Message ----- From: "Mike Touloumtzis" To: "Charlie Flynn" Cc: "Mike Touloumtzis" ; ; Sent: Tuesday, July 11, 2000 1:57 PM Subject: [Handhelds] Re: Touch Screen Driver Generic Interface for all Linux SA11x0 platforms. > In writing a digitizer driver API, there are a few main things to keep > in mind: > > -- Allow room for plenty of resolution, and don't assume pixel coords > will equal digitizer coords. This is another reason why I think the best thing is to just feed the raw data to userspace and divide it up there, avoiding any attempt to calibrate or smooth data in the kernel. > -- Timestamps are important because they allow pen velocity to be > measured. Agreed. Yet another reason for not munging things in the kernel. Give every point to userspace so that all timing is known. > -- Allow room for expansion to new data types in the API (for instance, > pen pressure info). Translation: pad structures a little :-). I > wouldn't want to try to overdesign this; that way lies X. I would > at read a bunch of data sheets before trying to settle on a canonical > API, though. Userspace. > -- Some digitizers have non-linear input systems and need input munging > beyond the simple device-independant translation/rotation/deskew that > calibration can provide. Most devices work fine with the equivalent > of a single affine transform at most, but I know of at least one > shipping touchscreen PDA/phone in Japan that essentially requires a > system of linear equations to normalize coordinates, and also has > two "dead zones" that must be worked around. Userspace. BTW, I've released a solved system of linear equations in my touch panel driver for microwindows. Several people got involved in the creation of those equations, and they work well. > A driver API should be clear about whether it normalizes coordinates > (in which case it must be possible to feed it calibration points from > a userspace app) or whether it passes raw digitizer input to higher > layers (in which case those layers must have hardware-dependent > code--this is the gpm approach). The kerenel should keep it's grubby fingers off the data. :-) Regards, Brad unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Tue Jul 11 21:54:12 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13C72h-00033j-00 for linux-arm-archive@lists.arm.linux.org.uk; Tue, 11 Jul 2000 21:54:11 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 75C2E16193; Tue, 11 Jul 2000 22:50:21 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 11 Jul 2000 16:37:53 -0400 Received: by vger.rutgers.edu id ; Tue, 11 Jul 2000 16:37:36 -0400 Received: from dfw7-1.relay.mail.uu.net ([199.171.54.106]:39184 "EHLO dfw7-1.relay.mail.uu.net") by vger.rutgers.edu with ESMTP id ; Tue, 11 Jul 2000 16:37:33 -0400 Received: from xedia.com by dfw7sosrv11.alter.net with SMTP (peer crosschecked as: madway.xedia.com [198.202.232.199]) id QQixkt16020; Tue, 11 Jul 2000 20:49:21 GMT Received: from tonga.xedia.com by xedia.com (4.1/SMI-4.1) id AA18913; Tue, 11 Jul 00 16:32:13 EDT Received: by tonga.xedia.com (SMI-8.6/SMI-SVR4) id QAA00458; Tue, 11 Jul 2000 16:49:19 -0400 From: Paul Koning Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <14699.34895.637086.531973@xedia.com> Date: Tue, 11 Jul 2000 16:49:19 -0400 (EDT) To: brad@ltc.com Cc: linux-arm@vger.rutgers.edu, handhelds@handhelds.org Subject: Re: [Handhelds] Re: Touch Screen Driver Generic Interface for all Linux SA11x0 platforms. References: <3962EAD8.E4DE217B@ozy.dec.com> <3969C50A.9E8C4BB6@ozy.dec.com> <20000710134727.H21694@fiji.bluemug.com> <396B2E9D.BAAC754B@ozy.dec.com> <20000711105708.T21694@fiji.bluemug.com> <004b01bfeb76$36e29330$0701010a@ltc.com> X-Mailer: VM 6.72 under 21.1 (patch 9) "Canyonlands" XEmacs Lucid Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu >>>>> "Bradley" == Bradley D LaRonde writes: >> ... Bradley> This is another reason why I think the best thing is to just Bradley> feed the raw data to userspace and divide it up there, Bradley> avoiding any attempt to calibrate or smooth data in the Bradley> kernel. I'd agree with that, provided you also get a query function that lets you discover what units are used for all those raw data items. That's a bit like X which gives you pixels (not world coordinates or millimeters or whatnot) but lets you find out how big the pixel is. (And unlike a certain other operating system which not only pretends to use inches, but then doesn't actually use the same size inches everyone else does.) >> -- Timestamps are important because they allow pen velocity to be >> measured. Bradley> Agreed. Yet another reason for not munging things in the Bradley> kernel. Give every point to userspace so that all timing is Bradley> known. I can't tell whether you meant "have the kernel timestamp every point and give the result to userspace" or "have the kernel give every point to userspace so the application can do the timestamping". The latter won't work, of course... >> -- Allow room for expansion to new data types in the API (for >> instance, pen pressure info). Translation: pad structures a >> little :-). I wouldn't want to try to overdesign this; that way >> lies X. I would at read a bunch of data sheets before trying to >> settle on a canonical API, though. Bradley> Userspace. Sure, though here in particular the need to query units is important. Also, I think you would want to linearize things, if the raw hardware has an oddball transfer function. paul unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Tue Jul 11 22:13:51 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13C7Lj-0003Pk-00 for linux-arm-archive@lists.arm.linux.org.uk; Tue, 11 Jul 2000 22:13:51 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 28E76160D6; Tue, 11 Jul 2000 23:11:14 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 11 Jul 2000 16:58:04 -0400 Received: by vger.rutgers.edu id ; Tue, 11 Jul 2000 16:57:54 -0400 Received: from [205.250.170.220] ([205.250.170.220]:3829 "EHLO xanadu.vip.ca") by vger.rutgers.edu with ESMTP id ; Tue, 11 Jul 2000 16:56:48 -0400 Date: Tue, 11 Jul 2000 17:06:44 -0400 (EDT) From: Nicolas Pitre To: "Bradley D. LaRonde" Cc: Mike Touloumtzis , Charlie Flynn , linux-arm@vger.rutgers.edu, handhelds@handhelds.org Subject: Re: [Handhelds] Re: Touch Screen Driver Generic Interface for all Linux SA11x0 platforms. In-Reply-To: <004b01bfeb76$36e29330$0701010a@ltc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu On Tue, 11 Jul 2000, Bradley D. LaRonde wrote: > ----- Original Message ----- > From: "Mike Touloumtzis" > To: "Charlie Flynn" > Cc: "Mike Touloumtzis" ; ; > > Sent: Tuesday, July 11, 2000 1:57 PM > Subject: [Handhelds] Re: Touch Screen Driver Generic Interface for all Linux > SA11x0 platforms. > > > > In writing a digitizer driver API, there are a few main things to keep > > in mind: > > > > -- Allow room for plenty of resolution, and don't assume pixel coords > > will equal digitizer coords. > > This is another reason why I think the best thing is to just feed the raw > data to userspace and divide it up there, avoiding any attempt to calibrate > or smooth data in the kernel. > > > -- Timestamps are important because they allow pen velocity to be > > measured. > > Agreed. Yet another reason for not munging things in the kernel. Give > every point to userspace so that all timing is known. You won't have reliable time stamping in user space. This has to be done at the interrupt level. Nicolas unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Tue Jul 11 22:20:04 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13C7Rk-0003Sh-00 for linux-arm-archive@lists.arm.linux.org.uk; Tue, 11 Jul 2000 22:20:04 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 40E3C16270; Tue, 11 Jul 2000 23:15:28 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 11 Jul 2000 16:51:53 -0400 Received: by vger.rutgers.edu id ; Tue, 11 Jul 2000 16:51:04 -0400 Received: from [38.149.17.171] ([38.149.17.171]:2078 "HELO ltc.com") by vger.rutgers.edu with SMTP id ; Tue, 11 Jul 2000 16:47:09 -0400 Received: from gw1.ltc.com (gw1.ltc.com [38.149.17.163]) by ltc.com (NTMail 3.03.0017/1.afdd) with ESMTP id va313425 for ; Tue, 11 Jul 2000 17:03:19 -0400 Message-ID: <00e001bfeb7b$16e19310$0701010a@ltc.com> From: "Bradley D. LaRonde" To: "Paul Koning" Cc: , References: <3962EAD8.E4DE217B@ozy.dec.com><3969C50A.9E8C4BB6@ozy.dec.com><20000710134727.H21694@fiji.bluemug.com><396B2E9D.BAAC754B@ozy.dec.com><20000711105708.T21694@fiji.bluemug.com><004b01bfeb76$36e29330$0701010a@ltc.com> <14699.34895.637086.531973@xedia.com> Subject: Re: [Handhelds] Re: Touch Screen Driver Generic Interface for all Linux SA11x0 platforms. Date: Tue, 11 Jul 2000 17:00:48 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu ----- Original Message ----- From: "Paul Koning" To: Cc: ; Sent: Tuesday, July 11, 2000 4:49 PM Subject: Re: [Handhelds] Re: Touch Screen Driver Generic Interface for all Linux SA11x0 platforms. > >>>>> "Bradley" == Bradley D LaRonde writes: > > >> ... > > Bradley> This is another reason why I think the best thing is to just > Bradley> feed the raw data to userspace and divide it up there, > Bradley> avoiding any attempt to calibrate or smooth data in the > Bradley> kernel. > > I'd agree with that, provided you also get a query function that lets > you discover what units are used for all those raw data items. That's > a bit like X which gives you pixels (not world coordinates or > millimeters or whatnot) but lets you find out how big the pixel is. > (And unlike a certain other operating system which not only pretends to > use inches, but then doesn't actually use the same size inches > everyone else does.) No, I mean send raw, unitless data to userspace. > >> -- Timestamps are important because they allow pen velocity to be > >> measured. > > Bradley> Agreed. Yet another reason for not munging things in the > Bradley> kernel. Give every point to userspace so that all timing is > Bradley> known. > > I can't tell whether you meant "have the kernel timestamp every point > and give the result to userspace" or "have the kernel give every point > to userspace so the application can do the timestamping". > > The latter won't work, of course... The touch panel that I work with takes samples at regular intervals. If all of those samples are delivered to userspace, then you can tell the timing of data relative to other data, but not the absolute timing. I suppose the kernel driver could put an absolute timestamp on every data point, but I can't offhand see the usefullness in that, and it certainly would eat kernel/userspace bandwidth. What would you need to compare any absolute time against? > >> -- Allow room for expansion to new data types in the API (for > >> instance, pen pressure info). Translation: pad structures a > >> little :-). I wouldn't want to try to overdesign this; that way > >> lies X. I would at read a bunch of data sheets before trying to > >> settle on a canonical API, though. > > Bradley> Userspace. > > Sure, though here in particular the need to query units is important. > Also, I think you would want to linearize things, if the raw hardware > has an oddball transfer function. I'm saying that I think that all interpretation and distribution of the data should be done in userspace, where it can be more easily engineered, debugged, and extended. Regards, Brad unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Tue Jul 11 22:36:44 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13C7hr-0003bx-00 for linux-arm-archive@lists.arm.linux.org.uk; Tue, 11 Jul 2000 22:36:44 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 48B6B15DEF; Tue, 11 Jul 2000 23:36:48 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 11 Jul 2000 17:23:59 -0400 Received: by vger.rutgers.edu id ; Tue, 11 Jul 2000 17:23:24 -0400 Received: from ns1.crynwr.com ([192.203.178.14]:1253 "HELO ns.crynwr.com") by vger.rutgers.edu with SMTP id ; Tue, 11 Jul 2000 17:23:16 -0400 Received: (qmail 18603 invoked from network); 11 Jul 2000 21:35:11 -0000 Received: from desk.crynwr.com (qmailr@206.150.82.98) by ns1.crynwr.com with SMTP; 11 Jul 2000 21:35:11 -0000 Received: (qmail 4232 invoked by uid 501); 11 Jul 2000 21:35:10 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 11 Jul 2000 17:35:09 -0400 (EDT) From: Russ Nelson To: linux-arm@vger.rutgers.edu, handhelds@handhelds.org Subject: Re: [Handhelds] Re: Touch Screen Driver Generic Interface for all Linux SA11x0 platforms. In-Reply-To: References: <004b01bfeb76$36e29330$0701010a@ltc.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14699.36836.422617.99497@desk.crynwr.com> X-Face: $K'YURj"g6ImvqTS_=]8)gqh!5;ElY<[.Rao%j8r+]iUfE{%|v%F<=mcq<6l{K=~mf&#:?" nslS]U~|x{2V=Eex_I#"9K~9)>?m7Lm={(j_&)SX~fzg&ST~P%QUhc{1p]c3@Zn1u*PZlkHM**X^vV l>GkB5y^Kz%w5p~^uDue]hL&ke,N;+Q > Agreed. Yet another reason for not munging things in the kernel. Give > > every point to userspace so that all timing is known. > > You won't have reliable time stamping in user space. This has to be done > at the interrupt level. Some people are assuming that the digitizer is spitting out points at a constant interval. Others are assuming that the digitizer is only spitting out deltas. -- -russ nelson http://russnelson.com Crynwr sells support for free software | PGPok | 521 Pleasant Valley Rd. | +1 315 268 1925 voice | Is Unix compatible with Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | Linux? unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Tue Jul 11 23:16:46 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13C8Kc-00048G-00 for linux-arm-archive@lists.arm.linux.org.uk; Tue, 11 Jul 2000 23:16:46 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 5656615EF0; Wed, 12 Jul 2000 00:14:57 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 11 Jul 2000 17:59:34 -0400 Received: by vger.rutgers.edu id ; Tue, 11 Jul 2000 17:57:55 -0400 Received: from ns1.crynwr.com ([192.203.178.14]:1738 "HELO ns.crynwr.com") by vger.rutgers.edu with SMTP id ; Tue, 11 Jul 2000 17:57:16 -0400 Received: (qmail 20072 invoked from network); 11 Jul 2000 22:09:35 -0000 Received: from desk.crynwr.com (qmailr@206.150.82.98) by ns1.crynwr.com with SMTP; 11 Jul 2000 22:09:35 -0000 Received: (qmail 4626 invoked by uid 501); 11 Jul 2000 22:09:30 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 11 Jul 2000 18:09:28 -0400 (EDT) From: "Russ Nelson" To: , Subject: Re: [Handhelds] Re: Touch Screen Driver Generic Interface for allLinux SA11x0 platforms. In-Reply-To: <012101bfeb83$e4da7b30$0701010a@ltc.com> References: <004b01bfeb76$36e29330$0701010a@ltc.com> <14699.36836.422617.99497@desk.crynwr.com> <012101bfeb83$e4da7b30$0701010a@ltc.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14699.39633.606896.137421@desk.crynwr.com> X-Face: $K'YURj"g6ImvqTS_=]8)gqh!5;ElY<[.Rao%j8r+]iUfE{%|v%F<=mcq<6l{K=~mf&#:?" nslS]U~|x{2V=Eex_I#"9K~9)>?m7Lm={(j_&)SX~fzg&ST~P%QUhc{1p]c3@Zn1u*PZlkHM**X^vV l>GkB5y^Kz%w5p~^uDue]hL&ke,N;+Q > Some people are assuming that the digitizer is spitting out points at > > a constant interval. Others are assuming that the digitizer is only > > spitting out deltas. > > Yup, I'm a constant interval assumer. :-) > > To all: is that safe to assume? Is there touch panel hardware out there > that won't do this? It's easier to generate deltas with a timestamp than it is to generate constant interval data, if you're given the "wrong" thing. -- -russ nelson http://russnelson.com Crynwr sells support for free software | PGPok | 521 Pleasant Valley Rd. | +1 315 268 1925 voice | Is Unix compatible with Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | Linux? unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Tue Jul 11 23:31:08 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13C8YW-0004DE-00 for linux-arm-archive@lists.arm.linux.org.uk; Tue, 11 Jul 2000 23:31:08 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id E62DD15F2D; Wed, 12 Jul 2000 00:25:55 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 11 Jul 2000 18:13:28 -0400 Received: by vger.rutgers.edu id ; Tue, 11 Jul 2000 17:51:08 -0400 Received: from [38.149.17.171] ([38.149.17.171]:2329 "HELO ltc.com") by vger.rutgers.edu with SMTP id ; Tue, 11 Jul 2000 17:50:10 -0400 Received: from gw1.ltc.com (gw1.ltc.com [38.149.17.163]) by ltc.com (NTMail 3.03.0017/1.afdd) with ESMTP id za313429 for ; Tue, 11 Jul 2000 18:06:20 -0400 Message-ID: <012101bfeb83$e4da7b30$0701010a@ltc.com> From: "Bradley D. LaRonde" To: "Russ Nelson" , , References: <004b01bfeb76$36e29330$0701010a@ltc.com> <14699.36836.422617.99497@desk.crynwr.com> Subject: Re: [Handhelds] Re: Touch Screen Driver Generic Interface for allLinux SA11x0 platforms. Date: Tue, 11 Jul 2000 18:03:50 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu ----- Original Message ----- From: "Russ Nelson" To: ; Sent: Tuesday, July 11, 2000 5:35 PM Subject: Re: [Handhelds] Re: Touch Screen Driver Generic Interface for allLinux SA11x0 platforms. > Nicolas Pitre writes: > > > Agreed. Yet another reason for not munging things in the kernel. Give > > > every point to userspace so that all timing is known. > > > > You won't have reliable time stamping in user space. This has to be done > > at the interrupt level. > > Some people are assuming that the digitizer is spitting out points at > a constant interval. Others are assuming that the digitizer is only > spitting out deltas. Yup, I'm a constant interval assumer. :-) To all: is that safe to assume? Is there touch panel hardware out there that won't do this? Regards, Brad unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Tue Jul 11 23:37:12 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13C8eO-0004Gg-00 for linux-arm-archive@lists.arm.linux.org.uk; Tue, 11 Jul 2000 23:37:12 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 4E70F15F47; Wed, 12 Jul 2000 00:33:17 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 11 Jul 2000 18:19:03 -0400 Received: by vger.rutgers.edu id ; Tue, 11 Jul 2000 18:18:18 -0400 Received: from [205.250.170.220] ([205.250.170.220]:3915 "EHLO xanadu.vip.ca") by vger.rutgers.edu with ESMTP id ; Tue, 11 Jul 2000 18:17:40 -0400 Date: Tue, 11 Jul 2000 18:27:26 -0400 (EDT) From: Nicolas Pitre To: "Bradley D. LaRonde" Cc: Paul Koning , linux-arm@vger.rutgers.edu, handhelds@handhelds.org Subject: Re: [Handhelds] Re: Touch Screen Driver Generic Interface for all Linux SA11x0 platforms. In-Reply-To: <00e001bfeb7b$16e19310$0701010a@ltc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu On Tue, 11 Jul 2000, Bradley D. LaRonde wrote: > I'm saying that I think that all interpretation and distribution of the data > should be done in userspace, where it can be more easily engineered, > debugged, and extended. The extreme stand on user space is not always so good. At some point you need a common base so the job doesn't have to be duplicated for every and all clients. That's the role of the kernel to present a coherent view of all peripherals types to user space apps, wether is is a sound card, a framebuffer device, a touchscreen panel, etc. Otherwise, we would already manage ethernet interfaces in user space, IDE chipsets, etc. The "all in the kernel" approach isn't good either, far from it. However a good balance is required for not duplicating the work for all user space clients. Since the kernel is the common point of communication for all hardware components and all software apps, we need to use it in order not to waste too much time on skattered user space maintenance. Thus the need for a well defined kernel interface. A good compromise might involve a common basic interface for presenting data that all types of touchscreens can provide, with the possibility for a user space app that wants more to turn the driver into a raw mode. The same principle is currently implemented with termios (think of cooked vs raw modes), keyboards (translated, keycodes or scancodes), etc. This way, all windowing systems using the basic interface would work automagically without modifications whenever a new touchscreen driver is produced which is not the case with the "all in user space" approach. What I would change from the original proposition is the following: For each TS events, a struct with the x, y, pressure coordinate and time stamp be returned with int values rather than short. This allows for a much larger scale while limiting alignment and size problems on architectures that doesn't support shorts naturally. Next, some ioctls that allows the client to probe for the x scale, y scale and pressure scale allowed by the hardware. Maybe also probe for the type of coordinates i.e. linear, polar or whatever could be common usage. If a certain hardware doesn't do sane coordinate and requires a special transform then it would have to be done in the driver so it could fit into the nearest standard coordinate type -- just like different color modes and representations are presented through the generic framebuffer interface. Probably the driver would benifit from an isteresis processing which parameters are configurable from user space, based on queried scale ranges. This has to be done in the kernel too so the user space client is not waken up unnecessary by the noise. But all interpretation of coordinates in order to match screen pixels, calibration, etc. has to be done in user space since that's what likely to change meaning from one application to another. Nicolas unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Tue Jul 11 23:37:51 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13C8f1-0004H5-00 for linux-arm-archive@lists.arm.linux.org.uk; Tue, 11 Jul 2000 23:37:51 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 5F58915EF5; Wed, 12 Jul 2000 00:37:36 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 11 Jul 2000 18:24:53 -0400 Received: by vger.rutgers.edu id ; Tue, 11 Jul 2000 18:24:44 -0400 Received: from [38.149.17.171] ([38.149.17.171]:2471 "HELO ltc.com") by vger.rutgers.edu with SMTP id ; Tue, 11 Jul 2000 18:24:30 -0400 Received: from gw1.ltc.com (gw1.ltc.com [38.149.17.163]) by ltc.com (NTMail 3.03.0017/1.afdd) with ESMTP id ea313434 for ; Tue, 11 Jul 2000 18:40:39 -0400 Message-ID: <017601bfeb88$b05a22c0$0701010a@ltc.com> From: "Bradley D. LaRonde" To: "Russ Nelson" , , References: <004b01bfeb76$36e29330$0701010a@ltc.com><14699.36836.422617.99497@desk.crynwr.com><012101bfeb83$e4da7b30$0701010a@ltc.com> <14699.39633.606896.137421@desk.crynwr.com> Subject: Re: [Handhelds] Re: Touch Screen Driver Generic Interface for allLinux SA11x0 platforms. Date: Tue, 11 Jul 2000 18:38:09 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu ----- Original Message ----- From: "Russ Nelson" To: ; Sent: Tuesday, July 11, 2000 6:09 PM Subject: Re: [Handhelds] Re: Touch Screen Driver Generic Interface for allLinux SA11x0 platforms. > Bradley D. LaRonde writes: > > > Some people are assuming that the digitizer is spitting out points at > > > a constant interval. Others are assuming that the digitizer is only > > > spitting out deltas. > > > > Yup, I'm a constant interval assumer. :-) > > > > To all: is that safe to assume? Is there touch panel hardware out there > > that won't do this? > > It's easier to generate deltas with a timestamp than it is to generate > constant interval data, if you're given the "wrong" thing. Ugh, I can just see it now, people taking a least-common-demoninator approach because it adapts better to hypothetical delta-spewing hardware. Regards, Brad unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Tue Jul 11 23:46:23 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13C8nH-0004Nz-00 for linux-arm-archive@lists.arm.linux.org.uk; Tue, 11 Jul 2000 23:46:23 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 2C83015EF0; Wed, 12 Jul 2000 00:45:39 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 11 Jul 2000 18:31:38 -0400 Received: by vger.rutgers.edu id ; Tue, 11 Jul 2000 18:30:52 -0400 Received: from [38.149.17.171] ([38.149.17.171]:2501 "HELO ltc.com") by vger.rutgers.edu with SMTP id ; Tue, 11 Jul 2000 18:29:42 -0400 Received: from gw1.ltc.com (gw1.ltc.com [38.149.17.163]) by ltc.com (NTMail 3.03.0017/1.afdd) with ESMTP id ia313438 for ; Tue, 11 Jul 2000 18:45:46 -0400 Message-ID: <018601bfeb89$672a8530$0701010a@ltc.com> From: "Bradley D. LaRonde" To: "Nicolas Pitre" Cc: "Paul Koning" , , References: Subject: Re: [Handhelds] Re: Touch Screen Driver Generic Interface for allLinux SA11x0 platforms. Date: Tue, 11 Jul 2000 18:43:16 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu ----- Original Message ----- From: "Nicolas Pitre" To: "Bradley D. LaRonde" Cc: "Paul Koning" ; ; Sent: Tuesday, July 11, 2000 6:27 PM Subject: Re: [Handhelds] Re: Touch Screen Driver Generic Interface for allLinux SA11x0 platforms. > On Tue, 11 Jul 2000, Bradley D. LaRonde wrote: > > > I'm saying that I think that all interpretation and distribution of the data > > should be done in userspace, where it can be more easily engineered, > > debugged, and extended. > > The extreme stand on user space is not always so good. At some point you > need a common base so the job doesn't have to be duplicated for every and > all clients. Just because it isn't in the kernel doesn't mean there can't be a comon base. Share libs and userspace processes can also do abstraction. Regards, Brad unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Tue Jul 11 23:59:50 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13C90I-0004b7-00 for linux-arm-archive@lists.arm.linux.org.uk; Tue, 11 Jul 2000 23:59:50 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 3A67015EAD; Wed, 12 Jul 2000 00:57:00 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 11 Jul 2000 18:43:01 -0400 Received: by vger.rutgers.edu id ; Tue, 11 Jul 2000 18:41:33 -0400 Received: from [212.219.8.163] ([212.219.8.163]:1564 "HELO inkvine.fluff.org") by vger.rutgers.edu with SMTP id ; Tue, 11 Jul 2000 18:40:31 -0400 Received: from localhost (localhost [127.0.0.1]) by inkvine.fluff.org (Postfix) with ESMTP id 80E0446820 for ; Tue, 11 Jul 2000 23:52:12 +0100 (BST) Date: Tue, 11 Jul 2000 23:52:12 +0100 (BST) From: Chris Rutter Reply-To: chris@fluff.org To: ARM Linux mailing list Subject: Re: Mailing lists In-Reply-To: <200007111950.UAA17293@flint.arm.linux.org.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu > For instance, I believe that we have at least a third person announcing > that they will create a site where an x86 ARM cross toolchain will be > available from. However, because it is distributed across a wide number > of hosts, it gets lost, and then someone else comes along and announces > the same thing. Eventually we end up with some people going to one site, > and someone else creating another toolchain. If you mean the emdebian.org people, they are pretty accurately targeting these problems with coordination from some ARM Linux types; I don't think at all that this is how their effort will end up. > I have always offered to provide FTP space on the main site - in fact > there has always been a set of cron scripts running which automagically > mail me when stuff gets uploaded into /pub/linux/arm/incoming so that > it can be moved into the appropriate area, but I've yet to see anyone > take up on this. I think terming ftp.arm.linux.org.uk `the main site' is a little contentious; ftp.netwinder.org (amongst others) contains at least as much data important to the Linux/ARM project. So eventually, I hope, will ftp.armlinux.org. > As it stands, the "community" is becoming very fragmented with little or > even no communication between the parties, The Linux/ARM project is, certainly in places, stricken with this problem; projects proceed in their relatively insulated autonomous groups, not, I think, owing to any sort of unsociability, but just a lack of conscious organisation at a higher level: it is a question that needs thought as to whether and what kind of higher organisation is desirable. armlinux.org is, incidentally, a part of my effort to remedy this sort of problem. > especially the 'armlinux.org' > group who appear to keep themselves completely to themselves. This is > BAD, since it will lead to decay of quality, not improvement. armlinux.org really is little more than a WHOIS record at the moment: this accusation is a paranoid one. There is no `armlinux.org group' or mafia; it is a domain name (and collection of i386/ARM machines) intended to help foster open development, communcation, and web/FTP/shell space for whoever might need it. c. unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Wed Jul 12 01:17:18 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13CADG-00064y-00 for linux-arm-archive@lists.arm.linux.org.uk; Wed, 12 Jul 2000 01:17:18 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id EEAB015FD8; Wed, 12 Jul 2000 02:17:23 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 11 Jul 2000 20:04:52 -0400 Received: by vger.rutgers.edu id ; Tue, 11 Jul 2000 20:04:45 -0400 Received: from [63.195.182.101] ([63.195.182.101]:3395 "EHLO barbados.bluemug.com") by vger.rutgers.edu with ESMTP id ; Tue, 11 Jul 2000 20:04:31 -0400 Received: from fiji.bluemug.com [192.168.50.32] (mail) by barbados.bluemug.com with esmtp (Exim 2.05 #1 (Debian)) id 13CABj-0004ZB-00; Tue, 11 Jul 2000 17:15:43 -0700 Received: from miket by fiji.bluemug.com with local (Exim 2.05 #1 (Debian)) id 13CABh-0002JF-00; Tue, 11 Jul 2000 17:15:41 -0700 Date: Tue, 11 Jul 2000 17:15:41 -0700 From: Mike Touloumtzis To: "Bradley D. LaRonde" Cc: Mike Touloumtzis , Charlie Flynn , linux-arm@vger.rutgers.edu, handhelds@handhelds.org Subject: Re: [Handhelds] Re: Touch Screen Driver Generic Interface for all Linux SA11x0 platforms. Message-ID: <20000711171541.Y21694@fiji.bluemug.com> References: <3962EAD8.E4DE217B@ozy.dec.com> <3969C50A.9E8C4BB6@ozy.dec.com> <20000710134727.H21694@fiji.bluemug.com> <396B2E9D.BAAC754B@ozy.dec.com> <20000711105708.T21694@fiji.bluemug.com> <004b01bfeb76$36e29330$0701010a@ltc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <004b01bfeb76$36e29330$0701010a@ltc.com>; from Bradley D. LaRonde on Tue, Jul 11, 2000 at 04:25:54PM -0400 Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu In case it wasn't clear from my message--I'm in favor of passing raw digitizer data to userspace, but with kernel-generated timestamps for accuracy (without that, even the amount of jitter generated by interrupt latency could hurt measurements). Most digitizers use regular sampling intervals, but I have used some that don't (including ones that can't generate interrupts and have to be polled by the OS--yuck!). miket unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Wed Jul 12 02:21:00 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13CBCu-0006vq-00 for linux-arm-archive@lists.arm.linux.org.uk; Wed, 12 Jul 2000 02:21:00 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 5D7C415FEC; Wed, 12 Jul 2000 03:21:06 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 11 Jul 2000 21:08:24 -0400 Received: by vger.rutgers.edu id ; Tue, 11 Jul 2000 21:08:18 -0400 Received: from ns1.crynwr.com ([192.203.178.14]:1540 "HELO ns.crynwr.com") by vger.rutgers.edu with SMTP id ; Tue, 11 Jul 2000 21:04:37 -0400 Received: (qmail 28117 invoked from network); 12 Jul 2000 01:17:05 -0000 Received: from desk.crynwr.com (qmailr@206.150.82.98) by ns1.crynwr.com with SMTP; 12 Jul 2000 01:17:05 -0000 Received: (qmail 6802 invoked by uid 501); 12 Jul 2000 01:17:03 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 11 Jul 2000 21:17:03 -0400 (EDT) From: "Russ Nelson" , To: , Subject: Re: [Handhelds] Re: Touch Screen Driver Generic Interface for allLinux SA11x0 platforms. In-Reply-To: <017601bfeb88$b05a22c0$0701010a@ltc.com> References: <004b01bfeb76$36e29330$0701010a@ltc.com> <14699.36836.422617.99497@desk.crynwr.com> <012101bfeb83$e4da7b30$0701010a@ltc.com> <14699.39633.606896.137421@desk.crynwr.com> <017601bfeb88$b05a22c0$0701010a@ltc.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14699.50691.705627.865757@desk.crynwr.com> X-Face: $K'YURj"g6ImvqTS_=]8)gqh!5;ElY<[.Rao%j8r+]iUfE{%|v%F<=mcq<6l{K=~mf&#:?" nslS]U~|x{2V=Eex_I#"9K~9)>?m7Lm={(j_&)SX~fzg&ST~P%QUhc{1p]c3@Zn1u*PZlkHM**X^vV l>GkB5y^Kz%w5p~^uDue]hL&ke,N;+Q > It's easier to generate deltas with a timestamp than it is to generate > > constant interval data, if you're given the "wrong" thing. > > Ugh, I can just see it now, people taking a least-common-demoninator > approach because it adapts better to hypothetical delta-spewing hardware. How are mice hypothetical? You lose nothing by compressing your data stream into "and I saw the same thing for N intervals until I saw this". You *do* avoid context switches and kernel/userspace copying, which are relatively expensive operations. Remember: every electron has to get pushed around by your battery. -- -russ nelson http://russnelson.com Crynwr sells support for free software | PGPok | 521 Pleasant Valley Rd. | +1 315 268 1925 voice | Is Unix compatible with Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | Linux? unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Wed Jul 12 02:49:53 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13CBer-0007Ji-00 for linux-arm-archive@lists.arm.linux.org.uk; Wed, 12 Jul 2000 02:49:53 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 20E2116059; Wed, 12 Jul 2000 03:49:59 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 11 Jul 2000 21:36:46 -0400 Received: by vger.rutgers.edu id ; Tue, 11 Jul 2000 21:34:57 -0400 Received: from [38.149.17.171] ([38.149.17.171]:3152 "HELO ltc.com") by vger.rutgers.edu with SMTP id ; Tue, 11 Jul 2000 21:34:26 -0400 Received: from gw1.ltc.com (gw1.ltc.com [38.149.17.163]) by ltc.com (NTMail 3.03.0017/1.afdd) with ESMTP id ma313442 for ; Tue, 11 Jul 2000 21:50:36 -0400 Message-ID: <027501bfeba3$39a2cb30$0701010a@ltc.com> From: "Bradley D. LaRonde" To: , References: <004b01bfeb76$36e29330$0701010a@ltc.com><14699.36836.422617.99497@desk.crynwr.com><012101bfeb83$e4da7b30$0701010a@ltc.com><14699.39633.606896.137421@desk.crynwr.com><017601bfeb88$b05a22c0$0701010a@ltc.com> <14699.50691.705627.865757@desk.crynwr.com> Subject: Re: [Handhelds] Re: Touch Screen Driver Generic Interface for allLinux SA11x0 platforms. Date: Tue, 11 Jul 2000 21:48:06 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu ----- Original Message ----- From: "Russ Nelson" To: ; Sent: Tuesday, July 11, 2000 9:17 PM Subject: Re: [Handhelds] Re: Touch Screen Driver Generic Interface for allLinux SA11x0 platforms. > Bradley D. LaRonde writes: > > > It's easier to generate deltas with a timestamp than it is to generate > > > constant interval data, if you're given the "wrong" thing. > > > > Ugh, I can just see it now, people taking a least-common-demoninator > > approach because it adapts better to hypothetical delta-spewing hardware. > > How are mice hypothetical? I know mice are delta beasts. I was talking about touch panels. > You lose nothing by compressing your data > stream into "and I saw the same thing for N intervals until I saw > this". You *do* avoid context switches and kernel/userspace copying, > which are relatively expensive operations. Remember: every electron > has to get pushed around by your battery. I agree with you in principle, but in practice, a touch panel data stream fluctuates enough so that this simple compression method doesn't buy you much at all except more electrons running around trying to figure out if they should (de)compress or not using that lonely extra code we've chucked into both the kernel and userland side, but practically always getting disappointed. And I suppose someone will say "then put some hysteresis and/or noise filtering in the kernel driver". So now whenever the user holds his pen perfectly still on the touch panel, all our extra code gets to do it's dance. :-) Regards, Brad unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Wed Jul 12 03:16:23 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13CC4V-0007mU-00 for linux-arm-archive@lists.arm.linux.org.uk; Wed, 12 Jul 2000 03:16:23 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 0A3F016006; Wed, 12 Jul 2000 04:16:30 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 11 Jul 2000 22:03:36 -0400 Received: by vger.rutgers.edu id ; Tue, 11 Jul 2000 22:03:30 -0400 Received: from tlug.sinica.edu.tw ([140.109.13.42]:2482 "EHLO linux.org.tw") by vger.rutgers.edu with ESMTP id ; Tue, 11 Jul 2000 22:03:17 -0400 Received: from localhost (chester@localhost) by linux.org.tw (8.9.3/8.9.3) with ESMTP id KAA13848; Wed, 12 Jul 2000 10:17:04 +0800 Date: Wed, 12 Jul 2000 10:17:04 +0800 (CST) From: To: Eads Sun Cc: lart@lart.tudelft.nl, Arm-Linux , linux-7110@redhat.com Subject: Re: Again, Help on Initrd for CL-PE7212 In-Reply-To: <007901bfeb6a$cf3c9ce0$2e7777de@eadsmobile> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Please don't cross post your mail,and look at linux/Document/ramdisk.txt first. You will got what you want. On Wed, 12 Jul 2000, Eads Sun wrote: > > Platform: CL-EP7212, Redhat 6.2, bootloader for SA1100 & CL-EP7211 > Project: porting arm-linux to CL-EP7212 > > > Hi, > > Really i want to know how can i create a initrd.gz, which should download > with the kernel image in order to boot the development board. > > > The arm-linx kernel image for CL-EP7212, i have made it based on the > following kernel and patch: > > "VERSION = 2 > PATCHLEVEL = 2 > SUBLEVEL = 1 > EXTRAVERSION = -rmk2" ----from the main Makefile > > it seems healthy. > > i have been downloaded it via the bootloader, unfortunately, the board > couldn't boot up because of without the initrd. > > A initrd.gz sample, i got from > ftp://ftp.netwinder.org/user/b/benw/initrd.gz 35393 bytes > > however, it couldn't work with the arm-inux kernel image before. > > Well, i wonder how i can create the initrd.gz step by step. > > > it's welcom for any other info about porting linux on CL-EP7212, thanks. > > > > Best Regards > > Eads Sun > > -- > To unsubscribe from this list: send the line "unsubscribe lart" in > the body of a message to majordomo@lart.tudelft.nl > Please read the LART FAQ at http://www.lart.tudelft.nl/faq.php3 > unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Wed Jul 12 09:37:19 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13CI18-0004Xd-00 for linux-arm-archive@lists.arm.linux.org.uk; Wed, 12 Jul 2000 09:37:18 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 71AA115D4B; Wed, 12 Jul 2000 10:37:25 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Wed, 12 Jul 2000 04:24:45 -0400 Received: by vger.rutgers.edu id ; Wed, 12 Jul 2000 04:24:31 -0400 Received: from [206.103.12.152] ([206.103.12.152]:5961 "EHLO nimbus.ee.iitm.ernet.in") by vger.rutgers.edu with ESMTP id ; Wed, 12 Jul 2000 04:24:15 -0400 Received: from astra.ee.iitm.ernet.in (root@astra [144.16.244.8]) by nimbus.ee.iitm.ernet.in (8.8.7/8.8.7) with ESMTP id OAA29293 for ; Wed, 12 Jul 2000 14:08:21 +0530 Received: from localhost (saran@localhost) by astra.ee.iitm.ernet.in (8.9.3/8.8.7) with ESMTP id OAA04030 for ; Wed, 12 Jul 2000 14:08:21 +0530 Date: Wed, 12 Jul 2000 14:08:21 +0530 (IST) From: "J.Saravanan" To: arm processor Subject: about gdb.. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Hi, can anyone tell me what `rdi' actually does. I'm working with arm clps7500fe evaluation board. when I try.. (gdb)target rdi /dev/ttyS0 it gives error message as.. can not reset the target.Try reset by pressing the reset button. thanx, saran unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Wed Jul 12 10:37:44 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13CIxc-0005RP-00 for linux-arm-archive@lists.arm.linux.org.uk; Wed, 12 Jul 2000 10:37:44 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id BCF9C15DD7; Wed, 12 Jul 2000 11:33:14 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Wed, 12 Jul 2000 05:20:17 -0400 Received: by vger.rutgers.edu id ; Wed, 12 Jul 2000 05:20:02 -0400 Received: from [202.104.32.245] ([202.104.32.245]:51177 "HELO 21cn.com") by vger.rutgers.edu with SMTP id ; Wed, 12 Jul 2000 05:19:50 -0400 Received: from =?ISO-8859-1?Q?=CB=E5=C1=A2=CC=CE([202.102.146.181]?=) by 21cn.com(JetMail 2.5.3.0) with SMTP id jm6396c4243; Wed, 12 Jul 2000 09:31:11 -0000 Date: Wed, 12 Jul 2000 17:34:3 +0800 From: huang To: linux-arm@vger.rutgers.edu Subject: error when mount NFS on assabet X-mailer: FoxMail 3.0 beta 2 [cn] Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <20000712091955Z156856-29734+281@vger.rutgers.edu> Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu i use linux2.4.0-test2-ac1-rmk2-np3,the ramdisk i downloaded it from CMU,http://www.cs.cmu.edu/~wearable/software/ramdisks/ramdisk_pcmcia.gz. and change the modules in the ramdisk. when i download the image to the assabet,run "ifconfig" ,i only can find the eth0 ,there is not lo. and it can not ping other PC, if i run " ifconfig eth0 down " and "ifconfig eth0 192.xxx.xxx.xxx.. netmask 255.255.0.0 broadcast 192.xxx.xxx.xxx." "ifconfig lo 127.0.0.1",then i can ping other PC, but when run "ping 127.0.0.1" it give this message 64 bytes from 127.0.0.1 :icmp_seq=xxx ttl=255 tim=0.4ms warning: unkonwn ICMP packet received(not echo-reply) ping itself also display the message like above. when i mount NFS ,it display this message. nfs warning:mount wersion older than kernel portmap:server localhost not respending, time out. lockd_up:makesock failed,error=-5 i have changed the /etc/pcmcia/network.opts in the ramdisk. Could anyone tell me why? thanks huang huang_ch@21cn.com unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Wed Jul 12 15:20:35 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13CNNL-0001R8-00 for linux-arm-archive@lists.arm.linux.org.uk; Wed, 12 Jul 2000 15:20:35 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id BFCE815DD8; Wed, 12 Jul 2000 16:15:58 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Wed, 12 Jul 2000 10:02:15 -0400 Received: by vger.rutgers.edu id ; Wed, 12 Jul 2000 10:00:48 -0400 Received: from dfw7-1.relay.mail.uu.net ([199.171.54.106]:35633 "EHLO dfw7-1.relay.mail.uu.net") by vger.rutgers.edu with ESMTP id ; Wed, 12 Jul 2000 10:00:25 -0400 Received: from xedia.com by dfw7sosrv11.alter.net with SMTP (peer crosschecked as: madway.xedia.com [198.202.232.199]) id QQixnk27863; Wed, 12 Jul 2000 14:12:27 GMT Received: from tonga.xedia.com by xedia.com (4.1/SMI-4.1) id AA27155; Wed, 12 Jul 00 10:08:36 EDT Received: by tonga.xedia.com (SMI-8.6/SMI-SVR4) id KAA01692; Wed, 12 Jul 2000 10:12:26 -0400 From: Paul Koning Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <14700.31946.403936.324861@xedia.com> Date: Wed, 12 Jul 2000 10:12:26 -0400 (EDT) To: brad@ltc.com Cc: rn-handhelds@crynwr.com, linux-arm@vger.rutgers.edu, handhelds@handhelds.org Subject: Re: [Handhelds] Re: Touch Screen Driver Generic Interface for allLinux SA11x0 platforms. References: <004b01bfeb76$36e29330$0701010a@ltc.com> <14699.36836.422617.99497@desk.crynwr.com> <012101bfeb83$e4da7b30$0701010a@ltc.com> X-Mailer: VM 6.72 under 21.1 (patch 9) "Canyonlands" XEmacs Lucid Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu >>>>> "Bradley" == Bradley D LaRonde writes: >> Some people are assuming that the digitizer is spitting out points >> at a constant interval. Others are assuming that the digitizer is >> only spitting out deltas. Bradley> Yup, I'm a constant interval assumer. :-) Bradley> To all: is that safe to assume? Is there touch panel Bradley> hardware out there that won't do this? I think so. Furthermore, passing only non-zero deltas across the kernel/user boundary is more efficient. Those boundary crossings are very efficient and doing one every millisecond or so is not particularly desirable. paul unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Wed Jul 12 16:11:27 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13COAZ-0002C1-00 for linux-arm-archive@lists.arm.linux.org.uk; Wed, 12 Jul 2000 16:11:27 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id F332D15FA1; Wed, 12 Jul 2000 17:07:52 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Wed, 12 Jul 2000 10:17:56 -0400 Received: by vger.rutgers.edu id ; Wed, 12 Jul 2000 10:16:56 -0400 Received: from [38.149.17.171] ([38.149.17.171]:1812 "HELO ltc.com") by vger.rutgers.edu with SMTP id ; Wed, 12 Jul 2000 10:16:06 -0400 Received: from gw1.ltc.com (gw1.ltc.com [38.149.17.163]) by ltc.com (NTMail 3.03.0017/1.afdd) with ESMTP id ha313463 for ; Wed, 12 Jul 2000 10:32:21 -0400 Message-ID: <051201bfec0d$a4dead50$0701010a@ltc.com> From: "Bradley D. LaRonde" To: "Paul Koning" Cc: , , References: <004b01bfeb76$36e29330$0701010a@ltc.com><14699.36836.422617.99497@desk.crynwr.com><012101bfeb83$e4da7b30$0701010a@ltc.com> <14700.31946.403936.324861@xedia.com> Subject: Re: [Handhelds] Re: Touch Screen Driver Generic Interface for allLinux SA11x0 platforms. Date: Wed, 12 Jul 2000 10:29:53 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu ----- Original Message ----- From: "Paul Koning" To: Cc: ; ; Sent: Wednesday, July 12, 2000 10:12 AM Subject: Re: [Handhelds] Re: Touch Screen Driver Generic Interface for allLinux SA11x0 platforms. > Furthermore, passing only non-zero deltas across the kernel/user > boundary is more efficient. Those boundary crossings are very > efficient and doing one every millisecond or so is not particularly > desirable. As I mentioned in a previous email, I agree in principle, but in practice non-zero deltas in raw touch panel data are too rare to bother with. Also, who says you have to get touch panel data one reading at a time? The kernel driver can buffer the readings. Regards, Brad unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Wed Jul 12 18:31:21 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13CQLv-0001bp-00 for linux-arm-archive@lists.arm.linux.org.uk; Wed, 12 Jul 2000 18:31:20 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 3D7921608A; Wed, 12 Jul 2000 19:28:39 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Wed, 12 Jul 2000 13:14:03 -0400 Received: by vger.rutgers.edu id ; Wed, 12 Jul 2000 13:13:16 -0400 Received: from mail2.digital.com ([204.123.2.56]:1274 "EHLO mail2.digital.com") by vger.rutgers.edu with ESMTP id ; Wed, 12 Jul 2000 13:12:10 -0400 Received: from pachyderm.pa.dec.com (pachyderm.pa.dec.com [16.4.16.23]) by mail2.digital.com (8.9.2/8.9.3/WV2.0h) with ESMTP id KAA07096; Wed, 12 Jul 2000 10:24:15 -0700 (PDT) Received: by pachyderm.pa.dec.com; id KAA18079; Wed, 12 Jul 2000 10:24:14 -0700 (PDT) Date: Wed, 12 Jul 2000 10:24:14 -0700 (PDT) From: jg@pa.dec.com (Jim Gettys) Message-Id: <200007121724.KAA18079@pachyderm.pa.dec.com> X-Mailer: Pachyderm (client pachyderm.pa-x.dec.com, user jg) To: Mike Touloumtzis Cc: Charlie Flynn , linux-arm@vger.rutgers.edu, handhelds@handhelds.org In-Reply-To: <20000710134727.H21694@fiji.bluemug.com> Subject: Re: [Handhelds] Re: Touch Screen Driver Generic Interface for all Linux SA11x0 platforms. Mime-Version: 1.0 Content-Type: text/plain Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu > Hi Charlie, > > Pixel coordinates won't be enough, in general. Digitizers used for > handwriting recognition often have much higher resolution than the > LCDs, and the extra information is vital for good handwriting > recognition, particularly for Asian languages. I agree... > > I've integrated Asian handwriting recognition libraries into OSes > which were not designed with this in mind, and I had to hack things > up get digitizer-resolution coordinates. > > Plus, I think it'd be nice to decouple the digitizer API from a > specific screen resolution. > Yup. Not just nice, but essential for some applications. This implies the driver interface(s) should be in device coordinates to me, rather than X coordinate systems. There are two interfaces in X that have to be built: one in which the touch screen is being used as the primary pointer, and then some other way to deal with it in all its glory, almost certainly via the X Input extension. (Un)fortunately, the X Input extension is something I haven't ever dealt with, so I'll have to spend some time figuring things out. This was going on about the same time as I was last working on X related topics (the XSync extension). Keith Packard knows quite a bit about the input extension (he and Bob Scheifler ripped it apart and put it back together again some years ago), and we're talking to each other about how in general we need X input to get redone (note that while touchscreen is burning for handhelds, that the widespread deployment of USB over the next year is going to require this issue to get visited in a general sense for X; Keith is also interested in handheld computing). Some work needs to be done to X in general in this area, as the input extension does not have the concept of devices coming and going (plug and play kinds of hardware weren't on the drawing board in the early '90's). So not all the cultural history has been lost. If we need to add an extension to make this all work, we can. So we'll probably have to do a bit of work to X in general and while we're at it, should ensure there be some way to get both screen coordinates from the X server, and higher resolution coordinates for applications that need them. - Jim -- Jim Gettys Technology and Corporate Development Compaq Computer Corporation jg@pa.dec.com unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Wed Jul 12 19:14:58 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13CR29-0002GM-00 for linux-arm-archive@lists.arm.linux.org.uk; Wed, 12 Jul 2000 19:14:57 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id C64AB160AF; Wed, 12 Jul 2000 20:09:08 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Wed, 12 Jul 2000 13:54:43 -0400 Received: by vger.rutgers.edu id ; Wed, 12 Jul 2000 13:54:11 -0400 Received: from [63.224.253.61] ([63.224.253.61]:61501 "EHLO orestes.keithp.com") by vger.rutgers.edu with ESMTP id ; Wed, 12 Jul 2000 13:53:39 -0400 Received: from orestes.keithp.com (localhost [127.0.0.1]) by orestes.keithp.com (8.9.3/8.9.3) with ESMTP id LAA14701; Wed, 12 Jul 2000 11:05:44 -0700 Message-Id: <200007121805.LAA14701@orestes.keithp.com> X-Mailer: exmh version 2.0.2 2/24/98 To: jg@pa.dec.com (Jim Gettys) Cc: Mike Touloumtzis , Charlie Flynn , linux-arm@vger.rutgers.edu, handhelds@handhelds.org Subject: Re: [Handhelds] Re: Touch Screen Driver Generic Interface for all Linux SA11x0 platforms. From: Keith Packard In-reply-to: Your message of "Wed, 12 Jul 2000 10:24:14 PDT." <200007121724.KAA18079@pachyderm.pa.dec.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 12 Jul 2000 11:05:44 -0700 Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu > There are two interfaces in X that have to be built: one in which the touch > screen is being used as the primary pointer, and then some other way to > deal with it in all its glory, almost certainly via the X Input extension. I've been thinking more about input recently, and it's less than clear that the input extension is sufficient for pen-based devices. Because the input device is so limited, I believe that a significant amount of policy will be required to distinguish between gestures intended as text input and gestures intended for pointer input. In addition, we need support for a digital ink "overlay". One of the important HWR lessons I learned from the Itsy was that graffiti with feedback is much more reliable than without. It's almost as if a separate app should be reading the touch screen and selectively synthesizing pointer and keyboard events; drawing digital ink on the screen to help make HWR usable. Perhaps a portion of this app could be done within the X server using a grab/queuing mechanism similar to the core grabs. Here's an idea -- have pen-down events cause raw input to be directed at the external agent and simultaneously queued within the server. The agent could then monitor the gesture and at some point decide whether to echo with digital ink, and finally decide whether to forward the entire queued event stream on to the X pointer input queue or send it along for HWR. The server could echo the ink itself or we could let the agent generate X protocol for that. keithp@suse.com XFree86 Core Team SuSE, Inc. unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Wed Jul 12 19:25:59 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13CRCo-0002Q1-00 for linux-arm-archive@lists.arm.linux.org.uk; Wed, 12 Jul 2000 19:25:58 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id B8E9515F0D; Wed, 12 Jul 2000 20:22:05 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Wed, 12 Jul 2000 14:06:10 -0400 Received: by vger.rutgers.edu id ; Wed, 12 Jul 2000 14:05:03 -0400 Received: from mail2.digital.com ([204.123.2.56]:1534 "EHLO mail2.digital.com") by vger.rutgers.edu with ESMTP id ; Wed, 12 Jul 2000 14:03:51 -0400 Received: from pachyderm.pa.dec.com (pachyderm.pa.dec.com [16.4.16.23]) by mail2.digital.com (8.9.2/8.9.3/WV2.0h) with ESMTP id LAA10034; Wed, 12 Jul 2000 11:15:58 -0700 (PDT) Received: by pachyderm.pa.dec.com; id LAA03539; Wed, 12 Jul 2000 11:15:57 -0700 (PDT) Date: Wed, 12 Jul 2000 11:15:57 -0700 (PDT) From: jg@pa.dec.com (Jim Gettys) Message-Id: <200007121815.LAA03539@pachyderm.pa.dec.com> X-Mailer: Pachyderm (client pachyderm.pa-x.dec.com, user jg) To: Mike Touloumtzis Cc: Charlie Flynn , linux-arm@vger.rutgers.edu, handhelds@handhelds.org In-Reply-To: <20000711105708.T21694@fiji.bluemug.com> Subject: Re: [Handhelds] Re: Touch Screen Driver Generic Interface for all Linux SA11x0 platforms. Mime-Version: 1.0 Content-Type: text/plain Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu > Sender: handhelds-admin@handhelds.org > From: Mike Touloumtzis > Date: Tue, 11 Jul 2000 10:57:08 -0700 > To: Charlie Flynn > Cc: Mike Touloumtzis , linux-arm@vger.rutgers.edu, > handhelds@handhelds.org > Subject: [Handhelds] Re: Touch Screen Driver Generic Interface for all Linux > SA11x0 platforms. > ----- > On Wed, Jul 12, 2000 at 12:26:37AM +1000, Charlie Flynn wrote: > > Thanks for the reply Mike. > > > > I haven't come across a Digitizer before so are you saying that a > > simple redesign of the TS_EVENT structure is all that is needed > > to accommodate the Digitizer or does the Digitizer require other > > special considerations? In other words will this spec accommodate the > > Digitizer without too much modification? > > > > A digitizer is just a touch screen input device. The Palm Pilot has > a digitizer; so does the Psion Series 5. In the lingo I've been used > to, digitizer + LCD == touch screen[1]. It sometimes connotes high > resolution, especially WRT to the graphic artist market. My experience is > mainly in Japanese consumer electronics; handwriting recognition is taken > much more seriously there than in the U.S. and European markets, because > everyone learns to write characters (even English ones) using a consistent > stroke order, so vector handwriting recognition works very well. > > Unfortunately, the word "digitizer" is overloaded, and also refers to > various forms of specialized A/D equipment, like ultra-high-resolution > physical surface scanners, and optical scanners. But it's pretty > unambiguous in the consumer electronics market; there's not a lot of > overlap. > > The type of information you get out a digitizer varies from coarse > worse-than-pixel resolution (this type might be used in a greasy-sceen > supermarket kiosk) to a current peak of about 10,000 lines per inch > (for high-end graphic artist drawing tablets). 10K LPI!!!! I don't believe they could possibly really be at that resolution, though the hardware might make claims to be that high... The second question is how large do tablets get? The product of LPI (LPC) and the size tells us how big the coordinates should be... By this theory, it sounds like 16 bits/coordinate may be enough, but at 32 bits/coordinate, it can't possibly be wrong (since this would imply a physical size for the digitizer of 6 miles or so). Since at 16 bits we are a bit close for taste (1K line resolution results in a 5 foot digitizer size), it sounds like coordinate values should be 32 bits to be safe. > > Handwriting recognition on consumer electronics devices is typically done > using vector paths at digitizer resolution; in addition to X+Y coordinates, > the following info might be available from the hardware: pressure, stylus > angle, stylus height (mainly for RF devices like the Cross input pad, I > think; I have no experience with this). The Jot HWR system stores a whole > bunch of info per path: > > "The ink is stored in vectorized form (important for resizing and > representation on higher resolution output devices) and currently may > include the following attributes[35]: stroke order, bounding coordinates, > groups of strokes, timing, pressure, stylus angle (in x and y directions), > pen color (including opacity), scaling and offset, height over the > digitizer surface, buttons on the pen, and pen tip type. Speed and > pressure, for example, are important for signature verification, and > color may be used for user identification in a multi-user environment."[2] > > Some of these attributes come from the hardware, while others are clearly > plugged in by software and probably wouldn't play a role in a kernel API. > Timing info is plugged in by software, but must be very high-precision > and so should probably be handled by the kernel (by sticking a > gettimeofday()-derived timestamp on input data points). Yup. More on time stamps below. I'm a bit skeptical about pen color: are there devices that can change colors of pens dynamically? Can they change pen types dynamically? If yes, then I suppose the data might be packed into each event, and if no, just via an interface to determine once... > > Good ink display is also best done with a sub-pixel coordinate system, > for the same reasons that sub-pixel sampling is good for antialiasing > and other graphical effects. > > In writing a digitizer driver API, there are a few main things to keep > in mind: > > -- Allow room for plenty of resolution, and don't assume pixel coords > will equal digitizer coords. > > -- Timestamps are important because they allow pen velocity to be > measured. Yes. I agree completely. X needs timestamps associated with device events to allow proper serialization among different devices as well. So I think timestamps should present in device driver events I can try work around their absense, but it is a pain, and always more questionable than if the device driver generates the timestamps itself. In short, user space timestamps are fundamentally unreliable and don't work well... The next question is units: is more than a millisecond resolution time stamp needed? Or do we return a struct timeval? (another 64 bits on 32 bit machines). X's timestamps are a 32 bit value in milliseconds, (32 bits). Just go the the Linux kernel list, where they are discussing worst case latencies for user space stuff at the moment: while they are working to minimize the latencies, the worst case are frightenly high. > > -- Allow room for expansion to new data types in the API (for instance, > pen pressure info). Translation: pad structures a little :-). I > wouldn't want to try to overdesign this; that way lies X. I would > at read a bunch of data sheets before trying to settle on a canonical > API, though. We did allow for new datatypes and padded structures in X. The core X stuff isn't so badly overdesigned, but some of the extensions went of the deep end... > > -- Some digitizers have non-linear input systems and need input munging > beyond the simple device-independant translation/rotation/deskew that > calibration can provide. Most devices work fine with the equivalent > of a single affine transform at most, but I know of at least one > shipping touchscreen PDA/phone in Japan that essentially requires a > system of linear equations to normalize coordinates, and also has > two "dead zones" that must be worked around. Question: is a single affine transform going to get more than 90% of the devices out there? If so, lets run with this, and be done with it; leave the others to suffer for their own sins of bad hardware... > > A driver API should be clear about whether it normalizes coordinates > (in which case it must be possible to feed it calibration points from > a userspace app) or whether it passes raw digitizer input to higher > layers (in which case those layers must have hardware-dependent > code--this is the gpm approach). > I believe it is important that things be "sane" when you power up a system. To me, this means that I need to be told somehow how to convert hardware device coordinates to something that applications (read X) can use. This argues to me to report the raw coordinates to user space, along with calibration data (which can be approximate when first started, but then updated with correct values if the user recalibrates the device). Since you might (or might not) run a calibration application under a window system, I think there should be a way to set the default calibration information in the driver, rather than have to recalibrate for each application that comes along. In some sense, this is rediculous (since all the calls would be doing is saving information for later), but the practical impact is large. Saving the information between processes is non-trivial... And for the record, devices that spew events continuously forever should be banned: it is certainly the case that this should not cause user space processes to be woken up continuously to deal with (non)events they don't care about. Informing applications that nothing has changed is brain-death beyond belief. (not on my battery power, you don't!). And yes, the kernel should buffer events for clients: clients get busy for a while, and it is much cheaper to to pick up a bunch of events at once when you are busy than handle them one at a time. This minimizes the overhead when you need to minimize it (when you are busy). - Jim -- Jim Gettys Technology and Corporate Development Compaq Computer Corporation jg@pa.dec.com unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Wed Jul 12 19:49:49 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13CRZt-0002kJ-00 for linux-arm-archive@lists.arm.linux.org.uk; Wed, 12 Jul 2000 19:49:49 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 0E1C715F0D; Wed, 12 Jul 2000 20:45:32 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Wed, 12 Jul 2000 14:31:15 -0400 Received: by vger.rutgers.edu id ; Wed, 12 Jul 2000 14:31:05 -0400 Received: from cvsftp.cotw.com ([208.242.241.39]:1536 "EHLO cvsftp.cotw.com") by vger.rutgers.edu with ESMTP id ; Wed, 12 Jul 2000 14:30:38 -0400 Received: from cotw.com (laptop1.ptec.com [192.168.10.10]) by cvsftp.cotw.com (8.9.3/8.9.3) with ESMTP id NAA27602; Wed, 12 Jul 2000 13:41:02 -0500 Message-ID: <396CBB72.E4115FBD@cotw.com> Date: Wed, 12 Jul 2000 13:39:46 -0500 From: Steve Hill X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.3.47 i686) X-Accept-Language: en MIME-Version: 1.0 To: Jim Gettys Cc: Mike Touloumtzis , Charlie Flynn , linux-arm@vger.rutgers.edu, handhelds@handhelds.org Subject: Re: [Handhelds] Re: Touch Screen Driver Generic Interface for all Linux SA11x0 platforms. References: <200007121815.LAA03539@pachyderm.pa.dec.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Jim Gettys wrote: > > > The type of information you get out a digitizer varies from coarse > > worse-than-pixel resolution (this type might be used in a greasy-sceen > > supermarket kiosk) to a current peak of about 10,000 lines per inch > > (for high-end graphic artist drawing tablets). > > 10K LPI!!!! I don't believe they could possibly really be at that > resolution, though the hardware might make claims to be that high... > Actually, from experience with digitizing tablets for CAD which use similar technology, the resolution is near that. > The second question is how large do tablets get? > I used tablets that were 12"x12" and 36"x24", but I have seen them as large as 48"x36". -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' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Wed Jul 12 19:52:09 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13CRc9-0002n7-00 for linux-arm-archive@lists.arm.linux.org.uk; Wed, 12 Jul 2000 19:52:09 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 0CC8015EE6; Wed, 12 Jul 2000 20:46:31 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Wed, 12 Jul 2000 14:23:27 -0400 Received: by vger.rutgers.edu id ; Wed, 12 Jul 2000 14:21:29 -0400 Received: from FORT-POINT-STATION.MIT.EDU ([18.72.0.53]:60786 "EHLO fort-point-station.mit.edu") by vger.rutgers.edu with ESMTP id ; Wed, 12 Jul 2000 14:19:35 -0400 Received: from grand-central-station.MIT.EDU (GRAND-CENTRAL-STATION.MIT.EDU [18.69.0.34]) by fort-point-station.mit.edu (8.9.2/8.9.2) with ESMTP id OAA27060 for ; Wed, 12 Jul 2000 14:31:48 -0400 (EDT) Received: from melbourne-city-street.MIT.EDU (MELBOURNE-CITY-STREET.MIT.EDU [18.69.0.45]) by grand-central-station.MIT.EDU (8.9.2/8.9.2) with ESMTP id OAA22698 for ; Wed, 12 Jul 2000 14:31:48 -0400 (EDT) Received: from baba-yaga.mit.edu (IDENT:root@BABA-YAGA.MIT.EDU [18.244.1.164]) by melbourne-city-street.MIT.EDU (8.9.3/8.9.2) with ESMTP id OAA13743 for ; Wed, 12 Jul 2000 14:31:48 -0400 (EDT) Received: by baba-yaga.mit.edu (8.9.3/4.7) id OAA18849; Wed, 12 Jul 2000 14:31:48 -0400 To: linux-arm Subject: Re: EEPro100 NICs and EBSA285. References: <396ADF3F.BDC59A4D@telscom.ch> From: Jacob Strauss Date: 12 Jul 2000 14:31:48 -0400 In-Reply-To: Mathias Teikari's message of "Tue, 11 Jul 2000 10:48:00 +0200" Message-ID: Lines: 84 X-Mailer: Gnus v5.7/Emacs 20.5 Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu This seems to be the same problem I'm having. Does anyone with a working ebsa-285 setup have it working on the newer revision of the board (Intel rather than Dec names, 21285-AB rather than 21285-AA) -Jacob Mathias Teikari writes: > Hi all, > > Has anybody had a working EBSA-285 setup with Intel's EEPro100 NICs? > > I am using a 2.2.15 kernel patched with patch-2.2.15-rmk1 (because I > need a 2.2 kernel at this point) and ebsa285-bios-1.06 w. diff2 > patch. > The eepro100 driver is compiled into the kernel because I want to > mount an NFS root fs. > > Now, the problem.. The cards won't initialise properly, or at least > that is what the kernel thinks. > > ... > POSIX conformance testing by UNIFIX > PCI: Probing PCI hardware > pci_scan_bus for bus 0 > PCI: 00:38 [8086/1229] > PCI: pci_scan_bus returning with max=00 > Linux NET4.0 for Linux 2.2 > Based upon Swansea University Computer Society NET3.039 > NET4: Unix domain sockets 1.0 for Linux NET4.0. > NET4: Linux TCP/IP 1.0 for NET4.0 > IP Protocols: ICMP, UDP, TCP > TCP: Hash tables configured (ehash 16384 bhash 16384) > Starting kswapd v 1.5 > RAM disk driver initialized: 1 RAM disks of 4096K size > Found Intel i82557 PCI Speedo at I/O 0xe1800000, IRQ 22. > PCI latency timer (CFLT) is 0x20. > eepro100.c:v1.09j-t 9/29/99 Donald Becker > http://cesdis.gsfc.nasa.gov/linux/drivers > /eepro100.html > eepro100.c: $Revision: 1.20.2.3 $ 2000/03/02 Modified by Andrey V. > Savochkin w.sw.com.sg> and others > eth0: Intel PCI EtherExpress Pro100 at 0xe1800000, > 00:90:27:8C:D8:6B, IRQ 22. > Receiver lock-up bug exists -- enabling work-around. > Board assembly 721383-006, Physical connectors present: RJ45 > Primary interface chip i82555 PHY #1. > Self test failed, status ffffffff: > Failure to initialize the i82557. > Verify that the card is in a bus-master capable slot. > ... > > I know that the hardware is OK because it's running when using > another OS (in house developed mini-OS). > > A thought that crossed my mind is address mapping problems > (PCI-SDRAM et vice-versa) or some other setup of the CSRs. > > Any suggestions? > > Thanks, > Mathias > > > > -- > +---------------------------------------------------------+ .--. > | Mathias Teikari mathias.teikari@telscom.ch | |o_o | > | Ba. Sc. EE. Office Ph: +41 (0)31 376 2030 | |:_/ | > | SW Development Engineer Mobile Ph: +41 (0)76 541 9449 | // \ \ > | Telscom AG Sandrainstr. 17, CH-3007 Bern | (| | ) > | | /'\_ _/`\ > +---------------- http://www.telscom.ch ------------------+ \___)=(___/ > > > > > unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu > ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ > ++ kernel-related discussions. ++ unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Wed Jul 12 19:56:15 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13CRg6-0002qV-00 for linux-arm-archive@lists.arm.linux.org.uk; Wed, 12 Jul 2000 19:56:15 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 2C01E15D79; Wed, 12 Jul 2000 20:56:07 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Wed, 12 Jul 2000 14:43:01 -0400 Received: by vger.rutgers.edu id ; Wed, 12 Jul 2000 14:42:51 -0400 Received: from crl.dec.com ([192.58.206.2]:2974 "EHLO crl.dec.com") by vger.rutgers.edu with ESMTP id ; Wed, 12 Jul 2000 14:42:22 -0400 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 OAA05526; Wed, 12 Jul 2000 14:54:30 -0400 (EDT) Received: by ims.crl.dec.com with Internet Mail Service (5.5.2650.21) id ; Wed, 12 Jul 2000 14:59:44 -0400 Message-ID: From: Jamey Hicks To: "'jg@pa.dec.com'" , Mike Touloumtzis Cc: Charlie Flynn , linux-arm@vger.rutgers.edu, handhelds@handhelds.org Subject: RE: [Handhelds] Re: Touch Screen Driver Generic Interface for all Linux SA11x0 platforms. Date: Wed, 12 Jul 2000 14:54:26 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu On pen color: There are devices that can track different pen colors. The mimio whiteboard capture unit from Virtual Ink tracks multiple pens. See www.mimio.com. -Jamey unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Wed Jul 12 20:07:38 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13CRr6-00031m-00 for linux-arm-archive@lists.arm.linux.org.uk; Wed, 12 Jul 2000 20:07:36 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 424BF15DDB; Wed, 12 Jul 2000 21:07:22 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Wed, 12 Jul 2000 14:51:47 -0400 Received: by vger.rutgers.edu id ; Wed, 12 Jul 2000 14:51:08 -0400 Received: from dfw7-1.relay.mail.uu.net ([199.171.54.106]:34942 "EHLO dfw7-1.relay.mail.uu.net") by vger.rutgers.edu with ESMTP id ; Wed, 12 Jul 2000 14:50:10 -0400 Received: from xedia.com by dfw7sosrv11.alter.net with SMTP (peer crosschecked as: madway.xedia.com [198.202.232.199]) id QQixoe28090; Wed, 12 Jul 2000 19:02:17 GMT Received: from tonga.xedia.com by xedia.com (4.1/SMI-4.1) id AA01399; Wed, 12 Jul 00 14:58:25 EDT Received: by tonga.xedia.com (SMI-8.6/SMI-SVR4) id PAA01974; Wed, 12 Jul 2000 15:02:15 -0400 From: Paul Koning Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <14700.49335.307702.539603@xedia.com> Date: Wed, 12 Jul 2000 15:02:15 -0400 (EDT) To: sjhill@cotw.com Cc: jg@pa.dec.com, miket@bluemug.com, flynn@ozy.dec.com, linux-arm@vger.rutgers.edu, handhelds@handhelds.org Subject: Re: [Handhelds] Re: Touch Screen Driver Generic Interface for all Linux SA11x0 platforms. References: <200007121815.LAA03539@pachyderm.pa.dec.com> <396CBB72.E4115FBD@cotw.com> X-Mailer: VM 6.72 under 21.1 (patch 9) "Canyonlands" XEmacs Lucid Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu >>>>> "Steve" == Steve Hill writes: Steve> Jim Gettys wrote: >> > The type of information you get out a digitizer varies from >> coarse > worse-than-pixel resolution (this type might be used in a >> greasy-sceen > supermarket kiosk) to a current peak of about >> 10,000 lines per inch > (for high-end graphic artist drawing >> tablets). >> >> 10K LPI!!!! I don't believe they could possibly really be at that >> resolution, though the hardware might make claims to be that >> high... >> Steve> Actually, from experience with digitizing tablets for CAD Steve> which use similar technology, the resolution is near that. Of course accuracy isn't anywhere near that, but so long as the device is monotonic, having the extra bits is potentially useful. >> The second question is how large do tablets get? >> Steve> I used tablets that were 12"x12" and 36"x24", but I have seen Steve> them as large as 48"x36". I've seen them quite a lot bigger than that. I remember pictures of tablets used for work on maps that were clearly bigger than a standard old-time draftman's drafting table. Maybe six feet or so longest dimension, perhaps even more. My strong prerefence is to play it safe. Squeezing coordinates into 16 bits doesn't buy much and it's sufficiently close to the edge that 32 bits is clearly the safer answer. Jim> I'm a bit skeptical about pen color: are there devices that can Jim> change colors of pens dynamically? Can they change pen types Jim> dynamically? If yes, then I suppose the data might be packed Jim> into each event, and if no, just via an interface to determine Jim> once... Pen type -- definitely. Consider the Wacom tablet, popular among graphic artists on PCs and Macs. They come with several pen types (pen, puck, airbrush). Also, the pen has an "erasers" on the other end, so you can flip it over to erase. That's a property seen across the API. I vaguely remember seeing mention of Wacom support in Linux and possibly in X. Certainly that device would be an important test case for any API, along with the perhaps more familiar architect-style puck tablets. The sort of parameters that the Wacom device sends relate to its need to emulate artist tools. Take a look at the "airbrush". I don't have one, my Wacom is too old. But a regular "double action" airbrush (the non-computer kind) has two control inputs apart from position: air volume and paint volume, which are independent. And position is in three coordinates, not just two (distance from the paper matters a lot). If the Wacom device emulates all that, it means that each sample would consist of five analog values (x, y, z, air, paint). Hm. Off the wall thought. Would it make sense for a digitizer API to be applicable to 3d input devices as well, things like 3d pointers, sensor gloves, stuff like that? There seems to be a lot of overlap, but it may be too much of a distraction. paul paul unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Wed Jul 12 20:23:43 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13CS6f-0003EV-00 for linux-arm-archive@lists.arm.linux.org.uk; Wed, 12 Jul 2000 20:23:42 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 2106C15D58; Wed, 12 Jul 2000 21:23:13 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Wed, 12 Jul 2000 15:08:45 -0400 Received: by vger.rutgers.edu id ; Wed, 12 Jul 2000 15:08:14 -0400 Received: from cvsftp.cotw.com ([208.242.241.39]:1584 "EHLO cvsftp.cotw.com") by vger.rutgers.edu with ESMTP id ; Wed, 12 Jul 2000 15:07:39 -0400 Received: from cotw.com (laptop1.ptec.com [192.168.10.10]) by cvsftp.cotw.com (8.9.3/8.9.3) with ESMTP id OAA27872; Wed, 12 Jul 2000 14:19:35 -0500 Message-ID: <396CC47B.2DEB0C72@cotw.com> Date: Wed, 12 Jul 2000 14:18:19 -0500 From: Steve Hill X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.3.47 i686) X-Accept-Language: en MIME-Version: 1.0 To: Paul Koning Cc: jg@pa.dec.com, miket@bluemug.com, flynn@ozy.dec.com, linux-arm@vger.rutgers.edu, handhelds@handhelds.org Subject: Re: [Handhelds] Re: Touch Screen Driver Generic Interface for all Linux SA11x0 platforms. References: <200007121815.LAA03539@pachyderm.pa.dec.com> <396CBB72.E4115FBD@cotw.com> <14700.49335.307702.539603@xedia.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Paul Koning wrote: > > Of course accuracy isn't anywhere near that, but so long as the device > is monotonic, having the extra bits is potentially useful. > I would agree. > Steve> I used tablets that were 12"x12" and 36"x24", but I have seen > Steve> them as large as 48"x36". > > I've seen them quite a lot bigger than that. I remember pictures of > tablets used for work on maps that were clearly bigger than a standard > old-time draftman's drafting table. Maybe six feet or so longest > dimension, perhaps even more. > Whoops, I forgot about the mapping agencies too. > My strong prerefence is to play it safe. Squeezing coordinates into > 16 bits doesn't buy much and it's sufficiently close to the edge that > 32 bits is clearly the safer answer. > You've got my vote for it. > I vaguely remember seeing mention of Wacom support in Linux and > possibly in X. Certainly that device would be an important test case > for any API, along with the perhaps more familiar architect-style puck > tablets. The sort of parameters that the Wacom device sends relate to > its need to emulate artist tools. Take a look at the "airbrush". I > don't have one, my Wacom is too old. But a regular "double action" > airbrush (the non-computer kind) has two control inputs apart from > position: air volume and paint volume, which are independent. And > position is in three coordinates, not just two (distance from the > paper matters a lot). If the Wacom device emulates all that, it means > that each sample would consist of five analog values (x, y, z, air, > paint). > Owen Tayler maintains the XInput HOWTO document which you can find at (http://www.gtk.org/~otaylor/xinput/howto/). I haven't looked at in a while though. It appears support is there for Wacom and Summagraphics just to name a few. This uses X to handle the data i.e. the user land side which goes back to an earlier comment by Brad that the data should come raw from the kernel to be handled by the application. > Hm. Off the wall thought. Would it make sense for a digitizer API to > be applicable to 3d input devices as well, things like 3d pointers, > sensor gloves, stuff like that? There seems to be a lot of overlap, > but it may be too much of a distraction. > I would have to say no. Something says to me "no" because things start popping in my head like Euler angles, infancy IMHO of 3d input devices, etc. I would be interested in other peoples thoughts, but we should probably start a different thread. -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' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Wed Jul 12 20:42:09 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13CSOV-0003Zo-00 for linux-arm-archive@lists.arm.linux.org.uk; Wed, 12 Jul 2000 20:42:08 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id EC51F15DD4; Wed, 12 Jul 2000 21:34:59 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Wed, 12 Jul 2000 15:20:18 -0400 Received: by vger.rutgers.edu id ; Wed, 12 Jul 2000 15:19:56 -0400 Received: from lnsmtpbos00.lhs.com ([208.162.98.43]:3764 "HELO lhs.com") by vger.rutgers.edu with SMTP id ; Wed, 12 Jul 2000 15:19:07 -0400 Received: by lhs.com(Lotus SMTP MTA v4.6.6 (890.1 7-16-1999)) id 8525691A.006C31BB ; Wed, 12 Jul 2000 15:41:46 -0400 X-Lotus-FromDomain: LHS From: nmistry@lhsl.com To: Steve Hill Cc: linux-arm@vger.rutgers.edu, handhelds@handhelds.org Message-ID: <8525691A.006C3074.00@lhs.com> Date: Wed, 12 Jul 2000 15:28:38 -0400 Subject: Re: [Handhelds] Re: Touch Screen Driver Generic Interface for all Linux SA11x0 platforms. Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu I can second that, i currently own an Calcomp/Sumagraphics Digitizer, and we get about 12,000 lpi, and its a 60"x48". It comes in handy for several things, especially for making 3D Digital Terrain Models by quickly tracing contours off a land plot plan. -Nick Steve Hill on 07/12/2000 02:39:46 PM To: Jim Gettys cc: Mike Touloumtzis , Charlie Flynn , linux-arm@vger.rutgers.edu, handhelds@handhelds.org (bcc: Nicholas Mistry/USER/US/LHS) Subject: Re: [Handhelds] Re: Touch Screen Driver Generic Interface for all Linux SA11x0 platforms. Jim Gettys wrote: > > > The type of information you get out a digitizer varies from coarse > > worse-than-pixel resolution (this type might be used in a greasy-sceen > > supermarket kiosk) to a current peak of about 10,000 lines per inch > > (for high-end graphic artist drawing tablets). > > 10K LPI!!!! I don't believe they could possibly really be at that > resolution, though the hardware might make claims to be that high... > Actually, from experience with digitizing tablets for CAD which use similar technology, the resolution is near that. > The second question is how large do tablets get? > I used tablets that were 12"x12" and 36"x24", but I have seen them as large as 48"x36". -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' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Wed Jul 12 20:43:29 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13CSPn-0003bG-00 for linux-arm-archive@lists.arm.linux.org.uk; Wed, 12 Jul 2000 20:43:29 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 2281115E7E; Wed, 12 Jul 2000 21:38:27 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Wed, 12 Jul 2000 15:22:38 -0400 Received: by vger.rutgers.edu id ; Wed, 12 Jul 2000 15:21:49 -0400 Received: from rover.village.org ([204.144.255.49]:4907 "EHLO rover.village.org") by vger.rutgers.edu with ESMTP id ; Wed, 12 Jul 2000 15:21:21 -0400 Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA54595; Wed, 12 Jul 2000 13:33:25 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA17194; Wed, 12 Jul 2000 13:33:16 -0600 (MDT) Message-Id: <200007121933.NAA17194@harmony.village.org> To: Paul Koning Subject: Re: [Handhelds] Re: Touch Screen Driver Generic Interface for all Linux SA11x0 platforms. Cc: sjhill@cotw.com, jg@pa.dec.com, miket@bluemug.com, flynn@ozy.dec.com, linux-arm@vger.rutgers.edu, handhelds@handhelds.org In-reply-to: Your message of "Wed, 12 Jul 2000 15:02:15 EDT." <14700.49335.307702.539603@xedia.com> References: <14700.49335.307702.539603@xedia.com> <200007121815.LAA03539@pachyderm.pa.dec.com> <396CBB72.E4115FBD@cotw.com> Date: Wed, 12 Jul 2000 13:33:16 -0600 From: Warner Losh Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu In message <14700.49335.307702.539603@xedia.com> Paul Koning writes: : Steve> I used tablets that were 12"x12" and 36"x24", but I have seen : Steve> them as large as 48"x36". : : I've seen them quite a lot bigger than that. I remember pictures of : tablets used for work on maps that were clearly bigger than a standard : old-time draftman's drafting table. Maybe six feet or so longest : dimension, perhaps even more. Back in school in the late 1980's, one of my jobs was to get a digitizer table working. While it didn't use a pen stylus, it was 6'x4' and had a resolution of about .001". Its coordinate space was something like 75000x50000. There were larger tables at the time (on the order of 12'x8') that were talked about in the manual that had an even better resolution, but they were mondo expensive so we didn't have one :-) Warner unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Wed Jul 12 20:49:28 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13CSVb-0003gm-00 for linux-arm-archive@lists.arm.linux.org.uk; Wed, 12 Jul 2000 20:49:28 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 55B4915E7E; Wed, 12 Jul 2000 21:46:49 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Wed, 12 Jul 2000 15:27:45 -0400 Received: by vger.rutgers.edu id ; Wed, 12 Jul 2000 15:27:32 -0400 Received: from mail1.digital.com ([204.123.2.50]:1922 "EHLO mail1.digital.com") by vger.rutgers.edu with ESMTP id ; Wed, 12 Jul 2000 15:26:15 -0400 Received: from pachyderm.pa.dec.com (pachyderm.pa.dec.com [16.4.16.23] (may be forged)) by mail1.digital.com (8.9.2/8.9.3/WV2.0h) with ESMTP id MAA04403; Wed, 12 Jul 2000 12:38:23 -0700 (PDT) Received: by pachyderm.pa.dec.com; id MAA19606; Wed, 12 Jul 2000 12:38:22 -0700 (PDT) Date: Wed, 12 Jul 2000 12:38:22 -0700 (PDT) From: jg@pa.dec.com (Jim Gettys) Message-Id: <200007121938.MAA19606@pachyderm.pa.dec.com> X-Mailer: Pachyderm (client pachyderm.pa-x.dec.com, user jg) To: Keith Packard Cc: jg@pa.dec.com (Jim Gettys), Mike Touloumtzis , Charlie Flynn , linux-arm@vger.rutgers.edu, handhelds@handhelds.org In-Reply-To: <200007121805.LAA14701@orestes.keithp.com> Subject: Re: [Handhelds] Re: Touch Screen Driver Generic Interface for all Linux SA11x0 platforms. Mime-Version: 1.0 Content-Type: text/plain Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu So what you are saying is that something like xscribble becomes central to input in general on handheld devices: it takes relatively raw input and then tells X what to do when it needs to. Building it into the core X server seems wrong to me: by definition, we won't get it right: I think we should regard it as though it were a window manager: a separate application providing some of the UI. The issue I see is how to arbitrate among more than one application that might want/need the high resolution digitizer device... We'll certainly be running something like scribble continuously, but other apps may need more than what the X core protocol gives them. If the Xinput stuff can adaquately handle this situation (other applications in addition to the scribble app), then we have a rational course of action. I guess it is time to go look at the Input extension and see if it can deal with digitizers adequately in the general case and whether it has any grab/replay notion. My book is at home, I'll try to remember to get a copy and stare at it some tomorrow. - Jim > Sender: handhelds-admin@handhelds.org > From: Keith Packard > Date: Wed, 12 Jul 2000 11:05:44 -0700 > To: jg@pa.dec.com (Jim Gettys) > Cc: Mike Touloumtzis , Charlie Flynn , > linux-arm@vger.rutgers.edu, handhelds@handhelds.org > Subject: Re: [Handhelds] Re: Touch Screen Driver Generic Interface for all > Linux SA11x0 platforms. > ----- > > There are two interfaces in X that have to be built: one in which the touch > > screen is being used as the primary pointer, and then some other way to > > deal with it in all its glory, almost certainly via the X Input extension. > > I've been thinking more about input recently, and it's less than clear > that the input extension is sufficient for pen-based devices. Because the > input device is so limited, I believe that a significant amount of policy > will be required to distinguish between gestures intended as text input > and gestures intended for pointer input. > > In addition, we need support for a digital ink "overlay". One of the > important HWR lessons I learned from the Itsy was that graffiti with > feedback is much more reliable than without. > > It's almost as if a separate app should be reading the touch screen and > selectively synthesizing pointer and keyboard events; drawing digital > ink on the screen to help make HWR usable. Perhaps a portion of this app > could be done within the X server using a grab/queuing mechanism similar > to the core grabs. > > Here's an idea -- have pen-down events cause raw input to be directed at > the external agent and simultaneously queued within the server. The agent > could then monitor the gesture and at some point decide whether to echo > with digital ink, and finally decide whether to forward the entire queued > event stream on to the X pointer input queue or send it along for HWR. The > server could echo the ink itself or we could let the agent generate X > protocol for that. > > keithp@suse.com XFree86 Core Team SuSE, Inc. > > > _______________________________________________ > Handhelds mailing list > Handhelds@handhelds.org > http://handhelds.org/mailman/listinfo/handhelds -- Jim Gettys Technology and Corporate Development Compaq Computer Corporation jg@pa.dec.com unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Wed Jul 12 20:50:02 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13CSW7-0003hJ-00 for linux-arm-archive@lists.arm.linux.org.uk; Wed, 12 Jul 2000 20:50:00 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id C807A15D90; Wed, 12 Jul 2000 21:48:11 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Wed, 12 Jul 2000 15:34:29 -0400 Received: by vger.rutgers.edu id ; Wed, 12 Jul 2000 15:33:40 -0400 Received: from [38.149.17.171] ([38.149.17.171]:2968 "HELO ltc.com") by vger.rutgers.edu with SMTP id ; Wed, 12 Jul 2000 15:33:21 -0400 Received: from gw1.ltc.com (gw1.ltc.com [38.149.17.163]) by ltc.com (NTMail 3.03.0017/1.afdd) with ESMTP id pa313471 for ; Wed, 12 Jul 2000 15:49:15 -0400 Message-ID: <072001bfec39$eaad4c20$0701010a@ltc.com> From: "Bradley D. LaRonde" To: "Jim Gettys" , "Mike Touloumtzis" Cc: "Charlie Flynn" , , References: <200007121815.LAA03539@pachyderm.pa.dec.com> Subject: Re: [Handhelds] Re: Touch Screen Driver Generic Interface for all Linux SA11x0 platforms. Date: Wed, 12 Jul 2000 15:46:48 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu ----- Original Message ----- From: "Jim Gettys" To: "Mike Touloumtzis" Cc: "Charlie Flynn" ; ; Sent: Wednesday, July 12, 2000 2:15 PM Subject: Re: [Handhelds] Re: Touch Screen Driver Generic Interface for all Linux SA11x0 platforms. > > A driver API should be clear about whether it normalizes coordinates > > (in which case it must be possible to feed it calibration points from > > a userspace app) or whether it passes raw digitizer input to higher > > layers (in which case those layers must have hardware-dependent > > code--this is the gpm approach). > > > > I believe it is important that things be "sane" when you power up a system. > To me, this means that I need to be told somehow how to convert hardware > device coordinates to something that applications (read X) can use. > > This argues to me to report the raw coordinates to user space, along with > calibration data (which can be approximate when first started, but then > updated with correct values if the user recalibrates the device). /etc/pointercal > Since you might (or might not) run a calibration application under a window > system, I think there should be a way to set the default calibration > information in the driver, rather than have to recalibrate for each > application that comes along. In some sense, this is rediculous (since > all the calls would be doing is saving information for later), but the > practical impact is large. Saving the information between processes is > non-trivial... echo ... > /etc/pointercal Regards, Brad unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Wed Jul 12 20:58:02 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13CSds-0003r0-00 for linux-arm-archive@lists.arm.linux.org.uk; Wed, 12 Jul 2000 20:58:02 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 02BFD15E17; Wed, 12 Jul 2000 21:57:49 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Wed, 12 Jul 2000 15:42:30 -0400 Received: by vger.rutgers.edu id ; Wed, 12 Jul 2000 15:39:58 -0400 Received: from [63.224.253.61] ([63.224.253.61]:61518 "EHLO orestes.keithp.com") by vger.rutgers.edu with ESMTP id ; Wed, 12 Jul 2000 15:38:52 -0400 Received: from orestes.keithp.com (localhost [127.0.0.1]) by orestes.keithp.com (8.9.3/8.9.3) with ESMTP id MAA14882; Wed, 12 Jul 2000 12:51:00 -0700 Message-Id: <200007121951.MAA14882@orestes.keithp.com> X-Mailer: exmh version 2.0.2 2/24/98 To: jg@pa.dec.com (Jim Gettys) Cc: Keith Packard , Mike Touloumtzis , Charlie Flynn , linux-arm@vger.rutgers.edu, handhelds@handhelds.org Subject: Re: [Handhelds] Re: Touch Screen Driver Generic Interface for all Linux SA11x0 platforms. From: Keith Packard In-reply-to: Your message of "Wed, 12 Jul 2000 12:38:22 PDT." <200007121938.MAA19606@pachyderm.pa.dec.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 12 Jul 2000 12:51:00 -0700 Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu > So what you are saying is that something like xscribble becomes central > to input in general on handheld devices: it takes relatively raw input > and then tells X what to do when it needs to. Building it into the > core X server seems wrong to me: by definition, we won't get it right: > I think we should regard it as though it were a window manager: a separate > application providing some of the UI. With help from the server for queuing and resending events. One tricky part will be to get it to work in the presence of server grabs... > The issue I see is how to arbitrate among more than one application that > might want/need the high resolution digitizer device... That's separate from input management, lets see if that can be made to use the X input extension. keithp@suse.com XFree86 Core Team SuSE, Inc. unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Wed Jul 12 20:58:49 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13CSee-0003rv-00 for linux-arm-archive@lists.arm.linux.org.uk; Wed, 12 Jul 2000 20:58:49 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 4A75315E22; Wed, 12 Jul 2000 21:58:37 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Wed, 12 Jul 2000 15:44:42 -0400 Received: by vger.rutgers.edu id ; Wed, 12 Jul 2000 15:42:29 -0400 Received: from [205.250.170.220] ([205.250.170.220]:4718 "EHLO xanadu.vip.ca") by vger.rutgers.edu with ESMTP id ; Wed, 12 Jul 2000 15:41:39 -0400 Date: Wed, 12 Jul 2000 15:51:57 -0400 (EDT) From: Nicolas Pitre To: Jacob Strauss Cc: linux-arm Subject: Re: EEPro100 NICs and EBSA285. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu You need to add all the cache coherency handling into the driver for it to work properly with ARM processors. If you'd use a 2.4.x kernel, everything is already done for you. On 12 Jul 2000, Jacob Strauss wrote: > > This seems to be the same problem I'm having. > Does anyone with a working ebsa-285 setup have it > working on the newer revision of the board > (Intel rather than Dec names, 21285-AB rather than > 21285-AA) > > -Jacob > > Mathias Teikari writes: > > > Hi all, > > > > Has anybody had a working EBSA-285 setup with Intel's EEPro100 NICs? > > > > I am using a 2.2.15 kernel patched with patch-2.2.15-rmk1 (because I > > need a 2.2 kernel at this point) and ebsa285-bios-1.06 w. diff2 > > patch. > > The eepro100 driver is compiled into the kernel because I want to > > mount an NFS root fs. > > > > Now, the problem.. The cards won't initialise properly, or at least > > that is what the kernel thinks. > > > > ... > > POSIX conformance testing by UNIFIX > > PCI: Probing PCI hardware > > pci_scan_bus for bus 0 > > PCI: 00:38 [8086/1229] > > PCI: pci_scan_bus returning with max=00 > > Linux NET4.0 for Linux 2.2 > > Based upon Swansea University Computer Society NET3.039 > > NET4: Unix domain sockets 1.0 for Linux NET4.0. > > NET4: Linux TCP/IP 1.0 for NET4.0 > > IP Protocols: ICMP, UDP, TCP > > TCP: Hash tables configured (ehash 16384 bhash 16384) > > Starting kswapd v 1.5 > > RAM disk driver initialized: 1 RAM disks of 4096K size > > Found Intel i82557 PCI Speedo at I/O 0xe1800000, IRQ 22. > > PCI latency timer (CFLT) is 0x20. > > eepro100.c:v1.09j-t 9/29/99 Donald Becker > > http://cesdis.gsfc.nasa.gov/linux/drivers > > /eepro100.html > > eepro100.c: $Revision: 1.20.2.3 $ 2000/03/02 Modified by Andrey V. > > Savochkin > w.sw.com.sg> and others > > eth0: Intel PCI EtherExpress Pro100 at 0xe1800000, > > 00:90:27:8C:D8:6B, IRQ 22. > > Receiver lock-up bug exists -- enabling work-around. > > Board assembly 721383-006, Physical connectors present: RJ45 > > Primary interface chip i82555 PHY #1. > > Self test failed, status ffffffff: > > Failure to initialize the i82557. > > Verify that the card is in a bus-master capable slot. > > ... > > > > I know that the hardware is OK because it's running when using > > another OS (in house developed mini-OS). > > > > A thought that crossed my mind is address mapping problems > > (PCI-SDRAM et vice-versa) or some other setup of the CSRs. > > > > Any suggestions? > > > > Thanks, > > Mathias > > > > > > > > -- > > +---------------------------------------------------------+ .--. > > | Mathias Teikari mathias.teikari@telscom.ch | |o_o | > > | Ba. Sc. EE. Office Ph: +41 (0)31 376 2030 | |:_/ | > > | SW Development Engineer Mobile Ph: +41 (0)76 541 9449 | // \ \ > > | Telscom AG Sandrainstr. 17, CH-3007 Bern | (| | ) > > | | /'\_ _/`\ > > +---------------- http://www.telscom.ch ------------------+ \___)=(___/ > > > > > > > > > > unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu > > ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ > > ++ kernel-related discussions. ++ > > unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu > ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ > ++ kernel-related discussions. ++ > unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Wed Jul 12 21:00:01 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13CSfU-0003tH-00 for linux-arm-archive@lists.arm.linux.org.uk; Wed, 12 Jul 2000 20:59:48 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 068D715DE8; Wed, 12 Jul 2000 21:59:29 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Wed, 12 Jul 2000 15:45:34 -0400 Received: by vger.rutgers.edu id ; Wed, 12 Jul 2000 15:44:52 -0400 Received: from rover.village.org ([204.144.255.49]:4948 "EHLO rover.village.org") by vger.rutgers.edu with ESMTP id ; Wed, 12 Jul 2000 15:42:56 -0400 Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA54688; Wed, 12 Jul 2000 13:55:05 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA17345; Wed, 12 Jul 2000 13:54:57 -0600 (MDT) Message-Id: <200007121954.NAA17345@harmony.village.org> To: jg@pa.dec.com (Jim Gettys) Subject: Re: [Handhelds] Re: Touch Screen Driver Generic Interface for all Linux SA11x0 platforms. Cc: Keith Packard , Mike Touloumtzis , Charlie Flynn , linux-arm@vger.rutgers.edu, handhelds@handhelds.org In-reply-to: Your message of "Wed, 12 Jul 2000 12:38:22 PDT." <200007121938.MAA19606@pachyderm.pa.dec.com> References: <200007121938.MAA19606@pachyderm.pa.dec.com> Date: Wed, 12 Jul 2000 13:54:56 -0600 From: Warner Losh Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu In message <200007121938.MAA19606@pachyderm.pa.dec.com> Jim Gettys writes: : So what you are saying is that something like xscribble becomes central : to input in general on handheld devices: it takes relatively raw input : and then tells X what to do when it needs to. Building it into the : core X server seems wrong to me: by definition, we won't get it right: : I think we should regard it as though it were a window manager: a separate : application providing some of the UI. : : The issue I see is how to arbitrate among more than one application that : might want/need the high resolution digitizer device... We'll certainly : be running something like scribble continuously, but other apps may need : more than what the X core protocol gives them. If the Xinput stuff can : adaquately handle this situation (other applications in addition to : the scribble app), then we have a rational course of action. : : I guess it is time to go look at the Input extension and see if it can : deal with digitizers adequately in the general case and whether it has : any grab/replay notion. My book is at home, I'll try to remember to get : a copy and stare at it some tomorrow. For what is worth.... I have a program that will read the newton keyboard input stream and feed it to the X server via the XInput extention. It deals well with all key events that I throw at it, as well as dealing fairly well with the kludge mouse events that I had in it for a while (I ripped them out because I could more easily do mouselike things with the keyboard via window manager mappings, etc). This stuff is much lower resolution than the digitizer input that you're talking about, but it does show that at least investigation down this path might be warranted. This works well. It certaily is entertaining to have two different keyboards that both do the right thing. I'm even able to use the serial keyboard on machine X to control the X server on machine Y. It is very flexible, at least for keyboard input. I'd imagine that scribble would recognize the drawn letters and conver them to key press key release events. I'd also imagine that a virtual keyboard would do the same sort of thing. Warner unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Wed Jul 12 21:08:43 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13CSoD-00047Y-00 for linux-arm-archive@lists.arm.linux.org.uk; Wed, 12 Jul 2000 21:08:43 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 6229615DD4; Wed, 12 Jul 2000 22:08:11 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Wed, 12 Jul 2000 15:49:37 -0400 Received: by vger.rutgers.edu id ; Wed, 12 Jul 2000 15:49:16 -0400 Received: from mail1.digital.com ([204.123.2.50]:1999 "EHLO mail1.digital.com") by vger.rutgers.edu with ESMTP id ; Wed, 12 Jul 2000 15:48:39 -0400 Received: from pachyderm.pa.dec.com (pachyderm.pa.dec.com [16.4.16.23] (may be forged)) by mail1.digital.com (8.9.2/8.9.3/WV2.0h) with ESMTP id NAA24757; Wed, 12 Jul 2000 13:00:52 -0700 (PDT) Received: by pachyderm.pa.dec.com; id NAA19830; Wed, 12 Jul 2000 13:00:51 -0700 (PDT) Date: Wed, 12 Jul 2000 13:00:51 -0700 (PDT) From: jg@pa.dec.com (Jim Gettys) Message-Id: <200007122000.NAA19830@pachyderm.pa.dec.com> X-Mailer: Pachyderm (client pachyderm.pa-x.dec.com, user jg) To: Warner Losh Cc: jg@pa.dec.com (Jim Gettys), Keith Packard , Mike Touloumtzis , Charlie Flynn , linux-arm@vger.rutgers.edu, handhelds@handhelds.org In-Reply-To: <200007121954.NAA17345@harmony.village.org> Subject: Re: [Handhelds] Re: Touch Screen Driver Generic Interface for all Linux SA11x0 platforms. Mime-Version: 1.0 Content-Type: text/plain Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu > > I'd imagine that scribble would recognize the drawn letters and conver > them to key press key release events. I'd also imagine that a virtual > keyboard would do the same sort of thing. > This is exactly how xscribble works: the source is in the handhelds.org CVS repository. So you don't need to imagine: you need to compile and run it instead.... xscribble synthesizes input sends it back to the X server to go to the right application. xscribble is the name of the application that does this that we've demoed on Itsy, and which is now on the iPAQ (and feel free to port it elsewhere). We haven't done a virtual keyboard (yet). Any volunteers? - Jim -- Jim Gettys Technology and Corporate Development Compaq Computer Corporation jg@pa.dec.com unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Wed Jul 12 21:09:48 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13CSpG-00048r-00 for linux-arm-archive@lists.arm.linux.org.uk; Wed, 12 Jul 2000 21:09:48 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id BC5EB15DD4; Wed, 12 Jul 2000 22:09:31 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Wed, 12 Jul 2000 15:54:48 -0400 Received: by vger.rutgers.edu id ; Wed, 12 Jul 2000 15:52:22 -0400 Received: from PACIFIC-CARRIER-ANNEX.MIT.EDU ([18.69.0.28]:4361 "HELO MIT.EDU") by vger.rutgers.edu with SMTP id ; Wed, 12 Jul 2000 15:52:00 -0400 Received: from GRAND-CENTRAL-STATION.MIT.EDU by MIT.EDU with SMTP id AA06022; Wed, 12 Jul 00 16:04:50 EDT Received: from melbourne-city-street.MIT.EDU (MELBOURNE-CITY-STREET.MIT.EDU [18.69.0.45]) by grand-central-station.MIT.EDU (8.9.2/8.9.2) with ESMTP id QAA17833; Wed, 12 Jul 2000 16:04:15 -0400 (EDT) Received: from baba-yaga.mit.edu (IDENT:root@BABA-YAGA.MIT.EDU [18.244.1.164]) by melbourne-city-street.MIT.EDU (8.9.3/8.9.2) with ESMTP id QAA10279; Wed, 12 Jul 2000 16:04:14 -0400 (EDT) Received: by baba-yaga.mit.edu (8.9.3/4.7) id QAA18978; Wed, 12 Jul 2000 16:04:14 -0400 To: Nicolas Pitre Cc: linux-arm Subject: Re: EEPro100 NICs and EBSA285. References: In-Reply-To: Nicolas Pitre's message of "Wed, 12 Jul 2000 15:51:57 -0400 (EDT)" From: Jacob Strauss Date: 12 Jul 2000 16:04:14 -0400 Message-Id: Lines: 15 X-Mailer: Gnus v5.7/Emacs 20.5 Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Yes, I've been using 2.4.0-test3-pre7-rmk1, with the both 3c905c and eepro100, and tried turning the dcache off (nocache_setup in mm-armv.c) with no changes. So I think that ought to rule out cache problems. -Jacob Nicolas Pitre writes: > You need to add all the cache coherency handling into the driver for it to > work properly with ARM processors. > > If you'd use a 2.4.x kernel, everything is already done for you. > > unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Thu Jul 13 10:06:57 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13CexN-0007uA-00 for linux-arm-archive@lists.arm.linux.org.uk; Thu, 13 Jul 2000 10:06:57 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 243AE15F0C; Thu, 13 Jul 2000 11:05:21 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Thu, 13 Jul 2000 04:52:19 -0400 Received: by vger.rutgers.edu id ; Thu, 13 Jul 2000 04:52:10 -0400 Received: from smtp2.fr.uu.net ([194.98.0.8]:62464 "HELO mail.fr.uu.net") by vger.rutgers.edu with SMTP id ; Thu, 13 Jul 2000 04:51:53 -0400 Received: from CarlCox.iway.fr (carlcox.iway.fr [194.98.0.128]) by mail.fr.uu.net (Postfix) with ESMTP id 572AA32861 for ; Thu, 13 Jul 2000 11:04:05 +0200 (MET DST) Received: from vad ([194.98.253.47]) by CarlCox.iway.fr (8.9.3/8.8.7) with SMTP id LAA11126298 for ; Thu, 13 Jul 2000 11:04:19 +0200 (METDST) From: "Vadim Lebedev" To: Subject: RE: [Handhelds] Re: Touch Screen Driver Generic Interface for all Linux SA11x0 platforms. Date: Thu, 13 Jul 2000 11:03:52 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Importance: Normal In-Reply-To: <396CC47B.2DEB0C72@cotw.com> Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Just my 2 cents I think that it will be good idea to design the API not only fow only for 2D tablets but also for 3D (or maybe even generic N-D) input devices.... Vadim -----Original Message----- From: owner-linux-arm@vger.rutgers.edu [mailto:owner-linux-arm@vger.rutgers.edu]On Behalf Of Steve Hill Sent: mercredi 12 juillet 2000 21:18 To: Paul Koning Cc: jg@pa.dec.com; miket@bluemug.com; flynn@ozy.dec.com; linux-arm@vger.rutgers.edu; handhelds@handhelds.org Subject: Re: [Handhelds] Re: Touch Screen Driver Generic Interface for all Linux SA11x0 platforms. Paul Koning wrote: > > Of course accuracy isn't anywhere near that, but so long as the device > is monotonic, having the extra bits is potentially useful. > I would agree. > Steve> I used tablets that were 12"x12" and 36"x24", but I have seen > Steve> them as large as 48"x36". > > I've seen them quite a lot bigger than that. I remember pictures of > tablets used for work on maps that were clearly bigger than a standard > old-time draftman's drafting table. Maybe six feet or so longest > dimension, perhaps even more. > Whoops, I forgot about the mapping agencies too. > My strong prerefence is to play it safe. Squeezing coordinates into > 16 bits doesn't buy much and it's sufficiently close to the edge that > 32 bits is clearly the safer answer. > You've got my vote for it. > I vaguely remember seeing mention of Wacom support in Linux and > possibly in X. Certainly that device would be an important test case > for any API, along with the perhaps more familiar architect-style puck > tablets. The sort of parameters that the Wacom device sends relate to > its need to emulate artist tools. Take a look at the "airbrush". I > don't have one, my Wacom is too old. But a regular "double action" > airbrush (the non-computer kind) has two control inputs apart from > position: air volume and paint volume, which are independent. And > position is in three coordinates, not just two (distance from the > paper matters a lot). If the Wacom device emulates all that, it means > that each sample would consist of five analog values (x, y, z, air, > paint). > Owen Tayler maintains the XInput HOWTO document which you can find at (http://www.gtk.org/~otaylor/xinput/howto/). I haven't looked at in a while though. It appears support is there for Wacom and Summagraphics just to name a few. This uses X to handle the data i.e. the user land side which goes back to an earlier comment by Brad that the data should come raw from the kernel to be handled by the application. > Hm. Off the wall thought. Would it make sense for a digitizer API to > be applicable to 3d input devices as well, things like 3d pointers, > sensor gloves, stuff like that? There seems to be a lot of overlap, > but it may be too much of a distraction. > I would have to say no. Something says to me "no" because things start popping in my head like Euler angles, infancy IMHO of 3d input devices, etc. I would be interested in other peoples thoughts, but we should probably start a different thread. -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' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Thu Jul 13 20:01:55 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13CoF8-0001QK-00 for linux-arm-archive@lists.arm.linux.org.uk; Thu, 13 Jul 2000 20:01:55 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 48DD316029; Thu, 13 Jul 2000 20:54:32 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Thu, 13 Jul 2000 14:33:23 -0400 Received: by vger.rutgers.edu id ; Thu, 13 Jul 2000 14:23:12 -0400 Received: from h0000c06cf87e.ne.mediaone.net ([24.147.212.45]:2041 "EHLO compaq.parker.boston.ma.us") by vger.rutgers.edu with ESMTP id ; Thu, 13 Jul 2000 14:22:12 -0400 Received: from p2.parker.boston.ma.us (p2 [192.245.5.16]) by compaq.parker.boston.ma.us (8.8.5/8.8.5) with ESMTP id OAA15430; Thu, 13 Jul 2000 14:34:38 -0400 Received: from p2.parker.boston.ma.us (localhost [127.0.0.1]) by p2.parker.boston.ma.us (8.9.3/8.8.8) with ESMTP id OAA24238; Thu, 13 Jul 2000 14:34:38 -0400 (EDT) (envelope-from brad@p2.parker.boston.ma.us) Message-Id: <200007131834.OAA24238@p2.parker.boston.ma.us> To: linux-arm-kernel@lists.arm.linux.org.uk, linux-usb-devel@lists.sourceforge.net Cc: linux-arm@vger.rutgers.edu, sa1100-linux@pa.dec.com Subject: port of ARM SA-1100 itsy usb function driver to 2.4.0-test2 Date: Thu, 13 Jul 2000 14:34:38 -0400 From: Brad Parker Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Hi, A few people asked about this, so I thought I'd put it up for ftp. I did an basic port of the Itsy usb function driver for the ARM SA-1100 to 2.4.0-test-blah. It's working now on a slightly out of rev 2.4.0-test2 tree. It implements a basic ethernet interface complete with and eth0 interface. I've not tried to pass packets to it (yet) but will in the next week or two. I don't know what the DECWRL folks talked to with it. Persumably they wrote some host code. I plan to implement the other side shortly. It does come up and talk to another usb host, takes an address and gives back it's config info, so the basics are working. here are diffs against a -test2 tree: ftp://ftp.parker.boston.ma.us/pub/arm/usbfunc.diffs.gz here are the raw files: ftp://ftp.parker.boston.ma.us/pub/arm/usbfunc.tar.gz If the diffs fail, I am sorry - I recently discovered that my -test2 may be stock from "ftp.kernel.org" with no/few arm patches. -brad unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Thu Jul 13 20:06:47 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13CoJr-0001Xp-00 for linux-arm-archive@lists.arm.linux.org.uk; Thu, 13 Jul 2000 20:06:47 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 53EDA1602C; Thu, 13 Jul 2000 21:00:30 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Thu, 13 Jul 2000 14:44:46 -0400 Received: by vger.rutgers.edu id ; Thu, 13 Jul 2000 14:43:42 -0400 Received: from mail2.digital.com ([204.123.2.56]:3593 "EHLO mail2.digital.com") by vger.rutgers.edu with ESMTP id ; Thu, 13 Jul 2000 14:42:53 -0400 Received: from pobox1.pa.dec.com (pobox1.pa.dec.com [16.1.240.19]) by mail2.digital.com (8.9.2/8.9.3/WV2.0h) with SMTP id LAA03476; Thu, 13 Jul 2000 11:55:27 -0700 (PDT) Received: from stowe.pa.dec.com by pobox1.pa.dec.com (5.65v3.2/1.1.10.5/07Nov97-1157AM) id AA25923; Thu, 13 Jul 2000 11:55:27 -0700 Received: by stowe.pa.dec.com; (5.65v4.0/1.1.8.2/06Jun96-0357PM) id AA30339; Thu, 13 Jul 2000 11:55:27 -0700 Date: Thu, 13 Jul 2000 11:55:27 -0700 Message-Id: <200007131855.AA30339@stowe.pa.dec.com> From: Deborah Wallach To: brad@parker.boston.ma.us Cc: linux-arm-kernel@lists.arm.linux.org.uk, linux-usb-devel@lists.sourceforge.net, linux-arm@vger.rutgers.edu, sa1100-linux@pa.dec.com In-Reply-To: <200007131834.OAA24238@p2.parker.boston.ma.us> (message from Brad Parker on Thu, 13 Jul 2000 14:34:38 -0400) Subject: Re: port of ARM SA-1100 itsy usb function driver to 2.4.0-test2 Address: Compaq Computer Corporation; Western Research Laboratory; 250 University Avenue; Palo Alto, CA 94301; USA Phone: 650-617-3315 Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu It implements a basic ethernet interface complete with and eth0 interface. I've not tried to pass packets to it (yet) but will in the next week or two. I don't know what the DECWRL folks talked to with it. Persumably they wrote some host code. I plan to implement the other side shortly. We talk to it using either Linux (2.3.34) on an x86 PC or Windows 95/2000. I haven't used the windows version myself, so I don't know anything about it. Yes, we wrote some host code for the linux setup, but it's flaky (the host machine crashes fairly often while using usb to the itsy), but if you think it would be useful I can see if I can dig it up and get it posted somewhere. -Debby unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Thu Jul 13 20:23:23 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13CoZv-0001rF-00 for linux-arm-archive@lists.arm.linux.org.uk; Thu, 13 Jul 2000 20:23:23 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 9E94B160C6; Thu, 13 Jul 2000 21:15:22 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Thu, 13 Jul 2000 14:58:53 -0400 Received: by vger.rutgers.edu id ; Thu, 13 Jul 2000 14:58:27 -0400 Received: from [12.38.17.9] ([12.38.17.9]:2670 "EHLO mail.aeptec.com") by vger.rutgers.edu with ESMTP id ; Thu, 13 Jul 2000 14:55:33 -0400 Received: by MAIL with Internet Mail Service (5.5.2650.21) id ; Thu, 13 Jul 2000 14:58:50 -0400 Message-ID: <32CC5B62AF0BD2119E4C00A0C9663E221F3BC5@MAIL> From: "Sun, Lei" To: "'linux-arm-kernel@lists.arm.linux.org.uk'" Cc: "'linux-arm@vger.rutgers.edu'" Subject: network problem again Date: Thu, 13 Jul 2000 14:58:40 -0400 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@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Hi all: Sorry for the cross post, I have a linux running in Sa1110 assabet with socket comm. LP-CF ethernetcard. I am using kernel 2.4.0-test1. I played with it for a week until now my eth0 device are up, and everything seems fine, no error message when boot up. thanks for Nico and Jeff for their big help. I found some weird problems regarding the network. 1) when I ping localhost, I can send and get the reply, however I got the warning message when each packet is received "WARING: received unknown ICMP packet" 2) I can logon to other machines through telnet, no problem, however, I can only logon to SA1110 by telnet at the first time, after that the telnet window display "Escape character is ^]" and stucked. it seems the connection is established but the data transmission has some problems. any idea? thank you ! Lei Sun unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Fri Jul 14 14:41:24 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13D5iW-0001i1-00 for linux-arm-archive@lists.arm.linux.org.uk; Fri, 14 Jul 2000 14:41:24 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 0D7E81601A; Fri, 14 Jul 2000 15:40:15 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Fri, 14 Jul 2000 09:26:48 -0400 Received: by vger.rutgers.edu id ; Fri, 14 Jul 2000 09:26:38 -0400 Received: from cvsftp.cotw.com ([208.242.241.39]:2655 "EHLO cvsftp.cotw.com") by vger.rutgers.edu with ESMTP id ; Fri, 14 Jul 2000 09:26:25 -0400 Received: from cotw.com (IDENT:samcconn@ptecdev2.ptec.com [192.168.10.4]) by cvsftp.cotw.com (8.9.3/8.9.3) with ESMTP id IAA02094 for ; Fri, 14 Jul 2000 08:39:36 -0500 Message-ID: <396F18A8.8D8F4091@cotw.com> Date: Fri, 14 Jul 2000 08:42:00 -0500 From: S A McConnell Reply-To: samcconn@cotw.com X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.14 i686) X-Accept-Language: en MIME-Version: 1.0 To: linux-arm@vger.rutgers.edu Subject: Need method to combine multiple binary images into one. (ld?) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu I am showing my lack of Linux/Unix experience.... I have five different binary images. To speed and simplify the loading/Flashing process I would like to combine the images into a single file placing each image at a set location. ( Image1 @ 0x0, Image2 @ 0x3800, Image3 @ 0x10000....) There will be holes between each image. The images are all ARM binaries. The command 'file' describes them as 'data' files. I tried to us arm-linux-ld but it complained about not knowing the format. I looked in the documentation but did not see a way to tell the linker to treat it as just data. $file image1 image1:data $arm-linux-gcc -Timage.ld image1 image2 image3 image4 image5 image1: file not recognized: File format not recognized collect2: ld returned 1 exit status INPUT(image1 image2 image3 image4 image5) OUTPUT (bigimage) SECTIONS { output : { image1 . = 0x3800; image2 . = 0x4000; image3 . = 0x1000; image4 . = 0x100000; image5 } } ------------------------------- Does anyone have a suggestion about how to do this with or without the linker? Thanks, SAM unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Fri Jul 14 16:29:15 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13D7Ot-0003d7-00 for linux-arm-archive@lists.arm.linux.org.uk; Fri, 14 Jul 2000 16:29:15 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 5175B160B0; Fri, 14 Jul 2000 17:24:54 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Fri, 14 Jul 2000 11:09:28 -0400 Received: by vger.rutgers.edu id ; Fri, 14 Jul 2000 11:08:08 -0400 Received: from dns1.cyberiansoftware.com ([24.229.50.7]:3892 "HELO cyberiansoftware.com") by vger.rutgers.edu with SMTP id ; Fri, 14 Jul 2000 11:07:04 -0400 Received: (qmail 31952 invoked from network); 14 Jul 2000 15:20:03 -0000 Received: from other.cyberiansoftware.com (HELO cyberiansoftware.com) (192.168.1.3) by cyberiansoftware.com with SMTP; 14 Jul 2000 15:20:03 -0000 Message-ID: <396F2FC2.4058D8A5@cyberiansoftware.com> Date: Fri, 14 Jul 2000 11:20:34 -0400 From: Tom Walsh X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.12-20 i686) X-Accept-Language: en MIME-Version: 1.0 To: samcconn@cotw.com Cc: linux-arm@vger.rutgers.edu Subject: Re: Need method to combine multiple binary images into one. (ld?) References: <396F18A8.8D8F4091@cotw.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu S A McConnell wrote: > > I am showing my lack of Linux/Unix experience.... > > I have five different binary images. To speed and simplify the > loading/Flashing process I would like to combine the images into a > single file placing each image at a set location. ( Image1 @ 0x0, Image2 > @ 0x3800, Image3 @ 0x10000....) There will be holes between each image. > > The images are all ARM binaries. The command 'file' describes them as > 'data' files. > > I tried to us arm-linux-ld but it complained about not knowing the > format. I looked in the documentation but did not see a way to tell the > linker to treat it as just data. > > $file image1 > image1:data > > $arm-linux-gcc -Timage.ld image1 image2 image3 image4 image5 > image1: file not recognized: File format not recognized > collect2: ld returned 1 exit status > > INPUT(image1 image2 image3 image4 image5) > > OUTPUT (bigimage) > > SECTIONS > { > output : > { > image1 > . = 0x3800; > image2 > . = 0x4000; > image3 > . = 0x1000; > image4 > . = 0x100000; > image5 > } > } > > ------------------------------- > Does anyone have a suggestion about how to do this with or without the > linker? Well, you are on the right track if the images were object files which contained symbolic info identifying segments within the files. If that were the case, then you would need to create and 'ld' file that specified which segment got placed into where. But, if your file is pure, raw, binary data, I would suggest that you write a quick program, or script, to append extra bytes to each image, then cat them together. Use 'dd' to spec the number & value of the appended padding. TomW > > Thanks, > SAM > > unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu > ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ > ++ kernel-related discussions. ++ -- Tom Walsh - WN3L - Embedded Systems Consultant 'www.openhardware.net', 'www.cyberiansoftware.com' "Windows? No thanks, I have work to do..." unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Fri Jul 14 17:01:44 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13D7uK-00044m-00 for linux-arm-archive@lists.arm.linux.org.uk; Fri, 14 Jul 2000 17:01:44 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id AA1D0160F1; Fri, 14 Jul 2000 17:59:45 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Fri, 14 Jul 2000 11:43:16 -0400 Received: by vger.rutgers.edu id ; Fri, 14 Jul 2000 11:42:51 -0400 Received: from penguin-ext.wise.edt.ericsson.se ([194.237.142.110]:52576 "EHLO penguin-ext.wise.edt.ericsson.se") by vger.rutgers.edu with ESMTP id convert rfc822-to-8bit; Fri, 14 Jul 2000 11:41:38 -0400 Received: from esealnt409.al.sw.ericsson.se (esealnt409.al.sw.ericsson.se [153.88.251.32]) by penguin.wise.edt.ericsson.se (8.10.1/8.10.1/WIREfire-1.3) with ESMTP id e6EFseM15437 for ; Fri, 14 Jul 2000 17:54:40 +0200 (MEST) Received: from SMTP ([153.88.251.32]) by esealnt409.al.sw.ericsson.se with Microsoft SMTPSVC(5.0.2172.1); Fri, 14 Jul 2000 17:54:40 +0200 Received: from esealnt743.al.sw.ericsson.se ([153.88.251.13]) by 153.88.251.32 (Norton AntiVirus for Internet Email Gateways 1.0) ; Fri, 14 Jul 2000 15:54:40 0000 (GMT) Received: by esealnt743.al.sw.ericsson.se with Internet Mail Service (5.5.2651.58) id ; Fri, 14 Jul 2000 17:54:39 +0200 Message-ID: From: "Arjan Opmeer (EMN)" To: "'linux-arm@vger.rutgers.edu'" Subject: Spurious characters after kernel boot on Intel dev. board Date: Fri, 14 Jul 2000 17:54:34 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2651.58) Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8BIT X-OriginalArrivalTime: 14 Jul 2000 15:54:40.0310 (UTC) FILETIME=[D1B42D60:01BFEDAB] Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Hi, I just received my Intel SA1110/SA1111 development board and have succeeded in booting and running a Linux kernel on it using the angelboot utility and the ramdisk image from Nico. But after the kernel booting messages have passed by and the init program is run there are all sorts of extra characters in the output of my minicom session. I can log in as root and execute commands just fine, but the output doesn't make much sense. Below is an example of what it looks like when I log in as root and execute the command 'ls ..'. (Provided MS Outlook what I have to use here :( doesn't f*ck things up....) VFS: Mounted root (ext2 filesystem). IN%£M.ùveÉ.Kzr.&æÑ3..bo½¢Jr;ÿ 68k initê IN%£M.ùEnt..Jr;.&asc*²+b.... ÿSÑ .¢Jr;.6.*j.Æ..¶¶.9:.ÿ sysl½:#ÿ ÿSÑ .¢Jr;...R4..seɲK*...ù i.+¢"ÿ ÿ ÿLi.«..Æ..¶.o:.ÿrÿoÿoÿtÿ ÿ[r½z¢..ZM[7../r½z¢ê.ñlÿs .ÿ.ÿ ÿl½.£Zd.S7..de....2.. eÑ...2.. var....2.. usr....2.. l¥.kL.nl.n bi....2.. r½z¢...2.. r....2... Now my question is, is there a way to clean up the output of the development board? Did I miss a setting or trick somewhere that can perform this task? Is there a FAQ I should have read? Thanks in advance for any response, Best regards, Arjan Opmeer P.s. Could the kind soul answering this question also please cc a reply to my email address as I am not subscribed to this list (yet). (I really don't mind being subscribed to a mailing list, but I don't know whether I want to use MS Outlook on an Exchange server to receive the email. I'll have to look into that...) unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Fri Jul 14 17:30:12 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13D8Ls-0004W7-00 for linux-arm-archive@lists.arm.linux.org.uk; Fri, 14 Jul 2000 17:30:12 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id AE358160DE; Fri, 14 Jul 2000 18:27:00 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Fri, 14 Jul 2000 12:11:52 -0400 Received: by vger.rutgers.edu id ; Fri, 14 Jul 2000 12:10:22 -0400 Received: from [216.85.232.66] ([216.85.232.66]:3177 "EHLO blazieresearch.com") by vger.rutgers.edu with ESMTP id ; Fri, 14 Jul 2000 12:09:44 -0400 Received: from cpq800.blazieresearch.com (cpq800 [216.85.232.67]) by blazieresearch.com (8.9.3/8.8.7) with ESMTP id MAA21391; Fri, 14 Jul 2000 12:21:07 -0400 Received: by CPQ800 with Internet Mail Service (5.5.2650.10) id <3465WL9T>; Fri, 14 Jul 2000 12:19:40 -0400 Message-ID: <412E1CF8088BD211AD5100805FAD9A800CD27A@CPQ800> From: Jim Kasper To: "'samcconn@cotw.com '" Cc: "'linux-arm@vger.rutgers.edu '" Subject: RE: Need method to combine multiple binary images into one. (ld?) Date: Fri, 14 Jul 2000 12:19:38 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.10) Content-Type: text/plain; charset="windows-1252" Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Sam, I had same problem, and while I am sure there must be a more elegant way, I ended up doing as Tom suggested. I did a make on the images seperatly, The boot part set with ld_script to 0x00, the second image set to a ram location. My little script then checked sizes and combined images. #!/bin/sh # little script gets size of first from current dir # and size of second from different source tree #copies first to a file, pads it out, then adds second size_boot=`ls -l boot_obj|awk '{print $5}' ` size_top=`ls -l /usr/src/zblob/src/util.obj|awk '{print $5}' ` #copy first object dd if=boot_obj of=sboot #pad with zeroes to 64K dd bs=1c if=/dev/zero of=sboot seek=$size_boot count=$((65536-$size_boot)) # seek to boundry, copy second file dd bs=1c if=/usr/src/zblob/src/util.obj of=sboot seek=65536c count=$size_top uuencode sboot freddy > sboot.uu -----Original Message----- From: Tom Walsh To: samcconn@cotw.com Cc: linux-arm@vger.rutgers.edu Sent: 07/14/00 11:20 Subject: Re: Need method to combine multiple binary images into one. (ld?) S A McConnell wrote: > > I am showing my lack of Linux/Unix experience.... > > I have five different binary images. To speed and simplify the > loading/Flashing process I would like to combine the images into a > single file placing each image at a set location. ( Image1 @ 0x0, Image2 > @ 0x3800, Image3 @ 0x10000....) There will be holes between each image. > > The images are all ARM binaries. The command 'file' describes them as > 'data' files. > > I tried to us arm-linux-ld but it complained about not knowing the > format. I looked in the documentation but did not see a way to tell the > linker to treat it as just data. > > $file image1 > image1:data > > $arm-linux-gcc -Timage.ld image1 image2 image3 image4 image5 > image1: file not recognized: File format not recognized > collect2: ld returned 1 exit status > > INPUT(image1 image2 image3 image4 image5) > > OUTPUT (bigimage) > > SECTIONS > { > output : > { > image1 > . = 0x3800; > image2 > . = 0x4000; > image3 > . = 0x1000; > image4 > . = 0x100000; > image5 > } > } > > ------------------------------- > Does anyone have a suggestion about how to do this with or without the > linker? Well, you are on the right track if the images were object files which contained symbolic info identifying segments within the files. If that were the case, then you would need to create and 'ld' file that specified which segment got placed into where. But, if your file is pure, raw, binary data, I would suggest that you write a quick program, or script, to append extra bytes to each image, then cat them together. Use 'dd' to spec the number & value of the appended padding. TomW > > Thanks, > SAM > > unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu > ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ > ++ kernel-related discussions. ++ -- Tom Walsh - WN3L - Embedded Systems Consultant 'www.openhardware.net', 'www.cyberiansoftware.com' "Windows? No thanks, I have work to do..." unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Fri Jul 14 17:37:17 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13D8Si-0004bh-00 for linux-arm-archive@lists.arm.linux.org.uk; Fri, 14 Jul 2000 17:37:17 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id E1898160FC; Fri, 14 Jul 2000 18:34:04 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Fri, 14 Jul 2000 12:18:04 -0400 Received: by vger.rutgers.edu id ; Fri, 14 Jul 2000 12:17:44 -0400 Received: from POST.ICES.CMU.EDU ([128.2.205.86]:34975 "HELO post.ices.cmu.edu") by vger.rutgers.edu with SMTP id ; Fri, 14 Jul 2000 12:15:23 -0400 Received: from VANCOUVER.ICES.CMU.EDU by post.ices.cmu.edu id aa26845; 14 Jul 2000 12:28 EDT Message-ID: <396EEC35.AC6C8297@cs.cmu.edu> Date: Fri, 14 Jul 2000 06:32:21 -0400 From: John G Dorsey Organization: Carnegie Mellon University X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.10 i686) X-Accept-Language: en MIME-Version: 1.0 To: "Arjan Opmeer (EMN)" Cc: "'linux-arm@vger.rutgers.edu'" Subject: Re: Spurious characters after kernel boot on Intel dev. board References: Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu "Arjan Opmeer (EMN)" wrote: > VFS: Mounted root (ext2 filesystem). > IN%M.ve.Kzr.&3..boJr; 68k init > IN%M.Ent..Jr;.&asc*+b.... > S > .Jr;.6.*j....9:. sysl:# > S > .Jr;...R4..seK*... i.+" > > Li......o:.root > [rz..ZM[7../rz.ls .. > l.Zd.S7..de....2.. e...2.. var....2.. usr....2.. l.kL.nl.n bi....2.. rz...2.. r....2... You're using 2.4.0-test2-ac1-rmk2-np3, aren't you? =) (I thought I was losing it yesterday when both my Assabet and Neponset started to do this.) Back out to -np1; -np3 has some fairly substantial changes in the serial character driver which may require some sorting. -jd unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Fri Jul 14 18:47:33 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13D9Yj-0005Wd-00 for linux-arm-archive@lists.arm.linux.org.uk; Fri, 14 Jul 2000 18:47:33 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id E351A160BF; Fri, 14 Jul 2000 19:39:28 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Fri, 14 Jul 2000 13:05:12 -0400 Received: by vger.rutgers.edu id ; Fri, 14 Jul 2000 13:04:23 -0400 Received: from crl.dec.com ([192.58.206.2]:2975 "EHLO crl.dec.com") by vger.rutgers.edu with ESMTP id ; Fri, 14 Jul 2000 13:02:42 -0400 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 NAA06574; Fri, 14 Jul 2000 13:15:39 -0400 (EDT) Received: by crlwebmail.crl.dec.com with Internet Mail Service (5.5.2650.21) id ; Fri, 14 Jul 2000 13:20:35 -0400 Message-ID: From: George France To: "'Tom Walsh'" , samcconn@cotw.com Cc: linux-arm@vger.rutgers.edu Subject: RE: Need method to combine multiple binary images into one. (ld?) Date: Fri, 14 Jul 2000 13:15:37 -0400 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@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu arm-linux-objcopy. --George George France, france@crl.dec.com Cambridge Research Laboratory, Compaq Computer Corporation One Cambridgecenter MS: CRL Cambridge, MA 02142 USA -----Original Message----- From: Tom Walsh [mailto:tom@cyberiansoftware.com] Sent: Friday, July 14, 2000 11:21 AM To: samcconn@cotw.com Cc: linux-arm@vger.rutgers.edu Subject: Re: Need method to combine multiple binary images into one. (ld?) S A McConnell wrote: > > I am showing my lack of Linux/Unix experience.... > > I have five different binary images. To speed and simplify the > loading/Flashing process I would like to combine the images into a > single file placing each image at a set location. ( Image1 @ 0x0, Image2 > @ 0x3800, Image3 @ 0x10000....) There will be holes between each image. > > The images are all ARM binaries. The command 'file' describes them as > 'data' files. > > I tried to us arm-linux-ld but it complained about not knowing the > format. I looked in the documentation but did not see a way to tell the > linker to treat it as just data. > > $file image1 > image1:data > > $arm-linux-gcc -Timage.ld image1 image2 image3 image4 image5 > image1: file not recognized: File format not recognized > collect2: ld returned 1 exit status > > INPUT(image1 image2 image3 image4 image5) > > OUTPUT (bigimage) > > SECTIONS > { > output : > { > image1 > . = 0x3800; > image2 > . = 0x4000; > image3 > . = 0x1000; > image4 > . = 0x100000; > image5 > } > } > > ------------------------------- > Does anyone have a suggestion about how to do this with or without the > linker? Well, you are on the right track if the images were object files which contained symbolic info identifying segments within the files. If that were the case, then you would need to create and 'ld' file that specified which segment got placed into where. But, if your file is pure, raw, binary data, I would suggest that you write a quick program, or script, to append extra bytes to each image, then cat them together. Use 'dd' to spec the number & value of the appended padding. TomW > > Thanks, > SAM > > unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu > ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ > ++ kernel-related discussions. ++ -- Tom Walsh - WN3L - Embedded Systems Consultant 'www.openhardware.net', 'www.cyberiansoftware.com' "Windows? No thanks, I have work to do..." unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Fri Jul 14 18:56:25 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13D9hJ-0005dK-00 for linux-arm-archive@lists.arm.linux.org.uk; Fri, 14 Jul 2000 18:56:25 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 50DDC16186; Fri, 14 Jul 2000 19:44:02 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Fri, 14 Jul 2000 13:28:44 -0400 Received: by vger.rutgers.edu id ; Fri, 14 Jul 2000 13:28:04 -0400 Received: from dns1.cyberiansoftware.com ([24.229.50.7]:3909 "HELO cyberiansoftware.com") by vger.rutgers.edu with SMTP id ; Fri, 14 Jul 2000 13:27:19 -0400 Received: (qmail 514 invoked from network); 14 Jul 2000 17:40:25 -0000 Received: from other.cyberiansoftware.com (HELO cyberiansoftware.com) (192.168.1.3) by cyberiansoftware.com with SMTP; 14 Jul 2000 17:40:25 -0000 Message-ID: <396F50A8.39B089DD@cyberiansoftware.com> Date: Fri, 14 Jul 2000 13:40:56 -0400 From: Tom Walsh X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.12-20 i686) X-Accept-Language: en MIME-Version: 1.0 To: George France Cc: samcconn@cotw.com, linux-arm@vger.rutgers.edu Subject: Re: Need method to combine multiple binary images into one. (ld?) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu George France wrote: > > arm-linux-objcopy. I did not want to mention that utility, I do use it for the uClinux on my 68EZ328 based design to create the S19 records to load into my flash. I found the docu on the utility to be a bit cryptic and after experimenting with it, gave up, and kept to the S19 record output it gave. Sometimes 'brute force' is the more elegant approach? ;-) Regards, TomW > > --George > > George France, france@crl.dec.com > Cambridge Research Laboratory, Compaq Computer Corporation > One Cambridgecenter MS: CRL > Cambridge, MA 02142 USA > > -----Original Message----- > From: Tom Walsh [mailto:tom@cyberiansoftware.com] > Sent: Friday, July 14, 2000 11:21 AM > To: samcconn@cotw.com > Cc: linux-arm@vger.rutgers.edu > Subject: Re: Need method to combine multiple binary images into one. > (ld?) > > S A McConnell wrote: > > > > I am showing my lack of Linux/Unix experience.... > > > > I have five different binary images. To speed and simplify the > > loading/Flashing process I would like to combine the images into a > > single file placing each image at a set location. ( Image1 @ 0x0, Image2 > > @ 0x3800, Image3 @ 0x10000....) There will be holes between each image. > > > > The images are all ARM binaries. The command 'file' describes them as > > 'data' files. > > > > I tried to us arm-linux-ld but it complained about not knowing the > > format. I looked in the documentation but did not see a way to tell the > > linker to treat it as just data. > > > > $file image1 > > image1:data > > > > $arm-linux-gcc -Timage.ld image1 image2 image3 image4 image5 > > image1: file not recognized: File format not recognized > > collect2: ld returned 1 exit status > > > > INPUT(image1 image2 image3 image4 image5) > > > > OUTPUT (bigimage) > > > > SECTIONS > > { > > output : > > { > > image1 > > . = 0x3800; > > image2 > > . = 0x4000; > > image3 > > . = 0x1000; > > image4 > > . = 0x100000; > > image5 > > } > > } > > > > ------------------------------- > > Does anyone have a suggestion about how to do this with or without the > > linker? > > Well, you are on the right track if the images were object files which > contained symbolic info identifying segments within the files. If that > were the case, then you would need to create and 'ld' file that > specified which segment got placed into where. > > But, if your file is pure, raw, binary data, I would suggest that you > write a quick program, or script, to append extra bytes to each image, > then cat them together. Use 'dd' to spec the number & value of the > appended padding. > > TomW > > > > > Thanks, > > SAM > > > > unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu > > ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for > ++ > > ++ kernel-related discussions. > ++ > > -- > Tom Walsh - WN3L - Embedded Systems Consultant > 'www.openhardware.net', 'www.cyberiansoftware.com' > "Windows? No thanks, I have work to do..." > > unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu > ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for > ++ > ++ kernel-related discussions. > ++ -- Tom Walsh - WN3L - Embedded Systems Consultant 'www.openhardware.net', 'www.cyberiansoftware.com' "Windows? No thanks, I have work to do..." unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Fri Jul 14 19:30:23 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13DAEB-00066i-00 for linux-arm-archive@lists.arm.linux.org.uk; Fri, 14 Jul 2000 19:30:23 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 6C876161BD; Fri, 14 Jul 2000 20:23:24 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Fri, 14 Jul 2000 14:07:09 -0400 Received: by vger.rutgers.edu id ; Fri, 14 Jul 2000 14:06:47 -0400 Received: from ice.fiftyone.com ([208.225.80.11]:3154 "EHLO ice.ar51.net") by vger.rutgers.edu with ESMTP id ; Fri, 14 Jul 2000 14:06:05 -0400 Received: from server01.asi (akron-80-166.ar51.net [208.225.80.166]) by ice.ar51.net (8.9.3/8.8.7) with ESMTP id OAA24693; Fri, 14 Jul 2000 14:18:55 -0400 Received: by SERVER01 with Internet Mail Service (5.5.2448.0) id <3YXN8CZL>; Fri, 14 Jul 2000 14:20:46 -0400 Message-ID: From: Jeff Sutherland To: "'John G Dorsey'" , "'Arjan Opmeer (EMN)'" Cc: "'linux-arm@vger.rutgers.edu'" Subject: RE: Spurious characters after kernel boot on Intel dev. board Date: Fri, 14 Jul 2000 14:20:40 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu MN)" wrote: > > > VFS: Mounted root (ext2 filesystem). > > IN%M.ve.Kzr.&3..boJr; 68k init > > IN%M.Ent..Jr;.&asc*+b.... > > S > > .Jr;.6.*j....9:. sysl:# > > S > > .Jr;...R4..seK*... i.+" > > > > Li......o:.root > > [rz..ZM[7../rz.ls .. > > l.Zd.S7..de....2.. e...2.. var....2.. usr....2.. > l.kL.nl.n bi....2.. rz...2.. r....2... > > You're using 2.4.0-test2-ac1-rmk2-np3, aren't you? =) > > (I thought I was losing it yesterday when both my Assabet and > Neponset started to do this.) > > Back out to -np1; -np3 has some fairly substantial changes in > the serial character driver which may require some > sorting. > > -jd I was going to suggest checking inittab on the ramdisk to see what the gettys are doing. Looks like something is fooling around with the serial port settings when the tty's are starting up. BTW my -np3 works fine except for that problem Nico mentioned with keyboard escape sequences and the like where two characters are sent back to back in quick succession. No trouble with output, though, and this is at 115200, n, 8, 1. I need to track this one down as we use serial I/O pretty extensively. //Jeff unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Fri Jul 14 19:54:04 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13DAb6-0006SU-00 for linux-arm-archive@lists.arm.linux.org.uk; Fri, 14 Jul 2000 19:54:04 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id E8747161D1; Fri, 14 Jul 2000 20:49:09 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Fri, 14 Jul 2000 14:34:13 -0400 Received: by vger.rutgers.edu id ; Fri, 14 Jul 2000 14:34:07 -0400 Received: from POST.ICES.CMU.EDU ([128.2.205.86]:34993 "HELO post.ices.cmu.edu") by vger.rutgers.edu with SMTP id ; Fri, 14 Jul 2000 14:33:38 -0400 Received: from VANCOUVER.ICES.CMU.EDU by post.ices.cmu.edu id aa27464; 14 Jul 2000 14:46 EDT Message-ID: <396F0CA3.5E20AFB7@cs.cmu.edu> Date: Fri, 14 Jul 2000 08:50:43 -0400 From: John G Dorsey Organization: Carnegie Mellon University X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.10 i686) X-Accept-Language: en MIME-Version: 1.0 To: Jeff Sutherland Cc: "'Arjan Opmeer (EMN)'" , "'linux-arm@vger.rutgers.edu'" Subject: Re: Spurious characters after kernel boot on Intel dev. board References: Content-Type: multipart/mixed; boundary="------------81C3D3C1BEBA5036A8E4452A" Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu This is a multi-part message in MIME format. --------------81C3D3C1BEBA5036A8E4452A Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Jeff Sutherland wrote: > No trouble > with output, though, and this is at 115200, n, 8, 1. I need to track this > one down as we use serial I/O pretty extensively. That's interesting, because it looks to me as though -np3 cannot actually implement that configuration (it doesn't believe in the "n"). The enclosed patch assumes that PARODD (or rather, its absence) does not imply PARENB. It fixes the output strangeness on my Assabet and Assabet+Neponset. -jd --------------81C3D3C1BEBA5036A8E4452A Content-Type: application/x-gzip; name="linux-2.4.0-test2-ac1-rmk2-np3-jd1.patch.gz" Content-Transfer-Encoding: base64 Content-Disposition: inline; filename="linux-2.4.0-test2-ac1-rmk2-np3-jd1.patch.gz" H4sICPUHbzkAA2xpbnV4LTIuNC4wLXRlc3QyLWFjMS1ybWsyLW5wMy1qZDEucGF0Y2gAlVLv b9owEP2M/4o3NrWlaYjDr1EQExTC1k0CBFSatE1RSBywFBJkO2xI/ePnJJ2Gsq1T8+Fyvnv3 /OR7AQ9DmKmYIeJx+sPyhL/TYW/5SRzybZ3HRcOMk4MnuDr9BUFM0/zneGUqOD6mEewWaLfX 6PYoRYNSSgzD+D93Zb1Li/Em6G2v3e21WsX4cAizfXvTgaGjTTEcErwGsEmSCJfAfexHacAg 08MhEQphIvB50e3QS4zns+n9e3c1sm1K3bxIEHICYvAQX1B984QYrVajO2ftzpzFfLZy1lUM UD1V8a0PtWMxMfR9AQt5zNz82jNi28aJGJrUyGRN+TYVDEmq8H3H9KzQBFxCnqRie6SSSTQ6 5oYraJnNRp6NFw+yTlCStBx/yMIvKWaCrwT5V8K0P5XlBqVlB4IfmZCWv/OEJZngXuRKL3uU ul9ezXPYMwM8B3uRFV5C1O61m79N0enSm7cwil/miop+wSs/jLwtLrAYLZ3ZXU1XK/7Ri/A4 wMN6vKTuwuk/QV+dg+eTSa1GzD/Rj0Uyd1Z9YpTbeRWaz7rGhCkm9tojCPiRS73fjSdZgCTW SRpAeIrh2tLg/DiAUid3y5SbHd2se8XjMDHf6XqtT8hPobEqqrMDAAA= --------------81C3D3C1BEBA5036A8E4452A-- unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Fri Jul 14 21:56:05 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13DCVB-00041r-00 for linux-arm-archive@lists.arm.linux.org.uk; Fri, 14 Jul 2000 21:56:05 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 25CAF160DD; Fri, 14 Jul 2000 22:52:13 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Fri, 14 Jul 2000 16:26:11 -0400 Received: by vger.rutgers.edu id ; Fri, 14 Jul 2000 16:25:55 -0400 Received: from [205.250.170.220] ([205.250.170.220]:2013 "EHLO xanadu.vipswitch.com") by vger.rutgers.edu with ESMTP id ; Fri, 14 Jul 2000 16:25:17 -0400 Date: Fri, 14 Jul 2000 16:35:18 -0400 (EDT) From: Nicolas Pitre To: John G Dorsey Cc: Jeff Sutherland , "'Arjan Opmeer (EMN)'" , "'linux-arm@vger.rutgers.edu'" Subject: Re: Spurious characters after kernel boot on Intel dev. board In-Reply-To: <396F0CA3.5E20AFB7@cs.cmu.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu On Fri, 14 Jul 2000, John G Dorsey wrote: > Jeff Sutherland wrote: > > > No trouble > > with output, though, and this is at 115200, n, 8, 1. I need to track this > > one down as we use serial I/O pretty extensively. > > That's interesting, because it looks to me as though -np3 cannot actually > implement that configuration (it doesn't believe in the "n"). Oops... That's surely my fault. What's strange is that the output isn't garbled for me nor Jeff. Only today I received two reports of the serial port being broken but I still can't make it to garble my output. > The enclosed patch assumes that PARODD (or rather, its absence) does not imply > PARENB. It fixes the output strangeness on my Assabet and Assabet+Neponset. Thanks! Now only the receive overflow has to be found... or maybe it's the same problem? ;-) I'll try to confirm that tonight. Nicolas unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Fri Jul 14 22:36:12 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13DD80-0004Xq-00 for linux-arm-archive@lists.arm.linux.org.uk; Fri, 14 Jul 2000 22:36:12 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id E2F8B16289; Fri, 14 Jul 2000 23:30:04 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Fri, 14 Jul 2000 16:58:37 -0400 Received: by vger.rutgers.edu id ; Fri, 14 Jul 2000 16:58:21 -0400 Received: from [205.250.170.220] ([205.250.170.220]:2046 "EHLO xanadu.vipswitch.com") by vger.rutgers.edu with ESMTP id ; Fri, 14 Jul 2000 16:57:45 -0400 Date: Fri, 14 Jul 2000 17:07:49 -0400 (EDT) From: Nicolas Pitre To: S A McConnell Cc: linux-arm@vger.rutgers.edu Subject: Re: Need method to combine multiple binary images into one. (ld?) In-Reply-To: <396F18A8.8D8F4091@cotw.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu On Fri, 14 Jul 2000, S A McConnell wrote: > I am showing my lack of Linux/Unix experience.... > > I have five different binary images. To speed and simplify the > loading/Flashing process I would like to combine the images into a > single file placing each image at a set location. ( Image1 @ 0x0, Image2 > @ 0x3800, Image3 @ 0x10000....) There will be holes between each image. Easily done with: dd if=image1 of=result bs=1k dd if=image2 of=result bs=1k seek=14 dd if=image3 of=result bs=1k seek=64 ... The important thing is to apply each piece in offset order. Nicolas unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Sat Jul 15 00:47:33 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13DFB7-0006QJ-00 for linux-arm-archive@lists.arm.linux.org.uk; Sat, 15 Jul 2000 00:47:33 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id D19E3162BA; Sat, 15 Jul 2000 01:43:51 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Fri, 14 Jul 2000 19:28:37 -0400 Received: by vger.rutgers.edu id ; Fri, 14 Jul 2000 19:27:04 -0400 Received: from [212.219.8.163] ([212.219.8.163]:1960 "HELO inkvine.fluff.org") by vger.rutgers.edu with SMTP id ; Fri, 14 Jul 2000 19:26:30 -0400 Received: from localhost (localhost [127.0.0.1]) by inkvine.fluff.org (Postfix) with ESMTP id D9C384681E for ; Sat, 15 Jul 2000 00:39:41 +0100 (BST) Date: Sat, 15 Jul 2000 00:39:41 +0100 (BST) From: Chris Rutter Reply-To: chris@fluff.org To: ARM Linux mailing list Subject: ARM Linux history Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu I'm trying to compile some sort of history of Linux/ARM, and thus seeking answers to questions like: - What was the very early history of the kernel? - When did binutils and gcc start supporting ARM-based formats? - Where did the first C library with ARM support come from? - (Tangentially) what other Unices ran on ARM before Linux? (I count, I think, NetBSD/arm32, Minix, RISCiX?) (Yes, I know there's some story on Russell's site, but it seems apocryphal.) Anyone who fances a pint (or just some thanks) please drop me the answers to any of these. Oh, yeah; and a credit in an article. c. unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Sat Jul 15 09:40:59 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13DNVL-0000Xu-00 for linux-arm-archive@lists.arm.linux.org.uk; Sat, 15 Jul 2000 09:40:59 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id D6A6516133; Sat, 15 Jul 2000 10:03:38 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Sat, 15 Jul 2000 03:48:58 -0400 Received: by vger.rutgers.edu id ; Sat, 15 Jul 2000 03:48:39 -0400 Received: from p39-cordelia-gui.tch.enablis.net ([212.250.233.39]:1622 "EHLO caramon.arm.linux.org.uk") by vger.rutgers.edu with ESMTP id ; Sat, 15 Jul 2000 03:48:16 -0400 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 JAA03050; Sat, 15 Jul 2000 09:00:53 +0100 Received: (from linux@localhost) by flint.arm.linux.org.uk (8.9.3/8.9.3) id JAA05166; Sat, 15 Jul 2000 09:00:07 +0100 From: Russell King - ARM Linux Admin Message-Id: <200007150800.JAA05166@flint.arm.linux.org.uk> Subject: Re: ARM Linux history To: chris@fluff.org Date: Sat, 15 Jul 2000 09:00:07 +0100 (BST) Cc: linux-arm@vger.rutgers.edu (ARM Linux mailing list) In-Reply-To: from "Chris Rutter" at Jul 15, 2000 12:39:41 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@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Chris Rutter writes: > - What was the very early history of the kernel? > - When did binutils and gcc start supporting ARM-based formats? See my site. > - Where did the first C library with ARM support come from? It was a mini-C library written by me on the A5000 to get things just "smash", the fileutils, etc going. > - (Tangentially) what other Unices ran on ARM before Linux? (I count, > I think, NetBSD/arm32, Minix, RISCiX?) Minix patches were available, and of course RISCiX. NetBSD/arm32 was in very early days (no console at least iirc). I started the kernel in early `94. > (Yes, I know there's some story on Russell's site, but it seems apocryphal.) Well, thanks a lot. I've had to put up with a lot of arsey comments over the past 6 years, and I certainly don't need people like you trying to be offensive and down right rude to me, or trying to make stuff I put on my site to be useful or interesting to be termed "a work of fiction". Why do you doubt it? If you'd been at UKUUG Linux99, then you'd have heard the full story, which starts off more or less with that. Oh, and if you want to check up on the info on that page, you could talk to either Martin Ebourne of !Zap fame, or Tim Chown, the Electronics and Computer Science CS admin at Southampton University (92 to at least 96). Martin, however, has the most detailed independent knowledge of the progress. Oh, and please, don't write an apocryphal story about it, lest you piss me off even more. After all, there is only ONE person who can really review such a story, and say "its accurate" isn't there? _____ |_____| ------------------------------------------------- ---+---+- | | Russell King linux@arm.linux.org.uk --- --- | | | | http://www.arm.linux.org.uk/ / / | | +-+-+ --- -+- / | THE developer of ARM Linux |+| /|\ / | | | --- | +-+-+ ------------------------------------------------- /\\\ | unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Sat Jul 15 20:03:26 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13DXDi-0004Yh-00 for linux-arm-archive@lists.arm.linux.org.uk; Sat, 15 Jul 2000 20:03:26 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 56B5A1626E; Sat, 15 Jul 2000 21:03:24 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Sat, 15 Jul 2000 14:48:19 -0400 Received: by vger.rutgers.edu id ; Sat, 15 Jul 2000 14:48:02 -0400 Received: from adsl-63-192-134-89.dsl.snfc21.pacbell.net ([63.192.134.89]:1074 "EHLO tsuenwan.causality.com") by vger.rutgers.edu with ESMTP id ; Sat, 15 Jul 2000 14:47:42 -0400 Received: from causality.com (localhost [127.0.0.1]) by tsuenwan.causality.com (8.9.3/8.9.2) with ESMTP id LAA00320; Sat, 15 Jul 2000 11:51:04 -0700 (PDT) (envelope-from neil@causality.com) Message-ID: <3970B298.7F5D33F3@causality.com> Date: Sat, 15 Jul 2000 11:51:04 -0700 From: "Neil A. Carson" Organization: Causality Limited X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 3.2-RELEASE i386) X-Accept-Language: en-GB MIME-Version: 1.0 To: Russell King - ARM Linux Admin Cc: chris@fluff.org, ARM Linux mailing list Subject: Re: ARM Linux history References: <200007150800.JAA05166@flint.arm.linux.org.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Russell King - ARM Linux Admin wrote: > > - (Tangentially) what other Unices ran on ARM before Linux? (I count, > > I think, NetBSD/arm32, Minix, RISCiX?) > > Minix patches were available, and of course RISCiX. NetBSD/arm32 was > in very early days (no console at least iirc). I started the kernel > in early `94. I think at the same time you had stuff coming up on the A5K, NetBSD was running kernel mode only on The RiscPC with a blob moving up and down the screen to illustrate a process :) Fun days :) unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Sat Jul 15 22:50:34 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13DZpR-0005Yn-00 for linux-arm-archive@lists.arm.linux.org.uk; Sat, 15 Jul 2000 22:50:33 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id A6A5F15DFD; Sat, 15 Jul 2000 23:50:32 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Sat, 15 Jul 2000 17:35:47 -0400 Received: by vger.rutgers.edu id ; Sat, 15 Jul 2000 17:35:28 -0400 Received: from [12.38.17.9] ([12.38.17.9]:1902 "EHLO mail.aeptec.com") by vger.rutgers.edu with ESMTP id ; Sat, 15 Jul 2000 17:35:07 -0400 Received: by MAIL with Internet Mail Service (5.5.2650.21) id ; Sat, 15 Jul 2000 17:40:11 -0400 Message-ID: <32CC5B62AF0BD2119E4C00A0C9663E221F3BCC@MAIL> From: "Sun, Lei" To: "'linux-arm@vger.rutgers.edu'" Subject: ramdisk size Date: Sat, 15 Jul 2000 17:40:10 -0400 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@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Hi : Sorry for my lack of experience in linux. Can anybody tell me how to expand the size of the ramdisk (downloaded from CMU website for arm-linux kernel)? Thank you ! Lei Sun unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Sun Jul 16 00:33:41 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13DbRF-0006Ft-00 for linux-arm-archive@lists.arm.linux.org.uk; Sun, 16 Jul 2000 00:33:41 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 16C1E16130; Sun, 16 Jul 2000 01:27:19 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Sat, 15 Jul 2000 19:12:22 -0400 Received: by vger.rutgers.edu id ; Sat, 15 Jul 2000 19:12:08 -0400 Received: from note.orchestra.cse.unsw.EDU.AU ([129.94.242.29]:1353 "HELO note.orchestra.cse.unsw.EDU.AU") by vger.rutgers.edu with SMTP id ; Sat, 15 Jul 2000 18:42:55 -0400 Received: From paulaner With LocalMail ; Sun, 16 Jul 2000 08:56:19 +1000 From: Adam 'WeirdArms' Wiggins To: Jim Kasper Date: Sun, 16 Jul 2000 08:56:19 +1000 (EST) X-Sender: awiggins@paulaner.disy.cse.unsw.EDU.AU Cc: "'samcconn@cotw.com '" , "'linux-arm@vger.rutgers.edu '" Subject: RE: Need method to combine multiple binary images into one. (ld?) In-Reply-To: <412E1CF8088BD211AD5100805FAD9A800CD27A@CPQ800> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu I have a program using libbfd which merges multiple elf (and other format) executables into a single elf file. Each executable is given its own program segment. If your interested look at ftp://ftp.cse.unsw.edu.au/pub/users/awigins it's in the ediot*.tar.gz archive. Cheers Adam On Fri, 14 Jul 2000, Jim Kasper wrote: > Sam, > I had same problem, and while I am sure there must be a more elegant > way, I ended up doing as Tom suggested. I did a make on the images > seperatly, The boot part set with ld_script to 0x00, the second image set to > a ram location. My little script then checked sizes and combined images. > > > #!/bin/sh > # little script gets size of first from current dir > # and size of second from different source tree > #copies first to a file, pads it out, then adds second > > > size_boot=`ls -l boot_obj|awk '{print $5}' ` > size_top=`ls -l /usr/src/zblob/src/util.obj|awk '{print $5}' ` > #copy first object > dd if=boot_obj of=sboot > #pad with zeroes to 64K > > dd bs=1c if=/dev/zero of=sboot seek=$size_boot count=$((65536-$size_boot)) > # seek to boundry, copy second file > dd bs=1c if=/usr/src/zblob/src/util.obj of=sboot seek=65536c > count=$size_top > > > > uuencode sboot freddy > sboot.uu > > > > -----Original Message----- > From: Tom Walsh > To: samcconn@cotw.com > Cc: linux-arm@vger.rutgers.edu > Sent: 07/14/00 11:20 > Subject: Re: Need method to combine multiple binary images into one. (ld?) > > S A McConnell wrote: > > > > I am showing my lack of Linux/Unix experience.... > > > > I have five different binary images. To speed and simplify the > > loading/Flashing process I would like to combine the images into a > > single file placing each image at a set location. ( Image1 @ 0x0, > Image2 > > @ 0x3800, Image3 @ 0x10000....) There will be holes between each > image. > > > > The images are all ARM binaries. The command 'file' describes them as > > 'data' files. > > > > I tried to us arm-linux-ld but it complained about not knowing the > > format. I looked in the documentation but did not see a way to tell > the > > linker to treat it as just data. > > > > $file image1 > > image1:data > > > > $arm-linux-gcc -Timage.ld image1 image2 image3 image4 image5 > > image1: file not recognized: File format not recognized > > collect2: ld returned 1 exit status > > > > INPUT(image1 image2 image3 image4 image5) > > > > OUTPUT (bigimage) > > > > SECTIONS > > { > > output : > > { > > image1 > > . = 0x3800; > > image2 > > . = 0x4000; > > image3 > > . = 0x1000; > > image4 > > . = 0x100000; > > image5 > > } > > } > > > > ------------------------------- > > Does anyone have a suggestion about how to do this with or without the > > linker? > > > > Well, you are on the right track if the images were object files which > contained symbolic info identifying segments within the files. If that > were the case, then you would need to create and 'ld' file that > specified which segment got placed into where. > > But, if your file is pure, raw, binary data, I would suggest that you > write a quick program, or script, to append extra bytes to each image, > then cat them together. Use 'dd' to spec the number & value of the > appended padding. > > > TomW > > > > > > Thanks, > > SAM > > > > unsubscribe: body of `unsubscribe linux-arm' to > majordomo@vger.rutgers.edu > > ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for > ++ > > ++ kernel-related discussions. > ++ > > -- > Tom Walsh - WN3L - Embedded Systems Consultant > 'www.openhardware.net', 'www.cyberiansoftware.com' > "Windows? No thanks, I have work to do..." > > unsubscribe: body of `unsubscribe linux-arm' to > majordomo@vger.rutgers.edu > ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for > ++ > ++ kernel-related discussions. > ++ > > unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu > ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ > ++ kernel-related discussions. ++ > unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Sun Jul 16 01:25:01 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13DcEu-0006XW-00 for linux-arm-archive@lists.arm.linux.org.uk; Sun, 16 Jul 2000 01:25:00 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 18A5815E56; Sun, 16 Jul 2000 02:24:59 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Sat, 15 Jul 2000 20:10:10 -0400 Received: by vger.rutgers.edu id ; Sat, 15 Jul 2000 20:10:03 -0400 Received: from SMTP2.ANDREW.CMU.EDU ([128.2.10.82]:36129 "EHLO smtp2.andrew.cmu.edu") by vger.rutgers.edu with ESMTP id ; Sat, 15 Jul 2000 20:09:56 -0400 Received: from cs.cmu.edu (NINESIXTEEN.REM.CMU.EDU [128.2.81.157]) by smtp2.andrew.cmu.edu (8.9.3/8.9.3) with ESMTP id UAA07796; Sat, 15 Jul 2000 20:24:10 -0400 (EDT) Message-ID: <39710063.2D1ABC93@cs.cmu.edu> Date: Sat, 15 Jul 2000 20:22:59 -0400 From: John G Dorsey Organization: Carnegie Mellon University X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i686) X-Accept-Language: en MIME-Version: 1.0 To: "Sun, Lei" Cc: "'linux-arm@vger.rutgers.edu'" Subject: Re: ramdisk size References: <32CC5B62AF0BD2119E4C00A0C9663E221F3BCC@MAIL> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu "Sun, Lei" wrote: > Hi : > Sorry for my lack of experience in linux. Can anybody tell me how to > expand the size of the ramdisk (downloaded from CMU website for arm-linux > kernel)? Probably the easiest way is to `mkfs` a new ext2 filesystem on an unused ramdisk device (e.g., /dev/ram0) which has the appropriate number of blocks. (ramdisk_pcmcia.gz has 7500, for reference) If you're starting from an existing filesystem, just mount the new device and the old ramdisk image, and transfer the contents using a `tar` pipeline or similar. Two limits of which to be aware: 1. On your development workstation, the default ramdisk size may be too small to support a large image. You can pass an option to the kernel at boot time to change this; in /etc/lilo.conf, `append="ramdisk_size=16384"` or the like will deal with this. 2. On your ARM target, the amount of physical memory reserved for a ramdisk image is hardwired into the kernel, if I recall correctly. I think it's something like 3MB on Assabet, but you should double check this in arch/arm/kernel just to be safe. -jd unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Sun Jul 16 02:59:10 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13Ddi2-00070c-00 for linux-arm-archive@lists.arm.linux.org.uk; Sun, 16 Jul 2000 02:59:10 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id F376015DBD; Sun, 16 Jul 2000 03:59:08 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Sat, 15 Jul 2000 21:43:56 -0400 Received: by vger.rutgers.edu id ; Sat, 15 Jul 2000 21:43:48 -0400 Received: from modemcable248.137-200-24.mtl.mc.videotron.net ([24.200.137.248]:62571 "EHLO xanadu.gn.com") by vger.rutgers.edu with ESMTP id ; Sat, 15 Jul 2000 21:43:28 -0400 Received: from localhost (nico@localhost) by xanadu.gn.com (8.9.3/8.9.3) with ESMTP id VAA20527; Sat, 15 Jul 2000 21:56:49 -0400 X-Authentication-Warning: xanadu.gn.com: nico owned process doing -bs Date: Sat, 15 Jul 2000 21:56:49 -0400 (EDT) From: Nicolas Pitre X-Sender: nico@xanadu.gn.com To: John G Dorsey Cc: "Sun, Lei" , "'linux-arm@vger.rutgers.edu'" Subject: Re: ramdisk size In-Reply-To: <39710063.2D1ABC93@cs.cmu.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu On Sat, 15 Jul 2000, John G Dorsey wrote: > 2. On your ARM target, the amount of physical memory reserved for a ramdisk > image is hardwired into the kernel, if I recall correctly. I think it's > something like 3MB on Assabet, but you should double check this in > arch/arm/kernel just to be safe. Also note that this is a limit on the compressed initrd file. The limit on the filesystem itself is typically set to 8192KB for Assabet. Nicolas unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Sun Jul 16 03:09:08 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13Ddrg-00074r-00 for linux-arm-archive@lists.arm.linux.org.uk; Sun, 16 Jul 2000 03:09:08 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id EE29515D63; Sun, 16 Jul 2000 04:09:06 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Sat, 15 Jul 2000 21:54:11 -0400 Received: by vger.rutgers.edu id ; Sat, 15 Jul 2000 21:54:04 -0400 Received: from modemcable248.137-200-24.mtl.mc.videotron.net ([24.200.137.248]:62575 "EHLO xanadu.gn.com") by vger.rutgers.edu with ESMTP id ; Sat, 15 Jul 2000 21:53:51 -0400 Received: from localhost (nico@localhost) by xanadu.gn.com (8.9.3/8.9.3) with ESMTP id WAA20538; Sat, 15 Jul 2000 22:07:21 -0400 X-Authentication-Warning: xanadu.gn.com: nico owned process doing -bs Date: Sat, 15 Jul 2000 22:07:21 -0400 (EDT) From: Nicolas Pitre X-Sender: nico@xanadu.gn.com To: John G Dorsey Cc: "'linux-arm@vger.rutgers.edu'" Subject: Re: Spurious characters after kernel boot on Intel dev. board In-Reply-To: <396F0CA3.5E20AFB7@cs.cmu.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu On Fri, 14 Jul 2000, John G Dorsey wrote: > Jeff Sutherland wrote: > > > No trouble > > with output, though, and this is at 115200, n, 8, 1. I need to track this > > one down as we use serial I/O pretty extensively. > > That's interesting, because it looks to me as though -np3 cannot actually > implement that configuration (it doesn't believe in the "n"). > > The enclosed patch assumes that PARODD (or rather, its absence) does not imply > PARENB. It fixes the output strangeness on my Assabet and Assabet+Neponset. ... and it fixes the more-than-two-characters-received problem too. The serial driver is fully working again. Nice catch John! My next patch should be less buggy than the two latest ones... ;) Nicolas unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Sun Jul 16 11:40:40 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13Dlqi-0002Xu-00 for linux-arm-archive@lists.arm.linux.org.uk; Sun, 16 Jul 2000 11:40:40 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 452B315D65; Sun, 16 Jul 2000 12:40:38 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Sun, 16 Jul 2000 06:25:33 -0400 Received: by vger.rutgers.edu id ; Sun, 16 Jul 2000 06:25:16 -0400 Received: from [212.219.8.163] ([212.219.8.163]:1993 "HELO inkvine.fluff.org") by vger.rutgers.edu with SMTP id ; Sun, 16 Jul 2000 06:25:01 -0400 Received: from localhost (localhost [127.0.0.1]) by inkvine.fluff.org (Postfix) with ESMTP id 8744946820 for ; Sun, 16 Jul 2000 11:38:58 +0100 (BST) Date: Sun, 16 Jul 2000 11:38:58 +0100 (BST) From: Chris Rutter Reply-To: chris@fluff.org To: ARM Linux mailing list Subject: Re: ARM Linux history In-Reply-To: <200007150800.JAA05166@flint.arm.linux.org.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu On Sat, 15 Jul 2000, Russell King - ARM Linux Admin wrote: > > - When did binutils and gcc start supporting ARM-based formats? > > See my site. All you say is "At the start of 1995, GCC supported the ARM processors, but binutils was lacking. [...] Binutils didn't have particularly brilliant support for ARM - it didn't link the bl instruction properly." I was really looking for something a bit more specific, like who contributed this work to gcc and binutils, and for what purpose originally. I find it a bit unlikely that there would have been some substantial amount of ARM support in these tools but that it was heavily broken -- that doesn't make much sense! > It was a mini-C library written by me on the A5000 to get things just > "smash", the fileutils, etc going. I was more after where the ARM support in libc4 came from, or equally where NetBSD got its ARM support in its C library. (I'm not sure about the code topology sharing between NetBSD 1.0 and Linux 1.1's C libraries.) > Minix patches were available, and of course RISCiX. NetBSD/arm32 was > in very early days (no console at least iirc). I started the kernel > in early `94. Right; are there any details on these Minix patches? And NetBSD/arm32 was, it seemed to me, out there and running X and friends a year or few before Linux/ARM -- am I imagining this? > > (Yes, I know there's some story on Russell's site, but it seems apocryphal.) > > Well, thanks a lot. I've had to put up with a lot of arsey comments > over the past 6 years, and I certainly don't need people like you > trying to be offensive and down right rude to me, or trying to make > stuff I put on my site to be useful or interesting to be termed > "a work of fiction". > > Why do you doubt it? If you'd been at UKUUG Linux99, then you'd have > heard the full story, which starts off more or less with that. > > Oh, and if you want to check up on the info on that page, you could > talk to either Martin Ebourne of !Zap fame, or Tim Chown, the > Electronics and Computer Science CS admin at Southampton University > (92 to at least 96). Martin, however, has the most detailed > independent knowledge of the progress. > > Oh, and please, don't write an apocryphal story about it, lest you > piss me off even more. After all, there is only ONE person who can > really review such a story, and say "its accurate" isn't there? I didn't term that story `a work of fiction'. I said it /seemed/ apocryphal, meaning `of questionable authenticity', where I take `authenticity' to mean `undisputed credibility'. Given that story is only your account, having been ratified by no one else to my knowledge, and also that parts of it seem a little strange (other kernel hackers have cast doubt upon the ability of any version of Norcroft C to compile /any/ version of the kernel), it seemed fair to say that its credibility is not unquestionable; anyone making an accurate account of history to which many people must agree surely must make this judgement of this source! I'm not about to write an apocryphal story: that's why I'm being careful about blindly accepting the facts you present on your site. Obviously I have no wish to `piss you off' without reason, but I certainly won't stop at presenting what I believe the truth to be /purely/ because it may irritate you. I think your statement "there is only ONE person who can really review such a story" is indicative of a minor attitude problem on your part; you've won your kudos by being the first to contribute ARM code to the Linux kernel -- don't now lose it by being a bad team player. (Yes, that's harsh, but it's my sincere opinion.) c. unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Sun Jul 16 11:47:37 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13DlxR-0002Zi-00 for linux-arm-archive@lists.arm.linux.org.uk; Sun, 16 Jul 2000 11:47:37 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 5B56A15E5D; Sun, 16 Jul 2000 05:44:10 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Sat, 15 Jul 2000 23:27:34 -0400 Received: by vger.rutgers.edu id ; Sat, 15 Jul 2000 23:26:45 -0400 Received: from tomts1.bellnexxia.net ([209.226.175.139]:55764 "EHLO tomts1-srv.bellnexxia.net") by vger.rutgers.edu with ESMTP id ; Sat, 15 Jul 2000 23:25:11 -0400 Received: from Nightbird.TZoNE.ORG ([216.209.192.14]) by tomts1-srv.bellnexxia.net (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20000716033931.JBQ8304.tomts1-srv.bellnexxia.net@Nightbird.TZoNE.ORG>; Sat, 15 Jul 2000 23:39:31 -0400 Received: (from fabien@localhost) by Nightbird.TZoNE.ORG (8.11.0.Beta1/8.11.0.Beta1/Debian 8.11.0-1) id e6G3dNm22502; Sat, 15 Jul 2000 23:39:23 -0400 From: Fabien Ninoles Date: Sat, 15 Jul 2000 23:39:19 -0400 To: Deborah Wallach Cc: brad@parker.boston.ma.us, linux-arm-kernel@lists.arm.linux.org.uk, linux-usb-devel@lists.sourceforge.net, linux-arm@vger.rutgers.edu, sa1100-linux@pa.dec.com Subject: Re: port of ARM SA-1100 itsy usb function driver to 2.4.0-test2 Message-ID: <20000715233918.A22473@Nightbird.TZoNE.ORG> References: <200007131834.OAA24238@p2.parker.boston.ma.us> <200007131855.AA30339@stowe.pa.dec.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2i In-Reply-To: <200007131855.AA30339@stowe.pa.dec.com>; from kerr@pa.dec.com on Thu, Jul 13, 2000 at 11:55:27AM -0700 Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu On Thu, Jul 13, 2000 at 11:55:27AM -0700, Deborah Wallach wrote: > > It implements a basic ethernet interface complete with and eth0 > interface. I've not tried to pass packets to it (yet) but will in the > next week or two. I don't know what the DECWRL folks talked to with > it. Persumably they wrote some host code. I plan to implement the > other side shortly. > > We talk to it using either Linux (2.3.34) on an x86 PC or Windows 95/2000. > I haven't used the windows version myself, so I don't know anything about > it. Yes, we wrote some host code for the linux setup, but it's flaky (the > host machine crashes fairly often while using usb to the itsy), but if you > think it would be useful I can see if I can dig it up and get it posted > somewhere. I will be very interested by all those code (both client and host, Win and Linux) since I already try to implement something like this. I got the usb pipe #0 running correctly and Linux (2.3.99preX) configuring it correctly but can get the other pipe running. On the windows side, I ask a demonstrator for the SA-1111 to show me some code (both WinCE embedded or WinDriver Host) and the only thing he could find me is a USB Mouse Driver (really... they're very stupid sometime - we really have a lot of fun imagining what we can do with a mouse running a StrongArm :) I can myself send you the module I create for the linux host side, although the bulk pipes were never tested. BTW, do you think we can used a common DeviceID/VendorID for the code in the both kernel? Especially since the driver implementation will all be the same (mainly a network driver with a ppp-like connection). > > -Debby -- -------------------------------* *------------------------- Fabien Niñoles / / fabien@tzone.org Chevalier Servant de Sa Dame / / C15D FE9E BB35 F596 127F Veneur Gris par la Clef / / BF7D 8F1F DFC9 BCE0 9436 Chaton pour Debian / / http://www.tzone.org/~fabien --------------------------* *------------------------------ unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Sun Jul 16 13:21:13 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13DnQ1-0003Dv-00 for linux-arm-archive@lists.arm.linux.org.uk; Sun, 16 Jul 2000 13:21:13 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 93D2E15DB8; Sun, 16 Jul 2000 14:21:11 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Sun, 16 Jul 2000 08:05:58 -0400 Received: by vger.rutgers.edu id ; Sun, 16 Jul 2000 08:05:49 -0400 Received: from p27-cordelia-gui.tch.enablis.net ([212.250.233.27]:1747 "EHLO caramon.arm.linux.org.uk") by vger.rutgers.edu with ESMTP id ; Sun, 16 Jul 2000 08:05:41 -0400 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 NAA03563; Sun, 16 Jul 2000 13:19:22 +0100 Received: (from linux@localhost) by flint.arm.linux.org.uk (8.9.3/8.9.3) id NAA10496; Sun, 16 Jul 2000 13:18:35 +0100 From: Russell King - ARM Linux Admin Message-Id: <200007161218.NAA10496@flint.arm.linux.org.uk> Subject: Re: ARM Linux history To: chris@fluff.org Date: Sun, 16 Jul 2000 13:18:35 +0100 (BST) Cc: linux-arm@vger.rutgers.edu (ARM Linux mailing list) In-Reply-To: from "Chris Rutter" at Jul 16, 2000 11:38:58 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@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Chris Rutter writes: > Given that story is only your account, having been ratified by no one > else to my knowledge, and also that parts of it seem a little strange > (other kernel hackers have cast doubt upon the ability of any version > of Norcroft C to compile /any/ version of the kernel), it seemed fair > to say that its credibility is not unquestionable; anyone making an > accurate account of history to which many people must agree surely must > make this judgement of this source! Ok, for those doubters of you out there, go to: and browse the SparkFS archives located there - full source to the 1.1.59+ kernel that can be compiled under RISC OS, as well as the boot loader for that version. If you still have doubts, I can upload the very first C library for ARM Linux (also compiled in RISC OS), and the MicroEMACS source (again, compiled under RISC OS). I'll update the history webpage to point to this proof of fact. _____ |_____| ------------------------------------------------- ---+---+- | | Russell King linux@arm.linux.org.uk --- --- | | | | http://www.arm.linux.org.uk/ / / | | +-+-+ --- -+- / | THE developer of ARM Linux |+| /|\ / | | | --- | +-+-+ ------------------------------------------------- /\\\ | unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Sun Jul 16 13:48:59 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13Dnqt-0003MC-00 for linux-arm-archive@lists.arm.linux.org.uk; Sun, 16 Jul 2000 13:48:59 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 124F415DA0; Sun, 16 Jul 2000 14:48:58 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Sun, 16 Jul 2000 08:33:41 -0400 Received: by vger.rutgers.edu id ; Sun, 16 Jul 2000 08:33:32 -0400 Received: from tazenda.demon.co.uk ([158.152.220.239]:1599 "EHLO tazenda.demon.co.uk") by vger.rutgers.edu with ESMTP id ; Sun, 16 Jul 2000 08:33:24 -0400 Received: from kings-cross.london.uk.eu.org (spring.labs.futuretv.com) [::ffff:192.168.2.83] by tazenda.demon.co.uk with esmtp (Exim 3.11 #1 (Debian)) id 13Dnqa-0001V3-00; Sun, 16 Jul 2000 13:48:40 +0100 Received: from localhost ([::ffff:127.0.0.1] helo=spring ident=pb) by spring.labs.futuretv.com with esmtp (Exim 3.12 #1 (Debian)) id 13Dnoo-0000eg-00 for ; Sun, 16 Jul 2000 13:46:50 +0100 X-Mailer: exmh version 2.1.1 10/15/1999 (debian) To: chris@fluff.org From: philb@gnu.org Cc: ARM Linux mailing list Subject: Re: ARM Linux history In-Reply-To: Message from Chris Rutter of "Sun, 16 Jul 2000 11:38:58 BST." References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 16 Jul 2000 12:17:29 +0100 Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Message-Id: <20000716123340Z157033-6822+315@vger.rutgers.edu> In message , Chris R utter writes: >I was really looking for something a bit more specific, like who >contributed this work to gcc and binutils, and for what purpose >originally. Both binutils and GCC had support for generic ARM in pre-Linux days. You should be able to trace the history of these early contributions from the ChangeLog files in the respective packages. >I was more after where the ARM support in libc4 came from, or equally >where NetBSD got its ARM support in its C library. (I'm not sure about >the code topology sharing between NetBSD 1.0 and Linux 1.1's C libraries.) I don't believe there is much or any commonality there. The Linux C library has always been derived from the GNU libc -- Linux libc4 was based on GNU libc 1.x. As far as I know NetBSD's libc is a completely independent effort. p. unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Sun Jul 16 13:49:25 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13DnrJ-0003MR-00 for linux-arm-archive@lists.arm.linux.org.uk; Sun, 16 Jul 2000 13:49:25 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 53C8115DBC; Sun, 16 Jul 2000 14:49:24 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Sun, 16 Jul 2000 08:34:22 -0400 Received: by vger.rutgers.edu id ; Sun, 16 Jul 2000 08:34:06 -0400 Received: from tazenda.demon.co.uk ([158.152.220.239]:1603 "EHLO tazenda.demon.co.uk") by vger.rutgers.edu with ESMTP id ; Sun, 16 Jul 2000 08:33:41 -0400 Received: from kings-cross.london.uk.eu.org (spring.labs.futuretv.com) [::ffff:192.168.2.83] by tazenda.demon.co.uk with esmtp (Exim 3.11 #1 (Debian)) id 13Dnr6-0001VF-00; Sun, 16 Jul 2000 13:49:12 +0100 Received: from localhost ([::ffff:127.0.0.1] helo=spring ident=pb) by spring.labs.futuretv.com with esmtp (Exim 3.12 #1 (Debian)) id 13DnpL-0000eq-00 for ; Sun, 16 Jul 2000 13:47:23 +0100 X-Mailer: exmh version 2.1.1 10/15/1999 (debian) To: Mike Touloumtzis Cc: David Rusling , linux-arm From: philb@gnu.org Subject: Re: Building cross libraries In-Reply-To: Message from Mike Touloumtzis of "Sun, 09 Jul 2000 20:37:10 PDT." <20000709203710.A21694@fiji.bluemug.com> References: <3965FBD3.65402A14@arm.com> <20000709203710.A21694@fiji.bluemug.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 15 Jul 2000 15:03:08 +0100 Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Message-Id: <20000716123413Z157033-6822+316@vger.rutgers.edu> In message <20000709203710.A21694@fiji.bluemug.com>, Mike Touloumtzis writes: >-- Grab safe binutils source. The current Debian version, 2.9.5.0.31, > is claimed to be buggy on one of the ARM mailing lists. 2.9.5.0.14 > is reported to be safe on Chris Rutter's ARM cross-compiler page, > so I'm going to give that a try. The latest version of binutils is 2.10. You can get it from ftp.gnu.org, sourceware.cygnus.com and mirrors. No extra patches are needed for ARM GNU/ Linux. > -- Phil Blundell's 2.95.2 gcc patch doesn't apply cleanly, but I looked > at the patch, and the changes look reasonable (right direction, > likely bug fixes, etc). The top-level stuff (ChangeLog, configure, > configure.in) will get rejected; the other stuff patches cleanly, > although I had to supply a path to each file. > -- The fold-const.c patch looks like it's still needed (it hasn't been > applied in 2.95.2). To be honest I don't really remember what the status of the 2.95.2 patch is. I think there is a "2.95.3" patch in my directory on netwinder.org that might be slightly better. That should also apply against 2.95.2 without too many problems. p. unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Sun Jul 16 14:50:06 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13Doo2-0003jt-00 for linux-arm-archive@lists.arm.linux.org.uk; Sun, 16 Jul 2000 14:50:06 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 1D07915DCD; Sun, 16 Jul 2000 15:50:05 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Sun, 16 Jul 2000 09:34:59 -0400 Received: by vger.rutgers.edu id ; Sun, 16 Jul 2000 09:34:42 -0400 Received: from note.orchestra.cse.unsw.EDU.AU ([129.94.242.29]:2291 "HELO note.orchestra.cse.unsw.EDU.AU") by vger.rutgers.edu with SMTP id ; Sun, 16 Jul 2000 09:34:31 -0400 Received: From paulaner With LocalMail ; Sun, 16 Jul 2000 23:48:49 +1000 From: Simon Winwood To: S A McConnell Date: Sun, 16 Jul 2000 23:48:49 +1000 Cc: linux-arm@vger.rutgers.edu Subject: Re: Need method to combine multiple binary images into one. (ld?) (fwd) Message-ID: <20000716234848.A20928@paulaner.cse.unsw.edu.au> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from awiggins@cse.unsw.EDU.AU on Sun, Jul 16, 2000 at 08:53:16AM +1000 Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu I am working on something similar to this, but it is pretty pre-alpha ... what exactly do you want? How are the binaries linked in the first place? (i.e. with what linker?) What does objdump tell you? (run objdump -f ) Simon On Sun, Jul 16, 2000 at 08:53:16AM +1000, Adam 'WeirdArms' Wiggins wrote: > > Can you help them out here? > > ---------- Forwarded message ---------- > Date: Fri, 14 Jul 2000 08:42:00 -0500 > From: S A McConnell > To: linux-arm@vger.rutgers.edu > Subject: Need method to combine multiple binary images into one. (ld?) > > I am showing my lack of Linux/Unix experience.... > > I have five different binary images. To speed and simplify the > loading/Flashing process I would like to combine the images into a > single file placing each image at a set location. ( Image1 @ 0x0, Image2 > @ 0x3800, Image3 @ 0x10000....) There will be holes between each image. > > The images are all ARM binaries. The command 'file' describes them as > 'data' files. > > I tried to us arm-linux-ld but it complained about not knowing the > format. I looked in the documentation but did not see a way to tell the > linker to treat it as just data. > > $file image1 > image1:data > > $arm-linux-gcc -Timage.ld image1 image2 image3 image4 image5 > image1: file not recognized: File format not recognized > collect2: ld returned 1 exit status > > > > INPUT(image1 image2 image3 image4 image5) > > OUTPUT (bigimage) > > SECTIONS > { > output : > { > image1 > . = 0x3800; > image2 > . = 0x4000; > image3 > . = 0x1000; > image4 > . = 0x100000; > image5 > } > } > > ------------------------------- > Does anyone have a suggestion about how to do this with or without the > linker? > > Thanks, > SAM > > unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu > ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ > ++ kernel-related discussions. ++ unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Sun Jul 16 18:43:58 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13DsSL-0005Cw-00 for linux-arm-archive@lists.arm.linux.org.uk; Sun, 16 Jul 2000 18:43:57 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 7FA4115F18; Sun, 16 Jul 2000 19:43:49 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Sun, 16 Jul 2000 13:28:24 -0400 Received: by vger.rutgers.edu id ; Sun, 16 Jul 2000 13:28:13 -0400 Received: from typhoon.mail.pipex.net ([158.43.128.27]:43110 "HELO typhoon.mail.pipex.net") by vger.rutgers.edu with SMTP id ; Sun, 16 Jul 2000 13:27:35 -0400 Received: (qmail 3706 invoked from network); 16 Jul 2000 17:42:06 -0000 Received: from userao07.uk.uudial.com (HELO localhost) (62.188.135.123) by smtp.dial.pipex.com with SMTP; 16 Jul 2000 17:42:06 -0000 Date: Sun, 16 Jul 2000 12:17:46 +0100 From: Tom Harris To: linux-arm@vger.rutgers.edu Subject: Trouble with SCSI card recognition on install Message-ID: <7083f9de49.Tom@nusreform.org.uk> X-Organization: Guild of Angband Hackers User-Agent: Messenger-Pro/2.04 (MsgServe/1.04a) (RISC-OS/4.02) POPstar/2.02 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu I'm having trouble with installation of Aleph One's v0.8 distribution on my RO4 SARPC on account of trouble recognising my Cumana SCSI II card. On booting into the installer, everything proceeds as expected, except for the list of expansion cards. My ANT ethernet card (in slot 0), DMI50 MIDI card (slot 2) and Atomwide dual serial card (slot 3) are all recognised correctly, but the SCSI card isn't. I've tried several times, including removing the other cards and shuffling the SCSI card about on the backplane, and almost all the time the boot program reports it as 1: EASI [0000:0000] *unknown* Though on a few occasions it's been reported as "EASI simple card x" (don't remember the number) and twice as the "SCSI-2 & CDFS Expansion Card" that RISC OS reports it as. Both those times I couldn't complete the install because of difficulties accessing the CD-ROM (which, along with a Jaz drive, is all that's on the SCSI bus at the moment). I had a look at the expansion card info in the PRMs (4-119) and it seems that the card ID is only mandated to be at the bottom of expansion card space immediately after a reset. Perhaps it's not paged in? Or is a faulty backplane a more likely problem? Any help appreciated. Tom -- Tom Harris t.harris@iname.com http://www.harris.ukgateway.net/ * 80% of people consider themselves to be above average drivers unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Sun Jul 16 18:54:47 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13Dscj-0005KS-00 for linux-arm-archive@lists.arm.linux.org.uk; Sun, 16 Jul 2000 18:54:47 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id C28FA15E9A; Sun, 16 Jul 2000 19:54:11 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Sun, 16 Jul 2000 13:38:44 -0400 Received: by vger.rutgers.edu id ; Sun, 16 Jul 2000 13:38:25 -0400 Received: from p56-magpie-gui.tch.enablis.net ([194.168.180.56]:2427 "EHLO caramon.arm.linux.org.uk") by vger.rutgers.edu with ESMTP id ; Sun, 16 Jul 2000 13:38:18 -0400 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 SAA04625; Sun, 16 Jul 2000 18:52:48 +0100 Received: (from linux@localhost) by flint.arm.linux.org.uk (8.9.3/8.9.3) id SAA11345; Sun, 16 Jul 2000 18:52:01 +0100 From: Russell King - ARM Linux Admin Message-Id: <200007161752.SAA11345@flint.arm.linux.org.uk> Subject: Re: Trouble with SCSI card recognition on install To: t.harris@iname.com (Tom Harris) Date: Sun, 16 Jul 2000 18:52:00 +0100 (BST) Cc: linux-arm@vger.rutgers.edu In-Reply-To: <7083f9de49.Tom@nusreform.org.uk> from "Tom Harris" at Jul 16, 2000 12:17:46 PM X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Tom Harris writes: > I had a look at the expansion card info in the PRMs (4-119) and it seems > that the card ID is only mandated to be at the bottom of expansion card > space immediately after a reset. Perhaps it's not paged in? Or is a faulty > backplane a more likely problem? I suspect that there's a problem with the cards firmware. Can you try something for me please? Try hitting ctrl-reset and then see if the card is still detected. I have a suspicion that it won't be. If this is the case, then the firmware is buggy, and thinks get complicated ;( _____ |_____| ------------------------------------------------- ---+---+- | | Russell King linux@arm.linux.org.uk --- --- | | | | http://www.arm.linux.org.uk/ / / | | +-+-+ --- -+- / | THE developer of ARM Linux |+| /|\ / | | | --- | +-+-+ ------------------------------------------------- /\\\ | unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Sun Jul 16 21:36:24 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13Dv9D-0006Ly-00 for linux-arm-archive@lists.arm.linux.org.uk; Sun, 16 Jul 2000 21:36:23 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 2CBAD15E32; Sun, 16 Jul 2000 22:36:01 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Sun, 16 Jul 2000 16:20:40 -0400 Received: by vger.rutgers.edu id ; Sun, 16 Jul 2000 16:20:32 -0400 Received: from d141-29-65.home.cgocable.net ([24.141.29.65]:61142 "EHLO embeddedobjects.org") by vger.rutgers.edu with ESMTP id ; Sun, 16 Jul 2000 16:20:26 -0400 Received: from cgocable.net (softdnserr [::ffff:192.168.0.2]) (IDENT: hbelange) by embeddedobjects.org with esmtp; Sun, 16 Jul 2000 16:34:40 -0400 Message-ID: <39721D52.9968378@cgocable.net> Date: Sun, 16 Jul 2000 16:38:42 -0400 From: Hugues Belanger X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i586) X-Accept-Language: en MIME-Version: 1.0 To: linux-arm@vger.rutgers.edu Subject: Re: Trouble with SCSI card recognition on install References: <200007161752.SAA11345@flint.arm.linux.org.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Hi All, Forgive my ignorance, but I need a little help to get me going on my porting project.... I've down loaded the ARM toolchain from handhleds.org, patched configured and compile a kernel, manage to get all the base libs stripped, compiled Busybox and Tinylogin... but now "ae" is complaning the -ltermcap -lcurses are missing... I'm assuming that I need to had these libs to my tool chain RIGHT ? and if so, how do I do that ? thanks Hugues Belanger unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Sun Jul 16 21:42:04 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13DvEi-0006P7-00 for linux-arm-archive@lists.arm.linux.org.uk; Sun, 16 Jul 2000 21:42:04 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 46CA615E32; Sun, 16 Jul 2000 22:41:53 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Sun, 16 Jul 2000 16:26:33 -0400 Received: by vger.rutgers.edu id ; Sun, 16 Jul 2000 16:26:14 -0400 Received: from d141-29-65.home.cgocable.net ([24.141.29.65]:61147 "EHLO embeddedobjects.org") by vger.rutgers.edu with ESMTP id ; Sun, 16 Jul 2000 16:26:01 -0400 Received: from cgocable.net (softdnserr [::ffff:192.168.0.2]) (IDENT: hbelange) by embeddedobjects.org with esmtp; Sun, 16 Jul 2000 16:40:14 -0400 Message-ID: <39721EA0.F51143CC@cgocable.net> Date: Sun, 16 Jul 2000 16:44:16 -0400 From: Hugues Belanger X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i586) X-Accept-Language: en MIME-Version: 1.0 To: linux-arm@vger.rutgers.edu Subject: Help with toolchain References: <200007161752.SAA11345@flint.arm.linux.org.uk> <39721D52.9968378@cgocable.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu > Hi All, > > Forgive my ignorance, but I need a little help to get me going on my porting > project.... > > I've down loaded the ARM toolchain from handhleds.org, patched configured and > compile a kernel, manage to get all the base libs stripped, compiled Busybox and > Tinylogin... but now "ae" is complaning the -ltermcap -lcurses are missing... > I'm assuming that I need to had these libs to my tool chain RIGHT ? > > and if so, how do I do that ? > > thanks > > Hugues Belanger unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 17 01:13:08 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13DyWy-0007xG-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 17 Jul 2000 01:13:08 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 7733E15F2A; Mon, 17 Jul 2000 02:13:07 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Sun, 16 Jul 2000 19:57:53 -0400 Received: by vger.rutgers.edu id ; Sun, 16 Jul 2000 19:57:35 -0400 Received: from hose.mail.pipex.net ([158.43.128.58]:62339 "HELO hose.pipex.net") by vger.rutgers.edu with SMTP id ; Sun, 16 Jul 2000 19:57:18 -0400 Received: from localhost (userav87.uk.uudial.com [62.188.138.134]) by hose.pipex.net (Postfix) with SMTP id 9DBE54525; Mon, 17 Jul 2000 01:11:54 +0100 (BST) Date: Mon, 17 Jul 2000 00:26:28 +0100 From: Tom Harris To: linux@arm.linux.org.uk Cc: linux-arm@vger.rutgers.edu Subject: Re: Trouble with SCSI card recognition on install Message-ID: <483a3cdf49.Tom@nusreform.org.uk> References: <200007161752.SAA11345@flint.arm.linux.org.uk> In-Reply-To: <200007161752.SAA11345@flint.arm.linux.org.uk> X-Organization: Guild of Angband Hackers User-Agent: Messenger-Pro/2.04 (MsgServe/1.04a) (RISC-OS/4.02) POPstar/2.02 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu On 16 Jul Russell King - ARM Linux Admin wrote: > Tom Harris writes: > > I had a look at the expansion card info in the PRMs (4-119) and it > > seems that the card ID is only mandated to be at the bottom of > > expansion card space immediately after a reset. Perhaps it's not paged > > in? Or is a faulty backplane a more likely problem? > > I suspect that there's a problem with the cards firmware. Can you try > something for me please? Certainly. > Try hitting ctrl-reset and then see if the card is still detected. I > have a suspicion that it won't be. If this is the case, then the > firmware is buggy, and thinks get complicated ;( Ctrl-reset and leaving to boot to desktop, f12, *podules -> shows correctly. Ctrl-reset and * to supervisor, *podules -> shows correctly. Also the same in both cases with the unmodified reset button and ctrl-break, though I doubt it made a difference as IIRC there's only one type of reset in RISC OS 3.5+. Any thoughts/ideas? Tom -- Tom Harris t.harris@iname.com http://www.harris.ukgateway.net/ * Gee, it's fun that we're speaking in tongues. (Buffy, BtVS) unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 17 10:49:15 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13E7WV-0004Kw-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 17 Jul 2000 10:49:15 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id F0DB915DA0; Mon, 17 Jul 2000 11:48:05 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Mon, 17 Jul 2000 05:32:42 -0400 Received: by vger.rutgers.edu id ; Mon, 17 Jul 2000 05:32:33 -0400 Received: from ws5.smartm.com ([206.111.156.6]:1735 "HELO smtphost.smartm.com") by vger.rutgers.edu with SMTP id ; Mon, 17 Jul 2000 05:32:20 -0400 Received: by smtphost.smartm.com(Lotus SMTP MTA v4.6.7 (934.1 12-30-1999)) id 8825691F.003725FF ; Mon, 17 Jul 2000 03:02:22 -0700 X-Lotus-FromDomain: SMART MODULAR@APEX DATA INC From: gerry.murphy@smartm.com To: linux-arm@vger.rutgers.edu Message-ID: <8825691F.00372518.00@smtphost.smartm.com> Date: Mon, 17 Jul 2000 10:47:12 +0100 Subject: Re: EEPro100 NICs and EBSA285. Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu What has changed in the 2.4.x kernel to fix the dma cache coherency problems. Do you know when this will be a stable kernel. We have ported the 82559 driver adding the DMA writebacks and invalidates which generally works but we still see some infrequent transmit problems. Gerry From: Nicolas Pitre@nico on 07/12/2000 08:51 PM To: Jacob Strauss@jastr@MIT.EDU@SMTP@EXCHANGE cc: linux-arm@linux-arm@vger.rutgers.edu@SMTP@EXCHANGE Subject: Re: EEPro100 NICs and EBSA285. You need to add all the cache coherency handling into the driver for it to work properly with ARM processors. If you'd use a 2.4.x kernel, everything is already done for you. unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 17 11:06:58 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13E7nd-0004VY-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 17 Jul 2000 11:06:57 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 5F5DD15DB6; Mon, 17 Jul 2000 12:06:56 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Mon, 17 Jul 2000 05:51:17 -0400 Received: by vger.rutgers.edu id ; Mon, 17 Jul 2000 05:51:01 -0400 Received: from [194.201.77.34] ([194.201.77.34]:52669 "HELO fw-maid.maidenhead.arm.com") by vger.rutgers.edu with SMTP id ; Mon, 17 Jul 2000 05:48:28 -0400 Received: by fw-maid.maidenhead.arm.com; id LAA07073; Mon, 17 Jul 2000 11:00:28 +0100 Received: from mhsun1.maidenhead.arm.com(192.168.2.10) by fw-maid.maidenhead.arm.com via smap (V5.0) id xma007071; Mon, 17 Jul 00 11:00:02 +0100 Received: from arm.com (dhcp2 [192.168.2.232]) by mhsun1.maidenhead.arm.com (8.9.3/8.9.3) with ESMTP id LAA21441 for ; Mon, 17 Jul 2000 11:02:49 +0100 (BST) Message-ID: <3972E569.D1FE42FB@arm.com> Date: Mon, 17 Jul 2000 11:52:25 +0100 From: David Rusling X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: linux-arm@vger.rutgers.edu Subject: /dev/tty References: <8825691F.00372518.00@smtphost.smartm.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu All, I'm trying to get Microwindows running on our prospector platform. When I build the keyboard into it, it fails for want of opening /dev/tty. My reading of the code is that that _should_ work, but it fails 'cos current has no tty at this point. How? init has a tty, the shell inherits it. Do I need to have logged in (via tinylogin) - at the moment my rc script just starts a shell... Dave ---------------------------------------------------------------------- David A Rusling Consulting Engineer ARM Limited Liberty House, Moorbridge Road, Maidenhead, SL6 8LT Tel: UK-(0)1628-427754 Fax: UK-(0)1628-780551 e-mail: david.rusling@arm.com ---------------------------------------------------------------------- unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 17 11:25:42 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13E85m-0004hX-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 17 Jul 2000 11:25:42 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 26A3F15DBE; Mon, 17 Jul 2000 12:25:42 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Mon, 17 Jul 2000 06:10:09 -0400 Received: by vger.rutgers.edu id ; Mon, 17 Jul 2000 06:10:01 -0400 Received: from nw176.netaddress.usa.net ([204.68.24.76]:51296 "HELO nw176.netaddress.usa.net") by vger.rutgers.edu with SMTP id convert rfc822-to-8bit; Mon, 17 Jul 2000 06:09:51 -0400 Received: (qmail 26099 invoked by uid 60001); 17 Jul 2000 10:24:36 -0000 Message-ID: <20000717102436.26098.qmail@nw176.netaddress.usa.net> Received: from 204.68.24.76 by nw176 for [32.97.136.235] via web-mailer(34FM1.5A.01A) on Mon Jul 17 10:24:35 GMT 2000 Date: 17 Jul 00 15:54:35 IST From: anand kumar To: Hugues Belanger Subject: Re: [Help with toolchain] Cc: linux-7110@redhat.com, linux-arm@vger.rutgers.edu X-Mailer: USANET web-mailer (34FM1.5A.01A) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8BIT Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu You have to get the sources/binaries(ARM) from netwinder.org/allrpms.htm and include it. Note:ARM Binaries may not be compatible for your needs.I suggest you get the sources and cross-compile it yourself using the toolchain. cheers anand Hugues Belanger wrote: > Hi All, > > Forgive my ignorance, but I need a little help to get me going on my porting > project.... > > I've down loaded the ARM toolchain from handhleds.org, patched configured and > compile a kernel, manage to get all the base libs stripped, compiled Busybox and > Tinylogin... but now "ae" is complaning the -ltermcap -lcurses are missing... > I'm assuming that I need to had these libs to my tool chain RIGHT ? > > and if so, how do I do that ? > > thanks > > Hugues Belanger unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ ____________________________________________________________________ Get free email and a permanent address at http://www.netaddress.com/?N=1 unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 17 14:25:33 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13EAtn-0006Hn-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 17 Jul 2000 14:25:32 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 01DDE15E11; Mon, 17 Jul 2000 15:21:45 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Mon, 17 Jul 2000 09:06:24 -0400 Received: by vger.rutgers.edu id ; Mon, 17 Jul 2000 09:06:06 -0400 Received: from d141-29-65.home.cgocable.net ([24.141.29.65]:62170 "EHLO embeddedobjects.org") by vger.rutgers.edu with ESMTP id ; Mon, 17 Jul 2000 09:05:48 -0400 Received: from cgocable.net (softdnserr [::ffff:192.168.0.2]) (IDENT: hbelange) by embeddedobjects.org with esmtp; Mon, 17 Jul 2000 09:20:19 -0400 Message-ID: <39730905.7F507993@cgocable.net> Date: Mon, 17 Jul 2000 09:24:21 -0400 From: Hugues Belanger X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i586) X-Accept-Language: en MIME-Version: 1.0 To: anand kumar Cc: linux-arm@vger.rutgers.edu Subject: Re: [Help with toolchain] References: <20000717102436.26098.qmail@nw176.netaddress.usa.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Hi Anand I've downloaded the SRPMS already, but could you do me a favor and describe the high level steps required to do this. I.e. 1- Install the RPM 2- uncompress the source 3- ./configure --target=arm-linux --prefix=/skiff/local/ 4- make 5- ?? Do I copy the include from the source to the toolchain include dir ? 6- Any other steps ? Thanks anand kumar wrote: > You have to get the sources/binaries(ARM) from netwinder.org/allrpms.htm > and include it. > Note:ARM Binaries may not be compatible for your needs.I suggest you get the > sources and cross-compile it yourself using the toolchain. > > cheers > anand > > Hugues Belanger wrote: > > > Hi All, > > > > Forgive my ignorance, but I need a little help to get me going on my > porting > > project.... > > > > I've down loaded the ARM toolchain from handhleds.org, patched configured > and > > compile a kernel, manage to get all the base libs stripped, compiled Busybox > and > > Tinylogin... but now "ae" is complaning the -ltermcap -lcurses are > missing... > > I'm assuming that I need to had these libs to my tool chain RIGHT ? > > > > and if so, how do I do that ? > > > > thanks > > > > Hugues Belanger > > unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu > ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ > ++ kernel-related discussions. ++ > > ____________________________________________________________________ > Get free email and a permanent address at http://www.netaddress.com/?N=1 > > unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu > ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ > ++ kernel-related discussions. ++ unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 17 15:54:05 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13ECHU-0007Em-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 17 Jul 2000 15:54:04 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 2581C15DFC; Mon, 17 Jul 2000 16:54:02 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Mon, 17 Jul 2000 10:30:42 -0400 Received: by vger.rutgers.edu id ; Mon, 17 Jul 2000 10:30:23 -0400 Received: from ice.fiftyone.com ([208.225.80.11]:2801 "EHLO ice.ar51.net") by vger.rutgers.edu with ESMTP id ; Mon, 17 Jul 2000 10:29:09 -0400 Received: from server01.asi (akron-80-189.ar51.net [208.225.80.189]) by ice.ar51.net (8.9.3/8.8.7) with ESMTP id KAA25668; Mon, 17 Jul 2000 10:43:58 -0400 Received: by SERVER01 with Internet Mail Service (5.5.2448.0) id <3YXN8CZ7>; Mon, 17 Jul 2000 10:45:49 -0400 Message-ID: From: Jeff Sutherland To: "'Nicolas Pitre'" , "'John G Dorsey'" Cc: "'linux-arm@vger.rutgers.edu'" Subject: RE: Spurious characters after kernel boot on Intel dev. board Date: Mon, 17 Jul 2000 10:45:40 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu > On Fri, 14 Jul 2000, John G Dorsey wrote: > > The enclosed patch assumes that PARODD (or rather, its > absence) does not imply > > PARENB. It fixes the output strangeness on my Assabet and > Assabet+Neponset. and Nico replied: > ... and it fixes the more-than-two-characters-received problem too. > The serial driver is fully working again. Nice catch John! Yes, indeed. Quite amazing, all my serial ports are now working fine again as well. Thanks, guys! //Jeff unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 17 16:08:52 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13ECVn-0007PB-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 17 Jul 2000 16:08:52 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 0748315D53; Mon, 17 Jul 2000 17:08:33 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Mon, 17 Jul 2000 10:52:38 -0400 Received: by vger.rutgers.edu id ; Mon, 17 Jul 2000 10:52:23 -0400 Received: from netwinder.org ([207.245.35.202]:64308 "EHLO kei.netwinder.org") by vger.rutgers.edu with ESMTP id ; Mon, 17 Jul 2000 10:52:03 -0400 Received: from netwinder.org ([10.1.19.121]) by kei.netwinder.org (8.9.3/8.9.3) with ESMTP id LAA10251; Mon, 17 Jul 2000 11:05:05 -0400 Message-ID: <39731EBC.4D3D424E@netwinder.org> Date: Mon, 17 Jul 2000 10:57:00 -0400 From: Scott Bambrough Organization: Rebel.com X-Mailer: Mozilla 4.7 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: philb@gnu.org Cc: Mike Touloumtzis , David Rusling , linux-arm Subject: Re: Building cross libraries References: <3965FBD3.65402A14@arm.com> <20000709203710.A21694@fiji.bluemug.com> <20000716123413Z157033-6822+316@vger.rutgers.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu > > -- Phil Blundell's 2.95.2 gcc patch doesn't apply cleanly, but I looked > > at the patch, and the changes look reasonable (right direction, > > likely bug fixes, etc). The top-level stuff (ChangeLog, configure, > > configure.in) will get rejected; the other stuff patches cleanly, > > although I had to supply a path to each file. > > -- The fold-const.c patch looks like it's still needed (it hasn't been > > applied in 2.95.2). > > To be honest I don't really remember what the status of the 2.95.2 patch is. > I think there is a "2.95.3" patch in my directory on netwinder.org that might > be slightly better. That should also apply against 2.95.2 without too many > problems. To be quite honest, I think the best source of patches for gcc is my source RPM on netwinder.org. I spent a great deal of time organizing and documenting them. AFAIK, they are fully up to date. Scott -- Scott Bambrough - Software Engineer REBEL.COM http://www.rebel.com NetWinder http://www.netwinder.org unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 17 16:43:23 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13ED3C-0007pG-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 17 Jul 2000 16:43:23 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 67CEC15E45; Mon, 17 Jul 2000 17:39:47 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Mon, 17 Jul 2000 11:18:19 -0400 Received: by vger.rutgers.edu id ; Mon, 17 Jul 2000 11:13:34 -0400 Received: from mailserv2.iuinc.com ([206.245.164.55]:2048 "HELO mailserv2.iuinc.com") by vger.rutgers.edu with SMTP id ; Mon, 17 Jul 2000 11:13:17 -0400 Received: (qmail 4489 invoked from network); 17 Jul 2000 15:28:10 -0000 Received: from ottawa.linuxcare.com (HELO vodka.thepuffingroup.com) (216.208.98.2) by mailserv2.iuinc.com with SMTP; 17 Jul 2000 15:28:10 -0000 Received: (from willy@localhost) by vodka.thepuffingroup.com (8.9.3/8.9.3) id KAA32307; Mon, 17 Jul 2000 10:22:41 -0400 Date: Mon, 17 Jul 2000 10:22:41 -0400 From: Matthew Wilcox To: gerry.murphy@smartm.com Cc: linux-arm@vger.rutgers.edu Subject: Re: EEPro100 NICs and EBSA285. Message-ID: <20000717102241.B30134@vodka.thepuffingroup.com> References: <8825691F.00372518.00@smtphost.smartm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4us In-Reply-To: <8825691F.00372518.00@smtphost.smartm.com>; from gerry.murphy@smartm.com on Mon, Jul 17, 2000 at 10:47:12AM +0100 Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu On Mon, Jul 17, 2000 at 10:47:12AM +0100, gerry.murphy@smartm.com wrote: > > > > > What has changed in the 2.4.x kernel to fix the dma cache coherency problems. Do it's all described in Documentation/DMA-mapping.txt -- Revolutions do not have corporate support. unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 17 18:19:38 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13EEYK-0000XW-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 17 Jul 2000 18:19:38 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 6154A15F6C; Mon, 17 Jul 2000 19:13:38 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Mon, 17 Jul 2000 12:56:38 -0400 Received: by vger.rutgers.edu id ; Mon, 17 Jul 2000 12:46:41 -0400 Received: from tazenda.demon.co.uk ([158.152.220.239]:2304 "EHLO tazenda.demon.co.uk") by vger.rutgers.edu with ESMTP id ; Mon, 17 Jul 2000 12:45:42 -0400 Received: from kings-cross.london.uk.eu.org [::ffff:192.168.2.83] by tazenda.demon.co.uk with esmtp (Exim 3.11 #1 (Debian)) id 13ECoY-0002sm-00; Mon, 17 Jul 2000 16:28:14 +0100 Received: from localhost ([::ffff:127.0.0.1] helo=tazenda.demon.co.uk) by kings-cross.london.uk.eu.org with esmtp (Exim 3.12 #1 (Debian)) id 13ECp7-00009Q-00; Mon, 17 Jul 2000 16:28:49 +0100 To: Scott Bambrough Cc: philb@gnu.org, Mike Touloumtzis , David Rusling , linux-arm Subject: Re: Building cross libraries In-reply-to: Your message of "Mon, 17 Jul 2000 10:57:00 EDT." <39731EBC.4D3D424E@netwinder.org> Date: Mon, 17 Jul 2000 16:28:49 +0100 From: Philip Blundell Message-Id: Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu >To be quite honest, I think the best source of patches for gcc is my source >RPM on netwinder.org. I spent a great deal of time organizing and documenting >them. AFAIK, they are fully up to date. Good point. Yes, I agree. p. unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 17 19:41:26 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13EFpW-0001rM-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 17 Jul 2000 19:41:26 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id ED66B1608E; Mon, 17 Jul 2000 20:37:12 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Mon, 17 Jul 2000 14:18:14 -0400 Received: by vger.rutgers.edu id ; Mon, 17 Jul 2000 14:17:29 -0400 Received: from cambridge.merl.com ([137.203.190.1]:18248 "EHLO cambridge.merl.com") by vger.rutgers.edu with ESMTP id ; Mon, 17 Jul 2000 14:16:20 -0400 Received: from merl.com (eagle.merl.com [137.203.128.4]) by cambridge.merl.com (8.8.7/8.8.7) with ESMTP id OAA10330 for ; Mon, 17 Jul 2000 14:31:17 -0400 Received: from zathrus.merl.com (carbone@zathrus.merl.com [137.203.128.26]) by merl.com (8.8.7/8.8.4) with ESMTP id OAA21497 for ; Mon, 17 Jul 2000 14:31:16 -0400 Received: from localhost (carbone@localhost) by zathrus.merl.com (8.9.3/8.8.3) with ESMTP id OAA31449 for ; Mon, 17 Jul 2000 14:31:16 -0400 Date: Mon, 17 Jul 2000 14:31:16 -0400 (EDT) From: Marco Carbone To: linux-arm@vger.rutgers.edu Subject: Toolchain problem w/ C++ cross-compiler Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Hello all, I have a working toolchain w/ the following: binutils-2.10.0.9 gcc-2.95.2 glibc-2.1.3 My c cross compiler and libraries have been tested and work with my Assabet. Now I want to build a c++ cross compiler, which is supposedly easy at this point in the toolchain build. (I used Chris Rutter's 'Building the GNU toolchain for ARM targets' to get to this point). When I run "make LANGUAGES='c c++'" I get the following error: P make[1]: *** No rule to make target `c++', needed by `native'. Stop. make[1]: Leaving directory `/usr/local/src/gcc-2.95.2/gcc' make: *** [all-gcc] Error 2 Now I've tried configuring w/ '--enable-languages=c,c++' as well, and this didn't work either. Does anyone know why the make is failing? I was under the impression that gcc-2.95.2 could make the c++ compiler as soon as glibc is installed, but the error above confuses me. Possibly I'm taking the wrong approach to build the c++ cross compiler? Thanks, Marco Carbone unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Tue Jul 18 00:37:41 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13EKSC-0005Zd-00 for linux-arm-archive@lists.arm.linux.org.uk; Tue, 18 Jul 2000 00:37:40 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 9C638162B2; Tue, 18 Jul 2000 01:35:00 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Mon, 17 Jul 2000 19:19:05 -0400 Received: by vger.rutgers.edu id ; Mon, 17 Jul 2000 19:11:25 -0400 Received: from [212.219.8.163] ([212.219.8.163]:2989 "HELO inkvine.fluff.org") by vger.rutgers.edu with SMTP id ; Mon, 17 Jul 2000 19:10:13 -0400 Received: from localhost (localhost [127.0.0.1]) by inkvine.fluff.org (Postfix) with ESMTP id 95C3E46820 for ; Tue, 18 Jul 2000 00:24:50 +0100 (BST) Date: Tue, 18 Jul 2000 00:24:50 +0100 (BST) From: Chris Rutter Reply-To: chris@fluff.org To: ARM Linux mailing list Subject: RISC OS emulation ideas Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu I've written a web page detailing the ideas that have cropped up so far with respect to RISC OS emulation. I'd be very grateful for people to scrutinise and comment on some of the ideas so far; find the page at: http://www.armlinux.org/~chris/rose.html Thanks, c. unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Tue Jul 18 04:19:54 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13ENvF-0007kk-00 for linux-arm-archive@lists.arm.linux.org.uk; Tue, 18 Jul 2000 04:19:54 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id CAC7015D61; Tue, 18 Jul 2000 05:19:54 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Mon, 17 Jul 2000 23:04:13 -0400 Received: by vger.rutgers.edu id ; Mon, 17 Jul 2000 23:04:05 -0400 Received: from ringding.cs.umd.edu ([128.8.126.2]:47203 "EHLO ringding.cs.umd.edu") by vger.rutgers.edu with ESMTP id ; Mon, 17 Jul 2000 23:03:45 -0400 Received: from localhost (localhost [127.0.0.1]) by ringding.cs.umd.edu (8.9.3/8.9.1) with ESMTP id XAA22881 for ; Mon, 17 Jul 2000 23:17:29 -0400 (EDT) Date: Mon, 17 Jul 2000 23:17:29 -0400 (EDT) From: Bill Arbaugh To: linux-arm@vger.rutgers.edu Subject: EBSA-285 v2.4 Kernel .config? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Does anyone have a kernel .config file for an EBSA-285 in add-in mode that results in an image? I've tried numerous settings with v2.4.0-test2-acl-rmk3 and haven't been able to get to an image yet. Thanks, Bill p.s. At this point, I'll settle for a v2.3. ------------------------------------------------------------------- Bill Arbaugh www.cs.umd.edu/~waa University of Maryland waa@cs.umd.edu College Park 301.405.2774 ------------------------------------------------------------------- unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Tue Jul 18 11:45:49 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13EUsn-000331-00 for linux-arm-archive@lists.arm.linux.org.uk; Tue, 18 Jul 2000 11:45:49 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 43A0915EA1; Tue, 18 Jul 2000 12:44:48 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 18 Jul 2000 06:25:01 -0400 Received: by vger.rutgers.edu id ; Tue, 18 Jul 2000 06:24:39 -0400 Received: from p09-robin-gui.tch.enablis.net ([194.168.180.69]:4074 "EHLO caramon.arm.linux.org.uk") by vger.rutgers.edu with ESMTP id ; Tue, 18 Jul 2000 06:24:26 -0400 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 IAA11574; Tue, 18 Jul 2000 08:00:01 +0100 Received: (from linux@localhost) by flint.arm.linux.org.uk (8.9.3/8.9.3) id HAA20460; Tue, 18 Jul 2000 07:59:10 +0100 From: Russell King - ARM Linux Admin Message-Id: <200007180659.HAA20460@flint.arm.linux.org.uk> Subject: Re: EBSA-285 v2.4 Kernel .config? To: waa@cs.umd.edu (Bill Arbaugh) Date: Tue, 18 Jul 2000 07:59:10 +0100 (BST) Cc: linux-arm@vger.rutgers.edu In-Reply-To: from "Bill Arbaugh" at Jul 17, 2000 11:17:29 PM X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Bill Arbaugh writes: > Does anyone have a kernel .config file for an EBSA-285 in add-in mode that > results in an image? I've tried numerous settings with > v2.4.0-test2-acl-rmk3 and haven't been able to get to an image yet. Thanks for pointing out that it doesn't compile. Its not one of the configurations I test (since I don't have the hardware to match this configuration). Could you indicate what fails when building, along with the .config file you used for that build? Thanks. _____ |_____| ------------------------------------------------- ---+---+- | | Russell King linux@arm.linux.org.uk --- --- | | | | http://www.arm.linux.org.uk/ / / | | +-+-+ --- -+- / | THE developer of ARM Linux |+| /|\ / | | | --- | +-+-+ ------------------------------------------------- /\\\ | unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Tue Jul 18 13:29:13 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13EWUr-00046e-00 for linux-arm-archive@lists.arm.linux.org.uk; Tue, 18 Jul 2000 13:29:13 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 2469315EBE; Tue, 18 Jul 2000 14:29:15 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 18 Jul 2000 08:13:20 -0400 Received: by vger.rutgers.edu id ; Tue, 18 Jul 2000 08:13:12 -0400 Received: from nanum.kaeri.re.kr ([147.43.15.12]:1688 "EHLO nanum.kaeri.re.kr") by vger.rutgers.edu with ESMTP id ; Tue, 18 Jul 2000 08:13:00 -0400 Received: from mail.robotics.co.kr ([147.43.73.178]) by nanum.kaeri.re.kr (8.9.1a-H1/8.9.3) with ESMTP id VAA07161 for ; Tue, 18 Jul 2000 21:37:14 +0900 (kst) Message-ID: <39744D47.AFB19EEC@mail.robotics.co.kr> Date: Tue, 18 Jul 2000 21:27:51 +0900 From: Sun-Gi Hong Organization: Hanwool Robotics Corp. X-Mailer: Mozilla 4.61 [ko] (X11; I; Linux 2.2.12-20kr i686) X-Accept-Language: ko MIME-Version: 1.0 To: linux-arm@vger.rutgers.edu Subject: [Q] Kernel Compilation Error (2.4.0.test2 version) Content-Type: text/plain; charset=EUC-KR Content-Transfer-Encoding: 8bit Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Greetings, I've already compiled the kernel 2.4.0.test1 version, now I try to compile the kernel 2.4.0.test2 version. However, it displays error messages when I set the Neponset support. (CONFIG_ASSABET_NEPONSET = y) The used kernels and patches are as follows. diff-2.4.0-test2-ac1-rmk2-np3.gz patch-2.4.0-test2-ac1-rmk2.gz linux-2.4.0-test2-ac1-rmk2-np3-jd1.patch patch-2.4.0test2-ac1.gz linux-2.4.0-test2.tar.gz Errors occur when compiling the file, /drivers/pcmcia/sa1100_neponset.c. Furthermore, I cannot configure modules when using "make modules". It just says "Nothing to de done for 'modules'". Any ideas? unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Tue Jul 18 14:40:11 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13EXbX-0004pM-00 for linux-arm-archive@lists.arm.linux.org.uk; Tue, 18 Jul 2000 14:40:11 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id DAE2C15D76; Tue, 18 Jul 2000 15:40:12 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 18 Jul 2000 09:24:17 -0400 Received: by vger.rutgers.edu id ; Tue, 18 Jul 2000 09:24:01 -0400 Received: from SMTP2.ANDREW.CMU.EDU ([128.2.10.82]:34304 "EHLO smtp2.andrew.cmu.edu") by vger.rutgers.edu with ESMTP id ; Tue, 18 Jul 2000 09:23:38 -0400 Received: from cs.cmu.edu (NINESIXTEEN.REM.CMU.EDU [128.2.81.157]) by smtp2.andrew.cmu.edu (8.9.3/8.9.3) with ESMTP id JAA06865; Tue, 18 Jul 2000 09:38:43 -0400 (EDT) Message-ID: <39745D9A.C2387E9@cs.cmu.edu> Date: Tue, 18 Jul 2000 09:37:30 -0400 From: John G Dorsey Organization: Carnegie Mellon University X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i686) X-Accept-Language: en MIME-Version: 1.0 To: Sun-Gi Hong Cc: linux-arm@vger.rutgers.edu Subject: Re: [Q] Kernel Compilation Error (2.4.0.test2 version) References: <39744D47.AFB19EEC@mail.robotics.co.kr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Sun-Gi Hong wrote: > I've already compiled the kernel 2.4.0.test1 version, now I try to > compile the kernel 2.4.0.test2 version. However, it displays error > messages when I set the Neponset support. (CONFIG_ASSABET_NEPONSET = y) Without knowing what the errors are, it's harder to diagnose this. I'll venture that what you're seeing is in some way related to CONFIG_SA1111 not being defined in Nicolas' next-to-most-recent patch. (You didn't list -np3-jd1 last; did you apply it last?) In any case, Nicolas' latest patch (2.4.0-test4-np1) sounds like a better bet. > Furthermore, I cannot configure modules when using "make modules". It > just says "Nothing to de done for 'modules'". Did you specifically configure anything as a module when setting up the kernel? The "assabet_config" included in Nicolas' patches puts everything in the kernel by default. I usually go in and specify `m` for things like the PCMCIA NE2000 (pcnet_cs) driver, and the PCMCIA ATA/IDE (ide_cs) driver. Good luck, -jd unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Tue Jul 18 14:47:43 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13EXip-0004sU-00 for linux-arm-archive@lists.arm.linux.org.uk; Tue, 18 Jul 2000 14:47:43 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 368EB15E34; Tue, 18 Jul 2000 15:47:45 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 18 Jul 2000 09:31:51 -0400 Received: by vger.rutgers.edu id ; Tue, 18 Jul 2000 09:31:33 -0400 Received: from [205.250.170.220] ([205.250.170.220]:4695 "EHLO xanadu.vipswitch.com") by vger.rutgers.edu with ESMTP id ; Tue, 18 Jul 2000 09:31:18 -0400 Date: Tue, 18 Jul 2000 09:43:24 -0400 (EDT) From: Nicolas Pitre To: Sun-Gi Hong Cc: linux-arm@vger.rutgers.edu Subject: Re: [Q] Kernel Compilation Error (2.4.0.test2 version) In-Reply-To: <39744D47.AFB19EEC@mail.robotics.co.kr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu On Tue, 18 Jul 2000, Sun-Gi Hong wrote: > Greetings, > > I've already compiled the kernel 2.4.0.test1 version, now I try to > compile the kernel 2.4.0.test2 version. However, it displays error > messages when I set the Neponset support. (CONFIG_ASSABET_NEPONSET = y) This patch version was missing the definition of CONFIG_SA1111 when CONFIG_ASSABET_NEPONSET is selected. Please use my latest patch which has many things fixed. Nicolas unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Tue Jul 18 15:34:18 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13EYRt-0005Ng-00 for linux-arm-archive@lists.arm.linux.org.uk; Tue, 18 Jul 2000 15:34:17 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 75FDC15EC2; Tue, 18 Jul 2000 16:26:08 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 18 Jul 2000 09:57:48 -0400 Received: by vger.rutgers.edu id ; Tue, 18 Jul 2000 09:57:25 -0400 Received: from flatpanels.com ([207.196.69.66]:2616 "EHLO ADSServer.flatpanels.com") by vger.rutgers.edu with ESMTP id ; Tue, 18 Jul 2000 09:57:02 -0400 Received: by flatpanels.com with Internet Mail Service (5.5.2650.21) id ; Tue, 18 Jul 2000 10:03:34 -0400 Message-ID: <91B07CA588CED3118CFE00105AC97594026FB8@flatpanels.com> From: "Huh, Woojung" To: "Sa1100-Linux (E-mail)" , "Linux-Arm (E-mail)" Cc: "Nicolas Pitre (E-mail)" Subject: [Q] gdb on ARM Linux Date: Tue, 18 Jul 2000 10:03:33 -0400 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@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Hi, I'm trying to use gdb on ARM linux (2.4.0-test2-ac1-rmk2-np3) I am able to run "gdb" itself and execute some internal commands. But when I tried to load application with "file" command or execute "gdb xxx". Then gdb displays "gdb: error in loading shared libraries: gdb: undefined symbol: __umodsi3" as follows. I'm using original ramdisk_img.gz Is there anyone who used gdb ? Thanks, [root@Linux /root]$gdb GNU gdb 19991011 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "armv4l-redhat-linux". (gdb) (gdb) (gdb) (gdb) file a gdb: error in loading shared libraries: gdb: undefined symbol: __umodsi3 Woojung Huh unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Tue Jul 18 16:03:55 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13EYuY-0005fy-00 for linux-arm-archive@lists.arm.linux.org.uk; Tue, 18 Jul 2000 16:03:54 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id B509215D47; Tue, 18 Jul 2000 17:03:56 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 18 Jul 2000 10:47:41 -0400 Received: by vger.rutgers.edu id ; Tue, 18 Jul 2000 10:47:35 -0400 Received: from penguin-ext.wise.edt.ericsson.se ([194.237.142.110]:61202 "EHLO penguin-ext.wise.edt.ericsson.se") by vger.rutgers.edu with ESMTP id ; Tue, 18 Jul 2000 10:47:24 -0400 Received: from esealnt409.al.sw.ericsson.se (esealnt409.al.sw.ericsson.se [153.88.251.32]) by penguin.wise.edt.ericsson.se (8.10.1/8.10.1/WIREfire-1.3) with ESMTP id e6IF2cM20901 for ; Tue, 18 Jul 2000 17:02:38 +0200 (MEST) Received: from SMTP ([153.88.251.32]) by esealnt409.al.sw.ericsson.se with Microsoft SMTPSVC(5.0.2172.1); Tue, 18 Jul 2000 17:02:38 +0200 Received: from esealnt743.al.sw.ericsson.se ([153.88.251.13]) by 153.88.251.32 (Norton AntiVirus for Internet Email Gateways 1.0) ; Tue, 18 Jul 2000 15:02:38 0000 (GMT) Received: by esealnt743.al.sw.ericsson.se with Internet Mail Service (5.5.2651.58) id ; Tue, 18 Jul 2000 17:02:36 +0200 Message-ID: From: "Arjan Opmeer (EMN)" To: "'linux-arm@vger.rutgers.edu'" Subject: Status of Ethernet/USB on SA1110/SA1111 board? Date: Tue, 18 Jul 2000 17:02:34 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2651.58) Content-Type: text/plain; charset="ISO-8859-1" X-OriginalArrivalTime: 18 Jul 2000 15:02:38.0518 (UTC) FILETIME=[369F8560:01BFF0C9] Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Hi, For a project here at work I would like to use the internal Ethernet interface and the USB host port on the SA1111 board. What is the status on these two? It seems that they aren't supported yet in Nico's latest patch. But the SMC Ethernet driver and the OHCI USB driver are already available. So it seems to me that it takes some hacking and glueing to get the thing working. Or am I mistaken? Is there maybe someone working on enabling either of the two of them? I don't mind to try to write the necessary code myself, but if someone else already has started something I would rather build further on that. (Not to mention that at the moment I am busy studying the code base and getting to understand the memory mapping and IRQ usage and things like that... :-) So if anyone out there is working on these issues and wants to share his/her code with me so I can help with developing and debugging, could you please email me? Thanks! Best regards, Arjan Opmeer unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Tue Jul 18 16:15:10 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13EZ5R-0005kp-00 for linux-arm-archive@lists.arm.linux.org.uk; Tue, 18 Jul 2000 16:15:09 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 1597415D53; Tue, 18 Jul 2000 17:15:12 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 18 Jul 2000 10:59:05 -0400 Received: by vger.rutgers.edu id ; Tue, 18 Jul 2000 10:58:59 -0400 Received: from [12.38.17.9] ([12.38.17.9]:2920 "EHLO mail.aeptec.com") by vger.rutgers.edu with ESMTP id ; Tue, 18 Jul 2000 10:58:47 -0400 Received: by MAIL with Internet Mail Service (5.5.2650.21) id ; Tue, 18 Jul 2000 11:04:50 -0400 Message-ID: <32CC5B62AF0BD2119E4C00A0C9663E221F3BD7@MAIL> From: "Sun, Lei" To: "'linux-arm@vger.rutgers.edu'" Subject: how to install rpm format pakage on arm-linux machine? Date: Tue, 18 Jul 2000 11:04:48 -0400 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@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Hi: I was trying to install apache server into my SA1110 assabet. I downloaded the binary for armv4l from netwinder websites. The only way I think is to copy all the files into the ramdisk. But I noticed that the binary is xxxx.armv4l.rpm format. How do I extract the files and copy it into the corresponding directory in my ramdisk? it's not a relocable pakage, I can't relocate to a sigel directory. thank you! Lei Sun unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Tue Jul 18 16:55:36 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13EZia-00063X-00 for linux-arm-archive@lists.arm.linux.org.uk; Tue, 18 Jul 2000 16:55:36 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 0BD2915DB7; Tue, 18 Jul 2000 17:54:46 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 18 Jul 2000 11:38:49 -0400 Received: by vger.rutgers.edu id ; Tue, 18 Jul 2000 11:38:42 -0400 Received: from [12.38.17.9] ([12.38.17.9]:3130 "EHLO mail.aeptec.com") by vger.rutgers.edu with ESMTP id ; Tue, 18 Jul 2000 11:38:31 -0400 Received: by MAIL with Internet Mail Service (5.5.2650.21) id ; Tue, 18 Jul 2000 11:44:36 -0400 Message-ID: <32CC5B62AF0BD2119E4C00A0C9663E221F3BDA@MAIL> From: "Sun, Lei" To: 'Nicolas Pitre' , Sun-Gi Hong Cc: linux-arm@vger.rutgers.edu Subject: RE: [Q] Kernel Compilation Error (2.4.0.test2 version) Date: Tue, 18 Jul 2000 11:44:34 -0400 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@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Hi: where is nico's latest patch (2.4.0-test4)? what's problem has been fixed ? -----Original Message----- From: Nicolas Pitre [mailto:nico@cam.org] Sent: Tuesday, July 18, 2000 9:43 AM To: Sun-Gi Hong Cc: linux-arm@vger.rutgers.edu Subject: Re: [Q] Kernel Compilation Error (2.4.0.test2 version) On Tue, 18 Jul 2000, Sun-Gi Hong wrote: > Greetings, > > I've already compiled the kernel 2.4.0.test1 version, now I try to > compile the kernel 2.4.0.test2 version. However, it displays error > messages when I set the Neponset support. (CONFIG_ASSABET_NEPONSET = y) This patch version was missing the definition of CONFIG_SA1111 when CONFIG_ASSABET_NEPONSET is selected. Please use my latest patch which has many things fixed. Nicolas unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Tue Jul 18 17:52:05 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13EabC-0006QO-00 for linux-arm-archive@lists.arm.linux.org.uk; Tue, 18 Jul 2000 17:52:03 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id A6A5815DD4; Tue, 18 Jul 2000 18:51:40 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 18 Jul 2000 12:35:21 -0400 Received: by vger.rutgers.edu id ; Tue, 18 Jul 2000 12:21:46 -0400 Received: from smtp02.wxs.nl ([195.121.6.60]:49604 "EHLO smtp02.wxs.nl") by vger.rutgers.edu with ESMTP id ; Tue, 18 Jul 2000 12:21:12 -0400 Received: from flipje.test ([195.121.177.218]) by smtp02.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAB1215; Tue, 18 Jul 2000 18:34:48 +0200 Received: (from mark@localhost) by flipje.test (8.9.3/8.9.1) id JAA11689; Tue, 18 Jul 2000 09:39:27 +0200 Date: Tue, 18 Jul 2000 09:39:27 +0200 From: Mark van Doesburg Message-Id: <200007180739.JAA11689@flipje.test> To: linux-arm@vger.rutgers.edu, waa@cs.umd.edu Subject: Re: EBSA-285 v2.4 Kernel .config? Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Does anyone have a kernel .config file for an EBSA-285 in add-in mode that results in an image? I've tried numerous settings with v2.4.0-test2-acl-rmk3 and haven't been able to get to an image yet. Thanks, Bill p.s. At this point, I'll settle for a v2.3. If you mean the co285 architecture complete with networking over the PCI interface you're out of luck. I haven't done any work on it for a few months. If everything goes as planned I will make a ppc version in december and will probably try to get the ebsa285 going again as well. greetings, Mark. unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Tue Jul 18 18:32:35 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13EbEQ-0006iM-00 for linux-arm-archive@lists.arm.linux.org.uk; Tue, 18 Jul 2000 18:32:35 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id ED79B15D72; Tue, 18 Jul 2000 19:32:31 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 18 Jul 2000 13:16:23 -0400 Received: by vger.rutgers.edu id ; Tue, 18 Jul 2000 13:16:10 -0400 Received: from ringding.cs.umd.edu ([128.8.126.2]:61075 "EHLO ringding.cs.umd.edu") by vger.rutgers.edu with ESMTP id ; Tue, 18 Jul 2000 13:15:14 -0400 Received: from localhost (localhost [127.0.0.1]) by ringding.cs.umd.edu (8.9.3/8.9.1) with ESMTP id NAA09269; Tue, 18 Jul 2000 13:30:15 -0400 (EDT) Date: Tue, 18 Jul 2000 13:30:15 -0400 (EDT) From: Bill Arbaugh To: Mark van Doesburg Cc: linux-arm@vger.rutgers.edu Subject: Re: EBSA-285 v2.4 Kernel .config? In-Reply-To: <200007180739.JAA11689@flipje.test> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu What's the last working version you have, and where can I find it? Thanks, Bill On Tue, 18 Jul 2000, Mark van Doesburg wrote: > Does anyone have a kernel .config file for an EBSA-285 in add-in > mode that results in an image? I've tried numerous settings > with v2.4.0-test2-acl-rmk3 and haven't been able to get to an > image yet. > > Thanks, Bill > > p.s. At this point, I'll settle for a v2.3. > > If you mean the co285 architecture complete with networking over the > PCI interface you're out of luck. I haven't done any work on it for a > few months. If everything goes as planned I will make a ppc version in > december and will probably try to get the ebsa285 going again as well. > > greetings, > > Mark. > unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Tue Jul 18 18:38:15 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13EbJt-0006kA-00 for linux-arm-archive@lists.arm.linux.org.uk; Tue, 18 Jul 2000 18:38:14 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 0582D15D72; Tue, 18 Jul 2000 19:38:11 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 18 Jul 2000 13:22:18 -0400 Received: by vger.rutgers.edu id ; Tue, 18 Jul 2000 13:22:03 -0400 Received: from ringding.cs.umd.edu ([128.8.126.2]:61171 "EHLO ringding.cs.umd.edu") by vger.rutgers.edu with ESMTP id ; Tue, 18 Jul 2000 13:21:41 -0400 Received: from localhost (localhost [127.0.0.1]) by ringding.cs.umd.edu (8.9.3/8.9.1) with ESMTP id NAA09471; Tue, 18 Jul 2000 13:36:52 -0400 (EDT) Date: Tue, 18 Jul 2000 13:36:52 -0400 (EDT) From: Bill Arbaugh To: Russell King - ARM Linux Admin Cc: linux-arm@vger.rutgers.edu Subject: Re: EBSA-285 v2.4 Kernel .config? In-Reply-To: <200007180659.HAA20460@flint.arm.linux.org.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Russell, My config is easy. I just did a make footbridge_config, and then set the processor type to footbridge, selected EBSA285 add-in, and de-selected netwinder. I've attached it at the end (it has the further changes described below). Here's what I've found out so far. The compile kicks out due to a preprocess error in memory.h. Tracing it down- it looks like while CONFIG_FOOTBRIDGE_ADDIN is defined, CONFIG_ARCH_CO285 is not. I manually setting CONFIG_ARCH_CO285 in .config (after make clean; make dep). Didn't eliminate the problem. Setting it manually in include/linux/autoconf.h did. Unfortunately, I can't help much on this since I don't know anything about Linux's config magic (I'm a BSD guy). The above change resulting in an error that PCIIACK_BASE was undeclared in irq.h. I followed that to include/asm/arch/hardware.h which had at line 14: #ifdef CONFIG_FOOTBRIDGE_HOST I changed that line to: #if defined(CONFIG_FOOTBRIDGE_HOST) || defined(CONFIG_FOOTBRIDGE_ADDIN) That gets me through the compile, but then the linker complains of several undefined references: boot_memory_end boot_commandL_line have_isa_bridge The last is from bios32.c which isn't added to the obj list in the kernel dir (no idea why). The boot symbols- I can't find. Bill ------------------------------------------------------------------------------ # # Automatically generated by make menuconfig: don't edit # CONFIG_ARM=y # CONFIG_SBUS is not set CONFIG_UID16=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y # CONFIG_OBSOLETE is not set # # System Type # # CONFIG_ARCH_ARC is not set # CONFIG_ARCH_A5K is not set # CONFIG_ARCH_CO285 is not set # CONFIG_ARCH_EBSA110 is not set CONFIG_ARCH_FOOTBRIDGE=y # CONFIG_ARCH_RPC is not set # CONFIG_ARCH_SA1100 is not set # CONFIG_ARCH_CATS is not set # CONFIG_ARCH_PERSONAL_SERVER is not set CONFIG_ARCH_EBSA285_ADDIN=y # CONFIG_ARCH_EBSA285_HOST is not set # CONFIG_ARCH_NETWINDER is not set CONFIG_CPU_32=y # CONFIG_CPU_26 is not set CONFIG_CPU_32v4=y CONFIG_CPU_SA110=y # CONFIG_ARCH_ACORN is not set CONFIG_FOOTBRIDGE=y # CONFIG_FOOTBRIDGE_HOST is not set CONFIG_FOOTBRIDGE_ADDIN=y CONFIG_ARCH_EBSA285=y # CONFIG_DISCONTIGMEM is not set # CONFIG_PCI is not set # CONFIG_ISA is not set # CONFIG_ISA_DMA is not set # # Loadable module support # CONFIG_MODULES=y # CONFIG_MODVERSIONS is not set CONFIG_KMOD=y # # General setup # # CONFIG_HOTPLUG is not set # CONFIG_PCMCIA is not set CONFIG_NET=y CONFIG_SYSVIPC=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_SYSCTL=y CONFIG_NWFPE=y CONFIG_KCORE_ELF=y # CONFIG_KCORE_AOUT is not set CONFIG_BINFMT_AOUT=y CONFIG_BINFMT_ELF=y # CONFIG_BINFMT_MISC is not set # CONFIG_PM is not set # CONFIG_ARTHUR is not set CONFIG_LEDS=y CONFIG_LEDS_TIMER=y # CONFIG_LEDS_CPU is not set CONFIG_ALIGNMENT_TRAP=y # # Parallel port support # CONFIG_PARPORT=y CONFIG_PARPORT_PC=y CONFIG_PARPORT_PC_FIFO=y # CONFIG_PARPORT_PC_SUPERIO is not set # CONFIG_PARPORT_ARC is not set # CONFIG_PARPORT_AMIGA is not set # CONFIG_PARPORT_MFC3 is not set # CONFIG_PARPORT_ATARI is not set # CONFIG_PARPORT_SUNBPP is not set # CONFIG_PARPORT_OTHER is not set CONFIG_PARPORT_1284=y # # Plug and Play configuration # CONFIG_PNP=y CONFIG_ISAPNP=y # # Block devices # # CONFIG_BLK_DEV_FD is not set # CONFIG_BLK_DEV_XD is not set CONFIG_PARIDE=m CONFIG_PARIDE_PARPORT=y CONFIG_PARIDE_PD=m CONFIG_PARIDE_PCD=m CONFIG_PARIDE_PF=m CONFIG_PARIDE_PT=m CONFIG_PARIDE_PG=m CONFIG_PARIDE_ATEN=m CONFIG_PARIDE_BPCK=m CONFIG_PARIDE_COMM=m CONFIG_PARIDE_DSTR=m CONFIG_PARIDE_FIT2=m CONFIG_PARIDE_FIT3=m CONFIG_PARIDE_EPAT=m CONFIG_PARIDE_EPIA=m CONFIG_PARIDE_FRIQ=m CONFIG_PARIDE_FRPW=m CONFIG_PARIDE_KBIC=m CONFIG_PARIDE_KTTI=m CONFIG_PARIDE_ON20=m CONFIG_PARIDE_ON26=m # CONFIG_BLK_CPQ_DA is not set # CONFIG_BLK_DEV_DAC960 is not set CONFIG_BLK_DEV_LOOP=m CONFIG_BLK_DEV_NBD=m # CONFIG_BLK_DEV_LVM is not set # CONFIG_BLK_DEV_MD is not set # CONFIG_MD_LINEAR is not set # CONFIG_MD_RAID0 is not set # CONFIG_MD_RAID1 is not set # CONFIG_MD_RAID5 is not set CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_RAM_SIZE=4096 # CONFIG_BLK_DEV_INITRD is not set # # Networking options # CONFIG_PACKET=y CONFIG_PACKET_MMAP=y # CONFIG_NETLINK is not set # CONFIG_NETFILTER is not set # CONFIG_FILTER is not set CONFIG_UNIX=y CONFIG_INET=y # CONFIG_IP_MULTICAST is not set # CONFIG_IP_ADVANCED_ROUTER is not set CONFIG_IP_PNP=y CONFIG_IP_PNP_BOOTP=y # CONFIG_IP_PNP_RARP is not set # CONFIG_IP_ROUTER is not set # CONFIG_NET_IPIP is not set # CONFIG_NET_IPGRE is not set CONFIG_IP_ALIAS=y CONFIG_SYN_COOKIES=y # CONFIG_SKB_LARGE is not set # CONFIG_IPV6 is not set # CONFIG_KHTTPD is not set # CONFIG_ATM is not set # CONFIG_IPX is not set # CONFIG_ATALK is not set # CONFIG_DECNET is not set # CONFIG_BRIDGE is not set # CONFIG_X25 is not set # CONFIG_LAPB is not set # CONFIG_LLC is not set # CONFIG_ECONET is not set # CONFIG_WAN_ROUTER is not set # CONFIG_NET_FASTROUTE is not set # CONFIG_NET_HW_FLOWCONTROL is not set # # QoS and/or fair queueing # # CONFIG_NET_SCHED is not set # # Network device support # CONFIG_NETDEVICES=y # # ARCnet devices # # CONFIG_ARCNET is not set # CONFIG_DUMMY is not set # CONFIG_BONDING is not set # CONFIG_EQUALIZER is not set # CONFIG_NET_SB1000 is not set # # Ethernet (10 or 100Mbit) # CONFIG_NET_ETHERNET=y # CONFIG_ARM_AM79C961A is not set CONFIG_NET_VENDOR_3COM=y # CONFIG_EL1 is not set # CONFIG_EL2 is not set # CONFIG_ELPLUS is not set # CONFIG_EL16 is not set # CONFIG_EL3 is not set # CONFIG_3C515 is not set CONFIG_VORTEX=y # CONFIG_LANCE is not set # CONFIG_NET_VENDOR_SMC is not set # CONFIG_NET_VENDOR_RACAL is not set # CONFIG_AT1700 is not set # CONFIG_DEPCA is not set # CONFIG_NET_ISA is not set CONFIG_NET_PCI=y # CONFIG_PCNET32 is not set # CONFIG_ADAPTEC_STARFIRE is not set # CONFIG_AC3200 is not set # CONFIG_APRICOT is not set # CONFIG_CS89x0 is not set # CONFIG_DE4X5 is not set # CONFIG_TULIP is not set # CONFIG_DGRS is not set # CONFIG_DM9102 is not set # CONFIG_EEPRO100 is not set # CONFIG_LNE390 is not set # CONFIG_NE3210 is not set # CONFIG_NE2K_PCI is not set # CONFIG_RTL8129 is not set # CONFIG_8139TOO is not set # CONFIG_SIS900 is not set # CONFIG_TLAN is not set # CONFIG_VIA_RHINE is not set # CONFIG_ES3210 is not set # CONFIG_EPIC100 is not set # CONFIG_NET_POCKET is not set # # Ethernet (1000 Mbit) # # CONFIG_YELLOWFIN is not set # CONFIG_ACENIC is not set # CONFIG_SK98LIN is not set # CONFIG_FDDI is not set # CONFIG_HIPPI is not set # CONFIG_PLIP is not set CONFIG_PPP=m # CONFIG_PPP_MULTILINK is not set CONFIG_PPP_ASYNC=m # CONFIG_PPP_SYNC_TTY is not set CONFIG_PPP_DEFLATE=m CONFIG_PPP_BSDCOMP=m CONFIG_PPPOE=m CONFIG_SLIP=m CONFIG_SLIP_COMPRESSED=y CONFIG_SLIP_SMART=y CONFIG_SLIP_MODE_SLIP6=y # # Wireless LAN (non-hamradio) # # CONFIG_NET_RADIO is not set # # Token Ring devices # # CONFIG_TR is not set # CONFIG_NET_FC is not set # CONFIG_RCPCI is not set # CONFIG_SHAPER is not set # # Wan interfaces # # CONFIG_WAN is not set # # Amateur Radio support # # CONFIG_HAMRADIO is not set # # IrDA (infrared) support # CONFIG_IRDA=m CONFIG_IRLAN=m CONFIG_IRCOMM=m CONFIG_IRDA_ULTRA=y CONFIG_IRDA_OPTIONS=y CONFIG_IRDA_CACHE_LAST_LSAP=y CONFIG_IRDA_FAST_RR=y # CONFIG_IRDA_DEBUG is not set # CONFIG_IRDA_COMPRESSION is not set # # Infrared-port device drivers # # CONFIG_IRTTY_SIR is not set # CONFIG_IRPORT_SIR is not set # CONFIG_NSC_FIR is not set CONFIG_WINBOND_FIR=m # CONFIG_TOSHIBA_FIR is not set # CONFIG_SMC_IRCC_FIR is not set # CONFIG_DONGLE is not set # # ATA/IDE/MFM/RLL support # CONFIG_IDE=y # # IDE, ATA and ATAPI Block devices # CONFIG_BLK_DEV_IDE=y # CONFIG_BLK_DEV_HD_IDE is not set # CONFIG_BLK_DEV_HD is not set CONFIG_BLK_DEV_IDEDISK=y CONFIG_IDEDISK_MULTI_MODE=y # CONFIG_BLK_DEV_IDEDISK_VENDOR is not set # CONFIG_BLK_DEV_IDEDISK_FUJITSU is not set # CONFIG_BLK_DEV_IDEDISK_IBM is not set # CONFIG_BLK_DEV_IDEDISK_MAXTOR is not set # CONFIG_BLK_DEV_IDEDISK_QUANTUM is not set # CONFIG_BLK_DEV_IDEDISK_SEAGATE is not set # CONFIG_BLK_DEV_IDEDISK_WD is not set # CONFIG_BLK_DEV_COMMERIAL is not set # CONFIG_BLK_DEV_TIVO is not set # CONFIG_BLK_DEV_IDECS is not set # CONFIG_BLK_DEV_IDECD is not set # CONFIG_BLK_DEV_IDETAPE is not set # CONFIG_BLK_DEV_IDEFLOPPY is not set # CONFIG_BLK_DEV_IDESCSI is not set # CONFIG_BLK_DEV_CMD640 is not set # CONFIG_BLK_DEV_CMD640_ENHANCED is not set # CONFIG_BLK_DEV_ISAPNP is not set # CONFIG_IDE_CHIPSETS is not set CONFIG_IDEDMA_AUTO=y # CONFIG_IDEDMA_IVB is not set # CONFIG_DMA_NONPCI is not set CONFIG_BLK_DEV_IDE_MODES=y # # SCSI support # # CONFIG_SCSI is not set # # I2O device support # # CONFIG_I2O is not set # CONFIG_I2O_BLOCK is not set # CONFIG_I2O_LAN is not set # CONFIG_I2O_SCSI is not set # CONFIG_I2O_PROC is not set # # ISDN subsystem # # CONFIG_ISDN is not set # # Character devices # CONFIG_VT=y CONFIG_VT_CONSOLE=y CONFIG_SERIAL=y CONFIG_SERIAL_CONSOLE=y # CONFIG_SERIAL_EXTENDED is not set CONFIG_SERIAL_NONSTANDARD=y # CONFIG_COMPUTONE is not set # CONFIG_ROCKETPORT is not set # CONFIG_CYCLADES is not set # CONFIG_DIGIEPCA is not set # CONFIG_DIGI is not set # CONFIG_ESPSERIAL is not set # CONFIG_MOXA_INTELLIO is not set # CONFIG_MOXA_SMARTIO is not set # CONFIG_ISI is not set # CONFIG_SYNCLINK is not set # CONFIG_N_HDLC is not set # CONFIG_RISCOM8 is not set # CONFIG_SPECIALIX is not set # CONFIG_SX is not set # CONFIG_RIO is not set # CONFIG_STALDRV is not set CONFIG_SERIAL_21285=y CONFIG_SERIAL_21285_CONSOLE=y CONFIG_UNIX98_PTYS=y CONFIG_UNIX98_PTY_COUNT=256 CONFIG_PRINTER=m # CONFIG_LP_CONSOLE is not set # CONFIG_PPDEV is not set # # I2C support # CONFIG_I2C=m # CONFIG_I2C_ALGOBIT is not set # CONFIG_I2C_ALGOPCF is not set # CONFIG_I2C_CHARDEV is not set # # Mice # # CONFIG_BUSMOUSE is not set CONFIG_MOUSE=y CONFIG_PSMOUSE=y # CONFIG_82C710_MOUSE is not set # CONFIG_PC110_PAD is not set # # Joysticks # # CONFIG_JOYSTICK is not set # CONFIG_QIC02_TAPE is not set # # Watchdog Cards # CONFIG_WATCHDOG=y # CONFIG_WATCHDOG_NOWAYOUT is not set # CONFIG_WDT is not set # CONFIG_WDTPCI is not set CONFIG_SOFT_WATCHDOG=y # CONFIG_PCWATCHDOG is not set # CONFIG_ACQUIRE_WDT is not set # CONFIG_60XX_WDT is not set # CONFIG_MIXCOMWD is not set CONFIG_21285_WATCHDOG=m # CONFIG_INTEL_RNG is not set CONFIG_NVRAM=m CONFIG_RTC=y # # Video For Linux # CONFIG_VIDEO_DEV=y # CONFIG_VIDEO_PROC_FS is not set # CONFIG_I2C_PARPORT is not set # CONFIG_RADIO_CADET is not set # CONFIG_RADIO_RTRACK is not set # CONFIG_RADIO_RTRACK2 is not set # CONFIG_RADIO_AZTECH is not set # CONFIG_RADIO_GEMTEK is not set # CONFIG_RADIO_MIROPCM20 is not set # CONFIG_RADIO_SF16FMI is not set # CONFIG_RADIO_TERRATEC is not set # CONFIG_RADIO_TRUST is not set # CONFIG_RADIO_TYPHOON is not set # CONFIG_RADIO_ZOLTRIX is not set # CONFIG_VIDEO_PMS is not set # CONFIG_VIDEO_BWQCAM is not set # CONFIG_VIDEO_CQCAM is not set # CONFIG_VIDEO_CPIA is not set # CONFIG_VIDEO_SAA5249 is not set # CONFIG_TUNER_3036 is not set # CONFIG_VIDEO_STRADIS is not set # CONFIG_VIDEO_ZORAN is not set # CONFIG_VIDEO_BUZ is not set # CONFIG_VIDEO_ZR36120 is not set # CONFIG_DTLK is not set # CONFIG_R3964 is not set # CONFIG_APPLICOM is not set # # Ftape, the floppy tape device driver # # CONFIG_FTAPE is not set # CONFIG_DRM is not set # CONFIG_DRM_TDFX is not set # CONFIG_AGP is not set # # File systems # # CONFIG_QUOTA is not set # CONFIG_AUTOFS_FS is not set CONFIG_AUTOFS4_FS=y CONFIG_ADFS_FS=m # CONFIG_ADFS_FS_RW is not set # CONFIG_AFFS_FS is not set # CONFIG_HFS_FS is not set # CONFIG_BFS_FS is not set CONFIG_FAT_FS=m CONFIG_MSDOS_FS=m # CONFIG_UMSDOS_FS is not set CONFIG_VFAT_FS=m # CONFIG_EFS_FS is not set # CONFIG_CRAMFS is not set # CONFIG_RAMFS is not set CONFIG_ISO9660_FS=m CONFIG_JOLIET=y # CONFIG_MINIX_FS is not set # CONFIG_NTFS_FS is not set # CONFIG_NTFS_RW is not set # CONFIG_HPFS_FS is not set CONFIG_PROC_FS=y # CONFIG_DEVFS_FS is not set # CONFIG_DEVFS_MOUNT is not set # CONFIG_DEVFS_DEBUG is not set CONFIG_DEVPTS_FS=y # CONFIG_QNX4FS_FS is not set # CONFIG_QNX4FS_RW is not set # CONFIG_ROMFS_FS is not set CONFIG_EXT2_FS=y # CONFIG_SYSV_FS is not set # CONFIG_SYSV_FS_WRITE is not set # CONFIG_UDF_FS is not set # CONFIG_UDF_RW is not set # CONFIG_UFS_FS is not set # CONFIG_UFS_FS_WRITE is not set # # Network File Systems # # CONFIG_CODA_FS is not set CONFIG_NFS_FS=y # CONFIG_NFS_V3 is not set CONFIG_ROOT_NFS=y CONFIG_NFSD=m # CONFIG_NFSD_V3 is not set CONFIG_SUNRPC=y CONFIG_LOCKD=y # CONFIG_SMB_FS is not set # CONFIG_NCP_FS is not set # CONFIG_NCPFS_PACKET_SIGNING is not set # CONFIG_NCPFS_IOCTL_LOCKING is not set # CONFIG_NCPFS_STRONG is not set # CONFIG_NCPFS_NFS_NS is not set # CONFIG_NCPFS_OS2_NS is not set # CONFIG_NCPFS_SMALLDOS is not set # CONFIG_NCPFS_MOUNT_SUBDIR is not set # CONFIG_NCPFS_NDS_DOMAINS is not set # CONFIG_NCPFS_NLS is not set # CONFIG_NCPFS_EXTRAS is not set # # Partition Types # CONFIG_PARTITION_ADVANCED=y CONFIG_ACORN_PARTITION=y # CONFIG_ACORN_PARTITION_ICS is not set CONFIG_ACORN_PARTITION_ADFS=y # CONFIG_ACORN_PARTITION_POWERTEC is not set # CONFIG_ACORN_PARTITION_RISCIX is not set # CONFIG_OSF_PARTITION is not set # CONFIG_AMIGA_PARTITION is not set # CONFIG_ATARI_PARTITION is not set # CONFIG_MAC_PARTITION is not set CONFIG_MSDOS_PARTITION=y # CONFIG_BSD_DISKLABEL is not set # CONFIG_SOLARIS_X86_PARTITION is not set # CONFIG_UNIXWARE_DISKLABEL is not set # CONFIG_SGI_PARTITION is not set # CONFIG_SUN_PARTITION is not set CONFIG_NLS=y # # Native Language Support # CONFIG_NLS_CODEPAGE_437=m # CONFIG_NLS_CODEPAGE_737 is not set # CONFIG_NLS_CODEPAGE_775 is not set CONFIG_NLS_CODEPAGE_850=m CONFIG_NLS_CODEPAGE_852=m # CONFIG_NLS_CODEPAGE_855 is not set # CONFIG_NLS_CODEPAGE_857 is not set # CONFIG_NLS_CODEPAGE_860 is not set # CONFIG_NLS_CODEPAGE_861 is not set # CONFIG_NLS_CODEPAGE_862 is not set # CONFIG_NLS_CODEPAGE_863 is not set # CONFIG_NLS_CODEPAGE_864 is not set # CONFIG_NLS_CODEPAGE_865 is not set # CONFIG_NLS_CODEPAGE_866 is not set # CONFIG_NLS_CODEPAGE_869 is not set # CONFIG_NLS_CODEPAGE_874 is not set CONFIG_NLS_ISO8859_1=m CONFIG_NLS_ISO8859_2=m # CONFIG_NLS_ISO8859_3 is not set # CONFIG_NLS_ISO8859_4 is not set # CONFIG_NLS_ISO8859_5 is not set # CONFIG_NLS_ISO8859_6 is not set # CONFIG_NLS_ISO8859_7 is not set # CONFIG_NLS_ISO8859_8 is not set # CONFIG_NLS_ISO8859_9 is not set # CONFIG_NLS_ISO8859_14 is not set CONFIG_NLS_ISO8859_15=m # CONFIG_NLS_KOI8_R is not set # # Console drivers # CONFIG_VGA_CONSOLE=y CONFIG_FB=y # # Frame-buffer support # CONFIG_FB=y CONFIG_DUMMY_CONSOLE=y # CONFIG_FB_VIRTUAL is not set CONFIG_FBCON_ADVANCED=y # CONFIG_FBCON_MFB is not set # CONFIG_FBCON_CFB2 is not set # CONFIG_FBCON_CFB4 is not set CONFIG_FBCON_CFB8=y CONFIG_FBCON_CFB16=y CONFIG_FBCON_CFB24=y # CONFIG_FBCON_CFB32 is not set # CONFIG_FBCON_AFB is not set # CONFIG_FBCON_ILBM is not set # CONFIG_FBCON_IPLAN2P2 is not set # CONFIG_FBCON_IPLAN2P4 is not set # CONFIG_FBCON_IPLAN2P8 is not set # CONFIG_FBCON_MAC is not set # CONFIG_FBCON_VGA_PLANES is not set CONFIG_FBCON_VGA=y # CONFIG_FBCON_HGA is not set # CONFIG_FBCON_FONTWIDTH8_ONLY is not set CONFIG_FBCON_FONTS=y # CONFIG_FONT_8x8 is not set # CONFIG_FONT_8x16 is not set # CONFIG_FONT_SUN8x16 is not set # CONFIG_FONT_SUN12x22 is not set # CONFIG_FONT_6x11 is not set # CONFIG_FONT_PEARL_8x8 is not set CONFIG_FONT_ACORN_8x8=y # # USB support # CONFIG_USB=m CONFIG_USB_DEBUG=y # CONFIG_USB_DEVICEFS is not set # CONFIG_USB_BANDWIDTH is not set # CONFIG_USB_UHCI is not set # CONFIG_USB_UHCI_ALT is not set CONFIG_USB_OHCI=m CONFIG_USB_PRINTER=m CONFIG_USB_SCANNER=m CONFIG_USB_AUDIO=m # CONFIG_USB_ACM is not set # CONFIG_USB_SERIAL is not set # CONFIG_USB_IBMCAM is not set # CONFIG_USB_OV511 is not set # CONFIG_USB_DC2XX is not set # CONFIG_USB_MDC800 is not set # CONFIG_USB_STORAGE is not set # CONFIG_USB_USS720 is not set # CONFIG_USB_DABUSB is not set # CONFIG_USB_PLUSB is not set # CONFIG_USB_PEGASUS is not set # CONFIG_USB_RIO500 is not set # CONFIG_USB_DSBR is not set # CONFIG_USB_MICROTEK is not set # CONFIG_USB_HID is not set CONFIG_USB_KBD=m CONFIG_USB_MOUSE=m # CONFIG_USB_WACOM is not set # CONFIG_INPUT_IFORCE_USB is not set # CONFIG_INPUT_KEYBDEV is not set # CONFIG_INPUT_MOUSEDEV is not set # CONFIG_INPUT_JOYDEV is not set # CONFIG_INPUT_EVDEV is not set # # Kernel hacking # CONFIG_FRAME_POINTER=y CONFIG_DEBUG_ERRORS=y CONFIG_DEBUG_USER=y # CONFIG_DEBUG_INFO is not set CONFIG_MAGIC_SYSRQ=y CONFIG_DEBUG_LL=y # CONFIG_DEBUG_DC21285_PORT is not set unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Thu Jul 20 09:57:01 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13FC8b-0006Ic-00 for linux-arm-archive@lists.arm.linux.org.uk; Thu, 20 Jul 2000 09:57:01 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id DCC9016293; Thu, 20 Jul 2000 10:34:26 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 18 Jul 2000 15:42:35 -0400 Received: by vger.rutgers.edu id ; Tue, 18 Jul 2000 15:41:20 -0400 Received: from p50-robin-gui.tch.enablis.net ([194.168.180.110]:4315 "EHLO caramon.arm.linux.org.uk") by vger.rutgers.edu with ESMTP id ; Tue, 18 Jul 2000 15:40:26 -0400 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 UAA13780; Tue, 18 Jul 2000 20:55:30 +0100 Received: (from linux@localhost) by flint.arm.linux.org.uk (8.9.3/8.9.3) id UAA22552; Tue, 18 Jul 2000 20:54:38 +0100 From: Russell King - ARM Linux Admin Message-Id: <200007181954.UAA22552@flint.arm.linux.org.uk> Subject: Re: EBSA-285 v2.4 Kernel .config? To: waa@cs.umd.edu (Bill Arbaugh) Date: Tue, 18 Jul 2000 20:54:38 +0100 (BST) Cc: linux-arm@vger.rutgers.edu In-Reply-To: from "Bill Arbaugh" at Jul 18, 2000 01:36:52 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@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu I think firs thing I'll raise here is that there are two different "modes" to add-in ebsa285 support: 1. Plain EBSA285 add-in This is intended to result in a kernel which gives you all available user space, and be compatable with the ebsa285 host kernel. (this is "new", and probably ought to be marked as "experimental" at the moment) 2. co-EBSA285 This is Mark's "multi-processor" special thang - he can probably give you a detailed description of this than me. However, it does result in all kernel code and userspace squashed into the lower 2GB. Bill Arbaugh writes: > The above change resulting in an error that PCIIACK_BASE was undeclared in > irq.h. I followed that to include/asm/arch/hardware.h which had at line > 14: This is a real problem! include/asm-arm/arch-ebsa285/irq.h shouldn't be looking at the PCIIACK space, so this should probably be surrounded by a suitable #ifdef CONFIG_FOOTBRIDGE_HOST macro. > That gets me through the compile, but then the linker complains of several > undefined references: > boot_memory_end > boot_commandL_line > have_isa_bridge > > The last is from bios32.c which isn't added to the obj list in the kernel > dir (no idea why). The boot symbols- I can't find. Well, the "quick hack" approach would be to #define have_isa_bridge 0 where-ever it is used, but I certainly won't accept a patch like that ;) It needs to be inteligently defined, dependent on the configuration options selected by the user (something that I'll sort out for the next release). The other two were iirc a couple of definitions I wasn't happy about. I don't think the final hunk is required, and should probably be cut off. (PS, this is from patch 178/1). diff -uNr orig/linux/arch/arm/kernel/head-armv.S linux/arch/arm/kernel/head-armv.S --- orig/linux/arch/arm/kernel/head-armv.S Thu May 6 16:39:24 1999 +++ linux/arch/arm/kernel/head-armv.S Thu May 6 14:30:29 1999 @@ -7,6 +7,7 @@ */ #include #include +#include .globl SYMBOL_NAME(swapper_pg_dir) .equ SYMBOL_NAME(swapper_pg_dir), TEXTADDR - 0x4000 @@ -56,6 +57,46 @@ mov r1, #5 #endif +#ifdef CONFIG_ARCH_CO285 + .globl SYMBOL_NAME(boot_command_line) + .equ SYMBOL_NAME(boot_command_line), TEXTADDR - 0x5000 + + .globl SYMBOL_NAME(boot_memory_end) + .equ SYMBOL_NAME(boot_memory_end), TEXTADDR - 0x4004 + mov r11,#0xfc + orr r11,r11,#0x3f00 + str sp,[r11] + +#ifdef DEBUG + mov r11,#0x42000000 @ initialize uart + mov r12,#0 @ 9600,n,8,1 + str r12, [r11, #0x174] + mov r12,#80 + str r12, [r11, #0x170] + mov r12,#0 + str r12, [r11, #0x16c] + mov r12,#0x70 + str r12, [r11, #0x168] + mov r12,#1 + str r12, [r11, #0x174] + mov r12,#'x' + str r12, [r11, #0x160] + ldr r12, [r11, #0x178] + tst r12,#0x20 + bne .-8 + mov r12,#10 + str r12, [r11, #0x160] + ldr r12, [r11, #0x178] + tst r12,#0x20 + bne .-8 + mov r12,#13 + str r12, [r11, #0x160] + ldr r12, [r11, #0x178] + tst r12,#0x20 + bne .-8 +#endif // DEBUG +#endif // CONFIG_ARCH_CO285 + /* * Entry point and restart point. Entry *must* be called with r0 == 0, * MMU off. Note! These should be unique!!! Please read Documentation/ARM-README @@ -127,7 +168,9 @@ * This allows debug messages to be output via a serial * before/while paging_init. */ - add r0, r4, #0x3800 + mov r14,#(ARMCSR_BASE>>18) & 0xff + orr r14,r14,#(ARMCSR_BASE>>18) & 0xff00 + add r0, r4, r14 orr r3, r6, r8 add r2, r0, #0x0800 1: str r3, [r0], #4 _____ |_____| ------------------------------------------------- ---+---+- | | Russell King linux@arm.linux.org.uk --- --- | | | | http://www.arm.linux.org.uk/ / / | | +-+-+ --- -+- / | THE developer of ARM Linux |+| /|\ / | | | --- | +-+-+ ------------------------------------------------- /\\\ | unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Thu Jul 20 10:10:04 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13FCLE-0006Qv-00 for linux-arm-archive@lists.arm.linux.org.uk; Thu, 20 Jul 2000 10:10:04 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 21AEE162BA; Thu, 20 Jul 2000 10:40:19 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 18 Jul 2000 16:28:36 -0400 Received: by vger.rutgers.edu id ; Tue, 18 Jul 2000 16:28:30 -0400 Received: from [63.195.182.101] ([63.195.182.101]:3007 "EHLO barbados.bluemug.com") by vger.rutgers.edu with ESMTP id ; Tue, 18 Jul 2000 16:28:11 -0400 Received: from fiji.bluemug.com [192.168.50.32] (mail) by barbados.bluemug.com with esmtp (Exim 2.05 #1 (Debian)) id 13EeDC-0000WN-00; Tue, 18 Jul 2000 13:43:30 -0700 Received: from miket by fiji.bluemug.com with local (Exim 2.05 #1 (Debian)) id 13EeDB-0003cj-00; Tue, 18 Jul 2000 13:43:29 -0700 Date: Tue, 18 Jul 2000 13:43:29 -0700 From: Mike Touloumtzis To: Jim Gettys Cc: Mike Touloumtzis , Charlie Flynn , linux-arm@vger.rutgers.edu, handhelds@handhelds.org Subject: Re: [Handhelds] Re: Touch Screen Driver Generic Interface for all Linux SA11x0 platforms. Message-ID: <20000718134329.K13807@fiji.bluemug.com> References: <20000711105708.T21694@fiji.bluemug.com> <200007121815.LAA03539@pachyderm.pa.dec.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <200007121815.LAA03539@pachyderm.pa.dec.com>; from Jim Gettys on Wed, Jul 12, 2000 at 11:15:57AM -0700 Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu On Wed, Jul 12, 2000 at 11:15:57AM -0700, Jim Gettys wrote: > > > > > -- Some digitizers have non-linear input systems and need input munging > > beyond the simple device-independant translation/rotation/deskew that > > calibration can provide. Most devices work fine with the equivalent > > of a single affine transform at most, but I know of at least one > > shipping touchscreen PDA/phone in Japan that essentially requires a > > system of linear equations to normalize coordinates, and also has > > two "dead zones" that must be worked around. > > Question: is a single affine transform going to get more than 90% of the > devices out there? If so, lets run with this, and be done with it; leave > the others to suffer for their own sins of bad hardware... > (sorry for the delay; I'm pretty burst with mailing list mail) I don't know with how much hardware an affine transform will work; I'm not really a digitizer expert, I've just worked with a number of specific components. It certainly seems reasonable to say "the kernel driver will normalize the coordinates if it's easy to do so, otherwise it'll somehow convey the device type to userspace, and it's the job of userspace to deal with weirdo hardware." miket unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Thu Jul 20 10:21:11 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13FCVz-0006XD-00 for linux-arm-archive@lists.arm.linux.org.uk; Thu, 20 Jul 2000 10:21:11 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id AEC66162C7; Thu, 20 Jul 2000 10:41:07 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 18 Jul 2000 20:11:29 -0400 Received: by vger.rutgers.edu id ; Tue, 18 Jul 2000 20:11:13 -0400 Received: from SMTP1.ANDREW.CMU.EDU ([128.2.10.81]:43249 "EHLO smtp1.andrew.cmu.edu") by vger.rutgers.edu with ESMTP id ; Tue, 18 Jul 2000 20:11:04 -0400 Received: from cs.cmu.edu (NINESIXTEEN.REM.CMU.EDU [128.2.81.157]) by smtp1.andrew.cmu.edu (8.9.3/8.9.3) with ESMTP id UAA18971; Tue, 18 Jul 2000 20:19:28 -0400 (EDT) Message-ID: <3974F3C8.803C597B@cs.cmu.edu> Date: Tue, 18 Jul 2000 20:18:16 -0400 From: John G Dorsey Organization: Carnegie Mellon University X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i686) X-Accept-Language: en MIME-Version: 1.0 To: Systems Administrator Cc: linux-arm@vger.rutgers.edu Subject: Re: SA-1110, SA-1111, BRUTUS, whatever References: <00071816382900.21123@rh6.gasboy.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Systems Administrator wrote: > How does a more intelligent person load a kernel and root file system into this > box? Such a person might read linux/Documentation/arm/SA1100/Assabet, or visit: http://www.cs.cmu.edu/~wearable/software/assabet.html -jd unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Thu Jul 20 10:27:28 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13FCc4-0006b6-00 for linux-arm-archive@lists.arm.linux.org.uk; Thu, 20 Jul 2000 10:27:28 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id EAC2A16394; Thu, 20 Jul 2000 10:44:37 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 18 Jul 2000 15:11:40 -0400 Received: by vger.rutgers.edu id ; Tue, 18 Jul 2000 14:25:17 -0400 Received: from ringding.cs.umd.edu ([128.8.126.2]:62313 "EHLO ringding.cs.umd.edu") by vger.rutgers.edu with ESMTP id ; Tue, 18 Jul 2000 14:24:36 -0400 Received: from localhost (localhost [127.0.0.1]) by ringding.cs.umd.edu (8.9.3/8.9.1) with ESMTP id OAA11194; Tue, 18 Jul 2000 14:39:45 -0400 (EDT) Date: Tue, 18 Jul 2000 14:39:44 -0400 (EDT) From: Bill Arbaugh To: Mark van Doesburg Cc: linux-arm@vger.rutgers.edu Subject: Re: EBSA-285 v2.4 Kernel .config? In-Reply-To: <200007181834.UAA00419@flipje.test> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu > > The last version I tried was 2.3.24-rmk1, you can find it on > ftp://nt4.el.utwente.nl/pub/co285 There's also a working Image available, > I'm not sure which version it is but I'm quite sure it worked for me. > Thanks- I'll give it a try. > Unfortunately you need to re-program the flash of the ebsa-285 and my > program isn't very user friendly. > I'm going to use the eCos safl utility to re-program the flash. It looks fairly straight forward. If it works, I'll post a copy of the source with directions. Basically, right now I'm trying to decide if I should use Linux or eCos. Both have advantages/disadvantages for what I want to do. Thanks, Bill unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Thu Jul 20 10:37:15 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13FClX-0006gO-00 for linux-arm-archive@lists.arm.linux.org.uk; Thu, 20 Jul 2000 10:37:15 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 2E7C7163C6; Thu, 20 Jul 2000 10:45:21 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 18 Jul 2000 21:17:21 -0400 Received: by vger.rutgers.edu id ; Tue, 18 Jul 2000 21:17:08 -0400 Received: from kirkland.gasboy.com ([204.57.208.52]:13599 "EHLO rh6.gasboy.com") by vger.rutgers.edu with ESMTP id ; Tue, 18 Jul 2000 21:12:30 -0400 Received: from localhost (localhost [[UNIX: localhost]]) by rh6.gasboy.com (8.9.3/8.9.3) id SAA21280 for linux-arm@vger.rutgers.edu; Tue, 18 Jul 2000 18:27:47 -0700 From: Systems Administrator To: linux-arm@vger.rutgers.edu Subject: Re: SA-1110, SA-1111, BRUTUS, whatever Date: Tue, 18 Jul 2000 18:16:30 -0700 X-Mailer: KMail [version 1.0.24] Content-Type: text/plain; charset=US-ASCII References: <3974F3C8.803C597B@cs.cmu.edu> MIME-Version: 1.0 Message-Id: <00071818274700.21266@rh6.gasboy.com> Content-Transfer-Encoding: 7BIT Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu On Tue, 18 Jul 2000, John G Dorsey wrote: > Systems Administrator wrote: > > > How does a more intelligent person load a kernel and root file system into this > > box? > > Such a person might read linux/Documentation/arm/SA1100/Assabet, or visit: > > http://www.cs.cmu.edu/~wearable/software/assabet.html > > -jd This people don't have a sa1100 directory under /usr/src/linux/Doc*/arm. As in redhat 6.2 just upgraded has Netwinder, nwfpe and and a README from Russel King. The www.cs.cmu.edu place seems to have gone out of business. This is quite normal for me. Any more suggestions? Mike Coburn Sys. Admin. "These are my opinions, and you can't have em" -- Bart Simpson unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Thu Jul 20 10:43:09 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13FCrF-0006lP-00 for linux-arm-archive@lists.arm.linux.org.uk; Thu, 20 Jul 2000 10:43:09 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id BCA3D163D5; Thu, 20 Jul 2000 10:45:34 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 18 Jul 2000 19:38:17 -0400 Received: by vger.rutgers.edu id ; Tue, 18 Jul 2000 19:38:09 -0400 Received: from kirkland.gasboy.com ([204.57.208.52]:13428 "EHLO rh6.gasboy.com") by vger.rutgers.edu with ESMTP id ; Tue, 18 Jul 2000 19:37:50 -0400 Received: from localhost (localhost [[UNIX: localhost]]) by rh6.gasboy.com (8.9.3/8.9.3) id QAA21148 for linux-arm@vger.rutgers.edu; Tue, 18 Jul 2000 16:53:07 -0700 From: Systems Administrator To: linux-arm@vger.rutgers.edu Subject: SA-1110, SA-1111, BRUTUS, whatever Date: Tue, 18 Jul 2000 16:18:25 -0700 X-Mailer: KMail [version 1.0.24] Content-Type: text/plain; charset=US-ASCII MIME-Version: 1.0 Message-Id: <00071816382900.21123@rh6.gasboy.com> Content-Transfer-Encoding: 7BIT Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu I have inherited a Strongarm Development Kit. I have a SA1110, and SA1111 and associated trivia, and some documentation. I have managed to get the thing stuck on to my linux box through minicom and I see "Angel Debug Monitor for DB1110 : Serial/FIQ : MMU on, n 4" or something close to that. I had to change the flash things from windows ce to angel, but I did manage. I can build a tool chain and a kernel. But how do I get executable stuff into the little box? Do I have to reflash the little postage stamp looking thingies or does this littel "angel" somehow manage to load a boot block and suck on the RS232 port or what? If so, how do it tell it to start inhaling? Maybe I'm supposed to hook the sa1111 board up and magically boot across the net, or put a kernel and root file system on a pcmcia card and slurp on it after plugging it into the sa1111. I can't find any documents that even mention the SA1111 or how it would be used. How does a more intelligent person load a kernel and root file system into this box? unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Thu Jul 20 10:53:25 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13FD1B-0006qb-00 for linux-arm-archive@lists.arm.linux.org.uk; Thu, 20 Jul 2000 10:53:25 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 11A6A163E8; Thu, 20 Jul 2000 10:46:00 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Wed, 19 Jul 2000 04:30:43 -0400 Received: by vger.rutgers.edu id ; Wed, 19 Jul 2000 04:30:25 -0400 Received: from navigator.sw.com.sg ([195.16.40.131]:39070 "EHLO navigator.sw.com.sg") by vger.rutgers.edu with ESMTP id ; Wed, 19 Jul 2000 04:30:20 -0400 Received: from slider.sw.ru (slider.sw.com.sg [195.16.40.254]) by navigator.sw.com.sg (8.9.1/8.9.1) with ESMTP id MAA08385 for ; Wed, 19 Jul 2000 12:45:08 +0400 (MSD) Received: from exchruhydro.sw.com.sg (exchruhydro.sw.com.sg [195.16.40.3]) by slider.sw.ru (8.9.1/8.9.1) with ESMTP id MAA26475 for ; Wed, 19 Jul 2000 12:44:59 +0400 (MSD) Received: from CYBER ([192.168.9.14]) by exchruhydro.sw.com.sg with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id PDSFCDXN; Wed, 19 Jul 2000 12:44:59 +0400 Message-ID: <009201bff15d$9f4ed720$0e09a8c0@cyber> From: "Gennadiy M. Kurtsman" To: Subject: Linux and SA-1100's FIQ Date: Wed, 19 Jul 2000 12:44:59 +0400 MIME-Version: 1.0 Content-Type: text/plain; charset="EUC-KR" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Hello everybody, I've tried to program ICLR register of interrupt controller of SA-1100 (revision G) so that level 11 interrupt was routed to CPU FIQ interrupt input. Then after interrupt pending Linux became dead (hung up without any reaction). When I don't touch ICLR register all work well. Am I wrong or it is defect of Linux or SA-1100? Any hint will be greatly appreciated. Gena Kurtsman. unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Thu Jul 20 14:04:11 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13FFzn-0000Jz-00 for linux-arm-archive@lists.arm.linux.org.uk; Thu, 20 Jul 2000 14:04:11 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 71B3A165E5; Thu, 20 Jul 2000 10:55:35 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Wed, 19 Jul 2000 09:07:18 -0400 Received: by vger.rutgers.edu id ; Wed, 19 Jul 2000 09:06:59 -0400 Received: from leonardo.telscom.ch ([193.247.121.34]:1942 "EHLO leonardo.telscom.ch") by vger.rutgers.edu with ESMTP id ; Wed, 19 Jul 2000 09:06:37 -0400 Received: from telscom.ch ([193.247.121.35]) by leonardo.telscom.ch (Post.Office MTA v3.1.2 release (PO205-101c) ID# 0-0U10L2S100) with ESMTP id AAA223 for ; Wed, 19 Jul 2000 15:15:08 +0200 Message-ID: <3975ADCC.3334A699@telscom.ch> Date: Wed, 19 Jul 2000 15:31:57 +0200 From: Mathias Teikari Organization: Telscom AG X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.15 i686) X-Accept-Language: en MIME-Version: 1.0 To: linux-arm Subject: BOOTP w. 2.4.0-test2 and EBSA-285 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Hi All, I have a problem using bootp with kernel 2.4.0-test2-ac1-rmk3 on my EBSA-285 with EEPro100 NIC. Everything looks good up until sending the bootp request, but then I get: Sending BOOTP requests............. timed out! IP-Config: Auto-configuration of network failed. I can see the bootp request packets on the network as well as the replies from the server, but the EBSA doesn't catch them. I realize this might be a problem on the server side just as well as on the EBSA but maybe someone has had similar problems before and could point me in the right direction. I use bootpd on a linux host and here's the /etc/bootptab galileo.telscom.ch: \ ht=ether: \ ha=0090278CD86B: \ ip=: \ sm=: \ gw=: \ ds= :\ hn: Any help is appreciated! Thanks for your time.. - Mathias -- +---------------------------------------------------------+ .--. | Mathias Teikari mathias.teikari@telscom.ch | |o_o | | Ba. Sc. EE. Office Ph: +41 (0)31 376 2030 | |:_/ | | SW Development Engineer Mobile Ph: +41 (0)76 541 9449 | // \ \ | Telscom AG Sandrainstr. 17, CH-3007 Bern | (| | ) | | /'\_ _/`\ +---------------- http://www.telscom.ch ------------------+ \___)=(___/ unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Thu Jul 20 14:57:30 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13FGpF-0000q3-00 for linux-arm-archive@lists.arm.linux.org.uk; Thu, 20 Jul 2000 14:57:25 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id C045716614; Thu, 20 Jul 2000 10:56:22 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 18 Jul 2000 14:20:56 -0400 Received: by vger.rutgers.edu id ; Tue, 18 Jul 2000 14:19:55 -0400 Received: from smtp06.wxs.nl ([195.121.6.58]:59041 "EHLO smtp06.wxs.nl") by vger.rutgers.edu with ESMTP id ; Tue, 18 Jul 2000 14:19:28 -0400 Received: from flipje.test ([195.121.176.35]) by smtp06.wxs.nl (Netscape Messaging Server 4.15) with ESMTP id FXWOX300.66O; Tue, 18 Jul 2000 20:34:15 +0200 Received: (from mark@localhost) by flipje.test (8.9.3/8.9.1) id UAA00419; Tue, 18 Jul 2000 20:34:37 +0200 Date: Tue, 18 Jul 2000 20:34:37 +0200 From: Mark van Doesburg Message-Id: <200007181834.UAA00419@flipje.test> To: waa@cs.umd.edu Subject: Re: EBSA-285 v2.4 Kernel .config? Cc: linux-arm@vger.rutgers.edu Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu What's the last working version you have, and where can I find it? The last version I tried was 2.3.24-rmk1, you can find it on ftp://nt4.el.utwente.nl/pub/co285 There's also a working Image available, I'm not sure which version it is but I'm quite sure it worked for me. Unfortunately you need to re-program the flash of the ebsa-285 and my program isn't very user friendly. greetings, Mark. unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Fri Jul 21 00:53:59 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13FQ8d-0007VA-00 for linux-arm-archive@lists.arm.linux.org.uk; Fri, 21 Jul 2000 00:53:59 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 5DE52166A2; Thu, 20 Jul 2000 11:59:55 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Thu, 20 Jul 2000 05:43:23 -0400 Received: by vger.rutgers.edu id ; Thu, 20 Jul 2000 05:43:15 -0400 Received: from p05-robin-gui.tch.enablis.net ([194.168.180.65]:1263 "EHLO caramon.arm.linux.org.uk") by vger.rutgers.edu with ESMTP id ; Thu, 20 Jul 2000 05:43:06 -0400 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 KAA20182; Thu, 20 Jul 2000 10:58:55 +0100 Received: (from linux@localhost) by flint.arm.linux.org.uk (8.9.3/8.9.3) id KAA27897; Thu, 20 Jul 2000 10:58:00 +0100 From: Russell King - ARM Linux Admin Message-Id: <200007200958.KAA27897@flint.arm.linux.org.uk> Subject: Re: Linux and SA-1100's FIQ To: krtsmn@infra2000.com (Gennadiy M. Kurtsman) Date: Thu, 20 Jul 2000 10:58:00 +0100 (BST) Cc: linux-arm@vger.rutgers.edu In-Reply-To: <009201bff15d$9f4ed720$0e09a8c0@cyber> from "Gennadiy M. Kurtsman" at Jul 19, 2000 12:44:59 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@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Gennadiy M. Kurtsman writes: > I've tried to program ICLR register of interrupt controller of SA-1100 > (revision G) so that level 11 interrupt was routed to CPU FIQ interrupt > input. Then after interrupt pending Linux became dead (hung up without any > reaction). When I don't touch ICLR register all work well. Am I wrong or it > is defect of Linux or SA-1100? Any hint will be greatly appreciated. Are you hooking into the FIQ vector? It is not supported via the normal "request_irq" stuff. _____ |_____| ------------------------------------------------- ---+---+- | | Russell King linux@arm.linux.org.uk --- --- | | | | http://www.arm.linux.org.uk/ / / | | +-+-+ --- -+- / | THE developer of ARM Linux |+| /|\ / | | | --- | +-+-+ ------------------------------------------------- /\\\ | unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Fri Jul 21 06:47:33 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13FVen-0002dR-00 for linux-arm-archive@lists.arm.linux.org.uk; Fri, 21 Jul 2000 06:47:33 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 2AFD416168; Thu, 20 Jul 2000 18:01:19 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Thu, 20 Jul 2000 11:44:32 -0400 Received: by vger.rutgers.edu id ; Thu, 20 Jul 2000 11:44:25 -0400 Received: from thalia.fm.intel.com ([132.233.247.11]:3089 "EHLO thalia.fm.intel.com") by vger.rutgers.edu with ESMTP id ; Thu, 20 Jul 2000 11:44:13 -0400 Received: from SMTP (fmsmsxvs01-1.fm.intel.com [132.233.42.201]) by thalia.fm.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.30 2000/06/08 18:25:35 dmccart Exp $) with SMTP id QAA13813; Thu, 20 Jul 2000 16:00:45 GMT Received: from fmsmsx17.intel.com ([132.233.48.17]) by 132.233.48.201 (Norton AntiVirus for Internet Email Gateways 1.0) ; Thu, 20 Jul 2000 15:59:47 0000 (GMT) Received: by fmsmsx17.fm.intel.com with Internet Mail Service (5.5.2650.21) id ; Thu, 20 Jul 2000 08:59:46 -0700 Message-ID: <4EE51D128990D211AC4100A0C96B1E44031444D1@fmsmsx74.fm.intel.com> From: "Meng, David" To: "'Nicolas Pitre'" , Sun-Gi Hong Cc: linux-arm@vger.rutgers.edu Subject: RE: [Q] Kernel Compilation Error (2.4.0.test2 version) Date: Thu, 20 Jul 2000 08:59:42 -0700 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@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Hi Nicolas: Would please let me know what package you used to build telnet utils in you ramdisk. I downloaded the telnet-0.10-29.src.rpm and tried to compile it use netwinder machine but go a lot of compiler errors. I would like to know which version of the telnet can be compiled and where to find the package. Regards. David unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Fri Jul 21 08:11:43 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13FWyF-0003UF-00 for linux-arm-archive@lists.arm.linux.org.uk; Fri, 21 Jul 2000 08:11:43 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 79A50167A1; Thu, 20 Jul 2000 19:09:13 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Thu, 20 Jul 2000 12:51:10 -0400 Received: by vger.rutgers.edu id ; Thu, 20 Jul 2000 12:50:02 -0400 Received: from [12.38.17.9] ([12.38.17.9]:2366 "EHLO mail.aeptec.com") by vger.rutgers.edu with ESMTP id ; Thu, 20 Jul 2000 12:49:33 -0400 Received: by MAIL with Internet Mail Service (5.5.2650.21) id ; Thu, 20 Jul 2000 12:56:23 -0400 Message-ID: <32CC5B62AF0BD2119E4C00A0C9663E221F3BE1@MAIL> From: "Sun, Lei" To: "'linux-arm@vger.rutgers.edu'" Cc: "'linux-arm-kernel@lists.arm.linux.org.uk'" Subject: socket comm. CF ethernet driver! Date: Thu, 20 Jul 2000 12:56:22 -0400 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@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Hi all: Sorry for the cross post! This is a old question but nobody answer me yet. I built linux-2.4.0-test2 with nico's patch and it's running in SA1110 Assabet with socket CF ethernet on it. right now there is a problem for the ethernet which has been torturing me for a long time. 1) after downloaded the kernel and boot up and configure the eth0, I can use telnet logon into my target from other machine, but after trying for a couple of time, the telnet will stuck at " Escape character is ^]" , however I can use telnet logon into other machine FROM the target, tried many times, no error occur. 2) I can use ftp logon to other machine and transfer files to or from my target, looks good, but each time I exit from the ftp program , the target console give me error message "eth0 interupt dropped". 3) as to use ftp logon to target from other machine, same thing with the telnet ( stucked after a couple of times). Nicolas said he had the same problem and won't have chance to fix it. I checked his latest patch (2.4.0-test4-np1), same thing happended. I was given this porting task for a month, now it's gonna due , but I haven't make the nework flow. So, if any one knows how to fix it, PLEASE, let me know. I think it's the driver problem. Which source file should I take a look? Thank you in advance! Regards Lei Sun unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Fri Jul 21 08:41:47 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13FXRL-0003pa-00 for linux-arm-archive@lists.arm.linux.org.uk; Fri, 21 Jul 2000 08:41:47 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id B9C62160F1; Thu, 20 Jul 2000 19:36:54 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Thu, 20 Jul 2000 13:11:45 -0400 Received: by vger.rutgers.edu id ; Thu, 20 Jul 2000 13:10:34 -0400 Received: from p16-robin-gui.tch.enablis.net ([194.168.180.76]:1465 "EHLO caramon.arm.linux.org.uk") by vger.rutgers.edu with ESMTP id ; Thu, 20 Jul 2000 13:09:32 -0400 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 SAA21677; Thu, 20 Jul 2000 18:25:28 +0100 Received: (from linux@localhost) by flint.arm.linux.org.uk (8.9.3/8.9.3) id SAA29287; Thu, 20 Jul 2000 18:24:34 +0100 From: Russell King - ARM Linux Admin Message-Id: <200007201724.SAA29287@flint.arm.linux.org.uk> Subject: Re: BOOTP w. 2.4.0-test2 and EBSA-285 To: mathias.teikari@telscom.ch (Mathias Teikari) Date: Thu, 20 Jul 2000 18:24:33 +0100 (BST) Cc: linux-arm@vger.rutgers.edu (linux-arm) In-Reply-To: <3975ADCC.3334A699@telscom.ch> from "Mathias Teikari" at Jul 19, 2000 03:31:57 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@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Mathias Teikari writes: > I can see the bootp request packets on the network as well as the > replies from the server, but the EBSA doesn't catch them. Could be one of many things. Can you give a "tcpdump -s 1540 -e -v" dump of the packets please? > galileo.telscom.ch: \ > ht=ether: \ > ha=0090278CD86B: \ > ip=: \ > sm=: \ > gw=: \ > ds= :\ > hn: The dns entries are redundant as far as the kernel goes. _____ |_____| ------------------------------------------------- ---+---+- | | Russell King linux@arm.linux.org.uk --- --- | | | | http://www.arm.linux.org.uk/ / / | | +-+-+ --- -+- / | THE developer of ARM Linux |+| /|\ / | | | --- | +-+-+ ------------------------------------------------- /\\\ | unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Fri Jul 21 08:59:30 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13FXiU-00040H-00 for linux-arm-archive@lists.arm.linux.org.uk; Fri, 21 Jul 2000 08:59:30 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 365CE1604C; Thu, 20 Jul 2000 20:16:00 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Thu, 20 Jul 2000 13:59:02 -0400 Received: by vger.rutgers.edu id ; Thu, 20 Jul 2000 13:58:55 -0400 Received: from crl.dec.com ([192.58.206.2]:1754 "EHLO crl.dec.com") by vger.rutgers.edu with ESMTP id ; Thu, 20 Jul 2000 13:58:40 -0400 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 OAA04983; Thu, 20 Jul 2000 14:14:20 -0400 (EDT) Received: by ims.crl.dec.com with Internet Mail Service (5.5.2650.21) id ; Thu, 20 Jul 2000 14:19:40 -0400 Message-ID: From: George France To: "'Meng, David'" , "'Nicolas Pitre'" , Sun-Gi Hong Cc: linux-arm@vger.rutgers.edu Subject: RE: [Q] Kernel Compilation Error (2.4.0.test2 version) Date: Thu, 20 Jul 2000 14:14:19 -0400 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@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Hello David; I am using the Carleton University telnet-0.10.29. You can find a copy at: ftp://ftp.handhelds.org/pub/linux/arm/carleton-winder-rpms --George George France, france@crl.dec.com Cambridge Research Laboratory, Compaq Computer Corporation One Cambridgecenter MS: CRL Cambridge, MA 02142 USA -----Original Message----- From: Meng, David [mailto:david.meng@intel.com] Sent: Thursday, July 20, 2000 12:00 PM To: 'Nicolas Pitre'; Sun-Gi Hong Cc: linux-arm@vger.rutgers.edu Subject: RE: [Q] Kernel Compilation Error (2.4.0.test2 version) Hi Nicolas: Would please let me know what package you used to build telnet utils in you ramdisk. I downloaded the telnet-0.10-29.src.rpm and tried to compile it use netwinder machine but go a lot of compiler errors. I would like to know which version of the telnet can be compiled and where to find the package. Regards. David unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Fri Jul 21 14:42:29 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13Fd4P-0007hi-00 for linux-arm-archive@lists.arm.linux.org.uk; Fri, 21 Jul 2000 14:42:29 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 1C17016AC9; Fri, 21 Jul 2000 10:38:07 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Fri, 21 Jul 2000 04:21:00 -0400 Received: by vger.rutgers.edu id ; Fri, 21 Jul 2000 04:20:29 -0400 Received: from rmx460-mta.mail.com ([165.251.48.47]:47278 "EHLO rmx460-mta.mail.com") by vger.rutgers.edu with ESMTP id ; Fri, 21 Jul 2000 04:19:07 -0400 Received: from web312-mc.mail.com (web312-mc.mail.com [165.251.48.170]) by rmx460-mta.mail.com (8.9.3/8.9.3) with SMTP id EAA28796; Fri, 21 Jul 2000 04:35:19 -0400 (EDT) Message-ID: <381754366.964168517236.JavaMail.root@web312-mc.mail.com> Date: Fri, 21 Jul 2000 04:35:16 -0400 (EDT) From: Michael Slater To: Hugues Belanger Subject: Re: [Help with toolchain] Cc: linux-arm@vger.rutgers.edu Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: mail.com X-Originating-IP: 32.97.110.70 Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Hi Hugues, Here are the steps ; Libtermcap : 1) mkdir tmp 2) do rpm2cpio filename | ( cd tmp && cpio -id) filename - downloaded libterm rpm file. 3)cd tmp. There will ba tar.gz file and some patches . extract tar ball and apply all the patches to it. now change the Makefile .. CC = arm-linux-gcc AR = arm-linux-ar make . You will get the .so file for libterm compiled for ARM.Just include this in your lib directory for ARM. Ncurses ; For ncurses follow the above stuff but you have to do the patch*.sh in the extracted ncurses directory which patches all the files . later apply the all the patches present. Then do ./configure --with-shared for enabling shared lib support.creates libncurses.so else it will create libcurses.a Then change the Makefile and replace all gcc,ld,ar with your arm-linux equivalents...also select the directory in which you want to install....That is the prefix in the Makefile . Default is set to usr....... Meaning your library will be installed in usr/lib...... Try this and let me know how you fare bye Anand ------Original Message------ From: Hugues Belanger To: anand kumar Sent: July 17, 2000 1:24:21 PM GMT Subject: Re: [Help with toolchain] Hi Anand I've downloaded the SRPMS already, but could you do me a favor and describe the high level steps required to do this. I.e. 1- Install the RPM 2- uncompress the source 3- ./configure --target=arm-linux --prefix=/skiff/local/ 4- make 5- ?? Do I copy the include from the source to the toolchain include dir ? 6- Any other steps ? Thanks anand kumar wrote: > You have to get the sources/binaries(ARM) from netwinder.org/allrpms.htm > and include it. > Note:ARM Binaries may not be compatible for your needs.I suggest you get the > sources and cross-compile it yourself using the toolchain. > > cheers > anand > > Hugues Belanger wrote: > > > Hi All, > > > > Forgive my ignorance, but I need a little help to get me going on my > porting > > project.... > > > > I've down loaded the ARM toolchain from handhleds.org, patched configured > and > > compile a kernel, manage to get all the base libs stripped, compiled Busybox > and > > Tinylogin... but now "ae" is complaning the -ltermcap -lcurses are > missing... > > I'm assuming that I need to had these libs to my tool chain RIGHT ? > > > > and if so, how do I do that ? > > > > thanks > > > > Hugues Belanger > > unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu > ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ > ++ kernel-related discussions. ++ > > ____________________________________________________________________ > Get free email and a permanent address at http://www.netaddress.com/?N=1 > > unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu > ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ > ++ kernel-related discussions. ++ unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ ______________________________________________ FREE Personalized Email at Mail.com Sign up at http://www.mail.com/?sr=signup unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Sat Jul 22 01:27:46 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13Fn8s-0008I7-00 for linux-arm-archive@lists.arm.linux.org.uk; Sat, 22 Jul 2000 01:27:46 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id C928F16BE4; Fri, 21 Jul 2000 15:39:27 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Fri, 21 Jul 2000 08:57:21 -0400 Received: by vger.rutgers.edu id ; Fri, 21 Jul 2000 08:56:51 -0400 Received: from leonardo.telscom.ch ([193.247.121.34]:2652 "EHLO leonardo.telscom.ch") by vger.rutgers.edu with ESMTP id ; Fri, 21 Jul 2000 08:55:51 -0400 Received: from telscom.ch ([193.247.121.35]) by leonardo.telscom.ch (Post.Office MTA v3.1.2 release (PO205-101c) ID# 0-0U10L2S100) with ESMTP id AAA251 for ; Fri, 21 Jul 2000 15:05:05 +0200 Message-ID: <39784E72.72626F58@telscom.ch> Date: Fri, 21 Jul 2000 15:21:55 +0200 From: Mathias Teikari Organization: Telscom AG X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.15 i686) X-Accept-Language: en MIME-Version: 1.0 To: linux-arm Subject: Re: BOOTP w. 2.4.0-test2 and EBSA-285 References: <200007201724.SAA29287@flint.arm.linux.org.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Below is the tcpdump output. 193.247.121.35 is the bootp server (0:d0:b7:3f:4a:90) and .36 is the client (0:90:27:8c:d8:6b) It does bother me somewhat that the server replies to the intended (but not yet configured) address of the client. I know this situation is discussed in the original bootp rfc (rfc951) but I don't know if any of the more recent extensions covers it? - Mathias 12:53:45.800521 0:90:27:8c:d8:6b ff:ff:ff:ff:ff:ff 0800 406: 0.0.0.0.68 > 255.255.255.255.67: xid:0x362989d0 secs:5 vend-rfc1048 SM:0.0.0.0 DG:0.0.0.0 HN:"^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@" T40:0,0,0,0,0,0,0,0 RP:"^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@" (DF) (ttl 64, id 0) 12:53:45.800663 0:d0:b7:3f:4a:90 0:90:27:8c:d8:6b 0800 406: 193.247.121.35.67 > 193.247.121.36.68: xid:0x362989d0 secs:5 Y:193.247.121.36 S:193.247.121.35 sname "neptune.telscom.ch" vend-rfc1048 SM:255.255.255.240 (ttl 64, id 61573) Russell King - ARM Linux Admin wrote: > > Could be one of many things. Can you give a "tcpdump -s 1540 -e -v" > dump of the packets please? > -- +---------------------------------------------------------+ .--. | Mathias Teikari mathias.teikari@telscom.ch | |o_o | | Ba. Sc. EE. Office Ph: +41 (0)31 376 2030 | |:_/ | | SW Development Engineer Mobile Ph: +41 (0)76 541 9449 | // \ \ | Telscom AG Sandrainstr. 17, CH-3007 Bern | (| | ) | | /'\_ _/`\ +---------------- http://www.telscom.ch ------------------+ \___)=(___/ unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Sat Jul 22 03:02:05 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13Foc9-0001Cy-00 for linux-arm-archive@lists.arm.linux.org.uk; Sat, 22 Jul 2000 03:02:05 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id A780D16C48; Fri, 21 Jul 2000 18:01:13 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Fri, 21 Jul 2000 11:43:05 -0400 Received: by vger.rutgers.edu id ; Fri, 21 Jul 2000 11:36:59 -0400 Received: from f319.law8.hotmail.com ([216.33.240.194]:4152 "HELO hotmail.com") by vger.rutgers.edu with SMTP id ; Fri, 21 Jul 2000 11:36:22 -0400 Received: (qmail 20649 invoked by uid 0); 21 Jul 2000 15:52:46 -0000 Message-ID: <20000721155246.20648.qmail@hotmail.com> Received: from 202.144.29.21 by www.hotmail.com with HTTP; Fri, 21 Jul 2000 08:52:46 PDT X-Originating-IP: [202.144.29.21] From: "Dinakar Guniguntala" To: linux-arm@vger.rutgers.edu Subject: Oops on a EP7211 Date: Fri, 21 Jul 2000 21:22:46 IST Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Hello, I am trying to get a 2.2.1 kernel with the latest patch from Ben Williamson cb26-benw3 (and other requisite patches) to boot through a serial port (COM1) on an EP7211 board when I get the following Oops I can see that we are in the do_rs7211_bh of the serial_7211 driver called from do_bottom_half. I have already made the changes to proc-arm6,7.S for TLB flushing of EP7211. Are there any other changes that need to be done Thanks for any inputs Dino PS: Sorry for the long post boot no options Linux version 2.2.1-rmk2-cb23 (root@orange) (gcc version egcs-2.91.66 19990325/philb (egcs-1.1.2 release)) #13 Fri Jul 21 18:43:57 IST 2000 initrd: start 0xc1713000, size 968537 -> start c0f13000, end 0xc0fff759 NetWinder Floating Point Emulator V0.94.1 (c) 1998 Corel Computer Corp. c0122f04-c1000000 memzero alloc_init_page [ mem c0126400, virt 00000000 -> phys c0125400 ]: D c0034000 := c00fd6c8 alloc_init_page [ mem c0126800, virt 00000000 -> phys c0125400 ]: P c0126400 setup_pagetables flush_tlb_all paging_init trap_init init_IRQ sched_init time_init (0) parse_options: parse_options (0xc014ebf0) rs_power: state = 1 console_init (67, 0xc014ebf0) init_modules (68) prof_shift (69) cpsr = 0x60000013 (70) SR1 0x00000904 MR1 0x00001200 SR2 0x00001004 MR2 0x00000000 sti (73, 0xc014ebf0) kmem_cache_init (0xc014ebf0) sti Calibrating delay loop... 68.61 BogoMIPS calibrate_delay Memory: 14096k/16M available (768k code, 224k reserved, 344k data, 4k init) POSIX conformance testing by UNIFIX &<6>Linux NET4.0 for Linux 2.2 Based upon Swansea University Computer Society NET3.039 NET4: Unix domain sockets 1.0 for Linux NET4.0. NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP Starting kswapd v 1.5 Power: PCMCIA 3300 mV ²rs_power: state = 1 rs_power: state = 1 alized: 16 RAM disks of 4096K size RAMDISK: Compressed image found at block 0 EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended VFS: Mounted root (ext2 filesystem). Freeing unused kernel memory: 4k init Enabling Transmits on Line 0 Line 0 opened Bad mode in prefetch abort handler detected: mode SVC_32 Internal error: Oops: 0 CPU: 0 pc : [<03a24008>] lr : [] sp : c015fe60 ip : c015fea8 fp : c015febc r10: c003820c r9 : c0108b60 r8 : c0108ce0 r7 : c0117a00 r6 : c0117a04 r5 : 00000001 r4 : c01078c8 r3 : 03a24009 r2 : 00000000 r1 : 00000001 r0 : 00000000 Flags: nzCv IRQs on FIQs on Mode SVC_32 Segment kernel INTSR1 0x00000b04 INTMR1 0x00003200 INTSR2 0x00001004 INTMR2 0x00002000 INTSR3 0x00002000 INTMR3 0x00002000 Control: 017D Table: C003401D DAC: 0000001D Process kflushd (pid: 2, stackpage=c015f000) Stack: c015fe80: c00c86fc 03a24008 c015fea0: 20000013 ffffffff 00000001 c0117a5c c015fed8 c015fec0 c004e95c c00c86d4 c015fec0: 00000000 00000000 0000000c c015ff08 c015fedc c003ac50 c004e8dc 00000180 c015fee0: c015ff0c 00003007 c015ff54 00000001 c00b8fbc 60000013 ffffffff c015ff9c c015ff00: c015ff0c c003a060 c003ab34 00000000 00000000 00000000 60000013 00000100 c015ff20: c0f11aa0 00000001 0000002a 00000002 c011cb10 c003820c c015ff9c c0111974 c015ff40: c015ff54 00000001 c00b8fbc 60000013 ffffffff deeb7397 c0f11ab8 c011cba0 c015ff60: 00000004 00000000 00000000 0000001e 00000001 00000001 c015ffd4 00000000 c015ff80: 00000001 00000400 00000001 00000100 c015ffc4 c015ffa0 c00b9170 c00b88f4 c015ffa0: c0f11d40 00000f90 00000002 00000010 c0100bac 00000008 c015fffc c015ffc8 c015ffc0: c00639b0 c00b8ff8 00000000 00000003 00000008 c0f11aa0 00000000 c00fd6c4 c015ffe0: c01226bc c00fd6c8 c00fd8ec 41807202 c0f0ffe4 c0160000 c0039bd8 c0063820 Backtrace: Function entered at [] from [] r5 = c0117a5c ^do_rs7211_bh ^do_bottom_half r4 = 00000001 Function entered at [] from [] r6 = 0000000c r5 = 00000000 r4 = 00000000 Function entered at [] from [] r9 = ffffffff r8 = 60000013 r7 = c00b8fbc r6 = 00000001 r5 = c015ff54 r4 = 00003007 Function entered at [] from [] r9 = 00000100 r8 = 00000001 r7 = 00000400 r6 = 00000001 r5 = 00000000 r4 = c015ffd4 Function entered at [] from [] r9 = 00000008 r8 = c0100bac r7 = 00000010 r6 = 00000002 r5 = 00000f90 r4 = c0f11d40 Function entered at [] from [] r9 = 41807202 r8 = c00fd8ec r7 = c00fd6c8 r6 = c01226bc r5 = c00fd6c4 r4 = 00000000 Function entered at [] from [<60000013>] Code: pc not in code space ________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Sat Jul 22 04:07:40 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13Fpdb-0002B0-00 for linux-arm-archive@lists.arm.linux.org.uk; Sat, 22 Jul 2000 04:07:40 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 680D115F59; Fri, 21 Jul 2000 18:46:16 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Fri, 21 Jul 2000 12:28:42 -0400 Received: by vger.rutgers.edu id ; Fri, 21 Jul 2000 12:28:30 -0400 Received: from thalia.fm.intel.com ([132.233.247.11]:1616 "EHLO thalia.fm.intel.com") by vger.rutgers.edu with ESMTP id ; Fri, 21 Jul 2000 12:27:43 -0400 Received: from SMTP (fmsmsxvs01-1.fm.intel.com [132.233.42.201]) by thalia.fm.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.30 2000/06/08 18:25:35 dmccart Exp $) with SMTP id QAA23516 for ; Fri, 21 Jul 2000 16:44:57 GMT Received: from fmsmsx17.intel.com ([132.233.48.17]) by 132.233.48.201 (Norton AntiVirus for Internet Email Gateways 1.0) ; Fri, 21 Jul 2000 16:44:01 0000 (GMT) Received: by fmsmsx17.fm.intel.com with Internet Mail Service (5.5.2650.21) id ; Fri, 21 Jul 2000 09:44:00 -0700 Message-ID: <4A043A1FE4B2D111AC3F00A0C96B5133055147AE@fmsmsx37.fm.intel.com> From: "Benavides, Edward A" To: linux-arm@vger.rutgers.edu Subject: ARM7 uclinux compilation Date: Fri, 21 Jul 2000 09:43:57 -0700 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@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu When I want to build the uclinux kernel for arm7 the make will not let me do zImage. The output says that there is no "vmlinuz" in the makefile. Is #make zImage the proper way to make the kernel? What about #make all? Where is the newly made kernel placed after the make is executed? Thanks Tony Benavides edward.a.benavides@intel.com unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Sat Jul 22 05:45:49 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13FrAa-0003ZE-00 for linux-arm-archive@lists.arm.linux.org.uk; Sat, 22 Jul 2000 05:45:48 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 81BBA163A9; Fri, 21 Jul 2000 22:22:05 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Fri, 21 Jul 2000 15:52:10 -0400 Received: by vger.rutgers.edu id ; Fri, 21 Jul 2000 15:50:45 -0400 Received: from thalia.fm.intel.com ([132.233.247.11]:2816 "EHLO thalia.fm.intel.com") by vger.rutgers.edu with ESMTP id ; Fri, 21 Jul 2000 15:49:18 -0400 Received: from SMTP (fmsmsxvs01-1.fm.intel.com [132.233.42.201]) by thalia.fm.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.30 2000/06/08 18:25:35 dmccart Exp $) with SMTP id UAA23586; Fri, 21 Jul 2000 20:06:36 GMT Received: from fmsmsx17.intel.com ([132.233.48.17]) by 132.233.48.201 (Norton AntiVirus for Internet Email Gateways 1.0) ; Fri, 21 Jul 2000 20:05:40 0000 (GMT) Received: by fmsmsx17.fm.intel.com with Internet Mail Service (5.5.2650.21) id ; Fri, 21 Jul 2000 13:05:37 -0700 Message-ID: From: "Chagas, Jason" To: linux@handhelds.org, linux-arm@vger.rutgers.edu, nanogui@linuxhacker.org, linuxce-devel@linuxce.org, sa1100-linux@pa.dec.com Cc: "Chagas, Jason" Subject: Easy installation kit for StrongARM* Linux cross development tool s AVAILABLE!! Date: Fri, 21 Jul 2000 13:05:24 -0700 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@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu An easy to install RPM based kit for StrongARM* Linux cross development tools is available for download (in both x386 binary and source code formats) at the following location: ftp://ftp.netwinder.org/users/c/chagas/arm-linux-cross This toolkit allows development of applications, device drivers and kernel development for StrongARM* Linux. Please refer to the README file for detailed installation instructions. Note, the kit also includes Linux v2.4 for the SA1110/SA1111 "Assabet" Development Board (http://developer.intel.com/design/strong/quicklist/eval-plat/). Although the binaries were compiled with RedHat v6.1 Linux, they should also run on other distributions of Linux. Regards, Jason *StrongARM(r) is a trademark of Advanced RISC Machines, Ltd. unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Sat Jul 22 19:37:57 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13G49t-0000Ij-00 for linux-arm-archive@lists.arm.linux.org.uk; Sat, 22 Jul 2000 19:37:57 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 183AC17830; Sat, 22 Jul 2000 09:11:09 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Sat, 22 Jul 2000 02:51:36 -0400 Received: by vger.rutgers.edu id ; Sat, 22 Jul 2000 02:49:31 -0400 Received: from violet.csa.iisc.ernet.in ([144.16.67.198]:1760 "EHLO violet.csa.iisc.ernet.in") by vger.rutgers.edu with ESMTP id ; Sat, 22 Jul 2000 02:48:14 -0400 Received: from localhost (alex@localhost) by violet.csa.iisc.ernet.in (8.9.3/8.9.3) with ESMTP id MAA06982; Sat, 22 Jul 2000 12:48:37 +0530 Date: Sat, 22 Jul 2000 12:48:37 +0530 (IST) From: Alex M Alex To: "Chagas, Jason" Cc: linux@handhelds.org, linux-arm@vger.rutgers.edu, nanogui@linuxhacker.org, linuxce-devel@linuxce.org, sa1100-linux@pa.dec.com Subject: Re: [linuxce-devel] Easy installation kit for StrongARM* Linux cross development tool s AVAILABLE!! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu HI, I am able to down load the images to SA1110 board but i am unable to get any display.But I was able to get even X working on Brutus board. regards alex On Fri, 21 Jul 2000, Chagas, Jason wrote: > An easy to install RPM based kit for StrongARM* Linux cross development > tools is available for download (in both x386 binary and source code > formats) at the following location: > > ftp://ftp.netwinder.org/users/c/chagas/arm-linux-cross > > This toolkit allows development of applications, device drivers and kernel > development for StrongARM* Linux. Please refer to the README file for > detailed installation instructions. Note, the kit also includes Linux v2.4 > for the SA1110/SA1111 "Assabet" Development Board > (http://developer.intel.com/design/strong/quicklist/eval-plat/). > > Although the binaries were compiled with RedHat v6.1 Linux, they should also > run on other distributions of Linux. > > Regards, > > Jason > > *StrongARM(r) is a trademark of Advanced RISC Machines, Ltd. > > unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Sat Jul 22 20:27:40 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13G4w0-00011Q-00 for linux-arm-archive@lists.arm.linux.org.uk; Sat, 22 Jul 2000 20:27:40 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 0F6D31644E; Sat, 22 Jul 2000 09:54:40 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Sat, 22 Jul 2000 03:35:20 -0400 Received: by vger.rutgers.edu id ; Sat, 22 Jul 2000 03:34:57 -0400 Received: from p58-robin-gui.tch.enablis.net ([194.168.180.118]:1172 "EHLO caramon.arm.linux.org.uk") by vger.rutgers.edu with ESMTP id ; Sat, 22 Jul 2000 03:34:15 -0400 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 IAA02066; Sat, 22 Jul 2000 08:50:49 +0100 Received: (from linux@localhost) by flint.arm.linux.org.uk (8.9.3/8.9.3) id IAA01738; Sat, 22 Jul 2000 08:49:26 +0100 From: Russell King - ARM Linux Admin Message-Id: <200007220749.IAA01738@flint.arm.linux.org.uk> Subject: Re: Oops on a EP7211 To: dinakar_g@hotmail.com (Dinakar Guniguntala) Date: Sat, 22 Jul 2000 08:49:26 +0100 (BST) Cc: linux-arm@vger.rutgers.edu In-Reply-To: <20000721155246.20648.qmail@hotmail.com> from "Dinakar Guniguntala" at Jul 21, 2000 09:22:46 PM X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Dinakar Guniguntala writes: > I am trying to get a 2.2.1 kernel with the latest patch from About 18 months of work has happened since this kernel was released. It is known to be buggy, and by this time I guess that very few people can remember what the problems were. > I can see that we are in the do_rs7211_bh of the serial_7211 > driver called from do_bottom_half. I have already made the changes > to proc-arm6,7.S for TLB flushing of EP7211. Are there any other > changes that need to be done Looks like its jumping off to somewhere silly 0x38 bytes into do_rs7211_bh. Apart from that, I can't comment what the problem may be. You'll have to look at the assembly code of that function to diagnose where its supposed to be jumping to. _____ |_____| ------------------------------------------------- ---+---+- | | Russell King linux@arm.linux.org.uk --- --- | | | | http://www.arm.linux.org.uk/ / / | | +-+-+ --- -+- / | THE developer of ARM Linux |+| /|\ / | | | --- | +-+-+ ------------------------------------------------- /\\\ | unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Sat Jul 22 20:41:04 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13G58y-0001Cc-00 for linux-arm-archive@lists.arm.linux.org.uk; Sat, 22 Jul 2000 20:41:04 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 2943717862; Sat, 22 Jul 2000 10:08:10 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Sat, 22 Jul 2000 03:49:01 -0400 Received: by vger.rutgers.edu id ; Sat, 22 Jul 2000 03:47:59 -0400 Received: from [202.141.26.181] ([202.141.26.181]:1335 "EHLO ee.iitm.ernet.in") by vger.rutgers.edu with ESMTP id ; Sat, 22 Jul 2000 03:47:29 -0400 Received: from space.ee.iitm.ernet.in (IDENT:root@space.ee.iitm.ernet.in [144.16.251.210]) by ee.iitm.ernet.in (8.9.3/8.9.3) with ESMTP id NAA02378; Sat, 22 Jul 2000 13:38:43 +0530 From: mali@space.ee.iitm.ernet.in Received: from localhost (mali@localhost) by space.ee.iitm.ernet.in (8.9.3/8.9.3) with ESMTP id WAA00581; Fri, 21 Jul 2000 22:18:57 +0530 Date: Fri, 21 Jul 2000 22:18:57 +0530 (IST) To: linux-arm@vger.rutgers.edu Cc: linux@handhelds.org, nanogui@linuxhacker.org, linuxce-devel@linuxce.org Subject: HOW TO WTRITE HARDWARE ADDR.. for ehternet chip In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu hello, Can anybody help me how to write the hard ware address for a CS8900 cirrus ethernet chip in the serial eeprom in cirrus evaluation board... Actually I tried with the one loader.tar file where i can get some more details? thank u. -mali unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Sun Jul 23 07:41:55 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13GFSV-0002Wp-00 for linux-arm-archive@lists.arm.linux.org.uk; Sun, 23 Jul 2000 07:41:55 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 6805B16764; Sat, 22 Jul 2000 22:18:19 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Sat, 22 Jul 2000 16:00:27 -0400 Received: by vger.rutgers.edu id ; Sat, 22 Jul 2000 16:00:11 -0400 Received: from host62-7-31-179.btinternet.com ([62.7.31.179]:62502 "EHLO tardis.home.dave") by vger.rutgers.edu with ESMTP id ; Sat, 22 Jul 2000 15:59:58 -0400 Received: from localhost (localhost [127.0.0.1]) by tardis.home.dave (8.9.3/8.8.7) with ESMTP id VAA23229 for ; Sat, 22 Jul 2000 21:10:56 +0100 Date: Sat, 22 Jul 2000 21:10:56 +0100 (BST) From: Dave Gilbert X-Sender: gilbertd@tardis.home.dave To: linux-arm@vger.rutgers.edu Subject: >>cheap<< ARM cards ??? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Hi, I'm after a >>cheap<< ARM card which can drive a 640x480 colour (3 bit per R/G/B) panel. Can I please reemphasize the word >>CHEAP<< - this is just for myself for messing about with, I'm not going to make any money from it. (The AEB doesn't look like it has quite enough umph to drive a display of that res.) Recommendations (and costs?) ? Dave -- ---------------- Have a happy GNU millennium! ---------------------- / Dr. David Alan Gilbert | Running GNU/Linux on | Happy \ \ gro.gilbert @ treblig.org | Alpha, x86, ARM and SPARC | In Hex / ____________________________|___ http://www.treblig.org |________/ unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Sun Jul 23 12:23:20 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13GJqq-0006aH-00 for linux-arm-archive@lists.arm.linux.org.uk; Sun, 23 Jul 2000 12:23:20 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 7D2F516CFC; Fri, 21 Jul 2000 20:03:46 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Fri, 21 Jul 2000 13:45:55 -0400 Received: by vger.rutgers.edu id ; Fri, 21 Jul 2000 13:44:27 -0400 Received: from [12.38.17.9] ([12.38.17.9]:1619 "EHLO mail.aeptec.com") by vger.rutgers.edu with ESMTP id ; Fri, 21 Jul 2000 13:43:44 -0400 Received: by MAIL with Internet Mail Service (5.5.2650.21) id ; Fri, 21 Jul 2000 13:50:50 -0400 Message-ID: <32CC5B62AF0BD2119E4C00A0C9663E221F3BE4@MAIL> From: "Sun, Lei" To: "'linux-arm@vger.rutgers.edu'" Subject: cross-compile ! Date: Fri, 21 Jul 2000 13:50:50 -0400 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@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Hi: I was trying to corss-compile the telnet program downloaded from netwinder website, to arm-linux executable. But after I run make, it exist with the following error: arm-linux-gcc -s authenc.o commands.o main.o network.o ring.o sys_bsd.o telnet.o terminal.o tn3270.o utilities.o genget.o -lncurses -o telnet /home/arm_backup/arm/arm-linux/bin/ld: cannot find -lncurses collect2: ld returned 1 exit status make[1]: *** [telnet] Error 1 It appears that couldn't find some library. How do I solve this problem? Thank you! Lei Sun unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Sun Jul 23 12:32:19 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13GJzX-0006hy-00 for linux-arm-archive@lists.arm.linux.org.uk; Sun, 23 Jul 2000 12:32:19 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 7DF0517549; Fri, 21 Jul 2000 20:49:13 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Fri, 21 Jul 2000 14:31:12 -0400 Received: by vger.rutgers.edu id ; Fri, 21 Jul 2000 14:29:39 -0400 Received: from thalia.fm.intel.com ([132.233.247.11]:3367 "EHLO thalia.fm.intel.com") by vger.rutgers.edu with ESMTP id ; Fri, 21 Jul 2000 14:27:09 -0400 Received: from SMTP (fmsmsxvs01-1.fm.intel.com [132.233.42.201]) by thalia.fm.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.30 2000/06/08 18:25:35 dmccart Exp $) with SMTP id SAA23457 for ; Fri, 21 Jul 2000 18:44:11 GMT Received: from fmsmsx27.FM.INTEL.COM ([132.233.48.27]) by 132.233.48.201 (Norton AntiVirus for Internet Email Gateways 1.0) ; Fri, 21 Jul 2000 18:43:15 0000 (GMT) Received: by fmsmsx27.fm.intel.com with Internet Mail Service (5.5.2650.21) id ; Fri, 21 Jul 2000 11:43:13 -0700 Message-ID: <4A043A1FE4B2D111AC3F00A0C96B5133055147B0@fmsmsx37.fm.intel.com> From: "Benavides, Edward A" To: "'linux-arm@vger.rutgers.edu'" Subject: ARM7TDMI Date: Fri, 21 Jul 2000 11:43:11 -0700 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@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu The uclinux kernel is now made via the aplionet site rpms and pre-configured code. I looked in the linux/arch/armnommu/boot directory and there was not a familiar file to my eyes. Where is the made kernel placed? There is a folder in /../../armnommu/boot that is called compressed. The file mentions vmlinux, what is this used for? I am using, obviously, an ARM7 platform. What is the best bootloader to use for this platform and how can I get this unfound kernel image loaded. thanks for the help, unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Sun Jul 23 14:35:10 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13GLuQ-0008Ou-00 for linux-arm-archive@lists.arm.linux.org.uk; Sun, 23 Jul 2000 14:35:10 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 9201316CFD; Fri, 21 Jul 2000 20:04:14 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Fri, 21 Jul 2000 13:46:47 -0400 Received: by vger.rutgers.edu id ; Fri, 21 Jul 2000 13:46:26 -0400 Received: from smtp2.fr.uu.net ([194.98.0.8]:42279 "HELO mail.fr.uu.net") by vger.rutgers.edu with SMTP id ; Fri, 21 Jul 2000 13:45:59 -0400 Received: from CarlCox.iway.fr (carlcox.iway.fr [194.98.0.128]) by mail.fr.uu.net (Postfix) with ESMTP id ECCB931F14; Fri, 21 Jul 2000 20:02:00 +0200 (MET DST) Received: from vad ([194.98.253.47]) by CarlCox.iway.fr (8.9.3/8.8.7) with SMTP id UAA13323835; Fri, 21 Jul 2000 20:02:11 +0200 (METDST) From: "Vadim Lebedev" To: "Benavides, Edward A" , Subject: RE: ARM7 uclinux compilation Date: Fri, 21 Jul 2000 20:02:15 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal In-Reply-To: <4A043A1FE4B2D111AC3F00A0C96B5133055147AE@fmsmsx37.fm.intel.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Edward, Did you download the uclinux from http://aplionet.aplio.fr/uclinux if not do so, and read the FAQ there Vadim |-----Original Message----- |From: owner-linux-arm@vger.rutgers.edu |[mailto:owner-linux-arm@vger.rutgers.edu]On Behalf Of Benavides, Edward |A |Sent: vendredi 21 juillet 2000 18:44 |To: linux-arm@vger.rutgers.edu |Subject: ARM7 uclinux compilation | | | |When I want to build the uclinux kernel for arm7 |the make will not let me do zImage. The output says that there is no |"vmlinuz" in the makefile. | |Is #make zImage the proper way to make the kernel? |What about #make all? |Where is the newly made kernel placed after the make is executed? | |Thanks | |Tony Benavides | |edward.a.benavides@intel.com | | |unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu |++ Please use linux-arm-kernel@lists.arm.linux.org.uk for | ++ |++ kernel-related discussions. | ++ | unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 24 04:00:15 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13GYTX-0002z7-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 24 Jul 2000 04:00:15 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 20AF915E08; Mon, 24 Jul 2000 04:55:32 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Sun, 23 Jul 2000 22:36:47 -0400 Received: by vger.rutgers.edu id ; Sun, 23 Jul 2000 22:36:23 -0400 Received: from smtppop2pub.gte.net ([206.46.170.21]:26587 "EHLO smtppop2.gte.net") by vger.rutgers.edu with ESMTP id ; Sun, 23 Jul 2000 22:36:00 -0400 Received: from gte.net (1Cust145.tnt4.redmond.wa.da.uu.net [63.23.202.145]) by smtppop2.gte.net with ESMTP for ; id VAA1715474 Sun, 23 Jul 2000 21:50:18 -0500 (CDT) Message-ID: <397B49F2.7DDE244B@gte.net> Date: Sun, 23 Jul 2000 12:39:30 -0700 From: Mike Coburn X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.5-15 i586) X-Accept-Language: en MIME-Version: 1.0 To: linux-arm@vger.rutgers.edu Subject: Understanding Patchfile Names Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu In: ftp://ftp.arm.linux.org.uk/pub/armlinux/source/kernel-patches/v2.3/ I find files like: patch-2.3.48-rmk1.gz patch-2.3.48-rmk2.gz patch-2.3.99-pre3-rmk1.gz patch-2.3.99-pre3-rmk2.gz patch-2.3.99-pre3-rmk3.gz patch-2.3.99-pre8-rmk2.gz patch-2.3.99-pre8-rmk1.gz patch-2.3.99-pre9-rmk2.gz pre-patch-2.3.23-rmk1.gz pre-patch-2.3.49-rmk1.gz pre-patch-3.3.51-rmk1.gz So. What is the code? I found a README that said the "2.3.xx" was the actual kernel release and the "rmk"x was a date. But that does not look like a date to me. And I've not been able to find what the pre stuff means. Any hints will be appreciated. I'm still trying to get out of the starting gate on this and I am slowly finding enough stuff that fits together (i.e. gcc-2. whatever instead of egcs and the newer bin-utils and such). I will assume for now that I'll be messing with kernel 2.3 but maybe I should be doing 2.4. At this point it probably does not matter. But the arm patch stuff and all the different Brutus, SA1100,1110, 1111, and Assebet, and others are all pretty bewildering. I have a board with sa1110 wrote on it and a board with sa1111 wrote on it and a touch screen. I don't know whether that is a Brutus or a Howdy Doody. All I know is that I've been commanded to "put linux on it". And I truly believe that if I can figure out what the numbers and letters mean on the patch file names I will be able to "put linux on it". Making it actually _do_ something will probably be a lot tougher. But, then, I wasn't commissioned to do _that_. Plaese advise as to where to find the keys or just give me a hint of what the pre and the rnk stuff means. Thanx. -- Coburn --- unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 24 06:44:22 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13Gb2M-0007cs-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 24 Jul 2000 06:44:22 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id A7FA315EBE; Mon, 24 Jul 2000 07:31:12 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Mon, 24 Jul 2000 01:12:35 -0400 Received: by vger.rutgers.edu id ; Mon, 24 Jul 2000 01:11:52 -0400 Received: from SMTP2.ANDREW.CMU.EDU ([128.2.10.82]:37612 "EHLO smtp2.andrew.cmu.edu") by vger.rutgers.edu with ESMTP id ; Mon, 24 Jul 2000 01:11:29 -0400 Received: from cs.cmu.edu (NINESIXTEEN.REM.CMU.EDU [128.2.81.157]) by smtp2.andrew.cmu.edu (8.9.3/8.9.3) with ESMTP id BAA13372; Mon, 24 Jul 2000 01:28:47 -0400 (EDT) Message-ID: <397BD3C5.6ECBD719@cs.cmu.edu> Date: Mon, 24 Jul 2000 01:27:33 -0400 From: John G Dorsey Organization: Carnegie Mellon University X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i686) X-Accept-Language: en MIME-Version: 1.0 To: Mike Coburn Cc: linux-arm@vger.rutgers.edu Subject: Re: Understanding Patchfile Names References: <397B49F2.7DDE244B@gte.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Mike Coburn wrote: > So. What is the code? I found a README that said the > "2.3.xx" was the actual kernel release and the "rmk"x was a date. > But that does not look like a date to me. And I've not been able to > find what the pre stuff means. These are all patches to the Linux kernel source tree. Essentially, to get a kernel that will do something useful on your hardware (more on that later), you'll need to collect a recent tree and one or more of these files which update the tree. Here's a current version of the kernel: ftp://ftp.kernel.org/pub/linux/kernel/v2.4/linux-2.4.0-test4.tar.gz Ordinarily, you'd have to collect two or three patches from various places in order to bring this code up to speed, but this week, you're in luck. Just get: ftp://ftp.arm.linux.org.uk/pub/armlinux/people/nico/diff-2.4.0-test4-np1.gz Information on applying patches and compiling the kernel can be found elsewhere online, so I won't repeat it here. > But the arm patch stuff and all the different Brutus, SA1100,1110, 1111, > and > Assebet, and others are all pretty bewildering. I have a board with > sa1110 > wrote on it and a board with sa1111 wrote on it and a touch screen. I > don't > know whether that is a Brutus or a Howdy Doody. It sounds like you have an Assabet (the SA-1110 board) and a Neponset (the SA-1111 board). Take a look at: http://www.cs.cmu.edu/~wearable/software/assabet.html > Plaese advise as to where to find the keys or just give me a hint of > what the pre and the rnk stuff means. Up until recently, we were at a pre-release version of kernel 2.3.99. Linus went on vacation, but has released a "test" release of kernel 2.4.0, which isn't too terribly different from the "pre" kernels. The "RMK" refers, naturally, to THE developer of ARM Linux (Russell King). As patches are released to a given kernel tree, the resulting tree is identified by a version string that might include the name of the developer and a serial number, as in "2.3.48-rmk2" (Russell's second patch release for kernel 2.3.48). -jd unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 24 17:01:23 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13GkfT-0008Pb-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 24 Jul 2000 17:01:23 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 7A5B3161D3; Mon, 24 Jul 2000 17:51:03 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Mon, 24 Jul 2000 11:31:31 -0400 Received: by vger.rutgers.edu id ; Mon, 24 Jul 2000 11:30:11 -0400 Received: from sofia.magic.fr ([195.115.17.9]:60304 "EHLO sofia.magic.fr") by vger.rutgers.edu with ESMTP id ; Mon, 24 Jul 2000 11:29:04 -0400 Received: from mail.inventel.fr (gw.inventel.fr [195.115.113.35]) by sofia.magic.fr (8.9.0/8.9.0) with ESMTP id RAA01325 for ; Mon, 24 Jul 2000 17:46:38 +0200 (CEST) Received: from inventel.fr (193.54.84.50) by mail.inventel.fr (NPlex 1.3.171) for linux-arm@vger.rutgers.edu; 24 Jul 2000 17:46:28 +0200 Message-ID: <397C8255.94F3C78D@inventel.fr> Date: Mon, 24 Jul 2000 17:52:21 +0000 From: Xavier DEBREUIL X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.12-32 i686) X-Accept-Language: en MIME-Version: 1.0 To: linux-arm@vger.rutgers.edu Subject: toolchain Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu I currently use : binutils-2.9.5.0.27 : ok gcc-2.95.2 patched with gcc-2.95.2-diff-991022 : following www.inkvine.fluff.org/~chris/arm-tools.html steps [root@L_XDE build_gcc-2.95.2]# make [LANGUAGES="c"] ... make[1]: Leaving directory `/home/xde/arm_linux/build_gcc-2.95.2/gcc' Configuring in arm-linux/libiberty loading cache ./config.cache checking host system type... arm-unknown-linux-gnu checking build system type... i686-pc-linux-gnu checking for arm-linux-ar... arm-linux-ar checking for arm-linux-ranlib... arm-linux-ranlib checking for gcc... /home/xde/arm_linux/build_gcc-2.95.2/gcc/xgcc -B/home/xde/arm_linux/build_gcc-2.95.2/gcc/ -B/usr/local/arm-linux/bin/ checking whether we are using GNU C... yes checking whether /home/xde/arm_linux/build_gcc-2.95.2/gcc/xgcc -B/home/xde/arm_linux/build_gcc-2.95.2/gcc/ -B/usr/local/arm-linux/bin/ accepts -g... yes checking for POSIXized ISC... no checking for a BSD compatible install... /usr/bin/install -c xhost-mkfrag is unchanged checking how to run the C preprocessor... /lib/cpp checking for sys/file.h... yes checking for sys/param.h... yes checking for stdlib.h... yes checking for string.h... yes checking for unistd.h... yes share/i18n/charmaps/NS_4551-1ñ9.././scripts/mkinstalldirs /usr/local/share/i18n/charmaps/aV/usr/bin/install -c -m 644 charmaps/NS_4551-2 /usr/local/share/i18n/charmaps/NS_4551-2ychecking for sys/time.h... yes checking for sys/resource.h... yes checking for sys/wait.h that is POSIX.1 compatible... no !!! checking whether the C compiler (/home/xde/arm_linux/build_gcc-2.95.2/gcc/xgcc -B/home/xde/arm_linux/build_gcc-2.95.2/gcc/ -B/usr/local/arm-linux/bin/ -g -O2 ) works... no configure: error: installation or configuration problem: C compiler cannot create executables. !!! make[1]: Entering directory `/home/xde/arm_linux/build_gcc-2.95.2/arm-linux/libio' test x"no" != xyes ||\ /home/xde/arm_linux/build_gcc-2.95.2/gcc/xgcc -B/home/xde/arm_linux/build_gcc-2.95.2/gcc/ -B/usr/local/arm-linux/bin/ -c -g -O2 -I. -I../../../gcc-2.95.2/libio -D_IO_MTSAFE_IO ../../../gcc-2.95.2/libio/iogetline.c -o pic/iogetline.o /home/xde/arm_linux/build_gcc-2.95.2/gcc/xgcc -B/home/xde/arm_linux/build_gcc-2.95.2/gcc/ -B/usr/local/arm-linux/bin/ -c -g -O2 -I. -I../../../gcc-2.95.2/libio -D_IO_MTSAFE_IO ../../../gcc-2.95.2/libio/iogetline.c In file included from ../../../gcc-2.95.2/libio/iogetline.c:26: ../../../gcc-2.95.2/libio/libioP.h:30: errno.h: Aucun fichier ou répertoire de ce type In file included from ../../../gcc-2.95.2/libio/iolibio.h:1, from ../../../gcc-2.95.2/libio/libioP.h:47, from ../../../gcc-2.95.2/libio/iogetline.c:26: ../../../gcc-2.95.2/libio/libio.h:30: _G_config.h: Aucun fichier ou répertoire de ce type ../../../gcc-2.95.2/libio/iogetline.c:27: string.h: Aucun fichier ou répertoire de ce type make[1]: *** [iogetline.o] Error 1 make[1]: Leaving directory `/home/xde/arm_linux/build_gcc-2.95.2/arm-linux/libio' make: *** [all-target-libio] Error 2 any help is welcomed glibc-2.1.3 glibc-linuxthreads-2.1.2 glibc-crypt-2.1 although the compiler seems not to be able to produce executables, the whole glibc has been compiled properly except a few lines in sysdeps/unix/sysv/linux/arm/ioperm.c (lines 103-104 and 107-112) I was compelled to comment out. Is there anything to bypass the compiler problem ? Where should I define the following variables CTL_BUS, BUS_ISA, BUS_ISA_PORT_BASE, BUS_ISA_PORT_SHIFT, so that ioperm.c could compile ? Thank you. Xavier.  unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 24 18:16:55 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13GlqZ-00014I-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 24 Jul 2000 18:16:55 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 9917316264; Mon, 24 Jul 2000 19:12:12 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Mon, 24 Jul 2000 12:51:07 -0400 Received: by vger.rutgers.edu id ; Mon, 24 Jul 2000 12:51:03 -0400 Received: from [12.38.17.9] ([12.38.17.9]:3206 "EHLO mail.aeptec.com") by vger.rutgers.edu with ESMTP id ; Mon, 24 Jul 2000 12:50:14 -0400 Received: by MAIL with Internet Mail Service (5.5.2650.21) id ; Mon, 24 Jul 2000 12:55:47 -0400 Message-ID: <32CC5B62AF0BD2119E4C00A0C9663E221F3BEC@MAIL> From: "Sun, Lei" To: "'linux-arm@vger.rutgers.edu'" Subject: kernel version! Date: Mon, 24 Jul 2000 12:55:47 -0400 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@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Hi all: I have been trying to port the linux to SA1110 for a month, I can make the linux-2.4.0 (test2 or test4) runing on it. But the network has some problem which is very hard to find out the reason. so I am thinking to change to older kernel. Does anybody know if the kernel 2.2.14 with Nico's patch could run on SA1110 ? I ever tried it before but I didn't make it. And if I build 2.2.14 kernel, How can I make the compact flash ethernet (socket comm. LP CF) working? I know I need install the pcmica card service package, but where can I get that specific driver for LP CF card? Thank you! Lei Sun unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 24 18:43:29 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13GmGG-0001TB-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 24 Jul 2000 18:43:28 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 644B515F07; Mon, 24 Jul 2000 19:36:24 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Mon, 24 Jul 2000 13:15:51 -0400 Received: by vger.rutgers.edu id ; Mon, 24 Jul 2000 13:15:29 -0400 Received: from POST.ICES.CMU.EDU ([128.2.205.86]:35852 "HELO post.ices.cmu.edu") by vger.rutgers.edu with SMTP id ; Mon, 24 Jul 2000 13:14:52 -0400 Received: from VANCOUVER.ICES.CMU.EDU by post.ices.cmu.edu id aa05603; 24 Jul 2000 13:32 EDT Message-ID: <397C2A13.CE6F4AD6@cs.cmu.edu> Date: Mon, 24 Jul 2000 07:35:47 -0400 From: John G Dorsey Organization: Carnegie Mellon University X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.10 i686) X-Accept-Language: en MIME-Version: 1.0 To: "Sun, Lei" Cc: "'linux-arm@vger.rutgers.edu'" Subject: Re: kernel version! References: <32CC5B62AF0BD2119E4C00A0C9663E221F3BEC@MAIL> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu "Sun, Lei" wrote: > Does anybody know if the kernel 2.2.14 with Nico's patch could run on > SA1110 ? I ever tried it before but I didn't make it. And if I build 2.2.14 > kernel, How can I make the compact flash ethernet (socket comm. LP CF) > working? I know I need install the pcmica card service package, but where > can I get that specific driver for LP CF card? As far as I know, pcnet_cs with that device has not been tried on a kernel earlier than 2.3.99. This probably doesn't matter, however. You could go and get a recent PCMCIA Card Services and run it against a 2.2 kernel, which in all likelihood would not behave differently from what you're now seeing on Neponset. I think that something is flaky with either the SA-1111 or the Nep PCMCIA implementation. That card works just fine on Assabet, but only comes close to working on Neponset if you play tricks with the device I/O. For example, there is a known corruption issue with the last octet of an odd-length frame transfer from the card, which simply does not happen on other systems. I'm sorry I can't offer you a more useful answer at the moment. =( -jd unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 24 18:49:36 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13GmMC-0001YN-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 24 Jul 2000 18:49:36 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 497A9160CD; Mon, 24 Jul 2000 19:43:34 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Mon, 24 Jul 2000 13:25:22 -0400 Received: by vger.rutgers.edu id ; Mon, 24 Jul 2000 13:25:13 -0400 Received: from [205.250.170.220] ([205.250.170.220]:4876 "EHLO xanadu.vipswitch.com") by vger.rutgers.edu with ESMTP id ; Mon, 24 Jul 2000 13:24:53 -0400 Date: Mon, 24 Jul 2000 13:39:08 -0400 (EDT) From: Nicolas Pitre To: "Sun, Lei" Cc: "'linux-arm@vger.rutgers.edu'" Subject: Re: kernel version! In-Reply-To: <32CC5B62AF0BD2119E4C00A0C9663E221F3BEC@MAIL> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu On Mon, 24 Jul 2000, Sun, Lei wrote: > Hi all: > I have been trying to port the linux to SA1110 for a month, I can make > the linux-2.4.0 (test2 or test4) runing on it. But the network has some > problem which is very hard to find out the reason. so I am thinking to > change to older kernel. > Does anybody know if the kernel 2.2.14 with Nico's patch could run on > SA1110 ? I ever tried it before but I didn't make it. And if I build 2.2.14 > kernel, How can I make the compact flash ethernet (socket comm. LP CF) > working? I know I need install the pcmica card service package, but where > can I get that specific driver for LP CF card? > Thank you! You'll have to port everything yourself i.e. the kernel support for Assabet, the PCMCIA subsystem, the ethernet driver, etc. And you'll be alone in your corner because 2.2.x kernels are no longer maintained as SA11x0 support is concerned. All this without any waranty that you won't have the same telnet problem at the end. Believe me you're way better to investigate yourself a little more on the 2.4.x kernels. Nicolas unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 24 18:55:22 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13GmRm-0001dd-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 24 Jul 2000 18:55:22 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id E9DEE16280; Mon, 24 Jul 2000 19:49:06 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Mon, 24 Jul 2000 13:30:52 -0400 Received: by vger.rutgers.edu id ; Mon, 24 Jul 2000 13:30:41 -0400 Received: from [205.250.170.220] ([205.250.170.220]:4888 "EHLO xanadu.vipswitch.com") by vger.rutgers.edu with ESMTP id ; Mon, 24 Jul 2000 13:30:02 -0400 Date: Mon, 24 Jul 2000 13:44:52 -0400 (EDT) From: Nicolas Pitre To: John G Dorsey Cc: "Sun, Lei" , "'linux-arm@vger.rutgers.edu'" Subject: Re: kernel version! In-Reply-To: <397C2A13.CE6F4AD6@cs.cmu.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu On Mon, 24 Jul 2000, John G Dorsey wrote: > As far as I know, pcnet_cs with that device has not been tried on a kernel > earlier than 2.3.99. This probably doesn't matter, however. You could go and get > a recent PCMCIA Card Services and run it against a 2.2 kernel, which in all > likelihood would not behave differently from what you're now seeing on Neponset. > > I think that something is flaky with either the SA-1111 or the Nep > PCMCIA implementation. That card works just fine on Assabet, but only comes > close to working on Neponset if you play tricks with the device I/O. It doesn't work perfectly on stand-alone Assabet either. Just try to telnet into your Assabet and logout a couple of times. The sixth telnet or so just hang because tcpd on the Assabet goes nuts and stalls for still unknown reasons... and I don't have the time to trace it down at the moment. Nicolas unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 24 19:16:21 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13Gmm5-0001y3-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 24 Jul 2000 19:16:21 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 994931629B; Mon, 24 Jul 2000 20:09:17 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Mon, 24 Jul 2000 13:50:55 -0400 Received: by vger.rutgers.edu id ; Mon, 24 Jul 2000 13:50:12 -0400 Received: from [12.38.17.9] ([12.38.17.9]:3994 "EHLO mail.aeptec.com") by vger.rutgers.edu with ESMTP id ; Mon, 24 Jul 2000 13:49:27 -0400 Received: by MAIL with Internet Mail Service (5.5.2650.21) id ; Mon, 24 Jul 2000 13:57:06 -0400 Message-ID: <32CC5B62AF0BD2119E4C00A0C9663E221F3BED@MAIL> From: "Sun, Lei" To: "'linux-arm@vger.rutgers.edu'" Subject: cross-compile! Date: Mon, 24 Jul 2000 13:57:05 -0400 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@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Hi: Sorry for so many questions. I have a generic questions about cross-compile source package for arm-linux. I have tool chain, compiler, glibc installed on my host machine (redhat linux 6.2) in /home/arm/ directory. some packages can be compiled by just specifying the compiler to be arm-linux-gcc, but some couldn't. My questions are: 1. sometimes, the make try to execute program generated during compiling, since it's cross-compile, it couldn't execute the binary, so it existed. how to solve this problem ( the make -i option could work, but sometimes the package need some files generated by the compiled binary program) ? 2. sometimes, it's couldn't find some Lib or header file, what is the search creteria of the lib and header for the cross-compilers? due to the resources limites, I can't install compiler on my target. In that case, things could be trival. Thank you! Any hint or suggestion is appreciated!! Lei Sun unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 24 19:22:10 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13Gmrh-00022h-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 24 Jul 2000 19:22:09 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 2782116100; Mon, 24 Jul 2000 20:10:19 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Mon, 24 Jul 2000 13:51:55 -0400 Received: by vger.rutgers.edu id ; Mon, 24 Jul 2000 13:51:49 -0400 Received: from [12.38.17.9] ([12.38.17.9]:4039 "EHLO mail.aeptec.com") by vger.rutgers.edu with ESMTP id ; Mon, 24 Jul 2000 13:51:38 -0400 Received: by MAIL with Internet Mail Service (5.5.2650.21) id ; Mon, 24 Jul 2000 13:59:55 -0400 Message-ID: <32CC5B62AF0BD2119E4C00A0C9663E221F3BEE@MAIL> From: "Sun, Lei" To: 'Nicolas Pitre' , 'Jeff Sutherland' Cc: "'linux-arm@vger.rutgers.edu'" Subject: Re: Kernel version! Date: Mon, 24 Jul 2000 13:59:55 -0400 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@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Hi: OK, I will stay in the latest kernel version :-) and try to play it by myself about the network problem. ( I wrote a socket program, let it constantly send a short message to other machine from Assabet, and the first 5 messages are correct, after that the message coming in become garbage code).After network error occured, I can't even reboot the system( shutdown or reboot doesn't work, have to push reset key). Jeff, see Nico's message, it doesn't work well on stand alone Assabet either, he reproduced the same telnet error as I met. THank you! lei unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 24 19:26:32 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13Gmvw-00026h-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 24 Jul 2000 19:26:32 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 563FE162A8; Mon, 24 Jul 2000 20:19:26 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Mon, 24 Jul 2000 13:59:22 -0400 Received: by vger.rutgers.edu id ; Mon, 24 Jul 2000 13:58:19 -0400 Received: from ice.fiftyone.com ([208.225.80.11]:1668 "EHLO ice.ar51.net") by vger.rutgers.edu with ESMTP id ; Mon, 24 Jul 2000 13:57:44 -0400 Received: from server01.asi (akron-80-154.ar51.net [208.225.80.154]) by ice.ar51.net (8.9.3/8.8.7) with ESMTP id OAA27092; Mon, 24 Jul 2000 14:14:15 -0400 Received: by SERVER01 with Internet Mail Service (5.5.2448.0) id <3YXN8C7N>; Mon, 24 Jul 2000 14:15:10 -0400 Message-ID: From: Jeff Sutherland To: "'Nicolas Pitre'" , "'John G Dorsey'" Cc: "'Sun, Lei'" , "'linux-arm@vger.rutgers.edu'" Subject: RE: kernel version! Date: Mon, 24 Jul 2000 14:15:07 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu > On Mon, 24 Jul 2000, John G Dorsey wrote: > > > As far as I know, pcnet_cs with that device has not been > tried on a kernel > > earlier than 2.3.99. This probably doesn't matter, however. > You could go and get > > a recent PCMCIA Card Services and run it against a 2.2 > kernel, which in all > > likelihood would not behave differently from what you're > now seeing on Neponset. > > > > I think that something is flaky with either the SA-1111 or the Nep > > PCMCIA implementation. That card works just fine on > Assabet, but only comes > > close to working on Neponset if you play tricks with the device I/O. Trust me, it's the design of the Nep >:( > It doesn't work perfectly on stand-alone Assabet either. Huh? News to me. Mine works great, root filesystem NFS mounted, streaming MP3's down the Ethernet all day long. Better check you bootloader's memory settings. My old phase 1 Assabet is pretty sedate due to broken things (main memory clocks at 1/4 cpu due to broken PLD for LCD, CPU fixed to 147MHz to make the 1394 codec work right, and so forth ad nausium...) so I have a bit of timing margin. You guys cranking up your processor clocks may see flaky things happen, but that's life in the fast lane :D > Just try to telnet into your Assabet and logout a couple of > times. The > sixth telnet or so just hang because tcpd on the Assabet goes nuts and > stalls for still unknown reasons... and I don't have the > time to trace it > down at the moment. Don't bother, Nicolas, I think it's your hardware. I do this all day long, leaving the little guy up for days at a time. Now could someone clue me in as to what happened to the frame buffer driver on the Assabet? It was working fine back in the 2.3.99-pre-something days, but lately I've noticed that every other scan line is blank even though the screen geometry over all is correct (no, it's not hardware, the phase 4 Assabet does it, too). X and MicroWindows don't find the touch screen. "Error 2 opening touch panel; Cannot initialise mouse" is what the nano-X driver says. The major number is assigned dynamically. I stuck a device in /dev anyway and pointed "mouse" to it, still no joy. This one's a little light on documentation. Hints, anyone, please? Thanks! //Jeff unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 24 19:33:57 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13Gn37-0002D2-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 24 Jul 2000 19:33:57 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 4FDB3162B5; Mon, 24 Jul 2000 20:28:55 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Mon, 24 Jul 2000 14:09:23 -0400 Received: by vger.rutgers.edu id ; Mon, 24 Jul 2000 14:09:09 -0400 Received: from ice.fiftyone.com ([208.225.80.11]:1693 "EHLO ice.ar51.net") by vger.rutgers.edu with ESMTP id ; Mon, 24 Jul 2000 14:07:29 -0400 Received: from server01.asi (akron-80-154.ar51.net [208.225.80.154]) by ice.ar51.net (8.9.3/8.8.7) with ESMTP id OAA27807; Mon, 24 Jul 2000 14:25:07 -0400 Received: by SERVER01 with Internet Mail Service (5.5.2448.0) id <3YXN8C73>; Mon, 24 Jul 2000 14:26:56 -0400 Message-ID: From: Jeff Sutherland To: "'Nicolas Pitre'" , "'John G Dorsey'" Cc: "'linux-arm@vger.rutgers.edu'" Subject: RE: kernel version! Date: Mon, 24 Jul 2000 14:26:51 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu > It doesn't work perfectly on stand-alone Assabet either. I failed to mention the kernel version in my earlier post, sorry. I'm using 2.4.0-test2-ac1-rmk2-np3 (which has no evident problem with telnet, ftp, or anything else). Is the flakyness you mentioned occurring in -test4-np1? I'm not there yet. Golly, I've been doing software too long! Imagine, me thinking there's a hardware problem! Sheesh! //Jeff unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 24 20:02:25 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13GnUe-0002dG-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 24 Jul 2000 20:02:25 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 95E0A162E5; Mon, 24 Jul 2000 20:48:34 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Mon, 24 Jul 2000 14:25:38 -0400 Received: by vger.rutgers.edu id ; Mon, 24 Jul 2000 14:23:57 -0400 Received: from p03-cordelia-gui.tch.enablis.net ([212.250.233.3]:1305 "EHLO caramon.arm.linux.org.uk") by vger.rutgers.edu with ESMTP id ; Mon, 24 Jul 2000 14:23:12 -0400 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 SAA04117; Mon, 24 Jul 2000 18:57:27 +0100 Received: (from linux@localhost) by flint.arm.linux.org.uk (8.9.3/8.9.3) id SAA03750; Mon, 24 Jul 2000 18:55:49 +0100 From: Russell King - ARM Linux Admin Message-Id: <200007241755.SAA03750@flint.arm.linux.org.uk> Subject: Re: Understanding Patchfile Names To: michael.l.coburn@gte.net (Mike Coburn) Date: Mon, 24 Jul 2000 18:55:49 +0100 (BST) Cc: linux-arm@vger.rutgers.edu In-Reply-To: <397B49F2.7DDE244B@gte.net> from "Mike Coburn" at Jul 23, 2000 12:39:30 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@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Mike Coburn writes: > patch-2.3.48-rmk1.gz > patch-2.3.48-rmk2.gz > > patch-2.3.99-pre3-rmk1.gz > patch-2.3.99-pre3-rmk2.gz > patch-2.3.99-pre3-rmk3.gz > patch-2.3.99-pre8-rmk2.gz > patch-2.3.99-pre8-rmk1.gz > patch-2.3.99-pre9-rmk2.gz > > pre-patch-2.3.23-rmk1.gz > pre-patch-2.3.49-rmk1.gz > pre-patch-3.3.51-rmk1.gz The pre- prefix means that its an alpha bit. The next section up to the -rmk is Linus' source code version number that you need to fetch to apply this patch to. Lastly, the -rmk number is the "generation" number of the patch for this version - the larger the later. Hope this explains it. _____ |_____| ------------------------------------------------- ---+---+- | | Russell King linux@arm.linux.org.uk --- --- | | | | http://www.arm.linux.org.uk/ / / | | +-+-+ --- -+- / | THE developer of ARM Linux |+| /|\ / | | | --- | +-+-+ ------------------------------------------------- /\\\ | unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 24 20:41:30 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13Go6U-0003Ib-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 24 Jul 2000 20:41:30 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 63823160C3; Mon, 24 Jul 2000 21:35:19 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Mon, 24 Jul 2000 15:15:12 -0400 Received: by vger.rutgers.edu id ; Mon, 24 Jul 2000 15:14:58 -0400 Received: from [205.250.170.220] ([205.250.170.220]:4982 "EHLO xanadu.vipswitch.com") by vger.rutgers.edu with ESMTP id ; Mon, 24 Jul 2000 15:12:05 -0400 Date: Mon, 24 Jul 2000 15:26:33 -0400 (EDT) From: Nicolas Pitre To: Jeff Sutherland Cc: "'John G Dorsey'" , "'linux-arm@vger.rutgers.edu'" Subject: RE: kernel version! In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu On Mon, 24 Jul 2000, Jeff Sutherland wrote: > > It doesn't work perfectly on stand-alone Assabet either. > > I failed to mention the kernel version in my earlier post, sorry. I'm using > 2.4.0-test2-ac1-rmk2-np3 (which has no evident problem with telnet, ftp, or > anything else). Is the flakyness you mentioned occurring in -test4-np1? I'm > not there yet. Golly, I've been doing software too long! Imagine, me > thinking there's a hardware problem! Sheesh! The bug occured with older kernel versions too. And it occurs reliably on the sixth telnet into the Assabet or so after every reboot. I don't think that a hardware bug can be triggered so deterministicly with such a high-level software sequence. I would rather suspect something with the ethernet driver and/or the TCP code. For example if odd-byte-length packets are mishandled by the driver then most likely TCP connections will fail where NFS on UDP will still work. Nicolas unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 24 22:56:24 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13GqD1-0006em-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 24 Jul 2000 22:56:24 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 08E50163D3; Mon, 24 Jul 2000 23:51:21 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Mon, 24 Jul 2000 17:08:09 -0400 Received: by vger.rutgers.edu id ; Mon, 24 Jul 2000 17:07:35 -0400 Received: from [137.203.190.1] ([137.203.190.1]:8331 "EHLO cambridge.merl.com") by vger.rutgers.edu with ESMTP id ; Mon, 24 Jul 2000 17:06:49 -0400 Received: from merl.com (eagle.merl.com [137.203.128.4]) by cambridge.merl.com (8.8.7/8.8.7) with ESMTP id RAA22368 for ; Mon, 24 Jul 2000 17:20:10 -0400 Received: from zathrus.merl.com (carbone@zathrus.merl.com [137.203.128.26]) by merl.com (8.8.7/8.8.4) with ESMTP id RAA01851 for ; Mon, 24 Jul 2000 17:20:10 -0400 Received: from localhost (carbone@localhost) by zathrus.merl.com (8.9.3/8.8.3) with ESMTP id RAA18527 for ; Mon, 24 Jul 2000 17:20:09 -0400 Date: Mon, 24 Jul 2000 17:20:09 -0400 (EDT) From: Marco Carbone To: linux-arm@vger.rutgers.edu Subject: RE: kernel version! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu >Now could someone clue me in as to what happened to the frame buffer >driver on the Assabet? It was working fine back in the >2.3.99-pre-something days, but lately I've noticed that every other scan >line is blank even though the screen geometry over all is correct (no, >it's not hardware, the phase 4 Assabet does it, too). I am not having that problem, with a 2.4.0-test1-etcetera kernel and using NanoX and Microwindows. Are you having this problem when Tux is drawn? >X and MicroWindows don't find the touch screen. "Error 2 opening touch >panel; Cannot initialise mouse" is what the nano-X driver says. The major >number is assigned dynamically. I stuck a device in /dev anyway and >pointed "mouse" to it, still no joy. This one's a little light on >documentation. >Hints, anyone, please? This is what Greg Haerr has to say on the NanoGUI mailing list (found at www.microwindows.org): "The microwindows touch screen drivers work on the MIPS Linux-VR kernels and the StrongARM ADS graphics client boxes only right now. I think Monta Vista has been working on a driver for the Assabet." I'm not sure how close Monta Vista is to finishing the driver, or if they are writing one at all (I'd assume that they are, seeing that they are marketing a product with a working touchscreen and X on the SA-1110). It's possible that a whole Assabet touchscreen driver might have to be written from scratch for Microwindows if the Monta Vista rumor is untrue, or at least the current driver will have to be modified... Marco Carbone unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 24 23:04:27 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13GqKp-0006n7-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 24 Jul 2000 23:04:27 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 550C5163DF; Mon, 24 Jul 2000 23:51:30 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Mon, 24 Jul 2000 15:57:16 -0400 Received: by vger.rutgers.edu id ; Mon, 24 Jul 2000 15:54:52 -0400 Received: from ice.fiftyone.com ([208.225.80.11]:1997 "EHLO ice.ar51.net") by vger.rutgers.edu with ESMTP id ; Mon, 24 Jul 2000 15:53:43 -0400 Received: from server01.asi (akron-80-154.ar51.net [208.225.80.154]) by ice.ar51.net (8.9.3/8.8.7) with ESMTP id QAA02536; Mon, 24 Jul 2000 16:11:22 -0400 Received: by SERVER01 with Internet Mail Service (5.5.2448.0) id <3YXN8C7T>; Mon, 24 Jul 2000 16:13:15 -0400 Message-ID: From: Jeff Sutherland To: "'Nicolas Pitre'" Cc: "'John G Dorsey'" , "'linux-arm@vger.rutgers.edu'" Subject: RE: kernel version! Date: Mon, 24 Jul 2000 16:13:10 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu > The bug occured with older kernel versions too. And it > occurs reliably on > the sixth telnet into the Assabet or so after every reboot. > I don't think > that a hardware bug can be triggered so deterministicly with such a > high-level software sequence. > > I would rather suspect something with the ethernet driver > and/or the TCP > code. For example if odd-byte-length packets are mishandled > by the driver > then most likely TCP connections will fail where NFS on UDP will still > work. > > > Nicolas OK, I've been doing some testing with this. With test4-np1 I can reproduce this. My old Assabet simply reboots when logging out from the sixth telnet session. I can't reproduce this on test2-ac1-rmk2-np3 (maybe I'm just not trying the right combinations of multiple login/logouts). Just tried logging in and out 12 times and it's still working fine. ?????? //Jeff unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Tue Jul 25 08:04:08 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13Gyl6-0006XJ-00 for linux-arm-archive@lists.arm.linux.org.uk; Tue, 25 Jul 2000 08:04:08 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 163F615D95; Tue, 25 Jul 2000 09:04:12 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 25 Jul 2000 02:44:47 -0400 Received: by vger.rutgers.edu id ; Tue, 25 Jul 2000 02:43:34 -0400 Received: from [195.77.25.34] ([195.77.25.34]:1596 "EHLO dmz1.ict.es") by vger.rutgers.edu with ESMTP id ; Tue, 25 Jul 2000 02:43:22 -0400 Received: from ict.es (Tec2.bcn.es.intranet [172.16.105.2]) by dmz1.ict.es (8.9.3/8.8.7) with ESMTP id IAA09260; Tue, 25 Jul 2000 08:02:50 +0200 Message-ID: <397D3AFF.55BCF0D3@ict.es> Date: Tue, 25 Jul 2000 09:00:15 +0200 From: Joan LLuis Montore Parera Organization: ICT electronics X-Mailer: Mozilla 4.73 [es] (X11; U; Linux 2.2.14-5.0 i686) X-Accept-Language: es-ES, es, en MIME-Version: 1.0 To: Jeff Sutherland Cc: nico@cam.org, linux-arm@vger.rutgers.edu Subject: Re: kernel version! References: Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Jeff Sutherland escribió: >X and MicroWindows don't find the touch screen. "Error 2 opening touch > panel; Cannot initialize mouse" is what the nano-X driver says. The major > number is assigned dynamically. I stuck a device in /dev anyway and pointed > "mouse" to it, still no joy. This one's a little light on documentation. > Hints, anyone, please? Hi Jeff. I have had microwindows running on Assabet for days (unfortunately, I am now waiting for my final board and I can not do more tests). The touchscreen was running without any problem (even not calibrated, a reduced version of minehunt that I modified -10x10 board- worked perfectly. In order to do so, I did this: 1.- Compiled touchscreen driver in kernel (from 2.4.0-tes1-"some_patches" up to 2.4.0-test4-np1) 2.- Started assabet 3.- "cat /proc/devices" looking for sa1100_touch (or similar). Major number found was 254. 4.- I then created 2 devices: mknod /dev/ts c 254 34 mknod /dev/tsraw c 254 18 ( I do not know if this last one is necessary) After that, microwindows was able to find and use touchscreen. I hope this helps. Saludos (Best regards). Joan Lluis Montore Parera Director de Tecnología (Technology Mgr.) ICT electronics SA email:jlm@ict.es web:www.ict.es unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Tue Jul 25 08:11:41 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13GysP-0006do-00 for linux-arm-archive@lists.arm.linux.org.uk; Tue, 25 Jul 2000 08:11:41 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 0EF4E15E17; Tue, 25 Jul 2000 09:11:42 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 25 Jul 2000 02:53:17 -0400 Received: by vger.rutgers.edu id ; Tue, 25 Jul 2000 02:53:02 -0400 Received: from web1205.mail.yahoo.com ([128.11.23.141]:4710 "HELO web1205.mail.yahoo.com") by vger.rutgers.edu with SMTP id ; Tue, 25 Jul 2000 02:52:44 -0400 Received: (qmail 21154 invoked by uid 60001); 25 Jul 2000 07:10:36 -0000 Message-ID: <20000725071036.21153.qmail@web1205.mail.yahoo.com> Received: from [202.108.21.83] by web1205.mail.yahoo.com; Tue, 25 Jul 2000 00:10:36 PDT Date: Tue, 25 Jul 2000 00:10:36 -0700 (PDT) From: wolf Subject: From sa1100 to sa1110 To: linux-arm@vger.rutgers.edu Cc: linux-arm-kernel@lists.arm.linux.org.uk MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Hi all, I ever built a arm toolchain for brutus sa1100 development board. It works well for armlinux-2.3.35 on sa1100. Now I start to try sa1110. I have too questions intuitively. 1.Do I need rebuild a new toolchain to build software for sa1110? 2.Do I need use new armlinux kernel such as armlinux-2.4.0 and corresponding new patches and what is the newest stable one? Thanks in advance. wolf __________________________________________________ Do You Yahoo!? Get Yahoo! Mail – Free email you can access from anywhere! http://mail.yahoo.com/ unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Tue Jul 25 13:05:48 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13H3T2-0002dD-00 for linux-arm-archive@lists.arm.linux.org.uk; Tue, 25 Jul 2000 13:05:48 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id ADEBE15E88; Tue, 25 Jul 2000 14:00:50 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 25 Jul 2000 07:40:20 -0400 Received: by vger.rutgers.edu id ; Tue, 25 Jul 2000 07:39:50 -0400 Received: from duteinh.et.tudelft.nl ([130.161.42.1]:2446 "EHLO duteinh.et.tudelft.nl") by vger.rutgers.edu with ESMTP id ; Tue, 25 Jul 2000 07:38:39 -0400 Received: from dutein75 by duteinh.et.tudelft.nl (8.9.3/BB-2.0) id NAA03217; Tue, 25 Jul 2000 13:56:32 +0200 (MET DST) Message-Id: <200007251156.NAA03217@duteinh.et.tudelft.nl> From: Erik Mouw To: Sun@AEPTEC.COM Cc: linux-arm@vger.rutgers.edu Subject: Re: cross-compile! In-Reply-To: <32CC5B62AF0BD2119E4C00A0C9663E221F3BED@MAIL> Organization: Eric conspiracy secret labs Date: Tue 25 Jul 2000 13:56:31 +0100 (MDT) 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.2devel - with PGP support, PGP engine version 0.5 (IRIX64) X-Mailerorigin: http://www.fsai.fh-trier.de/~schmitzj/Xclasses/XCmail/ X-Eric-Conspiracy: There is no conspiracy! X-Loop: erik@it.et.tudelft.nl MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu On Mon, 24 Jul 2000 13:57:05 -0400, Sun, Lei wrote: > I have a generic questions about cross-compile source package for > arm-linux. I have tool chain, compiler, glibc installed on my host machine > (redhat linux 6.2) in /home/arm/ directory. > some packages can be compiled by just specifying the compiler to be > arm-linux-gcc, but some couldn't. My questions are: > 1. sometimes, the make try to execute program generated during compiling, > since it's cross-compile, it couldn't execute the binary, so it existed. how > to solve this problem ( the make -i option could work, but sometimes the > package need some files generated by the compiled binary program) ? For GNU autoconf-ed packages (the ones with a configure script), you should also tell the package that you're actually cross compiling by specifying the target platform (arm-unknown-linux-gnu): setenv CC arm-linux-gcc ./configure [funny options] arm-unknown-linux-gnu With a properly crafted configure script, the binaries needed to generate the source files will be compiled with the system's native compiler, while the final binary will be compiled with the cross compiler. If that still doesn't work (like with bash), you need a native platform to get things compiled. Compaq CRL has some hosts online to do this: skiffcluster1.handhelds.org skiffcluster2.handhelds.org The username is: guest The password is: Jim Stud also has a Debian box which you can use for cross compiles. > 2. sometimes, it's couldn't find some Lib or header file, what is the > search creteria of the lib and header for the cross-compilers? > due to the resources limites, I can't install compiler on my target. In > that case, things could be trival. Use "arm-linux-gcc -pring-search-dirs" and the compiler will tell you about its directories. Erik -- "software industry, the: unique industry where selling substandard goods is legal and you can charge extra for fixing the problems." -- Duncan Simpson on BugTraq unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Tue Jul 25 18:11:15 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13H8Ed-0007mg-00 for linux-arm-archive@lists.arm.linux.org.uk; Tue, 25 Jul 2000 18:11:15 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id BC12E161A1; Tue, 25 Jul 2000 19:01:42 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 25 Jul 2000 12:41:08 -0400 Received: by vger.rutgers.edu id ; Tue, 25 Jul 2000 12:38:58 -0400 Received: from POST.ICES.CMU.EDU ([128.2.205.86]:36000 "HELO post.ices.cmu.edu") by vger.rutgers.edu with SMTP id ; Tue, 25 Jul 2000 12:37:32 -0400 Received: from VANCOUVER.ICES.CMU.EDU by post.ices.cmu.edu id aa10839; 25 Jul 2000 12:55 EDT Message-ID: <397D71FC.3BFB28EF@cs.cmu.edu> Date: Tue, 25 Jul 2000 06:54:53 -0400 From: John G Dorsey Organization: Carnegie Mellon University X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.10 i686) X-Accept-Language: en MIME-Version: 1.0 To: wolf Cc: linux-arm@vger.rutgers.edu Subject: Re: From sa1100 to sa1110 References: <20000725071036.21153.qmail@web1205.mail.yahoo.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu wolf wrote: > 1.Do I need rebuild a new toolchain to build software > for sa1110? Except for some differences that are mostly of interest to low-level code (e.g., SDRAM support), the SA-1110 is an SA-1100. Your existing toolchain should work nicely. > 2.Do I need use new armlinux kernel such as > armlinux-2.4.0 and corresponding new patches and what > is the newest stable one? Kernel 2.4.0-test4-np1 is the latest and greatest for the StrongARM; the patch you want is available from: ftp://ftp.arm.linux.org.uk/pub/armlinux/people/nico/ Note that only a couple of 1110 boards are supported at the moment. Hopefully yours is one of them. =) Good luck, -jd unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Tue Jul 25 22:22:47 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13HCA2-0003PW-00 for linux-arm-archive@lists.arm.linux.org.uk; Tue, 25 Jul 2000 22:22:46 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 890CF163F0; Tue, 25 Jul 2000 23:15:43 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 25 Jul 2000 16:55:20 -0400 Received: by vger.rutgers.edu id ; Tue, 25 Jul 2000 16:53:51 -0400 Received: from thalia.fm.intel.com ([132.233.247.11]:3420 "EHLO thalia.fm.intel.com") by vger.rutgers.edu with ESMTP id ; Tue, 25 Jul 2000 16:52:50 -0400 Received: from fmsmsx18.intel.com (fmsmsx18.fm.intel.com [132.233.233.232]) by thalia.fm.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.30 2000/06/08 18:25:35 dmccart Exp $) with ESMTP id VAA24654 for ; Tue, 25 Jul 2000 21:11:49 GMT Received: by fmsmsx18.fm.intel.com with Internet Mail Service (5.5.2650.21) id ; Tue, 25 Jul 2000 14:10:52 -0700 Message-ID: <4A043A1FE4B2D111AC3F00A0C96B5133055147B4@fmsmsx37.fm.intel.com> From: "Benavides, Edward A" To: "'linux-arm@vger.rutgers.edu'" Subject: Arm7 Date: Tue, 25 Jul 2000 14:10:44 -0700 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@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu I have to put uclinux on a custom board with an ARM7 processor. The memory map on my board is obviously different that say the Aplio board which starts its entry @ 00008000h. Where can I modify the src code before I make the kernel so that I can have the kernel start at address 00080000h. Thanks Tony Benavides unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Tue Jul 25 22:55:47 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13HCfz-000418-00 for linux-arm-archive@lists.arm.linux.org.uk; Tue, 25 Jul 2000 22:55:47 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 3BFFF1644D; Tue, 25 Jul 2000 23:51:03 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 25 Jul 2000 17:29:53 -0400 Received: by vger.rutgers.edu id ; Tue, 25 Jul 2000 17:28:39 -0400 Received: from cambridge.merl.com ([137.203.190.1]:29877 "EHLO cambridge.merl.com") by vger.rutgers.edu with ESMTP id ; Tue, 25 Jul 2000 17:28:09 -0400 Received: from merl.com (eagle.merl.com [137.203.128.4]) by cambridge.merl.com (8.8.7/8.8.7) with ESMTP id RAA31185; Tue, 25 Jul 2000 17:46:09 -0400 Received: from zathrus.merl.com (carbone@zathrus.merl.com [137.203.128.26]) by merl.com (8.8.7/8.8.4) with ESMTP id RAA26805; Tue, 25 Jul 2000 17:46:09 -0400 Received: from localhost (carbone@localhost) by zathrus.merl.com (8.9.3/8.8.3) with ESMTP id RAA21020; Tue, 25 Jul 2000 17:46:08 -0400 Date: Tue, 25 Jul 2000 17:46:08 -0400 (EDT) From: Marco Carbone To: Jeff Sutherland Cc: linux-arm@vger.rutgers.edu Subject: RE: kernel version! In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu > > >Now could someone clue me in as to what happened to the frame buffer > > >driver on the Assabet? It was working fine back in the > > >2.3.99-pre-something days, but lately I've noticed that > > every other scan > > >line is blank even though the screen geometry over all is > > correct (no, > > >it's not hardware, the phase 4 Assabet does it, too). > > > > I am not having that problem, with a 2.4.0-test1-etcetera > > kernel and using > > NanoX and Microwindows. Are you having this problem when Tux > > is drawn? > > Yes, unfortunately. Well, I upgraded to a 2.4.0-test4-np1 kernel and suddenly, my frame buffer was skipping pixel rows as well. With two cases, it seems like something is wrong with the framebuffer in this kernel. Does anyone out there have 2.4.0-test4-np1 working with a clean display? > I received a reply from jlm@ict.es who claimed to have the MicroWindows > driver working on an Assabet with the latest kernel. He suggested creating > two devices, mknod /dev/ts c 254 34 and mknod /dev/tsraw c 254 18 which was > the info I was looking for. However, when starting the nano-X binary, > nothing much happens until I touch the display, then I get a core dump. > Well, that's some progress I guess :( The specific error message is: > > GsError 7, 0 > Segmentation fault (core dumped) > > After looking at ucb1200_ts.c in the kernel it was obvious that this is a > work in progress. Did you try running any of the demos (like npanel.sh)? It's possible they might be more receptive to the touchscreen... I have done the same thing with the mknods, but rather than a Seg fault, I'm afraid I get no response at all. However, I'm no longer getting the 'Error 2 opening touch panel' - so that's a start. Has anyone else got the touchscreen working as simply as Joan? Marco unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Tue Jul 25 23:02:15 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13HCmF-00047u-00 for linux-arm-archive@lists.arm.linux.org.uk; Tue, 25 Jul 2000 23:02:15 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 7B1DB16430; Tue, 25 Jul 2000 23:54:25 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 25 Jul 2000 17:34:14 -0400 Received: by vger.rutgers.edu id ; Tue, 25 Jul 2000 17:33:07 -0400 Received: from [12.38.17.9] ([12.38.17.9]:3348 "EHLO mail.aeptec.com") by vger.rutgers.edu with ESMTP id ; Tue, 25 Jul 2000 17:32:45 -0400 Received: by MAIL with Internet Mail Service (5.5.2650.21) id ; Tue, 25 Jul 2000 17:41:30 -0400 Message-ID: <32CC5B62AF0BD2119E4C00A0C9663E221F3BF4@MAIL> From: "Sun, Lei" To: 'Jeff Sutherland' Cc: 'Nicolas Pitre' , 'John G Dorsey' , "'linux-arm@vger.rutgers.edu'" Subject: RE: kernel version! Date: Tue, 25 Jul 2000 17:41:22 -0400 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@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Hi all: I would like to report the status for the ethernet problem for 2.4.0-test2, test4 with or without neponset. for standalone SA1110 assbet. As I mentioned that the telnet session stuck after trying a couple of times. I rebuilt the tcpd program. but it didn't work. Obviously it's also not the in.telnetd problem, because the ftp also stucked if telnet session hang there. BUT a interesting thing I found is that I installed a apache webserver program on my target. I CAN always browse a simple webpage even when telnet or ftp hangning there. How could this happened? if the driver has some problem. webserver should also go wrong if other TCP program hang there. Lei Sun unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Wed Jul 26 00:23:36 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13HE2y-0005RJ-00 for linux-arm-archive@lists.arm.linux.org.uk; Wed, 26 Jul 2000 00:23:36 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id EB2D416525; Wed, 26 Jul 2000 01:15:24 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 25 Jul 2000 18:53:44 -0400 Received: by vger.rutgers.edu id ; Tue, 25 Jul 2000 18:53:12 -0400 Received: from pcow028o.blueyonder.co.uk ([195.188.53.124]:1714 "EHLO blueyonder.co.uk") by vger.rutgers.edu with ESMTP id ; Tue, 25 Jul 2000 18:52:45 -0400 Received: from RiscPC ([62.30.162.30]) by blueyonder.co.uk with Microsoft SMTPSVC(5.5.1877.197.19); Wed, 26 Jul 2000 00:11:10 +0100 MIME-Version: 1.0 From: "Jeremy Coates: Mailing Lists" To: linux-arm@vger.rutgers.edu Date: Wed, 26 Jul 2000 00:12:04 +0100 Subject: CATS? Message-ID: <49e3dd6e8flists@co-comp.co.uk> User-Agent: Pluto/2.02b (RISC-OS/4.02) POPstar/2.02 Content-Type: text/plain Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Hi All, Just a quicky - is their an idiots guide to getting a decent distribution going on a CATS server? I know the kernel had support added (Phil Blundell) but need a 'get going' webpage to show how it's all done. Any pointers gladly received. TIA, Jeremy Coates -- Co-Comp, PO BOX 199, PRESTON. PR1 9SS UK Turn-key computing and internet solutions Web: http://www.co-comp.co.uk RiscStation Registered Dealer Email: enquiry@co-comp.co.uk Castle Registered Dealer Tel: +44 (0)7970 064479 Authorised RISCOS Installer Fax: +44 (0)7971 434612 unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Wed Jul 26 00:46:17 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13HEOv-0005os-00 for linux-arm-archive@lists.arm.linux.org.uk; Wed, 26 Jul 2000 00:46:17 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 4D9C9160E6; Wed, 26 Jul 2000 01:39:15 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Tue, 25 Jul 2000 19:20:23 -0400 Received: by vger.rutgers.edu id ; Tue, 25 Jul 2000 19:20:10 -0400 Received: from baucis.sc.intel.com ([143.183.152.22]:2374 "EHLO baucis.sc.intel.com") by vger.rutgers.edu with ESMTP id ; Tue, 25 Jul 2000 19:19:57 -0400 Received: from SMTP (fmsmsxvs03-1.fm.intel.com [132.233.42.203]) by baucis.sc.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.30 2000/06/08 18:25:35 dmccart Exp $) with SMTP id QAA28231 for ; Tue, 25 Jul 2000 16:38:03 -0700 (PDT) Received: from fmsmsx19.fm.intel.com ([132.233.48.19]) by 132.233.48.203 (Norton AntiVirus for Internet Email Gateways 1.0) ; Tue, 25 Jul 2000 23:38:02 0000 (GMT) Received: by fmsmsx19.fm.intel.com with Internet Mail Service (5.5.2650.21) id ; Tue, 25 Jul 2000 16:38:01 -0700 Message-ID: From: "Naik, Uday" To: linux-arm@vger.rutgers.edu Subject: testsuite Date: Tue, 25 Jul 2000 16:37:58 -0700 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@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Hi, Is there a testsuite for linux, which comprehensively exercises OS features like semaphores, shared memory, threads etc. Thanks Uday --- All opinions expressed are mine and do not reflect those of my employer. unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Wed Jul 26 08:15:55 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13HLQ3-0002Ay-00 for linux-arm-archive@lists.arm.linux.org.uk; Wed, 26 Jul 2000 08:15:55 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 7D12A15F45; Wed, 26 Jul 2000 09:15:53 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Wed, 26 Jul 2000 02:56:53 -0400 Received: by vger.rutgers.edu id ; Wed, 26 Jul 2000 02:56:45 -0400 Received: from tazenda.demon.co.uk ([158.152.220.239]:3917 "EHLO tazenda.demon.co.uk") by vger.rutgers.edu with ESMTP id ; Wed, 26 Jul 2000 02:56:36 -0400 Received: from kings-cross.london.uk.eu.org [::ffff:192.168.2.83] by tazenda.demon.co.uk with esmtp (Exim 3.11 #1 (Debian)) id 13HLSG-0001uB-00; Wed, 26 Jul 2000 08:18:12 +0100 Received: from localhost ([::ffff:127.0.0.1] helo=tazenda.demon.co.uk ident=pb) by kings-cross.london.uk.eu.org with esmtp (Exim 3.12 #1 (Debian)) id 13HLQ8-00059m-00; Wed, 26 Jul 2000 08:16:00 +0100 X-Mailer: exmh version 2.1.1 10/15/1999 (debian) To: "Jeremy Coates: Mailing Lists" Cc: linux-arm@vger.rutgers.edu Subject: Re: CATS? In-Reply-To: Message from "Jeremy Coates: Mailing Lists" of "Wed, 26 Jul 2000 00:12:04 BST." <49e3dd6e8flists@co-comp.co.uk> References: <49e3dd6e8flists@co-comp.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 26 Jul 2000 08:16:00 +0100 From: Philip Blundell Message-Id: Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu >Just a quicky - is their an idiots guide to getting a decent distribution >going on a CATS server? It's not completely trivial at the moment. From what I remember the CATS firmware can't boot off CD or floppy so you need to either boot over NFS or from your NetBSD partition initially. Debian will run on a CATS but I don't know what the state of support in the boot disks is. You might be able to use some variant of the NetWinder install process. I hope to get time to look into this properly soon. p. unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Wed Jul 26 08:45:48 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13HLsy-0002Yg-00 for linux-arm-archive@lists.arm.linux.org.uk; Wed, 26 Jul 2000 08:45:48 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id EB7C615DBE; Wed, 26 Jul 2000 09:45:47 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Wed, 26 Jul 2000 03:26:57 -0400 Received: by vger.rutgers.edu id ; Wed, 26 Jul 2000 03:26:49 -0400 Received: from [195.77.25.34] ([195.77.25.34]:2178 "EHLO dmz1.ict.es") by vger.rutgers.edu with ESMTP id ; Wed, 26 Jul 2000 03:26:30 -0400 Received: from ict.es (Tec2.bcn.es.intranet [172.16.105.2]) by dmz1.ict.es (8.9.3/8.8.7) with ESMTP id IAA17854; Wed, 26 Jul 2000 08:46:40 +0200 Message-ID: <397E969E.44DBF96A@ict.es> Date: Wed, 26 Jul 2000 09:43:26 +0200 From: Joan LLuis Montore Parera Organization: ICT electronics X-Mailer: Mozilla 4.73 [es] (X11; U; Linux 2.2.14-5.0 i686) X-Accept-Language: es-ES, es, en MIME-Version: 1.0 To: Marco Carbone Cc: Jeff Sutherland , linux-arm@vger.rutgers.edu Subject: Re: kernel version! References: Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu >> I received a reply from jlm@ict.es who claimed to have the MicroWindows >> driver working on an Assabet with the latest kernel. He suggested creating >> two devices, mknod /dev/ts c 254 34 and mknod /dev/tsraw c 254 18 which was >> the info I was looking for. However, when starting the nano-X binary, >> nothing much happens until I touch the display, then I get a core dump. >> Well, that's some progress I guess :( The specific error message is: >> >> GsError 7, 0 >> Segmentation fault (core dumped) >> >> After looking at ucb1200_ts.c in the kernel it was obvious that this is a >> work in progress. The programs based on Nano-X die when you use the touch (concretely when receiving the pen up event). The programs based on microwindows (like mine) works properly. After some hacking, I found that if you comment out the line 72 ( return -1;) of microwindows/src/drivers/mou_ts.c the nano-X based applications work perfectly. I assumed it was a small misunderstanding between the nano-X code and the touchscreen driver that is being worked now. > Did you try running any of the demos (like npanel.sh)? It's possible they > might be more receptive to the touchscreen... If you try them without the modification I suggested, they are going to fail. As I previously said only the microwindows based (mine, malpha, etc.) work directly Saludos (Best regards). Joan Lluis Montore Parera Director de Tecnología (Technology Mgr.) ICT electronics SA email:jlm@ict.es web:www.ict.es unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Wed Jul 26 08:58:40 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13HM5Q-0002jP-00 for linux-arm-archive@lists.arm.linux.org.uk; Wed, 26 Jul 2000 08:58:40 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 7D7D715FD5; Wed, 26 Jul 2000 09:58:38 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Wed, 26 Jul 2000 03:37:53 -0400 Received: by vger.rutgers.edu id ; Wed, 26 Jul 2000 03:35:32 -0400 Received: from plum.flirble.org ([195.40.6.20]:3760 "EHLO plum.flirble.org") by vger.rutgers.edu with ESMTP id ; Wed, 26 Jul 2000 03:34:20 -0400 Received: from nick by plum.flirble.org with local (Exim 3.12 #5) id 13HLzV-0008DK-00; Wed, 26 Jul 2000 08:52:33 +0100 Date: Wed, 26 Jul 2000 08:52:33 +0100 From: Nicholas Clark To: "Naik, Uday" Cc: linux-arm@vger.rutgers.edu Subject: Re: testsuite Message-ID: <20000726085233.A31112@plum.flirble.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from uday.naik@intel.com on Tue, Jul 25, 2000 at 04:37:58PM -0700 X-Organisation: Tetrachloromethane Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu On Tue, Jul 25, 2000 at 04:37:58PM -0700, Naik, Uday wrote: > > Hi, > > Is there a testsuite for linux, which comprehensively exercises OS > features like semaphores, shared memory, threads etc. I don't know of a direct test, but parts of the perl testsuite can be quite effective (make test in the perl build directory). It certainly found what turned out to be a small bug in arm glibc 2.1 w.r.t. the size of group IDs, and the system V IPC module's tests attempt to exercise semaphores and shared memory. However, it's not ideal as one has to investigate (possibly with ad hoc C programs) whether reported failures are due to bugs in perl or bugs further down. Nicholas Clark unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Wed Jul 26 10:48:13 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13HNnR-0004Qk-00 for linux-arm-archive@lists.arm.linux.org.uk; Wed, 26 Jul 2000 10:48:13 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 9C5661601F; Wed, 26 Jul 2000 11:48:06 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Wed, 26 Jul 2000 05:28:46 -0400 Received: by vger.rutgers.edu id ; Wed, 26 Jul 2000 05:28:17 -0400 Received: from pcow024o.blueyonder.co.uk ([195.188.53.126]:2467 "EHLO blueyonder.co.uk") by vger.rutgers.edu with ESMTP id ; Wed, 26 Jul 2000 05:26:28 -0400 Received: from RiscPC ([62.30.162.30]) by blueyonder.co.uk with Microsoft SMTPSVC(5.5.1877.197.19); Wed, 26 Jul 2000 10:45:31 +0100 MIME-Version: 1.0 From: "Jeremy Coates: Mailing Lists" To: linux-arm@vger.rutgers.edu Date: Wed, 26 Jul 2000 10:46:11 +0100 Subject: Re: CATS? Message-ID: <49e4177cc9lists@co-comp.co.uk> In-Reply-To: References: <49e3dd6e8flists@co-comp.co.uk> 49e3dd6e8flists@co-comp.co.uk> User-Agent: Pluto/2.02b (RISC-OS/4.02) POPstar/2.02 Content-Type: text/plain Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu In article , Philip Blundell wrote: > >Just a quicky - is their an idiots guide to getting a decent > >distribution going on a CATS server? > It's not completely trivial at the moment. From what I remember the > CATS firmware can't boot off CD or floppy so you need to either boot > over NFS or from your NetBSD partition initially. Debian will run on a > CATS but I don't know what the state of support in the boot disks is. > You might be able to use some variant of the NetWinder install process. > I hope to get time to look into this properly soon. Cheers for the response - as I thought really - still black art stuff - I have other boxes running RHat 6.2 so could (in theory) boot from NFS via these - any webpages I should be reading? BTW, does Debian have native support for the CATS system or is it a kernel re-compile scenario? If you're doing any work in this are keep me posted! Ta! BFN Jeremy -- Co-Comp, PO BOX 199, PRESTON. PR1 9SS UK Turn-key computing and internet solutions Web: http://www.co-comp.co.uk RiscStation Registered Dealer Email: enquiry@co-comp.co.uk Castle Registered Dealer Tel: +44 (0)7970 064479 Authorised RISCOS Installer Fax: +44 (0)7971 434612 unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Wed Jul 26 13:08:48 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13HPzU-0006Sk-00 for linux-arm-archive@lists.arm.linux.org.uk; Wed, 26 Jul 2000 13:08:48 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 99FF01618F; Wed, 26 Jul 2000 14:01:30 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Wed, 26 Jul 2000 07:41:21 -0400 Received: by vger.rutgers.edu id ; Wed, 26 Jul 2000 07:41:12 -0400 Received: from tazenda.demon.co.uk ([158.152.220.239]:4021 "EHLO tazenda.demon.co.uk") by vger.rutgers.edu with ESMTP id ; Wed, 26 Jul 2000 07:40:53 -0400 Received: from kings-cross.london.uk.eu.org [::ffff:192.168.2.83] by tazenda.demon.co.uk with esmtp (Exim 3.11 #1 (Debian)) id 13HOgl-0002DX-00; Wed, 26 Jul 2000 11:45:23 +0100 Received: from localhost ([::ffff:127.0.0.1] helo=tazenda.demon.co.uk ident=pb) by kings-cross.london.uk.eu.org with esmtp (Exim 3.12 #1 (Debian)) id 13HOeY-0000pr-00; Wed, 26 Jul 2000 11:43:06 +0100 X-Mailer: exmh version 2.1.1 10/15/1999 (debian) To: "Jeremy Coates: Mailing Lists" Cc: linux-arm@vger.rutgers.edu Subject: Re: CATS? In-Reply-To: Message from "Jeremy Coates: Mailing Lists" of "Wed, 26 Jul 2000 10:46:11 BST." <49e4177cc9lists@co-comp.co.uk> References: <49e3dd6e8flists@co-comp.co.uk> 49e3dd6e8flists@co-comp.co.uk> <49e4177cc9lists@co-comp.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 26 Jul 2000 11:43:06 +0100 From: Philip Blundell Message-Id: Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu >BTW, does Debian have native support for the CATS system or is it a kernel >re-compile scenario? I'm not sure. You should probably ask on the debian-arm list. There's no reason the NetWinder kernel can't also support EBSA-285 and NetWinder, but it has to be compiled with the right options. p. unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Wed Jul 26 15:28:27 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13HSAd-00004x-00 for linux-arm-archive@lists.arm.linux.org.uk; Wed, 26 Jul 2000 15:28:27 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id DFC7316155; Wed, 26 Jul 2000 16:23:22 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Wed, 26 Jul 2000 10:04:28 -0400 Received: by vger.rutgers.edu id ; Wed, 26 Jul 2000 10:04:19 -0400 Received: from crl.dec.com ([192.58.206.2]:3712 "EHLO crl.dec.com") by vger.rutgers.edu with ESMTP id ; Wed, 26 Jul 2000 10:04:06 -0400 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 KAA05474; Wed, 26 Jul 2000 10:22:22 -0400 (EDT) Received: by crlwebmail.crl.dec.com with Internet Mail Service (5.5.2650.21) id ; Wed, 26 Jul 2000 10:27:25 -0400 Message-ID: From: George France To: "'Philip Blundell'" , "Jeremy Coates: Mailing Lists" Cc: linux-arm@vger.rutgers.edu Subject: RE: CATS? Date: Wed, 26 Jul 2000 10:22:24 -0400 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@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu I am using NFS for my CATS system. It seems that the ALI 15x3 (IDE) driver is broke in Linuxd-2.4.0-test4. When I get some time this week, I will take a look at it. --George George France, france@crl.dec.com Cambridge Research Laboratory, Compaq Computer Corporation One Cambridgecenter MS: CRL Cambridge, MA 02142 USA > -----Original Message----- > From: Philip Blundell [mailto:pb@tazenda.demon.co.uk] > Sent: Wednesday, July 26, 2000 6:43 AM > To: Jeremy Coates: Mailing Lists > Cc: linux-arm@vger.rutgers.edu > Subject: Re: CATS? > > > >BTW, does Debian have native support for the CATS system or > is it a kernel > >re-compile scenario? > > I'm not sure. You should probably ask on the debian-arm > list. There's no > reason the NetWinder kernel can't also support EBSA-285 and > NetWinder, but it > has to be compiled with the right options. > > p. > > > > unsubscribe: body of `unsubscribe linux-arm' to > majordomo@vger.rutgers.edu > ++ Please use linux-arm-kernel@lists.arm.linux.org.uk > for ++ > ++ kernel-related discussions. > ++ > unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Wed Jul 26 16:27:39 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13HT5v-00013G-00 for linux-arm-archive@lists.arm.linux.org.uk; Wed, 26 Jul 2000 16:27:39 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 7E45916155; Wed, 26 Jul 2000 17:19:25 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Wed, 26 Jul 2000 11:00:21 -0400 Received: by vger.rutgers.edu id ; Wed, 26 Jul 2000 11:00:08 -0400 Received: from cvsftp.cotw.com ([208.242.241.39]:4734 "EHLO cvsftp.cotw.com") by vger.rutgers.edu with ESMTP id ; Wed, 26 Jul 2000 10:59:46 -0400 Received: from cotw.com (IDENT:samcconn@ptecdev2.ptec.com [192.168.10.4]) by cvsftp.cotw.com (8.9.3/8.9.3) with ESMTP id KAA05950 for ; Wed, 26 Jul 2000 10:17:43 -0500 Message-ID: <397F01D9.82FC2D95@cotw.com> Date: Wed, 26 Jul 2000 10:20:57 -0500 From: S A McConnell Reply-To: samcconn@cotw.com X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.14 i686) X-Accept-Language: en MIME-Version: 1.0 To: linux-arm@vger.rutgers.edu Subject: RAM DISK problem Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu I am using an initrd. The kernel complains VFS: Mounted root (ext2 filesystem). attempt to access beyond end of device 01:00: rw=0, want=12637, limit=10324 What is the kernel trying to tell me? SAM unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Wed Jul 26 16:40:15 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13HTI6-0001FC-00 for linux-arm-archive@lists.arm.linux.org.uk; Wed, 26 Jul 2000 16:40:14 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id A322B1626F; Wed, 26 Jul 2000 17:32:45 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Wed, 26 Jul 2000 11:13:10 -0400 Received: by vger.rutgers.edu id ; Wed, 26 Jul 2000 11:12:55 -0400 Received: from [205.250.170.220] ([205.250.170.220]:2685 "EHLO xanadu.vipswitch.com") by vger.rutgers.edu with ESMTP id ; Wed, 26 Jul 2000 11:12:31 -0400 Date: Wed, 26 Jul 2000 11:27:19 -0400 (EDT) From: Nicolas Pitre To: S A McConnell Cc: linux-arm@vger.rutgers.edu Subject: Re: RAM DISK problem In-Reply-To: <397F01D9.82FC2D95@cotw.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu On Wed, 26 Jul 2000, S A McConnell wrote: > I am using an initrd. > > The kernel complains > > VFS: Mounted root (ext2 filesystem). > attempt to access beyond end of device > 01:00: rw=0, want=12637, limit=10324 > > > What is the kernel trying to tell me? That your initrd filesystem is too large for the maximum ramdisk size you specified to the kernel. Nicolas unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Wed Jul 26 17:21:40 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13HTwC-0001uL-00 for linux-arm-archive@lists.arm.linux.org.uk; Wed, 26 Jul 2000 17:21:40 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id C5FC716352; Wed, 26 Jul 2000 18:16:03 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Wed, 26 Jul 2000 11:38:26 -0400 Received: by vger.rutgers.edu id ; Wed, 26 Jul 2000 11:38:04 -0400 Received: from [212.166.156.49] ([212.166.156.49]:1110 "HELO finnegan.canbox.com") by vger.rutgers.edu with SMTP id ; Wed, 26 Jul 2000 11:37:21 -0400 Received: by finnegan.canbox.com (Postfix, from userid 1000) id 988613D7F; Wed, 26 Jul 2000 17:56:31 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by finnegan.canbox.com (Postfix) with ESMTP id 5B8273D7E for ; Wed, 26 Jul 2000 17:56:31 +0200 (CEST) Date: Wed, 26 Jul 2000 17:56:11 +0200 (CEST) From: Peter Koellner X-Sender: peter@finnegan To: linux-arm@vger.rutgers.edu Subject: strong arm cpu boards for linux? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu hi! for a prototype robot, i need an embedded system running linux. unfortunately i did not manage to get any useful information where to buy a standalone SA 1100 device within the last days. so are there any available? if yes, which is suitable for linux, and where can i get them? -- peter koellner canbox mobile reaction forces ;-) unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Wed Jul 26 18:09:08 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13HUg8-0002ek-00 for linux-arm-archive@lists.arm.linux.org.uk; Wed, 26 Jul 2000 18:09:08 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 7BD9316089; Wed, 26 Jul 2000 19:03:19 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Wed, 26 Jul 2000 12:43:32 -0400 Received: by vger.rutgers.edu id ; Wed, 26 Jul 2000 12:41:56 -0400 Received: from netwinder.org ([207.245.35.202]:64575 "EHLO kei.netwinder.org") by vger.rutgers.edu with ESMTP id ; Wed, 26 Jul 2000 12:41:33 -0400 Received: from netwinder.org ([10.1.19.121]) by kei.netwinder.org (8.9.3/8.9.3) with ESMTP id MAA01811; Wed, 26 Jul 2000 12:59:43 -0400 Message-ID: <397F165E.6ADE1CB0@netwinder.org> Date: Wed, 26 Jul 2000 12:48:30 -0400 From: Scott Bambrough Organization: Rebel.com X-Mailer: Mozilla 4.7 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 Newsgroups: netwinder.announce,netwinder.devel To: linux-arm@vger.rutgers.edu, linux-arm-announce@lists.arm.linux.org.uk Subject: New version of Java JDK 1.1.8 available for NetWinder DM 3.1-15. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu In response to the growing number of requests for a Java JDK to run on the NetWinder I asked Scott Hutinger of BlackDown to build and post a new version based on the latest shipping NetWinder image (DM 3.1-15a). He has graciously rebuilt JDK 1.1.8 and made it available from here: ftp://ftp.tux.org/pub/java/JDK-1.1.8/arm/v2 It should eventually be mirrored and appear on the Blackdown mirrors. Scott -- Scott Bambrough - Software Engineer REBEL.COM http://www.rebel.com NetWinder http://www.netwinder.org unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Wed Jul 26 18:43:58 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13HVDq-0004Mq-00 for linux-arm-archive@lists.arm.linux.org.uk; Wed, 26 Jul 2000 18:43:58 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 7FC641627E; Wed, 26 Jul 2000 19:34:19 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Wed, 26 Jul 2000 13:13:01 -0400 Received: by vger.rutgers.edu id ; Wed, 26 Jul 2000 13:12:50 -0400 Received: from h-207-228-100-82.gen.cadvision.com ([207.228.100.82]:1242 "EHLO vorcha.cal.montage.ca") by vger.rutgers.edu with ESMTP id ; Wed, 26 Jul 2000 13:11:36 -0400 Received: from montage.ca (192-168-42-157.cal.montage.ca [192.168.42.157]) by vorcha.cal.montage.ca (8.9.3/8.9.3) with ESMTP id LAA05667; Wed, 26 Jul 2000 11:28:58 -0600 Message-ID: <397F1FCB.B4799B0C@montage.ca> Date: Wed, 26 Jul 2000 11:28:43 -0600 From: Chris Price Organization: Montage IT Services X-Mailer: Mozilla 4.51 [en] (WinNT; U) X-Accept-Language: en,pdf MIME-Version: 1.0 To: Scott Bambrough Cc: linux-arm@vger.rutgers.edu Subject: Re: New version of Java JDK 1.1.8 available for NetWinder DM 3.1-15. References: <397F165E.6ADE1CB0@netwinder.org> Content-Type: multipart/mixed; boundary="------------B07EC6AF9037FB8FA1371A97" Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu This is a multi-part message in MIME format. --------------B07EC6AF9037FB8FA1371A97 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Scott Bambrough wrote: > > In response to the growing number of requests for a Java JDK to run on the > NetWinder I asked Scott Hutinger of BlackDown to build and post a new version > based on the latest shipping NetWinder image (DM 3.1-15a). He has graciously > rebuilt JDK 1.1.8 and made it available from here: > > ftp://ftp.tux.org/pub/java/JDK-1.1.8/arm/v2 > > It should eventually be mirrored and appear on the Blackdown mirrors. > > Scott Thanks Scott and Scott! I was wondering if there was any current effort underway to build a 1.2/1.3 jdk for ARM/Linux? Cheers Chris Price --------------B07EC6AF9037FB8FA1371A97 Content-Type: text/x-vcard; charset=us-ascii; name="chris.price.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Chris Price Content-Disposition: attachment; filename="chris.price.vcf" begin:vcard n:Price;Chris x-mozilla-html:FALSE url:http://www.montage.ca org:MONTAGE eIntegration(TM) Inc.;Technical Delivery Team adr:;;;Calgary;Alberta;;CANADA version:2.1 email;internet:chris.price@montage.ca title:Systems Specialist fn:Chris Price end:vcard --------------B07EC6AF9037FB8FA1371A97-- unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Thu Jul 27 07:21:06 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13Hh2Y-0007hj-00 for linux-arm-archive@lists.arm.linux.org.uk; Thu, 27 Jul 2000 07:21:06 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 9B00B1635A; Thu, 27 Jul 2000 08:21:05 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Thu, 27 Jul 2000 02:01:18 -0400 Received: by vger.rutgers.edu id ; Thu, 27 Jul 2000 02:01:06 -0400 Received: from nanum.kaeri.re.kr ([147.43.15.12]:2758 "EHLO nanum.kaeri.re.kr") by vger.rutgers.edu with ESMTP id ; Thu, 27 Jul 2000 02:00:40 -0400 Received: from sghong ([147.43.73.178]) by nanum.kaeri.re.kr (8.9.1a-H1/8.9.3) with SMTP id PAA21569 for ; Thu, 27 Jul 2000 15:19:26 +0900 (kst) Message-ID: <001c01bff792$93437220$5a00a8c0@sghong> From: "Sun-Gi Hong" To: Subject: [Q] Writing kernel image to the flash rom on Assaget BD Date: Thu, 27 Jul 2000 15:19:08 +0900 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0019_01BFF7DE.02B574F0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 Disposition-Notification-To: "Sun-Gi Hong" X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu This is a multi-part message in MIME format. ------=_NextPart_000_0019_01BFF7DE.02B574F0 Content-Type: text/plain; charset="ks_c_5601-1987" Content-Transfer-Encoding: base64 SGVsbG8sDQoNCk5vdyBJIGFtIHRyeWluZyB0byB3cml0ZSBrZXJuZWwgaW1hZ2UgdG8gdGhlIGZs YXNoIG9uIEFzc2FiZXQgQkQuIEFjY29yZGluZyB0byBteSBzdXJ2ZXksIHRoZXJlJ3JlIHNvbWUg Ym9vdCBsb2FkZXJzIGFzIGZvbGxvd3MuDQoNCkxBUlQgYm9vdCBsb2FkZXINCkhhbmRoZWxkcyBi b290IGxvYWRlcg0KSGFja2luZyBqZmxhc2ggcHJvZ3JhbQ0KDQpBbGwgdGhlIGFib3ZlIG5lZWQg bWUgdG8gbW9kaWZ5IHRoZSBzb3VyY2VzLCBob3dldmVyIEkgZG9uJ3Qgd2hhdCBJIHNob3VsZCBt b2RpZnkuIERvZXMgYW55b25lIHN1Y2NlZWQgaW4gd3JpdGluZyB0aGUga2VybmVsIGltYWdlIHRv IHRoZSBmbGFzaCBvbiBBc3NhYmV0IEJEPyBJZiB5ZXMsIHBsZWFzZSBnaXZlIG1lIGFueSBzdWdn ZXN0aW9ucy4gVGhhbmsgeW91IGluIGFkdmFuY2UuIA0K ------=_NextPart_000_0019_01BFF7DE.02B574F0 Content-Type: text/html; charset="ks_c_5601-1987" Content-Transfer-Encoding: base64 PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PWtz X2NfNTYwMS0xOTg3IiBodHRwLWVxdWl2PUNvbnRlbnQtVHlwZT4NCjxNRVRBIGNvbnRlbnQ9Ik1T SFRNTCA1LjAwLjI5MjAuMCIgbmFtZT1HRU5FUkFUT1I+DQo8U1RZTEU+PC9TVFlMRT4NCjwvSEVB RD4NCjxCT0RZIGJnQ29sb3I9I2ZmZmZmZj4NCjxESVY+PEZPTlQgc2l6ZT0yPkhlbGxvLDwvRk9O VD48L0RJVj4NCjxESVY+Jm5ic3A7PC9ESVY+DQo8RElWPjxGT05UIHNpemU9Mj5Ob3cgSSBhbSB0 cnlpbmcgdG8gd3JpdGUga2VybmVsIGltYWdlIHRvIHRoZSBmbGFzaCBvbiBBc3NhYmV0IA0KQkQu IEFjY29yZGluZyB0byBteSBzdXJ2ZXksIHRoZXJlJ3JlIHNvbWUgYm9vdCBsb2FkZXJzIGFzIGZv bGxvd3MuPC9GT05UPjwvRElWPg0KPERJVj4mbmJzcDs8L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0y PkxBUlQgYm9vdCBsb2FkZXI8L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIHNpemU9Mj5IYW5kaGVs ZHMgYm9vdCBsb2FkZXI8L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIHNpemU9Mj5IYWNraW5nIGpm bGFzaCBwcm9ncmFtPC9GT05UPjwvRElWPg0KPERJVj4mbmJzcDs8L0RJVj4NCjxESVY+PEZPTlQg c2l6ZT0yPkFsbCB0aGUgYWJvdmUgbmVlZCBtZSB0byBtb2RpZnkgdGhlIHNvdXJjZXMsIGhvd2V2 ZXIgSSBkb24ndCANCndoYXQgSSBzaG91bGQgbW9kaWZ5LiBEb2VzIGFueW9uZSBzdWNjZWVkIGlu IHdyaXRpbmcgdGhlIGtlcm5lbCBpbWFnZSB0byB0aGUgDQpmbGFzaCBvbiBBc3NhYmV0IEJEPyBJ ZiB5ZXMsJm5ic3A7cGxlYXNlIGdpdmUgbWUgYW55IHN1Z2dlc3Rpb25zLiBUaGFuayB5b3UgaW4g DQphZHZhbmNlLiA8L0ZPTlQ+PC9ESVY+PC9CT0RZPjwvSFRNTD4NCg== ------=_NextPart_000_0019_01BFF7DE.02B574F0-- unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Thu Jul 27 07:56:45 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13Hhb3-0008BG-00 for linux-arm-archive@lists.arm.linux.org.uk; Thu, 27 Jul 2000 07:56:45 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id BBE9515F2C; Thu, 27 Jul 2000 08:56:45 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Thu, 27 Jul 2000 02:37:36 -0400 Received: by vger.rutgers.edu id ; Thu, 27 Jul 2000 02:37:27 -0400 Received: from imail.cyberec.com ([202.60.252.12]:3190 "EHLO imail.cyberec.com") by vger.rutgers.edu with ESMTP id ; Thu, 27 Jul 2000 02:37:14 -0400 Received: from linux (ip-251-228.cyberec.com [203.85.251.228]) by imail.cyberec.com (8.9.3/8.8.7) with SMTP id PAA09825 for ; Thu, 27 Jul 2000 15:03:54 +0800 Message-ID: <00cc01bff798$700c30c0$4e01a8c0@linux.emsoftltd.com> From: "Jacky Lam" To: Subject: A strange library Date: Thu, 27 Jul 2000 15:00:36 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.1 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Currently, I have a library and want it to link with my application. So, I use "arm-linux-gcc -Wall main.c libxxx.a". It looks good that no error is produced. When I put it into my 7212 board, and run it, a kernel panic is resulted. The exact error is "Kernel panic: Unknown data abort code 4194304 [pc=020014e8, *pc=e14192b0] LR=0x014e8" When I trace the program, the data abort occurs at once it branch to the library code. Can anyone help? Yours, Jacky Lam unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Thu Jul 27 09:48:51 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13HjLW-0001LA-00 for linux-arm-archive@lists.arm.linux.org.uk; Thu, 27 Jul 2000 09:48:51 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id BCBDA16063; Thu, 27 Jul 2000 10:48:33 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Thu, 27 Jul 2000 04:29:21 -0400 Received: by vger.rutgers.edu id ; Thu, 27 Jul 2000 04:29:13 -0400 Received: from h114-210-243-147.iii.org.tw ([210.243.147.114]:49803 "EHLO mta0.iii.org.tw") by vger.rutgers.edu with ESMTP id ; Thu, 27 Jul 2000 04:28:59 -0400 Received: from [140.92.66.45] (helo=iiidns.iii.org.tw) by mta0.iii.org.tw with esmtp (Exim 3.14 #1) id 13HjJc-0003PU-00; Thu, 27 Jul 2000 16:46:52 +0800 Received: from Moya ([140.92.12.219]) by iiidns.iii.org.tw (8.10.2/8.10.2) with SMTP id e6R8qwn15239; Thu, 27 Jul 2000 16:52:58 +0800 (CST) Message-ID: <00cd01bff7a7$cc1090a0$db0c5c8c@Moya.trd.iii.org.tw> From: "Moya" To: "Benavides, Edward A" , Subject: Re: Arm7 Date: Thu, 27 Jul 2000 16:51:03 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="big5" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu >Where can I modify the src code before I make the kernel so that I can have the kernel >start at address 00080000h. try to modify arch/armnommu/Makefile:TEXTADDR = 0x00080000 or arch/armnommu/Makefile:textaddr =0x00080000 Good luck~ Regards, Moya unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Thu Jul 27 11:46:23 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13HlBH-0002yB-00 for linux-arm-archive@lists.arm.linux.org.uk; Thu, 27 Jul 2000 11:46:23 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 2D53715D63; Thu, 27 Jul 2000 12:46:23 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Thu, 27 Jul 2000 06:27:01 -0400 Received: by vger.rutgers.edu id ; Thu, 27 Jul 2000 06:26:51 -0400 Received: from tazenda.demon.co.uk ([158.152.220.239]:4731 "EHLO tazenda.demon.co.uk") by vger.rutgers.edu with ESMTP id ; Thu, 27 Jul 2000 06:26:44 -0400 Received: from kings-cross.london.uk.eu.org [::ffff:192.168.2.83] by tazenda.demon.co.uk with esmtp (Exim 3.11 #1 (Debian)) id 13HlER-0003vN-00; Thu, 27 Jul 2000 11:49:39 +0100 Received: from localhost ([::ffff:127.0.0.1] helo=tazenda.demon.co.uk ident=pb) by kings-cross.london.uk.eu.org with esmtp (Exim 3.12 #1 (Debian)) id 13HlBw-0002Yu-00; Thu, 27 Jul 2000 11:47:04 +0100 X-Mailer: exmh version 2.1.1 10/15/1999 (debian) To: "Jacky Lam" Cc: linux-arm@vger.rutgers.edu Subject: Re: A strange library In-Reply-To: Message from "Jacky Lam" of "Thu, 27 Jul 2000 15:00:36 +0800." <00cc01bff798$700c30c0$4e01a8c0@linux.emsoftltd.com> References: <00cc01bff798$700c30c0$4e01a8c0@linux.emsoftltd.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 27 Jul 2000 11:47:03 +0100 From: Philip Blundell Message-Id: Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu > "Kernel panic: Unknown data abort code 4194304 [pc=020014e8, >*pc=e14192b0] LR=0x014e8" Looks like your version of the kernel doesn't handle aborting halfword instructions. I think this was only recently added. p. unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Thu Jul 27 12:06:58 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13HlVC-0003Ja-00 for linux-arm-archive@lists.arm.linux.org.uk; Thu, 27 Jul 2000 12:06:58 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 2ACDF1616B; Thu, 27 Jul 2000 13:06:59 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Thu, 27 Jul 2000 06:45:11 -0400 Received: by vger.rutgers.edu id ; Thu, 27 Jul 2000 06:45:04 -0400 Received: from imail.cyberec.com ([202.60.252.12]:3454 "EHLO imail.cyberec.com") by vger.rutgers.edu with ESMTP id ; Thu, 27 Jul 2000 06:44:51 -0400 Received: from linux (ip-251-228.cyberec.com [203.85.251.228]) by imail.cyberec.com (8.9.3/8.8.7) with SMTP id TAA28376; Thu, 27 Jul 2000 19:11:47 +0800 Message-ID: <011601bff7bb$114765a0$4e01a8c0@linux.emsoftltd.com> From: "Jacky Lam" To: "Philip Blundell" Cc: Subject: Re: A strange library Date: Thu, 27 Jul 2000 19:08:30 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.1 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Dear Philip, The Thumb instruction set? If I have to overcome this problem(btw, can arm linux support thumb instruction?), what should I do? Upgrade the compiler and kernel? I have tried before. But it is too complicated to collect all the necessary patches.... Where can I find a complete instruction and patches to do this? Thanks very much. Jacky Lam -----Original Message----- From: Philip Blundell To: Jacky Lam Cc: linux-arm@vger.rutgers.edu Date: Thursday, July 27, 2000 6:44 PM Subject: Re: A strange library >> "Kernel panic: Unknown data abort code 4194304 [pc=020014e8, >>*pc=e14192b0] LR=0x014e8" > >Looks like your version of the kernel doesn't handle aborting halfword >instructions. I think this was only recently added. > >p. > > > >unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu >++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ >++ kernel-related discussions. ++ > unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Thu Jul 27 12:26:36 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13HloB-0003b2-00 for linux-arm-archive@lists.arm.linux.org.uk; Thu, 27 Jul 2000 12:26:36 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 12E7016397; Thu, 27 Jul 2000 13:21:16 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Thu, 27 Jul 2000 06:56:40 -0400 Received: by vger.rutgers.edu id ; Thu, 27 Jul 2000 06:55:48 -0400 Received: from tazenda.demon.co.uk ([158.152.220.239]:4755 "EHLO tazenda.demon.co.uk") by vger.rutgers.edu with ESMTP id ; Thu, 27 Jul 2000 06:54:56 -0400 Received: from kings-cross.london.uk.eu.org [::ffff:192.168.2.83] by tazenda.demon.co.uk with esmtp (Exim 3.11 #1 (Debian)) id 13HlgK-00043V-00; Thu, 27 Jul 2000 12:18:28 +0100 Received: from localhost ([::ffff:127.0.0.1] helo=tazenda.demon.co.uk ident=pb) by kings-cross.london.uk.eu.org with esmtp (Exim 3.12 #1 (Debian)) id 13Hldp-0002q4-00; Thu, 27 Jul 2000 12:15:53 +0100 X-Mailer: exmh version 2.1.1 10/15/1999 (debian) To: "Jacky Lam" Cc: linux-arm@vger.rutgers.edu Subject: Re: A strange library In-Reply-To: Message from "Jacky Lam" of "Thu, 27 Jul 2000 19:08:30 +0800." <011601bff7bb$114765a0$4e01a8c0@linux.emsoftltd.com> References: <011601bff7bb$114765a0$4e01a8c0@linux.emsoftltd.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 27 Jul 2000 12:15:53 +0100 From: Philip Blundell Message-Id: Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu > The Thumb instruction set? No, this isn't Thumb. The problem is that, on ARM7 based cores, if an instruction aborts the kernel needs to decode the faulting instruction to work out what to do. It can handle most common cases, but not absolutely every instruction that can fault. (For example, SWP still wasn't supported last time I looked; there have been a few reports of people having programs die because of this, too.) The particular instruction you are having trouble with is LDRH, which is just an ARM 16-bit load. If you upgrade to the latest kernel I think it will work. >(btw, can arm linux support thumb instruction?), People have done some work on this in the past but I don't know what the current status is. As far as I know the kernel doesn't deal with Thumb yet. p. unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Thu Jul 27 13:04:57 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13HmPJ-00048k-00 for linux-arm-archive@lists.arm.linux.org.uk; Thu, 27 Jul 2000 13:04:57 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 9D518163DD; Thu, 27 Jul 2000 13:58:58 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Thu, 27 Jul 2000 07:38:20 -0400 Received: by vger.rutgers.edu id ; Thu, 27 Jul 2000 07:37:22 -0400 Received: from ns0.utdallas.edu ([129.110.10.1]:40385 "HELO ns0.utdallas.edu") by vger.rutgers.edu with SMTP id ; Thu, 27 Jul 2000 07:36:11 -0400 Received: from apache.utdallas.edu (apache.utdallas.edu [129.110.16.9]) by ns0.utdallas.edu (Postfix) with ESMTP id 372D81A0003; Thu, 27 Jul 2000 06:54:18 -0500 (CDT) Received: from localhost (vasantr@localhost) by apache.utdallas.edu (8.9.1/8.9.1) with ESMTP id GAA03461; Thu, 27 Jul 2000 06:54:49 -0500 (CDT) X-Authentication-Warning: apache.utdallas.edu: vasantr owned process doing -bs Date: Thu, 27 Jul 2000 06:54:49 -0500 (CDT) From: Vasant Ramasubramanian To: sa1100-linux@pa.dec.com, linux-arm@vger.rutgers.edu, handhelds@handhelds.org Subject: GDB stubs for ARM Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu I've asked around but no one so far seems to have complete GDB stubs for ARM, or am I mistaken? (StrongARM hopefully). I know of the Arnold bootloader, but honestly that code is hard to follow since it links in so much functionality... Suggestions? Thanks, Vasant. unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Thu Jul 27 13:06:02 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13HmQM-0004AO-00 for linux-arm-archive@lists.arm.linux.org.uk; Thu, 27 Jul 2000 13:06:02 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 616D6163E3; Thu, 27 Jul 2000 14:01:33 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Thu, 27 Jul 2000 07:41:49 -0400 Received: by vger.rutgers.edu id ; Thu, 27 Jul 2000 07:41:35 -0400 Received: from cvsftp.cotw.com ([208.242.241.39]:1692 "EHLO cvsftp.cotw.com") by vger.rutgers.edu with ESMTP id ; Thu, 27 Jul 2000 07:41:14 -0400 Received: from cotw.com (IDENT:samcconn@ptecdev2.ptec.com [192.168.10.4]) by cvsftp.cotw.com (8.9.3/8.9.3) with ESMTP id GAA09251; Thu, 27 Jul 2000 06:59:22 -0500 Message-ID: <398024D6.E5EE96B3@cotw.com> Date: Thu, 27 Jul 2000 07:02:30 -0500 From: S A McConnell Reply-To: samcconn@cotw.com X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.14 i686) X-Accept-Language: en MIME-Version: 1.0 Cc: Jacky Lam , linux-arm@vger.rutgers.edu Subject: Re: A strange library References: <011601bff7bb$114765a0$4e01a8c0@linux.emsoftltd.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: unlisted-recipients: ;(no To-header on input) Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Cliff Brake cbrake@accelent.com supplied a patch for half-word support. RMK included it in his latest patch. SAM unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Thu Jul 27 15:27:02 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13Hoco-0006Mm-00 for linux-arm-archive@lists.arm.linux.org.uk; Thu, 27 Jul 2000 15:27:02 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 6BC1D16200; Thu, 27 Jul 2000 16:27:01 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Thu, 27 Jul 2000 10:07:29 -0400 Received: by vger.rutgers.edu id ; Thu, 27 Jul 2000 10:07:20 -0400 Received: from [12.38.17.9] ([12.38.17.9]:3670 "EHLO mail.aeptec.com") by vger.rutgers.edu with ESMTP id ; Thu, 27 Jul 2000 10:07:09 -0400 Received: by MAIL with Internet Mail Service (5.5.2650.21) id ; Thu, 27 Jul 2000 10:16:09 -0400 Message-ID: <32CC5B62AF0BD2119E4C00A0C9663E221F3BF5@MAIL> From: "Sun, Lei" To: "'linux-arm@vger.rutgers.edu'" Subject: need help in bug fixing! Date: Thu, 27 Jul 2000 10:16:06 -0400 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@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Hi all: I am tring to investigate the "telnet session stucks " bug in SA1110 Assabet for kernel 2.4.0-test2(in test4 version, things getting worse, even ping don't work on stand along assabet). I wrote a small packet monitoring progrm which use the packet socket and can read the whole raw packet from my arm target eth0 device, and print out the source IP address, destination IP, source port and destinaion port and the packet content. when I open this program on my arm target(IP 192.168.200.72) and try to telnet from 192.168.200.70, the packet monitoring program output looks like this: source IP: 192.168.40.73 source port: 23 dest IP: 192.168.200.70 dest port: 1078 ... source IP: 192.168.40.172 source port: 23 dest IP: 192.168.200.70 dest port: 1078 .... I tested this program in other linux machine, it works good. Noted that the source IP address doesn't exist at all, looks like the last two bytes IP address are mixed. so the reply packet are being send nowhere. so the telnet session will hang there because it couldn't receive further packet. Can anybody tell me what can cause this problem, ethernet driver ? or IP suite implementation? Thank you! Lei Sun unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Thu Jul 27 16:00:08 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13Hp8q-0006xG-00 for linux-arm-archive@lists.arm.linux.org.uk; Thu, 27 Jul 2000 16:00:08 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id AC92916419; Thu, 27 Jul 2000 16:53:40 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Thu, 27 Jul 2000 10:27:33 -0400 Received: by vger.rutgers.edu id ; Thu, 27 Jul 2000 10:26:59 -0400 Received: from p49-cordelia-gui.tch.enablis.net ([212.250.233.49]:2256 "EHLO caramon.arm.linux.org.uk") by vger.rutgers.edu with ESMTP id ; Thu, 27 Jul 2000 10:26:18 -0400 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 PAA12332; Thu, 27 Jul 2000 15:44:51 +0100 Received: (from linux@localhost) by flint.arm.linux.org.uk (8.9.3/8.9.3) id PAA14867; Thu, 27 Jul 2000 15:43:05 +0100 From: Russell King - ARM Linux Admin Message-Id: <200007271443.PAA14867@flint.arm.linux.org.uk> Subject: Re: need help in bug fixing! To: Sun@AEPTEC.COM (Sun, Lei) Date: Thu, 27 Jul 2000 15:43:05 +0100 (BST) Cc: linux-arm@vger.rutgers.edu ('linux-arm@vger.rutgers.edu') In-Reply-To: <32CC5B62AF0BD2119E4C00A0C9663E221F3BF5@MAIL> from "Sun, Lei" at Jul 27, 2000 10:16:06 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@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Sun, Lei writes: > I wrote a small packet monitoring progrm which use the packet socket and > can read the whole raw packet from my arm target eth0 device, and print out > the source IP address, destination IP, source port and destinaion port and > the packet content. You might want to look at the program called "tcpdump". It does exactly the same, but does a lot more interpretation. > when I open this program on my arm target(IP 192.168.200.72) and try to BTW, you don't "open" programs. You "run" them. "Open" is a microsoft-ism. > telnet from 192.168.200.70, the packet monitoring program output looks > like this: > > source IP: 192.168.40.73 source port: 23 > dest IP: 192.168.200.70 dest port: 1078 > ... > source IP: 192.168.40.172 source port: 23 > dest IP: 192.168.200.70 dest port: 1078 > .... Hmm, not sure - I'd like to see the output of tcpdump -s 256 -x to be sure. _____ |_____| ------------------------------------------------- ---+---+- | | Russell King linux@arm.linux.org.uk --- --- | | | | http://www.arm.linux.org.uk/ / / | | +-+-+ --- -+- / | THE developer of ARM Linux |+| /|\ / | | | --- | +-+-+ ------------------------------------------------- /\\\ | unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Thu Jul 27 16:48:29 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13Hptd-0007lF-00 for linux-arm-archive@lists.arm.linux.org.uk; Thu, 27 Jul 2000 16:48:29 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id C7B351640E; Thu, 27 Jul 2000 17:40:12 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Thu, 27 Jul 2000 11:19:48 -0400 Received: by vger.rutgers.edu id ; Thu, 27 Jul 2000 11:18:26 -0400 Received: from purple.alumni.cuhk.edu.hk ([202.45.188.17]:63209 "EHLO purple.alumni.cuhk.edu.hk") by vger.rutgers.edu with ESMTP id ; Thu, 27 Jul 2000 11:17:18 -0400 Received: from ismart.net (ppp078.alumni.cuhk.edu.hk [202.45.188.78]) by purple.alumni.cuhk.edu.hk (8.9.3/8.9.3) with ESMTP id XAA06678; Thu, 27 Jul 2000 23:34:46 +0800 (HKT) Message-ID: <3980577B.A415AB0A@ismart.net> Date: Thu, 27 Jul 2000 23:38:35 +0800 From: Yin X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: Philip Blundell Cc: linux-arm@vger.rutgers.edu Subject: Re: A strange library References: <00cc01bff798$700c30c0$4e01a8c0@linux.emsoftltd.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Dear Philip, Oh...I see....As I think that all the instructions on ARM is 32bit long, except THUMB. I am quite new in such low level programming. Anyway, I have find a way to go. But now, could you tell me how can I collect all packages so as to upgrade my development tools and kernel? Thanks very much. Yours, Jacky Lam Philip Blundell wrote: > > > "Kernel panic: Unknown data abort code 4194304 [pc=020014e8, > >*pc=e14192b0] LR=0x014e8" > > Looks like your version of the kernel doesn't handle aborting halfword > instructions. I think this was only recently added. > > p. > > unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu > ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ > ++ kernel-related discussions. ++ unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Thu Jul 27 21:18:37 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13Hu73-0004vw-00 for linux-arm-archive@lists.arm.linux.org.uk; Thu, 27 Jul 2000 21:18:37 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id F06E516653; Thu, 27 Jul 2000 22:13:44 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Thu, 27 Jul 2000 15:51:18 -0400 Received: by vger.rutgers.edu id ; Thu, 27 Jul 2000 15:48:40 -0400 Received: from tazenda.demon.co.uk ([158.152.220.239]:1201 "EHLO tazenda.demon.co.uk") by vger.rutgers.edu with ESMTP id ; Thu, 27 Jul 2000 15:47:52 -0400 Received: from kings-cross.london.uk.eu.org [::ffff:192.168.2.83] by tazenda.demon.co.uk with esmtp (Exim 3.11 #1 (Debian)) id 13Htyw-00058p-00; Thu, 27 Jul 2000 21:10:14 +0100 Received: from localhost ([::ffff:127.0.0.1] helo=tazenda.demon.co.uk ident=pb) by kings-cross.london.uk.eu.org with esmtp (Exim 3.12 #1 (Debian)) id 13HtwF-0000uW-00; Thu, 27 Jul 2000 21:07:27 +0100 X-Mailer: exmh version 2.1.1 10/15/1999 (debian) To: Yin Cc: linux-arm@vger.rutgers.edu Subject: Re: A strange library In-Reply-To: Message from Yin of "Thu, 27 Jul 2000 23:38:35 +0800." <3980577B.A415AB0A@ismart.net> References: <00cc01bff798$700c30c0$4e01a8c0@linux.emsoftltd.com> <3980577B.A415AB0A@ismart.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 27 Jul 2000 21:07:27 +0100 From: Philip Blundell Message-Id: Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu >Anyway, I have find a way to go. But now, could you tell me how can I >collect all packages so as to upgrade my development tools and kernel? For development tools, see Scott Bambrough's web page: http://www.netwinder.org/~scottb/notes/ For the kernel, what you need depends on your platform. You should ask the experts on the linux-arm-kernel list if you don't know what to get. p. unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Fri Jul 28 09:24:03 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13I5R5-00009e-00 for linux-arm-archive@lists.arm.linux.org.uk; Fri, 28 Jul 2000 09:24:03 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 81AD8165C4; Fri, 28 Jul 2000 09:32:50 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Fri, 28 Jul 2000 03:13:19 -0400 Received: by vger.rutgers.edu id ; Fri, 28 Jul 2000 03:13:11 -0400 Received: from f210.law8.hotmail.com ([216.33.241.210]:3370 "HELO hotmail.com") by vger.rutgers.edu with SMTP id ; Fri, 28 Jul 2000 03:12:52 -0400 Received: (qmail 3327 invoked by uid 0); 28 Jul 2000 07:31:45 -0000 Message-ID: <20000728073145.3326.qmail@hotmail.com> Received: from 210.94.6.83 by www.hotmail.com with HTTP; Fri, 28 Jul 2000 00:31:45 PDT X-Originating-IP: [210.94.6.83] From: "Jooyeon Cho" To: linux-arm@vger.rutgers.edu Subject: Compiling uclinux for arm7 Date: Fri, 28 Jul 2000 16:31:45 KST Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Hi Is there anybody who are willing to help me compiling uclinux kernel? arm system is aplio-trio and arm cpu is arm6/7. Final error message is as follows. make[1]: Entering directory `/data/uclinux/cross/linux/arch/armnommu/boot' make[2]: Entering directory `/data/uclinux/cross/linux/arch/armnommu/boot/compressed' ./xtract /data/uclinux/cross/linux/linux | gzip -9 | ./piggyback > piggy.o Non-GCC header of 'system' compressed size 20 arm-uclinux-ld -Ttext 0x2000 -o linux head.o misc.o piggy.o piggy.o: file not recognized: file format not recognized make[2]: [linux] Error 1 Thanks in advance. Regards Joe ________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Fri Jul 28 11:42:34 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13I7b8-0002NY-00 for linux-arm-archive@lists.arm.linux.org.uk; Fri, 28 Jul 2000 11:42:34 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id ACD76167FC; Fri, 28 Jul 2000 11:37:33 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Fri, 28 Jul 2000 05:16:32 -0400 Received: by vger.rutgers.edu id ; Fri, 28 Jul 2000 05:14:44 -0400 Received: from p09-robin-gui.tch.enablis.net ([194.168.180.69]:3333 "EHLO caramon.arm.linux.org.uk") by vger.rutgers.edu with ESMTP id ; Fri, 28 Jul 2000 05:14:11 -0400 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 KAA16582; Fri, 28 Jul 2000 10:33:07 +0100 Received: (from linux@localhost) by flint.arm.linux.org.uk (8.9.3/8.9.3) id KAA25373; Fri, 28 Jul 2000 10:31:19 +0100 From: Russell King - ARM Linux Admin Message-Id: <200007280931.KAA25373@flint.arm.linux.org.uk> Subject: Re: Compiling uclinux for arm7 To: jooyeon_cho@hotmail.com (Jooyeon Cho) Date: Fri, 28 Jul 2000 10:31:19 +0100 (BST) Cc: linux-arm@vger.rutgers.edu In-Reply-To: <20000728073145.3326.qmail@hotmail.com> from "Jooyeon Cho" at Jul 28, 2000 04:31:45 PM X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Jooyeon Cho writes: > make[1]: Entering directory `/data/uclinux/cross/linux/arch/armnommu/boot' > make[2]: Entering directory > `/data/uclinux/cross/linux/arch/armnommu/boot/compressed' > ./xtract /data/uclinux/cross/linux/linux | gzip -9 | ./piggyback > piggy.o > Non-GCC header of 'system' > compressed size 20 > arm-uclinux-ld -Ttext 0x2000 -o linux head.o misc.o piggy.o > piggy.o: file not recognized: file format not recognized > make[2]: [linux] Error 1 Looks like something has gone spectacularly wrong here - piggy.o is only 20 bytes, and therefore not a valid ELF file. I'd guess that ./xtract doesn't know about ELF (which is why we don't use it in the mainstream kernels anymore, but prefer to use objcopy and ld magic). I guess tha the armnommu people need to fix that up when using ELF. _____ |_____| ------------------------------------------------- ---+---+- | | Russell King linux@arm.linux.org.uk --- --- | | | | http://www.arm.linux.org.uk/ / / | | +-+-+ --- -+- / | THE developer of ARM Linux |+| /|\ / | | | --- | +-+-+ ------------------------------------------------- /\\\ | unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Fri Jul 28 11:59:37 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13I7rd-0002c0-00 for linux-arm-archive@lists.arm.linux.org.uk; Fri, 28 Jul 2000 11:59:37 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 924D7162E2; Fri, 28 Jul 2000 12:46:07 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Fri, 28 Jul 2000 06:26:34 -0400 Received: by vger.rutgers.edu id ; Fri, 28 Jul 2000 06:26:15 -0400 Received: from smtp2.fr.uu.net ([194.98.0.8]:41544 "HELO mail.fr.uu.net") by vger.rutgers.edu with SMTP id ; Fri, 28 Jul 2000 06:25:54 -0400 Received: from CarlCox.iway.fr (carlcox.iway.fr [194.98.0.128]) by mail.fr.uu.net (Postfix) with ESMTP id C026031C46; Fri, 28 Jul 2000 12:44:39 +0200 (MET DST) Received: from vad ([194.98.253.47]) by CarlCox.iway.fr (8.9.3/8.8.7) with SMTP id MAA15100004; Fri, 28 Jul 2000 12:44:44 +0200 (METDST) From: "Vadim Lebedev" To: "Jooyeon Cho" , "uCLinux" , "Linux-Arm" Subject: RE: Compiling uclinux for arm7 Date: Fri, 28 Jul 2000 12:36:32 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <20000728073145.3326.qmail@hotmail.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu I've just added followig chaptre to the ucLinux/ARM FAQ at http://aplionet.aplio.fr/uclinux 5. How does the system boot? The boot process for AEB target of ucLinux is uses bootrecod stored at adress 0x4040 in the flash memory and assumes that the flash contains FTL formatted disk image starting somewhere afterx 0xffff The boot recod contains boot items. Each boot item contains the list of sectors on FTL volume which decribes the file to load into ram , program start address and some optioanl data. The first boot items so decribes the linux_boot program (the sorce of the program is in AplioTRIO/common/ftl directory) . linux_boot is compiled to be position indepnedent. So the IPL code (which is activated upon reset at address 0x0000) loads the linux_boot program into ram and gives it the control. The linux_boot loads in turn loads the file Described by the second boot item (BTW the file can be gzip-compressed in this case it is uzipped during load) prepares the command line for the kernel and jumps to the kernel start address. In the AplioTRIO/common/ftl directory resides a source of the simpl.y makeboot utility which given name of the linux_boot and kerenl files prepares the bootrecord and Optionally writes it to the specified address in the flash. One more thing: when make command is run to build the kernel by default it builds 3 files: · linux – elf emage of the kernel, · linux.bin – absolute image of the kernel · linux.bin.gz – copressed version of above Enjoy ----------------------------------------- Vadim Lebedev Chief Software Engineer Aplio SA. mail:vlebedev@aplio.fr http://www.aplio.com ------------------------------------------ |-----Original Message----- |From: owner-linux-arm@vger.rutgers.edu |[mailto:owner-linux-arm@vger.rutgers.edu]On Behalf Of Jooyeon Cho |Sent: vendredi 28 juillet 2000 09:32 |To: linux-arm@vger.rutgers.edu |Subject: Compiling uclinux for arm7 | | |Hi | |Is there anybody who are willing to help me compiling uclinux kernel? |arm system is aplio-trio and arm cpu is arm6/7. |Final error message is as follows. | |make[1]: Entering directory `/data/uclinux/cross/linux/arch/armnommu/boot' |make[2]: Entering directory |`/data/uclinux/cross/linux/arch/armnommu/boot/compressed' |./xtract /data/uclinux/cross/linux/linux | gzip -9 | ./piggyback > piggy.o |Non-GCC header of 'system' |compressed size 20 |arm-uclinux-ld -Ttext 0x2000 -o linux head.o misc.o piggy.o |piggy.o: file not recognized: file format not recognized |make[2]: [linux] Error 1 | |Thanks in advance. | |Regards |Joe |________________________________________________________________________ |Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com | | |unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu |++ Please use linux-arm-kernel@lists.arm.linux.org.uk for | ++ |++ kernel-related discussions. | ++ | unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Sat Jul 29 05:31:20 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13IOHQ-00032H-00 for linux-arm-archive@lists.arm.linux.org.uk; Sat, 29 Jul 2000 05:31:20 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 4FF3C16A33; Sat, 29 Jul 2000 05:55:21 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Fri, 28 Jul 2000 23:35:29 -0400 Received: by vger.rutgers.edu id ; Fri, 28 Jul 2000 23:35:21 -0400 Received: from violet.csa.iisc.ernet.in ([144.16.67.198]:1110 "EHLO violet.csa.iisc.ernet.in") by vger.rutgers.edu with ESMTP id ; Fri, 28 Jul 2000 23:35:09 -0400 Received: from localhost (alex@localhost) by violet.csa.iisc.ernet.in (8.9.3/8.9.3) with ESMTP id JAA03165; Sun, 13 Aug 2000 09:51:15 +0530 Date: Sun, 13 Aug 2000 09:51:15 +0530 (IST) From: Alex M Alex To: linux@handhelds.org, linux-arm@vger.rutgers.edu, nanogui@linuxhacker.org Cc: linuxce-devel@linuxce.org, sa1100-linux@pa.dec.com Subject: Perl port Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Hi all, Did any one ported perl to Linux CE. regards alex unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Sat Jul 29 05:35:31 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13IOLT-00034B-00 for linux-arm-archive@lists.arm.linux.org.uk; Sat, 29 Jul 2000 05:35:31 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 77AD616A81; Sat, 29 Jul 2000 06:01:13 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Fri, 28 Jul 2000 23:41:22 -0400 Received: by vger.rutgers.edu id ; Fri, 28 Jul 2000 23:41:05 -0400 Received: from ns4.Sony.CO.JP ([202.238.80.4]:1892 "EHLO ns4.sony.co.jp") by vger.rutgers.edu with ESMTP id ; Fri, 28 Jul 2000 23:40:43 -0400 Received: from mail2.sony.co.jp (gatekeeper7.Sony.CO.JP [202.238.80.21]) by ns4.sony.co.jp (R8) with ESMTP id MAA64425; Sat, 29 Jul 2000 12:59:38 +0900 (JST) Received: from smail1.sm.sony.co.jp (smail1.sm.sony.co.jp [43.11.253.1]) by mail2.sony.co.jp (R8) with ESMTP id MAA28003; Sat, 29 Jul 2000 12:59:50 +0900 (JST) Received: from email.sm.sony.co.jp (email.sm.sony.co.jp [43.11.253.2]) by smail1.sm.sony.co.jp (8.8.8/3.6W) with ESMTP id MAA27775; Sat, 29 Jul 2000 12:58:47 +0900 (JST) Received: from sm.sony.co.jp (kei@gaia.sm.sony.co.jp [43.11.132.48]) by email.sm.sony.co.jp (8.8.8/3.6W) with ESMTP id MAA24795; Sat, 29 Jul 2000 12:54:43 +0900 (JST) Message-Id: <200007290354.MAA24795@email.sm.sony.co.jp> To: Alex M Alex Cc: linux@handhelds.org, linux-arm@vger.rutgers.edu, nanogui@linuxhacker.org, linuxce-devel@linuxce.org, sa1100-linux@pa.dec.com Subject: Re: [Linux] Perl port In-reply-to: Your message of Sun, 13 Aug 2000 09:51:15 +0530. Date: Sat, 29 Jul 2000 12:59:36 +0900 From: Hiroshi Kawashima Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Hi. > Hi all, > Did any one ported perl to > Linux CE. Perl 5.00503 is working on my hard-float userland. You can access all my hard-float RPMS from: http://www.peanuts.gr.jp/~kei/Hard-Float/ ---- Kawashima unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 31 08:21:30 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13J9tB-0004Nt-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 31 Jul 2000 08:21:29 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 5C29515D88; Mon, 31 Jul 2000 09:21:37 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Mon, 31 Jul 2000 03:01:04 -0400 Received: by vger.rutgers.edu id ; Mon, 31 Jul 2000 03:00:56 -0400 Received: from gate2.mn.man.de ([151.136.100.137]:56515 "EHLO gate2.mn.man.de") by vger.rutgers.edu with ESMTP id convert rfc822-to-8bit; Mon, 31 Jul 2000 03:00:46 -0400 Received: by gate2.mn.man.de (8.9.0/8.9.0) id JAA23886; Mon, 31 Jul 2000 09:20:18 +0200 (CEST) From: Martin_Doering@mn.man.de Received: (from smtp-gw@localhost) by gate2.mn.man.de (MSCAN) id 3/gate2.mn.man.de/smtp-gw/mscan; Mon Jul 31 09:20:17 2000 Cc: alex@violet.csa.iisc.ernet.in, linux@handhelds.org, linux-arm@vger.rutgers.edu, linuxce-devel@linuxce.org, nanogui@linuxhacker.org, sa1100-linux@pa.dec.com Content-transfer-encoding: 8BIT Content-type: text/plain; charset="iso-8859-1" Date: Mon, 31 Jul 2000 09:14:02 +0200 Message-id: Mime-version: 1.0 Subject: Antwort: Re: [Linux] Perl port To: Hiroshi Kawashima X-mailer: Lotus Notes Version 5.0.2c (Intl) 08 Februar 2000 X-mimetrack: Serialize by Router on MMMAIL001/SRV/MAN_Nutzfahrzeuge(Release 5.0.4 |June 8, 2000) at 07/31/2000 09:14:03 AM, Serialize complete at 07/31/2000 09:14:03 AM, Itemize by SMTP Server on MMHUB001/SRV/MAN_Nutzfahrzeuge(Release 5.0.4 |June 8, 2000) at 07/31/2000 09:21:16 AM, Serialize by Router on MMHUB001/SRV/MAN_Nutzfahrzeuge(Release 5.0.4 |June 8, 2000) at 07/31/2000 09:21:19 AM, Serialize complete at 07/31/2000 09:21:19 AM Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu What means hard-float? What a project is this? Regards, -------------------------------------------------------------------------------------------------------- Martin Döring, Systemtechnik (IDT) MAN Nutzfahrzeuge AG Dachauerstraße 667 D-80995 München Tel.: +49(0)89 / 1580 - 1199 Fax: +49(0)89 / 1580 - 91-1199 E-Mail: Martin_Doering@mn.man.de unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 31 11:00:17 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13JCMq-0006qf-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 31 Jul 2000 11:00:17 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 210F815F23; Mon, 31 Jul 2000 11:59:13 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Mon, 31 Jul 2000 05:38:00 -0400 Received: by vger.rutgers.edu id ; Mon, 31 Jul 2000 05:37:33 -0400 Received: from duteinh.et.tudelft.nl ([130.161.42.1]:2598 "EHLO duteinh.et.tudelft.nl") by vger.rutgers.edu with ESMTP id ; Mon, 31 Jul 2000 05:36:41 -0400 Received: from dutein75 by duteinh.et.tudelft.nl (8.9.3/BB-2.0) id LAA23955; Mon, 31 Jul 2000 11:55:42 +0200 (MET DST) Message-Id: <200007310955.LAA23955@duteinh.et.tudelft.nl> From: Erik Mouw To: Martin_Doering@mn.man.de Cc: alex@violet.csa.iisc.ernet.in, linux@handhelds.org, linux-arm@vger.rutgers.edu, linuxce-devel@linuxce.org, nanogui@linuxhacker.org, sa1100-linux@pa.dec.com Subject: Re: Antwort: Re: [Linux] Perl port In-Reply-To: Organization: Eric conspiracy secret labs Date: Mon 31 Jul 2000 11:55:41 +0100 (MDT) 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.2devel - with PGP support, PGP engine version 0.5 (IRIX64) X-Mailerorigin: http://www.fsai.fh-trier.de/~schmitzj/Xclasses/XCmail/ X-Eric-Conspiracy: There is no conspiracy! X-Loop: erik@it.et.tudelft.nl MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu On Mon, 31 Jul 2000 09:14:02 +0200, Martin_Doering@mn.man.de wrote: > What means hard-float? What a project is this? Hard-float means that you're using the floating point unit in the CPU (or emulate them in the OS). Soft-float means that you're emulating the floating point instructions in a software library. I can imagine that you can't follow this, I think you're subscribed to the nanogui list and this question is waaaaaaay off-topic for that list. People, _please_ don't cross post, but post your questions to the relevant mailing list. Erik -- LART. 250 MIPS under one Watt. Free hardware design files. http://www.lart.tudelft.nl/ unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 31 11:14:25 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13JCaW-00073h-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 31 Jul 2000 11:14:24 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id D8AC615F40; Mon, 31 Jul 2000 12:04:56 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Mon, 31 Jul 2000 05:43:50 -0400 Received: by vger.rutgers.edu id ; Mon, 31 Jul 2000 05:29:24 -0400 Received: from violet.csa.iisc.ernet.in ([144.16.67.198]:1737 "EHLO violet.csa.iisc.ernet.in") by vger.rutgers.edu with ESMTP id ; Mon, 31 Jul 2000 05:28:50 -0400 Received: from localhost (alex@localhost) by violet.csa.iisc.ernet.in (8.9.3/8.9.3) with ESMTP id PAA09640; Tue, 15 Aug 2000 15:45:22 +0530 Date: Tue, 15 Aug 2000 15:45:21 +0530 (IST) From: Alex M Alex To: Martin_Doering@mn.man.de Cc: linux@handhelds.org, linux-arm@vger.rutgers.edu, linuxce-devel@linuxce.org, nanogui@linuxhacker.org, sa1100-linux@pa.dec.com Subject: Has anybody ported perl to SA1110 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu Hi all I like to know any one has ported perl to strong arm . regards alex unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++ From owner-linux-arm-outgoing@vger.rutgers.edu Mon Jul 31 20:41:33 2000 Received: from [193.189.224.13] (helo=source.rfc822.org ident=postfix) by www.linux.org.uk with esmtp (Exim 3.13 #1) id 13JLRM-0000GN-00 for linux-arm-archive@lists.arm.linux.org.uk; Mon, 31 Jul 2000 20:41:32 +0100 Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by source.rfc822.org (Postfix) with ESMTP id 3B8F91620D; Mon, 31 Jul 2000 21:33:52 +0200 (CEST) Received: (majordomo@vger.rutgers.edu) by vger.rutgers.edu via listexpand id ; Mon, 31 Jul 2000 15:12:42 -0400 Received: by vger.rutgers.edu id ; Mon, 31 Jul 2000 15:11:11 -0400 Received: from mail-blue.research.att.com ([135.207.30.102]:4690 "HELO mail-blue.research.att.com") by vger.rutgers.edu with SMTP id ; Mon, 31 Jul 2000 15:10:28 -0400 Received: from hermes.research.att.com (hermes.research.att.com [135.207.16.38]) by mail-blue.research.att.com (Postfix) with ESMTP id 819934CE11 for ; Mon, 31 Jul 2000 15:30:34 -0400 (EDT) Received: from research.att.com (wave-137.research.att.com [135.207.10.137]) by hermes.research.att.com (8.8.7/8.8.7) with ESMTP id PAA11264 for ; Mon, 31 Jul 2000 15:29:11 -0400 (EDT) Message-ID: <3985D396.F1A823C3@research.att.com> Date: Mon, 31 Jul 2000 15:29:26 -0400 From: Jack Chang Organization: AT&T Labs- Research X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.15-4mdksecure i686) X-Accept-Language: en MIME-Version: 1.0 To: "'linux-arm@vger.rutgers.edu'" Subject: Re: LCD display on Assabet Content-Type: text/plain; charset=big5 Content-Transfer-Encoding: base64 Sender: owner-linux-arm@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu SGksIEkgd29uZGVyIHdoeSB0aGUgTENEIGRpc3BsYXkgKHRoZSBsb2dvKSB0dXJucyBvZmYg IGZldyBtaW51dGVzIGFmdGVyDQprZXJuZWwgYm9vdHMuIElzIHRoZXJlIHNvbWUgcG93ZXIg bWFuYWdlbWVudCBjYXVzZXMgdGhhdD8NCldoaWNoIGZpbGUgSSBzaG91bGQgbW9kaWZ5IHRv IGtlZXAgaW4gb24gYWxsIHRoZSB0aW1lPyBUaHgNCg0KLS0NCkphY2sgVC4gQ2hhbmcNCg0K DQo= unsubscribe: body of `unsubscribe linux-arm' to majordomo@vger.rutgers.edu ++ Please use linux-arm-kernel@lists.arm.linux.org.uk for ++ ++ kernel-related discussions. ++