From: Abraham Arce <abraham.arce.moreno@gmail.com>
To: Sebastien Jan <s-jan@ti.com>
Cc: netdev@vger.kernel.org, Ben Dooks <ben@simtec.co.uk>,
Abraham Arce <x0066660@ti.com>
Subject: Re: [RFC PATCH 0/2] ks8851: support for read/write MAC address from EEPROM
Date: Mon, 3 May 2010 21:13:46 -0500 [thread overview]
Message-ID: <r2gcb8016981005031913xf7b1d0c7gff1229a3fc47133e@mail.gmail.com> (raw)
In-Reply-To: <1269886638-11025-1-git-send-email-s-jan@ti.com>
Hi,
> 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!
>
Does anyone could guide us about the implementation done by Sebastien?
http://patchwork.ozlabs.org/patch/48880/
http://patchwork.ozlabs.org/patch/48881/
Best Regards
Abraham
prev parent reply other threads:[~2010-05-04 2:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 18:17 [RFC PATCH 0/2] ks8851: support for read/write MAC address from EEPROM Sebastien Jan
2010-03-29 18:17 ` [RFC PATCH 1/2] ks8851: Support MAC address write to companion EEPROM Sebastien Jan
2010-03-29 18:17 ` [RFC PATCH 2/2] ks8851: Support MAC address read from " Sebastien Jan
2010-05-04 2:13 ` Abraham Arce [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=r2gcb8016981005031913xf7b1d0c7gff1229a3fc47133e@mail.gmail.com \
--to=abraham.arce.moreno@gmail.com \
--cc=ben@simtec.co.uk \
--cc=netdev@vger.kernel.org \
--cc=s-jan@ti.com \
--cc=x0066660@ti.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 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).