From: "Joel Soete" <jsoe0708@tiscali.be>
To: "Matthew Wilcox" <willy@debian.org>,
"Mark Mestdagh" <Mark.Mestdagh@Icon-Europe.com>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Kernel compilation for J5600
Date: Tue, 1 Jul 2003 16:03:27 +0200 [thread overview]
Message-ID: <3ED71F6D0000C050@ocpmta7.freegates.net> (raw)
In-Reply-To: <20030701132146.GD23597@parcelfarce.linux.theplanet.co.uk>
Hi all,
> > drivers/ide/idedriver.o(.text.probe_hwif+0xfc): undefined reference to
> > `local_irq_set'
> This is 2.4.21-pa1?
Hmm not yet and my patch to Grant is definitely incomplete (Sorry, my bad).
In fact I am hesitate:
For many other paltform we can found:
(in system_irqsave.h)
[...]
/* For spinlocks etc */
#define local_irq_save(x) __save_and_cli(x)
#define local_irq_set(x) __save_and_sti(x)
#define local_irq_restore(x) __restore_flags(x)
#define local_irq_disable() __cli()
[...]
OTC for parisc:
[...]
#define local_irq_save(x) \
__asm__ __volatile__("rsm %1,%0" : "=r" (x) :"i" (PSW_I) : "memory" )
#define local_irq_restore(x) \
__asm__ __volatile__("mtsm %0" : : "r" (x) : "memory" )
[...]
So can we here simply add:
#define local_irq_set(x) __save_and_sti(x)
Or do we actualy need a specific local_irq_set(x)?
Thanks in advance for advise,
Joel
---------------------------------
Tiscali ADSL: 19,50 euros/mois...abonnez-vous sur www.tiscali.be
next prev parent reply other threads:[~2003-07-01 14:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-30 6:13 [parisc-linux] Kernel compilation for J5600 Mark Mestdagh
2003-06-30 6:30 ` Randolph Chung
2003-06-30 16:50 ` Grant Grundler
2003-07-01 8:10 ` Mark Mestdagh
2003-07-01 13:21 ` Matthew Wilcox
2003-07-01 14:00 ` Mark Mestdagh
2003-07-01 14:03 ` Joel Soete [this message]
2003-07-05 3:20 ` Grant Grundler
2003-07-04 10:01 ` [parisc-linux] Kernel compilation for B2000 Mark Mestdagh
2003-07-04 13:56 ` Joel Soete
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=3ED71F6D0000C050@ocpmta7.freegates.net \
--to=jsoe0708@tiscali.be \
--cc=Mark.Mestdagh@Icon-Europe.com \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=willy@debian.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