All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrei Borzenkov <arvidjaar@gmail.com>
To: Josef Bacik <jbacik@fb.com>
Cc: Vladimir 'phcoder' Serbinenko <phcoder@gmail.com>,
	Kernel Team <Kernel-team@fb.com>,
	The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] efinet: check for broken firmware
Date: Sat, 14 Nov 2015 16:11:22 +0300	[thread overview]
Message-ID: <564732FA.5060200@gmail.com> (raw)
In-Reply-To: <D228DF3D-D4D9-4E5C-9372-AD6E963EE29B@fb.com>

14.11.2015 07:08, Josef Bacik пишет:
>
>> On Nov 13, 2015, at 10:19 PM, Andrei Borzenkov <arvidjaar@gmail.com> wrote:
>>
>> 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?
>
> There is a MNP binding and the driver does not work. It sets everything up right but doesn't transmit or receive properly.
>

That's bad. It means even if we prefer MNP we still need to implement 
quirks to avoid it on known broken platforms.

> I figured out why my original approach wasn't working and why it works if I don't switch to exclusive.  I can now switch to exclusive and have things still working, just fixing up the patch now, I'll finish it on Monday and send it out.  Thanks,
>
> Josef
>



  reply	other threads:[~2015-11-14 19:49 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
2015-11-14  4:08           ` Josef Bacik
2015-11-14 13:11             ` Andrei Borzenkov [this message]
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=564732FA.5060200@gmail.com \
    --to=arvidjaar@gmail.com \
    --cc=Kernel-team@fb.com \
    --cc=grub-devel@gnu.org \
    --cc=jbacik@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.