public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stelian Pop <stelian@popies.net>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] AT91 Header File Clarification
Date: Sat, 05 Apr 2008 00:25:50 +0200	[thread overview]
Message-ID: <1207347950.3762.3.camel@voyager.dsnet> (raw)
In-Reply-To: <206b9e70804041332w695212f3me41cfa8f7f182f11@mail.gmail.com>


Le vendredi 04 avril 2008 ? 13:32 -0700, Zac Wheeler a ?crit :
> I have a question about the arrangement of include files for the
> at91sam9 family.
> 
> Is the intention that asm/arch/at91_xxx.h be applicable for all
> at91sam9 microcontrollers, or should they be broken down into subarch
> folders (e.g. asm/arch/at91sam9261/at91_pmc.h)?

They are supposed to be shareable for all at91sam microcontrollers, in
the same way it's done in Linux.

> I am trying to bring up the at91sam9261 on a custom board a little
> ahead of what appears to be the schedule for the at91sam9261ek and I
> want to try to be compatible with the existing format. 

I'm working on support for the at91sam9261, I will probably have a patch
for the end of the next week. Hopefully you can wait until then. If not,
please go ahead.

> I haven't done
> a lot of comparisons between 9260/9261/9263, but for some things (e.g.
> at91_lcd.h) 

There is no such file in u-boot, nor linux iirc. There is a atmel_lcdc.h
in Linux (and I plan importing it into U-Boot, but later...).

Stelian.
-- 
Stelian Pop <stelian@popies.net>

  reply	other threads:[~2008-04-04 22:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-04 20:32 [U-Boot-Users] AT91 Header File Clarification Zac Wheeler
2008-04-04 22:25 ` Stelian Pop [this message]
2008-04-04 23:32   ` Zac Wheeler
2008-04-05 18:02     ` Stelian Pop
2008-04-05  2:08   ` Zac Wheeler
2008-04-05 16:46     ` Stelian Pop

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=1207347950.3762.3.camel@voyager.dsnet \
    --to=stelian@popies.net \
    --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