public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Navya S Kamath" <navya@coreel.com>
To: "'Andrew Lunn'" <andrew@lunn.ch>
Cc: <ecos-discuss@ecos.sourceware.org>
Subject: RE: [ECOS] How to enable USB on IXP425 GRG
Date: Mon, 26 Nov 2007 08:58:00 -0000	[thread overview]
Message-ID: <20071126085800.m96CCQnnkpQid-SufDezTNffD6xqzTmZ_TkbT19C5n4@z> (raw)
In-Reply-To: <20071123201755.GC15731@lunn.ch>

Hi,

I have the code compiling now. The cdl_option for EP0 was taking the default
value of CYGINT_IO_USB_SLAVE_CLIENTS which was 0.I changed this value to 1
with this the USB code gets compiled.

Thank you so much for the information.

Regards,
Navya

-----Original Message-----
From: ecos-discuss-owner@ecos.sourceware.org
[mailto:ecos-discuss-owner@ecos.sourceware.org] On Behalf Of Andrew Lunn
Sent: Saturday, November 24, 2007 1:48 AM
To: Navya S Kamath
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] How to enable USB on IXP425 GRG

On Fri, Nov 23, 2007 at 05:57:25PM +0530, Navya S Kamath wrote:
> Hi,
> 
> I created a driver package for USB on IXP425. I have modified the ecos.db
to
> include the USB package. Similarly I have edited the .ecm files for the
> board. But while compiling the image the driver source is not compiled.Is
> there any other change to be made?

Nope. 

The linker may through the driver away if it is not used, but you say
it is not even being compiled. So this is a different issue. Does your
packages CDL have any enable/disable logic? Does you ecos.ecc file
contain the driver package and any options it make include. Do you get
a makefile for it in the build tree? Does the Makefile list the source
file?

        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



-- 
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-11-26  5:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1ItHm8-0002e2-00@londo.lunn.ch>
2007-11-17  8:49 ` Andrew Lunn
2007-11-17 17:46   ` Navya S Kamath
     [not found]   ` <E1ItJNI-0002rc-00@londo.lunn.ch>
2007-11-18 12:17     ` Andrew Lunn
2007-11-23 14:46       ` Navya S Kamath
     [not found]       ` <E1IvXeW-0006LI-00@londo.lunn.ch>
2007-11-23 21:02         ` Andrew Lunn
2007-11-26  8:58           ` Navya S Kamath [this message]
     [not found] <E1IwsNL-0006NW-00@londo.lunn.ch>
2007-11-27 14:39 ` Andrew Lunn
2007-11-27  6:47 Navya S Kamath
  -- strict thread matches above, loose matches on Subject: below --
2007-11-17  7:17 Navya S Kamath

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=20071126085800.m96CCQnnkpQid-SufDezTNffD6xqzTmZ_TkbT19C5n4@z \
    --to=navya@coreel.com \
    --cc=andrew@lunn.ch \
    --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).