From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753895Ab1HJMFM (ORCPT ); Wed, 10 Aug 2011 08:05:12 -0400 Received: from mout4.freenet.de ([195.4.92.94]:53489 "EHLO mout4.freenet.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753720Ab1HJMFL (ORCPT ); Wed, 10 Aug 2011 08:05:11 -0400 Message-ID: <4E4273F4.4000200@01019freenet.de> Date: Wed, 10 Aug 2011 14:05:08 +0200 From: Andreas Hartmann User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:6.0) Gecko/20110806 Firefox/6.0 SeaMonkey/2.3 MIME-Version: 1.0 To: Greg KH CC: linux-kernel@vger.kernel.org Subject: Re: Linux 3.0: broken ums_eneub6250 References: <20110808042231.GA6248@kroah.com> <4E3F9B71.7040206@01019freenet.de> <20110808153302.GA8637@kroah.com> <4E403837.6040902@01019freenet.de> <20110809033919.GB13283@kroah.com> In-Reply-To: <20110809033919.GB13283@kroah.com> X-Enigmail-Version: 1.3a1pre Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Greg KH schrieb: > On Mon, Aug 08, 2011 at 09:25:43PM +0200, Andreas Hartmann wrote: >> Greg KH schrieb: >>> On Mon, Aug 08, 2011 at 10:16:49AM +0200, Andreas Hartmann wrote: >>>> Greg KH schrieb: >>>>> On Sun, Aug 07, 2011 at 08:39:20PM +0200, Andreas Hartmann wrote: >>>>>> Hi, >>>>>> >>>>>> obviously, nobody seems to be interested to work on this bug. Until it's >>>>>> fixed: There is a workaround to get the device working again with 2.6.39 >>>>>> and 3.0 - just remove the unusable ums-eneub6250.ko and replace it with >>>>>> the complete old and fine keucr-module - staging but working :-) >>>>>> >>>>>> https://bugzilla.novell.com/show_bug.cgi?id=709243#c1 >>>>> >>>>> How about working on a patch for the in-kernel version of the code to >>>>> get it to work properly so we can resolve this? >>>> >>>> If I would be able do this, I would have done it! On the other side: Why >>>> should I do it, if there is a module, which works just fine? >>> >>> Because I'm guessing that you wish to see the in-kernel code work >>> properly, right? >>> >>>> But you could send me patches which I could test. >>> >>> Have you emailed the developers of this driver these questions? I'm >>> sure they could help you out as they do have the hardware and they wrote >>> the patches in the first place. >>> >>>>> Given that very few >>>>> people actually have this hardware, >>>> >>>> It's a MSI CR620 notebook. I don't think, that there are just very few >>>> out there :-). >>>> >>>>> it's hard for us to work on the >>>>> driver. >>>> >>>> Why did you remove a working module if you can't ensure, that the >>>> replacement will cover the old module 100%? >>> >>> Because I trusted the original developers of that patch, that's the way >>> kernel development works. >>> >>> So please contact them and they would be glad to work with you to >>> resolve this issue. >> >> They have been already connected prior in this thread. I didn't get any >> answer right now. >> >> Obviously they are not interested in fixing the problem. > > That's rude, I apologize for this. This was wrong. But I was really angry about this line of action. > perhaps they were busy, or, the driver works for them on > their hardware, but something is different with your device that is > different here. It's fixed now. Details see https://bugzilla.novell.com/show_bug.cgi?id=709243#c7 Unfortunately I had to open another bug now with this module: https://bugzilla.novell.com/show_bug.cgi?id=711496#c0 Andreas