From: Randolph Chung <randolph@tausq.org>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] kernel module relocation bug
Date: Mon, 29 Nov 2004 15:54:44 -0800 [thread overview]
Message-ID: <20041129235444.GP6359@tausq.org> (raw)
In-Reply-To: <200411292353.iATNrAc4005771@hiauly1.hia.nrc.ca>
> Another option which is probably less work is to build your kernel
> and modules with -mpa-risc-2-0. This should give you 22-bit branches.
well, except these 32-bit kernel/modules need to work on pa11 systems
too....
> There is also -mlong-calls. Not too well tested but in theory it
> should always avoid the above problem. It's much more expensive
> than -mpa-risc-2-0.
mmm.. maybe this is an option for pa11 systems.
randolph
--
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next prev parent reply other threads:[~2004-11-29 23:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-27 6:47 [parisc-linux] kernel module relocation bug Randolph Chung
2004-11-29 15:32 ` James Bottomley
2004-11-29 15:33 ` James Bottomley
2004-11-29 19:27 ` Ulrich Teichert
2004-11-29 19:46 ` Randolph Chung
2004-11-29 22:51 ` Ulrich Teichert
2004-11-29 23:46 ` John David Anglin
2004-12-02 21:54 ` [parisc-linux] Userland relocation problems resolved (was: kernel module relocation bug) Ulrich Teichert
2004-12-02 22:51 ` [parisc-linux] Re: Userland relocation problems resolved (was: kernel module relocat John David Anglin
2004-11-29 23:53 ` [parisc-linux] kernel module relocation bug John David Anglin
2004-11-29 23:54 ` Randolph Chung [this message]
2004-11-29 23:57 ` Randolph Chung
2004-11-30 0:08 ` John David Anglin
2004-11-30 0:11 ` James Bottomley
2004-11-30 0:23 ` John David Anglin
2004-11-30 1:18 ` James Bottomley
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=20041129235444.GP6359@tausq.org \
--to=randolph@tausq.org \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=parisc-linux@lists.parisc-linux.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