From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20026 invoked by alias); 5 Sep 2005 10:01:22 -0000 Mailing-List: contact ecos-maintainers-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: ecos-maintainers-owner@ecos.sourceware.org Received: (qmail 19917 invoked by uid 22791); 5 Sep 2005 10:01:15 -0000 Received: from norbert.ecoscentric.com (HELO smtp.ecoscentric.com) (212.13.207.197) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Mon, 05 Sep 2005 10:01:15 +0000 Received: by smtp.ecoscentric.com (Postfix, from userid 99) id 2B49165C086; Mon, 5 Sep 2005 11:01:13 +0100 (BST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by smtp.ecoscentric.com (Postfix) with ESMTP id 89A3165C064; Mon, 5 Sep 2005 11:01:00 +0100 (BST) Message-ID: <431C175F.8040909@ecoscentric.com> Date: Mon, 05 Sep 2005 10:01:00 -0000 From: John Dallaway User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: rrichardson7 Cc: ecos-maintainers@ecos.sourceware.org Subject: Re: Submission Standards/Guidance References: <00cd01c5b1cd$3c8c8020$6ccae144@EngAtPlayWS> In-Reply-To: <00cd01c5b1cd$3c8c8020$6ccae144@EngAtPlayWS> X-Enigmail-Version: 0.90.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on norbert.ecoscentric.com X-Spam-Level: X-Spam-Status: No, score=-5.9 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.0.4 X-SW-Source: 2005-09/txt/msg00001.txt.bz2 Hi rrichardson7 wrote: > While working with Hypercom, I'd had the pleasure of helping to > implement eCos onto power-Pc platform. > Notable mods we'd made, but not published, were to the memory caching > macros (have an explanation for why the flush macros "did not seem to > work", and a variation of the dlmalloc that allowed us to track > instances of dynamic memory loss/corruption). Those solutions were > internally focused - ie. not made for general consumption, which is why > I gather that they were not published. > > Since that company has recently decided to "go in a different > direction", I'm no longer restricted from making such changes suitable > for general consumption. What are the guide lines for doing so? Thank you for your interest in contributing your work. The procedure is described here: http://ecos.sourceware.org/fom-serv/ecos/cache/7.html John Dallaway