public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Sergei Gavrikov <w3sg@SoftHome.net>
To: Olivier.Gaste@AirLiquide.com
Cc: eCos discuss mail list <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] More recent LPC-H2294 package
Date: Wed, 19 Jul 2006 09:03:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.63.0607191208290.12856@sg.belavox.gomel.by> (raw)

[-- Attachment #1: Type: text/plain, Size: 826 bytes --]

A few months ago I sent my lpch2294-1.0.epk for the Olimex LPC-H2294
header board. In those days the package was tested with the 2005-09-27
eCos snapshot only. Nowadays, I do a checkout of eCos CVS a few times in
a week. I found what this is a good practice. The lpc2xxx variant branch
had been a bit changed since.  Certainly, my CDL had been changed too.

There is new definition in the hal_arm_lpc2xxx_lpch2294.cdl

       requires      { CYGHWR_HAL_ARM_LPC2XXX == "LPC2294" }

The fixed package should work with the *latest* eCos repository. To add
the package to repository, do it in bash:

export ECOSADMIN="tclsh ${ECOS_REPOSITORY}/ecosadmin.tcl" 
$ECOSADMIN --accept_license add lpch2294-20060719.epk

The package still is no part of the official eCos tree. I've planed to
offer it as a patch as soon as I can.

Sergei

[-- Attachment #2: Type: application/octet-stream, Size: 9193 bytes --]

[-- Attachment #3: Type: text/plain, Size: 148 bytes --]

-- 
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:[~2006-07-19  9:03 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=Pine.LNX.4.63.0607191208290.12856@sg.belavox.gomel.by \
    --to=w3sg@softhome.net \
    --cc=Olivier.Gaste@AirLiquide.com \
    --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).