Commentary

Serdar Yegulalp
 

Microsoft's Embedded Linux Deal With Kyocera May Not Be About Embedded Linux

After reading about Microsoft cutting a deal with Kyocera to cross-license some of its patents in certain embedded Linux devices, I wondered if this really had anything to do with Linux at all.  Many of the posts I've read on the subject have taken that to be the case, but is that true?

After reading about Microsoft cutting a deal with Kyocera to cross-license some of its patents in certain embedded Linux devices, I wondered if this really had anything to do with Linux at all.  Many of the posts I've read on the subject have taken that to be the case, but is that true?


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

I started by recalling what it was that Kyocera made -- mainly multifunction copiers, essentially high-volume printers for workgroups.  Perhaps all that's happening here is nothing more sinister than Kyocera licensing certain Microsoft protocols or technologies, such as SMB or NTFS (or maybe their fonts, as some people have speculated), in a Linux implementation.

In short, this probably isn't about MS claiming ownership of embedded Linux -- it's about Kyocera wanting to guarantee proper compatibility with aspects of Windows for certain devices that run embedded Linux.  It's just that the wording of the deal, as is often the case in such things, is so wretchedly vague that it's impossible to say exactly what's covered.

Unless someone intimately involved with the deal spills the beans, it will be difficult to say.  But I seriously doubt that even Microsoft is arrogant enough to claim it owns embedded Linux, or some statement to that effect.  They can't be that foolish.  (Can they?)


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links