All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Simmonds <chris@2net.co.uk>
To: yocto@yoctoproject.org
Subject: Re: VFAT patent EP 0 618 540
Date: Sun, 11 Oct 2015 14:17:13 +0100	[thread overview]
Message-ID: <561A6159.4070402@2net.co.uk> (raw)
In-Reply-To: <561943BE.40608@reliableembeddedsystems.com>

Hi

On 10/10/15 17:58, Robert Berger wrote:
> Hi
>
> On 10/09/2015 11:20 PM, Ayoub Zaki wrote:
>> TI Socs Boot Rom code can use Vfat but does not necessarly need it as
>> Bootloaders (spl, u-boot) can be loaded directly  from Raw MMC/eMMC.
> I just discovered this recently. Something like:
>
> sudo dd if=./u-boot/MLO of=${DISK} count=1 seek=1 bs=128k
> sudo dd if=./u-boot/u-boot.img of=${DISK} count=2 seek=1 bs=384k
>
> So even my made up scenario where you would need vfat on the first
> partition does not hold anymore.
Usually the need to include vfat support driven by the desire to
read/write removable media such as SD cards and USB mass storage
devices. If you want interoperability with certain legacy operating
systems vfat is the only option.

>
> ... but ...
>
> what about the patent and the on-chip ROMs of SoCs from Ti and Freescale
> (hmm NXP? or whoever bought them lately). Maybe the SoCs are affected
> since they are able to load stuff from vfat, even if we don't need to
> use this feature anymore.
Not a problem for two reasons. First the patent only applies to fat32;
you can do anything you like with fat16. The TI romcode only uses fat16,
I am pretty sure. Second, even with fat32, the patent is only concerned
with updates to the namespace, hence so long as the romcode does not
have the ability to create files it is also OK. Note that you can't get
round the patent just by mounting vfat partitions read-only because the
driver still has the ability to make new files. There was a patch for
the vfat driver which removed the code to create or modify directory
entries, but it seems to have got lost in the mists of time.
>
> Regards,
>
> Robert
>
> ..."Never express yourself more clearly than you think." - Niels Bohr
>
> My public pgp key is available,at:
> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1
>
>
-- 
Chris Simmonds, Consultant, 2net Ltd
http://www.2net.co.uk
+44 (0)1962 869003



  reply	other threads:[~2015-10-11 13:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-09  8:36 VFAT patent EP 0 618 540 Gorny Krystian
2015-10-09 18:30 ` Robert Berger
2015-10-09 19:58   ` Christian Ege
2015-10-09 20:20     ` Ayoub Zaki
2015-10-10 16:58       ` Robert Berger
2015-10-11 13:17         ` Chris Simmonds [this message]
2015-10-13 13:58           ` Gorny Krystian
2015-10-10 16:50     ` Robert Berger

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=561A6159.4070402@2net.co.uk \
    --to=chris@2net.co.uk \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.