public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Alexandre <thekyz@gmail.com>
To: Alexandre <thekyz@gmail.com>,
	 	ecos-discuss <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] I2C Driver not initializing
Date: Tue, 11 Sep 2007 14:26:00 -0000	[thread overview]
Message-ID: <d5aafeec0709110726qc2ad4e6l4a639c91c2f2e2d0@mail.gmail.com> (raw)
In-Reply-To: <20070911141526.GF23980@lunn.ch>

> Is this a I2C device driver you have written yourself? Or is it one of
> the existing device drivers?

Well it's one I've written myself as i didn't found any driver for the
LPC2XXX port.

> What do you have in the cdl file for the driver?

Actually, nothing, the driver part is style in my user code as I
wanted to test it before even trying to include it in eCos.
I added the package "I2C Support" to my package build and tried to
link my functions to it. Everything compiles just fine and i can
access the generic I2C functions as the headers are added to my
source.

> compile       -library=libextras.a my_i2c.c

libextras.a already exists in my config and contains my serial devices
configuration. It does not contain anything about i2c however, should
it ?

> Im wondering if the linker has throw the driver out because it is not
> being used. By adding the -library=libextras.a the linker cannot throw
> it away.

Well even the generic I2C driver code is not initialized so I think I
made a mistake by forgetting something or misunderstanding the whole
concept ^^

Alex

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2007-09-11 14:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-11 14:06 Alexandre
2007-09-11 14:15 ` Andrew Lunn
2007-09-11 14:26   ` Alexandre [this message]
2007-09-11 15:25     ` Andrew Lunn
2007-09-11 16:04       ` Alexandre

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d5aafeec0709110726qc2ad4e6l4a639c91c2f2e2d0@mail.gmail.com \
    --to=thekyz@gmail.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).