Date: Thu, 5 Jun 2014 06:31:01 +0000 From: "Scott, Brian" <brian.scott4@det.nsw.edu.au> To: Hans Petter Selasky <hps@selasky.org>, "'arm@freebsd.org'" <arm@freebsd.org> Subject: RE: Changes to dwc_otg USB controller code (stable/10) Message-ID: <7DB382CFB050654DBFF7A39B1F8056EB3321D251@WPEXCHMBSL1021.central.det.win> In-Reply-To: <53900BC2.3090701@selasky.org> References: <7DB382CFB050654DBFF7A39B1F8056EB3321BE3F@WPEXCHMBSL1021.central.det.win> <538EF145.5020608@selasky.org> <538EF541.9050502@selasky.org> <7DB382CFB050654DBFF7A39B1F8056EB3321D1F3@WPEXCHMBSL1021.central.det.win> <539009BB.5030906@selasky.org> <53900AC7.5070402@selasky.org> <53900BC2.3090701@selasky.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, Just rebuilt using the 'patched' version of the file rather than replacin= g the whole file. Compiles without problems. The other symptoms remain (erratic mouse movement, dropped keyboard chara= cters) on the new version. Thanks, Brian -----Original Message----- From: Hans Petter Selasky [mailto:hps@selasky.org]=20 Sent: Thursday, 5 June 2014 4:19 PM To: Scott, Brian; 'arm@freebsd.org' Subject: Re: Changes to dwc_otg USB controller code (stable/10) On 06/05/14 08:14, Hans Petter Selasky wrote: > On 06/05/14 08:10, Hans Petter Selasky wrote: >> On 06/05/14 07:56, Scott, Brian wrote: >>> Hans Petter, >>> >>> Good news and bad news. If I add some casts to the code to make it >>> compile (don't know if its valid or not, casting from a constant to a= >>> non-constant could be ugly and I haven't looked beyond the error >>> messages), I can now boot the system and the various USB devices are >>> recognised properly. >>> >>> The bad news is that the keyboard is very intermittent now. Many >>> characters are simply being dropped when I type. Sometimes I get a >>> character repeating as though the keyboard has gone into repeat mode,= >>> suggesting that a character up event has been lost. Moving the mouse >>> around has it freeze every few seconds then resume. >>> >>> I have had a similar behaviour on another raspberry pi at home that >>> I've just been blaming on poor hardware. This means that I may be >>> seeing an older problem here. Don't know. >> >> Hi, >> >> I'll see if I can reproduce. >> > > Reminds me, you probably should grab this patch aswell: > > http://svnweb.freebsd.org/changeset/base/265913 > > I'll see if I can get it MFC'ed. Seems to already be MFC'ed. --HPS ********************************************************************** This message is intended for the addressee named and may contain privileged information or confidential information or both. If you are not the intended recipient please delete it and notify the sender. **********************************************************************
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7DB382CFB050654DBFF7A39B1F8056EB3321D251>