From: Tahoma Toelkes <tahoma@nshore.com>
To: linux-mips@linux-mips.org
Cc: Dan Malek <dan@embeddededge.com>
Subject: zboot patch and linux_2_4 branch [was Re: Linux Boot Issue in Au1550]
Date: Fri, 12 Mar 2004 15:59:55 -0600 [thread overview]
Message-ID: <405232DB.5050902@nshore.com> (raw)
In-Reply-To: <4051D48F.5080300@embeddededge.com>
Dan Malek wrote:
> You will have to get the sources from linux-mips.org cvs,
> using the linux_2_4 tag. From
> ftp.linux-mips.org:/pub/linux/mips/people/ppopov/2.4
> get and apply the usb-nonpci-2.4.24.patch and zboot-2.4.25.patch
I'm having problems applying the zboot patch to the latest and greatest
from the linux_2_4 branch ("cvs checkout -r linux_2_4 -D 2004-03-12
linux"). When I try to apply the zboot patch, it rejects the chunk for
'arch/mips/Makefile'. However, upon inspection, I am unable to
determine why it isn't happy with the patch. Any suggestions?
-- Tahoma
Tahoma M. Toelkes
North Shore Circuit Design, L.L.P.
tahoma@nshore.com
next prev parent reply other threads:[~2004-03-12 22:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-12 7:44 Linux Boot Issue in Au1550 xavier prabhu
2004-03-12 15:17 ` Dan Malek
2004-03-12 21:59 ` Tahoma Toelkes [this message]
2004-03-15 17:49 ` zboot patch and linux_2_4 branch [was Re: Linux Boot Issue in Au1550] Pete Popov
2004-03-15 17:54 ` Dan Malek
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=405232DB.5050902@nshore.com \
--to=tahoma@nshore.com \
--cc=dan@embeddededge.com \
--cc=linux-mips@linux-mips.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