From: Maxim Levitsky <maximlevitsky@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Maxim Levitsky <maximlevitsky@gmail.com>,
"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 12:54:15 +0300 [thread overview]
Message-ID: <1244368455.22643.4.camel@localhost> (raw)
In-Reply-To: <1244367815.26071.4.camel@johannes.local>
On Sun, 2009-06-07 at 11:43 +0200, Johannes Berg wrote:
> On Sun, 2009-06-07 at 03:21 +0300, Maxim Levitsky wrote:
>
> > > Is this source for same firmware that was closed?
>
> Yes, but it was compiled differently afaik so you won't arrive at the
> same binary.
>
> > > Will AP mode work in future?
>
> Well, not TYPE=AP, but we'll integrate whatever is necessary into one
> firmware, I expect. It shouldn't be very hard given that AP mode really
> works with the TYPE=STA firmware already, almost.
>
> > What does this mean:
> >
> > eeprom : ORIGIN = 0x000000, LENGTH = 1024k
> >
> >
> > Does the device have whole 1M of eeprom?
> > What is there?
>
> The eeprom is mapped there, but I don't think it's 1M, it's just the max
> size of the mapping to the CPUs address space.
Fine, like I expected, but still, I guess there is some 'loader' in
eeprom?
>
> > Also what is this:
> >
> > sram : ORIGIN = 0x100000, LENGTH = 64k
>
> This is just memory. It's used for buffering frames and dma descriptors
> etc. internally. I want to change the code to do this with the linker
> script rather than manually assigning addresses in the source. But if
> you grep for this address you'll find how it's used.
Great.
>
> > Description says that pram is 32K, but:
> >
> > pram : ORIGIN = 0x200000, LENGTH = 16k
>
> Yeah, we're not exactly sure about this yet, but using 32k definitely
> crashes the device.
Thats fine too.
If there were a documentation too.
Isn't it possible to publish it?
This firmware contains so many 'magic' registers.
Best regards,
Maxim Levitsky
WARNING: multiple messages have this Message-ID (diff)
From: Maxim Levitsky <maximlevitsky@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Maxim Levitsky <maximlevitsky@gmail.com>,
"Luis R. Rodriguez" <mcgrof@gmail.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
linux-kernel@vger.kernel.org, otus-devel@venema.h4ckr.net,
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 12:54:15 +0300 [thread overview]
Message-ID: <1244368455.22643.4.camel@localhost> (raw)
In-Reply-To: <1244367815.26071.4.camel@johannes.local>
On Sun, 2009-06-07 at 11:43 +0200, Johannes Berg wrote:
> On Sun, 2009-06-07 at 03:21 +0300, Maxim Levitsky wrote:
>
> > > Is this source for same firmware that was closed?
>
> Yes, but it was compiled differently afaik so you won't arrive at the
> same binary.
>
> > > Will AP mode work in future?
>
> Well, not TYPE=AP, but we'll integrate whatever is necessary into one
> firmware, I expect. It shouldn't be very hard given that AP mode really
> works with the TYPE=STA firmware already, almost.
>
> > What does this mean:
> >
> > eeprom : ORIGIN = 0x000000, LENGTH = 1024k
> >
> >
> > Does the device have whole 1M of eeprom?
> > What is there?
>
> The eeprom is mapped there, but I don't think it's 1M, it's just the max
> size of the mapping to the CPUs address space.
Fine, like I expected, but still, I guess there is some 'loader' in
eeprom?
>
> > Also what is this:
> >
> > sram : ORIGIN = 0x100000, LENGTH = 64k
>
> This is just memory. It's used for buffering frames and dma descriptors
> etc. internally. I want to change the code to do this with the linker
> script rather than manually assigning addresses in the source. But if
> you grep for this address you'll find how it's used.
Great.
>
> > Description says that pram is 32K, but:
> >
> > pram : ORIGIN = 0x200000, LENGTH = 16k
>
> Yeah, we're not exactly sure about this yet, but using 32k definitely
> crashes the device.
Thats fine too.
If there were a documentation too.
Isn't it possible to publish it?
This firmware contains so many 'magic' registers.
Best regards,
Maxim Levitsky
next prev parent reply other threads:[~2009-06-07 9:56 UTC|newest]
Thread overview: 24+ 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:04 ` Luis R. Rodriguez
2009-06-05 19:12 ` Gábor Stefanik
2009-06-05 19:12 ` Gábor Stefanik
2009-06-05 19:24 ` Greg KH
2009-06-05 19:24 ` Greg KH
2009-06-05 22:06 ` Johannes Berg
2009-06-05 22:06 ` Johannes Berg
2009-06-06 1:54 ` Nick Kossifidis
2009-06-06 1:54 ` Nick Kossifidis
2009-06-06 6:10 ` Rami Rosen
2009-06-06 6:10 ` Rami Rosen
2009-06-06 22:22 ` Maxim Levitsky
2009-06-06 22:22 ` Maxim Levitsky
2009-06-07 0:21 ` Maxim Levitsky
2009-06-07 0:21 ` Maxim Levitsky
2009-06-07 9:43 ` Johannes Berg
2009-06-07 9:43 ` Johannes Berg
2009-06-07 9:54 ` Maxim Levitsky [this message]
2009-06-07 9:54 ` Maxim Levitsky
2009-06-07 10:24 ` Johannes Berg
2009-06-07 10:24 ` Johannes Berg
2009-06-07 12:23 ` Maxim Levitsky
2009-06-07 12:23 ` Maxim Levitsky
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=1244368455.22643.4.camel@localhost \
--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 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.