From: Andrei Borzenkov <arvidjaar@gmail.com>
To: Josef Bacik <jbacik@fb.com>,
Vladimir 'phcoder' Serbinenko <phcoder@gmail.com>,
The development of GRUB 2 <grub-devel@gnu.org>
Cc: kernel-team@fb.com
Subject: Re: [PATCH] efinet: check for broken firmware
Date: Sat, 14 Nov 2015 06:19:11 +0300 [thread overview]
Message-ID: <5646A82F.3060503@gmail.com> (raw)
In-Reply-To: <56463B5E.7000600@fb.com>
13.11.2015 22:34, Josef Bacik пишет:
> On 11/13/2015 09:38 AM, Vladimir 'phcoder' Serbinenko wrote:
>> Please try the patch currently used in Solaris flavour of GRUB. I think
>> of upstreaming their mnp driver
>
> This driver doesn't work at all for me. I may have done a bad job
> porting it, or the firmware is even crappier with MNP, either way it's
> completely unusable. I'll fix up this patch and send it along. Thanks,
>
So that I understand. You have a system where a) there is MNP Binding
Protocol on network device and b) this does not work? Or your system
does not offer MNP Binding Protocol for device?
next prev parent reply other threads:[~2015-11-14 3:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 22:07 [PATCH] efinet: check for broken firmware Josef Bacik
2015-11-13 13:10 ` Andrei Borzenkov
2015-11-13 14:30 ` Josef Bacik
2015-11-13 14:38 ` Vladimir 'phcoder' Serbinenko
2015-11-13 14:39 ` Andrei Borzenkov
2015-11-13 15:52 ` Josef Bacik
2015-11-13 16:34 ` Andrei Borzenkov
2015-11-13 19:34 ` Josef Bacik
2015-11-14 3:19 ` Andrei Borzenkov [this message]
2015-11-14 4:08 ` Josef Bacik
2015-11-14 13:11 ` Andrei Borzenkov
2015-11-14 14:13 ` Vladimir 'phcoder' Serbinenko
2015-11-16 15:42 ` Josef Bacik
2015-11-13 14:38 ` Andrei Borzenkov
2015-11-13 15:01 ` Josef Bacik
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=5646A82F.3060503@gmail.com \
--to=arvidjaar@gmail.com \
--cc=grub-devel@gnu.org \
--cc=jbacik@fb.com \
--cc=kernel-team@fb.com \
--cc=phcoder@gmail.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 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.