From: FORT David <epopo@onetelnet.fr>
To: David Ford <david@linux.com>,
bpemberton@dingoblue.net.au, linux-kernel@vger.kernel.org
Subject: Re: pcmcia
Date: Thu, 09 Nov 2000 03:44:06 +0100 [thread overview]
Message-ID: <3A0A0F76.BEAC838C@onetelnet.fr> (raw)
In-Reply-To: <Pine.LNX.4.21.0011091131240.9217-100000@tae-bo.generica.dyndns.org> <3A09FACF.9334A299@linux.com>
David Ford wrote:
> You may be in the same boat I'm in then. i82365 is what I used and it worked.
> yenta doesn't. Right now I'm stuck with using my USB nic because neither the
> kernel's pcmcia or dh pcmcia work for me.
>
> -d
>
> Brett wrote:
>
> > Hey,
>
[....]
>
> > > "The difference between 'involvement' and 'commitment' is like an
> > > eggs-and-ham breakfast: the chicken was 'involved' - the pig was
> > > 'committed'."
> > >
> > >
> > >
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > Please read the FAQ at http://www.tux.org/lkml/
>
> --
> "The difference between 'involvement' and 'commitment' is like an
> eggs-and-ham breakfast: the chicken was 'involved' - the pig was
> 'committed'."
I got the same problem for an old 486 with no PCI, as yenta_socket doesn't work, i
have to add CONFIG_I82365
in order to have things work. 'till this is set and recompiled, everything works
perfectly. The controller is a
VLSI 82C146.
I'm problably missing something, but these's two things i don't understand:
-why PCMCIA depends on PCI at compilation time
-why yenta is activated for i82365, as it doesn't do the job i82365 did.
--
%-------------------------------------------------------------------------%
% FORT David, %
% 7 avenue de la morvandière 0240726275 %
% 44470 Thouare, France epopo@onetelnet.fr %
% ICU:78064991 AIM: enlighted popo fort@irin.univ-nantes.fr %
%--LINUX-HTTPD-PIOGENE----------------------------------------------------%
% -datamining <-/ | .~. %
% -networking/flashed PHP3 coming soon | /V\ L I N U X %
% -opensource | // \\ >Fear the Penguin< %
% -GNOME/enlightenment/GIMP | /( )\ %
% feel enlighted.... | ^^-^^ %
% http://ibonneace.dnsalias.org/ when connected %
%-------------------------------------------------------------------------%
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-09 1:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-08 22:24 pcmcia David Feuer
2000-11-08 22:39 ` pcmcia Jeff Garzik
2000-11-08 23:59 ` pcmcia David Ford
2000-11-09 0:35 ` pcmcia Brett
2000-11-09 1:15 ` pcmcia David Ford
2000-11-09 2:44 ` FORT David [this message]
2000-11-09 2:19 ` pcmcia Horst von Brand
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=3A0A0F76.BEAC838C@onetelnet.fr \
--to=epopo@onetelnet.fr \
--cc=bpemberton@dingoblue.net.au \
--cc=david@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®