linux-kernel - Re: [ANN] Atheros 802.11n USB firmware source code released

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 07 Jun 2009 12:54:15 +0300
From:	Maxim Levitsky <maximlevitsky@...il.com>
To:	Johannes Berg <johannes@...solutions.net>
Cc:	Maxim Levitsky <maximlevitsky@...il.com>,
	"Luis R. Rodriguez" <mcgrof@...il.com>,
	linux-wireless <linux-wireless@...r.kernel.org>,
	linux-kernel@...r.kernel.org, otus-devel@...ts.madwifi-project.org,
	David Woodhouse <dwmw2@...radead.org>,
	"John W. Linville" <linville@...driver.com>
Subject: Re: [ANN] Atheros 802.11n USB firmware source code released

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/