From: Jeff Garzik <jeff@garzik.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: "Subbrathnam, Swaminathan" <swami.iyer@ti.com>,
Sergei Shtylyov <sshtylyov@ru.mvista.com>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: sata AHCI controller over non-PCI bus
Date: Sun, 16 Aug 2009 16:18:43 -0400 [thread overview]
Message-ID: <4A8869A3.7020504@garzik.org> (raw)
In-Reply-To: <1250436892.3856.87.camel@mulgrave.site>
On 08/16/2009 11:34 AM, James Bottomley wrote:
> Can't you get the best of both worlds? Do the separation but
> artificially glue them together again as a module at link time. This
> solves the current distro problem and you can remove the linker hack as
> soon as the distros get their act together.
>
> James
>
> ---
>
> diff --git a/drivers/ata/Makefile b/drivers/ata/Makefile
> index 9f7b500..10101d7 100644
> --- a/drivers/ata/Makefile
> +++ b/drivers/ata/Makefile
> @@ -1,8 +1,10 @@
>
> obj-$(CONFIG_ATA) += libata.o
>
> -obj-$(CONFIG_SATA_AHCI) += libahci.o ahci.o
> -obj-$(CONFIG_SATA_ACARD_AHCI) += libahci.o acard-ahci.o
> +obj-$(CONFIG_SATA_AHCI) += ahci_mod.o
> +obj-ahci_mod-y += libahci.o ahci.o
> +obj-ahci_mod-$(CONFIG_SATA_ACARD_AHCI) += acard-ahci.o
> +obj-ahci_mod-$(CONFIG_SATA_MV_AHCI) += mv-ahci.o
Yeah, that could definitely be an option...
Jeff
next prev parent reply other threads:[~2009-08-16 20:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-10 8:18 sata AHCI controller over non-PCI bus Subbrathnam, Swaminathan
2009-08-10 9:03 ` Sergei Shtylyov
2009-08-10 9:20 ` Sergei Shtylyov
2009-08-10 9:22 ` Subbrathnam, Swaminathan
2009-08-16 12:53 ` Jeff Garzik
[not found] ` <4A88014D.9060309-o2qLIJkoznsdnm+yROfE0A@public.gmane.org>
2009-08-16 14:35 ` Subbrathnam, Swaminathan
2009-08-16 14:35 ` Subbrathnam, Swaminathan
2009-08-16 15:34 ` James Bottomley
2009-08-16 20:18 ` Jeff Garzik [this message]
2009-08-16 16:55 ` Robert Hancock
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=4A8869A3.7020504@garzik.org \
--to=jeff@garzik.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sshtylyov@ru.mvista.com \
--cc=swami.iyer@ti.com \
/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.