linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Daniel Smith <viscous.liquid@gmail.com>
Cc: <linux-wireless@vger.kernel.org>,
	ath6kl-devel <ath6kl-devel@qualcomm.com>
Subject: Re: AR6002 support in ath6kl driver
Date: Fri, 6 Jan 2012 12:31:43 +0200	[thread overview]
Message-ID: <4F06CD8F.50204@qca.qualcomm.com> (raw)
In-Reply-To: <CADGLRPkBk+FhPSoEf=dK+W+yx1FS0HP3tkjv6BxPHQ5ZmCRg-A@mail.gmail.com>

Hi Daniel,

On 12/28/2011 11:01 PM, Daniel Smith wrote:

> So I have recently been asked to begin supporting an AR6002
> platform. Currently it is using the Atheros ar6000 (v 2.1.2) driver.
> I see that the ar6kl driver only supports the AR6003 and was
> wondering if there was some technical reason that support for the
> AR6002 was dropped in the up-streaming process?

No other reason than lack of time and resources.

> If not, would AR6002 support be welcomed in the mainstream driver
> should I decide to attempt the endeavor of porting/adding into the
> ath6kl driver?

I would be happy to take AR6002 patches as long as they follow the style
used in ath6kl and are otherwise of good quality. I would recommend that
you first setup your own git tree for this and once you have something
working we can start discussing merging your changes to ath6kl.

> Finally, could I expect any support from the ath6kl
> developers troubleshooting issues that would inevitable arise along
> the way?

Based on my long email backlog I cannot provide anything than reviewing
patches and giving general comments. I simply don't have the time to
work on the details.

Kalle

      reply	other threads:[~2012-01-06 10:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-28 21:01 AR6002 support in ath6kl driver Daniel Smith
2012-01-06 10:31 ` Kalle Valo [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=4F06CD8F.50204@qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=ath6kl-devel@qualcomm.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=viscous.liquid@gmail.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;
as well as URLs for NNTP newsgroup(s).