From owner-freebsd-arch@FreeBSD.ORG  Sun Sep 28 20:19:48 2008
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: freebsd-arch@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 9200D1065687
	for <freebsd-arch@FreeBSD.org>; Sun, 28 Sep 2008 20:19:48 +0000 (UTC)
	(envelope-from bright@elvis.mu.org)
Received: from elvis.mu.org (elvis.mu.org [192.203.228.196])
	by mx1.freebsd.org (Postfix) with ESMTP id 814D28FC0C
	for <freebsd-arch@FreeBSD.org>; Sun, 28 Sep 2008 20:19:48 +0000 (UTC)
	(envelope-from bright@elvis.mu.org)
Received: by elvis.mu.org (Postfix, from userid 1192)
	id 531121A3C37; Sun, 28 Sep 2008 13:19:48 -0700 (PDT)
Date: Sun, 28 Sep 2008 13:19:48 -0700
From: Alfred Perlstein <alfred@freebsd.org>
To: "M. Warner Losh" <imp@bsdimp.com>
Message-ID: <20080928201948.GE36572@elvis.mu.org>
References: <20080928100731.GA49323@onelab2.iet.unipi.it>
	<20080928.135855.1708680935.imp@bsdimp.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20080928.135855.1708680935.imp@bsdimp.com>
User-Agent: Mutt/1.4.2.3i
Cc: freebsd-arch@FreeBSD.org
Subject: Re: dynamic update of usb/pci/quirks tables
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion related to FreeBSD architecture <freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Sep 2008 20:19:48 -0000

* M. Warner Losh <imp@bsdimp.com> [080928 13:01] wrote:
> uscanner_devs and sis_devs aren't quirks.  They are device tables.
> 
> You've repeated ignored the mapping idea that I've posted.  You can't
> just add stuff to tables randomly and expect that to work (says
> someone who has actually done this to lots of drivers in the tree in
> the pccard era).  the driver has to know what kind of device to treat
> it as.
> 
> Putting a translation table into the kernel is much easier and you
> don't have to worry about hokey kludges like what you describe with
> 'patch'.
> 
> Maybe it will work out for the other tables you want to update, but it
> won't work well for device tables.

I really like the idea of using a kmod to just add the new device
strings.. (some form of what Hans did).

-Alfred