From owner-freebsd-mobile  Fri Apr  4 16:56:44 1997
Return-Path: <owner-mobile>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id QAA13731
          for mobile-outgoing; Fri, 4 Apr 1997 16:56:44 -0800 (PST)
Received: from root.com (implode.root.com [198.145.90.17])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA13710;
          Fri, 4 Apr 1997 16:56:39 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by root.com (8.8.5/8.6.5) with SMTP id QAA14294; Fri, 4 Apr 1997 16:56:40 -0800 (PST)
Message-Id: <199704050056.QAA14294@root.com>
X-Authentication-Warning: implode.root.com: localhost [127.0.0.1] didn't use HELO protocol
To: Doug White <dwhite@resnet.uoregon.edu>
cc: Just Baldrick <baldrick@rmsq.com>, freebsd-mobile@freebsd.org,
        freebsd-questions@freebsd.org
Subject: Re: FreeBSD-2.2.1 
In-reply-to: Your message of "Fri, 04 Apr 1997 10:58:37 PST."
             <Pine.BSF.3.96.970404105814.1738G-100000@localhost> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Fri, 04 Apr 1997 16:56:40 -0800
Sender: owner-mobile@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>On Fri, 4 Apr 1997, Just Baldrick wrote:
>
>> >setting flags 0x1 for npx0 (via -c at Boot:). There is a problem with
>> >the optimized bcopy code and some VGA cards.
>> 
>> This worked - I don't know why setting a flag for a math co-processor
>> fixes some interaction between bcopy code (string manipulation?)
>> and VGA cards 
>> but setting the flag to 0x1 via -c in the boot floppy
>> and subsequently adding to the kernal conf file 
>> enabled us to put up 2.2.1 on the laptop
>> thanks
>
>I saw that and it blew me away.  Thanks for the hint David.

   Incidently, the npx0 flags is a kludge. We don't yet have a way of toggling
generic kernel flags in userconfig, so instead Bruce is using the unused
flags on npx0 (which is a required device). This behavior will go away at
some point...

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project