From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19085 invoked by alias); 14 Jan 2009 14:19:51 -0000 Received: (qmail 19075 invoked by uid 22791); 14 Jan 2009 14:19:50 -0000 X-SWARE-Spam-Status: No, hits=-1.5 required=5.0 tests=AWL,BAYES_50,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org Received: from anchor-post-2.mail.demon.net (HELO anchor-post-2.mail.demon.net) (195.173.77.133) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 14 Jan 2009 14:19:14 +0000 Received: from calivar.demon.co.uk ([83.104.54.243] helo=xl5.calivar.com) by anchor-post-2.mail.demon.net with esmtp (Exim 4.69) id 1LN6aN-0005sV-ly; Wed, 14 Jan 2009 14:19:11 +0000 Received: from xl5.calivar.com (localhost [127.0.0.1]) by xl5.calivar.com (Postfix) with ESMTP id D9B34138766; Wed, 14 Jan 2009 14:19:10 +0000 (GMT) To: "damien millescamps" Cc: "Chris Zimman" , "andrew wiggin" , ecos-devel@ecos.sourceware.org Subject: Re: Serial VS Diagnostic interface References: <69b5c5160901131157x14de6cdek72b7b8c86455a709@mail.gmail.com> <69b5c5160901140502x62d7e748uc65136d473f83fb@mail.gmail.com> <587ce2cd0901140529h562f0daasa0d8dfde252249bf@mail.gmail.com> From: Nick Garnett Original-Sender: nickg@ecoscentric.com Date: Wed, 14 Jan 2009 14:19:00 -0000 In-Reply-To: <587ce2cd0901140529h562f0daasa0d8dfde252249bf@mail.gmail.com> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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/msg00026.txt.bz2 "damien millescamps" writes: > On Wed, Jan 14, 2009 at 2:24 PM, Chris Zimman wrote: > >> Actually as it just inline code. I have already checked it is > >> correctly included. Maybe I should have been more explicit: Is there > >> anything to ensure the HW serial driver is correctly initialized ? > >> Where should pc_serial_lookup() be called in a normal behavior ? > > > > If you can build the serial tests and they pass, you should be in good shape. > > Alternatively, if opening "/dev/ser0" succeeds, you're good to go. > > > > opening /dev/ser0 results in an error. Now that I know it should > normally work, I can start to instrument a little bit to find out why > it doesn't work for me. The most common problem with serial devices is not enabling CYGPKG_IO_SERIAL_DEVICES. Obviously you also have to include the CYGPKG_IO_SERIAL package too. Note that AT91 serial devices cannot be shared between diagnostics and serial drivers. So if you want to continue using diagnostics on a particular UART, you need to disable it for the drivers. -- Nick Garnett eCos Kernel Architect eCosCentric Limited http://www.eCosCentric.com The eCos experts Barnwell House, Barnwell Drive, Cambridge, UK. Tel: +44 1223 245571 Registered in England and Wales: Reg No: 4422071