From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 952 invoked by alias); 3 Jun 2007 16:33:22 -0000 Received: (qmail 943 invoked by uid 22791); 3 Jun 2007 16:33:21 -0000 X-Spam-Check-By: sourceware.org Received: from nz-out-0506.google.com (HELO nz-out-0506.google.com) (64.233.162.227) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sun, 03 Jun 2007 16:33:19 +0000 Received: by nz-out-0506.google.com with SMTP id s1so677723nze for ; Sun, 03 Jun 2007 09:33:17 -0700 (PDT) Received: by 10.143.158.16 with SMTP id k16mr174712wfo.1180888397441; Sun, 03 Jun 2007 09:33:17 -0700 (PDT) Received: by 10.143.33.18 with HTTP; Sun, 3 Jun 2007 09:33:17 -0700 (PDT) Message-ID: <70d4f620706030933n543135f6i77f3c8acd9ee64c5@mail.gmail.com> Date: Sun, 03 Jun 2007 16:33:00 -0000 From: "Mike Sweeney" To: "Gary Thomas" Cc: ecos-discuss@sourceware.org In-Reply-To: <4662E9D4.5000804@mlbassoc.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <70d4f620706030625r3f31543amc5fb3b5f8249fe1b@mail.gmail.com> <4662E9D4.5000804@mlbassoc.com> X-IsSubscribed: yes Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Subject: Re: [ECOS] Order in which CDL scripts are processed X-SW-Source: 2007-06/txt/msg00037.txt.bz2 On 6/3/07, Gary Thomas wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Mike Sweeney wrote: > > While looking through the code for the CYGPKG_HAL_ARM_XSCALE_CORE > > package I noticed that it exports some header files to cyg/hal in the > > install tree. In particular, it exports hal_cache.h which contains > > some cache size definitions and such. Furthermore, some of the generic > > ARM platform HAL packages such as the CYGPKG_HAL_ARM_AEB export > > hal_cache.h to the same directory. Now, granted since the generic ARM > > targets won't include the XScale package there won't be a conflict, > > but out of curiousity if I did export a hal_cache.h from an XScale > > variant HAL package is there any guarantee as to which hal_cache.h > > would end up in the install tree under include/cyg/hal, i.e. the one > > from CYGPKG_HAL_ARM_XSCALE_CORE or the one from my XScale variant HAL > > package? > > > > In a nutshell, if I export the same header file to the same directory > > from two different packages, which one wins out or is it undefined > > behavior? > > Undefined and probably no guaranteed behaviour, so don't do it. > > If you need platform and/or variant changes/additions, there are > files for that (which are in turn included by the main hal_cache.h) > > > - -- > - ------------------------------------------------------------ > Gary Thomas | Consulting for the > MLB Associates | Embedded world > - ------------------------------------------------------------ Thanks, I wasn't going to do it. I was just curious because I thought that XScale cores could have either 32KB or 16KB(read this in XScale core developer's manual) of data and instruction cache based on implementation but the cache size seems to be defined to be 32KB in the XScale package which parents the XScale variant and platform HALs. -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss