From owner-freebsd-arch@FreeBSD.ORG Sat Jul 10 15:16:56 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from green.homeunix.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id A7EAC16A4CE; Sat, 10 Jul 2004 15:16:55 +0000 (GMT) Received: from green.homeunix.org (green@localhost [127.0.0.1]) by green.homeunix.org (8.12.11/8.12.11) with ESMTP id i6AFGrNM018805; Sat, 10 Jul 2004 11:16:53 -0400 (EDT) (envelope-from green@green.homeunix.org) Received: (from green@localhost) by green.homeunix.org (8.12.11/8.12.11/Submit) id i6AFGm80018804; Sat, 10 Jul 2004 11:16:48 -0400 (EDT) (envelope-from green) Date: Sat, 10 Jul 2004 11:16:47 -0400 From: Brian Fundakowski Feldman To: Poul-Henning Kamp Message-ID: <20040710151647.GI1626@green.homeunix.org> References: <20040709232355.GB1626@green.homeunix.org> <1420.1089448716@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1420.1089448716@critter.freebsd.dk> User-Agent: Mutt/1.5.6i cc: arch@freebsd.org Subject: Re: userland firmware loader? X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Jul 2004 15:16:57 -0000 On Sat, Jul 10, 2004 at 10:38:36AM +0200, Poul-Henning Kamp wrote: > In message <20040709232355.GB1626@green.homeunix.org>, Brian Fundakowski Feldma > n writes: > > >I'm writing a driver that uses a 100KB firmware file and could need to > >read it again, after initialization, to reset the device (or to load > >more). Since this device is primarily found in CardBus form, I think > >it makes a lot of sense to be able to get the firmware file at any time > >but without specific user intervention. > > > >Is this something devd should be doing? > > I would advocate a generic interface for retrieving firmware from userland. What do you think about using the normal devctl_notify(9) for pushing out firmware requests, and having a new device method that receives just a user data pointer and length for it to copyin(9)? It wouldn't be a very symmetrical API, but it seems like a way that might fit it into the current structure the easiest, devd and devctl and newbus. -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\