All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org, Bernhard Reiter <bernhard@intevation.de>,
	debian-powerpc@lists.debian.org, paulus@samba.org
Subject: Re: compile quirk linux-2.6.24 (with workaround)
Date: Tue, 5 Feb 2008 10:10:17 -0600	[thread overview]
Message-ID: <20080205161017.GA26196@lixom.net> (raw)
In-Reply-To: <20080205093820.5918a216@zod.rchland.ibm.com>

On Tue, Feb 05, 2008 at 09:38:20AM -0600, Josh Boyer wrote:

> Taking a step back though, there will always be odd cases like this as
> we move forward.  Toolchain XXX will eventually not support instruction
> YYYY which will eventually be used, etc.  I'll try to make this
> specific case work because it's scope is quite limited.  But this
> problem as a whole will still remain.

Worst case, if it's only a couple of instructions, they could be covered
the way we usually handle new instructions in the ISA: make a macro for
them and hand-encode them.

See real_205_{read,write}b() in arch/powerpc/kernel/misc_64.S for
example.


-Olof

  reply	other threads:[~2008-02-05 16:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-03 16:29 compile quirk linux-2.6.24 (with workaround) Bernhard Reiter
2008-02-04  9:51 ` Sven Luther
2008-02-04 10:26   ` Bernhard Reiter
2008-02-04 17:34     ` Grant Likely
2008-02-05 13:08   ` Josh Boyer
2008-02-05 14:39     ` Sven Luther
2008-02-05 15:15       ` Josh Boyer
2008-02-05 15:24         ` Grant Likely
2008-02-05 15:38           ` Josh Boyer
2008-02-05 16:10             ` Olof Johansson [this message]
2008-02-06 10:07             ` Bernhard Reiter
2008-02-19  2:52             ` Josh Boyer
2008-02-22 14:50               ` Bernhard Reiter
2008-02-25 11:56                 ` Bernhard Reiter
2008-03-03 17:26                   ` Bernhard Reiter
2008-02-04 21:01 ` Josh Boyer

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=20080205161017.GA26196@lixom.net \
    --to=olof@lixom.net \
    --cc=bernhard@intevation.de \
    --cc=debian-powerpc@lists.debian.org \
    --cc=jwboyer@linux.vnet.ibm.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.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 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.