public inbox for ecos-patches@sourceware.org
 help / color / mirror / Atom feed
From: Sergei Gavrikov <sergei.gavrikov@gmail.com>
To: eCos patches list <ecos-patches@ecos.sourceware.org>
Subject: Re: New HAL for Olimex LPCX22XX boards
Date: Fri, 14 Aug 2009 08:04:00 -0000	[thread overview]
Message-ID: <20090814080545.GA5368@sg-ubuntu.local> (raw)
In-Reply-To: <20090813135105.GA25941@sg-ubuntu.local>

On Thu, Aug 13, 2009 at 04:51:05PM +0300, Sergei Gavrikov wrote:
> The HAL startup code is a common part for the boards and was implemented

A fresh look and tweak: all 6 (boards) + 1 (common) HALs were moved from
hal/arm/lpc2xxx into separate folder hal/arm/lpcx22xx/olpcx22xx/*. There
is not forest in arm/lpc2xxx anymore. It seemed for me that likes AT91
board variants now.

> I do not generate a patch just now, because the sources have not ECOSGPL
> banners yet (it's easier to read them) and I do not know, would such a
> replacement be interesting for community. I need a feedback.
> 
> FYI: You no need to install mercurial to overview the code, here are the
> links for the direct downloads

The below are freshmeat now. All templates: "redboot" {RAM,ROM,ROMRAM},
"default", and "net" were rebuilt to test the tweak (new HAL tree
arrangment).

> http://bitbucket.org/tickling/olpcx22xx/get/tip.zip
> http://bitbucket.org/tickling/olpcx22xx/get/tip.gz
> http://bitbucket.org/tickling/olpcx22xx/get/tip.bz2
> 
> There is install script (install.sh) there which replaces old targets
> and adds new ones.

And I forget one thing. LPC-E2294 Rev. B has Davicom DM9000 ethrenet
controller. My ethernet driver for the board needs this patch
http://bugs.ecos.sourceware.org/attachment.cgi?id=739

This request is not applied still
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000780

Sergei

      reply	other threads:[~2009-08-14  8:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-13 13:49 Sergei Gavrikov
2009-08-14  8:04 ` Sergei Gavrikov [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=20090814080545.GA5368@sg-ubuntu.local \
    --to=sergei.gavrikov@gmail.com \
    --cc=ecos-patches@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).