From: Robert Hancock <hancockr@shaw.ca>
To: Zbigniew Baniewski <zb@ispid.com.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: "modularized" 2.4.34.4 -> ide-core "unresolved symbols"
Date: Sat, 05 May 2007 20:41:52 -0600 [thread overview]
Message-ID: <463D4070.4080802@shaw.ca> (raw)
In-Reply-To: <fa.rg7bSh1mNv1yib9QUzNuRvWTPe8@ifi.uio.no>
Zbigniew Baniewski wrote:
> Hallo,
>
> I was trying to make "modularized kernel" (s.c. "Debian way") recently, yes,
> I made even kernel.deb package - but at the installation, I'm still getting
> an error: "ide-core: unresolved symbols".
>
> Making a quick search with Google I could see, it did occur to many other
> people even long ago. There was even a patch introduced - which, I believe,
> is in the 2.4.34.4 "drivers/ide" sub-dir - unfortunately it seems, that the
> patch is working no more.
>
> Perhaps there is another patch available for 2.4.34.4 ?
I don't think drivers/ide ever really played well when built modular, at
least not in 2.4, quite possibly in 2.6 as well. Things like DMA not
getting turned on automatically when the low-level driver was a module,
etc. Likely why Red Hat/Fedora never built it modular when they did
everything else..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2007-05-06 2:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.rg7bSh1mNv1yib9QUzNuRvWTPe8@ifi.uio.no>
2007-05-06 2:41 ` Robert Hancock [this message]
2007-05-05 19:49 "modularized" 2.4.34.4 -> ide-core "unresolved symbols" Zbigniew Baniewski
2007-05-06 4:36 ` Willy Tarreau
2007-05-08 20:23 ` Zbigniew Baniewski
2007-05-08 21:16 ` Willy Tarreau
2007-05-08 22:14 ` Zbigniew Baniewski
2007-05-08 22:39 ` Willy Tarreau
2007-05-08 22:53 ` Zbigniew Baniewski
2007-05-09 22:05 ` Zbigniew Baniewski
2007-05-10 9:21 ` Willy Tarreau
2007-05-12 11:08 ` 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=463D4070.4080802@shaw.ca \
--to=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=zb@ispid.com.pl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.