linux-kernel - Re: [PATCH RESEND v3.7.0] Add AHCI support for Enmotus Bobcat device.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <50E5E153.9040801@mvista.com>
Date:	Thu, 03 Jan 2013 22:51:47 +0300
From:	Sergei Shtylyov <sshtylyov@...sta.com>
To:	Hugh Daschbach <hugh.daschbach@...otus.com>
CC:	Jeff Garzik <jgarzik@...ox.com>, linux-ide@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH RESEND v3.7.0] Add AHCI support for Enmotus Bobcat device.

Hello.

On 01/03/2013 09:35 PM, Hugh Daschbach wrote:

> Silicon does not support standard AHCI BAR assignment.  Add
> vendor/device exception to force BAR 2.

> Signed-off-by: Hugh Daschbach <hugh.daschbach@...otus.com>
> ---
> Previously sent 14 Dec 2012.  Any feedback?
> Thanks,
> Hugh

>  drivers/ata/ahci.c | 6 ++++++
>  1 file changed, 6 insertions(+)

> diff --git a/drivers/ata/ahci.c b/drivers/ata/ahci.c
> index 7862d17..3cb008f 100644
> --- a/drivers/ata/ahci.c
> +++ b/drivers/ata/ahci.c
[...]
> @@ -1101,6 +1105,8 @@ static int ahci_init_one(struct pci_dev *pdev, const struct pci_device_id *ent)
>  	/* The Connext uses non-standard BAR */

   This comment probably needs updating now to include your device.

>  	if (pdev->vendor == PCI_VENDOR_ID_STMICRO && pdev->device == 0xCC06)
>  		ahci_pci_bar = AHCI_PCI_BAR_STA2X11;
> +	else if (pdev->vendor == 0x1c44 && pdev->device == 0x8000)
> +		ahci_pci_bar = AHCI_PCI_BAR_ENMOTUS;
>  
>  	/* acquire resources */
>  	rc = pcim_enable_device(pdev);
> 

MBR, Sergei

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/