From owner-freebsd-current@FreeBSD.ORG  Wed May 21 11:03:17 2008
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@FreeBSD.ORG
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 6C19B1065672;
	Wed, 21 May 2008 11:03:17 +0000 (UTC) (envelope-from sos@FreeBSD.ORG)
Received: from pasmtpB.tele.dk (pasmtpb.tele.dk [80.160.77.98])
	by mx1.freebsd.org (Postfix) with ESMTP id 1F2E08FC14;
	Wed, 21 May 2008 11:03:17 +0000 (UTC) (envelope-from sos@FreeBSD.ORG)
Received: from deepcore.dk (unknown [87.63.29.106])
	by pasmtpB.tele.dk (Postfix) with ESMTP id 3CA76E300C7;
	Wed, 21 May 2008 12:36:27 +0200 (CEST)
Received: from laptop.deepcore.dk (laptop.deepcore.dk [192.168.0.138])
	by deepcore.dk (8.13.8/8.13.8) with ESMTP id m4K8QpCl047971;
	Tue, 20 May 2008 10:26:51 +0200 (CEST)
	(envelope-from sos@FreeBSD.ORG)
Message-Id: <DC4E1D31-A755-4D2C-9972-7B37CD3B8459@FreeBSD.ORG>
From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= <sos@FreeBSD.ORG>
To: Scott Long <scottl@samsco.org>
In-Reply-To: <48283CCB.1060507@samsco.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Tue, 20 May 2008 10:26:57 +0200
References: <20080511004607.GA67182@nagual.pp.ru> <4827DCED.1000205@yandex.ru>
	<20080512062514.GA10058@nagual.pp.ru> <48283CCB.1060507@samsco.org>
X-Mailer: Apple Mail (2.919.2)
Cc: Andrey Chernov <ache@nagual.pp.ru>, "Andrey V. Elsukov" <bu7cher@yandex.ru>,
	current@FreeBSD.ORG, grehan@FreeBSD.ORG
Subject: Re: atadev->param.model problem or bug with Marvell 88SE6811 chip
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 21 May 2008 11:03:17 -0000

Actually ATAPI devices are identified with the ATAPI IDENTIFY command =20=

just as they should.

-S=F8ren




On 12May, 2008, at 14:49 , Scott Long wrote:

> Andrey Chernov wrote:
>> On Mon, May 12, 2008 at 10:00:13AM +0400, Andrey V. Elsukov wrote:
>>> Andrey Chernov wrote:
>>>> I have device detection problem with device attached to
>>>> atapci0: <Marvell ATA controller> port =20
>>>> 0xec00=20
>>>> -0xec07,0xe880-0xe883,0xe800-0xe807,0xe480-0xe483,0xe400-0xe40f =20
>>>> mem 0xfebffc00-0xfebfffff irq 16 at device 0.0 on pci3
>>>> (ASUS P5E3 motherboard).
>>>> It seems that this controller not fills atadev->param.model as =20
>>>> current ata-all.c code expects:
>>> Can you try this patch and show verbose dmesg with patched kernel?
>> I change them to atadev->param.config and atadev->param.reserved2
>> since there is no such members in atadev directly. Results are:
>> ata2: IDENTIFY DEVICE data is complete, word2 is 0x0000
>> ata2: IDENTIFY DEVICE data is complete, word2 is 0x0000
>> (per each channel)
>
> ATAPI devices should be getting their identifying strings via an
> MMC INQ command instead of an ATA IDENTIFY command.  What happens
> if you add the atapicam driver?
>
> Scott
>
>