From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5655 invoked by alias); 8 Jun 2005 11:24:44 -0000 Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Received: (qmail 5497 invoked by uid 22791); 8 Jun 2005 11:24:29 -0000 Received: from asav1.lyse.net (HELO asav1.lyse.net) (213.167.96.68) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Wed, 08 Jun 2005 11:24:29 +0000 Received: from asav1.lyse.net (asav1.lyse.net [127.0.0.1]) by localhost.lyse.net (Postfix) with ESMTP id 3C51090101; Wed, 8 Jun 2005 13:19:27 +0200 (CEST) Received: from mail1.lyse.net (unknown [192.168.42.2])by asav1.lyse.net (Postfix) with ESMTPid 17CDC9006B; Wed, 8 Jun 2005 13:19:27 +0200 (CEST) Received: from [84.234.138.230] (helo=[192.168.0.193])by mail1.lyse.net with smtp (Exim 4.34)id 1DfyeH-0000JI-0X; Wed, 08 Jun 2005 13:23:05 +0200 From: =?ISO-8859-1?Q?=D8yvind?= Harboe To: ecos-discuss@sources.redhat.com Cc: ezeq@cc.isel.ipl.pt Content-Type: text/plain; charset=ISO-8859-1 Date: Wed, 08 Jun 2005 11:24:00 -0000 Message-Id: <1118229873.11654.24.camel@localhost.localdomain> Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-imss-version: 2.025 X-imss-result: Passed X-imss-scores: Clean:1.55413 C:2 M:3 S:5 R:5 X-imss-settings: Baseline:2 C:1 M:1 S:1 R:1 (0.1500 0.1500) Subject: [ECOS] hal_delay_us() patch to at91_misc + multithreading X-SW-Source: 2005-06/txt/msg00063.txt.bz2 Original message: http://sourceware.org/ml/ecos-discuss/2005-05/msg00357.html Your fix seems approperiate. Perhaps you should try to post it to ecos-patches? Q: As near as I can tell, HAL_DELAY_US() is not thread safe in at91_misc.c. Is this correctly observed? I can't tell by reading the eCos documentation whether or not hal_delay_us or HAL_DELAY_US is supposed to be thread safe. http://sources.redhat.com/ecos/docs-2.0/ref/hal-interrupt-handling.html The implementation of I2C uses hal_delay_us, but since I'm not currently using that code(our home rolled I2C code has not been phased out yet), I'm not sure whether or not interrupts are disabled while hal_delay_us() is invoked inside the I2C code. --=20 =D8yvind Harboe http://www.zylin.com -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss