Date: Thu, 05 Jun 2014 08:18:42 +0200 From: Hans Petter Selasky <hps@selasky.org> To: "Scott, Brian" <brian.scott4@det.nsw.edu.au>, "'arm@freebsd.org'" <arm@freebsd.org> Subject: Re: Changes to dwc_otg USB controller code (stable/10) Message-ID: <53900BC2.3090701@selasky.org> In-Reply-To: <53900AC7.5070402@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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53900BC2.3090701>