From: "Randy.Dunlap" <rddunlap@osdl.org>
To: sam@ravnborg.org, "David S. Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org, ultralinux@vger.kernel.org
Cc: Horst von Brand <vonbrand@inf.utfsm.cl>
Subject: Re: SPARC64: Modular floppy?
Date: Tue, 01 Mar 2005 19:49:25 +0000 [thread overview]
Message-ID: <4224C745.4090605@osdl.org> (raw)
In-Reply-To: <200502282007.j1SK7hgE031074@laptop11.inf.utfsm.cl>
(Sam, your From: From: Sam Ravnborg <> really trips thunderbird.)
Sam wrote:
Documentation/kbuild/makefiles.txt is a good start.
For specific questions I can help out.
For this specific case the problem seems to me that you in the ppc64
case want to include floppy-ppc64.S in the build for the PPC64 case.
So something as simple as:
1) rename floppy.c to floppy-core.c
2) Change Makefile to look like:
floppy-y := floppy-core.o
floppy-$(PPC64) += floppy-ppc64.o
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Minor detail, This is for sparc64 (see Subject).
I also see that arch/arm[26]/lib/ has special handling for
floppydma.S, so there'a a model to consider also.
--
~Randy
WARNING: multiple messages have this Message-ID (diff)
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: sam@ravnborg.org, "David S. Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org, ultralinux@vger.kernel.org
Cc: Horst von Brand <vonbrand@inf.utfsm.cl>
Subject: Re: SPARC64: Modular floppy?
Date: Tue, 01 Mar 2005 11:49:25 -0800 [thread overview]
Message-ID: <4224C745.4090605@osdl.org> (raw)
(Sam, your From: From: Sam Ravnborg <> really trips thunderbird.)
Sam wrote:
Documentation/kbuild/makefiles.txt is a good start.
For specific questions I can help out.
For this specific case the problem seems to me that you in the ppc64
case want to include floppy-ppc64.S in the build for the PPC64 case.
So something as simple as:
1) rename floppy.c to floppy-core.c
2) Change Makefile to look like:
floppy-y := floppy-core.o
floppy-$(PPC64) += floppy-ppc64.o
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Minor detail, This is for sparc64 (see Subject).
I also see that arch/arm[26]/lib/ has special handling for
floppydma.S, so there'a a model to consider also.
--
~Randy
next prev parent reply other threads:[~2005-03-01 19:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-28 20:07 SPARC64: Modular floppy? Horst von Brand
2005-02-28 20:07 ` Horst von Brand
2005-02-28 23:51 ` David S. Miller
2005-02-28 23:51 ` David S. Miller
2005-03-01 1:53 ` Horst von Brand
2005-03-01 1:53 ` Horst von Brand
2005-03-01 17:25 ` Randy.Dunlap
2005-03-01 17:25 ` Randy.Dunlap
2005-03-01 19:26 ` Horst von Brand
2005-03-01 19:26 ` Horst von Brand
2005-03-01 19:34 ` Randy.Dunlap
2005-03-01 19:34 ` Randy.Dunlap
2005-03-01 23:04 ` David S. Miller
2005-03-01 23:04 ` David S. Miller
2005-03-01 19:49 ` Randy.Dunlap [this message]
2005-03-01 19:49 ` Randy.Dunlap
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=4224C745.4090605@osdl.org \
--to=rddunlap@osdl.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=ultralinux@vger.kernel.org \
--cc=vonbrand@inf.utfsm.cl \
/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.