From: Erwin Rol <mailinglists@erwinrol.com>
To: Antony Pavlov <antonynpavlov@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: Tegra 2
Date: Fri, 28 Oct 2011 15:22:03 +0200 [thread overview]
Message-ID: <4EAAAC7B.2030608@erwinrol.com> (raw)
In-Reply-To: <CAA4bVAEMFedmy71RUk1LKbfG-E13UoMKSBeKncLG3p=dnjVczg@mail.gmail.com>
Hey Antony,
On 28-10-2011 15:15, Antony Pavlov wrote:
> On 28 October 2011 12:36, Erwin Rol<mailinglists@erwinrol.com> wrote:
>> Hey all,
>>
>> If I remember right a while back someone mentioned Tegra 2 here. I would
>> like to ask what the status is of Tegra 2 support. Or if there is support at
>> all ? :-)
>
> There is initial support for Tegra 2 in my private git.
>
> I shall send the patches in a while.
>
> The current status:
> * barebox can start on Toshiba AC100 smartbook after U-Boot (not
> mainstream U-Boot);
Is this because of the tegra 2 CPU or because of the AC100 ? I am
looking into the Tegra 2 board from MSC (true embedded board)
> * barebox support console on Tegra's internal serial port;
> * barebox support USB host controller and Ethernet-USB
> Barebox does not support:
> * cache&mmu initialization;
> * graphical output;
> * i2c (so barebox can't use AC100's keyboard for input);
> * mmc controller.
>
> Currently, I'm working on porting of tegra-fb and i2c support.
I should get my board somewhere next week (I hope), and will start to
take a deeper look into things.
Most important thing will be, does it boot Linux and how fast does it do
that.
- Erwin
PS: do you have any general links of info on the Tegra 2 cpu ?
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2011-10-28 13:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-28 8:36 Erwin Rol
2011-10-28 9:25 ` Sascha Hauer
2011-10-28 13:15 ` Antony Pavlov
2011-10-28 13:22 ` Erwin Rol [this message]
2011-10-28 14:08 ` 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=4EAAAC7B.2030608@erwinrol.com \
--to=mailinglists@erwinrol.com \
--cc=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