On Thu, 2009-10-29 at 11:27 +0100, Daniel Mack wrote:
> On Wed, Oct 28, 2009 at 10:06:02AM -0700, Dan Williams wrote:
> > On Wed, 2009-10-28 at 17:47 +0100, Daniel Mack wrote:
> > > I did some more research on this and it turns out that the problem is
> > > related to multi block transfers. At leas
On Wed, Oct 28, 2009 at 10:06:02AM -0700, Dan Williams wrote:
> On Wed, 2009-10-28 at 17:47 +0100, Daniel Mack wrote:
> > I did some more research on this and it turns out that the problem is
> > related to multi block transfers. At least, this is when it first
> > occurs.
> >
> > The libertas SDI
On Wed, 2009-10-28 at 18:19 +0100, Daniel Mack wrote:
> On Wed, Oct 28, 2009 at 10:06:02AM -0700, Dan Williams wrote:
> > On Wed, 2009-10-28 at 17:47 +0100, Daniel Mack wrote:
> > > I did some more research on this and it turns out that the problem is
> > > related to multi block transfers. At leas
On Wed, Oct 28, 2009 at 10:11:04AM -0700, Dan Williams wrote:
> On Wed, 2009-10-28 at 17:47 +0100, Daniel Mack wrote:
> > I did some more research on this and it turns out that the problem is
> > related to multi block transfers. At least, this is when it first
> > occurs.
> >
> > The libertas SDI
On Wed, Oct 28, 2009 at 10:06:02AM -0700, Dan Williams wrote:
> On Wed, 2009-10-28 at 17:47 +0100, Daniel Mack wrote:
> > I did some more research on this and it turns out that the problem is
> > related to multi block transfers. At least, this is when it first
> > occurs.
> >
> > The libertas SDI
On Wed, 2009-10-28 at 17:47 +0100, Daniel Mack wrote:
> On Wed, Oct 21, 2009 at 01:15:19PM -0700, Dan Williams wrote:
> > On Wed, 2009-10-21 at 21:20 +0200, Daniel Mack wrote:
> > > Hi,
> > >
> > > we're having trouble getting SDIO connected harware to fly on MX31 based
> > > designs. In particula
On Wed, 2009-10-28 at 17:47 +0100, Daniel Mack wrote:
> On Wed, Oct 21, 2009 at 01:15:19PM -0700, Dan Williams wrote:
> > On Wed, 2009-10-21 at 21:20 +0200, Daniel Mack wrote:
> > > Hi,
> > >
> > > we're having trouble getting SDIO connected harware to fly on MX31 based
> > > designs. In particula
On Wed, Oct 21, 2009 at 01:15:19PM -0700, Dan Williams wrote:
> On Wed, 2009-10-21 at 21:20 +0200, Daniel Mack wrote:
> > Hi,
> >
> > we're having trouble getting SDIO connected harware to fly on MX31 based
> > designs. In particular, a SD8686 chip supported by the libertas_sdio
> > driver will ha
I didn't really debug it yet, but from what I see in the sources, the
maximum block size is 2048. The hardware is connected via the 4-wire
Hi Daniel,
Did you try to run the driver with 1-Bit mode?
Maybe you can try to have debug routine to report the IRQ status for
this sdhc controller.
On Wed, Oct 21, 2009 at 10:51:56PM +0200, Daniel Mack wrote:
> Hi Dan,
>
> On Wed, Oct 21, 2009 at 01:15:19PM -0700, Dan Williams wrote:
> > On Wed, 2009-10-21 at 21:20 +0200, Daniel Mack wrote:
> > > Hi,
> > >
> > > we're having trouble getting SDIO connected harware to fly on MX31 based
> > > d
Hi Dan,
On Wed, Oct 21, 2009 at 01:15:19PM -0700, Dan Williams wrote:
> On Wed, 2009-10-21 at 21:20 +0200, Daniel Mack wrote:
> > Hi,
> >
> > we're having trouble getting SDIO connected harware to fly on MX31 based
> > designs. In particular, a SD8686 chip supported by the libertas_sdio
> > drive
On Wed, 2009-10-21 at 21:20 +0200, Daniel Mack wrote:
> Hi,
>
> we're having trouble getting SDIO connected harware to fly on MX31 based
> designs. In particular, a SD8686 chip supported by the libertas_sdio
> driver will hang forever when built without CONFIG_MMC_DEBUG=y. With
> that option selec
Hi,
we're having trouble getting SDIO connected harware to fly on MX31 based
designs. In particular, a SD8686 chip supported by the libertas_sdio
driver will hang forever when built without CONFIG_MMC_DEBUG=y. With
that option selected, however, the behaviour is a little different, and
I can at le
13 matches
Mail list logo
