mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bill Gribble <grib@billgribble.com>
To: Pierre Ossman <drzeus-mmc@drzeus.cx>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.24-rc2 libertas_sdio fails to initialize Marvell SD8686
Date: Wed, 09 Jan 2008 14:53:58 -0500	[thread overview]
Message-ID: <87y7ayvkq1.fsf@billgribble.com> (raw)
In-Reply-To: <20071114190247.4f42aa05@poseidon.drzeus.cx> (Pierre Ossman's message of "Wed, 14 Nov 2007 19:02:47 +0100")

Pierre Ossman <drzeus-mmc@drzeus.cx> writes:
> Marvell tend to not have a one true firmware, but one for each device,
> so you might end up having to dig out the ones shipped with the
> device.

I finally got these firmware files from the manufacturer; still, with
2.6.24-rc6 and the new firmware files, the same errors occur.  

>> Nov 13 14:40:09 pequin kernel: mmc0: starting CMD53 arg 9a000002 flags 000001b5
>> Nov 13 14:40:09 pequin kernel: mmc0:     blksz 32 blocks 2 flags 00000100 tsac 1000 ms nsac 0
>> Nov 13 14:40:09 pequin kernel: sdhci [sdhci_irq()]: *** sdhci:slot0 got interrupt: 0x00000001
>> Nov 13 14:40:11 pequin kernel: sdhci [sdhci_irq()]: *** sdhci:slot0 got interrupt: 0x00108000
>> Nov 13 14:40:11 pequin kernel: mmc0: req done (CMD53): 0: 00002000 00000000 00000000 00000000
>> Nov 13 14:40:11 pequin kernel: mmc0:     32 bytes transferred: -110
>
> Your problem is here. The card chokes for some reason and times out
> when it's supposed to receive a chunk of the firmware. Odd, as the
> loading loop first queries the card if it is ready for more data.

Any other sage advice?  I feel like the device is really close to
working, but I just can't get it there!  

Thanks,
Bill Gribble


!DSPAM:4785262012631060021202!



  parent reply	other threads:[~2008-01-09 20:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-13 21:21 Bill Gribble
2007-11-14 18:02 ` Pierre Ossman
2007-11-15 21:06   ` Bill Gribble
2007-11-19 19:07     ` Pierre Ossman
2008-01-09 19:53   ` Bill Gribble [this message]
2008-01-11  8:30     ` Pierre Ossman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y7ayvkq1.fsf@billgribble.com \
    --to=grib@billgribble.com \
    --cc=drzeus-mmc@drzeus.cx \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome