From: Andrew Lunn <andrew@lunn.ch>
To: Chirag shah <chirag@masibus.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] SPI support for AT91SAM7XEK.
Date: Wed, 28 Feb 2007 13:25:00 -0000 [thread overview]
Message-ID: <20070228132515.GB24209@lunn.ch> (raw)
In-Reply-To: <1172643213416.85.postmaster@masibus.com>
On Wed, Feb 28, 2007 at 11:43:11AM +0530, Chirag shah wrote:
> Dear Andrew Lunn,
>
> Thanks for your guidance. But I know that I have to add package for
> generic SPI. But when I am trying to add package from windows based
> configuration tool through build ----> packages and trying to add generic
> SPI package it is prompting that " Add and Remove hardware packages by
> selecting a new hardware template ".
The GUI configuration tool does not allow you to add "hardware"
packages to an eCos configuration. ecosconfig does not impose this
restriction and that is what i always use, so i've not seen this
problem before.
This difference has been discussed before, so search the mail archive
for more information.
>
> And another way is through Tools---->Administration. When I am going
> to Add generic SPI package it is asking for .epk file to be opened. I
> searched in my local drives that there is no such extension file is
> available.
This is used to add a package to a repository. SPI is already in the
repository, so you don't need to add it this way. You just want to add
SPI to your configuration.
>
> So, how can I add this package to my configuration. I think this is
> the same problem for Ethernet also.
Use the net template. Or more likely, the lwip_eth template.
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
prev parent reply other threads:[~2007-02-28 13:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-26 9:48 Chirag shah
2007-02-26 13:52 ` Andrew Lunn
2007-02-28 6:15 ` Chirag shah
2007-02-28 13:25 ` Andrew Lunn [this message]
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=20070228132515.GB24209@lunn.ch \
--to=andrew@lunn.ch \
--cc=chirag@masibus.com \
--cc=ecos-discuss@sources.redhat.com \
/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).