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] about at91 board in uboot
Date: Fri, 17 Jun 2011 09:17:22 +0200	[thread overview]
Message-ID: <4DFAFF82.6010705@emk-elektronik.de> (raw)
In-Reply-To: <DB7B9DAED0B660469F69536325A1D65A022562BB@penmb01.corp.atmel.com>

Dear Lin,
> The following is the status XU Hong is reporting to me on u-boot-atmel/master.  
> I saw it has been silent for 2 days. I don?t know if we could do something to help maintain all the boards.
> I will try to help allocate some of my people to handling missing parts for our EK.

I send a message about 2 days ago, asking that the SoC relevant parts are changed in a manner
consistent with the changes for the 9260, like in
at91sam9260_devices.c, at91sam9260.h, at91sam9260_matrix.h.

Once that is done, and added to u-boot-atmel/master, the board specific
patches should be rebased on that and submitted.

Since nobody did volunteer so far, I was going to edit the SoC specific parts and submit them,
but unfortunately that could take some time (until next week maybe, I was going to start today
with that, but have paid work to finish as well :) )

I am not fond of quick and dirty solutions here,
the boards are not going to be removed with this u-boot release,
but will be after if no progress is seen - but we do have progress here - so no need to panic.

So lets do it in two distinct steps:
1. fix SoCs
2. fix boards

> 9261 soc & ek have been merged to atmel branch.
> 9rl ? v3 patches have been pushed out just now and shall be ok.
> 9263 ? soc part has been merged into atmel branch. I?m asking the ek part.
> 9g45 -  patches were sent by 3rd party.

The SoC specific changes will/should be based before those patches, and will
replace the current ones.

---

Original Message:

Dear Friends,

I have received several different patches reworking

"at91sam*_devices.c"

and

"at91sam9*.h".

Lokking at them, none of them is completely done the way the files for
at91sam9260 are done.

Examples:

9260, 9263: ATMEL_ID_USART0
9261: ATMEL_ID_US0

9260 uses the CONFIG_AT91_GPIO_PULLUP define, the others do not.

9261 still uses the CONFIG_USARTx defines.

Please have a look at at91sam9260 as a reference.

We do need a properly fixed SoC port for 9261, 9263 and the others
before individual board ports can be fixed.

Just because there is a sudden rush to get things fixed for the next release
should NOT tempt us to get in interim versions.

With Best Regards,
Reinhard

       reply	other threads:[~2011-06-17  7:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <DB7B9DAED0B660469F69536325A1D65A022562BB@penmb01.corp.atmel.com>
2011-06-17  7:17 ` Reinhard Meyer [this message]
2011-06-17  7:50   ` [U-Boot] about at91 board in uboot Hong Xu

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=4DFAFF82.6010705@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