From: "Bruno R. Barreyra" <bruno.r.barreyra@intel.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: make dep bug and patches
Date: Thu, 08 Mar 2001 11:08:25 -0800 [thread overview]
Message-ID: <3AA7D8A9.92476309@intel.com> (raw)
On today's linuxppc_2_4 snapshot, doing a make dep having selected
a 8xx CPU will bomb because of an include. On arch/ppc/Makefile,
line 34, the -I../8xx_io argument should be removed. It compiles
fine without it.
Also, I was wondering if two patches would be accepted to go in
the main trunk:
1 - reactivate FADS support : I've re-hacked FADS support on my
local tree and it works fine. Actually, I was having some problems
with the kernel available on Area51 from Montavista, and doing
this kernel upgrade fixed it.
2 - having an option to automatically set up the headers for PPCBoot.
I'm sure a lot of folks would appreciate this, and it wouldn't be
hard to automatically generate a PPCBoot image.
If I know the patches will be included, I'll most gladly write them and
send them.
--
[]'s Bruno Renato Barreyra
bruno.r.barreyra@ufl.edu
barreyra@ufl.edu
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
reply other threads:[~2001-03-08 19:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3AA7D8A9.92476309@intel.com \
--to=bruno.r.barreyra@intel.com \
--cc=linuxppc-embedded@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).