All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@snapgear.com>
To: linux-kernel@vger.kernel.org
Subject: [PATCH]: linux-2.6.10-uc0 (MMU-less fixups)
Date: Thu, 06 Jan 2005 16:54:03 +1000	[thread overview]
Message-ID: <41DCE08B.5010507@snapgear.com> (raw)

Hi All,

An update of the uClinux (MMU-less) fixups against 2.6.10.

I have completely reworked the startup code for the m68knommu
architectures. What was dozens of files is now a few common
varients for the obviously different sub-families (coldfire,
68x328 and 68360).

http://www.uclinux.org/pub/uClinux/uClinux-2.6.x/linux-2.6.10-uc0.patch.gz


Change log:

. import of linux-2.6.10                       <gerg@snapgear.com>
. rework head start code for m68knommu         <gerg@snapgear.com>
. auto-detect SDRAM size on most platforms     <gerg@snapgear.com>
. combine common 68x328 config code            <gerg@snapgear.com>
. remove duplicate M5275EVB entry in Kconfig   <gerg@snapgear.com>
. auto-generate m68knommu/entry.S offsets      <phdm@macqel.be>
. remove duplication with KTHREAD_SIZE         <phdm@macqel.be>
. fix stack alignment on trap return           <phdm@macqel.be>
. reduce code size in FEC ethernet driver      <phdm@macqel.be>
. export lib udelay symbold                    <gerg@snapgear.com>
. cleanup atomic and bitops macros             <phdm@macqel.be>
. remove unused io_hw_swap.h                   <domen@coderock.org>


Regards
Greg



------------------------------------------------------------------------
Greg Ungerer  --  Chief Software Dude       EMAIL:     gerg@snapgear.com
SnapGear -- a CyberGuard Company            PHONE:       +61 7 3435 2888
825 Stanley St,                             FAX:         +61 7 3891 3630
Woolloongabba, QLD, 4102, Australia         WEB: http://www.SnapGear.com


                 reply	other threads:[~2005-01-06  6:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=41DCE08B.5010507@snapgear.com \
    --to=gerg@snapgear.com \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.