From: Vladimir Zapolskiy <vz@mleia.com>
To: "Tomislav Sečen" <tomislav.secen@3plus.hr>
Cc: barebox@lists.infradead.org
Subject: Re: LPC3250 support
Date: Wed, 15 Feb 2012 08:54:48 +0200 [thread overview]
Message-ID: <4F3B56B8.10709@mleia.com> (raw)
In-Reply-To: <CANtfVZ2NJpVLbX65u7qMv2+8n5djAzjv3YLxh8iuwc=vSccXnQ@mail.gmail.com>
Hi,
On 13.02.2012 11:09, Tomislav Sečen wrote:
> Hi all,
>
> I was just wondering about the status of the NXP LPC3250 support in barebox.
>
barebox works on one my LPC3250 board pretty well, but I have to polish
the patches before public publishing in the barebox maillist.
> There are two commit logs on git from Feb 2010, s.hauer adding some files:
> http://uboot.jcrosoft.org/git?p=barebox.git;a=commit;h=9d4bff954fbfb94ba550b2ea3d51d9d723a413e0
>
> http://uboot.jcrosoft.org/git?p=barebox.git;a=commitdiff;h=18be3ca3673300c8f303254c8822e5e954ad8bf0#patch1
>
>
> but those files are not in the current codebase?
>
> Was lpc3250 support dropped, and if yes why?
> Are there any roadblocks to porting the lpc32xx support from u-boot?
>
If it's ok for you to wait a couple of weeks, I'll publish the changes
with basic support of LPC32XX SoCs.
--
With best wishes,
Vladimir
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2012-02-15 6:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-13 9:09 LPC3250 support Tomislav Sečen
2012-02-15 6:54 ` Vladimir Zapolskiy [this message]
2012-02-15 8:37 ` Sascha Hauer
2012-02-15 15:08 ` Tomislav Sečen
2012-02-15 15:08 ` Tomislav Sečen
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=4F3B56B8.10709@mleia.com \
--to=vz@mleia.com \
--cc=barebox@lists.infradead.org \
--cc=tomislav.secen@3plus.hr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.