throbber
Austin/Georgetown
`
`
`Dallas
`Silicon Valley
`
`
`
`Jennifer Towle
`800 S. Austin, Suite 200
`Georgetown, TX 78626
`512-582-2828
`www farneydaniels.com
`
`
`Minneapolis
`Wilmington
`
`
`March 28, 2014
`
`VIA E-MAIL
`
`Brian M. Berliner
`O’Melveny & Myers LLP
`400 South Hope Street
`Los Angeles, CA 90071-2899
`
`Re: Memory Integrity LLC v. Samsung Electronics Co., Ltd. et al., Case No. 1:13-cv-01808-
`GMS
`
`
`Dear Mr. Berliner:
`
`I write in response to your letter dated March 14, 2014. In your letter, you claim: (1) that
`Memory Integrity does not have a sufficient basis under Federal Rule of Civil Procedure 11 for
`claiming that Samsung infringes U.S. Patent No. 7,296,121 (the “’121 Patent”),
`
`
`
`Response to Samsung’s Allegation of a Rule 11 Violation:
`
`
`
`
`
`In your letter you assert that none of the accused Samsung products listed in the
`Complaint contain a “point-to-point” architecture. You further assert that all CPU
`communications in these products pass through the Snoop Control Unit using a bus structure
`rather than a point-to-point architecture. On this basis, you allege that Memory Integrity failed
`to conduct an adequate pre-filing investigation.1
`
`We respectfully disagree with your assertion that the Samsung products identified in the
`Complaint do not contain a point-to-point architecture and that Memory Integrity failed to
`conduct an adequate pre-filing investigation. As shown in Figure 1.1 of your letter (reproduced
`below), the Cortex-A9 contains separate links between each core (e.g., CPU0, CPU1, CPU2, and
`CPU3) and the Snoop Control Unit (SCU). Thus, the cores do not use a shared-bus architecture
`
`1 Your letter also states that the Galaxy Tab 7.0 product does not have a multicore processor. However, Samsung’s
`own webpage for the Samsung Galaxy Tab 7.0 Plus indicates that at least that version of the product has a multi-
`core processor: http://www.samsung.com/global/microsite/galaxytab/7.0/spec.html?type=find.
`
`1
`
`APPLE 1016
`
`

`

`March 28. 2014
`
`Page 2
`
`but rather utilize separate links to the SCU. Indeed, this is consistent with what the ’ 121 Patent
`shows in Figure 1B, which the Patent’s specification describes as a point-to-point architecture
`that can use the techniques of the patented invention. See ’ 121 Patent. Fig. 1B and 6:24-35.
`Further, the patent notes that the use of a switch as shown in Figure 1B is advantageous because
`it “allows implementation with fewer point-to-point links.” See id. at 6:28-30.
`
`Co rtex-AE L'PCure
`
`V
`
`V
`
`.
`
`Y
`
`Y
`
`‘
`CPU1
`:>
`
`
`Cache me UH'ECIO'Y
`
`«DupHcated cpsTag
`
`i
`
`’
`
`C ”0
`TN
`
`nstructlor‘. data, and coherency buses
`
`TN
`
`CPUZ
`TTT
`
`Ema
`fiT
`
`\r‘st'ocmm data. ar‘d owerency nuses
`
`.
`'
`|
`'
`Tag RA” ‘ '
`l Tao Ram ,‘ w
`‘
`Tag RAM a ->
`
`Tag RAH < w
`
`’
`
`Tag control
`
`
`Slate 0
`
`.
`
`Pwate timer
`Prrmatezmer
`ard watchdog)
`and n atchdug
`
`
`.
`-
`-
`pomt-to-pomt Imks
`
`
`
`Iaterrup:
`cowtru Ier
`
`
`
`Glocaltwmer
`
`I
`Snooo Control Vm USEL-
`
`Camera
`cametraqsfers
`
`
`
`“x
`
`n
`5 cup
`
`ta
`
`'n
`
`9
`
`ACCE‘EFBIO'
`
`
`Coherenqr
`an". IACPu
`Vlaster 0
`L’astar 1 xnutma A wrth
`
`IDDIIDHSII‘
`address Mermg canauumes
`See Figlu‘e 1.1 of the Cortex-A9 lieference Manual (annotations added in red).
`
`
`
`Accordingly, your assertions that SamSImg does not infringe the ’ 121 Patent and that Memory
`Integrity failed to conduct an adequate pre-filing investigation are without merit.
`
`
`
`
`2
`
`

`

`March 28, 2014
`
`Page 3
`
`
`
`Should you wish to discuss these matters fluther, please let me know.
`
`Sincerely,
`
`/s/ Jennifer Towle
`Jemlifer Towle
`
`3
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket