All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josef Bacik <jbacik@fb.com>
To: Andrei Borzenkov <arvidjaar@gmail.com>
Cc: The development of GNU GRUB <grub-devel@gnu.org>, kernel-team@fb.com
Subject: Re: [PATCH] efinet: check for broken firmware
Date: Fri, 13 Nov 2015 10:01:50 -0500	[thread overview]
Message-ID: <5645FB5E.9040804@fb.com> (raw)
In-Reply-To: <CAA91j0XzU6MfSXb-6=C7Z3tS=fJwChFXhUWM1+=+wfYvqtRZVg@mail.gmail.com>

On 11/13/2015 09:38 AM, Andrei Borzenkov wrote:
> On Fri, Nov 13, 2015 at 5:30 PM, Josef Bacik <jbacik@fb.com> wrote:
>>>> @@ -291,6 +286,9 @@ grub_efinet_findcards (void)
>>>>                                       0, &num_handles);
>>>>      if (! handles)
>>>>        return;
>>>> +
>>>> +  attributes = grub_snp_attributes();
>>>> +
>>>>      for (handle = handles; num_handles--; handle++)
>>>>        {
>>>>          grub_efi_simple_network_t *net;
>>>> @@ -319,8 +317,7 @@ grub_efinet_findcards (void)
>>>>             && GRUB_EFI_DEVICE_PATH_SUBTYPE (parent) ==
>>>> GRUB_EFI_MAC_ADDRESS_DEVICE_PATH_SUBTYPE)
>>>>           continue;
>>>>
>>>> -      net = grub_efi_open_protocol (*handle, &net_io_guid,
>>>> -                                   GRUB_EFI_OPEN_PROTOCOL_GET_PROTOCOL);
>>>> +      net = grub_efi_open_protocol (*handle, &net_io_guid, attributes);
>>>
>>>
>>> No, we cannot open exclusively here, it will destroy autocnfiguration
>>> information we need later. You need to add conditional in open_card.
>>
>>
>> The autoconfig stuff still works later for me but I can change it back.
>
> Thaty would mean your firmware probably is SNP based and not MNP
> based. But it will definitely break autoconfig for others - was there,
> done that :)
>

Fair enough, looks like this firmware is 2.3.1 so theoretically has MNP, 
I'll try and track down this solaris mnp driver and see if I can get it 
to work.  Thanks,

Josef


      reply	other threads:[~2015-11-13 15:02 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
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 [this message]

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=5645FB5E.9040804@fb.com \
    --to=jbacik@fb.com \
    --cc=arvidjaar@gmail.com \
    --cc=grub-devel@gnu.org \
    --cc=kernel-team@fb.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.