From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [EXT] Re: Cavium/Marvell Octeon Support
Date: Tue, 5 Nov 2019 09:15:16 -0500 [thread overview]
Message-ID: <20191105141516.GC4181@bill-the-cat> (raw)
In-Reply-To: <1838672.aZrPjDvGh8@flash>
On Tue, Nov 05, 2019 at 02:08:54AM +0000, Aaron Williams wrote:
> On Monday, November 4, 2019 8:23:08 AM PST Tom Rini wrote:
> > On Mon, Nov 04, 2019 at 04:44:18PM +0100, Wolfgang Denk wrote:
> > > Dear Aaron,
> > >
> > > In message <2710076.TiSPtmOvtb@flash> you wrote:
> > > > > What exactly do you need this for? Why don't you just link your
> > > > > code with the rest of U-Boot?
> > > >
> > > > We need it to obtain and modify the phy parameters. This is a custom 25G
> > > > gearbox that needs a lot of hand holding. This may end up being a low
> > > > priority (not the gearbox, but the API). It's only a few hundred lines
> > > > of code (the API).
> > >
> > > Again you don't answer my question. Why do you need a special new
> > > API for such code? Why do you not just link that code with the rest
> > > of U-Boot?
> > >
> > > It has been mentioned before, but just to be sure: this code which
> > > uses your new API is licensed under a GPLv2 conforming lincense?
> >
> > And, to be blunt, if it is not, handling your non-GPLv2 applications
> > via an EFI binary is the way forward, not extending the U-Boot binary
> > ABI, in my opinion.
>
> To be blunt, the current U-Boot EFI driver does not provide the required
> functionality. It would need to be extended in order to work. In addition,
> spinlocks would be required in order to handle the case of reentrancy. Also,
> how does the EFI loader deal with loading multiple applications across
> multiple cores? The block support is the least important part of it. There are
> several other services not related to block devices or network calls.
If there are parts of the EFI specification that we do not implement,
but could implement, it would be a much appreciated contribution to the
code. If once you're up in the EFI world there are things you cannot do
that you need to do, that should be taken up with the UEFI consortium.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20191105/2898357d/attachment.sig>
next prev parent reply other threads:[~2019-11-05 14:15 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 3:50 [U-Boot] Cavium/Marvell Octeon Support Aaron Williams
2019-10-24 6:44 ` Chris Packham
2019-10-25 15:13 ` Daniel Schwierzeck
2019-10-26 22:15 ` Tom Rini
2019-10-27 3:08 ` [U-Boot] [EXT] " Aaron Williams
2019-10-27 2:34 ` Aaron Williams
2019-10-29 13:12 ` Wolfgang Denk
2019-10-30 16:20 ` Daniel Schwierzeck
2019-10-30 17:21 ` Wolfgang Denk
2019-10-30 21:23 ` Aaron Williams
2019-10-31 10:36 ` Wolfgang Denk
2019-10-31 17:59 ` Aaron Williams
2019-11-04 15:44 ` Wolfgang Denk
2019-11-04 16:23 ` Tom Rini
2019-11-05 2:08 ` Aaron Williams
2019-11-05 8:37 ` Wolfgang Denk
2019-11-05 10:22 ` Aaron Williams
2019-11-05 11:36 ` Wolfgang Denk
2019-11-05 23:09 ` Aaron Williams
2019-11-06 15:06 ` Wolfgang Denk
2019-11-06 22:18 ` Aaron Williams
2019-11-07 0:21 ` Tom Rini
2019-11-05 14:15 ` Tom Rini [this message]
2019-11-05 1:57 ` Aaron Williams
2019-11-05 8:33 ` Wolfgang Denk
2019-11-05 14:16 ` Tom Rini
2019-10-30 22:05 ` [U-Boot] " Tom Rini
2019-10-30 23:36 ` [U-Boot] [EXT] " Aaron Williams
2019-10-31 10:40 ` Wolfgang Denk
2019-10-31 18:01 ` Aaron Williams
2019-11-04 17:22 ` Tom Rini
2019-11-05 2:13 ` Aaron Williams
2019-11-05 14:09 ` Tom Rini
2019-10-31 13:26 ` Tom Rini
2019-10-31 18:04 ` Aaron Williams
-- strict thread matches above, loose matches on Subject: below --
2019-11-06 0:03 Aaron Williams
2019-11-07 0:34 ` 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=20191105141516.GC4181@bill-the-cat \
--to=trini@konsulko.com \
--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