On Sat, 2013-11-16 at 16:15 +0100, Lennert Buytenhek wrote:
What needs to be done is that someone with access to the relevant
Marvell datasheets fix the driver to behave according to which chip
it's being used on. It's quite a bit of work to sort out this mess,
easily several tens of hours --
On Sun, 2013-11-17 at 18:04 +, Ben Hutchings wrote:
On Sun, 2013-11-17 at 14:27 +, Ian Campbell wrote:
On Sun, 2013-11-17 at 13:16 +, Ben Hutchings wrote:
The number of ports is the last-but-one digit in the PHY model number so
we could remove everything with a 4 there.
[...]
Hi Lennert,
Lennert Buytenhek buyt...@wantstofly.org writes:
The problem here was that the Marvell PHY driver at some point supported
one or two specific Marvell ethernet PHY models, and people then started
blindly adding new PHY IDs to it without checking whether the already
supported PHYs
On Sun, 2013-11-17 at 10:12 +0100, Michael Stapelberg wrote:
Hi Lennert,
Lennert Buytenhek buyt...@wantstofly.org writes:
The problem here was that the Marvell PHY driver at some point supported
one or two specific Marvell ethernet PHY models, and people then started
blindly adding new
On Sun, 2013-11-17 at 10:43 +, Ian Campbell wrote:
On Sun, 2013-11-17 at 10:12 +0100, Michael Stapelberg wrote:
Hi Lennert,
Lennert Buytenhek buyt...@wantstofly.org writes:
The problem here was that the Marvell PHY driver at some point supported
one or two specific Marvell
On Sun, 2013-11-17 at 13:16 +, Ben Hutchings wrote:
On Sun, 2013-11-17 at 10:43 +, Ian Campbell wrote:
On Sun, 2013-11-17 at 10:12 +0100, Michael Stapelberg wrote:
Hi Lennert,
Lennert Buytenhek buyt...@wantstofly.org writes:
The problem here was that the Marvell PHY driver
On Sun, 2013-11-17 at 14:27 +, Ian Campbell wrote:
On Sun, 2013-11-17 at 13:16 +, Ben Hutchings wrote:
On Sun, 2013-11-17 at 10:43 +, Ian Campbell wrote:
On Sun, 2013-11-17 at 10:12 +0100, Michael Stapelberg wrote:
Hi Lennert,
Lennert Buytenhek buyt...@wantstofly.org
On Mon, Nov 11, 2013 at 11:37:53AM -0800, Martin Michlmayr wrote:
I want to enable Wake On Lan on my qnap TS-119P II. In order to do this,
the kernel needs to use code that is specific to the marvell PHY,
m88e1318_get_wol and m88e1318_set_wol from drivers/net/phy/marvell.c to
be
git svn tells me that r14178 was the following.
commit a3535d328fe523c7c3dd0db212ee4f34d2c40583
Author: tbm tbm@510b9475-24dd-0310-9b6c-e0eefe99d49f
Date: Sun Aug 23 15:51:33 2009 +
[armel/orion5x, armel/kirkwood] Disable MARVELL_PHY since it may
lead to conflicts with the
Hi Martin,
Martin Michlmayr t...@cyrius.com writes:
git svn tells me that r14178 was the following.
commit a3535d328fe523c7c3dd0db212ee4f34d2c40583
Author: tbm tbm@510b9475-24dd-0310-9b6c-e0eefe99d49f
Date: Sun Aug 23 15:51:33 2009 +
[armel/orion5x, armel/kirkwood] Disable
* Michael Stapelberg stapelb...@debian.org [2013-11-15 18:59]:
Please set CONFIG_MARVELL_PHY=m for the kirkwood kernel builds. In case
anyone notices any breakage, let’s figure out a way to deal with it,
even if that way ends up just being a better comment on the disabled
build option :).
No
Hi Martin,
Martin Michlmayr t...@cyrius.com writes:
No objection from me (although it might be a good idea to ask the
upstream Kirkwood/Orion folks first).
How can we contact them? Is there an email address? Also, who can
actually make the change to the kernel config? Do you have the commit
bit
* Michael Stapelberg stapelb...@debian.org [2013-11-15 23:33]:
Martin Michlmayr t...@cyrius.com writes:
No objection from me (although it might be a good idea to ask the
upstream Kirkwood/Orion folks first).
How can we contact them? Is there an email address?
I'd email:
Thomas Petazzoni
On Mon, 2013-11-11 at 11:37 -0800, Martin Michlmayr wrote:
Unfortunately I cannot remember (and I cannot even read the commit
messages right now because Alioth is done).
git svn tells me that r14178 was the following.
commit a3535d328fe523c7c3dd0db212ee4f34d2c40583
Author: tbm
* Michael Stapelberg stapelb...@debian.org [2013-11-10 09:58]:
I want to enable Wake On Lan on my qnap TS-119P II. In order to do this,
the kernel needs to use code that is specific to the marvell PHY,
m88e1318_get_wol and m88e1318_set_wol from drivers/net/phy/marvell.c to
be specific.
Hi,
Michael Stapelberg stapelb...@debian.org writes:
I want to enable Wake On Lan on my qnap TS-119P II. In order to do this,
the kernel needs to use code that is specific to the marvell PHY,
m88e1318_get_wol and m88e1318_set_wol from drivers/net/phy/marvell.c to
be specific. This code can be
Package: linux-image-3.10-3-kirkwood
Version: 3.10.11-1
Severity: normal
Hi,
I hope I am filing this in the right place, if not, please reassign
accordingly.
I want to enable Wake On Lan on my qnap TS-119P II. In order to do this,
the kernel needs to use code that is specific to the marvell
17 matches
Mail list logo
