All of lore.kernel.org
 help / color / mirror / Atom feed
From: Elijah Anderson <kd0bpv@gmail.com>
To: Alessandro Suardi <alessandro.suardi@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 8139cp/too support not accessible?
Date: Thu, 12 Jun 2008 10:02:29 -0500	[thread overview]
Message-ID: <48513A85.7020002@gmail.com> (raw)
In-Reply-To: <5a4c581d0806120403n410b8deam627f4623d9b22a71@mail.gmail.com>

Thank you. That worked.

Sorry about the confusion, I just didn't know where else to ask. For 
future reference, what's a better list to ask for that sort of question?

Alessandro Suardi wrote:
> On Thu, Jun 12, 2008 at 9:02 AM, Elijah Anderson <kd0bpv@gmail.com> wrote:
>> Hey List,
>>
>> I will admit right off the bat that I'm new to interacting directly with the
>> kernel, much less building one.
>>
>> The issue I'm having is that my ethernet card requires either the 8139cp or
>> 8139too module. I don't remember which one, so I want to modularize them
>> both. Problem is, using $make xconfig; I can't select it. I have the
>> interface set to show me all the options, but the modules I need are grayed
>> out and I can't change the value.
>>
>> Using $make config; It doesn't show them, even if I say Y to "Prompt for
>> development and/or incomplete code/drivers"
>>
>> Is there a way to manually select those drivers for modularization, or am I
>> just missing a step somewhere?
>>
>> Thank you.
> 
> That's not really a kernel issue... however, since I have
>  that configuration (both drivers modular) at home, I
>  know it works :)
> 
> You probably haven't selected NET_PCI, which is the
>     entry described by
> 
>  "EISA, VLB, PCI and on board controllers"
> 
> The drivers you want depend on the above entry being selected.
> 
> --alessandro
> 
>  "Give me love / Or give me hate
>  Give me anything that's not just ok"
> 
>  (Sophia, 'Weightless')

      reply	other threads:[~2008-06-12 15:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-12  7:02 8139cp/too support not accessible? Elijah Anderson
2008-06-12 11:03 ` Alessandro Suardi
2008-06-12 15:02   ` Elijah Anderson [this message]

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=48513A85.7020002@gmail.com \
    --to=kd0bpv@gmail.com \
    --cc=alessandro.suardi@gmail.com \
    --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 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.