Actually ATAPI devices are identified with the ATAPI IDENTIFY command just as they should. -Søren 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 >>>> 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 > >Received on Wed May 21 2008 - 09:03:17 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:31 UTC