public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: Evgeniy Dushistov <dushistov@mail.ru>
To: ecos-discuss@ecos.sourceware.org, 	ecos-devel@ecos.sourceware.org
Subject: at91sam9263ek support ver. beta 1
Date: Thu, 15 Jan 2009 15:17:00 -0000	[thread overview]
Message-ID: <E1LNTuh-000KuA-00.dushistov-mail-ru@f164.mail.ru> (raw)

Hi,

here is the fresh series of patches to support at91sam9263 ek board.

Now it passes near 100 tests from ecos's test suite, uses MMU, support my nor flash
(there is empty place to install nor flash, at least on at91sam9263ek rev. B).

It still requires at91bootstrap or jtag to run.

Here is links to patches, I suppose size too big to attach:

Support of 115200 baudrate (common baudrate to work with serial line for u-boot and linux):

http://sites.google.com/site/duhistov/Home/0001-change-default-delay-in-get-character-via-serial-lin.patch?attredirects=0


Move pio definitions to differents files to reduce size of common for at91 boards file,
and make it easy for editing:

http://sites.google.com/site/duhistov/Home/0002-This-patch-separate-board-s-pio-layout.patch?attredirects=0

I need this changes, because of at91sam9 use the same code as arm9 to work with caches:
http://sites.google.com/site/duhistov/Home/0003-rename-all-hal_cache.h-to-var_cache.h-and-copy-creat.patch?attredirects=0

Common part for working with arm9 mmu, move it to common files, because of I see a lot of duplication in
hal/arm/arm9:
http://sites.google.com/site/duhistov/Home/0004-move-common-for-arm9-code-for-work-with-mmu-into-com.patch?attredirects=0

at91sam9263 hal package:
http://sites.google.com/site/duhistov/Home/0005-hal-package-for-at91sam9263ek-and-at91sam9.patch?attredirects=0

My nor flash support:
http://sites.google.com/site/duhistov/Home/0006-support-of-norflash-for-at91sam9263ek.patch?attredirects=0

Work with pio interrupts like they are real one:
http://sites.google.com/site/duhistov/Home/0007-implement-support-pio-interrupts-in-the-way-as-ordin.patch?attredirects=0

the last two patches not require to make full working at91sam9263's hal.

Any comments?

PS

Some time ago(several weeks or  whole month), I sent request to fsf, about assigning copyrights,
but have no reply, may be they just drop my email.

             reply	other threads:[~2009-01-15 15:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-15 15:17 Evgeniy Dushistov [this message]
2009-01-15 17:02 ` [ECOS] " Jonathan Larmour
2009-01-21 19:20   ` Evgeniy Dushistov
2009-01-21 19:54     ` Jonathan Larmour

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=E1LNTuh-000KuA-00.dushistov-mail-ru@f164.mail.ru \
    --to=dushistov@mail.ru \
    --cc=ecos-devel@ecos.sourceware.org \
    --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).