All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Berger <gmane@reliableembeddedsystems.com>
To: yocto@yoctoproject.org
Cc: Robert Berger
	<public-gmane-G/ASJRsgvFgvW+L+VdN226ESeJV5RFUqQQ4Iyu8u01E@plane.gmane.org>,
	public-yocto-EtnWKYl6rD/WsZ/bQMPhNw@plane.gmane.org
Subject: Re: VFAT patent EP 0 618 540
Date: Sat, 10 Oct 2015 19:58:38 +0300	[thread overview]
Message-ID: <561943BE.40608@reliableembeddedsystems.com> (raw)
In-Reply-To: <CA+-BmJZvJq1MeMWJa-KhkW=+p7ge2GZwh=9znuYNQtjrWSxQ=A@mail.gmail.com>

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.

... 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.

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




  reply	other threads:[~2015-10-10 16:58 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 [this message]
2015-10-11 13:17         ` Chris Simmonds
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=561943BE.40608@reliableembeddedsystems.com \
    --to=gmane@reliableembeddedsystems.com \
    --cc=public-gmane-G/ASJRsgvFgvW+L+VdN226ESeJV5RFUqQQ4Iyu8u01E@plane.gmane.org \
    --cc=public-yocto-EtnWKYl6rD/WsZ/bQMPhNw@plane.gmane.org \
    --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.