From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16485 invoked by alias); 23 Dec 2002 16:08:03 -0000 Mailing-List: contact sid-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: sid-owner@sources.redhat.com Received: (qmail 16468 invoked from network); 23 Dec 2002 16:08:02 -0000 Received: from unknown (HELO jensun147.jennic.com) (213.143.5.74) by 209.249.29.67 with SMTP; 23 Dec 2002 16:08:02 -0000 Received: from JENPC112 (jenpc112.jennic.com [99.99.98.112]) by jensun147.jennic.com (8.9.3+Sun/8.9.3) with SMTP id QAA01299; Mon, 23 Dec 2002 16:04:53 GMT From: "Robert Cragie" To: "Frank Ch. Eigler" , Subject: RE: hw-cpu-openrisc Date: Mon, 23 Dec 2002 08:08:00 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 X-SW-Source: 2002-q4/txt/msg00053.txt.bz2 I'm having a go at piecing the jigsaw together... > The work includes ... > - adding sid configury for the openrisc target; see > sid/config/sidtargets.m4; Will something like this be sufficient? Index: sidtargets.m4 =================================================================== RCS file: /cvs/src/src/sid/config/sidtargets.m4,v retrieving revision 1.4 diff -r1.4 sidtargets.m4 43a44 > sidtarget_openrisc=$sidtarget_default 56a58 > openrisc*) sidtarget_openrisc=1 ;; 70a73 > ${sidtarget_openrisc}) ;; 104a108,112 > > AC_MSG_CHECKING(OpenRISC family support) > AC_SUBST(sidtarget_openrisc) > AM_CONDITIONAL(SIDTARGET_OPENRISC,[test "x$sidtarget_openrisc" = x1]) > AC_MSG_RESULT($sidtarget_openrisc)# > will need autoconf/automake runs throughout So how do I do this exactly? I don't know much about these utilities, I'm afraid. I did 'autoconf' and 'automake' at the top but it didn't seem to make much difference to any of the files. If I need to go and read up about these utilities before trying to do anything else, let me know :-) > - adding sid configuration file generator pieces to sid/bsp/configrun-sid Again, I think I can see what to do here, assuming I don't want any 'boards' just yet. Would something like this do? Index: configrun-sid.in =================================================================== RCS file: /cvs/src/src/sid/bsp/configrun-sid.in,v retrieving revision 1.34 diff -r1.34 configrun-sid.in 19a20 > "openrisc" => "hw-cpu-openrisc/d", 25a27 > "openrisc" => "-EB", 34a37 > "openrisc" => "sw-gloss-openrisc/libgloss", 43a47 > "openrisc" => "0x00000000,0x00800000", > - populating sid/component/cgen-cpu/openrisc, mostly with > cgen-generated files, > plus one or two hand-written ones; the m32r target is amongst > the simplest to > use as a base This is where I'm getting a little bit unstuck. Looking at the m32r subdirectory, I can see the m32r-decode.cxx etc. files which all say they are automatically generated by CGEN. But how did they get here? Are they created somewhere else by an additional step then copied in? Again, I can see in CGEN there are the sid-xxx.scm files which I presume are extra to the normal CGEN release - do these build the 'extra bits' needed for SID? There doesn't seem to be much about it in the documentation - how do you build this? I presume the additional hand-written files are needed to implement the sid interfaces. > - testing, perhaps as a dejagnu "baseboard" Not even close :-) I would really like to have a go at doing this, but I'm finding it hard going with lack of documentation at the SID level and a huge directory tree. Any more help would be really appreciated - even if it's to say 'get fully acquainted with the GNU way of doing things first'. Then at least I know what I'm up against. Robert Cragie, Design Engineer _______________________________________________________________ Jennic Ltd, Furnival Street, Sheffield, S1 4QT, UK http://www.jennic.com Tel: +44 (0) 114 281 2655 _______________________________________________________________