All of lore.kernel.org
 help / color / mirror / Atom feed
From: Holger Schurig <hs4233@mail.mn-solutions.de>
To: libertas-dev@lists.infradead.org
Cc: Dan Williams <dcbw@redhat.com>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH, take 3] libertas: fix compact flash interrupt handling
Date: Wed, 28 May 2008 10:46:35 +0200	[thread overview]
Message-ID: <200805281046.35897.hs4233@mail.mn-solutions.de> (raw)
In-Reply-To: <1211919275.555.25.camel@localhost.localdomain>

> But again; if the patch works better for you, I'll ack it
> because it doesn't work any worse for me.  Logs with
> libertas_debug=0x443af available if you want to see them.

Yes, I'd like this. You can send me this as a .bz2 file.

For me, the problem with the old approach was in the "tx done" 
part. With take1+take2 of my patch, an error showed up when, 
while I was executing if_cs_send_data(), an interrupt could 
happen and my code did touch other chip registers, while it just 
should continue to send the data. Take 3 fixed this for me.


> I really don't know what to do to trace it further.  Is there a
> way to reset the CF card and kick the firmware in the head that
> I can try from the TX handler, like a USB port reset or
> something?  I also might be able to set this machine up for
> remote access so you can play with it if you like.

On CF, there's always one way to kick the firmware into the 
head: "pcmciactrl eject; pcmciactrl insert". You can be quite 
pretty sure that after this every state in the card, the 
firmware, the driver and the networking subsystem has been 
cleared :-)

However, maybe there are better ways, less sledge-hammer-like 
ones. I'll dig more into this.


One reason for my digging is this error that I had:

libertas_cs: card not ready for commands
libertas: DNLD_CMD: hw_host_to_card failed: -1
libertas: command 0x001f timed out
libertas: requeueing command 0x001f due to timeout (#1)
libertas_cs: card not ready for commands
libertas: DNLD_CMD: hw_host_to_card failed: -1
libertas: command 0x001f timed out
libertas: requeueing command 0x001f due to timeout (#2)
libertas_cs: card not ready for commands
libertas: DNLD_CMD: hw_host_to_card failed: -1
libertas: command 0x001f timed out
libertas: requeueing command 0x001f due to timeout (#3)
libertas_cs: card not ready for commands
libertas: DNLD_CMD: hw_host_to_card failed: -1
libertas: command 0x001f timed out
libertas: Excessive timeouts submitting command 0x001f
libertas_cs: no cmd response in card
libertas: PREP_CMD: command 0x0006 failed: -2
libertas: SCAN_CMD failed


However, I'm not yet sure if I can say (in this case) "the 
firmware is hosed" and I'm also not sure if it's wise to just 
send a CMD_802_11_RSSI command down as the driver currently 
does.

  parent reply	other threads:[~2008-05-28  8:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-26 10:50 [PATCH, take 3] libertas: fix compact flash interrupt handling Holger Schurig
2008-05-27 20:14 ` Dan Williams
2008-05-27 20:20   ` Dan Williams
2008-05-28  8:46   ` Holger Schurig [this message]
2008-05-27 20:15 ` Dan Williams

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=200805281046.35897.hs4233@mail.mn-solutions.de \
    --to=hs4233@mail.mn-solutions.de \
    --cc=dcbw@redhat.com \
    --cc=libertas-dev@lists.infradead.org \
    --cc=linux-wireless@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.