Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1161754AbXEBIWe (ORCPT ); Wed, 2 May 2007 04:22:34 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S964796AbXEBIWe (ORCPT ); Wed, 2 May 2007 04:22:34 -0400 Received: from cassiel.sirena.org.uk ([80.68.93.111]:1624 "EHLO cassiel.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752881AbXEBIWb (ORCPT ); Wed, 2 May 2007 04:22:31 -0400 Date: Wed, 2 May 2007 09:22:13 +0100 From: Mark Brown To: Tim Hockin Cc: =?utf-8?B?UmFmYcWC?= Bilski , Andrew Morton , linux-kernel@vger.kernel.org, netdev@vger.kernel.org Message-ID: <20070502082211.GD31630@sirena.org.uk> Mail-Followup-To: Tim Hockin , =?utf-8?B?UmFmYcWC?= Bilski , Andrew Morton , linux-kernel@vger.kernel.org, netdev@vger.kernel.org References: <20070501084639.GA528@sirena.org.uk> <46371590.4090004@interia.pl> <20070501180830.GA31630@sirena.org.uk> <46379A7E.3000109@interia.pl> <20070501212750.GC31630@sirena.org.uk> <46382798.2090709@interia.pl> <463830E1.8080107@interia.pl> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="FFoLq8A0u+X9iRU8" Content-Disposition: inline In-Reply-To: X-Cookie: Are you sure the back door is locked? User-Agent: Mutt/1.5.13 (2006-08-11) X-SA-Exim-Connect-IP: 82.32.140.119 X-SA-Exim-Mail-From: broonie@sirena.org.uk Subject: Re: Natsemi DP83815 driver spaming X-SA-Exim-Version: 4.2.1 (built Tue, 09 Jan 2007 17:23:22 +0000) X-SA-Exim-Scanned: Yes (on cassiel.sirena.org.uk) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1543 Lines: 43 --FFoLq8A0u+X9iRU8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, May 01, 2007 at 11:51:41PM -0700, Tim Hockin wrote: > I'm not sure what the right answer is. The code was designed to do > the right thing, and yet in your case it's broken. Does it need to be > a build option to work around broken hardware? Yuck. Without a system that really needs the original problem that was being worked around it's going to be hard to see if the workaround still does the job. Given the nature of the failure I wouldn't be surprised if it broke different things on every board that has problems. How about a sysfs tuneable? It's not nice but at least it's runtime. --=20 "You grabbed my hand and we fell into it, like a daydream - or a fever." --FFoLq8A0u+X9iRU8 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iQCVAwUBRjhKMA2erOLNe+68AQIcjQP+LTDTrSu3WKuiAAI4swDlo06iP3MfZFo3 N/1NgP23gXxkrPYnMjlPkjJOeTpbDDkdD2UdoheExSvNaJ069rdURIvnjanTe+52 ewJMpWYSNi5DZOgyMU1AlOcFN8OcKJ/bGSUl5aMPnGt5+/NdFAC7yIriCsgbbHFd mrBKjDG4IMQ= =o2XV -----END PGP SIGNATURE----- --FFoLq8A0u+X9iRU8-- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/