From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Pavel Roskin <proski@gnu.org>
Cc: Marcel Holtmann <marcel@holtmann.org>,
Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"jal2@gmx.de" <jal2@gmx.de>,
Peter Grabienski <Peter.Grabienski@Atheros.com>,
Stephen Chen <Stephen.Chen@Atheros.com>,
Michael Fortin <Michael.Fortin@Atheros.com>,
Johnny Cheng <Johnny.Cheng@Atheros.com>,
Yuan-Gu Wei <Yuan-Gu.Wei@Atheros.com>,
"otus-devel@lists.madwifi-project.org"
<otus-devel@lists.madwifi-project.org>
Subject: Re: [RFT 2/2] ar9170: add AVM FRITZ devices
Date: Thu, 28 May 2009 12:29:07 -0700 [thread overview]
Message-ID: <20090528192907.GE20870@tesla> (raw)
In-Reply-To: <1243524158.19748.2.camel@mj>
On Thu, May 28, 2009 at 08:22:38AM -0700, Pavel Roskin wrote:
> On Thu, 2009-05-28 at 09:17 +0200, Marcel Holtmann wrote:
>
> > can't you make this part of use_device_id table? Syncing up with product
> > ids in two places is not a good idea.
I take it you mean usb_device_id, and sure driver_info.
> It would be even better to use an internal chip ID, an equivalent to the
> SREV register in ath5k and ath9k, if it exists in ar9170.
Not sure if such things exists.
Luis
prev parent reply other threads:[~2009-05-28 19:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-28 1:48 [RFT 0/2] ar9170: initial stage 1 firmware support / AVM fritz Luis R. Rodriguez
2009-05-28 1:48 ` [RFT 1/2] ar9170: add initial support for 1-stage firmware Luis R. Rodriguez
2009-05-28 16:03 ` Christian Lamparter
2009-05-28 19:26 ` Luis R. Rodriguez
2009-05-28 21:16 ` [otus-devel] " Luis R. Rodriguez
2009-05-28 1:48 ` [RFT 2/2] ar9170: add AVM FRITZ devices Luis R. Rodriguez
2009-05-28 7:17 ` Marcel Holtmann
2009-05-28 15:22 ` Pavel Roskin
2009-05-28 19:29 ` Luis R. Rodriguez [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=20090528192907.GE20870@tesla \
--to=lrodriguez@atheros.com \
--cc=Johnny.Cheng@Atheros.com \
--cc=Luis.Rodriguez@Atheros.com \
--cc=Michael.Fortin@Atheros.com \
--cc=Peter.Grabienski@Atheros.com \
--cc=Stephen.Chen@Atheros.com \
--cc=Yuan-Gu.Wei@Atheros.com \
--cc=jal2@gmx.de \
--cc=linux-wireless@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=otus-devel@lists.madwifi-project.org \
--cc=proski@gnu.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).