From: Greg Ungerer <gerg@snapgear.com>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: David Woodhouse <dwmw2@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: [patch] Re: 2.5.56: undefined reference to `_ebss' from drivers/mtd/maps/uclinux.c
Date: Fri, 21 Mar 2003 10:48:09 +1000 [thread overview]
Message-ID: <3E7A6149.2010308@snapgear.com> (raw)
In-Reply-To: <20030320160008.GB3174@fs.tum.de>
Hi Adrian,
This seems reasonable to me. It is after all targeted at uclinux.
I suspect noone with VM setups would be much interrested in using
it anyway.
Patch looks good to me.
Regards
Greg
Adrian Bunk wrote:
> On Thu, Mar 20, 2003 at 03:59:28PM +0100, Adrian Bunk wrote:
>
>>...
>>It might not be a solution for the whole issue, but is it intentionally
>>that it's possible to enable CONFIG_MTD_UCLINUX on non-uClinux
>>architectures or should an appropriate dependency be added to the
>>Kconfig file?
>
>
> The following patch should do what I was thinking of:
>
> --- linux-2.5.65-full/drivers/mtd/maps/Kconfig.old 2003-03-20 16:56:25.000000000 +0100
> +++ linux-2.5.65-full/drivers/mtd/maps/Kconfig 2003-03-20 16:56:45.000000000 +0100
> @@ -348,7 +348,7 @@
>
> config MTD_UCLINUX
> tristate "Generic uClinux RAM/ROM filesystem support"
> - depends on MTD_PARTITIONS
> + depends on MTD_PARTITIONS && !MMU
> help
> Map driver to support image based filesystems for uClinux.
>
>
>
> Any comments on whether this is correct?
>
>
> cu
> Adrian
>
--
------------------------------------------------------------------------
Greg Ungerer -- Chief Software Wizard EMAIL: gerg@snapgear.com
SnapGear Pty Ltd PHONE: +61 7 3435 2888
825 Stanley St, FAX: +61 7 3891 3630
Woolloongabba, QLD, 4102, Australia WEB: www.SnapGear.com
prev parent reply other threads:[~2003-03-21 0:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-12 9:55 2.5.56: undefined reference to `_ebss' from drivers/mtd/maps/uclinux.c Adrian Bunk
2003-01-13 7:23 ` Greg Ungerer
2003-03-20 14:59 ` Adrian Bunk
2003-03-20 16:00 ` [patch] " Adrian Bunk
2003-03-21 0:48 ` Greg Ungerer [this message]
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=3E7A6149.2010308@snapgear.com \
--to=gerg@snapgear.com \
--cc=bunk@fs.tum.de \
--cc=dwmw2@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox