Date: Mon, 12 May 2008 06:49:15 -0600 From: Scott Long <scottl@samsco.org> To: Andrey Chernov <ache@nagual.pp.ru>, "Andrey V. Elsukov" <bu7cher@yandex.ru>, sos@FreeBSD.ORG, grehan@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: atadev->param.model problem or bug with Marvell 88SE6811 chip Message-ID: <48283CCB.1060507@samsco.org> In-Reply-To: <20080512062514.GA10058@nagual.pp.ru> References: <20080511004607.GA67182@nagual.pp.ru> <4827DCED.1000205@yandex.ru> <20080512062514.GA10058@nagual.pp.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
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 0xec00-0xec07,0xe880-0xe883,0xe800-0xe807,0xe480-0xe483,0xe400-0xe40f 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 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?48283CCB.1060507>