All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: "Subbrathnam, Swaminathan" <swami.iyer@ti.com>
Cc: 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 08:53:33 -0400	[thread overview]
Message-ID: <4A88014D.9060309@garzik.org> (raw)
In-Reply-To: <FCCFB4CDC6E5564B9182F639FC35608702F59891CB@dbde02.ent.ti.com>

Subbrathnam, Swaminathan wrote:
> Jeff,
> 	From the below link (from Sergei) it seems that you have already re-factored the AHCI implementation dependency on PCI.  I would like to add support for the OMAPL138 SATA on top of your changes.  That would be the ideal way forward for me.
> 
> 	Have the ahci re-factoring changes queued for mainline merge already?  I just joined the list and hence do not know the status.
> 
> Sergei,
> 	Appreciate the response.

I store the refactoring in git, on the "libahci" branch of
git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git

Unfortunately, I am having second thoughts about an element of the 
current design.  With current Linux distributions, they do not appear to 
deal well with the multi-module dependency libata -> libahci -> ahci. 
If I had to guess, I would say that mkinitrd creation tools only look at 
one tree level's worth of kernel module dependencies.

Thus, ahci would wind up -not- in initrd, in a libahci solution.

I am thinking that I will just add Marvell and ATP support to ahci.c, 
and let someone else deal with libahci separation -- which is still needed.

At this point, I would rather get Marvell/ATP support into users' hands, 
rather than wait for distros to catch up to modern technology.

	Jeff





  reply	other threads:[~2009-08-16 12:53 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 [this message]
     [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
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=4A88014D.9060309@garzik.org \
    --to=jeff@garzik.org \
    --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.