From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17463 invoked by alias); 14 Jan 2009 00:21:33 -0000 Received: (qmail 17452 invoked by uid 22791); 14 Jan 2009 00:21:32 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from mgcp1.bloomberg.com (HELO mgcp1.bloomberg.com) (208.22.56.39) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 14 Jan 2009 00:20:57 +0000 Received: from ny1520.bloomberg.com ([10.16.11.97]) by mgcp1.bloomberg.com with ESMTP; 13 Jan 2009 19:23:02 -0500 Received: from NY2528-DR.corp.bloomberg.com (ny2528-dr.corp.bloomberg.com [10.14.21.30]) by ny1520.bloomberg.com (8.14.1/8.14.1) with ESMTP id n0E0KkBk013385; Tue, 13 Jan 2009 19:20:46 -0500 Received: from ny2545.corp.bloomberg.com ([172.20.73.98]) by NY2528-DR.corp.bloomberg.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 13 Jan 2009 19:20:46 -0500 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Subject: RE: Serial VS Diagnostic interface Date: Wed, 14 Jan 2009 00:21:00 -0000 Message-ID: In-Reply-To: <69b5c5160901131157x14de6cdek72b7b8c86455a709@mail.gmail.com> References: <69b5c5160901131157x14de6cdek72b7b8c86455a709@mail.gmail.com> From: "Chris Zimman" To: "andrew wiggin" , X-IsSubscribed: yes Mailing-List: contact ecos-devel-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: ecos-devel-owner@ecos.sourceware.org X-SW-Source: 2009-01/txt/msg00021.txt.bz2 > I am working with eCos on an AT91 platform for several month now, and > I have always used the serial port as a diagnostic interface for > debugging purpose. However, now I need to use it as a standard serial > in order to be able to use the O_NONBLOCK flag but I couldn't find a > way to use the 16x55 serial driver instead of the haldiag interface: > whatever I do, only the haldiag interface is selected, and removing > the haldiag seems to make it impossible to compile. >=20 > I know I can use the solution consisting in replacing the GETC > function with a nonblocking one, and patching whatever function may > need blocking calls on it, but I can't imagine there is no way in eCos > to select whether my only serial port shall be considered as a > diagnostic interface or a _real_ serial port. >=20 > Any clue will be welcome. Make sure you have the hardware serial port drivers compiled in. With that you can use "/dev/ser0" etc. instead of "/dev/haldiag" and use non-blocking interfaces. --Chris