From: Abramo Bagnara <abramo@alsa-project.org>
To: Richard Henderson <rth@twiddle.net>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [2*PATCH] alpha I/O access and mb()
Date: Mon, 11 Dec 2000 09:00:10 +0100 [thread overview]
Message-ID: <3A34898A.8629587F@alsa-project.org> (raw)
In-Reply-To: <3A31F094.480AAAFB@alsa-project.org> <20001209161013.A30555@twiddle.net> <3A334F7C.3205A3DF@alsa-project.org> <20001210104413.A31257@twiddle.net> <3A33D3A7.FCD55F4@alsa-project.org> <20001210124918.A31383@twiddle.net> <3A33F448.258A731@alsa-project.org> <20001210161955.A31596@twiddle.net>
Before of all I want to publicly apologize with Richard as never my
intention was to exacerbate him.
>
> On Sun, Dec 10, 2000 at 10:23:20PM +0100, Abramo Bagnara wrote:
> > asm/io.h uses out of line function only when CONFIG_ALPHA_GENERIC is
> > defined, otherwise it uses (take writel as an example) __raw_writel that
> > IMHO need to be defined in core_t2.h.
>
> Perhaps you should _show_ an actual failure rather than just guessing.
I've not access to this specific hardware but I was trying to fix the
alpha case wrt write[bwlq] function as I've had a lot of trouble with
ALSA drivers and 2.2 (that still now is broken wrt mb() and I've sent a
patch to Alpha Processor guys). This is the reason why I've given a look
to 2.4.
>
> You are wildly incorrect asserting that out of line functions are used
> only with CONFIG_ALPHA_GENERIC. You should examine
>
> #ifndef __raw_writel
> # define __raw_writel(v,a) ___raw_writel((v),(unsigned long)(a))
> #endif
>
> and suchlike definitions.
Now I understand, thanks.
I see that some core*.h leaves out of line some functions because they
are more complex than a choosen threshold.
--
Abramo Bagnara mailto:abramo@alsa-project.org
Opera Unica Phone: +39.546.656023
Via Emilia Interna, 140
48014 Castel Bolognese (RA) - Italy
ALSA project is http://www.alsa-project.org
sponsored by SuSE Linux http://www.suse.com
It sounds good!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2000-12-11 8:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-09 8:43 [2*PATCH] alpha I/O access and mb() Abramo Bagnara
2000-12-09 10:12 ` Gérard Roudier
2000-12-09 11:32 ` Abramo Bagnara
2000-12-09 13:46 ` Gérard Roudier
2000-12-10 0:10 ` Richard Henderson
2000-12-10 9:40 ` Abramo Bagnara
2000-12-10 18:44 ` Richard Henderson
2000-12-10 19:04 ` Abramo Bagnara
2000-12-10 20:49 ` Richard Henderson
2000-12-10 21:23 ` Abramo Bagnara
2000-12-11 0:19 ` Richard Henderson
2000-12-11 8:00 ` Abramo Bagnara [this message]
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=3A34898A.8629587F@alsa-project.org \
--to=abramo@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rth@twiddle.net \
/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