All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: grub-devel@gnu.org
Subject: Re: GRUB port for ARMv7-A U-Boot
Date: Fri, 19 Oct 2012 21:11:41 +0200	[thread overview]
Message-ID: <5081A5ED.1080003@gmail.com> (raw)
In-Reply-To: <5081a0b0.0a4a340a.1cd2.ffffb04aSMTPIN_ADDED@mx.google.com>

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

On 19.10.2012 20:47, Leif Lindholm wrote:

> I have created a port of GRUB to the ARMv7-A architecture, running on top of
> the
> U-Boot firmware. The "U-Boot API", created by Rafal Jaworowsky
> <raj@semihalf.com>, provides the hardware abstraction layer. Console is
> supported on serial port using the termios subsystem.
> 
> This port supports, and indeed relies on, flattened device trees (FDT) -
> passed on from firmware, or loaded from a filesystem. My implementation uses
> libfdt rather than trying to recycle the existing openfirmware code, and if
> possible I would like to keep it that way, and have libfdt included in GRUB.
> 
> libfdt is dual-licensed, GPLv2+/BSD, and the copyright belongs to David
> Gibson <dwg@au1.ibm.com>. I have a patch against the libfdt included in
> http://jdl.com/software/dtc-v1.3.0.tgz that makes it build under GRUB.
> 

I'd prefer rather without libfdt and share more code with openfirmware
since it's similar brain damage.

> The U-Boot API is released under GPLv2+ consists of 3 source files. They are
> licensed under GPLv2+. The port also contains a crc32 checker I included
> from the FreeBSD loader, copyright Gary S. Brown with the statement that
> "You may use this program, or code or tables extracted from it, as desired
> without restriction.". The crc32 checker is not strictly speaking required,
> so could be removed if this poses any problems.
> 

GRUB already has crc32 from libgcrypt. Could you use it?

> In addition to this, the port includes libgcc helper functions (aeabi_*)
> taken from linux/arch/arm/lib, licensed under GPLv2+.
> 

These should be included at compile time from system libgcc.

> My intent is to set up a public repository on launchpad.net containing my
> modifications on Monday.

Could you send the patch here even if it's not finished?

> Do you have any opinions about how I should treat
> the third-party software when I do this?
> 


> Regards,
> 
> Leif
> 
> 
> 
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
> 



-- 
Regards
Vladimir 'φ-coder/phcoder' Serbinenko


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]

       reply	other threads:[~2012-10-19 19:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5081a0b0.0a4a340a.1cd2.ffffb04aSMTPIN_ADDED@mx.google.com>
2012-10-19 19:11 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2012-10-22 11:16   ` GRUB port for ARMv7-A U-Boot Leif Lindholm
     [not found] <5081a0af.21b4340a.1059.ffffb383SMTPIN_ADDED@mx.google.com>
2012-10-19 19:08 ` Adam Hunston
2012-10-19 19:15   ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-10-19 19:49     ` Adam Hunston
2012-10-19 19:54       ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-10-19 18:47 Leif Lindholm

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=5081A5ED.1080003@gmail.com \
    --to=phcoder@gmail.com \
    --cc=grub-devel@gnu.org \
    /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.