From: Ian Molton <spyro@f2s.com>
To: Russell King <rmk@arm.linux.org.uk>
Cc: alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org
Subject: Re: ARM26 [NEW ARCHITECTURE]
Date: Tue, 13 May 2003 17:10:02 +0100 [thread overview]
Message-ID: <20030513171002.741f080b.spyro@f2s.com> (raw)
In-Reply-To: <20030513170029.B15172@flint.arm.linux.org.uk>
On Tue, 13 May 2003 17:00:29 +0100
Russell King <rmk@arm.linux.org.uk> wrote:
> The basic idea is to rip out the arm26 code from arch/arm and
> include/asm-arm, thereby allowing include/asm-arm/proc-armv to
> be collapsed into include/asm-arm, removing some clutter.
Yep.
speaking of which - let me know when you want the next round of patches
to remove the ARM26 stuff from arch/arm please ;-)
> Separating it out should also allow arm26 to shrink down to
> something smaller, which is fairly critical for these machines.
Yep. the [compiled size of the] kernel has already begun to decrease,
and its looking quite promising (If I ever get the time to finish it!)
I just want to get it 'out there' so the couple of other folks
interested can start hacking on it too.
I have an ide driver too, if anyone wants to submit it for the
mainstream kernel. It drives SIMTEC IDE cards, found in Acorn machines,
and is, of course, non-invasive to the tree. Its for 2.4. I'd imagine
Russell would be happy to let someone else take it off his hands?
(Russell?)
--
Spyros lair: http://www.mnementh.co.uk/
Do not meddle in the affairs of Dragons, for you are tasty and good with
ketchup.
Systems programmers keep it up longer.
next prev parent reply other threads:[~2003-05-13 15:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-13 14:33 ARM26 [NEW ARCHITECTURE] Ian Molton
2003-05-13 14:23 ` Alan Cox
2003-05-13 15:30 ` Ian Molton
2003-05-13 15:08 ` Alan Cox
2003-05-13 16:00 ` Russell King
2003-05-13 16:10 ` Ian Molton [this message]
2003-05-13 19:35 ` Geert Uytterhoeven
2003-05-13 20:35 ` Steven Cole
2003-05-13 20:43 ` Geert Uytterhoeven
2003-05-13 23:13 ` Alan Cox
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=20030513171002.741f080b.spyro@f2s.com \
--to=spyro@f2s.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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