Netdev List
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Giri Reddy <giri.reddy@qlogic.com>
Cc: David Miller <davem@davemloft.net>, netdev <netdev@vger.kernel.org>
Subject: Re: Use of 'SIOCDEVPRIVATE' in ethernet drivers.
Date: Tue, 7 Jan 2014 15:44:56 -0800	[thread overview]
Message-ID: <20140107154456.7e5af377@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <124064C45E1FC84193A69A61ED3A1F46E230D6@AVMB1.qlogic.org>

On Tue, 7 Jan 2014 22:22:45 +0000
Giri Reddy <giri.reddy@qlogic.com> wrote:

> On 1/7/14 11:05 AM, David Miller wrote:
> > From: Giri Reddy <giri.reddy@qlogic.com>
> > Date: Tue, 7 Jan 2014 18:21:17 +0000
> >
> >> Are we still allowed to use 'SIOCDEVPRIVATE' in drivers if there the
> >> deprecation efforts are on hold.
> > To say that use of SIOCDEVPRIVATE is discouraged would be an
> > understatement.
> >
> > Please create a generic ethtool based facility that other drivers in
> > similar situations can use as well.
> 
> Thanks for the input. I will explore the 'ethtool' option. We will have
> multiple control frames exchanged between user space and kernel for
> every flash update operation, most of this will be proprietary stuff
> that will get exchanged - I will explore how to provide a generic
> interface for that.
> 
> Giri

Maybe a debugfs or sysfs filesystem would work better than adding ioctl';s

  reply	other threads:[~2014-01-07 23:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-07 18:21 Use of 'SIOCDEVPRIVATE' in ethernet drivers Giri Reddy
2014-01-07 19:05 ` David Miller
2014-01-07 22:22   ` Giri Reddy
2014-01-07 23:44     ` Stephen Hemminger [this message]
2014-01-08 16:02       ` Giri Reddy
2014-01-09 21:09         ` Ben Hutchings
2014-01-10  3:45           ` Giri Reddy
2014-01-09 21:07 ` Ben Hutchings

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=20140107154456.7e5af377@nehalam.linuxnetplumber.net \
    --to=stephen@networkplumber.org \
    --cc=davem@davemloft.net \
    --cc=giri.reddy@qlogic.com \
    --cc=netdev@vger.kernel.org \
    /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