From owner-freebsd-mobile  Thu Jun 19 08:41:20 1997
Return-Path: <owner-mobile>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id IAA02871
          for mobile-outgoing; Thu, 19 Jun 1997 08:41:20 -0700 (PDT)
Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA02866
          for <mobile@freebsd.org>; Thu, 19 Jun 1997 08:41:17 -0700 (PDT)
Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id JAA10101; Thu, 19 Jun 1997 09:41:05 -0600 (MDT)
Date: Thu, 19 Jun 1997 09:41:05 -0600 (MDT)
Message-Id: <199706191541.JAA10101@rocky.mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: John Robert LoVerso <loverso@opengroup.org>
Cc: Nate Williams <nate@mt.sri.com>, Peter Dufault <dufault@hda.com>,
        mobile@freebsd.org
Subject: Re: 3c589d and ep0 
In-Reply-To: <199706181826.OAA08067@postman.opengroup.org>
References: <nate@mt.sri.com>
	<199706181810.MAA04323@rocky.mt.sri.com>
	<199706181826.OAA08067@postman.opengroup.org>
X-Mailer: VM 6.29 under 19.15 XEmacs Lucid
Sender: owner-mobile@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> 	What is the timeframe with pulling all the PAO code into some
> 	official branch of FreeBSD?

That's not going to happen as long as I'm responsible for the laptop
support.  No offense to the Nomads, but there are *huge* kluges in the
code where the correct fix wasn't even attempted, but instead a 'quick'
fix which fixed the problem (but hid the real prolblem) was made.
Sometimes these fixes affect desktop units, so applying the patches
whole-sale could often times negatively affect the stability of
'standard' FreeBSD installations.

In the past I've fixed what I felt to be the worse offenders, but the
entire 'pccard' daemon code really needs to be re-written to make it
much simpler than it is now.  The original author did a wonderful job,
but he never finished it so there are portions of unused code,
undocumented code, and such that have been extended in ways that are
probably incorrect.  Now that we understand things a bit better, lots of
those extensions aren't necessary, so we should be able to simplify
things alot more thus making the PAO code less 'obtrusive'.


Nate