From: Laszlo Ersek <lersek@redhat.com>
To: HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>
Cc: grub-devel@gnu.org, arvidjaar@gmail.com, daniel.kiper@oracle.com,
glin@suse.com, seth.goldberg@oracle.com,
Mark Salter <msalter@redhat.com>,
edk2-devel-01 <edk2-devel@ml01.01.org>
Subject: Re: [grub PATCH] efinet: disable MNP background polling
Date: Wed, 14 Oct 2015 00:23:03 +0200 [thread overview]
Message-ID: <561D8447.4040709@redhat.com> (raw)
In-Reply-To: <20151013221106.GA6558@router-fw-old.local.net-space.pl>
On 10/14/15 00:11, Daniel Kiper wrote:
> On Thu, Oct 01, 2015 at 08:53:44PM +0300, Andrei Borzenkov wrote:
>> 01.10.2015 14:50, Laszlo Ersek ??????????:
>>> - assuming it is "ethernet packet", look for MNPSB first, and if it's
>>> there, call it to get a private-use MNP instance, in order to transmit
>>> and receive,
>>> - if MNPSB is not there, open SNP in exclusive mode, same as now.
>>>
>>> Or else,
>>> - stick with the current exclusive SNP reopen, but make sure that all
>>> aspects are reconfigured from the ground up.
>>>
>>
>> I completely agree; the tiny insignificant missing piece here is actual
>> code :) Of course it also means new can of worms and new unknown
>> firmware bugs ...
>>
>> Hatayama-san, would you consider implementing MNP-based driver for GRUB?
>> Having at least proof of concept available for testing would be good.
>
> Are we sure that we want to migrate to MNP? As I saw others (e.g. PXELINUX,
> iPXE) use SNP and it work for them.
Hatayama-san, can you perhaps test PXELINUX and iPXE on those machines
where the current grub code exposes problems?
Thank you,
Laszlo
>
> If yes then I can post my unfinished rebase work for Solaris GRUB2 MNP patches.
> I did that for our internal needs, however, I did not finish it because usptream
> GRUB2 solved our problems. Well, patches are very raw, based on very old GRUB2
> (Apr 2012) and do not build. However, maybe they could be a good starting point
> for further work.
>
> Daniel
>
next prev parent reply other threads:[~2015-10-13 22:24 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 9:26 [PATCH] efinet: disable MNP background polling HATAYAMA Daisuke
2015-10-01 11:50 ` [grub PATCH] " Laszlo Ersek
2015-10-01 17:53 ` Andrei Borzenkov
2015-10-01 22:04 ` Yinghai Lu
2015-10-02 3:48 ` Andrei Borzenkov
2015-10-09 10:15 ` HATAYAMA Daisuke
2015-10-13 22:11 ` Daniel Kiper
2015-10-13 22:23 ` Laszlo Ersek [this message]
2015-10-14 1:01 ` Yinghai Lu
2015-10-14 7:00 ` Andrei Borzenkov
2015-10-09 10:10 ` HATAYAMA Daisuke
2015-10-09 11:19 ` Laszlo Ersek
2015-10-13 21:49 ` Daniel Kiper
2015-10-13 22:21 ` Laszlo Ersek
2015-10-13 22:56 ` Daniel Kiper
2015-10-14 0:43 ` Seth Goldberg
2015-10-14 5:19 ` [edk2] " Ye, Ting
2015-10-14 5:57 ` Andrei Borzenkov
2015-10-14 6:15 ` Ye, Ting
2015-10-14 6:58 ` Andrei Borzenkov
2015-10-14 8:00 ` Ye, Ting
2015-10-14 17:52 ` Andrei Borzenkov
2015-10-14 11:08 ` Daniel Kiper
2015-10-14 15:39 ` Seth Goldberg
2015-10-15 2:11 ` Ye, Ting
2015-10-15 18:14 ` Laszlo Ersek
2015-10-15 22:33 ` Andrew Fish
2015-10-15 22:57 ` Michael Brown
2015-10-15 23:38 ` Laszlo Ersek
2015-10-29 14:47 ` Vladimir 'φ-coder/phcoder' Serbinenko
2015-10-01 17:40 ` [PATCH] " Andrei Borzenkov
2015-10-09 10:30 ` HATAYAMA Daisuke
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=561D8447.4040709@redhat.com \
--to=lersek@redhat.com \
--cc=arvidjaar@gmail.com \
--cc=d.hatayama@jp.fujitsu.com \
--cc=daniel.kiper@oracle.com \
--cc=edk2-devel@ml01.01.org \
--cc=glin@suse.com \
--cc=grub-devel@gnu.org \
--cc=msalter@redhat.com \
--cc=seth.goldberg@oracle.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).