This is the mail archive of the ecos-patches@sources.redhat.com mailing list for the eCos project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: AT91 serial driver

From: Andrew Lunn <andrew at lunn dot ch>
To: Thomas Koeller <thomas dot koeller at baslerweb dot com>
Cc: Laurent GONZALEZ <laurent dot gonzalez at silicomp dot fr>,ecos-patches at sources dot redhat dot com
Date: Fri, 24 Oct 2003 09:47:02 +0200
Subject: Re: AT91 serial driver
References: <20031023171941.31c80379.laurent.gonzalez@ri.silicomp.fr> <200310240007.47048.thomas.koeller@baslerweb.com>

> However, you do of course have a point - minimizing system load is
> always good, and depending on the nature of the particular
> application this advantage may outweigh the speed penalty. Is there
> any reason why we can't (or shouldn't) have two at91 serial drivers
> in ecos?

Its definitely possible. We have two network stacks.....

But from a maintenance, testing and user confusion side of things it
would be better to have one driver. Would it be possible to merge the
two drivers keeping as much code as common as possible and CDL options
to configure between Low CPU-higher latency, and higherCPU-lower
latency?

        Thanks
                Andrew

Follow-Ups:
- Re: AT91 serial driver
  - From: Thomas Koeller

References:
- AT91 serial driver
  - From: Laurent GONZALEZ
- Re: AT91 serial driver
  - From: Thomas Koeller

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]