Please do not top-post.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
six: Don't reset PHY on if_up for ASIX 88772" breaks net on
arndale platform
On Tue, 2014-11-04 at 20:09 +, Charles Keepax wrote:
> On Tue, Nov 04, 2014 at 11:23:06AM +0100, Stam, Michel [FINT] wrote:
> > Hello Riku,
> >
> > >Fixing a bug (ethtool support)
On Tue, 2014-11-04 at 20:09 +, Charles Keepax wrote:
> On Tue, Nov 04, 2014 at 11:23:06AM +0100, Stam, Michel [FINT] wrote:
> > Hello Riku,
> >
> > >Fixing a bug (ethtool support) must not cause breakage elsewhere (in
> > this case on arndale). This is now a regression of functionality from
>
On Thu, Nov 06, 2014 at 01:39:07PM +0100, Stam, Michel [FINT] wrote:
> Hello Riku and Charles,
>
> I tried this with my original patch and the suggested patch applied,
> this seems to work for me too.
>
> One thing that bothers me, is the suspend / resume situation; usbnet.c
> seems to call the b
; Stam, Michel [FINT]; fre...@asix.com.tw;
da...@davemloft.net; linux-...@vger.kernel.org; net...@vger.kernel.org;
linux-kernel@vger.kernel.org; linux-samsung-...@vger.kernel.org
Subject: Re: "asix: Don't reset PHY on if_up for ASIX 88772" breaks net
on arndale platform
On Thu, Nov 06
On Thu, Nov 06, 2014 at 10:01:04AM +, Charles Keepax wrote:
> On Thu, Nov 06, 2014 at 11:06:51AM +0200, Riku Voipio wrote:
> > The asix on arndale comes semi-configured from u-boot, which I guess is
> > not the state kernel expects it to come in. At least in my case where
> > I use tftp from u-
On Thu, Nov 06, 2014 at 11:06:51AM +0200, Riku Voipio wrote:
> On Wed, Nov 05, 2014 at 03:02:58PM +, Charles Keepax wrote:
> > On Wed, Nov 05, 2014 at 01:04:37PM +0100, Stam, Michel [FINT] wrote:
> > > Hello Charles,
> > >
> > > After looking around I found the reset value for the 8772 chip, w
On Wed, Nov 05, 2014 at 03:02:58PM +, Charles Keepax wrote:
> On Wed, Nov 05, 2014 at 01:04:37PM +0100, Stam, Michel [FINT] wrote:
> > Hello Charles,
> >
> > After looking around I found the reset value for the 8772 chip, which
> > seems to be 0x1E1 (ANAR register).
> >
> > This equates to (a
y, November 04, 2014 10:44 AM
> To: Stam, Michel [FINT]
> Cc: Riku Voipio; da...@davemloft.net; linux-...@vger.kernel.org;
> net...@vger.kernel.org; linux-kernel@vger.kernel.org;
> linux-samsung-...@vger.kernel.org; ckee...@opensource.wolfsonmicro.com
> Subject: Re: "asix: Don&
sday, November 04, 2014 10:44 AM
To: Stam, Michel [FINT]
Cc: Riku Voipio; da...@davemloft.net; linux-...@vger.kernel.org;
net...@vger.kernel.org; linux-kernel@vger.kernel.org;
linux-samsung-...@vger.kernel.org; ckee...@opensource.wolfsonmicro.com
Subject: Re: "asix: Don't reset PHY on if_up fo
On Tue, Nov 04, 2014 at 09:19:26AM +0100, Stam, Michel [FINT] wrote:
> Interesting, as the commit itself is a revert from a kernel back to 2.6
> somewhere. The problem I had is related to the PHY being reset on
> interface-up, can you confirm that you require this?
I can't confirm what exactly is
Hello Riku,
Interesting, as the commit itself is a revert from a kernel back to 2.6
somewhere. The problem I had is related to the PHY being reset on
interface-up, can you confirm that you require this? Reverting this
breaks ethtool support in turn.
Kind regards,
Michel Stam
-Original Messa
12 matches
Mail list logo
