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] Fwd: [STATUS] WARNING: huge ARM board removal pending
Date: Tue, 07 Jun 2011 12:41:26 +0200	[thread overview]
Message-ID: <4DEE0056.7070105@emk-elektronik.de> (raw)
In-Reply-To: <4DEDF88D.2020903@atmel.com>

Dear Hong Xu,
>> If there are SoC specific files to be adapted, they should be adapted
>> as done in 9260.
>>
>> Board specific files should be looking like those of at91sam9260-ek.
>>
>> Remove fixed boards from the global Makefile and add them to boards.cfg.
>>
>> I'll put the fix for at91sam9260*-ek on u-boot-atmel/master in the next hours,
>> you can have a look at it - or look at the patch I posted yesterday for it.
> 
> OK, very nice. I'm just worried because I can not compile at91sam9260ek on u-boot-atmel/master and u-boot-atmel/next 3 hrs ago.
> 
> So, we're waiting for your work on sam9260 and take it as a starting point for other boards.

Its now there.

With toolchain ARM-4.5.2 the following warning is given (building top9000_eval_xe_config).
I had no time to look into this. The warning is not due to rework and shows only with newer
toolchains, I think.

*** make u-boot.bin
macb.c: In function ???macb_write_hwaddr???:
macb.c:525:2: warning: dereferencing type-punned pointer will break strict-aliasing rules

at91sam9260-ek builds but throws a few more warnings in the dataflash_spi driver.
Please also see my post titled
"[U-Boot] ATMEL atmel_dataflash_spi.c - work at hand - can someone do it ?"

Maybe you can look into that :)

Best Regards,

Reinhard

      reply	other threads:[~2011-06-07 10:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4C79549CB6F772498162A641D92D532801E23ACF@penmb01.corp.atmel.com>
2011-06-07  8:18 ` [U-Boot] Fwd: [STATUS] WARNING: huge ARM board removal pending Reinhard Meyer
2011-06-07 10:08   ` Hong Xu
2011-06-07 10:41     ` Reinhard Meyer [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=4DEE0056.7070105@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