All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@fs.tum.de>
To: "Richard B. Johnson" <root@chaos.analogic.com>, robert@schwebel.de
Cc: cliff white <cliffw@osdl.org>,
	piggin@cyberone.com.au, mpm@selenic.com,
	linux-kernel@vger.kernel.org
Subject: Re: [1/4] better i386 CPU selection
Date: Sat, 17 Jan 2004 03:15:32 +0100	[thread overview]
Message-ID: <20040117021532.GH12027@fs.tum.de> (raw)
In-Reply-To: <Pine.LNX.4.53.0401161425110.31018@chaos>

On Fri, Jan 16, 2004 at 02:32:39PM -0500, Richard B. Johnson wrote:
> On Fri, 16 Jan 2004, cliff white wrote:
> 
> > On Sat, 10 Jan 2004 01:52:32 +0100
> > Adrian Bunk <bunk@fs.tum.de> wrote:
> >
> >
> > > Changes:
> 
> > > - AMD Elan is a different subarch, you can't configure a kernel that
> > >   runs on both the AMD Elan and other i386 CPUs
> 
> NO! NO!  This prevents development of an AMD embeded system on an
> "ordinary" machine like this one (Pentium IV). The fact that the
> timer runs at a different speed means nothing, one just sets the
> workstation time every day. Please do NOT do this. It prevents
> important usage.

What problems exacly are you referring to?

Besides the AMD Elan cpufreq driver I see nothing where CONFIG_MELAN
gave you any real difference (except your highest goal is to avoid a
recompilation when switching from the Pentium 4 to the AMD Elan - but I
doubt the really "prevents development").

But I'm not religious about this issue. Let Robert decide, the Elan 
support is his child.

> > > - added optimizing CFLAGS for the AMD Elan
> 
> There are no such different "optimizations" for ELAN.

What's wrong wih the -march=i486 Robert suggested?

> Cheers,
> Dick Johnson

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


  parent reply	other threads:[~2004-01-17  2:15 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-06  5:48 2.6.1-rc1-tiny2 Matt Mackall
2004-01-06  6:33 ` 2.6.1-rc1-tiny2 Nick Piggin
2004-01-06  6:46   ` 2.6.1-rc1-tiny2 Matt Mackall
2004-01-06  7:08     ` 2.6.1-rc1-tiny2 Nick Piggin
2004-01-10  0:46       ` 2.6.1-rc1-tiny2 Adrian Bunk
2004-01-10  0:50         ` [0/4] better i386 CPU selection Adrian Bunk
2004-01-10  0:52         ` [1/4] " Adrian Bunk
2004-01-10 11:04           ` Wichert Akkerman
2004-01-11  3:13             ` Adrian Bunk
2004-01-14 20:49               ` [-mm patch] " Adrian Bunk
2004-01-16 19:15           ` [1/4] " cliff white
2004-01-16 19:32             ` Richard B. Johnson
2004-01-17  0:01               ` Andrew Morton
2004-01-17  2:57                 ` Adrian Bunk
2004-01-19 15:14                   ` John Stoffel
2004-01-19 23:42                     ` Nick Piggin
2004-01-17  2:15               ` Adrian Bunk [this message]
2004-01-17  9:13                 ` Robert Schwebel
2004-01-20 22:10                   ` Adrian Bunk
2004-01-20 22:31                     ` Richard B. Johnson
2004-01-20 22:47                     ` George Anzinger
2004-01-17 10:01                 ` aeriksson
2004-01-10  0:57         ` [2/4] move "struct movsl_mask movsl_mask" to usercopy.c Adrian Bunk
2004-01-10  0:57         ` [3/4] proof of concept: make arch/i386/kernel/cpu/Makefile CPU specific Adrian Bunk
2004-01-10  0:58         ` [4/4] proof of concept: make arch/i386/kernel/cpu/mtrr/Makefile " Adrian Bunk
2004-01-10 22:14         ` 2.6.1-rc1-tiny2 Matt Mackall
2004-01-12  2:20           ` 2.6.1-rc1-tiny2 Nick Piggin
2004-01-07 14:06 ` 2.6.1-rc1-tiny2 Jens Axboe
2004-01-07 18:50   ` 2.6.1-rc1-tiny2 Matt Mackall
2004-01-07 19:27     ` 2.6.1-rc1-tiny2 Mitchell Blank Jr
2004-01-07 20:10       ` 2.6.1-rc1-tiny2 Matt Mackall
2004-01-07 21:41         ` 2.6.1-rc1-tiny2 Trond Myklebust
2004-01-07 21:10     ` 2.6.1-rc1-tiny2 Jens Axboe
2004-01-07 21:30       ` 2.6.1-rc1-tiny2 Matt Mackall

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=20040117021532.GH12027@fs.tum.de \
    --to=bunk@fs.tum.de \
    --cc=cliffw@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpm@selenic.com \
    --cc=piggin@cyberone.com.au \
    --cc=robert@schwebel.de \
    --cc=root@chaos.analogic.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 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.