From: Michael Schwingen <rincewind@discworld.dascon.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [STATUS] v2011.03-rc1 released
Date: Fri, 04 Feb 2011 00:00:06 +0100 [thread overview]
Message-ID: <4D4B3376.30108@discworld.dascon.de> (raw)
In-Reply-To: <20110203192712.A94E6D81AE2@gemini.denx.de>
Am 02/03/2011 08:27 PM, schrieb Wolfgang Denk:
> Dear Michael Schwingen,
>
> In message <4D4ACBA0.9030607@discworld.dascon.de> you wrote:
>>> Note that still a large number of ARM boards are broken. I hope many
>>> people join the efforts and fix all the currently broken boards.
>>> Thanks in advance to everybody who lends a helping hand.
>>>
>> What is the time frame?
> The original entry in doc/feature-removal-schedule.txt said:
>
> Support for CONFIG_SYS_ARM_WITHOUT_RELOC will be removed
> after release v2011.03; all boards that have not been
> converted by then, i. e. that are still broken then, are
> considered unmaintained and without interest for the
> community and will be removed as well.
>
> Support for CONFIG_SYS_ARM_WITHOUT_RELOC has already been dropped,
> which makes the problem obvious, but the time frame remains: boards
> that are not working after v2011.03 has been released are treated as
> wolfsheads i. e. may be killed on sight by anybody who submits such a
> patch.
>
> Of course, you can still object to such patches, but then you will
> probably be asked to provide fixes to make the respective board
> working before the end of the merge window.
Sorry, unclear wording on my part - I meant "what is the timeframe to
submit the final version of the patches for inclusion into the current
release".
>> This works fine for configuration, and I can dump and modify memory (eg.
>> the bootrom on a E1000 card), but I can't get any of the ethernet
>> drivers to work - possibly due to endian issues, but this might take
>> some time to sort out.
>>
>> Would it be OK to commit this as-is, knowing it may require some further
>> fixups? At least it does work better than before.
> From my point of view this is OK. And if you are actually working on
> this, then there is little danger. We will not remove a board that is
> visibly actively being maintained,
OK - I will proceed that route. I think I can clean this up for
submission during the next weekend.
cu
Michael
next prev parent reply other threads:[~2011-02-03 23:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-02 21:55 [U-Boot] [STATUS] v2011.03-rc1 released Wolfgang Denk
2011-02-03 3:47 ` John Rigby
2011-02-03 4:35 ` Paulraj, Sandeep
2011-02-03 7:53 ` Nobuhiro Iwamatsu
2011-02-03 13:56 ` Ben Gardiner
2011-02-03 15:37 ` Michael Schwingen
2011-02-03 19:27 ` Wolfgang Denk
2011-02-03 23:00 ` Michael Schwingen [this message]
2011-02-03 17:52 ` Alexander Holler
2011-02-04 17:23 ` Scott Wood
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=4D4B3376.30108@discworld.dascon.de \
--to=rincewind@discworld.dascon.de \
--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