From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] biosemu: include <asm/io.h> header
Date: Tue, 2 Apr 2013 12:32:40 +0200 [thread overview]
Message-ID: <20130402123240.7ba96cd9@lilith> (raw)
In-Reply-To: <CACRpkdYREoPSGDQNZxoT-yL-Mxvf8aPJUE8uvd48s0qazhhVkQ@mail.gmail.com>
Hi Linus,
On Tue, 2 Apr 2013 12:09:21 +0200, Linus Walleij
<linus.walleij@linaro.org> wrote:
> On Tue, Apr 2, 2013 at 10:56 AM, Albert ARIBAUD
> <albert.u.boot@aribaud.net> wrote:
>
> > NAK -- no ARM target needs bios emulation, so basing the #define on ARM
> > requirements is incorrect.
> >
> > Actually, ARM targets build drivers/bios_emulator/libatibiosemu.o as
> > the result of an overlook in ./Makefile where this object is compiled
> > unconditionally.
> >
> > A git grep CONFIG_BIOSEMU seems to indicate only a handful of PowerPC
> > targets need bios emulation; I suggest doing a V2 of this patch
> > where the object is built only for PowerPC, and the #define is removed.
>
> So the patch was initiated by the discussion here:
> http://marc.info/?l=linux-arm-kernel&m=136399798826572&w=2
>
> I am looking into getting biosemu up on ARM for the PCI-equipped
> ARM boards, but admittedly I have no idea where it'll go.
>
> But this can surely wait until I have a series that can be run as well.
Indeed: when some real ARM target needs biosemu, then yes, this patch
will make sense as part of the series that introduces this target.
> Yours,
> Linus Walleij
Amicalement,
--
Albert.
next prev parent reply other threads:[~2013-04-02 10:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 8:14 [U-Boot] [PATCH] biosemu: include <asm/io.h> header Linus Walleij
2013-04-02 8:56 ` Albert ARIBAUD
2013-04-02 10:09 ` Linus Walleij
2013-04-02 10:32 ` Albert ARIBAUD [this message]
2013-04-03 16:02 ` Tom Rini
2013-04-03 17:07 ` Linus Walleij
2013-04-03 22:05 ` Tom Rini
2013-04-04 5:59 ` Linus Walleij
2013-04-04 20:14 ` Tom Rini
2013-04-03 15:30 ` [U-Boot] " Tom Rini
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=20130402123240.7ba96cd9@lilith \
--to=albert.u.boot@aribaud.net \
--cc=u-boot@lists.denx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.