mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Ford <david@linux.com>
To: Brett <bpemberton@dingoblue.net.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: pcmcia
Date: Wed, 08 Nov 2000 17:15:59 -0800	[thread overview]
Message-ID: <3A09FACF.9334A299@linux.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0011091131240.9217-100000@tae-bo.generica.dyndns.org>

[-- Attachment #1: Type: text/plain, Size: 1713 bytes --]

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,
>
> I don't know if this counts as a _problem_,
> but I need to enable pci support to get pcmcia/cardbus activated.
> Is this really necessary ?? My current kernels work fine without pci
> support, and sure, enabling it won't hurt, just make the kernel bigger,
> but why is the restriction there ?
>
> Also, what has happened to the i82365 support that I need ?
> Its nicely commented out in drivers/net/pcmcia/Config.in
>
> I remember everything working fine up until about test3/4, since then I've
> had to revert to the pcmcia-cs package.
>
> Just wondering whats going on ?
>
>         / Brett
>
> On Wed, 8 Nov 2000, David Ford wrote:
> >
> > With a few exceptions, it should work.  The problematic systems are few.
> >
> > -d
> >
> > David Feuer wrote:
> >
> > > What is the current status of PC-card support?  I've seen ominous signs on
> > > this list about the state of support....  I have a laptop with a PCMCIA
> > > network card (a 3com thing). Will it work?
> >
> > --
> > "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'."



[-- Attachment #2: Card for David Ford --]
[-- Type: text/x-vcard, Size: 176 bytes --]

begin:vcard 
n:Ford;David
x-mozilla-html:TRUE
adr:;;;;;;
version:2.1
email;internet:david@kalifornia.com
title:Blue Labs Developer
x-mozilla-cpt:;14688
fn:David Ford
end:vcard

  reply	other threads:[~2000-11-09  1:16 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     ` David Ford [this message]
2000-11-09  2:44       ` pcmcia FORT David
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=3A09FACF.9334A299@linux.com \
    --to=david@linux.com \
    --cc=bpemberton@dingoblue.net.au \
    --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®