public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Karsten Keil <kkeil@suse.de>
Cc: Jukka Partanen <jspartanen@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.4.32] Fix AVM C4 ISDN card init problems with newer CPUs
Date: Fri, 04 Aug 2006 11:00:46 +0100	[thread overview]
Message-ID: <1154685646.23655.185.camel@localhost.localdomain> (raw)
In-Reply-To: <20060803173104.GA22317@pingi.kke.suse.de>

Ar Iau, 2006-08-03 am 19:31 +0200, ysgrifennodd Karsten Keil:
> Yes, that should be go in.
> 
> AVM C4 ISDN NIC: Add three memory barriers, taken from 2.6.7,
> (they are there in 2.6.17.7 too), to fix module initialization
> problems appearing with at least some newer Celerons and
> Pentium III.
> 
> Acked-by: Karsten Keil <kkeil@suse.de>
> Signed-off-by: Jukka Partanen <jspartanen@gmail.com>

NAK: Alan Cox <alan@redhat.com>

Two reasons

#1	You should use cpu_relax in such loops
#2	The readl (which c4inmeml is a pointless #define of) is defined to be
a volatile reference itself

That means that the real bug would appear to be different and either you
have a gcc bug which is possible or you have something stranger going
on, such as the continued polling busying the microcontroller the other
end, in which case you need a delay not the lucky chance that mb() is
slowish on some x86 systems.

So you either want

		cpu_relax + other fixes
	or	udelay(something)


Alan


  reply	other threads:[~2006-08-04  9:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-03 16:53 [PATCH 2.4.32] Fix AVM C4 ISDN card init problems with newer CPUs Jukka Partanen
2006-08-03 17:31 ` Karsten Keil
2006-08-04 10:00   ` Alan Cox [this message]
2006-08-03 17:56 ` Alan Cox
2006-08-04  5:08   ` Willy Tarreau
2006-08-04  6:56   ` Willy Tarreau
2006-08-04 10:39     ` Michael Buesch
2006-08-04 12:21       ` Willy Tarreau
2006-08-04 20:14       ` Willy Tarreau

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1154685646.23655.185.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=jspartanen@gmail.com \
    --cc=kkeil@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox