On Thu, Dec 3, 2015 at 1:19 AM, wrote:
> From: Igal Liberman
>
> This patch adds the Ethernet MAC driver supporting the three
> different types of MACs: dTSEC, tGEC and mEMAC.
>
> Signed-off-by: Igal Liberman
[...]
> +
> +MODULE_LICENSE("Dual BSD/GPL");
> +
> +MODULE_AUTHOR("Emil Medve ");
I
No functional changes other than to recognize this PHYID.
Signed-off-by: Andy Fleming
Signed-off-by: Kumar Gala
Signed-off-by: Ben Collins
Cc: net...@vger.kernel.org
---
drivers/net/phy/vitesse.c | 17 -
1 file changed, 16 insertions(+), 1 deletion(-)
diff --git a/drivers/net
of_phy_connect is useful for most systems, but some drivers will want
finer-grained control over their PHYs, and won't want to use the
PHY Lib state machine or interrupt handlers.
This mirrors phy_attach() in libphy, which is already exported.
Signed-off-by: Andy Fleming
Signed-off-by
.
Signed-off-by: Andy Fleming
Signed-off-by: Ben Collins
Cc: net...@vger.kernel.org
---
include/linux/netdev_features.h | 2 ++
net/core/dev.c | 6 ++
2 files changed, 8 insertions(+)
diff --git a/include/linux/netdev_features.h b/include/linux/netdev_features.h
index
abstraction layer.
I 've tetsted this with the macb driver.
Signed-off-by: Rini van Zetten <[EMAIL PROTECTED]>
Acked-by: Andy Fleming <[EMAIL PROTECTED]>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PRO
gned-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
Acked-by: Andy Fleming <[EMAIL PROTECTED]>
---
I think I copied that code from elsewhere without truly understanding
it.
*bows head in shame*
As such, I have no objection to this patch unless someone says it
breaks their boa
On Mar 2, 2007, at 11:42, Shan Lu wrote:
Changelog:
Function `phy_mii_ioctl' returns physical device's information
based on
user requests. When requested to return the basic mode control
register
information (BMCR), the original implementation only returns the
physical device's duplex info
On Dec 7, 2006, at 11:05, Jeff Garzik wrote:
Yes, I merged the code, but looking deeper at phy its clear I
missed some things.
Looking into libphy's workqueue stuff, it has the following sequence:
disable interrupts
schedule_work()
... time passes ...
... wo
On Dec 5, 2006, at 14:39, Andrew Morton wrote:
On Tue, 5 Dec 2006 17:48:05 + (GMT)
"Maciej W. Rozycki" <[EMAIL PROTECTED]> wrote:
Essentially there is a race when disconnecting from a PHY, because
interrupt delivery uses the event queue for processing. The
function to
handle interrupt
On Dec 5, 2006, at 00:03, Benjamin Herrenschmidt wrote:
I believe that this fiber enabling can be done by defining
config_init in the phy_driver struct.
struct phy_driver {
/* Called to initialize the PHY,
* including after a reset */
int (*config_init)(struct phy
On Dec 5, 2006, at 11:48, Maciej W. Rozycki wrote:
Essentially there is a race when disconnecting from a PHY, because
interrupt delivery uses the event queue for processing. The
function to
handle interrupts that is called from the event queue is phy_change().
It takes a pointer to a stru
On Sep 9, 2005, at 05:10, Bogdan Costescu wrote:
On Thu, 8 Sep 2005, Andy Fleming wrote:
Is the cost of an extra read every minute really too high?
You probably didn't look at the code. The MII registers are not
exposed in the PCI space, they need to be accessed through a s
On Sep 8, 2005, at 10:42, Bogdan Costescu wrote:
On Thu, 8 Sep 2005, Tommy Christensen wrote:
Personally, I'd prefer the delay to be < 10 seconds.
If you sample every 60 seconds ? Teach Shannon how to do it ;-)
If you mean to reduce the sampling period, there is a very good
reason not t
13 matches
Mail list logo
