From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: Michael Olbrich <m.olbrich@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 0/12] EFI: drop arch efi
Date: Mon, 13 Mar 2017 18:48:47 +0800 [thread overview]
Message-ID: <8178DF2B-A885-4B8B-9C64-15A9CA93D607@jcrosoft.com> (raw)
In-Reply-To: <20170313102755.fddlbzorzczkdshk@pengutronix.de>
> On 13 Mar 2017, at 6:27 PM, Michael Olbrich <m.olbrich@pengutronix.de> wrote:
>
> On Sun, Mar 12, 2017 at 01:05:38PM +0100, Jean-Christophe PLAGNIOL-VILLARD wrote:
>> On 17:26 Sat 11 Mar , Michael Olbrich wrote:
>>> On Wed, Feb 15, 2017 at 08:29:32PM +0100, Jean-Christophe PLAGNIOL-VILLARD wrote:
>>>> Today the EFI is build as an other ARCH when in fact it's just a boot mode
>>>>
>>>> so move it back to arch/x86 for the spicific x86 part and the common
>>>> to common and driver
>>>>
>>>> The last 3 patches allow to debug EFI and prepare for more efi support
>>>>
>>>> The following changes since commit b225bbf295c92263adbcec2c385c5e8d83542c72:
>>>>
>>>> i.MX: esdhc: fix imx-esdhc driver for non-OF boards (2017-02-14 08:48:34 +0100)
>>>>
>>>> are available in the git repository at:
>>>>
>>>> git://git.jcrosoft.org/barebox.git
>>>>
>>>> for you to fetch changes up to df12536f83b485c9a4ee28f78637356c6abab6f6:
>>>>
>>>> efi: add efi handle dump command (2017-02-15 07:32:24 +0800)
>>>
>>> While testing the serial stuff I noticed that the
>>> CONFIG_ARCH_EFI_REGISTER_COM1 option got lost during this rework.
>> I did not merge it as it's a hack more than a feature as this by pass the EFI
>> API and access the hw directly instead of using Serial IO
>>
>> Which was add after
>>
>> And I plan to drop this hack
>
> You cannot assume a sane EFI. I have a hardware with a serial port that
> works just fine with the ns16550 driver but the EFI does not implement the
> serial IO protocol. So this hack is still needed in some way.
>
I agree with you on that EFI implementation are erradict at best.
> Maybe we could register the ns16550 console if no efi serial IO protocol is
> found?
I’d prefer we use a DT to add more device at build time or runtime that hack in the
general code.
Or Create a specific board code for you hardware
So we keep the generic code as generic as possible
Best Regards,
J.
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2017-03-13 10:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 19:29 Jean-Christophe PLAGNIOL-VILLARD
2017-02-15 19:34 ` [PATCH 01/12] efi: move block io driver to driver/block Jean-Christophe PLAGNIOL-VILLARD
2017-02-15 19:34 ` [PATCH 02/12] efi: move clocksource out of arch Jean-Christophe PLAGNIOL-VILLARD
2017-02-15 19:34 ` [PATCH 03/12] efi: move bus driver to driver/efi Jean-Christophe PLAGNIOL-VILLARD
2017-02-15 19:34 ` [PATCH 04/12] efi: move debug_ll.h to include/efi Jean-Christophe PLAGNIOL-VILLARD
2017-02-15 19:34 ` [PATCH 05/12] efi: move startup and payload to common/efi Jean-Christophe PLAGNIOL-VILLARD
2017-02-15 19:34 ` [PATCH 06/12] x86: move bios bootup code to arch/x86/bios Jean-Christophe PLAGNIOL-VILLARD
2017-02-15 19:34 ` [PATCH 07/12] efi: move x86 efi boot support to x86 arch Jean-Christophe PLAGNIOL-VILLARD
2017-02-16 7:27 ` Michael Olbrich
2017-02-23 11:39 ` Jean-Christophe PLAGNIOL-VILLARD
2017-02-27 7:50 ` Sascha Hauer
2017-03-07 8:31 ` [PATCH] fixup! " Michael Olbrich
2017-03-09 6:37 ` Sascha Hauer
2017-02-15 19:34 ` [PATCH 08/12] ARCH: efi: Finally drop it as now we can build efi bootup from x86 Jean-Christophe PLAGNIOL-VILLARD
2017-02-15 19:34 ` [PATCH 09/12] efi: bus: add firmware vendor and resision and tables info Jean-Christophe PLAGNIOL-VILLARD
2017-02-16 7:38 ` [PATCH 0/12] EFI: drop arch efi Michael Olbrich
2017-02-16 7:42 ` Michael Olbrich
2017-02-20 3:10 ` [PATCH 10/12] efi: add minor and major to the bus and display it at boot Jean-Christophe PLAGNIOL-VILLARD
2017-02-20 3:10 ` [PATCH 11/12] efi-gui: add Timestamp Protocol GUID definition Jean-Christophe PLAGNIOL-VILLARD
2017-02-20 3:10 ` [PATCH 12/12] efi: add efi handle dump command Jean-Christophe PLAGNIOL-VILLARD
2017-03-11 16:26 ` [PATCH 0/12] EFI: drop arch efi Michael Olbrich
2017-03-12 12:05 ` Jean-Christophe PLAGNIOL-VILLARD
2017-03-13 10:27 ` Michael Olbrich
2017-03-13 10:48 ` Jean-Christophe PLAGNIOL-VILLARD [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=8178DF2B-A885-4B8B-9C64-15A9CA93D607@jcrosoft.com \
--to=plagnioj@jcrosoft.com \
--cc=barebox@lists.infradead.org \
--cc=m.olbrich@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