Hello All,
Thanks for your replies. If we see the dump, you will observe that
the NAND flash supports the MDMA2 but the driver does not set it but
goes in for PIO4. On looking at the ata_port_info structure populated
in case of 3100 SATA controller chipset namely the first entry, the
mwdma mask is not initialized causing the driver to skip the same and
go in for PIO modes. When I did add the MDMA mask, everything fell in
place and I was able to access the flash devices.
Can you please let me know if there is any specific reason as to
why the mdma masks are not added in the ata_port_info initialisations.
Regards,
Girish
On 10/22/07, Alan Cox <alan@xxxxxxxxxxxxxxxxxxx> wrote:
> On Mon, 22 Oct 2007 18:34:57 +0900
> Tejun Heo <htejun@xxxxxxxxx> wrote:
>
> > Mark Lord wrote:
> > > Alan / Tejun,
> > >
> > > Another case of MDMA2 not working through a SATA->PATA bridge.
> > > Do we have an easy way yet, for Girish to force non-MDMA2 modes?
> >
> > libata.dma=1 should do the trick for 2.6.24-rcX. For 2.6.23, there
> > isn't any. :-(
>
> For CF specifying libata.dma=3 should do the trick even better as it will
> leave DMA enabled on disk and ATAPI
>
-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
