Saeed Bishara wrote:
>>> host->private_data = hpriv;
>>> hpriv->n_ports = n_ports;
>>>
>>> -host->iomap = NULL;
>>> hpriv->base = ioremap(res->start, res->end - res->start + 1);
>>> +host->iomap = &hpriv->base;
>>> hpriv->base -= MV_SATAHC0_REG_BASE;
>>>
>>> rc = mv
>> host->private_data = hpriv;
>> hpriv->n_ports = n_ports;
>>
>> -host->iomap = NULL;
>> hpriv->base = ioremap(res->start, res->end - res->start + 1);
>> +host->iomap = &hpriv->base;
>> hpriv->base -= MV_SATAHC0_REG_BASE;
>>
>> rc = mv_create_dma_pools(hpriv, &pdev
Mark Lord wrote:
> Byron Bradley wrote:
>> I'm having problems getting the sata_mv driver working as a platform
>> driver on the QNAP TS-209 and the Linkstation/Kurobox (both are Marvell
>> Orion 88f5182 based devices). First of all it would oops in
>> mv_port_start() while calling dma_pool_alloc()
Byron Bradley wrote:
On Fri, 8 Feb 2008, Byron Bradley wrote:
I'm having problems getting the sata_mv driver working as a platform
driver on the QNAP TS-209 and the Linkstation/Kurobox (both are Marvell
Orion 88f5182 based devices). First of all it would oops in
mv_port_start() while calling dm
Byron Bradley wrote:
I'm having problems getting the sata_mv driver working as a platform
driver on the QNAP TS-209 and the Linkstation/Kurobox (both are Marvell
Orion 88f5182 based devices). First of all it would oops in
mv_port_start() while calling dma_pool_alloc(), the patch to fix this is
at
On Fri, 8 Feb 2008, Byron Bradley wrote:
> I'm having problems getting the sata_mv driver working as a platform
> driver on the QNAP TS-209 and the Linkstation/Kurobox (both are Marvell
> Orion 88f5182 based devices). First of all it would oops in
> mv_port_start() while calling dma_pool_alloc(),
I'm having problems getting the sata_mv driver working as a platform
driver on the QNAP TS-209 and the Linkstation/Kurobox (both are Marvell
Orion 88f5182 based devices). First of all it would oops in
mv_port_start() while calling dma_pool_alloc(), the patch to fix this is
at the end of this email.
