| |||||||||||||
A line in the sand for graphics driversA line in the sand for graphics driversPosted Jul 9, 2010 9:57 UTC (Fri) by yoe (subscriber, #25743)In reply to: A line in the sand for graphics drivers by Baylink Parent article: A line in the sand for graphics drivers
Everyone who writes some software is violating everyone else's patent. That's not an issue.
It becomes one if you violate someone's patent knowingly; but proving that you knew about something at some distant point in the past is rather hard.
(Log in to post comments)
A line in the sand for graphics drivers Posted Jul 9, 2010 10:21 UTC (Fri) by __alex (subscriber, #38036) [Link]
It does make it much easier for patent trolls to spam vendors with litigation if they can simply grep through some source files for bits of code that look vaguely infringing though right? I have no idea if vendors actually think this way but I can see where this argument comes from.
A line in the sand for graphics drivers Posted Dec 27, 2010 15:11 UTC (Mon) by ksandstr (guest, #60862) [Link]
Program code cannot be analyzed for patent violations by simply grepping through it.
A line in the sand for graphics drivers Posted Jul 9, 2010 17:14 UTC (Fri) by njs (guest, #40338) [Link]
Whether you knew about the patent only affects how much the patent owner can demand in damages -- they can in any case stop you from shipping your product and demand a chunk of all your past revenue.
Everyone who writes some software is violating other people's patents; the problem is if one of those patent owners notices and can sue you.
|
|||||||||||||