mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Krzysztof Halasa <khc@pm.waw.pl>
To: barebox@lists.infradead.org
Subject: New round of my IXP42x patches
Date: Thu, 06 Jan 2011 15:48:38 +0100	[thread overview]
Message-ID: <m38vyym6k9.fsf@intrepid.localdomain> (raw)

I've fixed the 3 remaining patches:
1.  Fix error handling with malloc, memalign etc. Introduce xmemalign().

    The idea is to panic() when there is no memory available for normal
    operation. Exception: code which can consume arbitrary amount of RAM
    (example: files allocated in ramfs) must report error instead of
    panic().

    This patch also fixes code which didn't check for NULL from malloc()
    etc.

    Usage: malloc(), xmemalign() return NULL when out of RAM.
    xmalloc(), xmemalign() always return non-NULL or panic().

(I've removed the clkdev changes as requested)

2.  ARM: support big/little endian switching in "bootz".
    I've renamed CONFIG_BOOTZ_ENDIANNESS_SWITCH to
                 CONFIG_BOOT_ENDIANNESS_SWITCH anticipating support for
    endianness switching for bootm and bootu, either automatic or with
    additional parameter.

3. ARM: Add support for IXP4xx CPU and for Goramo Multilink router
   platform.

Fixed the memalign() -> xmemalign() usage in IXP4xx Ethernet driver.

I'm currently using Barebox with these three patches applied.
-- 
Krzysztof Halasa

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2011-01-06 14:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-06 14:48 Krzysztof Halasa [this message]
2011-01-06 15:23 ` [PATCH 1/3] Fix error handling with malloc, memalign etc. Introduce xmemalign() Krzysztof Halasa
2011-01-06 15:25 ` [PATCH 2/3] ARM: support big/little endian switching in "bootX" Krzysztof Halasa
2011-01-06 15:26 ` [PATCH 3/3] ARM: Add support for IXP4xx CPU and for Goramo Multilink router platform Krzysztof Halasa
2011-01-06 23:36   ` Jean-Christophe PLAGNIOL-VILLARD
2011-01-08 12:16     ` Krzysztof Halasa
2011-01-08 13:55       ` Sascha Hauer
2011-01-08 17:35         ` Krzysztof Halasa
2011-01-08 18:10           ` Jean-Christophe PLAGNIOL-VILLARD
2011-01-09 12:03             ` Krzysztof Halasa
2011-01-08 13:33     ` Krzysztof Halasa

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=m38vyym6k9.fsf@intrepid.localdomain \
    --to=khc@pm.waw.pl \
    --cc=barebox@lists.infradead.org \
    /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