public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Reinhard Meyer <u-boot@emk-elektronik.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] at91sam9263_nandflash build issues
Date: Wed, 02 Feb 2011 09:16:46 +0100	[thread overview]
Message-ID: <4D4912EE.8040509@emk-elektronik.de> (raw)
In-Reply-To: <201102020849.36451.marek.vasut@gmail.com>

Dear Marek Vasut,

> The problem is clear from this IRC log, where "vickylinuxer" described his grief 
> (so I included the log, the board really doesn't build). I also did a quick and 
> dirty patch (follows the log, it might give you an idea where it breaks, but 
> it's a mess -- not all is relevant and it probably breaks it even more).

All ATMEL AT91 boards except for AT91SAM9260ek (which I fixed) boards are currently broken.
People are working towards bringing the others in-line again, but that will take time.

> diff --git a/drivers/serial/atmel_usart.c b/drivers/serial/atmel_usart.c
> index bfa1f3a..1cc8bc0 100644
> --- a/drivers/serial/atmel_usart.c
> +++ b/drivers/serial/atmel_usart.c
> @@ -23,6 +23,7 @@
>  
>  #include <asm/io.h>
>  #include <asm/arch/clk.h>
> +#include <asm/arch/hardware.h>
>  #include <asm/arch/memory-map.h>

Things like that are fixed at u-boot-atmel.git/rework101228...

> diff --git a/drivers/spi/atmel_dataflash_spi.c b/drivers/spi/atmel_dataflash_spi.c
> index 4a5c4aa..d5215c0 100644
> --- a/drivers/spi/atmel_dataflash_spi.c
> +++ b/drivers/spi/atmel_dataflash_spi.c
> @@ -158,12 +158,12 @@ unsigned int AT91F_SpiWrite(AT91PS_DataflashDesc pDesc)
>         }
>  
>         /* arm simple, non interrupt dependent timer */
> -       reset_timer_masked();
> +       reset_timer();

NO. reset_timer() is not acceptable anymore. A fix is already in the list, I just need
some time to handle it all:)

> diff --git a/include/configs/at91sam9263ek.h b/include/configs/at91sam9263ek.h
> index f6cb406..3db8bd0 100644
> --- a/include/configs/at91sam9263ek.h
> +++ b/include/configs/at91sam9263ek.h
> @@ -27,6 +27,9 @@
>  #ifndef __CONFIG_H
>  #define __CONFIG_H
>  
> +#define CONFIG_AT91_LEGACY

There should be no need for LEGACY anymore.

I have project deadlines I must meet first, then I will handle all accumulated AT91 patches.

Best Regards,
Reinhard

  reply	other threads:[~2011-02-02  8:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-02  7:49 [U-Boot] at91sam9263_nandflash build issues Marek Vasut
2011-02-02  8:16 ` Reinhard Meyer [this message]
2011-02-02  8:18   ` [U-Boot] AT91: dataflash: was " Reinhard Meyer
2011-02-02  9:06   ` [U-Boot] " Marek Vasut
2011-02-02 11:14 ` Wolfgang Denk
2011-02-02 19:43 ` Scott Wood
2011-02-02 23:57   ` Marek Vasut

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=4D4912EE.8040509@emk-elektronik.de \
    --to=u-boot@emk-elektronik.de \
    --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