RE: What is TDI in ehci_is_TDI()

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> 
> This is really something you should discuss with Xilinx's lawyers.
But
> you asked for my opinion, so here it is...
> 
> The idea that you can sidestep a copyright violation by using 28
> instead of 26 is ludicrous.  Nobody has a copyright on the number 26.
> If you're worried about infringing on somebody else's intellectual
> property, I don't think changing one number will be enough to avoid
the
> issue.
> 
> If you really intend to design and market your own version of the
> "integrated-TT" controller, then it's most likely a mistake to vary
the
> programming interface.  This will cause market fragmentation and will
> help nobody.
> 
> For example, what will happen in a system that has two EHCI
controllers
> made by separate vendors, each with a different layout of bits in the
> port status registers?  Then a single #define would never work.
> 
> Alan Stern
> 

Totally make sense, thanks, Alan,

Julie.

This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.


--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux