Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758138AbXF2I35 (ORCPT ); Fri, 29 Jun 2007 04:29:57 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751961AbXF2I3s (ORCPT ); Fri, 29 Jun 2007 04:29:48 -0400 Received: from s131.mittwaldmedien.de ([62.216.178.31]:25158 "EHLO s131.mittwaldmedien.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751951AbXF2I3r (ORCPT ); Fri, 29 Jun 2007 04:29:47 -0400 From: Holger Schurig To: Clemens Koller Subject: Re: 2.6.21.5: BUG: usbtouchscreen.c DMC TSC-10 wrong descriptor type / type->init() failed. Date: Fri, 29 Jun 2007 10:29:40 +0200 User-Agent: KMail/1.9.5 Cc: Dmitry Torokhov , linux-kernel@vger.kernel.org, daniel.ritz@gmx.ch References: <468294E4.40801@anagramm.de> <4683D444.5030408@anagramm.de> In-Reply-To: <4683D444.5030408@anagramm.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200706291029.40779.hs4233@mail.mn-solutions.de> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1257 Lines: 32 > After the reset, I got a 0x06 0x00 back, which is fine. > > But when the driver sets the coordinate output rate, the > TSC-103 answered 0x15 0x01 which means that the TSC-10 is used > with an EEPROM but the EEPROM data is empty (which is > correct). > > In that case the driver should at least continue to allow > initialization of the EEPROM later on. No, I don't think so. Not in it's current form. Currently, usbtouchscreen doesn't have any means to initialize an EEPROM. And in the absence of such a possibility, you need other means to accomplish your task. The current behavior provides you with this "plan b": If you set the rate and that doesn't work because no EEPROM is there, the driver fails. While doing it, it will release the device. This brings in the opportunity to access the touchscreen controller from userspace, e.g. with libusb, and write the EEPROM. After this, reboot, and be happy. Because now the device would act correctly on the "set rate" command and would be usable. - 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/