grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: Andrei Borzenkov <arvidjaar@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Cc: Paulo Flabiano Smorigo <pfsmorigo@br.ibm.com>,
	pfsmorigo@linux.vnet.ibm.com
Subject: Re: [RFC PATCH 0/3] grub powerpc64 little-endian enablement
Date: Sun, 21 Sep 2014 17:58:44 +0400	[thread overview]
Message-ID: <20140921175844.359e7927@opensuse.site> (raw)
In-Reply-To: <1409255765-3209-1-git-send-email-pfsmorigo@linux.vnet.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 1981 bytes --]

В 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);
>   2) Check elf endianess and byteswap if necessary (patch 3);
> 
> 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.
> 

Unfortunately I'm still not able to boot this version on QEMU. I build
on openSUSE for three acrhs - ppc, ppc64, ppc64le. First two are OK and
boot successfully. Third one does not work - it ends up in exception. I
get initial GRUB greeting and that's all.

Same problem I got with Vladimir libgcc patch series.

It could be toolkit issue of course; but still it would need fixing
before we can merge it.

Could you help in debugging this issue? I have near to zero experience
with PPC; I can do what you tell me, but not much more.

I run it with

qemu-system-ppc64 -M pseries -cdrom /tmp/grub2-ppc64le.iso -boot d

Attached is screenshot of error.



[-- Attachment #2: QEMU_022.png --]
[-- Type: image/x-apple-ios-png, Size: 9292 bytes --]

  parent reply	other threads:[~2014-09-21 13:59 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 ` Andrei Borzenkov [this message]
2014-09-21 14:24   ` [RFC PATCH 0/3] grub powerpc64 little-endian enablement 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

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=20140921175844.359e7927@opensuse.site \
    --to=arvidjaar@gmail.com \
    --cc=grub-devel@gnu.org \
    --cc=pfsmorigo@br.ibm.com \
    --cc=pfsmorigo@linux.vnet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).