All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Salter <msalter@redhat.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Sam Ravnborg <sam@ravnborg.org>, linux-arch@vger.kernel.org
Subject: Re: [PATCH 04/24] C6X: build infrastructure
Date: Wed, 24 Aug 2011 10:10:32 -0400	[thread overview]
Message-ID: <1314195033.2344.8.camel@deneb.redhat.com> (raw)
In-Reply-To: <1314193639.16478.3.camel@i7.infradead.org>

On Wed, 2011-08-24 at 14:47 +0100, David Woodhouse wrote:
> On Tue, 2011-08-23 at 09:23 -0400, Mark Salter wrote:
> > 
> > > > +cflags-y := -D__linux__ -D__TMS320C6X__
> > > 
> > > Why is __linux__ and __TMS3206C6X__ neeeded?
> > > and why are they not needed for CHECKFLAGS ?
> > 
> > I think these two defines were left over from trying to compensate
> > for differences between TI compiler and GCC. They aren't needed.
> 
> Last time I looked, the Coda file system was broken and would not
> compile if __linux__ wasn't defined. This is the *only* thing that
> prevents you from building a kernel with a generic $ARCH-elf toolchain,
> IIRC.
> 

The reason we defined it in the C6X Makefile was that the TI compiler
did not define it for us. GCC does define it, so we're good without it
the makefile now.

It looks like coda still needs it as well as drm, scsi/aic7xxx driver,
and a couple other places.

--Mark

  reply	other threads:[~2011-08-24 14:10 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-22 20:09 [PATCH v2 00/24] C6X: New architecture patch set Mark Salter
2011-08-22 20:09 ` [PATCH 01/24] fix default __strnlen_user macro Mark Salter
2011-08-22 20:09 ` [PATCH 02/24] fixed generic page.h for non-zero PAGE_OFFSET Mark Salter
2011-08-22 20:09 ` [PATCH 03/24] add ELF machine define for TI C6X DSPs Mark Salter
2011-08-22 20:09 ` [PATCH 04/24] C6X: build infrastructure Mark Salter
2011-08-22 20:55   ` Sam Ravnborg
2011-08-23 13:23     ` Mark Salter
2011-08-24 13:47       ` David Woodhouse
2011-08-24 14:10         ` Mark Salter [this message]
2011-08-22 20:09 ` [PATCH 05/24] C6X: early boot code Mark Salter
2011-08-22 20:09 ` [PATCH 06/24] C6X: devicetree Mark Salter
2011-08-22 20:09 ` [PATCH 07/24] C6X: memory management and DMA support Mark Salter
2011-08-22 20:09 ` [PATCH 08/24] C6X: process management Mark Salter
2011-08-22 20:55   ` Arnd Bergmann
2011-08-22 20:09 ` [PATCH 09/24] C6X: signal management Mark Salter
2011-08-22 20:09 ` [PATCH 10/24] C6X: time management Mark Salter
2011-08-22 20:09 ` [PATCH 11/24] C6X: interrupt handling Mark Salter
2011-08-22 20:58   ` Arnd Bergmann
2011-08-22 21:08     ` Mark Salter
2011-08-22 21:29     ` Benjamin Herrenschmidt
2011-08-22 20:09 ` [PATCH 12/24] C6X: syscalls Mark Salter
2011-08-22 21:00   ` Arnd Bergmann
2011-08-22 20:09 ` [PATCH 13/24] C6X: traps Mark Salter
2011-08-22 20:09 ` [PATCH 14/24] C6X: clocks Mark Salter
2011-08-22 20:09 ` [PATCH 15/24] C6X: cache control Mark Salter
2011-08-22 20:09 ` [PATCH 16/24] C6X: loadable module support Mark Salter
2011-08-22 21:04   ` Arnd Bergmann
2011-08-22 21:14     ` Mark Salter
2011-08-22 20:09 ` [PATCH 17/24] C6X: ptrace support Mark Salter
2011-08-22 21:07   ` Arnd Bergmann
2011-08-22 20:09 ` [PATCH 18/24] C6X: headers Mark Salter
2011-08-22 21:14   ` Arnd Bergmann
2011-08-23 13:43     ` Mark Salter
2011-08-24  4:53       ` Sam Ravnborg
2011-08-22 20:09 ` [PATCH 19/24] C6X: library code Mark Salter
2011-08-22 20:09 ` [PATCH 20/24] C6X: general SoC support Mark Salter
2011-08-22 20:09 ` [PATCH 21/24] C6X: specific " Mark Salter
2011-08-22 22:21   ` Arnd Bergmann
2011-08-22 20:09 ` [PATCH 22/24] C6X: EMIF - External Memory Interface Mark Salter
2011-08-22 21:17   ` Arnd Bergmann
2011-08-22 21:34     ` Mark Salter
2011-08-22 20:09 ` [PATCH 23/24] C6X: Power and Sleep Controller Mark Salter
2011-08-22 21:20   ` Arnd Bergmann
2011-08-22 21:32     ` Mark Salter
2011-08-22 20:09 ` [PATCH 24/24] C6X: MAINTAINERS Mark Salter
2011-08-22 22:25 ` [PATCH v2 00/24] C6X: New architecture patch set Arnd Bergmann
2011-09-26 14:31   ` Arnd Bergmann
2011-09-26 14:38     ` Mark Salter
2011-08-25 14:53 ` Peter Zijlstra
2011-08-25 16:00   ` Mark Salter
2011-08-25 17:27     ` Peter Zijlstra
2011-08-25 17:34       ` Mark Salter
2011-08-25 17:36         ` Peter Zijlstra
  -- strict thread matches above, loose matches on Subject: below --
2011-08-31 21:26 Mark Salter
2011-08-31 21:26 ` [PATCH 04/24] C6X: build infrastructure Mark Salter
2011-08-31 21:26   ` Mark Salter
2011-08-08 21:44 [PATCH 00/24] C6X: New architecture patch set Mark Salter
2011-08-08 21:44 ` [PATCH 04/24] C6X: build infrastructure Mark Salter
2011-08-09 15:21   ` Arnd Bergmann
2011-08-09 15:56     ` Mark Salter
2011-08-09 19:17   ` Sam Ravnborg

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=1314195033.2344.8.camel@deneb.redhat.com \
    --to=msalter@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=sam@ravnborg.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.