From: "Grant Mills" <gmills@ucsd.edu>
To: "Andrew Lunn" <andrew@lunn.ch>,
"eCos Discussion" <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Modifying RedBoot to support multiple flash devices
Date: Thu, 09 Mar 2006 21:09:00 -0000 [thread overview]
Message-ID: <6f506bf60603091309u3b2cc4d7kd4a9b06f01956d3d@mail.gmail.com> (raw)
In-Reply-To: <20060309205801.GL19406@lunn.ch>
On 3/9/06, Andrew Lunn <andrew@lunn.ch> wrote:
> > 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?
>
> Humm, looks O.K.
>
> I've never done this myself, i've never needed to mix the branch and
> the trunk. So i cannot say it will actually work.
>
> You might also want to look at the changes that have been made to the
> AMD flash driver in the trunk since the branch was made. Some flash
> devices have been added which might not exist in the V2 driver.
>
> Andrew
>
>
Andrew,
Basically the -j switch merges the specified revision (flash_v2,
but it's a branch tag so cvs takes the tips of the branch) into the
current sandbox, which for me is HEAD/tip/trunk. So I've effectively
brought the flash_v2 changes to the tip.
There were some conflicts, most were in the ChangeLog files.
That's expected because cvs detected different changes in the same
space. There were a few in the code and I'll sort through those
before I build.
All,
Would anybody be interested in a report on the conflicts?
Thanks again.
--
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 21: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
2006-03-09 20:58 ` Andrew Lunn
2006-03-09 21:09 ` Grant Mills [this message]
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=6f506bf60603091309u3b2cc4d7kd4a9b06f01956d3d@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).