netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Benoît Vaillant" <benoit.vaillant@no-log.org>
To: Dan Williams <dcbw@redhat.com>
Cc: "Benoît Vaillant" <benoit.vaillant@no-log.org>, netdev@vger.kernel.org
Subject: Re: sd8686 linux system hang: not always
Date: Sat, 22 Aug 2009 00:55:50 +0200	[thread overview]
Message-ID: <20090821225550.GA1634@kaos.fbx.proxad.net> (raw)
In-Reply-To: <1250859856.2876.11.camel@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1705 bytes --]

Hi,

On Fri, Aug 21, 2009 at 08:04:16AM -0500, Dan Williams wrote:
> Well, besides the fact that the Poulsbo SDHC driver hasn't actually
> passed review for the kernel yet... 

And other parts of Poulsbo drivers were removed from -at least-
debian, for the xorg part of it. I had that in mind.

> That doesn't mean the Poulsbo driver isn't a fine driver, but if
> Pierre hasn't acked it, I don't really trust it.  The largest # of
> problems people have had with Libertas SDIO have been with the host
> controller with things like transfer widths, clocking, interrupt
> vs. polled mode, chunk size, etc.  When the SDHC driver and hardware
> they are using actually starts working well, then libertas actually
> starts working well.

Ok. I'll check on parameters when I get spare time. I did consider
such things could be part (all? :) ) of the issue.

Pointers welcomed, if any other than browsing the web!

> So I don't mean to brush you off, but we know the chip works pretty well
> with the Ricoh line (which I'm typing this on right now with an sd8686)
> and a few other embedded-type controllers.  So I'd start diving down
> into the SDHC driver code for Poulsbo and try to figure out what's going
> on there and in the MMC layer.

Hehe, no worry, I know the chip works fine under midinux. Yet
compiling such working drivers would either lead me to revert to an
older kernel version (and not provide testing with newer ones, thus)
or adapt the marvell driver to newer kernel, task which I'm rather not
sure to be able to carry by some quite good amount of time :)

You didn't brush me off, I wasn't expecting a straight working
solution :)

TFYA,

-- 
Benoît

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

      reply	other threads:[~2009-08-21 22:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-19 18:56 sd8686 linux system hang: not always Benoît Vaillant
2009-08-19 19:39 ` Dan Williams
2009-08-20 20:40   ` Benoît Vaillant
2009-08-21 13:04     ` Dan Williams
2009-08-21 22:55       ` Benoît Vaillant [this message]

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=20090821225550.GA1634@kaos.fbx.proxad.net \
    --to=benoit.vaillant@no-log.org \
    --cc=dcbw@redhat.com \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).