public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jordan Crouse <jordan.crouse@amd.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: AMD Geode GX/LX support
Date: Mon, 03 Oct 2005 21:46:09 +0100	[thread overview]
Message-ID: <1128372369.26992.48.camel@localhost.localdomain> (raw)
In-Reply-To: <20051003195531.GB30975@cosmic.amd.com>

On Llu, 2005-10-03 at 13:55 -0600, Jordan Crouse wrote:
> As I mentioned in the previous e-mail, the GEODEGX1 define as it stands
> is incorrect - the cache line size should be 16 bytes for the GX1.  The 
> GX and LX share a newer core, so it stands, I think that they should have
> a different define.

What makes the cores different ? Cache line size ? If they share the
same kernel options and build then they don't need a new define, the
existing one just need generalising.
  
> I suppose that I should come with something more solid then a gut feeling, 
> though, substantial as my gut may be.

Indeed. With gcc 3.x I ended up with -m486 -falign-functions=0 and that
used to be the settings. I don't know who changed it to pentium-mmx in
the end but I objected to about four different patches that did this
over time and people still kept submitting them.



  reply	other threads:[~2005-10-03 20:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-03 17:47 [PATCH 1/7] AMD Geode GX/LX support Jordan Crouse
2005-10-03 18:05 ` Adrian Bunk
2005-10-03 19:46   ` Jordan Crouse
2005-10-05 19:26     ` Adrian Bunk
2005-10-03 18:08 ` [PATCH 1/7] " Zwane Mwaikambo
2005-10-03 19:01 ` Alan Cox
2005-10-03 19:55   ` Jordan Crouse
2005-10-03 20:46     ` Alan Cox [this message]
2005-10-03 22:22       ` Jordan Crouse

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=1128372369.26992.48.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=jordan.crouse@amd.com \
    --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