From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Robin Getz <rgetz@blackfin.uclinux.org>
Cc: Greg Ungerer <gerg@snapgear.com>,
linux-kernel@vger.kernel.org, David Howells <dhowells@redhat.com>,
Paul Mundt <lethal@linux-sh.org>
Subject: Re: [PATCH]: linux-2.6.21-uc0 (MMU-less updates)
Date: Sun, 6 May 2007 12:44:54 +0100 [thread overview]
Message-ID: <20070506114453.GB29643@flint.arm.linux.org.uk> (raw)
In-Reply-To: <200705041212.03614.rgetz@blackfin.uclinux.org>
On Fri, May 04, 2007 at 12:12:03PM -0400, Robin Getz wrote:
> > > Depending on how TASK_SIZE is defined - it looks like everyone else
> > > forces it to end of memory, except 68k[nommu].
> > >
> > > asm-arm/memory.h:#define TASK_SIZE (CONFIG_DRAM_SIZE)
> >
> > That is one way to handle it. Have you followed all the other
> > uses of TASK_SIZE and verified it is not a problem?
>
> No, I assumed that Russell/David were smarter than we were, and that doing so
> would not be a problem :)
Don't look at me - the above came from Hyok, and I just assumed that it
was correct without really understanding it.
I've noticed though that Hyok's gone rather quiet, so I'm not sure
whether we'll ever get ARM uclinux integration complete.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
next prev parent reply other threads:[~2007-05-06 11:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-02 5:23 Greg Ungerer
2007-05-02 8:58 ` Robin Getz
2007-05-02 11:32 ` Greg Ungerer
2007-05-03 10:55 ` Robin Getz
2007-05-03 11:03 ` Greg Ungerer
2007-05-03 11:35 ` Robin Getz
2007-05-03 13:30 ` Greg Ungerer
2007-05-04 16:12 ` Robin Getz
2007-05-06 11:44 ` Russell King [this message]
2007-05-07 11:59 ` Greg Ungerer
2007-05-07 1:24 ` Paul Mundt
2007-05-02 9:06 ` Christoph Hellwig
2007-05-02 10:37 ` Greg Ungerer
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=20070506114453.GB29643@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=dhowells@redhat.com \
--cc=gerg@snapgear.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rgetz@blackfin.uclinux.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
Powered by JetHome