public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kalin KOZHUHAROV <kalin@thinrope.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Problem getting PCMCIA to compile in Kernel.
Date: Sat, 14 Jan 2006 01:40:28 +0900	[thread overview]
Message-ID: <dq8l5t$fg0$1@sea.gmane.org> (raw)
In-Reply-To: <43C8252F.6483.C6B2A8@mikes.kuentos.guam.net>

Michael D. Setzer II wrote:
> I've tried to set the PCMCIA options to Y in the kernel build, but get a 
> message that something else is build as a modual, so these can not be 
> changed to y.

How did you do that?

Use `make menuconfig` to configure kernel.

> I went to the .config file and replaced every =m to =y, and then 
> ran make. The kernel then was built with no problem, but it reset all these 
> option back to =m.
> 
> CONFIG_PCMCIA_AHA152X=m
> CONFIG_PCMCIA_FDOMAIN=m
> CONFIG_PCMCIA_NINJA_SCSI=m
> CONFIG_PCMCIA_QLOGIC=m
> CONFIG_PCMCIA_SYM53C500=m
> CONFIG_I2C_STUB=m
> 
> I build kernels for G4L, and build everything directly into the kernel, but 
> these do not seem to work, and I don't have an ideal why, since everything 
> else is built in. So what am I missing. This is the 2.6.15 kernel. 

If you play with .config directly, run a `make oldconfig` after that.
So, `make oldconfig && make && make` should always work.
If you tired that ant it did NOT, please post your .config file (not
compressed) here, or upload it to a website (somewhere).

Kalin.

-- 
|[ ~~~~~~~~~~~~~~~~~~~~~~ ]|
+-> http://ThinRope.net/ <-+
|[ ______________________ ]|


  reply	other threads:[~2006-01-13 16:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-13 12:09 Problem getting PCMCIA to compile in Kernel Michael D. Setzer II
2006-01-13 16:40 ` Kalin KOZHUHAROV [this message]
2006-01-13 17:32   ` Michael D. Setzer II
2006-01-13 19:12     ` Kalin KOZHUHAROV

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='dq8l5t$fg0$1@sea.gmane.org' \
    --to=kalin@thinrope.net \
    --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