linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yegor Yefremov <yegorslists-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
To: Linux I2C <linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Cc: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Subject: Accessing EEPROM from Linux driver
Date: Tue, 24 Jan 2012 10:51:27 +0100	[thread overview]
Message-ID: <CAGm1_ku3N0ksJ4USt9Rae=Yo3xcTFX=dLVh6=YMkFjUaLABu-A@mail.gmail.com> (raw)

I've an external i2c attached EEPROM, where I hold the MAC addresses
for 3 interfaces including WLAN. My SoC is am3517 from TI. I found
EEPROM driver under drivers/misc/eeprom/at24.c I can access EEPROM via
sysfs from userland. What were the appropriate method of accessing
EEPROM from a network driver? AFAIK no functions were exported from
eeprom.c.

Regards,
Yegor

             reply	other threads:[~2012-01-24  9:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-24  9:51 Yegor Yefremov [this message]
     [not found] ` <CAGm1_ku3N0ksJ4USt9Rae=Yo3xcTFX=dLVh6=YMkFjUaLABu-A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-01-24  9:54   ` Accessing EEPROM from Linux driver Bill Gatliff
2012-01-24 10:06   ` Wolfram Sang
     [not found]     ` <20120124100636.GB2609-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2012-01-24 10:13       ` Yegor Yefremov
     [not found]         ` <CAGm1_ksgrtyAmo73f-GCr_ZH=8i8LxbwFpMH81U2STQzmT9GYQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-01-24 11:03           ` Yegor Yefremov
     [not found]             ` <CAGm1_kugwA-rWXmCNNcxRc4XZ5u-2N8Rwf+LBaoRrOgBWMTbDg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-01-24 11:13               ` Wolfram Sang
     [not found]                 ` <20120124111320.GD2609-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2012-01-25 11:19                   ` Yegor Yefremov
2012-10-11  9:58                     ` samir

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='CAGm1_ku3N0ksJ4USt9Rae=Yo3xcTFX=dLVh6=YMkFjUaLABu-A@mail.gmail.com' \
    --to=yegorslists-gm/ye1e23mwn+bqq9rbeug@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.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).