linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: linville@tuxdriver.com, chunkeey@web.de,
	linux-wireless@vger.kernel.org, jal2@gmx.de,
	Peter.Grabienski@Atheros.com, Stephen.Chen@Atheros.com,
	Michael.Fortin@Atheros.com, Johnny.Cheng@Atheros.com,
	Yuan-Gu.Wei@atheros.com, otus-devel@lists.madwifi-project.org
Subject: Re: [PATCH 0/2] ar9170: 1-stage firmware support / AVM fritz
Date: Sun, 14 Jun 2009 17:11:48 +0200	[thread overview]
Message-ID: <1244992308.15367.3.camel@violet> (raw)
In-Reply-To: <1243546565-19404-1-git-send-email-lrodriguez@atheros.com>

Hi Luis,

> This series now works for me on my WNDA31000, it took a newer shiny
> 1-stage firmware to work. I'll push the firmware into linux-firmware
> next.
> 
> Should work with the AVM Fritz devices now, haven't tested it but
> I think it should work.

I happened to have one of these AVM devices. With ar9170.fw firmware it
does work fine with the other ones it doesn't.

The ar9170.fw is still not in linux-firmware.git, any reason for that?

Also since ar9170-1.fw and ar9170-2.fw are not working at all, we better
not even try and give the user a crypted error message that the device
is in a bad state. Just printk that the firmware might be too old.

Regards

Marcel



  parent reply	other threads:[~2009-06-14 15:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-28 21:36 [PATCH 0/2] ar9170: 1-stage firmware support / AVM fritz Luis R. Rodriguez
2009-05-28 21:36 ` [PATCH 1/2] ar9170: add support for 1-stage firmware Luis R. Rodriguez
2009-05-28 21:36 ` [PATCH 2/2] ar9170: add AVM FRITZ devices Luis R. Rodriguez
2009-06-14 15:11 ` Marcel Holtmann [this message]
2009-06-15 18:13   ` [PATCH 0/2] ar9170: 1-stage firmware support / AVM fritz Luis R. Rodriguez
2009-06-15 18:57     ` Marcel Holtmann
2009-06-15 19:48       ` Luis R. Rodriguez
2009-06-15 19:54         ` Marcel Holtmann
2009-06-15 20:13           ` Luis R. Rodriguez

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=1244992308.15367.3.camel@violet \
    --to=marcel@holtmann.org \
    --cc=Johnny.Cheng@Atheros.com \
    --cc=Michael.Fortin@Atheros.com \
    --cc=Peter.Grabienski@Atheros.com \
    --cc=Stephen.Chen@Atheros.com \
    --cc=Yuan-Gu.Wei@atheros.com \
    --cc=chunkeey@web.de \
    --cc=jal2@gmx.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=lrodriguez@atheros.com \
    --cc=otus-devel@lists.madwifi-project.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).