From: Cristian Birsan <cristian.birsan@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Olimex SAM9-L9260 board support
Date: Sat, 01 Nov 2008 14:49:26 +0200 [thread overview]
Message-ID: <1225543766.3374.14.camel@localhost.localdomain> (raw)
In-Reply-To: <20081031070538.GD23324@game.jcrosoft.org>
Dear Jean-Christophe PLAGNIOL-VILLARD,
I will remove all unnecessary white spaces from the previous patch. I
have now a patch version for u-boot u-boot v2008.10
> > "
> >
> > #########################################################################
> > diff --git a/Makefile b/Makefile
> > index 7c13ce8..5b0acae 100644
> > --- a/Makefile
> > +++ b/Makefile
> > @@ -2487,15 +2487,6 @@ shannon_config : unconfig
> > at91rm9200dk_config : unconfig
> > @$(MKCONFIG) $(@:_config=) arm arm920t at91rm9200dk atmel at91rm9200
> >
> > -at91sam9261ek_config : unconfig
> > - @$(MKCONFIG) $(@:_config=) arm arm926ejs at91sam9261ek atmel at91
> > -
> > -at91sam9263ek_config : unconfig
> > - @$(MKCONFIG) $(@:_config=) arm arm926ejs at91sam9263ek atmel at91
> > -
> > -at91sam9rlek_config : unconfig
> > - @$(MKCONFIG) $(@:_config=) arm arm926ejs at91sam9rlek atmel at91
> > -
> > cmc_pu2_config : unconfig
> > @$(MKCONFIG) $(@:_config=) arm arm920t cmc_pu2 NULL at91rm9200
> >
> > @@ -2521,6 +2512,18 @@ at91cap9adk_config : unconfig
> > at91sam9260ek_config : unconfig
> > @$(MKCONFIG) $(@:_config=) arm arm926ejs at91sam9260ek atmel at91
> >
> > +at91sam9261ek_config : unconfig
> > + @$(MKCONFIG) $(@:_config=) arm arm926ejs at91sam9261ek atmel at91
> > +
> > +at91sam9263ek_config : unconfig
> > + @$(MKCONFIG) $(@:_config=) arm arm926ejs at91sam9263ek atmel at91
> > +
> > +at91sam9rlek_config : unconfig
> > + @$(MKCONFIG) $(@:_config=) arm arm926ejs at91sam9rlek atmel at91
> > +
> > +sam9l9260_config : unconfig
> > + @$(MKCONFIG) $(@:_config=) arm arm926ejs sam9l9260 olimex at91
> > +
> why do you touch other at91 config?
I touched other configs because i tried to put correctly boards with
arm920t and arm926ejs in their sections. I belive that at91sam9261ek
at91sam9263ek should be placed in the arm926ejs core section. Please
correct me if i'm wrong.
> > +#ifndef __CONFIG_H
> > +#define __CONFIG_H
> > +
> > +/* Hostname */
> > +#define CONFIG_HOSTNAME sam9l9260
> > +
> > +/* ARM asynchronous clock */
> > +#define AT91_MAIN_CLOCK 198656000 /* from 18.432 MHz crystal */
> > +#define AT91_MASTER_CLOCK 99328000 /* peripheral = main / 2 */
> > +#define CFG_HZ 1000000 /* 1us resolution */
> please update to CONFIG_SYS_
> Note that I've plan and announce that I'll generate a common code for
> at91sam9260 and other to reduce duplicate code.
I can change CFG_HZ to CONFIG_SYS_HZ but that macro is used
in /cpu/arm926ejs/at91/timer.c. If I change the macro from timer.c I
should update all at91 configurations but I can test only on Olimex
(at91sam9260) board. I do not know if it's safe to modify other
configurations without appropriate testing.
Regards,
Cristian
next prev parent reply other threads:[~2008-11-01 12:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-06 18:03 [U-Boot] [PATCH] Olimex SAM9-L9260 board support Cristian Birsan
2008-10-06 18:43 ` Wolfgang Denk
2008-10-06 20:33 ` Cristian Birsan
2008-10-06 20:44 ` Wolfgang Denk
2008-10-07 16:35 ` Cristian Birsan
2008-10-07 18:37 ` Wolfgang Denk
2008-10-07 21:12 ` Cristian Birsan
2008-10-07 22:05 ` Cristian Birsan
2008-10-07 22:55 ` Wolfgang Denk
2008-10-10 10:24 ` Cristian Birsan
2008-10-30 23:41 ` Cristian Birsan
2008-10-31 7:00 ` Jean-Christophe PLAGNIOL-VILLARD
2008-10-31 7:05 ` Jean-Christophe PLAGNIOL-VILLARD
2008-10-31 8:23 ` Jean-Christophe PLAGNIOL-VILLARD
2008-10-31 8:48 ` Wolfgang Denk
2008-10-31 9:05 ` Jean-Christophe PLAGNIOL-VILLARD
2008-11-01 12:49 ` Cristian Birsan [this message]
2008-11-01 13:19 ` Jean-Christophe PLAGNIOL-VILLARD
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=1225543766.3374.14.camel@localhost.localdomain \
--to=cristian.birsan@gmail.com \
--cc=u-boot@lists.denx.de \
/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