linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Chris Emerson <cemerson@chiark.greenend.org.uk>,
	<linuxppc-dev@lists.linuxppc.org>
Subject: Re: [Dri-devel] PPC Lockup (ati-pcigart-branch)
Date: Sat, 20 Jan 2001 02:38:32 +0100	[thread overview]
Message-ID: <19341214191016.27444@mailhost.mipsys.com> (raw)
In-Reply-To: <14952.53532.864761.156822@chiark.greenend.org.uk>


>Ok.  Is there a fundamental reason which prevents it being possible to
>use the USB keyboard, or just hard work?
>
>> >I'm currently running 2.4.1pre7 rsynced from the bk tree.
>>
>> pre8 is already there ;)
>
>Well, unless there are any vital fixes, I'll hold off for a few days.
>:-)

Very hard work indeed :) You'd have to write a mecanism to let most of
the OHCI controller code to run in a polled way from within the
debugger... quite nasty.

Ben.

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-01-20  1:38 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-19  3:26 PPC Lockup (ati-pcigart-branch) Michel Dänzer
2001-01-19  3:55 ` Dan Malek
2001-01-19  6:53   ` [Dri-devel] " Gareth Hughes
2001-01-19 16:48     ` Jeff Hartmann
2001-01-19 17:24     ` Dan Malek
2001-01-20  0:45       ` Gareth Hughes
2001-01-19 16:40 ` [Dri-devel] " Jeff Hartmann
2001-01-19 17:11   ` Benjamin Herrenschmidt
2001-01-19 22:26     ` Chris Emerson
2001-01-19 22:59       ` Benjamin Herrenschmidt
2001-01-19 23:43         ` Chris Emerson
2001-01-20  1:38           ` Benjamin Herrenschmidt [this message]
2001-01-20 13:21             ` Michael Schmitz
2001-01-20 16:00               ` Benjamin Herrenschmidt
2001-01-20 17:03                 ` Michael Schmitz
2001-01-20  2:46     ` Michel Dänzer
2001-01-20  4:17       ` Michel Dänzer
2001-01-22  9:44         ` Michel Dänzer
2001-01-22 17:59           ` Roman Zippel
2001-01-22 18:18             ` Michel Dänzer
2001-01-22 18:54               ` Roman Zippel
2001-01-22 19:39                 ` Dan Malek
2001-01-22 20:08                   ` Michel Dänzer
2001-01-22 20:30                   ` Jeff Hartmann
2001-01-22 21:23                     ` Roman Zippel
2001-01-22 23:12                       ` Frank Rowand
2001-01-22 21:31                     ` Dan Malek
2001-01-22 21:48                       ` Jeff Hartmann
2001-01-22 22:15                         ` Roman Zippel
2001-01-23 16:14                         ` Mike Beede
2001-01-22 22:31                       ` Roman Zippel
2001-01-23  0:24                         ` Dan Malek
2001-01-23  2:28                           ` Takashi Oe
2001-01-23  2:40                             ` Dan Malek
2001-01-23  4:40                               ` Ralph Metzler
2001-01-23  5:48                               ` Takashi Oe
2001-01-23 11:24                           ` Roman Zippel
2001-01-23  0:34                         ` Frank Rowand
2001-01-23  0:43                           ` Frank Rowand
2001-01-23 11:32                           ` Roman Zippel
2001-01-22 20:43                   ` Roman Zippel
2001-01-22 21:07                     ` Jeff Hartmann
2001-01-22 17:33         ` Dan Malek
2001-01-22 17:38           ` Jeff Hartmann
2001-01-22 17:38           ` Gareth Hughes
2001-01-22 17:43           ` Michel Dänzer
2001-01-22 18:36             ` Dan Malek
2001-01-22 18:44               ` Jeff Hartmann
2001-01-22 18:47               ` Michel Dänzer
2001-01-22 21:13         ` Dan Malek
2001-01-22 21:58           ` Roman Zippel
2001-01-22 23:48         ` Paul Mackerras
2001-01-23  0:13           ` Dan Malek
2001-01-20 13:15       ` Michael Schmitz
2001-01-19 17:11   ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2001-01-23  3:34 Iain Sandoe
2001-01-23  6:49 Robert E Brose II
2001-01-23  7:01 ` 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=19341214191016.27444@mailhost.mipsys.com \
    --to=benh@kernel.crashing.org \
    --cc=cemerson@chiark.greenend.org.uk \
    --cc=linuxppc-dev@lists.linuxppc.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).