From owner-freebsd-current  Fri Jul 25 18:20:08 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id SAA06491
          for current-outgoing; Fri, 25 Jul 1997 18:20:08 -0700 (PDT)
Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA06473
          for <current@freebsd.org>; Fri, 25 Jul 1997 18:20:01 -0700 (PDT)
Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.6/8.6.9) with ESMTP id SAA20229; Fri, 25 Jul 1997 18:19:21 -0700 (PDT)
To: hosokawa@jp.freebsd.org
cc: current@freebsd.org
Subject: pccard and -current; a long way to go. :-(
Date: Fri, 25 Jul 1997 18:19:21 -0700
Message-ID: <20225.869879961@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Well, I've been poking at this on and off for the last 2 days now and
I can say without too much fear of contradiction that getting pccard
support up in -current is no easy job.  At least my pccardd no longer
bitches on startup, but it also fails to do anything. :-)

I also have to seriously question Nate & Mike's assertions that all is
hunky-dory in 2.2.2 land.  First off, my LINKSYS and AT&T modem cards
are _not_ supported with the stock 2.2.2 stuff, I've tried that nine
ways to Sunday, and even though upgrading to the latest and greatest
2.2.2 bits gets me past the card recognition phase, there is still the
pccardd/ifconfig startup race which Nate claimed was not an issue.
Trust me - it's an issue! :-)

So now I'm left somewhat befuddled as to the best approach to take
here.  Normally, this stuff would be developed in -current and all the
new stuff tested there, but we don't _have_ working versions (at least
not that I could test with my available hardware) in -current, so
that's kind of a washout from my perspective.  The state of the art
appears to have advanced to relative usability for me in 2.2.2+PAO, on
the other hand, but we don't check new stuff directly into RELENG_2_2
so that route's kind of out too - I can get a working 2.2+ system out
of this, but it won't be much good from the perspective of advancing
development.

I'm not sure how closely the Nomads want to work with the FreeBSD
Project on this, but if the answer is "not closely enough to support
-current" then I can see no other alternative but to pursue another,
totally new effort for solving the pccard issues in FreeBSD.

Any answers?

					Jordan