From: Andreas Werner <wernerandy@gmx.de>
To: kavitha bk <bk.kavitha1@gmail.com>
Cc: linux-kernel@vger.kernel.org, andreas.werner@men.de
Subject: Re: eeprom Board Information EEPROM
Date: Tue, 2 Sep 2014 11:52:54 +0200 [thread overview]
Message-ID: <20140902095253.GA693@awedesk.fritz.box> (raw)
In-Reply-To: <CACx5bVzvJ-x7EdnGX+AraNBwKaxKNwRVvBwN1-0DNY3O155U5Q@mail.gmail.com>
On Mon, Sep 01, 2014 at 01:52:10PM +0530, kavitha bk wrote:
> On Sat, Aug 30, 2014 at 2:26 AM, Andreas Werner <wernerandy@gmx.de> wrote:
>
> > I have a question regarding a driver for a Board Information EEPROM.
> >
> > I want to give our customer easy access to our Board Information EEPROM
> > which is an 256byte I2C eeprom.
> >
>
>
> >
> > There is a defined structure of information at the beginning of the eeprom
> > which includes board name, serialnumber, production date, repair date and
> > a eeprom structure ident number.
> >
> > The rest of the eeprom is for user defined settings where customer can
> > write
> > any data to.
> >
> > I want to have access to the eeprom without any special to and without
> > installing
> > anything just running linux and to a cat/echo to sysfs entries to
> > read/write
> > data to the eeprom.
> >
> > What i want to do is to create sysfs entries for the pre defined settings
> > and
> > on entrie where customer can access the rest of the eeprom bytes.
> >
> > Is drivers/misc/eeprom the right place to put those kind of driver in?
>
>
> Yes You can add here
>
> > Or are
> > there any other options to write those kind of driver?
> >
>
> Which eeprom are you using? You can explore CONFIG_EEPROM_AT24 driver for
> writing a sys interface
>
Ok i will check it out.
Thanks.
Regards
Andy
>
> >
> >
> > Regards
> > Andy
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
> >
next prev parent reply other threads:[~2014-09-02 7:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-29 20:56 eeprom Board Information EEPROM Andreas Werner
[not found] ` <CACx5bVzvJ-x7EdnGX+AraNBwKaxKNwRVvBwN1-0DNY3O155U5Q@mail.gmail.com>
2014-09-02 9:52 ` Andreas Werner [this message]
[not found] ` <CACx5bVwUaHXOD0NxOiGzEMVQ0HYF2eLXVBL3nu1s=xAemYP9LQ@mail.gmail.com>
[not found] ` <20140903143415.GA3684@awedesk.fritz.box>
[not found] ` <CACx5bVxpGW=vb8zXLLJ9ewUOfw3ib0g=YBHUcTAS=vMhZ7NnHg@mail.gmail.com>
[not found] ` <20140915172255.GA798@awedesk.fritz.box>
[not found] ` <CACx5bVwHo4AUN8UXarX1ygCr9jddYWnM8A-BCOF9W97FcMLJuQ@mail.gmail.com>
2014-09-20 11:23 ` Andreas Werner
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=20140902095253.GA693@awedesk.fritz.box \
--to=wernerandy@gmx.de \
--cc=andreas.werner@men.de \
--cc=bk.kavitha1@gmail.com \
--cc=linux-kernel@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).