From: "Grant Mills" <gmills@ucsd.edu>
To: "Andrew Lunn" <andrew@lunn.ch>
Cc: "eCos Discussion" <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Modifying RedBoot to support multiple flash devices
Date: Thu, 09 Mar 2006 06:09:00 -0000 [thread overview]
Message-ID: <6f506bf60603082209g3c434909rebe1c139b26dc03c@mail.gmail.com> (raw)
In-Reply-To: <20060308223947.GH19406@lunn.ch>
On 3/8/06, Andrew Lunn <andrew@lunn.ch> wrote:
> On Wed, Mar 08, 2006 at 02:26:26PM -0800, Grant Mills wrote:
> > On 3/8/06, Andrew Lunn <andrew@lunn.ch> wrote:
> > > > Excellent. Now if I could only convince the Corporate IT people to
> > > > open up the firewall enough for me to access the cvs server.
> > > >
> > > > Thanks.
> > > >
> > > > --
> > > > Grant Mills
> > > > gmills@ucsd.edu
> > >
> > > ucsd.edu..... I would expect they have a unix machine on the outside
> > > which you can build an SSH tunnel to to access CVS.
> > >
> > > Andrew
> > >
> > >
> >
> > Yes, but I work for Motorola. I can't even SSH out of here to my home
> > box, where I could do the same thing. I'll probably write a script to
> > grab daily snapshots of the branch and e-mail them to my work address.
>
> No need to do daily snapshots. Nothing much happens in the branch. In
> fact it is suffering from bit rot :-(
>
> What you will probably want to do is from the v2 branch take io/flash,
> and dev/flash. Merge this with the trunk. You will also probably want
> to take a diff for of all the v2 changes in redboot and apply them to
> the trunk redboot.
>
> That should then give you an up to date eCos system but with flash v2
> features.
>
> The flash_v2 branch will get merged into the trunk when we make the
> next major release. That will happen when we assign eCos to the
> FSF. However that it taking much much longer than we expected.
>
> Andrew
>
>
Andrew,
So is sounds like I should be able to enter the packages directory
and execute this:
cvs -q -z3 up -j flash_v2 io/flash devs/flash redboot
Then I'll clean up the conflicts and I should be off and running. Right?
--
Grant Mills
gmills@ucsd.edu
--
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:[~2006-03-09 6:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-08 19:21 Grant Mills
2006-03-08 19:59 ` Andrew Lunn
2006-03-08 20:21 ` Grant Mills
2006-03-08 22:04 ` Alex Schuilenburg
2006-03-08 22:12 ` Andrew Lunn
2006-03-09 18:23 ` Chuck McManis
2006-03-10 11:11 ` Alex Schuilenburg
[not found] ` <20060308220250.GE19406@lunn.ch>
[not found] ` <6f506bf60603081426j4ec71e7dg1f068b4f42ad4b17@mail.gmail.com>
[not found] ` <20060308223947.GH19406@lunn.ch>
2006-03-09 6:09 ` Grant Mills [this message]
2006-03-09 20:58 ` Andrew Lunn
2006-03-09 21:09 ` Grant Mills
2006-03-09 21:18 ` Andrew Lunn
2006-03-09 21:40 ` Bart Veer
2006-03-08 22:07 ` Bart Veer
2006-03-08 22:14 ` Andrew Lunn
2006-03-08 22:31 ` Grant Mills
2006-03-10 4:44 yh
2006-03-10 7:22 ` Andrew Lunn
2006-03-10 11:19 ` Alex Schuilenburg
2006-03-10 17:25 ` Grant Mills
2006-03-14 3:17 yh
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=6f506bf60603082209g3c434909rebe1c139b26dc03c@mail.gmail.com \
--to=gmills@ucsd.edu \
--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).