public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-boot] Uboot's plan for ARMv8
Date: Fri, 10 Jan 2014 07:08:24 +0100	[thread overview]
Message-ID: <20140110060824.2CA263803F9@gemini.denx.de> (raw)
In-Reply-To: <CANiE1qoyXV10iDghK=qK9=Wjb2yueWC7U2MTRt-sSUyY5QiSJQ@mail.gmail.com>

Dear Abraham,

In message <CANiE1qoyXV10iDghK=qK9=Wjb2yueWC7U2MTRt-sSUyY5QiSJQ@mail.gmail.com> you wrote:
> 
> u-boot is an open source bootloader. It isn't run by a single
> organization (though it IS headed by denx). Architecturally the
> software can be divided into multiple processor and development
> boards.
> 
> Now, if organization A is developing a new processor (along with
> development board) and they want to use u-boot as the bootloader, they
> would need to write the necessary /cpu sections by themselves and post
> it as a patch to the u-boot mailing list. Assuming it meets the coding

This is not strictly correct.  Anybody interested in support for some
piece of hardware can implement it and submit the patches - this is
not necessarily the vendor of the chip or the board.  So if Tiger Liu
is interested in support for some specific ARMv8 hardware, he could
implement it himself, or hire some external experts to implement it
for him - or wait until some other member of the community submits
patches.

> Looking it at from another perspective, it is rather arrogant (and
> rude) of organization-A to build a brand new processor, come in here
> and expect u-boot to magically support it. Most people don't work for
> free. And even if they wanted to, since the rest of the mailing list
> does not have physical access to the new processor/board, how much
> help can you _reasonably_ expect?

Correct.  Some hardware vendors actively support the community, for
example by providing free eval boards to active community members, and
especially by providing full documentation for their hardware.  Others
don't.  You can see this pretty easily by the level of support for
such hardware in mainline U-Boot.  For example, look around how much
support for Qualcomm chips we have in mainline, just to name one.


In general the old rule applies: Scratch where it itches.  If I don't
have free access to such hardware, and if no (paying( customer asks me
to do it, I see little reason to spend time and efforts for some
specific new piece of hardware - there are so many of them...

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
A committee is a group that keeps the minutes and loses hours.
                                                      -- Milton Berle

  reply	other threads:[~2014-01-10  6:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-10  3:02 [U-Boot] [U-boot] Uboot's plan for ARMv8 TigerLiu at viatech.com.cn
2014-01-10  4:54 ` Abraham Varricatt
2014-01-10  6:08   ` Wolfgang Denk [this message]
2014-01-10  6:09 ` bhupesh.sharma at freescale.com
2014-01-10  6:54   ` TigerLiu at viatech.com.cn
2014-01-10  7:29     ` bhupesh.sharma at freescale.com
2014-01-10  8:02       ` bhupesh.sharma at freescale.com
2014-01-10 14:15 ` 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=20140110060824.2CA263803F9@gemini.denx.de \
    --to=wd@denx.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox