public inbox for
 help / color / mirror / Atom feed
From: "Kumar, Vivek" <>
To: 'Andrew Lunn' <>, Vivek Kumar <>
Subject: RE: Assignment query
Date: Thu, 26 Aug 2004 23:03:00 -0000	[thread overview]
Message-ID: <0175EEA85416D811893E009027D0F5D7938A05@MAILHOST> (raw)

[-- Attachment #1: Type: text/plain, Size: 2163 bytes --]

Hi Andrew,

After some negotiation and emails it seems that the management is ok with me
putting my flash driver code in open source. I talked to my manager and he
said the email from them saying "Go Ahead With This" (Attached) will
suffice. Do I still need to get more stuff from them.

Also I was thinking if I rewrite the drivers at home from scratch, can I put
them in open source. Is there a standard letter I can send the management
saying I am working from home on something similar and if they are OK with


> -----Original Message-----
> From: Andrew Lunn []
> Sent: Tuesday, August 10, 2004 12:04 AM
> To: Vivek Kumar
> Cc:
> Subject: Re: Assignment query
> On Mon, Aug 09, 2004 at 03:54:48PM -0700, Vivek Kumar wrote:
> > Hi,
> >
> > I wrote a Flash Driver Code for the company I am working for and
> > would like to release it to ecos. They seem to be open to that but
> > the problem I had in this is that the company still wants to use the
> > code in the proprietary system.
> >
> > I Was wondering if there are some standard license agreements where
> > they give up the copyright for the source-code but still maintain
> > non-exclusive rights for them and there distributors to use the code
> The standard eCos Assignment can be found at
> The second paragraph says:
>    Upon thirty days prior written notice, eCosCentric Limited 
> agrees to
> grant me non-exclusive rights to use the Work (i.e. just my changes
> and enhancements, not eCos as a whole) as I see fit; (and
> eCosCentric's rights shall otherwise continue unchanged).
> So what you want is not a problem. Simply invoke this clause. 
>    Andrew

Confidentiality note: This email and any attachments may contain private, confidential, and privileged material for the sole use of the intended recipient. Any unauthorized review, use, disclosure or distribution is strictly prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.

[-- Attachment #2: RE: --]
[-- Type: message/rfc822, Size: 1403 bytes --]

From: "Pandula, Louis" <>
To: "Kumar, Vivek" <>, "Patel, Dharmesh" <>
Subject: RE:
Date: Thu, 26 Aug 2004 15:25:26 -0700
Message-ID: <0175EEA85416D811893E009027D0F5D7C0CDF5@MAILHOST>

Dharmesh, Go ahead with this. Louis

-----Original Message-----
From: Kumar, Vivek 
Sent: Tuesday, August 17, 2004 10:39 AM
To: Pandula, Louis; Patel, Dharmesh


I wanted to release the generic flashDriver files we are using to
freesoftware, specialy for use in ecos.
These files are derived from the work I did to develop the genericFlash
driver in Target Manager to handle JEDEC-CFI flash detection, configuration
and usage.

For this I would need to get a "copyright disclaimer" from zeevo. 

    Zeevo Inc., hereby disclaims all copyright interest in the seven listed
files (which together     
    implement a generic cfi flash driver) written by Vivek Kumar.

1.	 FlashCfiGeneric.c 

2.	 FlashCfiGeneric.h 

3.	 FlashCommon.h 

4.	 FlashDevice.c 

5.	 FlashDevice.h 

6.	 FlashQuery.c 

7.	 FlashQuery.h

These seven files are attached in this email    

Vivek Kumar
Firmware Engineer, Zeevo Inc.
2500 Condensa Street Santa Clara, CA 95051
Tel:  (408) 982-8040 Fax: (408) 982-8008

             reply	other threads:[~2004-08-26 23:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-26 23:03 Kumar, Vivek [this message]
2004-08-27  6:56 ` Andrew Lunn
2004-08-27 10:20   ` Alex Schuilenburg
2004-08-27 12:25   ` Jonathan Larmour
  -- strict thread matches above, loose matches on Subject: below --
2007-06-25 13:10 Rutger Hofman
2007-07-05 13:07 ` Jonathan Larmour
2006-01-09 15:35 Chase, Thomas
2006-01-12 15:41 ` Jonathan Larmour
2004-08-27 16:47 Kumar, Vivek
2004-08-09 22:54 Vivek Kumar
2004-08-10  7:04 ` Andrew Lunn

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0175EEA85416D811893E009027D0F5D7938A05@MAILHOST \ \ \ \ \

* 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 read-only IMAP folder(s) and NNTP newsgroup(s).