All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luis R. Rodriguez <lrodriguez@atheros.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Extensive AR9280 Documentation
Date: Thu, 6 Jan 2011 14:17:24 -0800	[thread overview]
Message-ID: <20110106221724.GC5284@tux> (raw)
In-Reply-To: <20110106214548.18602.qmail@stuge.se>

On Thu, Jan 06, 2011 at 01:45:48PM -0800, Peter Stuge wrote:
> Luis R. Rodriguez wrote:
> > It helps if the community acknowledges efforts and tries to work
> > with companies who are putting good effort on things.
> 
> I would love to ack effort if I had experienced some. I've touched on
> a plethora of indications of significant issues in the driver a few
> times volunteering to acquire information and do further debugging,
> but since all has fallen absolutely flat, it's very hard to ack.

Can you provide links to your kernel.org bug reports?

> > Respecting IP is a small trade off that we do ask for.
> 
> Yes of course. Especially doing something in spite is bad form
> uncalled for and unneccessary.
> 
> When there is working efficient communication then there is also
> no point at all in leaking whatever is considered private. In other
> projects there are NDAs between hardware companies and developers,
> which allows the software to develop quickly and work really really
> great. Maybe that is going on for ath9k too, but has not helped me. :\

Active developers do get documentation for ath5k without an NDA but
with a gentelmen's petition to not redistribute. We do this for other
OSes too, like for FreeBSD. For ath9k we have not received permission to
release the same docs publicly but am working on creating a better
review process which will let us reconsider releaseing more docs after
a period of time. This is a company process that needs to be built,
so it takes time. In the meantime we do enable active developers to
work with engineers through our private internal list but since
ath9k is Actively maintained by Atheros engineers if you have issues
they should be clearly reported and Atheros will take care of them.

If you have issues I advise you not only use a mailing list but
the bugzilla on kernel.org and report your issue against the
stable kernel you are having an issue with. If you are using
a bleeding edge release (compat-wireless based on linux-next)
or just wireless-testing then you can just use the linux-wireless
mailing list and provide clear details of your issues there.

I believe you have an AR9280 and AR9280 should be IMHO the best
supported 802.11 card on Linux today for both STA/AP mode of operation.
If you have issues can you please put a list together and report them
with clear details either on bugzilla if on a stable kernel or on
linux-wireless if its on wireless-testing.

  Luis

  reply	other threads:[~2011-01-06 22:17 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-06 18:39 [ath9k-devel] Extensive AR9280 Documentation Galen
2011-01-06 19:37 ` Daniel Halperin
2011-01-06 20:01   ` Peter Stuge
2011-01-06 20:57     ` Daniel Halperin
2011-01-06 21:20       ` Luis R. Rodriguez
2011-01-06 21:45         ` Peter Stuge
2011-01-06 22:17           ` Luis R. Rodriguez [this message]
2011-01-06 23:04             ` Ben Greear
2011-01-06 23:14               ` Luis R. Rodriguez
2011-01-06 23:19                 ` Ben Greear
2011-01-06 23:22                   ` Luis R. Rodriguez
2011-01-06 23:31                     ` Ben Greear
2011-01-07  8:49             ` Adrian Chadd
2011-01-08 11:30               ` Luca Olivetti
2011-01-06 21:33       ` Peter Stuge
2011-01-06 22:22         ` 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=20110106221724.GC5284@tux \
    --to=lrodriguez@atheros.com \
    --cc=ath9k-devel@lists.ath9k.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.