From: Andreas Barth <aba@not.so.argh.org>
To: David Daney <ddaney@caviumnetworks.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Problems and workarounds while building octeon kernels
Date: Wed, 24 Feb 2010 00:47:12 +0100 [thread overview]
Message-ID: <20100223234712.GA27216@mails.so.argh.org> (raw)
In-Reply-To: <4B82F610.8070105@caviumnetworks.com>
* David Daney (ddaney@caviumnetworks.com) [100222 22:25]:
> * Were you able to produce a *bootable* kernel after your workarounds?
We couldn't test that, as I don't have direct hardware access.
However file tells me it's the same type as the working kernel:
vmlinux: ELF 64-bit MSB executable, MIPS, MIPS64 rel2 version 1 (SYSV), statically linked, not stripped
As soon as it got tested, I'll tell you.
> * What did your make invocation look like?
"make" and "fakeroot make-kpkg --revision 1 kernel_image".
Cheers,
Andi
prev parent reply other threads:[~2010-02-23 23:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-20 17:51 Problems and workarounds while building octeon kernels Andreas Barth
2010-02-22 17:42 ` David Daney
2010-02-22 20:25 ` Andreas Barth
2010-02-22 20:55 ` David Daney
2010-02-22 21:03 ` Andreas Barth
2010-02-22 21:24 ` David Daney
2010-02-23 23:47 ` Andreas Barth [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=20100223234712.GA27216@mails.so.argh.org \
--to=aba@not.so.argh.org \
--cc=ddaney@caviumnetworks.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