mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Antony Pavlov <antonynpavlov@gmail.com>
To: barebox <barebox@lists.infradead.org>
Subject: [RFC] add Tegra support to barebox
Date: Thu, 11 Aug 2011 00:24:27 +0400	[thread overview]
Message-ID: <CAA4bVAH7aOUcCC0aHWLorE_FAaeBdnUvQcj8d3ZCH4W+ko7adA@mail.gmail.com> (raw)

Hi!

I have a Toshiba AC100 smartbook. It is based on Nvidia Tegra 250 T20 chip.
I want to port barebox to it.

I have successfully built and run u-boot for AC100 from
https://github.com/chpec/uboot-ac100.git. This u-boot version has lcd,
serial port and USB support.
There is another tegra support u-boot branch:
https://github.com/muromec/uboot-tegra.git
Also linux has satisfactory tegra support.

I want to discuss source file organization for Tegra and AC100 support
in the barebox.
AFAIK tegra is not resemble to current arm machines, supported by barebox.

For example, this is the comment from barebox tegra source code:

/*
 * Tegra2 uses 2 separate CPUs - the AVP (ARM7TDMI) and the CPU (dual A9s).
 * U-Boot runs on the AVP first, setting things up for the CPU (PLLs,
 * muxes, clocks, clamps, etc.). Then the AVP halts, and expects the CPU
 * to pick up its reset vector, which points here.
 */

I propose such file structure:

  arch/arm/
  arch/arm/boards/toshiba_ac100
  arch/arm/mach-tegra

Has anybody any objections or comments?

-- 
Best regards,
  Antony Pavlov

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2011-08-10 20:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-10 20:24 Antony Pavlov [this message]
2011-08-11  5:01 ` Jean-Christophe PLAGNIOL-VILLARD
2011-08-11  6:12 ` Antony Pavlov
2011-08-11  6:25 ` Sascha Hauer
2011-08-11  7:04   ` Antony Pavlov

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=CAA4bVAH7aOUcCC0aHWLorE_FAaeBdnUvQcj8d3ZCH4W+ko7adA@mail.gmail.com \
    --to=antonynpavlov@gmail.com \
    --cc=barebox@lists.infradead.org \
    /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