From: Ben Hutchings <bhutchings@solarflare.com>
To: Guo-Fu Tseng <cooldavid@cooldavid.org>
Cc: Jeff Garzik <jgarzik@pobox.com>, Ethan <ethanhsiao@jmicron.com>,
akeemting <akeem@jmicron.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH netdev-2.6] jme: JMicron Gigabit Ethernet Driver
Date: Mon, 25 Aug 2008 17:21:26 +0100 [thread overview]
Message-ID: <20080825162125.GU7908@solarflare.com> (raw)
In-Reply-To: <48B03522.9020604@cooldavid.org>
Guo-Fu Tseng wrote:
> Jeff Garzik wrote:
[...]
> >* we prefer not to add custom ioctls, but rather add functionality to
> >ethtool. in particular, JMESPIIOCTL does not appear to have any
> >security checks, and is a potential security hole that permits an
> >unpriveleged user direct access to hardware
> >
>
> Should I add privilege check, or should(could?) I send a patch that add
> ethtool interface for flash(For storing PXE code) read/write?
Flash devices are normally handled by MTD drivers. However an MTD
driver that works through a network controller will normally need to
coordinate with the network driver. We have an MTD driver for exactly
the purpose of updating boot code, but the coordinating mechanism
("driverlink") has not been accepted in-tree.
I think we would be happy to implement an ethtool API for flash
memory if this was agreed to be the right interface. It just seems
like it would be duplicating the MTD API.
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2008-08-25 16:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-23 6:05 [PATCH netdev-2.6] jme: JMicron Gigabit Ethernet Driver Guo-Fu Tseng
2008-08-23 6:41 ` Jeff Garzik
2008-08-23 16:04 ` Guo-Fu Tseng
2008-08-25 16:21 ` Ben Hutchings [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-09-15 17:00 Guo-Fu Tseng
2008-09-16 2:47 ` Ethan
2008-09-18 16:07 ` Jeff Garzik
2008-11-21 5:20 ` Stephen Hemminger
2008-11-21 5:36 ` David Miller
2008-11-21 6:45 ` Stephen Hemminger
2008-11-21 8:46 ` David Miller
2008-11-21 16:22 ` Guo-Fu Tseng
2008-11-21 16:18 ` Guo-Fu Tseng
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=20080825162125.GU7908@solarflare.com \
--to=bhutchings@solarflare.com \
--cc=akeem@jmicron.com \
--cc=cooldavid@cooldavid.org \
--cc=ethanhsiao@jmicron.com \
--cc=jgarzik@pobox.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;
as well as URLs for NNTP newsgroup(s).