I was asking why it acted like I compiled in a module. The sound card
requires me to compile it as a module to work (even though it can be
compiled directly into the kernel). The printerport was acting the same
way. The soundcard documenation said that I had to compile his as a
module, but nothing was said that way about the printer port.
-=>Jim Roland
"Never settle with words what you can settle with a flamethrower."
--Anonymous
On Tue, 7 Mar 2000, Tim Waugh wrote:
> Date: Tue, 7 Mar 2000 16:46:43 +0000 (GMT)
> From: Tim Waugh <[EMAIL PROTECTED]>
> To: Jim Roland <[EMAIL PROTECTED]>
> Subject: Re: Parallel port on Dell Latitude
>
> On Tue, 7 Mar 2000, Jim Roland wrote:
>
> > Okay. I combined Adrian's and Billy's info, and it works. Strange. In
> > kernel 2.2.14 Ihad to install as a module, even though I told menuconfig
> > that I wanted it as a non-module. There are not any docs that I could see
> > to tell me this (not in parport.txt nor lp.c), but the same thing happened
> > with my sound card. It had options for module or no-module (compiled in as
> > regular kernel stuff), but the README for my sound card (Neomagic 256AV)
> > said it *HAS* to be compiled as module. When I compiled the sound as
> > module, it worked great. IS LP like this from now on?
>
> I don't really understand the question. Can you explain it to me simply
> please?
>
> Tim.
> */
>
