why not just say I2C?
CASTalk.com Forum Index CASTalk.com
Discussion of DSP, FPGA, storage and embedded system.
 
 FAQFAQ   MemberlistMemberlist     RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
 
Google
 
Web castalk.com
why not just say I2C?

 
Post new topic   Reply to topic    CASTalk.com Forum Index -> Embedded System
Author Message
tim
Guest





Posted: Tue Dec 21, 2004 2:04 am    Post subject: why not just say I2C? Reply with quote

I am currently working with a range of peripherals whos
control lines look remarkably like an I2C interface.

The data sheets go into great detail about how the data and
clock line are used to communicate with the device and how
it has an own 'address' so that you can differentiate it from
other devices etc.......

Why not just say that it's an I2C comptable device FFS.

Do they have to pay Philips some extra money for admitting
that it's I2C rather than pretending that it is something else?

(and is it really still in patent after 20 years?)

sorry rant over.

tim
Back to top
peterk
Guest





Posted: Tue Dec 21, 2004 2:22 am    Post subject: Re: why not just say I2C? Reply with quote

Just call it SPI like everybody else. It's probably more of a trademark
than a patent issue in the same way you can't call your latest vacuum
cleaner a Hoover.
Peter
Back to top
Grant Edwards
Guest





Posted: Tue Dec 21, 2004 2:30 am    Post subject: Re: why not just say I2C? Reply with quote

On 2004-12-20, peterk <peterk.vt80@gmail.com> wrote:

Quote:
Just call it SPI like everybody else.

Because I2C and SPI aren't very similar at all?

--
Grant Edwards grante Yow! I'LL get it!! It's
at probably a FEW of my
visi.com ITALIAN GIRL-FRIENDS!!
Back to top
Guest






Posted: Tue Dec 21, 2004 2:31 am    Post subject: Re: why not just say I2C? Reply with quote

SPI is not I2C. SPI is to "three-wire interface" as I2C is to "two wire
interface". Or to put it another way, SPI is to Motorola as I2C is to
Philips.

Also, note that "I2C-like" peripherals are in no way guaranteed to be
FULLY I2C compatible.
Back to top
Spehro Pefhany
Guest





Posted: Tue Dec 21, 2004 2:35 am    Post subject: Re: why not just say I2C? Reply with quote

On 20 Dec 2004 13:22:36 -0800, the renowned "peterk"
<peterk.vt80@gmail.com> wrote:

Quote:
Just call it SPI like everybody else. It's probably more of a trademark
than a patent issue in the same way you can't call your latest vacuum
cleaner a Hoover.
Peter

I think you mean "two wire".


Best regards,
Spehro Pefhany
--
"it's the network..." "The Journey is the reward"
speff@interlog.com Info for manufacturers: http://www.trexon.com
Embedded software/hardware/analog Info for designers: http://www.speff.com
Back to top
peterk
Guest





Posted: Tue Dec 21, 2004 3:27 am    Post subject: Re: why not just say I2C? Reply with quote

Oops, of course you are right, it's TWI. I should put my brain into
gear before writing.
Peter
Back to top
Gene S. Berkowitz
Guest





Posted: Tue Dec 21, 2004 7:58 am    Post subject: Re: why not just say I2C? Reply with quote

In article <cq7eol$ac4$00$1@news.t-online.com>,
520010973502.removethis@t-online.de says...
Quote:

I am currently working with a range of peripherals whos
control lines look remarkably like an I2C interface.

The data sheets go into great detail about how the data and
clock line are used to communicate with the device and how
it has an own 'address' so that you can differentiate it from
other devices etc.......

Why not just say that it's an I2C comptable device FFS.

Do they have to pay Philips some extra money for admitting
that it's I2C rather than pretending that it is something else?

(and is it really still in patent after 20 years?)

sorry rant over.

tim

Well, yes, they DO have to pay Philips if they use the term "I2C" or
"IIC".
In exchange, Philips grants them a unique device identifier for their
product.

It's also a trademark.

--Gene
Back to top
Mike Harrison
Guest





Posted: Tue Dec 21, 2004 4:27 pm    Post subject: Re: why not just say I2C? Reply with quote

On Tue, 21 Dec 2004 00:32:17 -0500, Gene S. Berkowitz <first.last@comcast.net> wrote:

Quote:
In article <cq7eol$ac4$00$1@news.t-online.com>,
520010973502.removethis@t-online.de says...

I am currently working with a range of peripherals whos
control lines look remarkably like an I2C interface.

The data sheets go into great detail about how the data and
clock line are used to communicate with the device and how
it has an own 'address' so that you can differentiate it from
other devices etc.......

Why not just say that it's an I2C comptable device FFS.

Do they have to pay Philips some extra money for admitting
that it's I2C rather than pretending that it is something else?

(and is it really still in patent after 20 years?)

sorry rant over.

tim

Well, yes, they DO have to pay Philips if they use the term "I2C" or
"IIC".
In exchange, Philips grants them a unique device identifier for their
product.
Not always - only if it is a new type of device - e.g. all eeproms have the same address prefix.
Back to top
Guest






Posted: Wed Dec 22, 2004 7:58 am    Post subject: Re: why not just say I2C? Reply with quote

Last I heard, I2C was a registered trademark and you had to pay Philips
for using it. There's a lot of these shenanegans being played -
OneWire, SPI, I2C etc. I think that manufacturers have tried to play by
the rules and still let you know what they mean - Atmel uses the TWI -
Two wire interface that can be used with I2C

But you're right - it is annoying

Tom

tim wrote:
Quote:
I am currently working with a range of peripherals whos
control lines look remarkably like an I2C interface.

The data sheets go into great detail about how the data and
clock line are used to communicate with the device and how
it has an own 'address' so that you can differentiate it from
other devices etc.......

Why not just say that it's an I2C comptable device FFS.

Do they have to pay Philips some extra money for admitting
that it's I2C rather than pretending that it is something else?

(and is it really still in patent after 20 years?)

sorry rant over.

tim
Back to top
Ulf Samuelsson
Guest





Posted: Thu Dec 23, 2004 2:05 am    Post subject: Re: why not just say I2C? Reply with quote

<surftom@hotmail.com> skrev i meddelandet
news:1103688440.284627.4970@f14g2000cwb.googlegroups.com...
Quote:
Last I heard, I2C was a registered trademark and you had to pay Philips
for using it. There's a lot of these shenanegans being played -
OneWire, SPI, I2C etc. I think that manufacturers have tried to play by
the rules and still let you know what they mean - Atmel uses the TWI -
Two wire interface that can be used with I2C

But you're right - it is annoying

Tom


Yes, you should ask Philips to adopt the TWI
so we can have one standard :-)

--
Best Regards,
Ulf Samuelsson ulf@a-t-m-e-l.com
This is a personal view which may or may not be
share by my Employer Atmel Nordic AB
Back to top
tim
Guest





Posted: Mon Jan 03, 2005 5:27 am    Post subject: Re: why not just say I2C? Reply with quote

<surftom@hotmail.com> wrote in message
news:1103688440.284627.4970@f14g2000cwb.googlegroups.com...

stupid me for posting the day before I went on my Xmas leave but...

Quote:
Last I heard, I2C was a registered trademark and you had to pay Philips
for using it.

Ah ha, so the name is trademarked and you have to pay Philips to
use it, but the invention is (probably) out of patent so you are
free to use it in a design if you don't say so.

Ta

tim
Back to top
 
Post new topic   Reply to topic    CASTalk.com Forum Index -> Embedded System All times are GMT
Page 1 of 1

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum




VoIP Electronics Powered by phpBB