From: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
To: Yegor Yefremov <yegorslists-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
Cc: Linux I2C <linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Accessing EEPROM from Linux driver
Date: Tue, 24 Jan 2012 11:06:36 +0100 [thread overview]
Message-ID: <20120124100636.GB2609@pengutronix.de> (raw)
In-Reply-To: <CAGm1_ku3N0ksJ4USt9Rae=Yo3xcTFX=dLVh6=YMkFjUaLABu-A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 720 bytes --]
> sysfs from userland. What were the appropriate method of accessing
> EEPROM from a network driver? AFAIK no functions were exported from
> eeprom.c.
Please state always which version you are using. There is code exactly
for your use case in the driver since ~2.6.30 (and clearly described as
such).
437 /*
438 * This lets other kernel code access the eeprom data. For example, it
439 * might hold a board's Ethernet address, or board-specific calibration
440 * data generated on the manufacturing floor.
441 */
Regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-01-24 10:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-24 9:51 Accessing EEPROM from Linux driver Yegor Yefremov
[not found] ` <CAGm1_ku3N0ksJ4USt9Rae=Yo3xcTFX=dLVh6=YMkFjUaLABu-A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-01-24 9:54 ` Bill Gatliff
2012-01-24 10:06 ` Wolfram Sang [this message]
[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=20120124100636.GB2609@pengutronix.de \
--to=w.sang-bicnvbalz9megne8c9+irq@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=yegorslists-gM/Ye1E23mwN+BqQ9rBEUg@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).