public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "ariga masahiro" <ariga@link-lab.co.jp>
To: "Andrew Lunn" <andrew@lunn.ch>
Cc: <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] How DSR is executed in interrupt ?
Date: Wed, 12 Sep 2007 08:19:00 -0000	[thread overview]
Message-ID: <000301c7f515$a21a2810$1c0110ac@ariga> (raw)

Hi,

About revising eCos source,
please teach me.

I wrote in prev. mail.
> First I copied and reserved current ecos directory C:\cygwin\opt\ecos
> by renaminig C:\cygwin\opt\ecos_precvs.
> And I copied renewd source from /ecoscvs into corresponding current 
> directoy,
But after copied CVS checkout source int  C:\cygwin\opt\ecos there appeared 
\v2_0 directory and \current directory.
Like next.
Previously only
C:\cygwin\opt\ecos\ecos-2.0\packages\devs\eth\sh\etherc\v2_0\src\if_etherc.c
existed.
After copied CVS,also appeared
C:\cygwin\opt\ecos\ecos-2.0\packages\devs\eth\sh\etherc\current\src\if_etherc.c
Now how to correctly revise these sources ?
Is it possibile to modify \current source according to \v2_0 source,
and delete  \v2_0 directory,only remaining \current directory ?
Can I build without error ?
I wonder it is impossible.

Please enlighten me.

Masahiro Ariga 


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

             reply	other threads:[~2007-09-12  8:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-12  8:19 ariga masahiro [this message]
2007-09-12  8:25 ` Andrew Lunn
  -- strict thread matches above, loose matches on Subject: below --
2007-09-10  8:21 ariga masahiro
2007-09-10  8:52 ` Andrew Lunn
2007-09-11  2:44   ` ariga masahiro
2007-09-11 14:19     ` Andrew Lunn
2007-09-12  4:51       ` ariga masahiro
2007-09-12  5:14         ` Paul D. DeRocco

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='000301c7f515$a21a2810$1c0110ac@ariga' \
    --to=ariga@link-lab.co.jp \
    --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).