From: "Matthias Suthe" <msuthe@mut-group.com>
To: barebox@lists.infradead.org
Subject: Sandbox Segfault
Date: Fri, 15 Jul 2011 09:13:41 +0200 [thread overview]
Message-ID: <D08CBAE0A98EB548B293DA79621E27110425C059@zcom02.mut-group.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1341 bytes --]
Hi,
I'm trying to start barebox is described in the First Steps chapter of
the barebox documentation, but I get a segfault.
I followed the User's Manual step by step and now I try to run
./barebox -e env.bin -i cramfs.bin
Did I maybe miss something when creating the cramfs.bin? Do I need to
put files into somedir?
I'm using barebox-2011.05.0
OS: Debian 6.0.1 (squeeze)
Kernel: Linux 2.6.32-5-686-bigmem
Neither this patch:
--- a/arch/sandbox/board/hostfile.c
+++ b/arch/sandbox/board/hostfile.c
@@ -107,7 +107,8 @@ int barebox_register_filedev(struct hf_platform_data
*hf)
dev->platform_data = hf;
- strcpy(dev->name, "hostfile");
+ /* Registering 2 devices with same name creates problem? */
+ strcpy(dev->name, hf->filename);
dev->size = hf->size;
dev->map_base = hf->map_base;
Nor this patch:
--- a/arch/sandbox/board/hostfile.c
+++ b/arch/sandbox/board/hostfile.c
@@ -109,6 +109,7 @@ int barebox_register_filedev(struct hf_platform_data
*hf)
strcpy(dev->name, "hostfile");
dev->size = hf->size;
+ dev->id = -1;
dev->map_base = hf->map_base;
return register_device(dev);
help.
I would be grateful for any help.
With kind regards
Matthias Suthe
[-- Attachment #1.2: Type: text/html, Size: 6346 bytes --]
[-- Attachment #2: Type: text/plain, Size: 149 bytes --]
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2011-07-15 7:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-15 7:13 Matthias Suthe [this message]
2011-07-15 8:03 ` Sascha Hauer
2011-07-15 8:46 ` Peter Korsgaard
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=D08CBAE0A98EB548B293DA79621E27110425C059@zcom02.mut-group.com \
--to=msuthe@mut-group.com \
--cc=barebox@lists.infradead.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