From owner-freebsd-mobile@FreeBSD.ORG Fri Jun 6 09:27:38 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5F63C37B401; Fri, 6 Jun 2003 09:27:38 -0700 (PDT) Received: from foem.leiden.webweaving.org (fia224-72.dsl.hccnet.nl [62.251.72.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id A740343FA3; Fri, 6 Jun 2003 09:27:34 -0700 (PDT) (envelope-from dirkx@webweaving.org) Received: from foem (IDENT:chuckwebweaving.org@foem [10.11.0.2]) h56GRPv7056481; Fri, 6 Jun 2003 18:27:25 +0200 (CEST) (envelope-from dirkx@webweaving.org) Date: Fri, 6 Jun 2003 18:27:25 +0200 (CEST) From: Dirk-Willem van Gulik X-X-Sender: dirkx@foem To: "M. Warner Losh" In-Reply-To: <20030606.101813.10580156.imp@bsdimp.com> Message-ID: <20030606182439.D801-100000@foem> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: hackers@freebsd.org cc: mobile@freebsd.org Subject: Re: Prism2 firmware upload support. X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jun 2003 16:27:38 -0000 On Fri, 6 Jun 2003, M. Warner Losh wrote: > I've looked into it. Primary/secondary versions aren't as interesting > as the actual product ID for determining which hex file to load. > There's also a need for getting additional data out of the current > firmware so it can be merged into the hex file before we burn the new > firmware. There's also a number of sanity checks that need to be made Yes - I've started with extracting the PDA information in a way so that it can be read by the likes of prism2dl. I find that I now need to decode the hex files in much more detail (Up to know I assumed it was just an intel hex file which needed to be uploaded in a some bit of ram. Turns out there is more to it than that :-(. > to make sure that primary firmware is compatible with the secondary > firmware you are loading, etc. Aye - I've also added an ioctl to get the 3 id/major/minor/variant values for nic/pri/sec; which is enough to drive prism2dl together with the PDA info. > to preclude it coming back up, do the firmware upload, and then call > wi_init again. It may make sense to set certain flags based on the > new version, but I don't think much else is required. Thanks - will limit myself to that. Dw