[PATCH] mmc: atmel-mci: do not assume idle after atmci_request_end

2018-10-19 Thread Jonas Danielsson
594371ddfa284bd6 ]--- This is: WARN_ON(host->cmd); This was fixed on our board by letting atmci_request_end determine what state we are in. Instead of unconditionally setting it to STATE_IDLE on STATE_END_REQUEST. Signed-off-by: Jonas Danielsson --- drivers/mmc/host/atmel-mci.c | 3 ++- 1 f

[PATCH] mmc: atmel-mci: do not assume idle after atmci_request_end

2018-10-19 Thread Jonas Danielsson
594371ddfa284bd6 ]--- This is: WARN_ON(host->cmd); This was fixed on our board by letting atmci_request_end determine what state we are in. Instead of unconditionally setting it to STATE_IDLE on STATE_END_REQUEST. Signed-off-by: Jonas Danielsson --- drivers/mmc/host/atmel-mci.c | 3 ++- 1 f

Re: [PATCH] power: reset: at91-reset: enable I-cache for at91sam9260_reset

2018-10-19 Thread Jonas Danielsson
thought on how to approach this? > Thank you, > Claudiu Beznea > Regards Jonas > > > >> Best regards, > >> Alexander > > > > Jonas > > > >> > >> > >> > > > > -- JONAS DANIELSSON Software Dev

Re: [PATCH] power: reset: at91-reset: enable I-cache for at91sam9260_reset

2018-10-19 Thread Jonas Danielsson
thought on how to approach this? > Thank you, > Claudiu Beznea > Regards Jonas > > > >> Best regards, > >> Alexander > > > > Jonas > > > >> > >> > >> > > > > -- JONAS DANIELSSON Software Dev

Re: [PATCH] power: reset: at91-reset: enable I-cache for at91sam9260_reset

2018-10-17 Thread Jonas Danielsson
On Tue, Oct 16, 2018 at 4:52 PM Alexander Stein wrote: > > On Tuesday, October 16, 2018, 3:30:24 PM CEST claudiu.bez...@microchip.com > wrote: > > Hi Jonas, > > > > On 07.10.2018 15:57, Jonas Danielsson wrote: > > > From: Jonas Danielsson > > > >

Re: [PATCH] power: reset: at91-reset: enable I-cache for at91sam9260_reset

2018-10-17 Thread Jonas Danielsson
On Tue, Oct 16, 2018 at 4:52 PM Alexander Stein wrote: > > On Tuesday, October 16, 2018, 3:30:24 PM CEST claudiu.bez...@microchip.com > wrote: > > Hi Jonas, > > > > On 07.10.2018 15:57, Jonas Danielsson wrote: > > > From: Jonas Danielsson > > > >

Re: [PATCH] power: reset: at91-reset: enable I-cache for at91sam9260_reset

2018-10-16 Thread Jonas Danielsson
abled. I wonder as well! If you have any idea I can try them out on my board tomorrow! The effect of enabling them is real. I have managed over 1000 reboots with this patch. And at the most 20 without. > Best regards, > Alexander Jonas > > On Sunday, October 7, 2018, 2:57:45 PM

Re: [PATCH] power: reset: at91-reset: enable I-cache for at91sam9260_reset

2018-10-16 Thread Jonas Danielsson
abled. I wonder as well! If you have any idea I can try them out on my board tomorrow! The effect of enabling them is real. I have managed over 1000 reboots with this patch. And at the most 20 without. > Best regards, > Alexander Jonas > > On Sunday, October 7, 2018, 2:57:45 PM

Re: [PATCH] power: reset: at91-reset: enable I-cache for at91sam9260_reset

2018-10-16 Thread Jonas Danielsson
On Tue, Oct 16, 2018 at 3:30 PM wrote: > > Hi Jonas, > Hi, > On 07.10.2018 15:57, Jonas Danielsson wrote: > > From: Jonas Danielsson > > > > This fixes a bug where our embedded system (AT91SAM9260 based) would > > hang at reboot. At the most we

Re: [PATCH] power: reset: at91-reset: enable I-cache for at91sam9260_reset

2018-10-16 Thread Jonas Danielsson
On Tue, Oct 16, 2018 at 3:30 PM wrote: > > Hi Jonas, > Hi, > On 07.10.2018 15:57, Jonas Danielsson wrote: > > From: Jonas Danielsson > > > > This fixes a bug where our embedded system (AT91SAM9260 based) would > > hang at reboot. At the most we

[PATCH] power: reset: at91-reset: enable I-cache for at91sam9260_reset

2018-10-07 Thread Jonas Danielsson
From: Jonas Danielsson This fixes a bug where our embedded system (AT91SAM9260 based) would hang at reboot. At the most we managed 16 boot loops without a hang. With this patch applied the problem has not been observed and the board has managed above 250 boot loops. The AT91SAM9260 datasheet

[PATCH] power: reset: at91-reset: enable I-cache for at91sam9260_reset

2018-10-07 Thread Jonas Danielsson
From: Jonas Danielsson This fixes a bug where our embedded system (AT91SAM9260 based) would hang at reboot. At the most we managed 16 boot loops without a hang. With this patch applied the problem has not been observed and the board has managed above 250 boot loops. The AT91SAM9260 datasheet

Regression introduced by commit dbe9a4173ea53

2015-01-23 Thread Jonas Danielsson
Hi, I have seen a regression, that I think is caused by: commit dbe9a4173ea53b72b2c35d19f676a85b69f1c9fe Author: Eric W. Biederman Date: Thu Sep 6 18:20:01 2012 + scm: Don't use struct ucred in NETLINK_CB and struct scm_cookie. With this commit the value send as uid when

Regression introduced by commit dbe9a4173ea53

2015-01-23 Thread Jonas Danielsson
Hi, I have seen a regression, that I think is caused by: commit dbe9a4173ea53b72b2c35d19f676a85b69f1c9fe Author: Eric W. Biederman ebied...@xmission.com Date: Thu Sep 6 18:20:01 2012 + scm: Don't use struct ucred in NETLINK_CB and struct scm_cookie. With this commit the value send

[PATCH][v2] net/ipv4/arp.c: Fix arp reply when sender ip 0

2007-11-20 Thread Jonas Danielsson
Fix arp reply when received arp probe with sender ip 0. Send arp reply with target ip address 0.0.0.0 and target hardware address set to hardware address of requester. Previously sent reply with target ip address and target hardware address set to same as source fields. Signed-off-by: Jonas

[PATCH][v2] net/ipv4/arp.c: Fix arp reply when sender ip 0

2007-11-20 Thread Jonas Danielsson
Fix arp reply when received arp probe with sender ip 0. Send arp reply with target ip address 0.0.0.0 and target hardware address set to hardware address of requester. Previously sent reply with target ip address and target hardware address set to same as source fields. Signed-off-by: Jonas

Re: [PATCH] net/ipv4/arp.c: Fix arp reply when sender ip 0

2007-11-16 Thread Jonas Danielsson
2007/11/16, David Miller <[EMAIL PROTECTED]>: > From: "Jonas Danielsson" <[EMAIL PROTECTED]> > Date: Thu, 15 Nov 2007 22:40:13 +0100 > > > Is there a reason that the target hardware address isn't the target > > hardware address? > > Because o

Re: [PATCH] net/ipv4/arp.c: Fix arp reply when sender ip 0

2007-11-16 Thread Jonas Danielsson
2007/11/16, David Miller [EMAIL PROTECTED]: From: Jonas Danielsson [EMAIL PROTECTED] Date: Thu, 15 Nov 2007 22:40:13 +0100 Is there a reason that the target hardware address isn't the target hardware address? Because of this, in cases where a choice can be made Linux will advertise

Re: [PATCH] net/ipv4/arp.c: Fix arp reply when sender ip 0 (was: Strange behavior in arp probe reply, bug or feature?)

2007-11-15 Thread Jonas Danielsson
Hi, I started to look at this code when I was working on a project of rewriting a dhcp-client. I wanted to make the client use arp to determine if the offered address was free or in use. Thats when I noticed that linux machines responded in this, for me, odd way. The problem is not really the

[PATCH] net/ipv4/arp.c: Fix arp reply when sender ip 0 (was: Strange behavior in arp probe reply, bug or feature?)

2007-11-15 Thread Jonas Danielsson
hardware adress in target fields. Now sends target ip and target hw as received in arp probe. Signed-off-by: Jonas Danielsson <[EMAIL PROTECTED]> --- arp.c |3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) Index: arp.c === RC

[PATCH] net/ipv4/arp.c: Fix arp reply when sender ip 0 (was: Strange behavior in arp probe reply, bug or feature?)

2007-11-15 Thread Jonas Danielsson
hardware adress in target fields. Now sends target ip and target hw as received in arp probe. Signed-off-by: Jonas Danielsson [EMAIL PROTECTED] --- arp.c |3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) Index: arp.c === RCS file

Re: [PATCH] net/ipv4/arp.c: Fix arp reply when sender ip 0 (was: Strange behavior in arp probe reply, bug or feature?)

2007-11-15 Thread Jonas Danielsson
Hi, I started to look at this code when I was working on a project of rewriting a dhcp-client. I wanted to make the client use arp to determine if the offered address was free or in use. Thats when I noticed that linux machines responded in this, for me, odd way. The problem is not really the

Strange behavior in arp probe reply, bug or feature?

2007-11-14 Thread Jonas Danielsson
Hi, I was working on a project that involved having our dhcp-client performing a check on the offered IP-address to make sure it wasn't in use. The standard way of doing this is sending out an arp request with the sender ip set to 0. (RFC2131). When I was testing out my implemented solution I

Strange behavior in arp probe reply, bug or feature?

2007-11-14 Thread Jonas Danielsson
Hi, I was working on a project that involved having our dhcp-client performing a check on the offered IP-address to make sure it wasn't in use. The standard way of doing this is sending out an arp request with the sender ip set to 0. (RFC2131). When I was testing out my implemented solution I