public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Marcelo Ricardo Leitner <mleitner@redhat•com>
To: Or Gerlitz <or.gerlitz@gmail•com>
Cc: Yevgeny Petrilin <yevgenyp@mellanox•co.il>,
	netdev <netdev@vger•kernel.org>,
	Or Gerlitz <ogerlitz@mellanox•com>,
	Doug Ledford <dledford@redhat•com>,
	Yishai Hadas <yishaih@dev•mellanox.co.il>
Subject: Re: Question about Mellanox FW reporting (incorrect) port types
Date: Wed, 17 Oct 2012 16:49:41 -0300	[thread overview]
Message-ID: <507F0BD5.7080005@redhat.com> (raw)
In-Reply-To: <CAJZOPZ+T7paqVe12n+sBw4ra8AEWCZ+W2GZ52iJY=9Hrgoxuaw@mail.gmail.com>

On 10/17/2012 04:22 PM, Or Gerlitz wrote:
> Marcelo Ricardo Leitner <mleitner@redhat•com> wrote:
>>
>> [...] So my questions are: is it possible to the firmware report a wrong port type like
>> that? Is it somehow configurable by sysadmin (via fw update, ..), can we flip that byte
>> or is it a manufacturing issue?
>
>
> I'm not sure, Yevgeny/Yishai do you have any insights here?
>
>> I can't try upstream driver
>
> why?! netdev is dealing with upstream, isn't it?

Yes, it is. By upstream I actually mean a non-RHEL kernel/driver. I 
tried but so far couldn't reproduce this issue in-house, sorry. My ports 
always answer ETH :) So I have to ask for customer to test and then 
unfortunately things get complicated..

Thanks,
Marcelo

  reply	other threads:[~2012-10-17 19:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-17 16:27 Question about Mellanox FW reporting (incorrect) port types Marcelo Ricardo Leitner
2012-10-17 19:22 ` Or Gerlitz
2012-10-17 19:49   ` Marcelo Ricardo Leitner [this message]
2012-11-09 20:37     ` Marcelo Ricardo Leitner

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=507F0BD5.7080005@redhat.com \
    --to=mleitner@redhat$(echo .)com \
    --cc=dledford@redhat$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=ogerlitz@mellanox$(echo .)com \
    --cc=or.gerlitz@gmail$(echo .)com \
    --cc=yevgenyp@mellanox$(echo .)co.il \
    --cc=yishaih@dev$(echo .)mellanox.co.il \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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