linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <bh40@calva.net>
To: Dan Malek <dan@mvista.com>,
	linuxppc-dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: BK 2.4-test8 PCI/USB/G4
Date: Mon, 18 Sep 2000 11:03:50 +0200	[thread overview]
Message-ID: <20000918090350.7377@mailhost.mipsys.com> (raw)
In-Reply-To: <39C3F4DA.2363A35E@mvista.com>


>For those of you using the latest 2.4 BitKeeper tree on a G4, I have
>a partial solution to making USB work again.  After pulling updates,
>simply 'bk get -r1.18 arch/ppc/kernel/pci.c', which will get the
>previous version of this file.  Build the kernel and at least you get
>the mouse/keyboard, X, and stuff like that again.  At least you can
>make progress on other tasks while we sort this out.

I've pushed a temporary workaround yesterday that re-enables the "old"
code via
a #define, at least until I've found what's wrong with Geert new code.

Ben.


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

      reply	other threads:[~2000-09-18  9:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-16 22:31 BK 2.4-test8 PCI/USB/G4 Dan Malek
2000-09-18  9:03 ` Benjamin Herrenschmidt [this message]

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=20000918090350.7377@mailhost.mipsys.com \
    --to=bh40@calva.net \
    --cc=dan@mvista.com \
    --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).