Bug#552270: Marvell CESA driver and Kirkwood
I got the following answer, so I'll go ahead and enable CESA for
Kirkwood.
* Sebastian Andrzej Siewior <sebastian@breakpoint.cc> [2009-10-26 22:53]:
> * Martin Michlmayr | 2009-10-26 18:26:08 [+0800]:
>
> >Hi Sebastian and Nico,
> Hi Martin,
>
> >I put Sebastian's CESA driver into Debian's 2.6.31 kernel and enabled
> >it for orion5x. A Debian user asked me why I didn't enable it for
> >Kirkwood. AFAIK, there are some differences between the CESA on
> >Orion5x and Kirkwood, so my assumption was that the current CESA
> >driver doesn't work on Kirkwood. But I'm actually not sure if this is
> >true.
> >
> >Do you know if the current driver will work on Kirkwood?
> I don't really know. I just looked through the spec and compared them
> and they look very alike:
> - Orion's has larger sram space. The driver does not assume, it uses the
> size specified and Kirkwood's is set to 2KiB
> - the register seem to be at the same spot. Orion has two engines,
> Kirkwood just one. Right now, only the first one is used.
> - security engine's descriptor looks the same
> - the DMA engine differs in a few spot but it is not yet implemented so
> it doesn't matter.
>
> As far as I can see in current git, Nico enabled the CESA engine on
> Kirkwood [0]. It looks like he assumes that it should work, I don't know
> if he ever has tested it :)
>
> [0] http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=ae5c8c83735f5fcb09b380944e4854a383006998
> Sebastian
--
Martin Michlmayr
http://www.cyrius.com/
Reply to: