From owner-freebsd-mobile  Tue Jan 28 12:25:41 1997
Return-Path: <owner-mobile>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id MAA08147
          for mobile-outgoing; Tue, 28 Jan 1997 12:25:41 -0800 (PST)
Received: from lenlen.mt.cs.keio.ac.jp (lenlen.mt.cs.keio.ac.jp [131.113.32.126])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA08124
          for <mobile@freebsd.org>; Tue, 28 Jan 1997 12:24:54 -0800 (PST)
Received: (from hosokawa@localhost) by lenlen.mt.cs.keio.ac.jp (8.8.4/8.8.2) id FAA03167; Wed, 29 Jan 1997 05:20:57 +0900 (JST)
Date: Wed, 29 Jan 1997 05:20:57 +0900 (JST)
Message-Id: <199701282020.FAA03167@lenlen.mt.cs.keio.ac.jp>
To: mobile@freebsd.org
Subject: I want to restructure pccardd....
From: hosokawa@mt.cs.keio.ac.jp (HOSOKAWA Tatsumi)
X-Mailer: mnews [version 1.19PL2] 1996-01/26(Fri)
Sender: owner-mobile@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I'm planning to rewrite pccardd (and related interface of sys/pccard)
from scratch because,

1. To extend the syntax of pccard.conf is very difficult because it
   uses a parser written in plain C.

2. Very early version of pccardd only supports one I/O window and
   fixed parameters, etc.  I added many hack to overcome these limits.
   But now, I want to support complete PnP resource configuration of
   PC-cards and I want to add multifunction card support.  I tried to
   add these features as hack for pccardd, but it's too difficult.  I
   abandoned this project.

3. The current design of 'ether' subcommand in pccard.conf is not good
   because it mainly focuses upon support for NE2000 compatible cards
   (I'm talking about how pccardd uses 'misc' member of slot
   structure, not about the syntax of pccard.conf).  Megahertz's cards
   and WaveLAN uses very different scheme to pass MAC address to the
   card.

I want to implement new pccardd in C and lex/yacc.  I'm nurvous about
programming language because I was involved in a flame war in another
mailing list about the programming language of metaconfiguration
system of kernel structure :-), but I think C is the best language for
this purpose.  I think Perl (and Tcl) can be alternative, but using a
fat interpreter is bad idea for daemons, and utilities incorporated
into boot.flp.

Any comments?

I have time in March (I'm too busy this February).  If there are no
strong complaints about this project, I'll entirely rewrite pccardd
(and write multifunction card support) this March.

--
HOSOKAWA, Tatsumi
hosokawa@mt.cs.keio.ac.jp
hosokawa@jp.FreeBSD.org

From owner-freebsd-mobile  Tue Jan 28 14:07:35 1997
Return-Path: <owner-mobile>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id OAA14028
          for mobile-outgoing; Tue, 28 Jan 1997 14:07:35 -0800 (PST)
Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA14022
          for <mobile@freebsd.org>; Tue, 28 Jan 1997 14:07:25 -0800 (PST)
Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id PAA24236; Tue, 28 Jan 1997 15:06:47 -0700 (MST)
Date: Tue, 28 Jan 1997 15:06:47 -0700 (MST)
Message-Id: <199701282206.PAA24236@rocky.mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
To: hosokawa@mt.cs.keio.ac.jp (HOSOKAWA Tatsumi)
Cc: mobile@freebsd.org
Subject: Re: I want to restructure pccardd....
In-Reply-To: <199701282020.FAA03167@lenlen.mt.cs.keio.ac.jp>
References: <199701282020.FAA03167@lenlen.mt.cs.keio.ac.jp>
Sender: owner-mobile@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> I'm planning to rewrite pccardd (and related interface of sys/pccard)
> from scratch because,
> 
> 1. To extend the syntax of pccard.conf is very difficult because it
>    uses a parser written in plain C.

True, but see below.

> 2. Very early version of pccardd only supports one I/O window and
>    fixed parameters, etc.  I added many hack to overcome these limits.
>    But now, I want to support complete PnP resource configuration of
>    PC-cards and I want to add multifunction card support.  I tried to
>    add these features as hack for pccardd, but it's too difficult.  I
>    abandoned this project.

Multifunction card support shouldn't be too hard to add, but this also
requires some non-significant kernel modifications.  (Though they aren't
too terribly difficult.)

> 3. The current design of 'ether' subcommand in pccard.conf is not good
>    because it mainly focuses upon support for NE2000 compatible cards
>    (I'm talking about how pccardd uses 'misc' member of slot
>    structure, not about the syntax of pccard.conf).

Agreed.  That's why it's not in -current. :) :)

> I want to implement new pccardd in C and lex/yacc.  I'm nurvous about
> programming language because I was involved in a flame war in another
> mailing list about the programming language of metaconfiguration
> system of kernel structure :-), but I think C is the best language for
> this purpose.  I think Perl (and Tcl) can be alternative, but using a
> fat interpreter is bad idea for daemons, and utilities incorporated
> into boot.flp.
> 
> Any comments?

I'd like to see pccardd become *much* simpler.  Basically, the only
thing the userland utility should have to do is:
1) Figure out the card <-> kernel driver mapping
2) Read the CIS structures and pass in all relevant information to
   the kernel.

Currently, it does lots of selecting of resources, and I believe this is
a bad thing for a couple of reasons.

1) It doesn't know what resources are *really* available.  The kernel
   knows (or can be modified) which ports are free, which IRQ's are
   unused, etc..  The user-land code does not.

2) You can't boot from a PCCARD disk/FLASH card simply because you have
   to be running in multi-user mode before it will be recognized.  By
   moving alot of the resource handling in the kernel it would be easier
   to have a really simple CIS reader in the kernel for embedded
   systems.  (Easier said than done.)

3) It requires too much 'card-specific' information to be
   known/understood by the user.

I'd like to see a much simpler syntax, rather than a more complicated
syntax used in /etc/pccard.conf.

Ie:
card "3Com Corporation" "3C589"
     driver 'ep'
     insert echo "3Com Etherlink III inserted"
     insert /etc/pccard_ether ep0 -link0 link1
     remove echo "3Com Etherlink III removed"
     remove /sbin/ifconfig ep0 delete

And, the card daemon would pass the 'available' parameters it can use
to the kernel, instead of picking one.  The user-land daemon could build
up the list of 'usable' configurations and the kernel could choose the
one that matched it's list of available resources.

I think this would make things *much* easier to deal with, but would
still leave most of the complexity (CIS tuple reading) in user-land.

And, if you had a 'known' CIS tuple the kernel could do a simple
recognition on it and boot from it.  (Again, this would be useful to
embedded systems who are less concerned about people throwing in funky
new PCCARDs).

What do you think?



Nate

From owner-freebsd-mobile  Tue Jan 28 17:28:55 1997
Return-Path: <owner-mobile>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id RAA28891
          for mobile-outgoing; Tue, 28 Jan 1997 17:28:55 -0800 (PST)
Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA28873
          for <mobile@freebsd.org>; Tue, 28 Jan 1997 17:28:46 -0800 (PST)
Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id LAA14542; Wed, 29 Jan 1997 11:58:16 +1030 (CST)
From: Michael Smith <msmith@atrad.adelaide.edu.au>
Message-Id: <199701290128.LAA14542@genesis.atrad.adelaide.edu.au>
Subject: Re: I want to restructure pccardd....
In-Reply-To: <199701282020.FAA03167@lenlen.mt.cs.keio.ac.jp> from HOSOKAWA Tatsumi at "Jan 29, 97 05:20:57 am"
To: hosokawa@mt.cs.keio.ac.jp (HOSOKAWA Tatsumi)
Date: Wed, 29 Jan 1997 11:58:15 +1030 (CST)
Cc: mobile@freebsd.org
X-Mailer: ELM [version 2.4ME+ PL28 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-mobile@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

HOSOKAWA Tatsumi stands accused of saying:
> 
> I want to implement new pccardd in C and lex/yacc.  I'm nurvous about
> programming language because I was involved in a flame war in another
> mailing list about the programming language of metaconfiguration
> system of kernel structure :-), but I think C is the best language for
> this purpose.  I think Perl (and Tcl) can be alternative, but using a
> fat interpreter is bad idea for daemons, and utilities incorporated
> into boot.flp.

I agree with you entirely here; and likewise with Nate's sentiments that
pccardd is trying to do too much.

As I see it, pccardd's total purpose in life is limited to :

 - Cross-referencing CIS details against a database to decide which 
   driver and parameters are appropriate.
 - Running a user-mode script if the card is accepted.
 - Running a user-mode script when a card goes away.

I really don't think that it should try to do anything more.

> HOSOKAWA, Tatsumi

-- 
]] Mike Smith, Software Engineer        msmith@gsoft.com.au             [[
]] Genesis Software                     genesis@gsoft.com.au            [[
]] High-speed data acquisition and      (GSM mobile)     0411-222-496   [[
]] realtime instrument control.         (ph)          +61-8-8267-3493   [[
]] Unix hardware collector.             "Where are your PEZ?" The Tick  [[

From owner-freebsd-mobile  Tue Jan 28 23:38:19 1997
Return-Path: <owner-mobile>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id XAA16218
          for mobile-outgoing; Tue, 28 Jan 1997 23:38:19 -0800 (PST)
Received: from lenlen.mt.cs.keio.ac.jp (dhcp2.mt.cs.keio.ac.jp [131.113.32.182])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA15929
          for <mobile@freebsd.org>; Tue, 28 Jan 1997 23:33:47 -0800 (PST)
Received: (from hosokawa@localhost) by lenlen.mt.cs.keio.ac.jp (8.8.4/8.8.2) id QAA03592; Wed, 29 Jan 1997 16:27:01 +0900 (JST)
Date: Wed, 29 Jan 1997 16:27:01 +0900 (JST)
Message-Id: <199701290727.QAA03592@lenlen.mt.cs.keio.ac.jp>
To: nate@mt.sri.com
Cc: mobile@freebsd.org, hosokawa@mt.cs.keio.ac.jp
Subject: Re: I want to restructure pccardd....
In-Reply-To: Your message of Tue, 28 Jan 1997 15:06:47 -0700 (MST).
	<199701282206.PAA24236@rocky.mt.sri.com>
From: hosokawa@mt.cs.keio.ac.jp (HOSOKAWA Tatsumi)
X-Mailer: mnews [version 1.19PL2] 1996-01/26(Fri)
Sender: owner-mobile@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In article <199701282206.PAA24236@rocky.mt.sri.com>
nate@mt.sri.com writes:

>> Multifunction card support shouldn't be too hard to add, but this also
>> requires some non-significant kernel modifications.  (Though they aren't
>> too terribly difficult.)

Yes.  Shared IRQ allocation, etc.  It's not terribly difficult, but
it's so difficult that I don't want to go on with current
implementation of pccardd :-).

>> Agreed.  That's why it's not in -current. :) :)

:-).

>> I'd like to see pccardd become *much* simpler.  Basically, the only
>> thing the userland utility should have to do is:
>> 1) Figure out the card <-> kernel driver mapping
>> 2) Read the CIS structures and pass in all relevant information to
>>    the kernel.

Agree.

>> 1) It doesn't know what resources are *really* available.  The kernel
>>    knows (or can be modified) which ports are free, which IRQ's are
>>    unused, etc..  The user-land code does not.

Yes.  I'm planning to implement PC-card utility automatically adds new
pccard.conf entries of unknown cards like PC-card manager of Windows
95 (as an extention of xpccard, or implement new utility).

For example, if you plug unknown PC-card to the machine, and pccardd
has no definition of corresponding pccard.conf entry in the database,
pccardd notices this event, pccardd passes it to user interface client
or record it as syslog.  User interface client prompts user to specify
the corresponding driver from menu system.  If users specify
appropriate driver, user interface utility passes it to pccardd, and
pccardd kicks ther kenel to initialize the driver with specified
driver.  If it succeeds, it will add to /etc/pccard.conf.local.

If I add a feature that user interface utility to prompt user to
e-mail me the new pccard.conf entry, it will make us and you happy :-).

>> 2) You can't boot from a PCCARD disk/FLASH card simply because you have
>>    to be running in multi-user mode before it will be recognized.  By
>>    moving alot of the resource handling in the kernel it would be easier
>>    to have a really simple CIS reader in the kernel for embedded
>>    systems.  (Easier said than done.)

Hmm.  That's true.  I think we also have to add a feature function to
isolate any slot from pccardd's management.

>> 3) It requires too much 'card-specific' information to be
>>    known/understood by the user.
>> 
>> I'd like to see a much simpler syntax, rather than a more complicated
>> syntax used in /etc/pccard.conf.
>> 
>> Ie:
>> card "3Com Corporation" "3C589"
>>      driver 'ep'
>>      insert echo "3Com Etherlink III inserted"
>>      insert /etc/pccard_ether ep0 -link0 link1
>>      remove echo "3Com Etherlink III removed"
>>      remove /sbin/ifconfig ep0 delete

Very good.  I want to remove index specification and IRQ specification.

>> And, the card daemon would pass the 'available' parameters it can use
>> to the kernel, instead of picking one.  The user-land daemon could build
>> up the list of 'usable' configurations and the kernel could choose the
>> one that matched it's list of available resources.

Yes, we have to add an interface to get resource map from userland
daemon.

>> I think this would make things *much* easier to deal with, but would
>> still leave most of the complexity (CIS tuple reading) in user-land.
>> 
>> And, if you had a 'known' CIS tuple the kernel could do a simple
>> recognition on it and boot from it.  (Again, this would be useful to
>> embedded systems who are less concerned about people throwing in funky
>> new PCCARDs).
>> 
>> What do you think?

Flash ATA and HDD PC-card can be handleed by most BIOSses on laptops,
but booting from SCSI PCMCIA or Ethernet PCMCIA is very challenging
work :-).

--
HOSOKAWA, Tatsumi
hosokawa@mt.cs.keio.ac.jp
hosokawa@jp.FreeBSD.org

From owner-freebsd-mobile  Wed Jan 29 00:02:25 1997
Return-Path: <owner-mobile>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id AAA17469
          for mobile-outgoing; Wed, 29 Jan 1997 00:02:25 -0800 (PST)
Received: from lenlen.mt.cs.keio.ac.jp (dhcp2.mt.cs.keio.ac.jp [131.113.32.182])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA17221
          for <mobile@freebsd.org>; Tue, 28 Jan 1997 23:59:03 -0800 (PST)
Received: (from hosokawa@localhost) by lenlen.mt.cs.keio.ac.jp (8.8.4/8.8.2) id QAA03662; Wed, 29 Jan 1997 16:57:59 +0900 (JST)
Date: Wed, 29 Jan 1997 16:57:59 +0900 (JST)
Message-Id: <199701290757.QAA03662@lenlen.mt.cs.keio.ac.jp>
To: mobile@freebsd.org
Cc: hosokawa@mt.cs.keio.ac.jp
Subject: PCMCIA NCR53C500 and Future Domain TMC18C30 drivers.
From: hosokawa@mt.cs.keio.ac.jp (HOSOKAWA Tatsumi)
X-Mailer: mnews [version 1.19PL2] 1996-01/26(Fri)
Sender: owner-mobile@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I'm working on the next release of PAO.  It will be released on today
or tomorrow.  This version have two new drivers.  One is for
NCR/Symbios 53C800 based SCSI cards (ncv) and the other is Future
Domain TMC18C30 based cards (stg).

These are very long-awaited drivers, and we decided to incorporate it
as soon as possible because most SCSI PC-card in market uses one of
these chipsets (except Adaptec and some minor vendors).

These drivers are ported from NetBSD/pc98 (based on NetBSD 1.2) and is
very dirty because these drivers depend on implementation policy of
NetBSD SCSI driver.

I want hackers to clean up these driver into FreeBSD style.  If you
can work on this project, please e-mail me.

According to Ryuji Saeki san's survey, SCSI PC-cards using following
chipsets.  I think most of cards whose 'Driver' is '?', are using
NCR/symbios or Future Domain's chipset.

Vendor                  Model                   Chip                    Driver
------------------------------------------------------------------------------
Adaptec			APA-1460J		aic6360			aic
Alpha Data		AD-PCS2			?			?
Caravelle		PSC-FASC		?			?
Future Domain		SCSI2GO?		TMC18C[35]0		stg
I/O Data		PCSC-98 (mPS-110 OEM)	SYM53C500/406		ncv
I/O Data		PCSC-II (mPS-110 OEM)	SYM53C500/406		ncv
I/O Data		PCSC-V			SYM53C500/406?		ncv?
IBM			SCSI PCMCIA Card	TMC18C[35]0		stg
ICM			PSC-2401-X		TMC18C[35]0		stg
KME			CD WORKMAN?		SYM53C500/406		ncv
Logitec			LPM-SCSI		SYM53C500/406		ncv
MACNICA			mPS-100 (M-SCSI I)	SYM53C500/406		ncv
MACNICA			mPS-110(LP) (M-SCSI II) SYM53C500/406		ncv
MACNICA			mPS-120 (M-SCSI III)	SYM53C500/406?		ncv?
Media Intelligent	MSC-200H		?			?
Melco			IFC-DC			?			?
Melco			IFC-SC			TMC18C[35]0		stg
Melco			IFC-SC2			SYM53C500/406		ncv
Memolex			PC-1695			FAS408?			?
Midori Elec.		CN-SC43			SYM53C500/406		ncv
NEC			PC-9801N-J03		SYM53C500/406		ncv
NewMedia		BusToaster		aic6360			aic
Panasonic		CF-JSC/01		SYM53C500/406?		ncv?
Panasonic		CF-JSC/02		SYM53C500/406?		ncv?
Panasonic		LK-RJ120ZF/H		SYM53C500/406		ncv
Panasonic Kyushu	?			SYM53C500/406		ncv
Qlogic			Fast! SCSI PCMCIA-10	FAS408			?
RATOC			REX-5535AC/AMC/X/XM	MB89352A		spc
RATOC			REX-5536A/M/H/Z		TMC18C[35]0		stg
RATOC			REX-5572W		SYM53C500/406		ncv
RATOC			REX-9530A/AM		SYM53C500/406		ncv
SONY			PRD-250			aic6360			aic
Toshiba			SCSC200A/B		SYM53C500/406		ncv
Toshiba Info. System	PTJ-SCSI II		TMC18C[35]0?		stg

--
HOSOKAWA, Tatsumi
hosokawa@mt.cs.keio.ac.jp
hosokawa@jp.FreeBSD.org

From owner-freebsd-mobile  Wed Jan 29 04:49:28 1997
Return-Path: <owner-mobile>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id EAA28290
          for mobile-outgoing; Wed, 29 Jan 1997 04:49:28 -0800 (PST)
Received: from tfs.com (tfs.com [140.145.250.1])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id EAA28285
          for <mobile@FreeBSD.org>; Wed, 29 Jan 1997 04:49:26 -0800 (PST)
Received: from schizo.dk.tfs.com by tfs.com (smail3.1.28.1) with SMTP
	id m0vpZRa-0003vzC; Wed, 29 Jan 97 04:48 PST
Received: from critter.dk.tfs.com (critter-home [193.162.32.19]) by schizo.dk.tfs.com (8.8.2/8.7.3) with ESMTP id NAA15603; Wed, 29 Jan 1997 13:48:46 +0100 (MET)
Received: from critter.dk.tfs.com (localhost [127.0.0.1]) by critter.dk.tfs.com (8.8.2/8.8.2) with ESMTP id NAA14720; Wed, 29 Jan 1997 13:50:03 +0100 (MET)
To: hosokawa@mt.cs.keio.ac.jp (HOSOKAWA Tatsumi)
cc: mobile@FreeBSD.org
Subject: Re: I want to restructure pccardd.... 
In-reply-to: Your message of "Wed, 29 Jan 1997 05:20:57 +0900."
             <199701282020.FAA03167@lenlen.mt.cs.keio.ac.jp> 
Date: Wed, 29 Jan 1997 13:50:02 +0100
Message-ID: <14718.854542202@critter.dk.tfs.com>
From: Poul-Henning Kamp <phk@critter.dk.tfs.com>
Sender: owner-mobile@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

In message <199701282020.FAA03167@lenlen.mt.cs.keio.ac.jp>, HOSOKAWA Tatsumi wr
ites:

>I'm planning to rewrite pccardd (and related interface of sys/pccard)
>from scratch because,
>
> [...]
>
>Any comments?

I'm a little bit torn on this one.  On one hand, I hate to have a daemon
like pccard to do what the device-drivers really should be doing, on the
other hand I don't like the idea of adding the necessary code to the 
kernel too much either.

Considering that we will need to have a daemon running anyway, to do 
the necessary userland initializations (ifconfig &c) I pressume we
might as well have it do the CIS parsing and all that jazz...

So based on that I guess the answer is "yes, go for it".

Now, having reached this position let me ask a really nasty question:

Why not make this a tcl application ?  You wouldn't have to write a
parse and all that, and it would be so much more flexible...

--
Poul-Henning Kamp           | phk@FreeBSD.ORG       FreeBSD Core-team.
http://www.freebsd.org/~phk | phk@login.dknet.dk    Private mailbox.
whois: [PHK]                | phk@tfs.com           TRW Financial Systems, Inc.
Power and ignorance is a disgusting cocktail.

From owner-freebsd-mobile  Wed Jan 29 07:35:02 1997
Return-Path: <owner-mobile>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id HAA06044
          for mobile-outgoing; Wed, 29 Jan 1997 07:35:02 -0800 (PST)
Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA06026
          for <mobile@freebsd.org>; Wed, 29 Jan 1997 07:34:58 -0800 (PST)
Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id IAA27310; Wed, 29 Jan 1997 08:34:25 -0700 (MST)
Date: Wed, 29 Jan 1997 08:34:25 -0700 (MST)
Message-Id: <199701291534.IAA27310@rocky.mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
To: hosokawa@mt.cs.keio.ac.jp (HOSOKAWA Tatsumi)
Cc: nate@mt.sri.com, mobile@freebsd.org
Subject: Re: I want to restructure pccardd....
In-Reply-To: <199701290727.QAA03592@lenlen.mt.cs.keio.ac.jp>
References: <199701282206.PAA24236@rocky.mt.sri.com>
	<199701290727.QAA03592@lenlen.mt.cs.keio.ac.jp>
Sender: owner-mobile@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> >> Multifunction card support shouldn't be too hard to add, but this also
> >> requires some non-significant kernel modifications.  (Though they aren't
> >> too terribly difficult.)
> 
> Yes.  Shared IRQ allocation, etc.  It's not terribly difficult, but
> it's so difficult that I don't want to go on with current
> implementation of pccardd :-).

Agreed.  The user-land code is a real mess, but IMHO most of it is not
due to bad design, but due to lots of 'magic' in the CIS tuple code.

> >> 1) It doesn't know what resources are *really* available.  The kernel
> >>    knows (or can be modified) which ports are free, which IRQ's are
> >>    unused, etc..  The user-land code does not.
> 
> Yes.  I'm planning to implement PC-card utility automatically adds new
> pccard.conf entries of unknown cards like PC-card manager of Windows
> 95 (as an extention of xpccard, or implement new utility).
> 
> For example, if you plug unknown PC-card to the machine, and pccardd
> has no definition of corresponding pccard.conf entry in the database,
> pccardd notices this event, pccardd passes it to user interface client
> or record it as syslog.  User interface client prompts user to specify
> the corresponding driver from menu system.  If users specify
> appropriate driver, user interface utility passes it to pccardd, and
> pccardd kicks ther kenel to initialize the driver with specified
> driver.  If it succeeds, it will add to /etc/pccard.conf.local.
> 
> If I add a feature that user interface utility to prompt user to
> e-mail me the new pccard.conf entry, it will make us and you happy :-).

*grin*  This is nice, but it's really not in the scope (yet) of
re-writing pccardd.

> >> 2) You can't boot from a PCCARD disk/FLASH card simply because you have
> >>    to be running in multi-user mode before it will be recognized.  By
> >>    moving alot of the resource handling in the kernel it would be easier
> >>    to have a really simple CIS reader in the kernel for embedded
> >>    systems.  (Easier said than done.)
> 
> Hmm.  That's true.  I think we also have to add a feature function to
> isolate any slot from pccardd's management.

True, I hadn't even thought about that.  If the kernel is handling
things you certainly don't want it changing things out from under the
kernel.

> >> 3) It requires too much 'card-specific' information to be
> >>    known/understood by the user.
> >> 
> >> I'd like to see a much simpler syntax, rather than a more complicated
> >> syntax used in /etc/pccard.conf.
> >> 
> >> Ie:
> >> card "3Com Corporation" "3C589"
> >>      driver 'ep'
> >>      insert echo "3Com Etherlink III inserted"
> >>      insert /etc/pccard_ether ep0 -link0 link1
> >>      remove echo "3Com Etherlink III removed"
> >>      remove /sbin/ifconfig ep0 delete
> 
> Very good.  I want to remove index specification and IRQ specification.

Me too.

> >> And, the card daemon would pass the 'available' parameters it can use
> >> to the kernel, instead of picking one.  The user-land daemon could build
> >> up the list of 'usable' configurations and the kernel could choose the
> >> one that matched it's list of available resources.
> 
> Yes, we have to add an interface to get resource map from userland
> daemon.

Most of this is already there, we just need to extend it.

> >> I think this would make things *much* easier to deal with, but would
> >> still leave most of the complexity (CIS tuple reading) in user-land.
> >> 
> >> And, if you had a 'known' CIS tuple the kernel could do a simple
> >> recognition on it and boot from it.  (Again, this would be useful to
> >> embedded systems who are less concerned about people throwing in funky
> >> new PCCARDs).
> >> 
> >> What do you think?
> 
> Flash ATA and HDD PC-card can be handleed by most BIOSses on laptops,
> but booting from SCSI PCMCIA or Ethernet PCMCIA is very challenging
> work :-).

Very true, but I suspect it can be done.

In any case, I'm not sure this needs a 'new lex/C' syntax for
/etc/pccard.conf, but feel free to convince me otherwise.  It would be
*really* nice if we could write the CIS parser in lex though. :) :)


Nate


From owner-freebsd-mobile  Wed Jan 29 07:44:30 1997
Return-Path: <owner-mobile>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id HAA06442
          for mobile-outgoing; Wed, 29 Jan 1997 07:44:30 -0800 (PST)
Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA06436
          for <mobile@freebsd.org>; Wed, 29 Jan 1997 07:44:27 -0800 (PST)
Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id IAA27398; Wed, 29 Jan 1997 08:44:19 -0700 (MST)
Date: Wed, 29 Jan 1997 08:44:19 -0700 (MST)
Message-Id: <199701291544.IAA27398@rocky.mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
To: hosokawa@mt.cs.keio.ac.jp (HOSOKAWA Tatsumi)
Cc: mobile@freebsd.org
Subject: Re: PCMCIA NCR53C500 and Future Domain TMC18C30 drivers.
In-Reply-To: <199701290757.QAA03662@lenlen.mt.cs.keio.ac.jp>
References: <199701290757.QAA03662@lenlen.mt.cs.keio.ac.jp>
Sender: owner-mobile@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> I'm working on the next release of PAO.  It will be released on today
> or tomorrow.  This version have two new drivers.  One is for
> NCR/Symbios 53C800 based SCSI cards (ncv) and the other is Future
> Domain TMC18C30 based cards (stg).
...

> These drivers are ported from NetBSD/pc98 (based on NetBSD 1.2) and is
> very dirty because these drivers depend on implementation policy of
> NetBSD SCSI driver.

Umm, the original NetBSD 53C800 driver was based on the FreeBSD driver.
Did the 'porter' look at the FreeBSD driver before using the NetBSD
driver?


Nate

From owner-freebsd-mobile  Wed Jan 29 07:45:06 1997
Return-Path: <owner-mobile>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id HAA06493
          for mobile-outgoing; Wed, 29 Jan 1997 07:45:06 -0800 (PST)
Received: from lenlen.mt.cs.keio.ac.jp (lenlen.mt.cs.keio.ac.jp [131.113.32.126])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA06466
          for <mobile@freebsd.org>; Wed, 29 Jan 1997 07:44:55 -0800 (PST)
Received: (from hosokawa@localhost) by lenlen.mt.cs.keio.ac.jp (8.8.4/8.8.2) id AAA04315; Thu, 30 Jan 1997 00:40:47 +0900 (JST)
Date: Thu, 30 Jan 1997 00:40:47 +0900 (JST)
Message-Id: <199701291540.AAA04315@lenlen.mt.cs.keio.ac.jp>
To: mobile@freebsd.org
Cc: hosokawa@mt.cs.keio.ac.jp
Subject: Re: PCMCIA NCR53C500 and Future Domain TMC18C30 drivers.
In-Reply-To: Your message of Wed, 29 Jan 1997 16:57:59 +0900 (JST).
	<199701290757.QAA03662@lenlen.mt.cs.keio.ac.jp>
From: hosokawa@mt.cs.keio.ac.jp (HOSOKAWA Tatsumi)
X-Mailer: mnews [version 1.19PL2] 1996-01/26(Fri)
Sender: owner-mobile@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In article <199701290757.QAA03662@lenlen.mt.cs.keio.ac.jp>
 writes:

>> I'm working on the next release of PAO.  It will be released on today
>> or tomorrow.  This version have two new drivers.  One is for
>> NCR/Symbios 53C800 based SCSI cards (ncv) and the other is Future
>> Domain TMC18C30 based cards (stg).

Done.

ftp://jaz.jp.FreeBSD.org/pub/FreeBSD-jp/PAO/PAO-970129.tar.gz

--
HOSOKAWA, Tatsumi
hosokawa@mt.cs.keio.ac.jp
hosokawa@jp.FreeBSD.org

From owner-freebsd-mobile  Wed Jan 29 08:01:12 1997
Return-Path: <owner-mobile>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id IAA07330
          for mobile-outgoing; Wed, 29 Jan 1997 08:01:12 -0800 (PST)
Received: from frig.mt.cs.keio.ac.jp (frig.mt.cs.keio.ac.jp [131.113.32.7])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id IAA07320
          for <mobile@freebsd.org>; Wed, 29 Jan 1997 08:01:09 -0800 (PST)
Received: (from hosokawa@localhost) by frig.mt.cs.keio.ac.jp (8.6.12+2.4W/3.4Wbeta3) id BAA02459; Thu, 30 Jan 1997 01:00:47 +0900
Date: Thu, 30 Jan 1997 01:00:47 +0900
Message-Id: <199701291600.BAA02459@frig.mt.cs.keio.ac.jp>
To: nate@mt.sri.com
Cc: mobile@freebsd.org, hosokawa@mt.cs.keio.ac.jp
Subject: Re: PCMCIA NCR53C500 and Future Domain TMC18C30 drivers.
In-Reply-To: Your message of Wed, 29 Jan 1997 08:44:19 -0700 (MST).
	<199701291544.IAA27398@rocky.mt.sri.com>
From: hosokawa@mt.cs.keio.ac.jp (HOSOKAWA Tatsumi)
X-Mailer: mnews [version 1.18PL3] 1994-08/01(Mon)
Sender: owner-mobile@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In article <199701291544.IAA27398@rocky.mt.sri.com>
nate@mt.sri.com writes:

>> Umm, the original NetBSD 53C800 driver was based on the FreeBSD driver.
>> Did the 'porter' look at the FreeBSD driver before using the NetBSD
>> driver?

FreeBSD has NCR 5380 and 53c400 driver, but I can't find 53c800
driver.  I don't know whether 5380 is compatible with 53c800.  If 5380
is compatible with 53c800, we'll modify nca driver instead.

I can't find any nca-compatible code in ncv driver.

And NetBSD/pc98 is based on NetBSD 1.2, but it's not NetBSD 1.2.

hosokawa

From owner-freebsd-mobile  Wed Jan 29 08:49:40 1997
Return-Path: <owner-mobile>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id IAA09239
          for mobile-outgoing; Wed, 29 Jan 1997 08:49:40 -0800 (PST)
Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA09231
          for <mobile@freebsd.org>; Wed, 29 Jan 1997 08:49:36 -0800 (PST)
Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id JAA27570; Wed, 29 Jan 1997 09:49:27 -0700 (MST)
Date: Wed, 29 Jan 1997 09:49:27 -0700 (MST)
Message-Id: <199701291649.JAA27570@rocky.mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
To: hosokawa@mt.cs.keio.ac.jp (HOSOKAWA Tatsumi)
Cc: nate@mt.sri.com, mobile@freebsd.org
Subject: Re: PCMCIA NCR53C500 and Future Domain TMC18C30 drivers.
In-Reply-To: <199701291600.BAA02459@frig.mt.cs.keio.ac.jp>
References: <199701291544.IAA27398@rocky.mt.sri.com>
	<199701291600.BAA02459@frig.mt.cs.keio.ac.jp>
Sender: owner-mobile@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> >> Umm, the original NetBSD 53C800 driver was based on the FreeBSD driver.
> >> Did the 'porter' look at the FreeBSD driver before using the NetBSD
> >> driver?
> 
> FreeBSD has NCR 5380 and 53c400 driver, but I can't find 53c800
> driver.  I don't know whether 5380 is compatible with 53c800.  If 5380
> is compatible with 53c800, we'll modify nca driver instead.

It looks like I was confused.  I remember Steven Esser adding code for
alot of new boards, but it appears that they are all 53c810 or better.

Sorry!


Nate

From owner-freebsd-mobile  Wed Jan 29 16:06:31 1997
Return-Path: <owner-mobile>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id QAA01479
          for mobile-outgoing; Wed, 29 Jan 1997 16:06:31 -0800 (PST)
Received: from magigimmix.xs4all.nl (magigimmix.xs4all.nl [194.109.6.25])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA01458
          for <freebsd-mobile@freebsd.org>; Wed, 29 Jan 1997 16:06:24 -0800 (PST)
Received: from asterix.xs4all.nl (asterix.xs4all.nl [194.109.6.11]) by magigimmix.xs4all.nl (8.7.6/XS4ALL) with ESMTP id BAA19072 for <freebsd-mobile@freebsd.org>; Thu, 30 Jan 1997 01:06:22 +0100 (MET)
Received: from plm.xs4all.nl (uucp@localhost) by asterix.xs4all.nl (8.7.5/8.7.2) with UUCP id AAA01859 for freebsd-mobile@freebsd.org; Thu, 30 Jan 1997 00:51:47 +0100 (MET)
Received: (from plm@localhost) by plm.xs4all.nl (8.8.4/8.7.3) id XAA00669; Wed, 29 Jan 1997 23:22:42 +0100 (MET)
To: freebsd-mobile@freebsd.org
Subject: Megahertz BNC/UTP problem
From: Peter Mutsaers <plm@xs4all.nl>
Date: 29 Jan 1997 23:22:41 +0100
Message-ID: <87g1zkf7f2.fsf@localhost.xs4all.nl>
Lines: 20
X-Mailer: Gnus v5.2.39/Emacs 19.34
Sender: owner-mobile@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I have a Megahertz PCMCIA ethernet card with a BNC and UTP
connection. Under FreeBSD (latest PAO) it doesn't work.

The card is recognized. When I send data I see the led blink, and when
data arrives I see it blink too.

But the data which is supposed to be sent, never really arrives on the
ethernet (it is not seen by my other computer).

Is this a known problem? Is it possible that it tries to send on UTP?
I have only BNC connected.

Under Win95 I have to choose manually whether to use BNC or UTP. Can I
or must I do that with FreeBSD/PAO?

Thanks,

-- 
Peter Mutsaers  |  Abcoude (Utrecht), |  Trust is a good quality
plm@xs4all.nl   |  the Netherlands    |  for other people to have

From owner-freebsd-mobile  Thu Jan 30 10:05:26 1997
Return-Path: <owner-mobile>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id KAA22609
          for mobile-outgoing; Thu, 30 Jan 1997 10:05:26 -0800 (PST)
Received: from cs.pdx.edu (root@cs.pdx.edu [204.203.64.22])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA22602
          for <freebsd-mobile@freebsd.org>; Thu, 30 Jan 1997 10:05:22 -0800 (PST)
Received: from sirius.cs.pdx.edu (root@sirius.cs.pdx.edu [204.203.64.13])
	by cs.pdx.edu (8.8.5/8.8.5) with ESMTP id KAA05508
	for <freebsd-mobile@freebsd.org>; Thu, 30 Jan 1997 10:05:19 -0800 (PST)
Received: from localhost (jrb@localhost [127.0.0.1])
	by sirius.cs.pdx.edu (8.8.5/8.8.5) with ESMTP id KAA01615
	for <freebsd-mobile@freebsd.org>; Thu, 30 Jan 1997 10:05:18 -0800 (PST)
Message-Id: <199701301805.KAA01615@sirius.cs.pdx.edu>
To: freebsd-mobile@freebsd.org
Subject: Mike Smith beta port of 2.2 ISA wavelan driver
Date: Thu, 30 Jan 1997 10:05:17 -0800
From: Jim Binkley <jrb@cs.pdx.edu>
Sender: owner-mobile@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


Michael Smith has made a beta port of "our" * 
PSU ISA Wavelan driver from my 2.1.0 version to 2.2.  I made a
local copy of it, which you can grab at:
	ftp://zymurgy.cs.pdx.edu/pub/mobility/wl970131.tar.gz

* (in a very loose sense, the code is a lot like the hw 
in terms of owners (NCR/ATT/LUCENT) so far; i.e.,
many folks have hacked on it over time (Klemets/RTM jr./jrb/msmith)).

				Jim Binkley
				jrb@cs.pdx.edu
				Portland State University/CS dept.

From owner-freebsd-mobile  Thu Jan 30 17:51:33 1997
Return-Path: <owner-mobile>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id RAA20721
          for mobile-outgoing; Thu, 30 Jan 1997 17:51:33 -0800 (PST)
Received: from frig.mt.cs.keio.ac.jp (frig.mt.cs.keio.ac.jp [131.113.32.7])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id RAA20712
          for <mobile@freebsd.org>; Thu, 30 Jan 1997 17:51:18 -0800 (PST)
Received: (from hosokawa@localhost) by frig.mt.cs.keio.ac.jp (8.6.12+2.4W/3.4Wbeta3) id KAA18476; Fri, 31 Jan 1997 10:50:25 +0900
Date: Fri, 31 Jan 1997 10:50:25 +0900
Message-Id: <199701310150.KAA18476@frig.mt.cs.keio.ac.jp>
To: hosokawa@mt.cs.keio.ac.jp
Cc: mobile@freebsd.org, hosokawa@mt.cs.keio.ac.jp,
        honda@Kururu.math.hokudai.ac.jp
Subject: Re: PCMCIA NCR53C500 and Future Domain TMC18C30 drivers.
In-Reply-To: Your message of Wed, 29 Jan 1997 16:57:59 +0900 (JST).
	<199701290757.QAA03662@lenlen.mt.cs.keio.ac.jp>
From: hosokawa@mt.cs.keio.ac.jp (HOSOKAWA Tatsumi)
X-Mailer: mnews [version 1.18PL3] 1994-08/01(Mon)
Sender: owner-mobile@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I must apologize to the original author about following message on
this list.

In article <199701290757.QAA03662@lenlen.mt.cs.keio.ac.jp>
hosokawa@mt.cs.keio.ac.jp writes:

>> These drivers are ported from NetBSD/pc98 (based on NetBSD 1.2) and is
>> very dirty because these drivers depend on implementation policy of
   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> NetBSD SCSI driver.

I didn't intended to abuse upon the author of original drivers.  I
only meant that current porting status is very dirty.  I think that
original driver is very beautiful code, but we couldn't incorporate it
smoothly into FreeBSD source tree because the implementation policy
between SCSI driver of FreeBSD and it of NetBSD is very different.

I'm very sorry.

--
	HOSOKAWA, Tatsumi              E-mail: hosokawa@mt.cs.keio.ac.jp
	  WWW homepage: http://www.mt.cs.keio.ac.jp/person/hosokawa.html
	Department of Computer Science, Keio University, Yokohama, Japan

From owner-freebsd-mobile  Fri Jan 31 06:57:00 1997
Return-Path: <owner-mobile>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id GAA25807
          for mobile-outgoing; Fri, 31 Jan 1997 06:57:00 -0800 (PST)
Received: from hcshh.hcs.de (hcshh.hcs.de [194.49.17.1])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id GAA25801
          for <mobile@freebsd.org>; Fri, 31 Jan 1997 06:56:56 -0800 (PST)
Received: from hcswork.hcs.de by hcshh.hcs.de with smtp
	(Smail3.1.28.1 #9) id m0vqKOF-000TOsC; Fri, 31 Jan 97 15:56 MET
Received: by hcswork.hcs.de (Smail3.1.29.0 #12)
	id m0vqKO9-0000ayC; Fri, 31 Jan 97 15:56 MET
Message-Id: <m0vqKO9-0000ayC@hcswork.hcs.de>
From: hm@hcs.de (Hellmuth Michaelis)
Subject: 2.1.6.1 + PAO: occasional panic at boot
To: mobile@freebsd.org
Date: Fri, 31 Jan 1997 15:56:24 +0100 (MET)
Reply-To: hm@hcs.de
Organization: HCS Hanseatischer Computerservice GmbH
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-mobile@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Hi,

i've just installed 2.1.6.1 and the PAO package from the PAO www site for 
2.1.5 - and i'm very pleased!

The only problem i'm experiencing so far is that i get panics from time
to time at boot time, after the message for the apm0 driver: "cannot mount
root". Then i get into ddb and when pressing a key i get the message
"Card 0 inserted" (there is an 3com 3c589c in slot 0 using the ep driver).

The machine is a digital Hinote 433, 12Mb Ram, 512Mb disk (Toshiba MK1924FCV).

Is this a known problem ?

hellmuth
-- 
Hellmuth Michaelis    HCS Hanseatischer Computerservice GmbH    Hamburg, Europe
    In their infinite wisdom, the folks at HP have decided that mere mortals
    such as you and I don't need to know what the kernel's proc structure looks
    like. (William LeFebvre, top 3.4 README, HP-UX 10.10)

From owner-freebsd-mobile  Fri Jan 31 07:43:43 1997
Return-Path: <owner-mobile>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id HAA27702
          for mobile-outgoing; Fri, 31 Jan 1997 07:43:43 -0800 (PST)
Received: from hcshh.hcs.de (hcshh.hcs.de [194.49.17.1])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id HAA27695
          for <mobile@freebsd.org>; Fri, 31 Jan 1997 07:43:35 -0800 (PST)
Received: from hcswork.hcs.de by hcshh.hcs.de with smtp
	(Smail3.1.28.1 #9) id m0vqL7U-000TOuC; Fri, 31 Jan 97 16:43 MET
Received: by hcswork.hcs.de (Smail3.1.29.0 #12)
	id m0vqL7O-0000ayC; Fri, 31 Jan 97 16:43 MET
Message-Id: <m0vqL7O-0000ayC@hcswork.hcs.de>
From: hm@hcs.de (Hellmuth Michaelis)
Subject: setnetparms - setup network environment at boot time
To: mobile@freebsd.org
Date: Fri, 31 Jan 1997 16:43:09 +0100 (MET)
Reply-To: hm@hcs.de
Organization: HCS Hanseatischer Computerservice GmbH
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-mobile@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Hi,

i have just uploaded a small utility package to ftp.freebsd.org into
FreeBSD/incoming with filename setnetparms.tar.gz which i think is very
useful in FreeBSD based laptop environments.

It lets you specify i.e. the IP address, subnetmask, hostname and other
parameter at boot time in a menu based utility which is configurable by
very(!) simple text files.

I'm using it for quite some time now on my laptop to simply plug into
the networks of customers which don't even know what bootp or DHCP is.

It lacks any form of error detection or recovery, it has no manual pages
and if i would see this code for the first time i would say that its a hack.

Constructive feedback welcome!

Have fun,
hellmuth
-- 
Hellmuth Michaelis    HCS Hanseatischer Computerservice GmbH    Hamburg, Europe
    In their infinite wisdom, the folks at HP have decided that mere mortals
    such as you and I don't need to know what the kernel's proc structure looks
    like. (William LeFebvre, top 3.4 README, HP-UX 10.10)

From owner-freebsd-mobile  Fri Jan 31 08:41:58 1997
Return-Path: <owner-mobile>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id IAA29927
          for mobile-outgoing; Fri, 31 Jan 1997 08:41:58 -0800 (PST)
Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA29922
          for <mobile@freebsd.org>; Fri, 31 Jan 1997 08:41:54 -0800 (PST)
Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id JAA09683; Fri, 31 Jan 1997 09:41:43 -0700 (MST)
Date: Fri, 31 Jan 1997 09:41:43 -0700 (MST)
Message-Id: <199701311641.JAA09683@rocky.mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
To: hm@hcs.de
Cc: mobile@freebsd.org
Subject: Re: 2.1.6.1 + PAO: occasional panic at boot
In-Reply-To: <m0vqKO9-0000ayC@hcswork.hcs.de>
References: <m0vqKO9-0000ayC@hcswork.hcs.de>
Sender: owner-mobile@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> i've just installed 2.1.6.1 and the PAO package from the PAO www site for 
> 2.1.5 - and i'm very pleased!
> 
> The only problem i'm experiencing so far is that i get panics from time
> to time at boot time, after the message for the apm0 driver: "cannot mount
> root". Then i get into ddb and when pressing a key i get the message
> "Card 0 inserted" (there is an 3com 3c589c in slot 0 using the ep driver).

Weird.  But, the apm0 driver doesn't print that out, but the kernel
itself does.  Can you do a backtrace to see whose calling panic()?

> The machine is a digital Hinote 433, 12Mb Ram, 512Mb disk (Toshiba
> MK1924FCV).

How old is the BIOS on this thing?


Nate

From owner-freebsd-mobile  Fri Jan 31 09:46:29 1997
Return-Path: <owner-mobile>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id JAA03275
          for mobile-outgoing; Fri, 31 Jan 1997 09:46:29 -0800 (PST)
Received: from mail11.digital.com (mail11.digital.com [192.208.46.10])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA03269
          for <mobile@freebsd.org>; Fri, 31 Jan 1997 09:46:21 -0800 (PST)
Received: from muggsy.lkg.dec.com by mail11.digital.com (8.7.5/UNX 1.5/1.0/WV)
	id MAA31127; Fri, 31 Jan 1997 12:30:14 -0500 (EST)
Received:  from whydos.lkg.dec.com by muggsy.lkg.dec.com (5.65/DEC-Ultrix/4.3) with SMTP
	id AA20174; Fri, 31 Jan 1997 12:30:11 -0500
Received: from localhost.lkg.dec.com (localhost.lkg.dec.com [127.0.0.1]) by whydos.lkg.dec.com (8.6.12/8.6.12) with SMTP id NAA18577; Fri, 31 Jan 1997 13:38:43 GMT
Message-Id: <199701311338.NAA18577@whydos.lkg.dec.com>
X-Authentication-Warning: whydos.lkg.dec.com: Host localhost.lkg.dec.com didn't use HELO protocol
X-Mailer: exmh version 1.6.5 12/11/95
To: Nate Williams <nate@mt.sri.com>
Cc: hm@hcs.de, mobile@freebsd.org
Subject: Re: 2.1.6.1 + PAO: occasional panic at boot 
In-Reply-To: Your message of "Fri, 31 Jan 1997 09:41:43 MST."
             <199701311641.JAA09683@rocky.mt.sri.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 31 Jan 1997 13:38:38 +0000
From: Matt Thomas <matt@lkg.dec.com>
Sender: owner-mobile@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


> > The machine is a digital Hinote 433, 12Mb Ram, 512Mb disk (Toshiba
> > MK1924FCV).
> 
> How old is the BIOS on this thing?

If it isn't at 1.42, upgrade!  This is (new! as of 1/27/97) BIOS:

http://www.pc.digital.com/~ftp/mobile/hinote/hinote/BGP7142A.EXE

(You'll to run this under DOS/Windows to make a diskette.)

-- 
Matt Thomas               Internet:   matt@3am-software.com
3am Software Foundry      WWW URL:    http://www.3am-software.com/bio/matt.html
Westford, MA              Disclaimer: I disavow all knowledge of this message



From owner-freebsd-mobile  Fri Jan 31 12:12:22 1997
Return-Path: <owner-mobile>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id MAA09779
          for mobile-outgoing; Fri, 31 Jan 1997 12:12:22 -0800 (PST)
Received: from hcshh.hcs.de (hcshh.hcs.de [194.49.17.1])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id MAA09771
          for <mobile@freebsd.org>; Fri, 31 Jan 1997 12:12:14 -0800 (PST)
Received: from hcswork.hcs.de by hcshh.hcs.de with smtp
	(Smail3.1.28.1 #9) id m0vqPJY-000TX2C; Fri, 31 Jan 97 21:12 MET
Received: by hcswork.hcs.de (Smail3.1.29.0 #12)
	id m0vqPJS-0000ayC; Fri, 31 Jan 97 21:11 MET
Message-Id: <m0vqPJS-0000ayC@hcswork.hcs.de>
From: hm@hcs.de (Hellmuth Michaelis)
Subject: Re: 2.1.6.1 + PAO: occasional panic at boot
To: nate@mt.sri.com (Nate Williams)
Date: Fri, 31 Jan 1997 21:11:53 +0100 (MET)
Cc: hm@hcs.de, mobile@freebsd.org
In-Reply-To: <199701311641.JAA09683@rocky.mt.sri.com> from "Nate Williams" at Jan 31, 97 09:41:43 am
Reply-To: hm@hcs.de
Organization: HCS Hanseatischer Computerservice GmbH
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-mobile@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>From the keyboard of Nate Williams:

> Weird.  But, the apm0 driver doesn't print that out, but the kernel
> itself does.  Can you do a backtrace to see whose calling panic()?

Will do that.

> > The machine is a digital Hinote 433, 12Mb Ram, 512Mb disk (Toshiba
> > MK1924FCV).
> 
> How old is the BIOS on this thing?

1.42. But it also did it with 1.41.

Everything else functions just fine. Suspend/resume works. Removal and
plug-in of the 3c589 just works. The ep driver just works. Good work !!

hellmuth
-- 
Hellmuth Michaelis    HCS Hanseatischer Computerservice GmbH    Hamburg, Europe
    In their infinite wisdom, the folks at HP have decided that mere mortals
    such as you and I don't need to know what the kernel's proc structure looks
    like. (William LeFebvre, top 3.4 README, HP-UX 10.10)

From owner-freebsd-mobile  Fri Jan 31 19:20:12 1997
Return-Path: <owner-mobile>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id TAA01201
          for mobile-outgoing; Fri, 31 Jan 1997 19:20:12 -0800 (PST)
Received: from 3rivers3.3rivers.net (3rivers3.3rivers.net [208.136.177.20])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA01194
          for <freebsd-mobile@freebsd.org>; Fri, 31 Jan 1997 19:20:05 -0800 (PST)
Received: (from ron@localhost) by 3rivers3.3rivers.net (8.8.4/8.6.12) id UAA01631; Fri, 31 Jan 1997 20:19:57 -0700 (MST)
Message-ID: <Mutt.19970131201925.ron@3rivers3.3rivers.net>
Date: Fri, 31 Jan 1997 20:19:25 -0700
From: ron@3rivers.net (Ron Warnick)
To: freebsd-mobile@freebsd.org
Subject: ps/2 (?) mouse on compaq laptop
X-Mailer: Mutt 0.51
Mime-Version: 1.0
Sender: owner-mobile@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I just got X11R6 running at 800x600 on my 4120 compaq armada, with
2.2-BETA, by copying over a previous version XF86_SVGA, and 
kludging the device section. However, I haven't yet succeeded in
getting the touchpad mouse to be recognized. I compiled psm0 in
the kernel, but it is not found on boot. Any suggestions???

Ron

@}-->-->-------

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Ron Warnick	ron@3rivers.net	   406.264.5549, Fax 406.264.5721
System Administration  Solaris, SunOs, Aix, Linux, FreeBSD, Plan9

From owner-freebsd-mobile  Sat Feb  1 07:21:48 1997
Return-Path: <owner-mobile>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id HAA26356
          for mobile-outgoing; Sat, 1 Feb 1997 07:21:48 -0800 (PST)
Received: from magigimmix.xs4all.nl (magigimmix.xs4all.nl [194.109.6.25])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA26350
          for <freebsd-mobile@freebsd.org>; Sat, 1 Feb 1997 07:21:45 -0800 (PST)
Received: from asterix.xs4all.nl (asterix.xs4all.nl [194.109.6.11]) by magigimmix.xs4all.nl (8.7.6/XS4ALL) with ESMTP id QAA16425 for <freebsd-mobile@freebsd.org>; Sat, 1 Feb 1997 16:21:32 +0100 (MET)
Received: from plm.xs4all.nl (uucp@localhost) by asterix.xs4all.nl (8.7.5/8.7.2) with UUCP id QAA01961 for freebsd-mobile@freebsd.org; Sat, 1 Feb 1997 16:15:33 +0100 (MET)
Received: (from plm@localhost) by plm.xs4all.nl (8.8.4/8.7.3) id QAA01627; Sat, 1 Feb 1997 16:14:36 +0100 (MET)
To: freebsd-mobile@freebsd.org
Subject: 3c589 (zp driver) doesn't turn on card (?)
From: Peter Mutsaers <plm@xs4all.nl>
Date: 01 Feb 1997 16:14:35 +0100
Message-ID: <87ybd8blt0.fsf@localhost.xs4all.nl>
Lines: 19
X-Mailer: Gnus v5.2.39/Emacs 19.34
Sender: owner-mobile@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Hello,

I use the zp driver in 2.2 or 3.0-current for my 3c589c card. The card
however is only detected if I run Win95 first.

If win95 runs, the led will turn green (looks like the card is turned
on somehow). When I reboot to FreeBSD, zp0 is detected and works find.

If I halt the system and boot FreeBSD right away however, the led
doesn't turn green. zp driver will tell me that the slot is not empty,
but it doesn't detect the card.

Does anyone have an explanation for this behaviour, and maybe even a
solution?


-- 
Peter Mutsaers  |  Abcoude (Utrecht), |  Trust is a good quality
plm@xs4all.nl   |  the Netherlands    |  for other people to have

From owner-freebsd-mobile  Sat Feb  1 09:25:28 1997
Return-Path: <owner-mobile>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id JAA00793
          for mobile-outgoing; Sat, 1 Feb 1997 09:25:28 -0800 (PST)
Received: from jli.com (jli.com [199.2.111.1])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id JAA00788
          for <freebsd-mobile@FreeBSD.ORG>; Sat, 1 Feb 1997 09:25:23 -0800 (PST)
Received: from cumulus by jli.com with uucp
	(Smail3.1.29.1 #3) id m0vqjAZ-0002TWC; Sat, 1 Feb 97 09:24 PST
Message-Id: <m0vqjAu-00004qC@cloud.rain.com>
To: ron@3rivers.net (Ron Warnick)
cc: freebsd-mobile@FreeBSD.ORG
Subject: Re: ps/2 (?) mouse on compaq laptop 
References: <Mutt.19970131201925.ron@3rivers3.3rivers.net> 
In-reply-to: Your message of Fri, 31 Jan 1997 20:19:25 MST.
             <Mutt.19970131201925.ron@3rivers3.3rivers.net> 
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----- =_aaaaaaaaaa0"
Content-ID: <6429.854817863.0@cloud.rain.com>
Date: Sat, 01 Feb 1997 09:24:24 -0800
From: Bill Trost <trost@cloud.rain.com>
Sender: owner-mobile@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

------- =_aaaaaaaaaa0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <6429.854817863.1@cloud.rain.com>

Ron Warnick writes:
    I just got X11R6 running at 800x600 on my 4120 compaq armada, with
    2.2-BETA, by copying over a previous version XF86_SVGA, and kludging the
    device section. However, I haven't yet succeeded in getting the touchpad
    mouse to be recognized.

You might find the attached email useful -- at least it's a place to start.  I
tried to send email the adddress listed in the first message, but no luck.

Incidentally, have you used any PCMCIA devices yet?  I'm very seriously
considering buying a 4120 or better, and would like to make sure it can handle
*those* devices correctly before I do so.

------- =_aaaaaaaaaa0
Content-Type: multipart/digest; boundary="----- =_aaaaaaaaaa1"
Content-ID: <6429.854817863.2@cloud.rain.com>


------- =_aaaaaaaaaa1

Return-Path: trost@cloud.rain.com
Return-Path: <trost@cloud.rain.com>
Received: for <trost> from grey.cloud.rain.com by cloud.rain.com with smtp
	(Smail3.1.29.1 #2) id m0vRVrn-00006uC; Sat, 23 Nov 96 20:08 WET
Sender: trost
Message-ID: <3297CA3A.41C67EA6@cloud.rain.com>
Date: Sat, 23 Nov 1996 20:08:26 -0800
From: Bill Trost <trost@cloud.rain.com>
X-Mailer: Mozilla 2.01 (X11; I; FreeBSD 2.1.0-RELEASE i386)
MIME-Version: 1.0
To: trost
Subject: Linux on the Compaq Armada 4120
X-URL: http://www.aplac.hut.fi/staff/sakari/armada.html
Content-Type: multipart/mixed; boundary="------------446B9B3D2781E494167EB0E7"

This is a multi-part message in MIME format.

--------------446B9B3D2781E494167EB0E7
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

http://www.aplac.hut.fi/staff/sakari/armada.html

--------------446B9B3D2781E494167EB0E7
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; filename="armada.html"

<BASE HREF="http://www.aplac.hut.fi/staff/sakari/armada.html">

<html>  
<head> <title> Linux on the Compaq Armada 4120</title> </head>
<body>

<center>
<img src="armada.gif">
</center>


<center> 
<a name="Linux"></a><h1>Linux on the Compaq Armada 4120</h1> 
</center>

<hr>
<hr>


<h3> Introduction </h3>

Our laboratory recently bought a Compaq Armada 4120 notebook computer.
This page describes the installation of Linux on it.  I only pay attention
to the particular difficulties encountered  -  look
elsewhere for a complete description of Linux installation. 
<p>

What proved extremely helpful was Chris Burghart's 
 <a href="http://www.atd.ucar.edu/homes/burghart/SENS810.html">
Linux on the Samsung SENS 810</a> (it seems the Armada is a rather
close copy of the Samsung machine.) Chris Burghart includes many
other tips you might be interested in; I haven't copied all of them
here.
Many thanks to others with similar pages on the <a
href="http://www.cs.utexas.edu/users/kharker/linux-laptop/">
 Linux Laptop Homepage</a>.

<p>
<hr>

<h3> Keeping Windows 95 </h3>

The Armada comes with Windows 95 pre-installed on a single partition
that spans almost the whole hard disk, i.e., there is no free
partition to set up Linux on. That is not a problem if you
do not plan to keep Windows 95 available, in which case you
just use the partition for Linux.
<p>

On the other hand, if you do want to keep Windows 95 available,
then note that Compaq does not supply a Windows 95 CD-ROM 
with the computer, which means that if you want to back-up
the Windows 95 installation, you need 31 (thirty-one) diskettes
and... a lot of patience. (I did this, just for safety's sake,
but it was not fun.)
<p>

Next, you could, conceivably, re-partition and re-format the
Windows 95 partition. However, as a less brutal alternative,  
you can split the existing Windows 95 partition with Arno
Schaefer's non-destructive partition splitting program
<a href="http://www.student.informatik.th-darmstadt.de/~schaefer/fips.html">
FIPS</a>. It runs under DOS and is simple to use, so I did, ending
up with two partitions of about 500MB each. (Compaq has put a third
partition of some 4MB at the start of the disk - it seems to contain
various Compaq setup files, so I did not touch it.)
</ul>

<hr>

<h3> Installing Linux </h3>

I installed Slackware 3.0, starting with the <tt>idenet</tt> boot
disk. If you get the CD-ROM expansion unit, you can install the rest
from a CD-ROM. Of course, the kernel should have IDE/ATAPI
CD-ROM support enabled. In our case, the drive showed up as <tt>/dev/hdb</tt>. 
<p>

<h4> XFree86 </h4>

I installed the SVGA X server (XF86_SVGA). The VGA16 server works, too,
but there's not much point in using it.
<p>

The Armada 4120 has a Cirrus Logic CL-GD7548 graphics chip.  While
this chip is listed among those supported by the SVGA server
(current version 3.2), the support appears broken. However,
the chip can be treated as a CL-GD5428, which <i>is</i> supported by the
server.  Here is a copy of our current 
<a href="XF86Config"><tt>XF86Config</tt></a>
file (from <tt>/etc/XF86Config</tt>); note that it is set up to
support our Finnish keyboard.
<p>

I have noticed the same occasional 16x1 horizontal glitches
as Chris Burghart.  As he says, <tt>xrefresh</tt> fixes the
problem. Another problem is that the <tt>variable</tt> font that
I'm fond of shows up disproportionately large. Perhaps a
new version from XFree86 will solve these problems.
<p>

The mouse is overly sensitive. However, it is so under Windows 95, too,
so this is not XFree86's fault.

<h4> Sound </h4> 
Chris Burghart's sound configuration works fine:
<ul>
  <li> SoundBlaster
  <li> address base: 0x220
  <li> IRQ: 10
  <li> first (8-bit) DMA slot: 1
  <li> second (16-bit) DMA slot: 7
  <li> DSP buffer size: 16 Kbytes
</ul>

Some programs, notably RealAudio, will open both the audio in (microphone)
and the audio out (loudspeaker) channels. The speaker output will then feed
back through the mic, and the Armada starts emitting a terrible whine.
Get the <a href="ftp://ftp.funet.fi/pub/Linux/util/sound/snd-kit/snd-util-3.5.tar.gz">
SoundKit</a> package; it includes a mixer utility that can mute the microphone:
<p>
<tt>armada:~>mixer mic 0</tt>

<h4> PCMCIA Card Services </h4>

The Armada has the typical PCMCIA slot for two type II cards or
one type III one. The first Ethernet card we put in - a D-Link DE-850T -
wouldn't work; indeed, it wouldn't work under Window 95, either
(well, it's not supposed to, as documented in the README file
on D-Link's driver diskette.) It would appear that only D-Link's DE-850
<i>combo</i> card works, the one with both 10Base2 and 10baseT.
In any case, we swapped it for a 3Com 589CS - another combo card - and
that card works just fine.
<p>

The card services are built as modules; get the 
<a href="ftp://ftp.funet.fi/pub/mirrors/sunsite.unc.edu/pub/Linux/kernel/pcmcia/pcmcia-cs-2.8.23.tar.gz">
PCMCIA card services</a> package.
Once again, Chris Burghart's set-up (<a href="http://www.atd.ucar.edu/homes/burghart/config.opts">
config.opts</a>) did not need changing.
<p>

<h4>Advanced Power Management</h4>
With APM enabled in the kernel (in our case, 2.0.24), things seem
generally to work as they are supposed to. Even hibernation (the contents
of the RAM are written to disk, then restored) works. However, there
are problems that manifest themselves with the keyboard - when resuming
after suspension,
the Armada comes up seemingly not accepting any keyboard
input at all. A trick we've found is to change to another virtual terminal,
then come back to the first one.
<p>
The PCMCIA devices - in our case, the Ethernet card - do not seem
much bothered by suspension (this is contrary to Chris Burghart's
experiences with the Samsung). That is, inside of an X11 session with
Netscape running, you can hit the suspend button and go away for a while,
then come back, hit the suspend button again, and have your network
connection still up and running.

<h4>IrDA</h4>

The IrDA port's use under Linux is currently a mystery. It appears
to need some sort of enabling, that is, it is not automatically
active. Some other laptops apparently have a choice in the BIOS
setup for this; unfortunately, I haven't found anything concerning
the IrDA port in the Compaq diagnostics, say.

<hr>

<h3> Other References </h3>

<li> <a href="http://www.caldera.com/LDP/">The Linux Documentation Project</a>
<li><a href="http://www.cs.utexas.edu/users/kharker/linux-laptop/">
    The Linux Laptop Home Page</a>
<li><a href="http://www.XFree86.org/">XFree86</a>
<li><a href="http://hyper.stanford.edu/~dhinds/pcmcia/pcmcia.html">
    Linux PCMCIA Information</a>
<li><a href="http://www.xnet.com/~blatura/linapps.shtml">Linux Applications
    and Utilities</a>

<p>
<hr>
<hr>

<address><a href="mailto:sakari@aplac.hut.fi">
Sakari Aaltonen &lt;sakari@aplac.hut.fi&gt;
</a></address>

<!-- hhmts start -->
Last modified: Nov 20 1996
<!-- hhmts end -->

</body>
</html>

--------------446B9B3D2781E494167EB0E7--


------- =_aaaaaaaaaa1

Return-Path: trost@cloud.rain.com
Return-Path: <trost@cloud.rain.com>
Received: for <trost> from grey.cloud.rain.com by cloud.rain.com with smtp
	(Smail3.1.29.1 #2) id m0vRVsk-00006uC; Sat, 23 Nov 96 20:09 WET
Sender: trost
Message-ID: <3297CA75.794BDF32@cloud.rain.com>
Date: Sat, 23 Nov 1996 20:09:25 -0800
From: Bill Trost <trost@cloud.rain.com>
X-Mailer: Mozilla 2.01 (X11; I; FreeBSD 2.1.0-RELEASE i386)
MIME-Version: 1.0
To: trost
Subject: XF86Config for Armada (sort of)
X-URL: http://www.aplac.hut.fi/staff/sakari/XF86Config
Content-Type: multipart/mixed; boundary="------------1CFBAE3959E2B60015FB7483"

This is a multi-part message in MIME format.

--------------1CFBAE3959E2B60015FB7483
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

http://www.aplac.hut.fi/staff/sakari/XF86Config

--------------1CFBAE3959E2B60015FB7483
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; filename="XF86Config"

#
# XF86Config file for the Samsung SENS 810
#

Section "Files"
  RgbPath  "/usr/X11R6/lib/X11/rgb"
  FontPath "/usr/X11R6/lib/X11/fonts/misc/"
  FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
  FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
  FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
  FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"
EndSection

Section "ServerFlags"
EndSection

Section "Keyboard"
    Protocol	"Standard"
    XkbRules	"xfree86"
    XkbModel	"pc102"
    XkbLayout	"fi"
    AutoRepeat	500 5
EndSection

Section "Pointer"
    Protocol    "PS/2"
    Device      "/dev/psaux"
    Emulate3Buttons
EndSection



Section "Monitor"
  Identifier    "Samsung Sens810 LCD"
  VendorName    "Samsung"
  ModelName     "Sens810"
  Bandwidth 100.0
  HorizSync 31-69
  VertRefresh 55-120
  Modeline "800x600"  50  800  800  808 808 600 600 608 608
EndSection



Section "Device"
    Identifier  "Cirrus CL-GD7548"
    VendorName  "Cirrus"
    BoardName   "CL-GD7548"

    VideoRam    1024
    Chipset     "clgd5428"
    Clockchip   "cirrus"
    Option	"linear"
# s.a.   MemBase	0xfc000000
    Option	"no_bitblt"
EndSection



Section "Screen"
    Driver      "svga"
    Device      "Cirrus CL-GD7548"
    Monitor     "Samsung Sens810 LCD"
    Subsection  "Display"
        Depth       8
        Modes       "800x600"
#        Virtual     1152 900
    EndSubsection
    Subsection  "Display"
        Depth       16
        Modes       "800x600"
    EndSubsection
EndSection


--------------1CFBAE3959E2B60015FB7483--


------- =_aaaaaaaaaa1--

------- =_aaaaaaaaaa0--