public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: "Andreas Bießmann" <andreas.devel@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v1 3/3] arm, at91: add siemens corvus board
Date: Tue, 29 Oct 2013 14:05:59 +0100	[thread overview]
Message-ID: <526FB2B7.4090501@gmail.com> (raw)
In-Reply-To: <526FAD0A.8010403@denx.de>

Hello Heiko,

On 10/29/2013 01:41 PM, Heiko Schocher wrote:
> Am 29.10.2013 11:01, schrieb Andreas Bie?mann:
>> On 10/28/2013 06:45 AM, Bo Shen wrote:
>>> On 10/22/2013 13:51, Heiko Schocher wrote:
>>>> Signed-off-by: Boris Schmidt<boris.schmidt@siemens.com>
>>>> Reviewed-by: Heiko Schocher<hs@denx.de>
>>>> Cc: Andreas Bie?mann<andreas.devel@googlemail.com>
>>>> ---
>>>>    board/siemens/corvus/Makefile |  39 +++++
>>>>    board/siemens/corvus/board.c  | 345
>>>> ++++++++++++++++++++++++++++++++++++++++++
>>>>    boards.cfg                    |   1 +
>>>>    include/configs/corvus.h      | 185 ++++++++++++++++++++++
>>>>    4 files changed, 570 insertions(+)
>>>>    create mode 100644 board/siemens/corvus/Makefile
>>>>    create mode 100644 board/siemens/corvus/board.c
>>>>    create mode 100644 include/configs/corvus.h
>>>>
>>>> diff --git a/board/siemens/corvus/board.c
>>>> b/board/siemens/corvus/board.c
>>>> new file mode 100644
>>>> index 0000000..1940da7
>>>> --- /dev/null
>>>> +++ b/board/siemens/corvus/board.c

<snip>

>>>> +
>>>> +#define CONFIG_AT91_LEGACY
>>>> +#define CONFIG_ATMEL_LEGACY        /* required until (g)pio is
>>>> fixed */
>>
>> The ATMEL_LEGACY is required for dataflash, please consider using the
>> generic mtd sf stuff instead.
> 
> Ok, think about that ...

This legacy stuff is really a mess ... hopefully I get the gpio thing
cleaned up for 2014.01 and completely removed for the follow-up release.

> [...]
>>>> +/* LED */
>>>> +#define CONFIG_AT91_LED
>>>> +#define    CONFIG_RED_LED        AT91_PIN_PD31    /* this is the
>>>> user1 led */
>>>> +#define    CONFIG_GREEN_LED    AT91_PIN_PD0    /* this is the user2
>>>> led */
>>
>> Would you mind to use the generic gpio led stuff instead?
> 
> You mean ./drivers/misc/gpio_led.c ?

I mean the STATUS_LED thing (first part in README.LED). There is the
taskit stamp9g20 board which uses it already (in connection with the
at91 specific colour_LED thing)

<snip>

>>
>> nand read ${laodaddr} kernel ?
>>
>> When using mtdparts in u-boot ... just my 2?
> 
> You mean:
> nand read ${loadaddr} kernel
> ;-)

I do ;)

By,
Andreas

      reply	other threads:[~2013-10-29 13:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-22  5:51 [U-Boot] [PATCH v1 0/3] arm, at91: support for the taurus and corvus board Heiko Schocher
2013-10-22  5:51 ` [U-Boot] [PATCH v1 1/3] at91: add defines for reset type Heiko Schocher
2013-10-28  5:05   ` Bo Shen
2013-10-22  5:51 ` [U-Boot] [PATCH v1 2/3] arm, at91: add Siemens board taurus (based on AT91SAM9G20) Heiko Schocher
2013-10-28  5:24   ` Bo Shen
2013-10-29  9:43     ` Andreas Bießmann
2013-10-29 12:25       ` Heiko Schocher
2013-10-22  5:51 ` [U-Boot] [PATCH v1 3/3] arm, at91: add siemens corvus board Heiko Schocher
2013-10-28  5:45   ` Bo Shen
2013-10-29 10:01     ` Andreas Bießmann
2013-10-29 12:41       ` Heiko Schocher
2013-10-29 13:05         ` Andreas Bießmann [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=526FB2B7.4090501@gmail.com \
    --to=andreas.devel@googlemail.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