netdev - Re: [PATCH] alx: add a simple AR816x/AR817x device driver

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 for Android: free password hash cracker in your pocket

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

Message-ID: <1371327319.14174.1.camel@jlt4.sipsolutions.net>
Date:	Sat, 15 Jun 2013 22:15:19 +0200
From:	Johannes Berg <johannes@...solutions.net>
To:	Johannes Stezenbach <js@...21.net>
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH] alx: add a simple AR816x/AR817x device driver

On Sat, 2013-06-15 at 20:26 +0200, Johannes Berg wrote:
> On Fri, 2013-06-14 at 07:53 +0200, Johannes Stezenbach wrote:
> 
> > > Does it still pass traffic after that? Or is it actually dead?
> > 
> > It is dead.  Not interrupts, I tried ping from both ends
> > of the link (link LED flashes on RX).
> 
> Can you check if one of RX actually works? It seems TX doesn't, at least
> given the message, but it'd be good to know if RX actually worked? Just
> trying ping obviously wouldn't determine that, maybe try tcpdump?
> 
> I don't see any difference between 8171 and 8161 in the TX code
> though ...

FWIW I tried again on my device against 3.9.6, and it works fine :-/

Latest code is here: http://p.sipsolutions.net/c2e7235ba77373f0.txt in
case you want to retry that.

I'm assuming you did try the QCA driver and it works?

johannes

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html