From: Andrew Lunn <andrew@lunn.ch>
To: Gary Thomas <gary@mlbassoc.com>
Cc: Bob.Brusa@gmail.com,
"MailingList:ecos-discuss ;" <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Fwd: AT91SAM7X-EK with TC/IP - unresolved conflicts
Date: Sat, 30 Aug 2008 00:10:00 -0000 [thread overview]
Message-ID: <20080829162608.GV31987@lunn.ch> (raw)
In-Reply-To: <48B8137D.7040803@mlbassoc.com>
> I just tried it here with no problems:
>
> [gthomas@titan at91]$ ECOS_REPOSITORY=/local/ecos/packages ecosconfig new at91sam7xek net
> U CYGHWR_HAL_ARM_AT91, new inferred value AT91SAM7S
> U CYGHWR_HAL_ARM_AT91_FIQ, new inferred value 1
> U CYGHWR_HAL_ARM_AT91SAM7, new inferred value at91sam7x256
> U CYGHWR_DEVS_ETH_PHY_DM9161A, new inferred value 1
> U CYGBLD_ISO_STRUCTTIMEVAL_HEADER, new inferred value <cyg/posix/sys/time.h>
> U CYGBLD_ISO_FNMATCH_HEADER, new inferred value <cyg/fileio/fnmatch.h>
> [gthomas@titan at91]$ ECOS_REPOSITORY=/local/ecos/packages ecosconfig tree
Me too.
However, this is a pointless exercise. The AT91SAM7X only has 64K
RAM. Getting the FreeBSD stack to work in that is probably impossible.
Try the lwip_eth template. Then you will need to tune the lwip
configuration.
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
next prev parent reply other threads:[~2008-08-29 16:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-29 15:04 [ECOS] " Robert Brusa
2008-08-29 15:20 ` [ECOS] Fwd: " Robert Brusa
2008-08-29 15:54 ` Gary Thomas
2008-08-29 16:06 ` Robert Brusa
2008-08-29 16:26 ` Gary Thomas
2008-08-30 0:10 ` Andrew Lunn [this message]
2008-09-01 9:27 ` Robert Brusa
2008-09-01 9:38 ` Andrew Lunn
2008-09-02 8:10 ` Robert Brusa
2008-09-02 8:42 ` Andrew Lunn
2008-09-03 13:22 ` Robert Brusa
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=20080829162608.GV31987@lunn.ch \
--to=andrew@lunn.ch \
--cc=Bob.Brusa@gmail.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=gary@mlbassoc.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).