From owner-freebsd-hardware Wed May 20 02:27:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA26261 for freebsd-hardware-outgoing; Wed, 20 May 1998 02:27:33 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA26255; Wed, 20 May 1998 02:27:28 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id TAA27055; Wed, 20 May 1998 19:25:01 +1000 Date: Wed, 20 May 1998 19:25:01 +1000 From: Bruce Evans Message-Id: <199805200925.TAA27055@godzilla.zeta.org.au> To: hardware@FreeBSD.ORG, tarkhil@asteroid.svib.ru Subject: Re: IWill and sio, again and again Cc: current@FreeBSD.ORG Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >I am using IWill MB with weird comports, not detectable by sio driver. I have >found patches, applied them and all was well. > >I've tried to build current kernel and found that sio.c has changed, and the >old patch won't fit anymore. I don't know of any correct patch, but the problem can be worked around by ignoring the results of tests 5 and 7. >Does anyone know if there is any effort to commit changes to kernel ssources, >to make soi.c understand EVERY comport, or at least make something like >options WEIRDCOMPORT, so I won't have to patch again and again? This is impossible, since manufacturers keep inventing new incompatibilites. The IWill actually seems to have compatible sio ports and an incompatible interrupt controller. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message