public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Michael Schwingen <rincewind@discworld.dascon.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [STATUS] v2011.03-rc1 released
Date: Thu, 03 Feb 2011 16:37:04 +0100	[thread overview]
Message-ID: <4D4ACBA0.9030607@discworld.dascon.de> (raw)
In-Reply-To: <20110202215519.7F04ECDE29B@gemini.denx.de>

Wolfgang Denk wrote:
> Hello  everybody:
>
> * U-Boot v2011.03-rc1 was released on Wed, 02 Feb 2011.
>
> * Release "v2011.03" is scheduled in 39 days - on March 13, 2011.
>
> Please help testing, and check if all your relevant patches have been
> included.
>
>
> 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?

I think I have IXP425 mostly in shape - my own boards work, and IXDP425 
boots up and basically works. PCI is still a working area: I pulled out 
most of the old, IXP-specific code and changed the PCI code to use 
u-boot's PCI infrastructure.

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.

Otherwise, I could leave out the whole PCI area and only provide patches 
for the boards without PCI, leaving IXP PCI in its current broken state.

cu
Michael

  parent reply	other threads:[~2011-02-03 15:37 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 [this message]
2011-02-03 19:27   ` Wolfgang Denk
2011-02-03 23:00     ` Michael Schwingen
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=4D4ACBA0.9030607@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