From: Erwin Rol <mailinglists@erwinrol.com>
To: Sascha Hauer <s.hauer@pengutronix.de>, barebox@lists.infradead.org
Subject: Re: Introducing barebOS
Date: Tue, 01 Apr 2014 11:33:41 +0200 [thread overview]
Message-ID: <533A87F5.9080400@erwinrol.com> (raw)
In-Reply-To: <20140401090229.GT17250@pengutronix.de>
You could use a small Linux system with an adapted kexec to boot
barebOS. That way barebOS doesn't have to bother with the boot processes.
- Erwin
On 1-4-2014 11:02, Sascha Hauer wrote:
> Hi All,
>
> barebox more and more comes in the area that is has everything an
> operating system needs:
>
> - support for all kinds of storage devices
> - support for various different fileystems
> - Cooperative multitasking with the poller mechanism
> - memory management in form of malloc/free and iospace resources
> - drivers for Networking, MMC, USB, UARTs, Framebuffer devices, (S)ATA,
> SPI, I2C, W1, Keyboard, EEPROMs, LEDs
>
> I therefore decided that it's no longer necessary to have the overhead
> of Linux at all. The project will be renamed to barebOS in the next few
> days. Support for booting Linux will be dropped as soon as some the
> remaining missing features are added, like for example a working vi
> applet and nodejs integration. I'm looking forward to your feedback!
>
> Sascha
>
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2014-04-01 9:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 9:02 Sascha Hauer
2014-04-01 9:20 ` Alexander Shiyan
2014-04-01 9:23 ` Franck Jullien
2014-04-01 9:35 ` Alessandro Rubini
2014-04-01 9:45 ` Alexander Aring
2014-04-01 15:22 ` Nur Hussein
2014-04-01 16:16 ` Alessandro Rubini
2014-04-01 9:32 ` Alexander Aring
2014-04-01 9:33 ` Erwin Rol [this message]
2014-04-05 2:53 ` Jean-Christophe PLAGNIOL-VILLARD
2014-04-05 5:49 ` Antony Pavlov
2014-04-05 5:52 ` Jean-Christophe PLAGNIOL-VILLARD
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=533A87F5.9080400@erwinrol.com \
--to=mailinglists@erwinrol.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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