From: Benny Chen <bennyc@rtunet.com>
To: Frank Pagliughi <fpagliughi@mindspring.com>
Cc: Andrew Lunn <andrew@lunn.ch>, ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Redboot JFFS2 Support
Date: Wed, 13 Jul 2005 23:49:00 -0000 [thread overview]
Message-ID: <1121298520.31422.268.camel@Vigor4> (raw)
In-Reply-To: <42D5394D.8030300@mindspring.com>
Hi Frank,
I have the login for Cirrus website and are currently running their
latest tree cirrus-arm-linux-1.4.3.
With this tree they are using the ecos2.0 release version. Hence, do
not include any of the Redboot JFFS2 changes.
Cheers,
Benny
On Thu, 2005-07-14 at 01:54, Frank Pagliughi wrote:
> Andrew Lunn wrote:
>
> >>Seriously, thanks for your info. I will get the latest installed.
> >>However, I have another question for now. Cirrus has a patch that needs
> >>to be applied to the ecos tree. This patch is for the ecos v2.0, I know
> >>that someone (most likely me) will need to go through and make sure that
> >>the patch does not break the system. But can I post the final patch on
> >>the list so that you can have a look at it?
> >>
> >>
> >
> >Sure.
> >
> >Could you give me a reference to the original patch straight from
> >Cirrus. Is it on there website?
> >
> > Thanks
> > Andrew
> >
> >
> >
> The original EDB9301 patch that Cirrus released was just enough to get
> RedBoot running, but not enough for a full-blown eCos, multithreaded
> app. Cirrus later released (in the fall of 2004, I believe) a more
> complete implementation, though still somewhat lacking. Both had
> modifications to JFFS2. Be sure to get the latest patch from Cirrus.
>
> I added some code and device drivers to their implementation. If you
> guys can get the Cirrus code into the eCos CVS, I'll gladly submit my
> additions.
>
> I just looked at their site, and believe that they've now hidden the
> patches behind a registration/login for their eval boards. I was working
> with a 3rd party board and don't have access. What to do?
>
> Frank Pagliughi
>
>
--
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:[~2005-07-13 23:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-12 4:02 Benny Chen
2005-07-12 6:56 ` Andrew Lunn
2005-07-12 23:47 ` Benny Chen
2005-07-13 6:45 ` Andrew Lunn
2005-07-13 15:55 ` Frank Pagliughi
2005-07-13 16:47 ` Andrew Lunn
2005-07-13 23:43 ` Benny Chen
2005-07-28 5:59 ` Benny Chen
2005-07-28 7:06 ` Andrew Lunn
2005-07-29 5:24 ` Benny Chen
2005-07-13 23:49 ` Benny Chen [this message]
2005-07-31 22:27 ` Benny Chen
2005-08-01 9:47 ` Andrew Lunn
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=1121298520.31422.268.camel@Vigor4 \
--to=bennyc@rtunet.com \
--cc=andrew@lunn.ch \
--cc=ecos-discuss@sources.redhat.com \
--cc=fpagliughi@mindspring.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).