netdev - [RFC PATCH 0/2] ks8851: support for read/write MAC address from EEPROM

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 29 Mar 2010 20:17:16 +0200
From:	Sebastien Jan <s-jan@...com>
To:	netdev@...r.kernel.org, Ben Dooks <ben@...tec.co.uk>
Cc:	Abraham Arce <x0066660@...com>, Sebastien Jan <s-jan@...com>
Subject: [RFC PATCH 0/2] ks8851: support for read/write MAC address from EEPROM

Hello,

I needed to program a mac address to the companion eeprom of our ks8851, and
wrote the following patches, which use debug-fs as interface.

I then realized that this seemed not the usual way to access net controller
eeproms (ethtool seems the more standard way).

I am very interesed in getting your feedbacks on the following:
 1) Does it make any sense to you to use this debug-fs interface to read/write
the mac address (advantage: no need for user to know how ks8851 manages the
eeprom / alignment / offset), and can it be upstreamed?
 2) Must a more generic eeprom access be implemented through ethtool (or another
interface?)? Is it the only choice or can it coexist with option 1)? (most of
code would be common)
 3) Any feedback regarding the code itself or anything else is very welcome!

Thanks,
Sebastien

Sebastien Jan (2):
  ks8851: Add support for MAC address write to companion EEPROM
  ks8851: Add support for MAC address read from companion EEPROM

 drivers/net/ks8851.c |  445 ++++++++++++++++++++++++++++++++++++++++++++++++++
 drivers/net/ks8851.h |   14 ++-
 2 files changed, 458 insertions(+), 1 deletions(-)

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html