public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Milton Miller <miltonm@bga.com>
Cc: gerg@uclinux.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH]: linux-2.6.14-uc0 (MMU-less support)
Date: Sat, 5 Nov 2005 20:12:24 +0100	[thread overview]
Message-ID: <20051105191224.GB4493@stusta.de> (raw)
In-Reply-To: <40564dc5fa508b27c752b692f93562f4@bga.com>

On Sat, Nov 05, 2005 at 12:42:42PM -0600, Milton Miller wrote:
> On Tue Nov 01 2005 - 23:01:02 EST, Greg Ungerer wrote:
>...
> >@@ -1190,7 +1190,7 @@
> >
> > config NET_PCI
> > 	bool "EISA, VLB, PCI and on board controllers"
> >-	depends on NET_ETHERNET && (ISA || EISA || PCI)
> >+	depends on NET_ETHERNET && (ISA || EISA || PCI || EMBEDDED)
> > 	help
> > 	  This is another class of network cards which attach directly to the
> > 	  bus. If you have one of those, say Y and read the Ethernet-HOWTO,
> >
> 
> Lots of people turn on EMBEDDED for lots of reasons, asking about
> a lot more drivers seems burdensome.
> 
> Care to create a single intermediate Kconfig var for those?
> Something like "Controllers attached directly to a cpu?"

It seems the real problem is a misunderstanding regarding the semantics 
of EMBEDDED.

EMBEDDED is _not_ strictly connected to any usage of the kernel.

All EMBEDDED does is to offer additional option for people needing a 
small kernel in space-limited environments.

CC_OPTIMIZE_FOR_SIZE is one example, but it also allows to e.g. deselect 
futex support.

(ISA || EISA || PCI || EMBEDDED) doesn't make any sense since this 
dependency expresses the supported busses. If this was required for any 
purpose, it should be reported to find a proper solution.

>...
> > ifdef CONFIG_CC_OPTIMIZE_FOR_SIZE
> >-CFLAGS		+= -Os
> >+CFLAGS		+= -O
> > else
> > CFLAGS		+= -O2
> > endif
> 
> Sees this undoes part of the benefit, perhaps you should add a
> third option.

Even further, I don't see any reason for using -O - the resulting code 
is expected to be both bigger and slower than with -Os.

Is this a workaround for a gcc bug on some platform?

> milton

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2005-11-05 19:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-05 18:42 [PATCH]: linux-2.6.14-uc0 (MMU-less support) Milton Miller
2005-11-05 19:12 ` Adrian Bunk [this message]
2005-11-07  5:50   ` Greg Ungerer
2005-11-07  5:49 ` Greg Ungerer
  -- strict thread matches above, loose matches on Subject: below --
2005-11-02  4:01 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=20051105191224.GB4493@stusta.de \
    --to=bunk@stusta.de \
    --cc=gerg@uclinux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miltonm@bga.com \
    /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