From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: ramp@oddjob.uchicago.edu
Cc: linuxppc-user@lists.linuxppc.org, linuxppc-dev@lists.linuxppc.org
Subject: Re: trying cutting edge kernel ..
Date: Wed, 26 Jan 2000 14:12:31 -0500 [thread overview]
Message-ID: <388F471F.D33F9B7C@mandrakesoft.com> (raw)
In-Reply-To: Pine.LNX.4.10.10001261247070.7391-100000@xpol.uchicago.edu
ramp@oddjob.uchicago.edu wrote:
> After having my USB printer work I wanted to see if my USB Zip250
> would work. I looked at the linux-usb mailing list archives and
> found that some people were working on it and that some devel
> kernels 2.3.41-? could be made to work. So I went to ftp.kernel.org
> and found the following files -
>
> v2.3/linux-2.3.40.tar.bz2
> testing/pre-patch-2.3.41-X.bz2 where X=[1,2,3]
>
> My question is: Do I need to patch all 3 in order or should I just
> patch with the last file - in this case 3.
You just need the greatest 'pre' number, currently 2.3.41-pre3.
> Also, does this include all of the latest 2.3.39 linux-pmac-devel
> from linuxcare.com.au?
I only boot vanilla kernels on my PowerMac 7200. 2.2.15-pre4 works, and
with a little bit of tweaking, 2.3.41-preXX works too. It's too much of
a PITA to work with loads of patches outside the main kernel source
tree.
I've send a couple small patches off to Cort. Let me know if you can't
build on 2.3.41-preXX and I'll send the fixes to you and the lists.
Jeff
--
Jeff Garzik | Andre the Giant has a posse.
Building 1024 |
MandrakeSoft, Inc. |
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2000-01-26 19:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-26 19:02 trying cutting edge kernel ramp
2000-01-26 19:12 ` Jeff Garzik [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=388F471F.D33F9B7C@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=linuxppc-user@lists.linuxppc.org \
--cc=ramp@oddjob.uchicago.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.