From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Has versatilepb board support permanently been dropped in latest u-boot?
Date: Wed, 29 Nov 2017 13:45:37 -0500 [thread overview]
Message-ID: <20171129184537.GA3587@bill-the-cat> (raw)
In-Reply-To: <CAEK-7JJvMd8gET6by6u0fDdmJ-Cpe1HZJrjYuvHO9DJPMkL2Ow@mail.gmail.com>
On Tue, Nov 28, 2017 at 10:32:49PM -0800, Dipanjan Das wrote:
> In order to compile u-boot for versatilepb, I had to use [this](
> https://github.com/toyoshim/u-boot) version of u-boot that contains a patch
> for the board with this commit message.:
>
> "Restore ARM versatile platform only for QEMU
> The port was removed for mssing deadline to migrate the generic-board.
> Thie patch revive the port for QEMU arm system emulation mode.
>
> Not verified well, but it boots."
>
> The [official source](https://github.com/u-boot/u-boot) doesn't have a
> configs/versatilepb_defconfig, hence can't be built for versatilepb. Has
> versatilepb board support permanently been dropped in latest u-boot?
The platform was indeed dropped due to lack of maintainer. A new
maintainer that would be willing to keep the platform up to date with
relevant modern changes would be appreciated and could restore support,
thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20171129/4a391925/attachment.sig>
next prev parent reply other threads:[~2017-11-29 18:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 6:32 [U-Boot] Has versatilepb board support permanently been dropped in latest u-boot? Dipanjan Das
2017-11-29 18:45 ` Tom Rini [this message]
2017-11-29 19:43 ` Tuomas Tynkkynen
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=20171129184537.GA3587@bill-the-cat \
--to=trini@konsulko.com \
--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