linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: linux-i2c@vger.kernel.org
Subject: Re: can't write more than one byte to AT24C64 EEPROM using "eeprog"
Date: Wed, 26 Jul 2017 17:31:13 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.20.1707261729480.3404@localhost.localdomain> (raw)
In-Reply-To: <20170726205740.GB1510@katana>

On Wed, 26 Jul 2017, Wolfram Sang wrote:

> >   thoughts? is no one else seeing this issue?
>
> Just for the record: I always use the kernel at24 driver for eeproms
> and haven't used those tools for ages. I could imagine this is true
> for most people and would explain undiscovered bugs and bitrot.

  i'm not even sure what that means ... how do you distinguish between
the kernel drivers and the user space utilities?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

  reply	other threads:[~2017-07-26 21:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-25 12:51 can't write more than one byte to AT24C64 EEPROM using "eeprog" rpjday
2017-07-25 17:51 ` Robert P. J. Day
2017-07-26 18:30   ` Robert P. J. Day
2017-07-26 20:57     ` Wolfram Sang
2017-07-26 21:31       ` Robert P. J. Day [this message]
2017-07-26 21:57         ` Wolfram Sang
2017-07-27  8:40       ` Robert P. J. Day
2017-07-27  9:34         ` Wolfram Sang

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=alpine.LFD.2.20.1707261729480.3404@localhost.localdomain \
    --to=rpjday@crashcourse.ca \
    --cc=linux-i2c@vger.kernel.org \
    --cc=wsa@the-dreams.de \
    /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).