The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Jose Alberto Reguero <jareguero@telefonica.net>
To: Alan <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: pata_marvell and Marvell 88SE6121
Date: Sun, 17 Dec 2006 14:22:48 +0100	[thread overview]
Message-ID: <200612171422.49112.jareguero@telefonica.net> (raw)
In-Reply-To: <20061216193146.06373923@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 522 bytes --]

El Sábado, 16 de Diciembre de 2006 20:31, Alan escribió:
> On Sat, 16 Dec 2006 18:41:26 +0100
>
> Jose Alberto Reguero <jareguero@telefonica.net> wrote:
> > I am trying to make work the driver pata_marvell of linux-2.6.20-rc1 with
> > Marvell 88SE6121.
>
> The 6121 is I believe ahci.

So there is no change to make work with pata_marvell ?
I thought that 61xx series was similar.

Do you suggest to try with ahci driver?

I atach new log with kernel 2.6.19 and pata_marvell patch.

Thanks.
Jose Alberto

[-- Attachment #2: log --]
[-- Type: text/plain, Size: 1920 bytes --]

Dec 17 13:07:28 jar kernel: ata3: PATA max UDMA/100 cmd 0xEC00 ctl 0xE882 bmdma 0xE400 irq 28
Dec 17 13:07:28 jar kernel: ata4: PATA max UDMA/133 cmd 0xE800 ctl 0xE482 bmdma 0xE408 irq 28
Dec 17 13:07:28 jar kernel: scsi2 : pata_marvell
Dec 17 13:07:28 jar kernel: BAR5:00:02 01:7F 02:22 03:CA 04:00 05:00 06:00 07:80 08:00 09:00 0A:00 0B:00 0C:07 0D:00 0E:00 0F:00 
Dec 17 13:07:28 jar kernel: ATA: abnormal status 0x7F on port 0xEC07
Dec 17 13:07:28 jar kernel: scsi3 : pata_marvell
Dec 17 13:07:28 jar kernel: BAR5:00:02 01:7F 02:22 03:CA 04:00 05:00 06:00 07:80 08:00 09:00 0A:00 0B:00 0C:07 0D:00 0E:00 0F:00 
Dec 17 13:07:28 jar kernel: ATA: abnormal status 0x7F on port 0xE807
Dec 17 13:07:28 jar kernel: ATA: abnormal status 0x7F on port 0xE807
Dec 17 13:07:58 jar kernel: ata4.00: qc timeout (cmd 0xec)
Dec 17 13:07:58 jar kernel: ata4.00: failed to IDENTIFY (I/O error, err_mask=0x4)
Dec 17 13:07:59 jar kernel: BAR5:00:02 01:7F 02:22 03:CA 04:00 05:00 06:00 07:80 08:00 09:00 0A:00 0B:00 0C:07 0D:00 0E:00 0F:00 
Dec 17 13:07:59 jar kernel: ATA: abnormal status 0x7F on port 0xE807
Dec 17 13:07:59 jar kernel: ATA: abnormal status 0x7F on port 0xE807
Dec 17 13:08:29 jar kernel: ata4.00: qc timeout (cmd 0xec)
Dec 17 13:08:29 jar kernel: ata4.00: failed to IDENTIFY (I/O error, err_mask=0x4)
Dec 17 13:08:29 jar kernel: BAR5:00:02 01:7F 02:22 03:CA 04:00 05:00 06:00 07:80 08:00 09:00 0A:00 0B:00 0C:07 0D:00 0E:00 0F:00 
Dec 17 13:08:30 jar kernel: ATA: abnormal status 0x7F on port 0xE807
Dec 17 13:08:30 jar kernel: ATA: abnormal status 0x7F on port 0xE807
Dec 17 13:09:00 jar kernel: ata4.00: qc timeout (cmd 0xec)
Dec 17 13:09:00 jar kernel: ata4.00: failed to IDENTIFY (I/O error, err_mask=0x4)
Dec 17 13:09:00 jar kernel: BAR5:00:02 01:7F 02:22 03:CA 04:00 05:00 06:00 07:80 08:00 09:00 0A:00 0B:00 0C:07 0D:00 0E:00 0F:00 
Dec 17 13:14:30 jar vdr: [3345] connect from 127.0.0.1, port 33449 - accepted

  reply	other threads:[~2006-12-17 13:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-16 17:41 pata_marvell and Marvell 88SE6121 Jose Alberto Reguero
2006-12-16 19:31 ` Alan
2006-12-17 13:22   ` Jose Alberto Reguero [this message]
2007-01-02 17:19 ` Jose Alberto Reguero

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=200612171422.49112.jareguero@telefonica.net \
    --to=jareguero@telefonica.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.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