[PATCH] net: fec: Rename "phy-reset-active-low" property

>From the perspective of RESET, the meaning of the new property is actually "active high". Thanks for Troy Kisky for pointing that out. Since the patch is in linux-next, this patch is incremental and doesn't replace the original patch. Signed-off-by: Bernhard Walle --- Docume

Re: [PATCH] net: fec: Add "phy-reset-active-low" property to DT

Hi, sorry for my late reply. * Troy Kisky [2016-03-01 18:16]: >invalid and 1 millisecond will be used instead. > +- phy-reset-active-low : If present then the reset sequence using the GPIO > + specified in the "phy-reset-gpios" property is reversed (H=reset state, > + L=operation state). >

[PATCH v2] net: fec: Add "phy-reset-active-low" property to DT

We need that for a custom hardware that needs the reverse reset sequence. Signed-off-by: Bernhard Walle --- Changes compared to v1: - Add documentation to 'phy-reset-gpios' that flags are ignored as suggested by Andrew Lunn. Documentation/devicetree/bindings/net/fsl-f

[PATCH] net: fec: Add "phy-reset-active-low" property to DT

We need that for a custom hardware that needs the reverse reset sequence. Signed-off-by: Bernhard Walle --- Documentation/devicetree/bindings/net/fsl-fec.txt | 3 +++ drivers/net/ethernet/freescale/fec_main.c | 8 ++-- 2 files changed, 9 insertions(+), 2 deletions(-) diff --git a

Re: locking api self-test hanging

* Andrew Morton <[EMAIL PROTECTED]> [2008-02-04 14:04]: > > but that code really needs help. Using spin_lock_irqsave() is what rtc_get_rtc_time() does which was used before I changed to get_rtc_time() does. So it should be ok. I missed that difference. However, I agree with you the whole RTC "emu

Re: [PATCH] proc_fs.h redux

* Russell King <[EMAIL PROTECTED]> [2007-10-28 14:04]: > On Sun, Oct 28, 2007 at 12:59:52PM +0100, Bernhard Walle wrote: > > * Russell King <[EMAIL PROTECTED]> [2007-10-28 11:34]: > > > > > > If you go down that route, you end up with _lots_ of circular >

Re: [PATCH] proc_fs.h redux

* Russell King <[EMAIL PROTECTED]> [2007-10-28 11:34]: > > If you go down that route, you end up with _lots_ of circular > dependencies - header file X needs Y needs Z which needs X. We've > been there, several times. It very quickly becomes quite > unmaintainable - you end up with hard to predi

[PATCH] Fix config requirements of IPv6

[PATCH] Fix config requirements of IPv6 net/ipv6/inet6_connection_sock.c in function __inet6_csk_dst_store() requires flow_cache_genid which is defined in net/core/flow.c which is compiled when CONFIG_XFRM is set. This patch expresses that dependency. Signed-off-by: Bernhard Walle <[EM

Re: [PATCH] Fix crash in tg3 when using irqpoll

Hello Michael, * Michael Chan <[EMAIL PROTECTED]> [2007-03-22 23:04]: > On Thu, 2007-03-22 at 21:46 +0100, Bernhard Walle wrote: > > > This patch makes sure that even the tr32() instruction in the interrupt > > handler > > is not executed which accesses PCI mem

[PATCH] Fix crash in tg3 when using irqpoll

memory when pci_restore_state() is called is a bad idea because that function modifies the BARs of the PCI device. I think the problem could also happen when using shared interrupts, not only irqpoll. Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]> --- drivers/net/tg3.c

[PATCH] Fix oops in xfrm4_dst_destroy()

ommit with git identifier 4337226228e1cfc1d70ee975789c6bd070fb597c (Linus tree) "[IPSEC]: IPv4 over IPv6 IPsec tunnel". This patch fixes that oops. I don't know the network code of the Linux kernel in deep, so if that fix is wrong, please change it. But please fix the oops. :)

Re: r8169: Crash after reloading driver if network hangs

Hello, * Francois Romieu <[EMAIL PROTECTED]> [2007-01-29 08:56]: > Bernhard Walle <[EMAIL PROTECTED]> : > > > @@ -1371,10 +1371,9 @@ static inline void rtl8169_request_timer > > return; > > > > init_timer(ti

Re: r8169: Crash after reloading driver if network hangs

* Francois Romieu <[EMAIL PROTECTED]> [2007-01-28 20:04]: > Bernhard Walle <[EMAIL PROTECTED]> : > [...] > > Simple fix is attached. Although that seems to fix the symptom and not > > the cause, please apply it if you don't have a better solution. > > Wha

r8169: Crash after reloading driver if network hangs

Hello, also after applying the latest patch that was posted on that mailing list, I have still the problem described in http://bugzilla.kernel.org/show_bug.cgi?id=5137. So after a network hang with several NETDEV WATCHDOG: eth0: transmit timed out in the kernel log, I removed the drive

Re: [rft] r8169: merge release 6.001.00 of Realtek's driver - take #1

* Francois Romieu <[EMAIL PROTECTED]> [2007-01-25 00:17]: > Untested, straight from the "release early" dept. You have been warned. Works here. Regards, Bernhard - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info