From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Schwingen Date: Fri, 04 Feb 2011 00:00:06 +0100 Subject: [U-Boot] [STATUS] v2011.03-rc1 released In-Reply-To: <20110203192712.A94E6D81AE2@gemini.denx.de> References: <20110202215519.7F04ECDE29B@gemini.denx.de> <4D4ACBA0.9030607@discworld.dascon.de> <20110203192712.A94E6D81AE2@gemini.denx.de> Message-ID: <4D4B3376.30108@discworld.dascon.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.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