From: Paulo Flabiano Smorigo <pfsmorigo@linux.vnet.ibm.com>
To: Andrei Borzenkov <arvidjaar@gmail.com>
Cc: grub-devel@gnu.org, Paulo Flabiano Smorigo <pfsmorigo@br.ibm.com>
Subject: Re: [RFC PATCH 0/3] grub powerpc64 little-endian enablement
Date: Tue, 16 Jun 2015 09:36:45 -0300 [thread overview]
Message-ID: <5580185D.4020902@linux.vnet.ibm.com> (raw)
In-Reply-To: <20150615201508.65201eb9@opensuse.site>
On 2015-06-15 14:15, Andrei Borzenkov wrote:
> В Thu, 28 Aug 2014 16:56:02 -0300
> Paulo Flabiano Smorigo <pfsmorigo@linux.vnet.ibm.com> пишет:
>
>> From: Paulo Flabiano Smorigo <pfsmorigo@br.ibm.com>
>>
>> Hi,
>>
>> At the beginning of the year we provide a patchset that enabled GRUB for
>> little-endian PowerPC. Our approach at the time was to build GRUB itself and
>> its tools in 64-bit little-endian. One of the reasons of build in 64-bit is
>> to avoid 32-bit dependencies in the distro and build a system entirely 64-bit.
>>
>> This patchset was not welcomed at the time because it would bring a
>> high-maintainance-cost, without real gain since it could just be cross-compiled.
>>
>> After that, Brent Baude, Vladmir (phcoder) and I started to work in a solution
>> that would cross-compile but without 32-bit dependencies. This patchset is the
>> result of this new approach. It's based on the work of Brent Baude, Vladimir
>> (phcoder), and Tomohiro.
>>
>> It can be devided in two parts:
>>
>> 1) Skip libgcc dependency just for ppc64el (patch 1 and 2);
>
> This is now default for all platforms
>
>> 2) Check elf endianess and byteswap if necessary (patch 3);
>>
>
> That's still pending.
Yes, I'm aware of that. :)
>
>> The result is GRUB itself in 32-bit BE and its tools in 64-bit LE. This solution
>> satisfies the needs of the distros. I tested it in three different distros, in
>> both endianess and it's fine.
>>
>> If thoses patches were accepted we will have an official solution. Nowadays,
>> distros are taking diffrent approachs. Some of then are using the original
>> solutions and others are using cross-compiler.
>>
>
> Could you resend missing bits rebased to current head?
>
Sure thing. I'll review it once more and send it to the ML later this week.
--
Paulo Flabiano Smorigo
IBM Linux Technology Center
prev parent reply other threads:[~2015-06-16 12:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-28 19:56 [RFC PATCH 0/3] grub powerpc64 little-endian enablement Paulo Flabiano Smorigo
2014-08-28 19:56 ` [RFC PATCH 1/3] Add powerpc little-endian (ppc64le) flags Paulo Flabiano Smorigo
2014-09-17 22:04 ` Paulo Flabiano Smorigo
2014-09-19 13:48 ` Colin Watson
2014-09-21 16:05 ` Vladimir 'φ-coder/phcoder' Serbinenko
2014-08-28 19:56 ` [RFC PATCH 2/3] Files reorganization and include some libgcc fuctions Paulo Flabiano Smorigo
2014-09-08 2:16 ` Colin Watson
2014-09-17 21:43 ` Paulo Flabiano Smorigo
2014-09-19 14:03 ` Colin Watson
2014-09-21 16:07 ` Vladimir 'φ-coder/phcoder' Serbinenko
2014-08-28 19:56 ` [RFC PATCH 3/3] Suport for bi-endianess in elf file Paulo Flabiano Smorigo
2015-06-16 16:44 ` Andrei Borzenkov
2014-09-21 13:58 ` [RFC PATCH 0/3] grub powerpc64 little-endian enablement Andrei Borzenkov
2014-09-21 14:24 ` Andrei Borzenkov
2014-09-25 22:48 ` Paulo Flabiano Smorigo
2014-09-26 15:52 ` Andrei Borzenkov
2014-09-26 18:18 ` Paulo Flabiano Smorigo
2015-06-15 17:15 ` Andrei Borzenkov
2015-06-16 12:36 ` Paulo Flabiano Smorigo [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=5580185D.4020902@linux.vnet.ibm.com \
--to=pfsmorigo@linux.vnet.ibm.com \
--cc=arvidjaar@gmail.com \
--cc=grub-devel@gnu.org \
--cc=pfsmorigo@br.ibm.com \
/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.