[ECOS] Driver Development approach
Trenton D. Adams
tadams@extremeeng.com
Tue Jun 12 13:07:00 GMT 2001
Ah, see the headers below. The list is CCing to it's self and creating
duplicate messages, no?
Return-Path:
<ecos-discuss-return-7450-tadams=extremeeng.com@sources.redhat.com>
Received: from sourceware.cygnus.com ([205.180.83.71])
by Firewall.extremeeng.com (Post.Office MTA v3.5.3 release 223
ID# 0-0U10L2S100V35) with SMTP id com
for <tadams@extremeeng.com>; Tue, 12 Jun 2001 14:04:48 -0600
Received: (qmail 15839 invoked by alias); 12 Jun 2001 18:09:08 -0000
Mailing-List: contact ecos-discuss-help@sourceware.cygnus.com; run by
ezmlm
Precedence: bulk
List-Unsubscribe:
< mailto:ecos-discuss-unsubscribe-tadams=extremeeng.com@sources.redhat.co
m>
List-Subscribe: < mailto:ecos-discuss-subscribe@sources.redhat.com >
List-Archive: < http://sources.redhat.com/ml/ecos-discuss/ >
List-Post: < mailto:ecos-discuss@sources.redhat.com >
List-Help: < mailto:ecos-discuss-help@sources.redhat.com >,
< http://sources.redhat.com/ml/#faqs >
Sender: ecos-discuss-owner@sources.redhat.com
Delivered-To: mailing list ecos-discuss@sources.redhat.com
Received: (qmail 15753 invoked from network); 12 Jun 2001 18:08:58 -0000
Received: from unknown (HELO executor.cambridge.redhat.com)
(195.224.55.237)
by sourceware.cygnus.com with SMTP; 12 Jun 2001 18:08:58 -0000
Received: from redhat.com (murgh.cambridge.redhat.com [172.16.18.70])
by executor.cambridge.redhat.com (Postfix) with ESMTP
id 6665AABB03; Tue, 12 Jun 2001 19:08:50 +0100 (BST)
Message-ID: < 3B265AB2.67E19640@redhat.com >
Date: Tue, 12 Jun 2001 19:08:50 +0100
From: Jonathan Larmour <jlarmour@redhat.com>
Organization: Red Hat UK Ltd.
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.17-14enterprise i686)
X-Accept-Language: en
MIME-Version: 1.0
To: "Trenton D. Adams" <tadams@extremeeng.com>
Cc: 'eCos Discussion' <ecos-discuss@sourceware.cygnus.com>
References: < 000e01c0f2c2$77c59ab0$090110ac@BURN >
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: [ECOS] Driver Development approach
-----Original Message-----
From: ecos-discuss-owner@sources.redhat.com
[ mailto:ecos-discuss-owner@sources.redhat.com ] On Behalf Of Jonathan
Larmour
Sent: Tuesday, June 12, 2001 12:09 PM
To: Trenton D. Adams
Cc: 'eCos Discussion'
Subject: Re: [ECOS] Driver Development approach
"Trenton D. Adams" wrote:
>
> I've been reading up on driver development. I want some advice on my
> approach.
>
> I was thinking that I could make a driver that simply prints to stdout
> when cyg_io_write() or cyg_io_read() are called on it. I could make a
> test harness program, and run it through GDB. Then when connecting
> through GDB, I would know that it's working because the messages would
> be output to me.
>
> Will this even work? If so, is this a good approach to learn how the
> drivers interact with the system?
I think it could work, while the cyg_io stuff isn't particularly
intended to be re-entrant, I think it is anyway.
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223)
271062 Maybe this world is another planet's Hell -Aldous Huxley ||
Opinions==mine Come to the Red Hat TechWorld open source conference in
Brussels!
Keynotes, techie talks and exhibitions
http://www.redhat-techworld.com/
More information about the Ecos-discuss
mailing list