linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sven Luther <sven.luther@wanadoo.fr>
To: Mark Lord <liml@rtr.ca>
Cc: Sven Luther <sven.luther@wanadoo.fr>,
	Jeff Garzik <jgarzik@pobox.com>,
	Alexandre.Bounine@tundra.com, linux-ide@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linuxppc-dev list <linuxppc-dev@ozlabs.org>,
	Paul Mackerras <paulus@samba.org>,
	Yang Xin-Xin-r48390 <Xin-Xin.Yang@freescale.com>
Subject: Re: [PATCH/2.6.17-rc4 10/10]  bugs fix for marvell SATA on powerp c pl atform
Date: Fri, 26 May 2006 13:42:45 +0200	[thread overview]
Message-ID: <20060526114245.GA32330@powerlinux.fr> (raw)
In-Reply-To: <4476E964.90509@rtr.ca>

On Fri, May 26, 2006 at 07:41:24AM -0400, Mark Lord wrote:
> Sven Luther wrote:
> >I'm trying to use a Marvell 88SX5081 based card here in my pegasos machine,
> >and i never got it working with the libata driver, even with the patches 
> >Zang
> >provided (and 2.6.16 though, maybe i should update to a newer version). The
> >marvell provided driver worked though at some time.
> >
> >Would it be possible to have access to your work, in order to not duplicate
> >effort or something ? 
> 
> All of the relevant bits of "my work" are now in Jeff's upstream libata 
> tree,
> from the recently posted sata_mv patches.

Ok. can i use this tree with a 2.6.16 base ?
 
> After struggling with bad SDRAM earlier this week, I now have Ubuntu 
> installed
> and running reliably on my G3 box here.  Next step is to upgrade the kernel
> to something modern, and add in the latest sata_mv.

Ok.
 
> After that, I'll try my own 6081 Marvell card in it, and hopefully see the 
> same failures as you.. hopefully!

I tried getting a 6081 based low profile card, but they don't seem to sell in
europe.

Friendly,

Sven Luther


  reply	other threads:[~2006-05-26 11:47 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-18  4:03 [PATCH/2.6.17-rc4 10/10] bugs fix for marvell SATA on powerp c pl atform Zang Roy-r61911
2006-05-18  7:02 ` Benjamin Herrenschmidt
2006-05-18 15:26   ` Jeff Garzik
2006-05-18 20:50     ` Mark Lord
2006-05-18 21:07       ` Jeff Garzik
2006-05-18 21:37         ` Mark Lord
2006-05-26  8:39       ` Sven Luther
2006-05-26  8:56         ` Jeff Garzik
2006-05-26  8:58           ` Sven Luther
2006-05-26 11:41         ` Mark Lord
2006-05-26 11:42           ` Sven Luther [this message]
2006-05-26 13:19             ` Mark Lord
2006-05-26 14:15               ` Sven Luther
2006-05-26 15:47                 ` Mark Lord
2006-05-26 16:01                   ` Sven Luther
2006-05-26 16:15                     ` Sven Luther
2006-05-26 16:21                     ` Mark Lord
2006-05-26 16:25                       ` Sven Luther
2006-05-18 12:01 ` Ric Wheeler
  -- strict thread matches above, loose matches on Subject: below --
2006-05-19  4:06 Zang Roy-r61911
2006-05-19  4:12 Zang Roy-r61911

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=20060526114245.GA32330@powerlinux.fr \
    --to=sven.luther@wanadoo.fr \
    --cc=Alexandre.Bounine@tundra.com \
    --cc=Xin-Xin.Yang@freescale.com \
    --cc=jgarzik@pobox.com \
    --cc=liml@rtr.ca \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).