From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: Michel Stam <michel@reverze.net>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: RFC: barebox-x86 as a coreboot payload
Date: Tue, 8 Apr 2014 14:47:52 +0800 [thread overview]
Message-ID: <7333B557-37B1-4CEF-8084-2AF713055F24@jcrosoft.com> (raw)
In-Reply-To: <A5DB3EAC-DA3A-4BF2-8C21-7C57B5CF9AAE@reverze.net>
[-- Attachment #1.1: Type: text/plain, Size: 1316 bytes --]
On Apr 6, 2014, at 10:32 PM, Michel Stam <michel@reverze.net> wrote:
> Hello Antony,
>
> Interesting idea- I wonder if its difficult given that U-boot is already supported?
>
> Personally I have no experience with coreboot, the systems I test on are industrial x86 SBCs with their own BIOS. I suppose it is oossible, maybe we can borrow code from u-boot.
>
Should be fairly easy
> Another thing along the sane lines that crossed my mind is EFI support for barebox, I wonder if theres interest in that?
EFI yes as ARM will use UEFI too
>
> Next on my list is keyboard/VGA, maybe VESA support if I have the time. I would like to see a console, possibly a framebuffer driver. No idea how difficult that will be.
>
good idea
> Cheers,
>
> Michel Stam
>
>
>> On 5 apr. 2014, at 21:00, Antony Pavlov <antonynpavlov@gmail.com> wrote:
>>
>> Hi!
>>
>> I have seen your recent activity on barebox-x86 improvements.
>>
>> IMHO using barebox-x86 as a coreboot payload can be beneficial for barebox promotion.
>>
>> Please see http://www.coreboot.org/Payloads
>>
>> --
>> Best regards,
>> Antony Pavlov
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
[-- Attachment #1.2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 842 bytes --]
[-- Attachment #2: Type: text/plain, Size: 149 bytes --]
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2014-04-08 6:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-05 19:00 Antony Pavlov
2014-04-05 19:02 ` Alexander Shiyan
2014-04-05 19:27 ` Alexander Aring
2021-04-01 13:52 ` Ahmad Fatoum
2021-04-02 5:23 ` Antony Pavlov
2014-04-08 6:48 ` Jean-Christophe PLAGNIOL-VILLARD
2014-04-08 21:45 ` Marc Kleine-Budde
2014-04-08 21:50 ` [PATCH] 2048: port to barebox Marc Kleine-Budde
2014-04-09 3:27 ` Alexander Aring
2014-04-09 7:20 ` RFC: barebox-x86 as a coreboot payload Sascha Hauer
2014-04-06 14:32 ` Michel Stam
2014-04-08 6:47 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2014-04-10 5:52 ` Sascha Hauer
2014-04-10 11:30 ` Michel Stam
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=7333B557-37B1-4CEF-8084-2AF713055F24@jcrosoft.com \
--to=plagnioj@jcrosoft.com \
--cc=barebox@lists.infradead.org \
--cc=michel@reverze.net \
/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