From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "David S. Miller" <davem@davemloft.net>
Cc: Paul Mackerras <paulus@samba.org>,
jk@blackdown.de, akpm@osdl.org, oleg@tv-sign.ru,
linux-kernel@vger.kernel.org, maneesh@in.ibm.com
Subject: Re: [PATCH] fix __mod_timer vs __run_timers deadlock.
Date: Wed, 04 May 2005 09:44:53 +1000 [thread overview]
Message-ID: <1115163893.7568.49.camel@gaston> (raw)
In-Reply-To: <20050503115103.7461ae5e.davem@davemloft.net>
On Tue, 2005-05-03 at 11:51 -0700, David S. Miller wrote:
> On Tue, 3 May 2005 12:48:40 +1000
> Paul Mackerras <paulus@samba.org> wrote:
>
> > Juergen Kreileder writes:
> >
> > > BTW, xmon doesn't work for me. 'echo x > /proc/sysrq-trigger' gives
> > > me a :mon> prompt but I can't enter any commands.
> >
> > We don't have polled interrupts-off input methods for USB keyboards.
>
> There is nothing in the USB nor INPUT layers really blocking an
> implementation of this BTW.
>
> I need this on Sparc64 as well, so that PROM command line input
> works after booting with USB keyboards.
Nothing prevents it ? well, I wouldn't be that optimistic :) The USB
stuff is a bit complex, it inlcudes doing DMAs, so manipulating the
iommu, dealing with URB queues (and thus allocating/releasing them)
etc... and especially in the context of xmon, that mean letting the
driver do a lot of these at any time whatever state the system is...
So it's possible, but will probably be difficult and not very reliable.
An alternative is to take over the OHCI chip completely and implement a
micro-stack that only does interrupt pipe polling and hard decodes kbd
data based on a standard boot protocol layout... Handing the controller
back to normal USB operations may prove a bit difficult here though.
Ben.
next prev parent reply other threads:[~2005-05-03 23:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-01 7:55 [PATCH] fix __mod_timer vs __run_timers deadlock Oleg Nesterov
2005-05-01 9:31 ` Andrew Morton
2005-05-02 22:50 ` Juergen Kreileder
2005-05-03 0:13 ` Benjamin Herrenschmidt
2005-05-03 1:24 ` Lee Revell
2005-05-03 1:28 ` Benjamin Herrenschmidt
2005-05-03 1:33 ` Zwane Mwaikambo
2005-05-03 1:35 ` Juergen Kreileder
2005-05-03 2:48 ` Paul Mackerras
2005-05-03 18:51 ` David S. Miller
2005-05-03 23:44 ` Benjamin Herrenschmidt [this message]
2005-05-03 23:39 ` David S. Miller
2005-05-04 0:05 ` Benjamin Herrenschmidt
2005-05-02 4:08 ` Maneesh Soni
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=1115163893.7568.49.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=jk@blackdown.de \
--cc=linux-kernel@vger.kernel.org \
--cc=maneesh@in.ibm.com \
--cc=oleg@tv-sign.ru \
--cc=paulus@samba.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