Re: USB keyboard not working

>So the next thing I 
> stumbled over is ehci support. As I said earlier I merged your gc-linux changes 
> into kvm.git which is pretty close to tip. Apparently I'm getting a DSI in the 
> interrupt handling code now.
>

Obviously your fault :-P

>Basically there are two questions arising 
> from this:
>
>1) Is there an easy way to debug such things? I'm having a 
> hard time reading from a TV screen, the contents scroll out, copy&paste 
> doesn't work, etc. Netconsole isn't an option I guess because wifi doesn't play 
> well with it. So what is left to get dumps?
>

The easiest way to debug stuff is to use an "usbgecko".
It's an adapter that plugs into a memory card slot of the gamecube/wii on one side and a USB port on your PC on the other side. It provides a USB serial connection on the PC and a simple SPI interface on the gamecube/wii which allows to send/receive data to the PC.

>2) Would you mind rebasing 
> your master to something more current 
> :-).


I decided to mainline code instead of continuing development out of tree.
See www.gc-linux.org/wiki/Mainline_Kernel for a current status of what's already in.

But, as mainlining is taking more time than I expected (for example, I'm stuck waiting for some USB and swiotlb core changes that the EHCI driver patches for mainline depends on) I may eventually integrate as-is the old MIKE series into a mainline-based branch. While doing that, I'll get rid of all IOS-based support which I don't plan to support on the mainline kernel.

Cheers,
Albert



      

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev