Linux wireless drivers development
 help / color / mirror / Atom feed
From: Maxim Levitsky <maximlevitsky@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	linux-kernel@vger.kernel.org,
	otus-devel@lists.madwifi-project.org,
	David Woodhouse <dwmw2@infradead.org>,
	"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [ANN] Atheros 802.11n USB firmware source code released
Date: Sun, 07 Jun 2009 15:23:42 +0300	[thread overview]
Message-ID: <1244377422.15333.6.camel@nadejda-laptop> (raw)
In-Reply-To: <1244370250.2907.1.camel@johannes.local>

On Sun, 2009-06-07 at 12:24 +0200, Johannes Berg wrote:
> On Sun, 2009-06-07 at 12:54 +0300, Maxim Levitsky wrote:
> 
> > Fine, like I expected, but still, I guess there is some 'loader' in
> > eeprom?
> 
> Yes.
> 
> > If there were a documentation too.
> > Isn't it possible to publish it?
> > 
> > This firmware contains so many 'magic' registers.
> 
> There is some, but it's not public. We can try to document some when we
> replace the magic values by constants.
> 
> johannes

Exactly.

If you could make it public.....

I am taking even not especially about this device, but 
about ath5k AR2425.

My aspire one has several very nasty bugs, and little hope they will be
fixed, and I blame no one for that, developers are busy, and  load is
high.

But on the other hand, chances I fix them are low, I already read whole
ath5k drivers, and without documentation it is hard to see what it going
on.

The only way out I see, it to load windows driver in ndiswrapper, pray
that it will work, and then use mmiotrace to see what is done
differently. I really hate going this way.


Best regards,
	Maxim Levitsky




      reply	other threads:[~2009-06-07 12:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-05 19:04 [ANN] Atheros 802.11n USB firmware source code released Luis R. Rodriguez
2009-06-05 19:12 ` Gábor Stefanik
2009-06-05 19:24 ` Greg KH
2009-06-05 22:06 ` Johannes Berg
2009-06-06  1:54 ` Nick Kossifidis
2009-06-06  6:10   ` Rami Rosen
2009-06-06 22:22 ` Maxim Levitsky
2009-06-07  0:21   ` Maxim Levitsky
2009-06-07  9:43     ` Johannes Berg
2009-06-07  9:54       ` Maxim Levitsky
2009-06-07 10:24         ` Johannes Berg
2009-06-07 12:23           ` Maxim Levitsky [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=1244377422.15333.6.camel@nadejda-laptop \
    --to=maximlevitsky@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mcgrof@gmail.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