9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Chris McGee <sirnewton_01@yahoo.ca>
To: 9front@9front.org
Subject: Re: [9front] Re: [9fans] New 9front image for raspberry pi
Date: Sun, 15 Jan 2017 19:45:17 -0500	[thread overview]
Message-ID: <BE4FEB30-DF3C-4EB4-9D86-4F7ED5BF0480@yahoo.ca> (raw)
In-Reply-To: <4739132bb32ee3c1ec0b11dd94fd27e9@pi3L.jitaku.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1753 bytes --]

Yes, there's something wrong with the USB driver. I'm looking into it but if someone can spot the problem please let me know.

https://github.com/sirnewton01/rpi-9front/tree/master/bcm

It doesn't seem to be be present with the older single core pis. The problem presents itself as a HID message indicating extra key presses that get sent to kbdfs. It seems that the packet gets corrupted somehow.

Thanks,
Chris

> On Jan 15, 2017, at 7:38 PM, kokamoto@hera.eonet.ne.jp wrote:
> 
> The mouse input also freezes some time.
> When I playes with games/mahjonng, it occures.
> It may be recovered when I wait some time, and tries it onece again.
> Probabley usb driver has something problem?
> 
> Kenji
> 
>> Thanks for trying it out. I'm not sure about the Japanese keyboard, but that key input chattering problem is the one I'm currently hunting.
>> 
>> If anyone can spot the flaw in the usbdwc.c, trap.c or clock.c it would be a great help. Meanwhile, I'll keep looking at it myself, if slowly.
>> 
>> Chris
>> 
>> On Jan 15, 2017, at 7:01 PM, kokamoto@hera.eonet.ne.jp wrote:
>> 
>>>> I'm still working out some USB kinks. Have you had any keyboard problems? Did you compile/run with 9front
>>> 
>>> Thank you verry much, Chris.
>>> 
>>> Yes, I'm using the 9pif2 kernel for terminal (now using it)
>>> with root from tcp. I'm glad to see 4 cores here!
>>> 
>>> Yes, I have a problem to use Japanese USB keyboard.
>>> I can use it for typing '_' '|' by patching by myself
>>> (it may not be needed for another country).
>>> 
>>> I have one problem to use it, that is seeing chattering of keyinput,
>>> such that
>>> secstore: WHC
>>> where I did not type anything before that prompt.
>>> 
>>> Kenji
>>> 
> 

[-- Attachment #2: Type: text/html, Size: 4254 bytes --]

  reply	other threads:[~2017-01-16  0:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-09  3:17 kokamoto
2017-01-15  6:16 ` [9front] " kokamoto
2017-01-15 13:13   ` Chris McGee
2017-01-15 17:54     ` Steve Simon
2017-01-16  0:01     ` kokamoto
2017-01-16  0:11       ` Chris McGee
2017-01-16  0:38         ` kokamoto
2017-01-16  0:45           ` Chris McGee [this message]
2017-01-16  2:15             ` kokamoto

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BE4FEB30-DF3C-4EB4-9D86-4F7ED5BF0480@yahoo.ca \
    --to=sirnewton_01@yahoo.ca \
    --cc=9front@9front.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).