Return-path: Received: from crystal.sipsolutions.net ([195.210.38.204]:60830 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932469AbXBNTY5 (ORCPT ); Wed, 14 Feb 2007 14:24:57 -0500 Subject: Re: network manager vs. missing firmware From: Johannes Berg To: James Ketrenos Cc: Dan Williams , linux-wireless@vger.kernel.org In-Reply-To: <45D25984.7080808@linux.intel.com> References: <1171392106.10344.100.camel@johannes.berg> <1171394598.5329.31.camel@localhost.localdomain> <45D25984.7080808@linux.intel.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-jIrnq8ett1/VzRSg4+s6" Date: Wed, 14 Feb 2007 20:24:46 +0100 Message-Id: <1171481086.6093.8.camel@johannes.berg> Mime-Version: 1.0 Sender: linux-wireless-owner@vger.kernel.org List-ID: --=-jIrnq8ett1/VzRSg4+s6 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Tue, 2007-02-13 at 16:36 -0800, James Ketrenos wrote: > Perhaps solving the larger problem of "the driver knows something is=20 > horribly wrong, but has no way to tell the user" would be good.=20 Yes, but I think it's out of scope for wireless. Maybe we should come up with a generic "driver problem" userspace interface. johannes --=-jIrnq8ett1/VzRSg4+s6 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Comment: Johannes Berg (powerbook) iD8DBQBF02H+/ETPhpq3jKURArRqAJ4vklt7yx/nWBedSFexT7iA+EcJmQCePUOF Rtm2cTxxWf9/498BdrR1QKQ= =rmar -----END PGP SIGNATURE----- --=-jIrnq8ett1/VzRSg4+s6--