As I said off-list, I have several devices using 2313, 2315, and 2317 chips. I
will continue to work with you to test the patches as they come through.
One aspect I would propose to add is to expose information like vendor Id sub
vendor ID etc. so they can be associated properly by iwinfo to a
Hi Jonathan,
On Friday 09 November 2012 06:11:47 Jonathan Bither wrote:
> Good morning list,
> I was writing to ask if there is a current maintainer for the Atheros
> target that I may contact.
> The reason that I ask is because I was contacted about a patch that I had
> submitted prior in
Thanks,
I'll setup my git environment again and merge them all into branches
and split the patches.
On 11/09/2012 07:22 AM, John Crispin wrote:
> On 09/11/12 13:16, Karl Palsson wrote:
>> On Fri, Nov 09, 2012 at 06:11:47AM -0500, Jonathan Bither wrote:
>>> Good morning list,
>>> I was
On 09/11/12 13:16, Karl Palsson wrote:
On Fri, Nov 09, 2012 at 06:11:47AM -0500, Jonathan Bither wrote:
Good morning list,
I was writing to ask if there is a current maintainer for the Atheros
target that I may contact.
The reason that I ask is because I was contacted about a patch that
On Fri, Nov 09, 2012 at 06:11:47AM -0500, Jonathan Bither wrote:
> Good morning list,
> I was writing to ask if there is a current maintainer for the Atheros
> target that I may contact.
> The reason that I ask is because I was contacted about a patch that I had
> submitted prior in regards
Good morning list,
I was writing to ask if there is a current maintainer for the Atheros
target that I may contact.
The reason that I ask is because I was contacted about a patch that I had
submitted prior in regards to allowing various EnGenius devices to successfully
reboot without a k
