Re: [PATCH 6/9] fs_enet: Be an of_platform device when CONFIG_PPC_CPM_NEW_BINDING is set.

Am Freitag, den 15.02.2008, 13:50 +0100 schrieb Laurent Pinchart: > We're loosing the possibility of having MDC and MDIO on different ports. This > is quite easy to fix for the non-CONFIG_PPC_CPM_NEW_BINDING case but I'm not > familiar with OF bindings (yet) to fix the CONFIG_PPC_CPM_NEW_BINDIN

patches "using mii-bitbang on different processor ports"

Hello! I am about this two patches. http://www.spinics.net/lists/netdev/msg45778.html http://www.spinics.net/lists/netdev/msg47159.html They was not applied. Could they be picked? Thank you Sergej. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [

Re: [PATCH for 2.6.24][NET] fs_enet: check for phydev existence in the ethtool handlers

Am Dienstag, den 08.01.2008, 22:05 +0300 schrieb Anton Vorontsov: > Otherwise oops will happen if ethernet device has not been opened: > > Unable to handle kernel paging request for data at address 0x014c > Faulting instruction address: 0xc016f7f0 > Oops: Kernel access of bad area, sig: 11 [#

[PATCH v2] using mii-bitbang on different processor ports - update the booting-without-of.txt-file

The patch updates the booting-without-of.txt-file. There is a description for the case if mdio data and clock pins are on different processor ports. It extends the "[PATCH v3] using mii-bitbang on different processor ports". Signed-off-by: Sergej Stepanov <[EMAIL PROTECTED]> Sign

Re: [PATCH] using mii-bitbang on different processor ports - update the booting-without-of.txt-file

Am Donnerstag, den 08.11.2007, 14:20 -0600 schrieb Scott Wood: > Sergej Stepanov wrote: > > If both mdio and mdc controlling pins are on the same processor port, > > one resource should be used. > > Otherwise, two resources are used: the 1-st - mdio, the 2-nd - mdc. >

Re: [PATCH] using mii-bitbang on different processor ports - update the booting-without-of.txt-file

Am Dienstag, den 06.11.2007, 12:46 -0600 schrieb Scott Wood: > > > > + The "reg"-property may have also depending on board design > > + the following form: > > + reg = <10d40 14 10d60 14>; > > + In that case the pin for mdio data controlling is on the port C, > > + and the pin for mdio

[PATCH] using mii-bitbang on different processor ports - update the booting-without-of.txt-file

The patch updates the booting-without-of.txt-file. There is a description for the case if mdio data and clock pins are on different processor ports. It is a extending for e-mail "[PATCH v3] using mii-bitbang on different processor ports". Signed-off-by: Sergej Stepanov <[EM

[PATCH v3] using mii-bitbang on different processor ports

s taken from older version. Signed-off-by: Sergej Stepanov <[EMAIL PROTECTED]> -- diff --git a/drivers/net/fs_enet/mii-bitbang.c b/drivers/net/fs_enet/mii-bitbang.c index b8e4a73..83ce0c6 100644 --- a/drivers/net/fs_enet/mii-bitbang.c +++ b/drivers/net/fs_enet/mii-bitbang.c @@ -29,12 +29

Re: [PATCH v2] using mii-bitbang on different processor ports

Am Dienstag, den 30.10.2007, 13:23 -0500 schrieb Scott Wood: > Sergej Stepanov wrote: > > + if( !of_address_to_resource(np, 1, &res[1])) { > > The spacing is still wrong. > > > - iounmap(bitbang->dir); > > + if ( bitbang->mdio.dir != bitbang-&

[PATCH v2] using mii-bitbang on different processor ports

s taken from older version. Signed-off-by: Sergej Stepanov <[EMAIL PROTECTED]> -- diff --git a/drivers/net/fs_enet/mii-bitbang.c b/drivers/net/fs_enet/mii-bitbang.c index b8e4a73..eea5feb 100644 --- a/drivers/net/fs_enet/mii-bitbang.c +++ b/drivers/net/fs_enet/mii-bitbang.c @@ -29,12 +29

Info about updates

Hello list. For our embedded platform i wrote the driver for micrel phy and integrated it into drivers/net/phy. I need general information about how do i send the patch to the netdev-list. Thanks for any advice and sorry. Best regards Sergej. -- Sergej I. Stepanov IDS GmbH Nobelstr. 18, Zim. 2