From: robert.jarzmik@free.fr
To: barebox@lists.infradead.org
Subject: Envfs embedded in barebox.bin
Date: Thu, 17 Nov 2011 16:05:19 +0100 (CET) [thread overview]
Message-ID: <6cf41d5b-a894-46f5-90e3-23f2b615b104@zimbra1-e1.priv.proxad.net> (raw)
In-Reply-To: <15dd21bf-86c1-4ca8-a830-caef28d617ee@zimbra1-e1.priv.proxad.net>
Hi,
I'm working on a very specific board, where I lack :
- a serial console (all UARTs are wired to GSM/Bluetooth/GPS chips)
- a JTAG adapter
- internal MTD access (I have not ported the MTD driver from linux kernel yet)
- a USB ethernet / console access (put I didn't port the pxa27x_udc yet)
What I have is :
- a smartphone screen (framebuffer of PXA270)
I launch barebox.bin using a tool which does it well : disable MMU, flush cache, copy barebox.bin to start of RAM, and transfer control to it.
My issue is that while I'm developping my board code, I have no feedback (because no console available).
I'd like to run some hush scripts, and the only available way (so far) is to embed the envfs into barebox.bin.
What I'm attempting is basically to :
(1) ld -b binary barebox_default_env -o barebox_default_env.o
(2) add barebox_default_env.o in Makefile, target barebox-common
(3) add in my board code (board.c) the creation of env0 device:
devfs_add_partition("ram0", _binary_barebox_default_env_start,
_binary_barebox_default_env_size,
PARTITION_FIXED, "env0")
I'm feeling like reinventing the wheel there. Have I missed another clean way of including my board default envfs into barebox.bin ?
Of course, that will only last until I port the correct drivers to have access to my MTD ...
Cheers.
--
Robert
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next parent reply other threads:[~2011-11-17 15:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <15dd21bf-86c1-4ca8-a830-caef28d617ee@zimbra1-e1.priv.proxad.net>
2011-11-17 15:05 ` robert.jarzmik [this message]
2011-11-17 15:49 ` Sascha Hauer
2011-11-17 16:02 ` robert.jarzmik
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=6cf41d5b-a894-46f5-90e3-23f2b615b104@zimbra1-e1.priv.proxad.net \
--to=robert.jarzmik@free.fr \
--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