From: Dan Williams <dcbw@redhat.com>
To: Holger Schurig <hs4233@mail.mn-solutions.de>
Cc: linux-wireless@vger.kernel.org, libertas-dev@lists.infradead.org,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH 3/4] libertas: check for old, unsupported hardware
Date: Tue, 19 Aug 2008 15:44:05 -0400 [thread overview]
Message-ID: <1219175045.23157.25.camel@localhost.localdomain> (raw)
In-Reply-To: <200806051402.39736.hs4233@mail.mn-solutions.de>
On Thu, 2008-06-05 at 14:02 +0200, Holger Schurig wrote:
> I got this piece of code from the 5.0.16 GPL driver, but
> implemented it differently. I mainly put it in to find out if
> YOU have such an old silicon. When people yell "my card isn't
> supported, I get this kernel error" we can still add the
> necessary support.
>
> I don't want to add the support right now because I don't have
> this old hardware and don't know anyone with it. So no-one could
> test this.
So it turns out I have two of these cards, which are the ones I've been
using for testing since last year. Which might explain why I've been
having so many problems that you're not having. They are AmbiCom
WL54-CF rev 1.0 cards which I believe are B0 revision looking at the FCC
internal photos. The card returns 0x10 as the revision.
> The 5.0.16 source mentions two things needed for this old
> hardware:
>
> * doing read-modify-write instead of just setting bits, this
> applies to IF_CS_HOST_STATUS and IF_CS_HOST_INT_CAUSE
Any chance you could whip up a quick test patch for this one?
> * and an interrupt workaround
I'll try to figure out what needs to happen for this, lack of it might
be the cause of the hangs I've been seeing with my B0 hardware.
Dan
prev parent reply other threads:[~2008-08-19 19:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-05 11:08 [PATCH 3/4] libertas: check for old, unsupported hardware Holger Schurig
2008-06-05 11:46 ` Dan Williams
2008-06-05 12:02 ` Holger Schurig
2008-08-19 19:44 ` Dan Williams [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=1219175045.23157.25.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=hs4233@mail.mn-solutions.de \
--cc=libertas-dev@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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