From: Trent Piepho <xyzzy-zY4eFNvK5D+xbKUeIHjxjQ@public.gmane.org>
To: David Brownell <david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
Cc: Linux I2C <i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org>
Subject: Re: [PATCH 2/3] i2c: Let bus drivers add SPD to their class
Date: Wed, 4 Jun 2008 13:05:31 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0806041303340.10290@shell4.speakeasy.net> (raw)
In-Reply-To: <200806040018.10191.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
On Wed, 4 Jun 2008, David Brownell wrote:
> > Also, couldn't these platforms have other EEPROMs on these buses,
> > either EDID EEPROMs or proprietary ones, for which people might be
> > using the read-only eeprom driver at the moment? I don't want users to
> > experience a regression by applying this patch set. I'd rather have
> > them migrate their platform to the at24 driver once it is upstream and
> > remove the I2C_CLASS_SPD flag when they do.
>
> Unlikely. At least in the cases I called out.
>
> Oh, and parport. DRAM sticks, or LCD displays, over parport
> links would be strange. ;)
An eeprom programmer or reader using a parport i2c interface doesn't seem
all that strange. If I needed to make an i2c eeprom programmer, that's
probably what I'd do.
_______________________________________________
i2c mailing list
i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
http://lists.lm-sensors.org/mailman/listinfo/i2c
next prev parent reply other threads:[~2008-06-04 20:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-03 11:02 [PATCH 2/3] i2c: Let bus drivers add SPD to their class Jean Delvare
[not found] ` <20080603130221.1f819e64-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-06-03 20:19 ` David Brownell
[not found] ` <200806031319.56606.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
2008-06-03 21:12 ` Jon Smirl
[not found] ` <9e4733910806031412t52e7ed1bl8fd56751bef12a7a-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-06-03 21:33 ` Trent Piepho
[not found] ` <Pine.LNX.4.58.0806031420160.10290-13q4cmjDBaTP3RPoUHIrnuTW4wlIGRCZ@public.gmane.org>
2008-06-03 22:03 ` Jon Smirl
[not found] ` <9e4733910806031503w46662d4fib36d3b67563bbdf1-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-06-04 19:59 ` Trent Piepho
2008-06-04 6:09 ` Jean Delvare
[not found] ` <20080604080933.456c8ce2-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-06-04 7:18 ` David Brownell
[not found] ` <200806040018.10191.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
2008-06-04 20:05 ` Trent Piepho [this message]
[not found] ` <Pine.LNX.4.58.0806041303340.10290-13q4cmjDBaTP3RPoUHIrnuTW4wlIGRCZ@public.gmane.org>
2008-06-04 20:48 ` David Brownell
2008-06-04 21:01 ` Jean Delvare
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=Pine.LNX.4.58.0806041303340.10290@shell4.speakeasy.net \
--to=xyzzy-zy4efnvk5d+xbkueihjxjq@public.gmane.org \
--cc=david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org \
--cc=i2c-GZX6beZjE8VD60Wz+7aTrA@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.