From owner-freebsd-current Tue Feb 12 11:55:47 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail.yadt.co.uk (yadt.demon.co.uk [158.152.4.134]) by hub.freebsd.org (Postfix) with SMTP id 571C737B41D for ; Tue, 12 Feb 2002 11:55:42 -0800 (PST) Received: (qmail 44988 invoked from network); 12 Feb 2002 19:51:35 -0000 Received: from unknown (HELO mail.gattaca.yadt.co.uk) (qmailr@10.0.0.2) by yadt.demon.co.uk with SMTP; 12 Feb 2002 19:51:35 -0000 Received: (qmail 779 invoked by uid 1000); 12 Feb 2002 19:51:35 -0000 Date: Tue, 12 Feb 2002 19:51:35 +0000 From: David Taylor To: freebsd-current@freebsd.org Subject: urio driver Message-ID: <20020212195135.GA746@gattaca.yadt.co.uk> Mail-Followup-To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline User-Agent: Mutt/1.3.25i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG The urio driver appears to call make_dev, discarding the returned dev_t, and never bothers to call destroy_dev. Although this is presumably broken, it did _work_ previously. however, there is now a 'panic("don't do that");' call in make_dev (and destroy_dev) to prevent duplicate calls, thus the machine will crash if you attach/detach/re-attach a rio. This has been happing for quite a while now, but I've never been bothered enough to actually try to fix it, until now. :) I have approximately no experience with FreeBSD device drivers, but I'm currently attempting to see if I can figure out how the other u*.c files handle detaching... any hints would be appreciated :) -- David Taylor davidt@yadt.co.uk "The future just ain't what it used to be" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message