From: Mandeep Sandhu <mandeepsandhu.chd@gmail.com>
To: John Dallaway <john@dallaway.org.uk>
Cc: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Re: USB on at91sam7xek [ was Re: ecos memory footprint ]
Date: Tue, 14 Jul 2009 12:47:00 -0000 [thread overview]
Message-ID: <b18c5f790907140547o5bfdc51dp31e8671a00552920@mail.gmail.com> (raw)
In-Reply-To: <4A5C7964.4080305@dallaway.org.uk>
> CYGPKG_IO_USB and CYGPKG_IO_USB_SLAVE are _hardware_ packages. They are
> accessed by selecting an appropriate eCos _target_ which includes a USB
> driver (eg target "pc_usb_d12").
>
> I assume you are experimenting with the at91sam7xek target. The target
> record for this target should include the CYGPKG_IO_USB and
> CYGPKG_IO_USB_SLAVE packages but they are missing from the package list.
> Locate the "target at91sam7xek" record in
> /opt/ecos/ecos-3.0/packages/ecos.db and add the missing packages to the
> package list.
Thanks John. That fixed the problem!
-mandeep
>
> I will fix this problem in the eCos CVS repository.
>
> John Dallaway
>
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2009-07-14 12:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-13 13:14 [ECOS] ecos memory footprint Mandeep Sandhu
2009-07-13 22:09 ` Alexander Neundorf
2009-07-14 4:52 ` Mandeep Sandhu
2009-07-14 8:43 ` Simon Kallweit
2009-07-14 10:28 ` Mandeep Sandhu
2009-07-14 10:34 ` Sergei Gavrikov
2009-07-14 11:04 ` Mandeep Sandhu
2009-07-14 13:18 ` Mandeep Sandhu
2009-07-14 13:22 ` Mandeep Sandhu
2009-07-14 13:31 ` Sergei Gavrikov
2009-07-14 13:30 ` Andrew Lunn
2009-07-14 10:43 ` Ross Younger
2009-07-14 11:16 ` Mandeep Sandhu
2009-07-14 12:26 ` [ECOS] USB on at91sam7xek [ was Re: ecos memory footprint ] John Dallaway
2009-07-14 12:47 ` Mandeep Sandhu [this message]
2009-07-14 14:22 ` [ECOS] Re: ecos memory footprint Grant Edwards
2009-07-15 4:34 ` Mandeep Sandhu
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=b18c5f790907140547o5bfdc51dp31e8671a00552920@mail.gmail.com \
--to=mandeepsandhu.chd@gmail.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=john@dallaway.org.uk \
/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).