From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19206 invoked by alias); 5 Feb 2014 08:59:10 -0000 Mailing-List: contact ecos-patches-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: ecos-patches-owner@ecos.sourceware.org Received: (qmail 19187 invoked by uid 89); 5 Feb 2014 08:59:07 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=1.5 required=5.0 tests=AWL,BAYES_00,BODY_8BITS,GARBLED_BODY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 X-HELO: mail.ecoscentric.com Received: from hagrid.ecoscentric.com (HELO mail.ecoscentric.com) (212.13.207.197) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Wed, 05 Feb 2014 08:59:06 +0000 Received: from localhost (hagrid.ecoscentric.com [127.0.0.1]) by mail.ecoscentric.com (Postfix) with ESMTP id 33D054680001 for ; Wed, 5 Feb 2014 08:59:03 +0000 (GMT) Received: from mail.ecoscentric.com ([127.0.0.1]) by localhost (hagrid.ecoscentric.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bnv6zVTDEKiw; Wed, 5 Feb 2014 08:58:56 +0000 (GMT) From: bugzilla-daemon@bugs.ecos.sourceware.org To: ecos-patches@ecos.sourceware.org Subject: [Bug 1001933] New HAL for the M4 core of Freescale Vybrid targets Date: Wed, 05 Feb 2014 08:59:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: eCos X-Bugzilla-Component: Patches and contributions X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: ilijak@siva.com.mk X-Bugzilla-Status: ASSIGNED X-Bugzilla-Priority: low X-Bugzilla-Assigned-To: ilijak@siva.com.mk X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.ecos.sourceware.org/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-02/txt/msg00001.txt.bz2 Please do not reply to this email, use the link below. http://bugs.ecos.sourceware.org/show_bug.cgi?id=3D1001933 --- Comment #7 from Ilija Kocho [=D0=98=D0=BB=D0=B8=D1=98=D0=B0 =D0=9A=D0= =BE=D1=87=D0=BE] --- Hi Stefan (In reply to comment #6) [snip] >=20 > "There are a lot of "reg*.h" files in HAL include directory. Devices in e= Cos > are decoupled from HAL in order to enable usage of device drivers with > different architectures. I know that this philosophy is not perfectly > implemented, but I aim to do best for new packages. It is especially bene= fit > for Freescale's chips that re-use peripherals on different architectures." > This is exactly the reason for us having those files. For example we have > designed an Audio Framework, that works on MPC5xxx (Big Endian Power > Architecture) and Vybrid (Little Endian ARM CortexM), because all of those > peripheral definitions are taken from the HAL, so it e.g. includes the > "sai_reg.h" file for the definition of the SAI (Serial Audio Interface) > Peripheral, which are endianess swapped files between those two > architectures. Isn't that exactly what you want to achieve ? How else wou= ld > I achieve that ? This may justify their inclusion. However, putting them within some architecture implies another copy for every architecture/variant... You may consider the hal/misc directory. It is created for devices that do = not have formal I/O API, and are combined with different architectures. Exampl= es are DMA, memory devices, etc. You will already find "freescale" directory there parenting eDMA library package. You have several possibilities: - Create a package (some kind of Freescale device library. It may start = with headers, but may also (now and/or in future) also have some code. - If you already have some generic library for a particular device, you = can make a package (in a way eDMA is now). Note: This is not limited only to on-chip devices, however you should consi= der which of either devs or hal/misc would be preferable location. Following discussion may give you some insight on the background of hal/misc and how = to choose between hal/misc vs devs http://bugs.ecos.sourceware.org/show_bug.cgi?id=3D1001428#c5 . >=20 > "I'm glad to see SGML docs, but they seem incomplete and their compilation > raises errors." Quite frankly I do not even know how to correctly view SG= ML. > I just opened your Kinetis files with a text editor and tried to get > something semi correct. >=20 Text editor is right tool :) for editing, and in order to see the document = you need to generate HTML or PDF. This link http://ecos.sourceware.org/ml/ecos-discuss/2014-01/msg00004.html may help y= ou regarding needed tools and doc. generation, I would just add that if you us= e a common Linux distribution (I use Ubuntu) you'll find all tools in it's pack= age manager (such as Synaptic). However, if you are not able to generate HTML/PDF, I can feed you back or t= ake care that it compiles, but the contents has to be accurate, up to date and reflect real state of matters. Please take care of that. > "I have noticed CDL for Compiler selection. It is unnecessary because user > can specify compiler prefix and flags in "Global Build Options". Please > remove it." Actually we driving a lot of things from that selection, e.g. > whether we can move some critical code into the TCM (Tightly coupled > Memory). This requires, that the Compiler can generate some trampolin code > for that purpose, which the standard eCOS Compiler will not, but the > Codesourcery will. That checkbox will avoid a lot of user erros and all > members of our team really like that feature. Is it really a compiler feature or a linker script? Perhaps some macros? Le= t's investigate it. Ilija --=20 You are receiving this mail because: You are on the CC list for the bug.