From: Hugh Caley <hcaley@loomer.com>
To: hollis@andrew.cmu.edu, linuxppc-dev@lists.linuxppc.org
Subject: Re: Lombard patches - which tree?
Date: Wed, 06 Oct 1999 22:38:00 -0700 [thread overview]
Message-ID: <37FC31B5.A450DFFF@loomer.com> (raw)
Hi, Hollis. Paul's rsync stable source does not require any other patches to
support ethernet or USB on a Lombard (at least it works with my Lombard's
ethernet and a Logitech Wingman USB mouse).
You could make your own, or the version I use is up on my web site:
http://www.loomer.com/linuxppc
Hugh
> Date: Wed, 06 Oct 1999 14:15:26 -0400
> From: "Hollis"
> Subject: Lombard patches - which tree?
>
> I'm looking to compile a Lombard kernel which has patches for both ethernet
> and USB (it does need a USB patch, right?). Have the patches made their way
> into Paul's rsync, or anywhere for that matter?
>
> - -Hollis
>
--
Hugh Caley, Unix Administrator
Babcock & Brown, San Francisco
510-524-1672
hughc@babcockbrown.com
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~1999-10-07 5:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-07 5:38 Hugh Caley [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-10-06 18:15 Lombard patches - which tree? Hollis
1999-10-06 19:03 ` Shaw Terwilliger
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=37FC31B5.A450DFFF@loomer.com \
--to=hcaley@loomer.com \
--cc=hollis@andrew.cmu.edu \
--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).