From: Eric Valette <eric.valette@free.fr>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: RE : 2.6.6-rc3-mm2 : REGPARAM forced => no external module with some object code only
Date: Wed, 05 May 2004 13:56:13 +0200 [thread overview]
Message-ID: <4098D65D.9010107@free.fr> (raw)
Andrew,
The Changelog says nothing really important but forcing REGPARAM is
rather important : it breaks any external module using object only code
that calls a kernel function.
I do not want to enter the "binary module" debate just reports facts so
that people be aware of the problem.
I have a bewan PCI ST ADSL modem. They provide a linux driver that works
with 2.6 like a charm but contains an object file. And of course code
located in this object only file breaks because it calls alloc_obj:
alloc_obj:kmalloc failed,size=-742088876,type=abc0
Complete stack trace attached... (that shows they do not expect kmalloc
to fail :-( )
Do not blame Bewan : they have always been very responsive and do
provide an almost GPL compliant module that works with 2.4 and 2.6
kernels like a charm. In particular, fixing the code to support 2.6
module generation scheme has only taken in a couple of weeks after I
politely asked to the maintainer sending an initial patch. They are just
dependent on STMicro (if I remember correctly) for the library that
drives the ATM chipset and apparently they failed to ask them to open up
their code...
Maybe they can just ask them to compile with regpram=3 but anyway as an
end-user I have no solution...
I will report the bug to my contact...
--
__
/ ` Eric Valette
/-- __ o _. 6 rue Paul Le Flem
(___, / (_(_(__ 35740 Pace
Tel: +33 (0)2 99 85 26 76 Fax: +33 (0)2 99 85 26 76
E-mail: eric.valette@free.fr
next reply other threads:[~2004-05-05 11:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-05 11:56 Eric Valette [this message]
2004-05-05 12:09 ` Re : 2.6.6-rc3-mm2 : REGPARAM forced => no external module with some object code only Eric Valette
2004-05-05 20:18 ` RE " Andrew Morton
2004-05-06 12:44 ` Zephaniah E. Hull
2004-05-06 12:56 ` Jan-Benedict Glaw
2004-05-06 13:05 ` Eric Valette
2004-05-06 15:21 ` Andrew Morton
2004-05-09 17:03 ` Bill Davidsen
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=4098D65D.9010107@free.fr \
--to=eric.valette@free.fr \
--cc=akpm@osdl.org \
--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