linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Buell <alex.buell@munted.org.uk>
To: David Miller <davem@davemloft.net>
Cc: linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Using s3virge card in Sun Blade 2000
Date: Tue, 04 Jan 2011 20:38:22 +0000	[thread overview]
Message-ID: <1294173502.17576.26.camel@lithium> (raw)
In-Reply-To: <20110104.121958.232738534.davem@davemloft.net>

On Tue, 2011-01-04 at 12:19 -0800, David Miller wrote:

> First of all, the machine dies because those illegal I/O accesses
> generate an unrecoverable asynchronous memory error, we cannot recover
> from it so we have to panic the entire machine.
> 
> Secondly, the keyboard doesn't work because I never implemented the
> monstrous amount of code necessary to allow USB keyboard to work with
> OpenPROM after booting up.
> 
> You have to essentially reset the entire USB host controller, unload
> all of the pending queued URBs in the host controller, put it into a
> quiescent state, and then asynchronously process all USB keyboard
> device events via USB host controller polling implemented via OpenPROM
> backcalls into the kernel, and from there feed the characters to
> OpenPROM so it can see the keypresses.  Upon return from OpenPROM you
> have to reload all of the unloaded URBs back onto the USB host
> controller queues so the kernel can use USB again.
> 
> I never considered this enormous amount of work worth doing, the
> payback is just too small.

Thank you for that explanation, it's much appreciated.
-- 
Tactical Nuclear Kittens

  reply	other threads:[~2011-01-04 20:38 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-03 16:32 Using s3virge card in Sun Blade 2000 Alex Buell
2011-01-03 18:58 ` David Miller
2011-01-03 19:39   ` Alex Buell
2011-01-03 19:43     ` David Miller
2011-01-03 20:33       ` Alex Buell
2011-01-03 20:39         ` David Miller
2011-01-03 21:36           ` Alex Buell
2011-01-03 22:36             ` David Miller
2011-01-04 15:57               ` Alex Buell
2011-01-04 17:26                 ` David Miller
2011-01-04 20:11                   ` Alex Buell
2011-01-04 20:19                     ` David Miller
2011-01-04 20:38                       ` Alex Buell [this message]
2011-01-05 19:07             ` David Miller
2011-01-05 21:13               ` Alex Buell
2011-01-06  0:33                 ` Alex Buell
2011-01-06 20:42                   ` Francois Romieu
2011-01-06 20:50                     ` Alex Buell
2011-01-06 22:24                       ` Alex Buell
2011-01-06 22:29                         ` David Miller
2011-01-06 23:25                           ` Alex Buell
2011-01-06 23:34                           ` Alex Buell
2011-01-03 20:37     ` Dave Airlie
2011-01-05 20:37   ` Geert Uytterhoeven

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=1294173502.17576.26.camel@lithium \
    --to=alex.buell@munted.org.uk \
    --cc=davem@davemloft.net \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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).