Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@lvl7.com>
To: Charlie Brady <charlieb-linux-mips@e-smith.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Broadcom 4702?
Date: Thu, 15 Jan 2004 14:14:07 -0500	[thread overview]
Message-ID: <4006E67F.7010906@lvl7.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0401151343460.17500-100000@allspice.nssg.mitel.com>

Charlie Brady wrote:

>+ifdef CONFIG_BCM4710
>+GCCFLAGS       += -m4710a0kern
> endif
>
>I haven't tried building and running a kernel built without the gcc 
>workarounds, so I don't know whether they are only required for early 
>  
>
I don't know about the 4710 or 4702 (I haven't got around to that yet), 
but the 4704 doesn't seem to need any special flags for building the 
kernel (or anything else).

Of course, YMMV...

John

-- 
John W. Linville
LVL7 Systems, Inc.

  reply	other threads:[~2004-01-15 19:14 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-13 22:00 Broadcom 4702? Charlie Brady
2004-01-13 22:28 ` Jun Sun
2004-01-14 20:49   ` Charlie Brady
2004-01-14 21:05     ` Jim Thompson
2004-01-14 21:15       ` Alan Cox
2004-01-14 21:42         ` Jim Thompson
2004-01-14 22:00           ` Broadcom gcc/binutils mods (Re: Broadcom 4702?) Charlie Brady
2004-01-14 22:53           ` Broadcom 4702? Alan Cox
2004-01-15  1:03           ` Jun Sun
2004-01-15  3:39             ` Charlie Brady
2004-01-15  9:11               ` Dominic Sweetman
2004-01-15 21:33                 ` Alan Cox
2004-01-15 22:46                   ` ilya
2004-01-14 21:50       ` Broadcom gcc/binutils changes (was Re: Broadcom 4702?) Charlie Brady
2004-01-14 21:18     ` Broadcom 4702? Jun Sun
2004-01-15 18:53 ` Charlie Brady
2004-01-15 19:14   ` John W. Linville [this message]
2004-01-15 20:08     ` Broadcom gcc changes (was Re: Broadcom 4702?) Charlie Brady
2004-01-15 20:18       ` Steven J. Hill
2004-01-15 20:25       ` John W. Linville

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=4006E67F.7010906@lvl7.com \
    --to=linville@lvl7.com \
    --cc=charlieb-linux-mips@e-smith.com \
    --cc=linux-mips@linux-mips.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