public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: hanumant <hanumant@codeaurora.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] Porting U-boot
Date: Mon, 31 Oct 2011 16:57:57 -0700	[thread overview]
Message-ID: <4EAF3605.9060503@codeaurora.org> (raw)


I am trying to port u-boot to multiple soc/boards from an arm vendor.
I would appreciate any input on the following approach

1)The controller instance on various SOC are the same with minor 
differences in the fifo size, gpios, clocks.

2)In order to help the porting effort, my idea is to add soc/board 
neutral driver header files under the include/asm/ directory.
Possibly creating a vendor directory under there ie
arch/arm/include/asm/($vendor)/
(Different from the soc specific header files arch-$SOC)

3)Implement driver in respective driver category drivers/<$category>

4)Allow the SOC specific files to define the resources for specific 
peripherals based on the header files from 2)

Thanks

             reply	other threads:[~2011-10-31 23:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-31 23:57 hanumant [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-01-30  5:58 [U-Boot] Porting U-boot JYOTI DUBEY
2014-01-30 13:26 ` Michal Suchanek

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=4EAF3605.9060503@codeaurora.org \
    --to=hanumant@codeaurora.org \
    --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