From: Kai Holthaus <kmh@sonic.net>
To: Joel Soete <soete.joel@tiscali.be>
Cc: parisc-linux <parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] Module Relocation Problem
Date: Sun, 25 Jun 2006 19:02:04 -0700 [thread overview]
Message-ID: <200606251902.11694.kmh@sonic.net> (raw)
In-Reply-To: <448B184F.7020309@tiscali.be>
[-- Attachment #1.1: Type: text/plain, Size: 1266 bytes --]
> 1. How do I compile the qc-usb driver directly into the kernel rather
> than as a standalone module?
>
> At the moment, it is not possible without a lot of work to build the
> qc-usb driver into the kernel. We recommend building qc-usb driver as a
> separate module rather than directly into the kernel. [snip]
>
> So apparently there is a few chance but regarding the generic advise it
> could be out dated, the best is certainly to contact developers to get an
> actual status ;-)
Thanks for the help and advice - here's the answer from the developer:
"I haven't tried doing this recently. I made a couple of attempts to
shoehorn the driver into the kernel build system, but it ended up being
a rathole I didn't want to go down until I've cleaned up the driver
itself. Integrating the qc-usb driver into the kernel is definitely on
the TODO list, just not right now. Sorry."
> Appology if I don't have much more help to offer (no hardware and mainly
> dramaticaly lakes of time, specialy for the moment).
This has all been very helpful. If it is indeed a problem in the hppa-linux
kernel, I'll keep a watchful eye out for fixes. If there's anything a kernel
layman like me can do, please let me know.
Thanks,
Kai
[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 169 bytes --]
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next parent reply other threads:[~2006-06-26 2:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <J0FGHF$3C34E7AFFFACE857F314B50EFB7BB29D@scarlet.be>
[not found] ` <200606101105.38472.kmh@sonic.net>
[not found] ` <448B184F.7020309@tiscali.be>
2006-06-26 2:02 ` Kai Holthaus [this message]
2006-06-26 2:10 ` [parisc-linux] Module Relocation Problem Kyle McMartin
[not found] ` <200606252124.58264.kmh@sonic.net>
2006-06-26 12:10 ` Kyle McMartin
2006-06-06 1:45 Kai Holthaus
2006-06-06 2:20 ` John David Anglin
2006-06-06 2:26 ` John David Anglin
2006-06-06 2:38 ` Kai Holthaus
2006-06-06 3:07 ` John David Anglin
2006-06-06 3:20 ` Kai Holthaus
2006-06-06 3:49 ` John David Anglin
2006-06-06 12:51 ` Thibaut VARENE
2006-06-14 8:02 ` Randolph Chung
2006-06-14 16:47 ` 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=200606251902.11694.kmh@sonic.net \
--to=kmh@sonic.net \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=soete.joel@tiscali.be \
/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