From: Wolfgang Denk <wd@denx.de>
To: Rupjyoti Sarmah <rsarmah@amcc.com>
Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org,
linux-ide@vger.kernel.org, sr@denx.de, jgarzik@pobox.com
Subject: Re: [PATCH]460EX on-chip SATA driver<kernel 2.6.33><resubmission>
Date: Sun, 06 Jun 2010 23:09:28 +0200 [thread overview]
Message-ID: <20100606210928.1BEE6FA8EE@gemini.denx.de> (raw)
In-Reply-To: <201006041226.o54CQH2V017366@amcc.com>
Dear Rupjyoti Sarmah,
In message <201006041226.o54CQH2V017366@amcc.com> you wrote:
> This patch enables the on-chip DWC SATA controller of the AppliedMicro processor 460EX.
>
> Signed-off-by: Rupjyoti Sarmah <rsarmah@appliedmicro.com>
> Signed-off-by: Mark Miesfeld <mmiesfeld@appliedmicro.com>
> Signed-off-by: Prodyut Hazarika <phazarika@appliedmicro.com>
>
> ---
> drivers/ata/Kconfig | 9 +
> drivers/ata/Makefile | 1 +
> drivers/ata/sata_dwc_460ex.c | 1808 ++++++++++++++++++++++++++++++++++++++++++
> 3 files changed, 1818 insertions(+), 0 deletions(-)
> create mode 100644 drivers/ata/sata_dwc_460ex.c
This driver needs fixing. It will not compile against recent kernel
versions.
...
> diff --git a/drivers/ata/sata_dwc_460ex.c b/drivers/ata/sata_dwc_460ex.c
> new file mode 100644
> index 0000000..e6e2896
> --- /dev/null
> +++ b/drivers/ata/sata_dwc_460ex.c
> @@ -0,0 +1,1808 @@
...
> +#include <linux/kernel.h>
> +#include <linux/module.h>
> +#include <linux/init.h>
> +#include <linux/device.h>
> +#include <linux/of_platform.h>
> +#include <linux/libata.h>
> +#include "libata.h"
> +
> +#include <scsi/scsi_host.h>
> +#include <scsi/scsi_cmnd.h>
You miss a "#include <linux/slab.h>" here.
...
> + for (i = 0; i < SATA_DWC_QCMD_MAX; i++)
> + hsdevp->cmd_issued[i] = SATA_DWC_CMD_ISSUED_NOT;
> +
> + ap->prd = 0; /* set these so libata doesn't use them */
> + ap->prd_dma = 0;
s/prd/bmdma_prd/ in these two lines (cf. commit f60d7011).
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
He had quite a powerful intellect, but it was as powerful like a
locomotive, and ran on rails and was therefore almost impossible to
steer. - Terry Pratchett, _Lords and Ladies_
next prev parent reply other threads:[~2010-06-06 21:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-04 12:26 [PATCH]460EX on-chip SATA driver<kernel 2.6.33><resubmission> Rupjyoti Sarmah
2010-06-06 18:52 ` Josh Boyer
2010-06-06 21:09 ` Wolfgang Denk [this message]
2010-06-18 4:34 ` Jassi Brar
2010-06-29 1:33 ` Marek Vasut
2010-06-29 12:20 ` Rupjyoti Sarmah
2010-06-29 12:44 ` Anton Vorontsov
-- strict thread matches above, loose matches on Subject: below --
2010-05-05 17:57 [PATCH]460EX on-chip SATA driver <Kernel 2.6.33> < resubmission > Rupjyoti Sarmah
2010-05-14 17:44 ` Sergei Shtylyov
2010-05-15 23:40 ` Benjamin Herrenschmidt
2010-05-17 10:06 ` Stefan Roese
2010-05-17 10:36 ` Benjamin Herrenschmidt
2010-05-14 21:56 ` Jeff Garzik
2010-05-19 1:49 ` Jassi Brar
2010-05-19 9:53 ` Alan Cox
2010-05-19 11:19 ` Jassi Brar
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=20100606210928.1BEE6FA8EE@gemini.denx.de \
--to=wd@denx.de \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=rsarmah@amcc.com \
--cc=sr@denx.de \
/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).