From: "Byron Bradley" <byron.bbradley@gmail.com>
To: "Mark Lord" <liml@rtr.ca>
Cc: saeed <saeed@marvell.com>, "Jeff Garzik" <jeff@garzik.org>,
linux-ide@vger.kernel.org, jon@ngndg.com,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Sata-MV, Intergated Sata Device Support
Date: Tue, 4 Mar 2008 18:42:19 +0000 [thread overview]
Message-ID: <57e2b00803041042k67f7b1c6ge8da83efaf1aa9f6@mail.gmail.com> (raw)
In-Reply-To: <47C43655.1050907@rtr.ca>
On Tue, Feb 26, 2008 at 3:55 PM, Mark Lord <liml@rtr.ca> wrote:
> saeed wrote:
> >
> > On Mon, 25 Feb 2008, Jeff Garzik wrote:
> >
> >>> ...
> >>>
> >>> Saeed: isn't this what your SOC patches already implemented for us?
> >>> As near as I can tell, sata_mv now already has support for the 60x1C0.
> >> Saeed's stuff didn't support PCI though, and Jon Li is definitely talking
> >> about PCI...
> > yes, my patch added support for the SoC sata like in the 5182, and this
> > is what Jon Li was concerned about. he mentioneded the 60x1C0 pci device
> > just to suggest to use it's code for the SoC sata as it is very similar.
> ..
>
> I don't think I understand your english there.
>
> Does the current sata_mv driver work as-is with the chipset this person wants?
> If not, then exactly what has to change to make it work?
Jon Li was one of the people who started porting Linux to the Marvell
Orion 88F5182 before Marvell did it. sata_mv does now work on the
device Jon was talking about. When this was sent I think we were
unsure whether it could work over PCI or just the system bus which
probably confused things a little.
Cheers,
--
Byron Bradley
next prev parent reply other threads:[~2008-03-04 18:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1176673884.5109.30.camel@Desktop>
2008-02-25 23:40 ` Jeff Garzik
2008-02-26 0:07 ` Mark Lord
2008-02-26 0:17 ` Jeff Garzik
2008-02-26 11:39 ` saeed
2008-02-26 15:55 ` Mark Lord
2008-03-04 18:26 ` Mark Lord
2008-03-04 18:42 ` Byron Bradley [this message]
2008-03-04 21:18 ` Mark Lord
2008-03-05 13:07 ` Jeff Garzik
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=57e2b00803041042k67f7b1c6ge8da83efaf1aa9f6@mail.gmail.com \
--to=byron.bbradley@gmail.com \
--cc=jeff@garzik.org \
--cc=jon@ngndg.com \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=saeed@marvell.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®