From: Jonathan Larmour <jifl@eCosCentric.com>
To: Patrick Doyle <wpd@delcomsys.com>
Cc: ecos-maintainers@sources.redhat.com
Subject: Re: Adding OMAP to list of supported Hardware
Date: Wed, 12 Feb 2003 21:05:00 -0000 [thread overview]
Message-ID: <3E4AB701.30701@eCosCentric.com> (raw)
In-Reply-To: <NFBBJAJICAKJPMMKDAGBAEMADKAA.wpd@delcomsys.com>
Patrick Doyle wrote:
> Thanks... it looks great and the links work. I just noticed the "Thanks to
> Patrick Doyle..." blurb at the bottom of the "More Info" link. Wow, my name
> in lights again!!! :-)
:-)
>>Remember to include the eth device driver in the target innovator {} bit
>>in ecos.db when you get this working for eCos and not just RedBoot.
>
>
> I added that yesterday and am about to prepare a new patch. I just need to
> figure out the right incantation for cvs diff to produce the new ChangeLog
> files that I created. ("cvs add" gets mad at me because I don't have write
> access to the server).
Ah yes, that can be a pain with anoncvs. Unfortunately I've never found a
better way than generating the patch for the files that changed and then
for every new file/directory manually do:
diff -urN /dev/null FILENAME >> patch
at the same level as the patch.
> FWIW, TI is now steering some folks to eCos for the OMAP. They find that
> some folks want WinCE, but most folks want to run either Linux or just run
> on the bare metal. The later category are the ones that are being steered
> to eCos, with all three categories being made aware of it.
Yes, being fully open source can be a great help to those who would
otherwise do a home-grown system. Hopefully this will help spread the
message :-).
Jifl
--
eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts
--[ "You can complain because roses have thorns, or you ]--
--[ can rejoice because thorns have roses." -Lincoln ]-- Opinions==mine
prev parent reply other threads:[~2003-02-12 21:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-11 22:11 Patrick Doyle
2003-02-12 17:36 ` Jonathan Larmour
2003-02-12 18:27 ` Patrick Doyle
2003-02-12 21:05 ` Jonathan Larmour [this message]
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=3E4AB701.30701@eCosCentric.com \
--to=jifl@ecoscentric.com \
--cc=ecos-maintainers@sources.redhat.com \
--cc=wpd@delcomsys.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).