Re: 31244 & sata_vsc & PPC

[Ajit Prem <Ajit.Prem@motorola.com>]

As a follow-up to my previous email where
I indicated that int_status on entry into
vsc_sata_interrupt indicates 0x8300, I
put in a crude fix in the vsc_sata_interrupt
handler to read the taskfile status register,
and to clear the appropriate bits in the
SATA SError register, and now things work
just fine.

Thank you very much for your help.

AP


Jeff Garzik wrote:

>On Wed, Feb 16, 2005 at 12:05:16PM -0700, Ajit Prem wrote:
>  
>
>>The email archives indicate that sata_vsc worked
>>on a 31244 in a Dell Powervault once the
>>kernel included the following configuration:
>>
>>Processor type and features -> Local APIC support on uniprocessors
>>Processor type and features -> IO-APIC support on uniprocessors
>>General setup -> Power Management support -> ACPI Support
>>
>>Trying to use sata_vsc on a 31244 in a PPC board
>>results in the same problem as other users had on
>>an X86 board configured without ACPI support - interrupts
>>come in too early to vsc_sata_interrupt, the interrupt
>>doesn't get cleared, and the kernel finally disables the irq.
>>What should one do to get sata_vsc/libata to work on a PPC board?
>>    
>>
>
>Ultimately I wonder if sata_vsc is masking/clearing all interrupt
>conditions during startup.
>
>There might also be a problem with PIO polling.
>
>	Jeff
>
>
>
>  
>