This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Accessing custom built driver functions in eCos.
- From: Andrew Lunn <andrew at lunn dot ch>
- To: John Taylor <eestudydude at hotmail dot com>
- Cc: ecos-discuss at sources dot redhat dot com
- Date: Mon, 21 Mar 2005 08:39:34 +0100
- Subject: Re: [ECOS] Accessing custom built driver functions in eCos.
- References: <BAY19-F81BCE180ADB3B39684DDBB04D0@phx.gbl>
On Mon, Mar 21, 2005 at 07:01:52PM +1200, John Taylor wrote:
> I?ve had some trouble with accessing original device driver functions
> written for eCos v2.0. Whenever the application source attempts to access a
> function in the device driver, the function source is not recognised. E.g.
> a simple function such as modem_wait_incoming_call(void*); written as a
> device driver with an associated prototype included in a header file
> produces the error: ?undefined reference to
> modem_wait_incoming_call(&input))?. This problem is solved if the driver
> file is included within the application code, however if it is possible I
> would like to avoid this. Do I need to modify devtab.h?
> If anyone has any input on what may resolve this issue, I would be very
> grateful.
Hi John
Let see if i understand you correctly.
You have added a new package to eCos which is a device driver. This
device driver has a header file and at least one function, which is
called modem_wait_incoming_call().
When do you get the error, during compilation or during linking?
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss