linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <bh40@calva.net>
To: <linux-usb@suse.com>
Cc: "Dunlap, Randy" <randy.dunlap@intel.com>,
	<linuxppc-dev@lists.linuxppc.org>
Subject: RE: [linux-usb] USB problems on Lombard Powerbook ... and more
Date: Thu, 20 Apr 2000 16:27:31 +0200	[thread overview]
Message-ID: <20000420142732.6194@mailhost.mipsys.com> (raw)
In-Reply-To: <D5E932F578EBD111AC3F00A0C96B1E6F0545CA3E@orsmsx31.jf.intel.com>


On Wed, Apr 19, 2000, Dunlap, Randy <randy.dunlap@intel.com> wrote:

>> (kernel 2.2.15pre17 compiles fine, with usb modules. I think
>> the kernel I am using
>> has a USB backport coming from 2.3. Actually I got these sources from
>> linuxcare - see point 2)
>
>Some things below make me think that whatever you have
>is not very recent, so the Linux USB Guide and
>current email threads don't necessarily apply to your
>USB source code.

The "current" stable kernel used on PowerMacs is Paul Mackerras tree and
contains an old backport of the 2.3.x USB stack (one of the last version
to use Greg old ohci.c driver). We use it because it's stable and appear
to work fine with keyboards and mice on all macs out there. That mean
that machines with USB-only kbds and mice could at least be used, which
was a progress over previous stacks ;)

However, it's definitely not complete enough to be used for anything
else. (Well, a few drivers actually work, but that's not the point).

The recent 2.3.x stack appear to work quite well on macs too, now that
the biggest OHCI problems were ironed out, but has not yet been
"tortured" enough for us to backport it into our stable 2.2.x series.

>Yes (centralized).  Yes (several wandering around).
>Linus maintains the blessed tree for all architectures.
>Development trees can and do also exist elsewhere,
>like PPC, Sparc, ARM, etc.  They will eventually get merged
>back into the Linus tree.

In the case of the macs, we have a quite huge batch of changes that has
not been merged in the 2.2.x tree yet, mostly because those changes (that
concern new machines support) were finished too late for inclusing in
2.2.14, and Alan wants only bug fixes in 2.2.15.
Also, since we use this weird USB backport that may never end up in the
"official" 2.2.x series, PowerMac users usually rely on kenrels
maintained by Paul Mackerras (who is _the_ maintainer of the PowerMac port).

For 2.3.x series, the work is done on our "specific" PPC trees (Paul's
tree and hq.fsmlabs.com bitkeeper tree) and regulary merged in Linus main
one. Ideally, when 2.4 is final, all the PowerMac specific stuffs will be
up-to-date.

For more infos about PowerMac kernels, one can consult Paul's page at:

http://linuxcare.com.au/paulus/kernels.html


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

      reply	other threads:[~2000-04-20 14:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-20  0:06 [linux-usb] USB problems on Lombard Powerbook ... and more Dunlap, Randy
2000-04-20 14:27 ` 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=20000420142732.6194@mailhost.mipsys.com \
    --to=bh40@calva.net \
    --cc=linux-usb@suse.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=randy.dunlap@intel.com \
    /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).