Re: [yocto] Can any one please tell the what is the exact difference between DEPENDS and RDEPENDS

2015-10-09 Thread Vivek Per 
Hi,
 Thanks
 I have one more doubt when RDEPENDS variable depends is packages . Do you
know why RDEPENDS variable in (rootfs-image.bb recipe) which inherit
core-image. why RDEPENDS cant able to install packages in final roofs image
apart from IMAGE_INSTALL .



Thanks and regrads
 Vivek

On Thu, Oct 8, 2015 at 6:19 PM, Petter Mabäcker  wrote:

> 2015-10-08 06:37 skrev Vivek Per:
>
> Hi,
>  Can any one please tell the what is the exact difference between
> DEPENDS and RDEPENDS . I am not able to get it . How these variables are
> exactly parsed.
>
>
> -regards
> vivek
>
>
>
> Hi,
>
> I guess you already have read through the manual about the variables?
>
>
> http://www.yoctoproject.org/docs/1.8/ref-manual/ref-manual.html#var-RDEPENDS
>
> http://www.yoctoproject.org/docs/1.8/ref-manual/ref-manual.html#var-DEPENDS
>
>
>
> The overall description of the differences are (please someone correct me
> if you find my answer incorrect) that DEPENDS specifics build-time
> dependencies (e.i. other recipe files) so you should be guaranteed that all
> packages listed in the DEPENDS has been built and installed in the sysroot
> before your new package starts its configure task.
>
> RDEPENDS on the other hand, is a run-time dependency so instead of other
> recipe files RDEPENDS lists packages that should have been installed in
> order to correctly run your package on target.
>
>
> All this is explained more in detail in the manual (see above links). Also
> keep in mind that DEPENDS works with recipes and RDEPENDS with packages
> (which isn't necessary the same). Debug the PACKAGES for a specific
> variable (
> http://www.yoctoproject.org/docs/1.8/ref-manual/ref-manual.html#var-PACKAGES)
> in order to get a clue about what packages a recipe will generate.
>
> If you still have a hard to understanding the differences my suggestion is
> that you starts playing around a bit with them. Create a project and add
> some DEPENDS and RDEPENDS to a recipe(s), build the affected packages and
> investigate if they have been built in the expected order. This can for
> example be verified by tracking the build output or by looking through the
> cooker logs tmp/log/cooker/*.
>
> BR Petter
>
>
>
> Petter Mabäcker
>
> Technux www.technux.se
>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] can any one please tell the difference between DEPENDS and RDEPENDS

2015-10-09 Thread Vivek Per 
Hi,
Thanks
  As i read RDEPENDS  in recipe  do_build task depends on
do_pacakge_write_rpm task (i.e packages )
 I have one more doubt when RDEPENDS variable depends is packages . Do you
know why RDEPENDS variable in (rootfs-image.bb recipe) which inherit
core-image. why RDEPENDS cant able to install packages in final roofs image
apart from IMAGE_INSTALL .



Thanks and regrads
 Vivek

On Thu, Oct 8, 2015 at 9:16 PM, Robert Berger <
gm...@reliableembeddedsystems.com> wrote:

> On 10/07/2015 09:10 AM, Vivek Per wrote:
> > Hi,
> >  Can any one please tell the what is the exact difference between
> > DEPENDS and RDEPENDS .
>
> DEPENDS:
>
> http://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#var-DEPENDS
>
> RDEPENDS:
>
> http://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#var-RDEPENDS
>
> > I am not able to get it . How these variables are
> > exactly parsed.
> >
>
> Do you need more info?
>
> >
> > regards
> > vivek
> >
> >
> > --
> >
>
> Regards,
>
> Robert
>
>
> ...No matter what the problem is,it's always a people problem.- Jerry
> Weinberg
>
> My public pgp key is available,at:
> http://pgp.mit.edu:11371/pks/lookup?op=get=0x90320BF1
>
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] VFAT patent EP 0 618 540

2015-10-09 Thread Gorny Krystian 
Hi,
I have a question regarding the VFAT patent (EP 0 618 540) owned by Microsoft. 
It's about common name space for long and short filenames. I have read that 
this patent was canceled by Germany / EU, but it's still available in the US 
right? So is there a patch/option where we can activate to avoid this patent?
Thanks
Krystian


_

Krystian Gorny
Research & Development

Wipotec GmbH
Adam-Hoffmann-Str. 26
67657 Kaiserslautern

T +49.631.34146-0
F +49.631.34146-8640
http://www.wipotec.com


[http://www.wipotec.com/fileadmin/user_upload/Signatur/W_Standard.jpg]

Legal information:
Wipotec Wiege- und Positioniersysteme GmbH
HRB 2317 Kaiserslautern, Management: T. D?ppre, U. Wagner

This e-mail may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and delete this e-mail. Any unauthorized
copying, disclosure or distribution of the material in this e-mail is strictly
forbidden.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Remove my email from your database

2015-10-09 Thread Khem Raj 
Unsubscribe from mailing list. The link is right at bottom of the email

> On Oct 8, 2015, at 4:38 AM, neerajdadhwal1...@gmail.com wrote:
> 
> Sir
> Please remove my email id . Iam frustate with ur unwanted mails.
> 
> 
> Sent from my Huawei Mobile
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto



signature.asc
Description: Message signed with OpenPGP using GPGMail
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] kernel-module- prefix for out-of-tree modules mandatory?

2015-10-09 Thread Khem Raj 

> On Oct 8, 2015, at 1:29 PM, Daniel.  wrote:
> 
> Hi all,
> 
> Is the kernel-module- prefix mandatory for out-of-tree modules
> compiled inside Yocto? And, This prefix applies to package names or
> recipe names? Should I rename my recipe file with this prefix or setup
> PN stuff?

if you inherit module bbclass then the split will happen automatically
you can name your recipe anything you like, the naming applies to out packages 
only

> 
> Cheers,
> 
> --
> "Do or do not. There is no try"
>  Yoda Master
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto



signature.asc
Description: Message signed with OpenPGP using GPGMail
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Intelligent global config files setting

2015-10-09 Thread Gilles CARRY 
Hi,

I have a concern regarding global config files to be put into rootfs when 
several components need to alter a common config file.
Let me explain with an example.
I have two components (recipes) that need to write options into /etc/directfbrc.
Let's call the recipes c1.bb and c2.bb and respectively optc1 and optc2, the 
options they want to write to /etc/directfbrc.

The fast (and not very clean) way to do it is to centralized all the settings 
in a single recipe but this is not what I want. For a matter of maintenance, I 
would like the option settings be attached to their respective components. If 
c1 is not required (not in dependency list) then optc1 is not set.

I tried to use ROOTFS_POSTPROCESS_COMMAND in c1.bb and c2.bb but this mechanism 
only seems to work in images recipes. (inherit core-image)
Then I considered using base-file.bbappend in directories where c1 and c2 are 
stored but this does not work as base-file.bbappend is always read even though 
c1 or c2 are disabled.

Any clue?

Thanks,
Best regards,
Gilles.

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] VFAT patent EP 0 618 540

2015-10-09 Thread Ayoub Zaki 
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.
Am 09.10.2015 21:59 schrieb "Christian Ege" :

> Hi,
> Am 09.10.2015 8:31 nachm. schrieb "Robert Berger" <
> gm...@reliableembeddedsystems.com>:
> >
> > Hi,
> >
> > On 10/09/2015 11:36 AM, Gorny Krystian wrote:
> > > Hi,
> > >
> > > I have a question regarding the VFAT patent (EP 0 618 540) owned by
> > > Microsoft. It’s about common name space for long and short filenames. I
> > > have read that this patent was canceled by Germany / EU, but it’s still
> > > available in the US right? So is there a patch/option where we can
> > > activate to avoid this patent?
> >
> > I am not a lawyer, but wouldn't it be easier not to use VFAT?
> > The only reason I would use it, would be because the bootloader of my
> > SoC would only be able to boot over FAT/FAT32 from a managed flash. A
> > patch will not help here as well;)
> A decent U-Boot can load the kernel from ext4. And I do not know any ROM
> loader which needs vfat, except maybe this TI SOCs...
>
> Regards,
> Christian
> >
> > There are rumors that a fix was implemented a long time ago[1] ;)
> >
> > >
> > > Thanks
> > >
> > > Krystian
> > >
> >
> > Regards,
> >
> > Robert
> >
> >
> > [1]
> >
> http://arstechnica.com/information-technology/2009/07/vfat-linux-patch-could-circumvent-microsofts-patent-claims/
> >
> > >
> > > Legal information:
> > > Wipotec Wiege- und Positioniersysteme GmbH
> > > HRB 2317 Kaiserslautern, Management: T. Düppre, U. Wagner
> > >
> > > This e-mail may contain confidential and/or privileged information.
> > > If you are not the intended recipient (or have received this e-mail in
> > > error)
> > > please notify the sender immediately and delete this e-mail. Any
> > > unauthorized
> > > copying, disclosure or distribution of the material in this e-mail is
> > > strictly
> > > forbidden.
> > >
> >
> > Since you are concerned about legal issues you might also want to remove
> > this footer when posting to public lists ;)
> >
> > >
> > > --
> > >
> >
> > ..."Rules of Optimization: Rule1: Don't do it. Rule 2 (for experts
> > only): Don't do it yet." - M.A. Jackson (not the singer)
> >
> > My public pgp key is available,at:
> > http://pgp.mit.edu:11371/pks/lookup?op=get=0x90320BF1
> >
> >
> > --
> > ___
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Status WW41

2015-10-09 Thread Jolley, Stephen K 
Current Dev Position: YP 2.0 Final (rc1 out of QA and being reviewed.)

Next Deadline: YP 2.0 Final Release Target: Before Oct. 30, 2015


SWAT team rotation: Cristian -> Randy

https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team


Top Bugs to be tackled:

* systemd timeouts in the sanity tests (#7919, #8141, #8142)

* All LSB builds fail sanity testing (#8452)

* wic fails selftest (#8466)


Key Status/Updates:

* Hopefully everyone at ELC-E is having a good time!

* Jethro has branched, current master and jethro are identical and 
master will track jethro until close to release.

* RC1 is out of QA and the results from QA are being reviewed.  RC2 
should be built and go into QA early next week.

* Intermittent systemd, and repeatable LSB and wic failures in sanity 
tests causing failed build runs.

* Reminder:

oWe have renamed YP 1.9 to YP 2.0.

oThe current version that is in development will launch as YP 2.0 in 
October, 2015.

oThe release name for YP 2.0 is 'jethro'.


Key YP 1.9/2.0 Dates:

YP 2.0 Final - 2.0 Cut off: Sept. 28, 2015 noon GMT (rc1 build in QA)

YP 2.0 final Release Target: Before Oct. 30, 2015


Key Status Links for YP:

https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.9_Status

https://wiki.yoctoproject.org/wiki/Yocto_1.9_Schedule

https://wiki.yoctoproject.org/wiki/Yocto_1.9_Features


Tracking Metrics:

WDD 2055 (last week 2170)

(https://wiki.yoctoproject.org/charts/combo.html)


[If anyone has suggestions for other information you'd like to see on this 
weekly status update, let us know!]

Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*   Work Telephone:  (503) 712-0534
*Cell:(208) 244-4460
* Email: stephen.k.jol...@intel.com

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Status WW41 - Updated

2015-10-09 Thread Jolley, Stephen K 
Current Dev Position: YP 2.0 Final (rc1 out of QA and being reviewed.)

Next Deadline: YP 2.0 Final Release Target: Before Oct. 30, 2015


SWAT team rotation: Cristian -> Randy

https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team


Top Bugs to be tackled (2.0 release blockers):

* systemd timeouts in the sanity tests (#7919, #8141, #8142)

* All LSB builds fail sanity testing (#8452)

* wic fails selftest (#8466)


Key Status/Updates:

* Hopefully everyone at ELC-E is having a good time!

* Jethro has branched, current master and jethro are identical and 
master will track jethro for now.

* RC1 is out of QA and the results from QA are being reviewed.  RC2 
will be built and go into QA early next week, assuming fixes become available.

* Intermittent systemd, and repeatable LSB and wic failures in sanity 
tests causing failed build runs are high priority issues which will block 
release.


Reminders:

* We have renamed YP 1.9 to YP 2.0.

* The current version that is in development will launch as YP 2.0 in 
October, 2015.

* The release name for YP 2.0 is 'jethro'.


Key YP 1.9/2.0 Dates:

YP 2.0 Final - 2.0 Cut off: Sept. 28, 2015 noon GMT (rc1 build in QA)

YP 2.0 final Release Target: Before Oct. 30, 2015


Key Status Links for YP:

https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.9_Status

https://wiki.yoctoproject.org/wiki/Yocto_1.9_Schedule

https://wiki.yoctoproject.org/wiki/Yocto_1.9_Features


Tracking Metrics:

WDD 2055 (last week 2170)

(https://wiki.yoctoproject.org/charts/combo.html)


[If anyone has suggestions for other information you'd like to see on this 
weekly status update, let us know!]

Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*   Work Telephone:  (503) 712-0534
*Cell:(208) 244-4460
* Email: stephen.k.jol...@intel.com

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Can any one please tell the what is the exact difference between DEPENDS and RDEPENDS

2015-10-09 Thread Burton, Ross 
On 9 October 2015 at 10:16, Vivek Per  wrote:

>  I have one more doubt when RDEPENDS variable depends is packages . Do you
> know why RDEPENDS variable in (rootfs-image.bb recipe) which inherit
> core-image. why RDEPENDS cant able to install packages in final roofs image
> apart from IMAGE_INSTALL .
>

Because an image isn't a package.  RDEPENDS works on packages.  To specify
what goes into an image, use IMAGE_INSTALL and related variables.

Ross
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] kernel-module- prefix for out-of-tree modules mandatory?

2015-10-09 Thread Daniel. 
Thanks!!
Em 09/10/2015 04:25, "Khem Raj"  escreveu:

>
> > On Oct 8, 2015, at 1:29 PM, Daniel.  wrote:
> >
> > Hi all,
> >
> > Is the kernel-module- prefix mandatory for out-of-tree modules
> > compiled inside Yocto? And, This prefix applies to package names or
> > recipe names? Should I rename my recipe file with this prefix or setup
> > PN stuff?
>
> if you inherit module bbclass then the split will happen automatically
> you can name your recipe anything you like, the naming applies to out
> packages only
>
> >
> > Cheers,
> >
> > --
> > "Do or do not. There is no try"
> >  Yoda Master
> > --
> > ___
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[linux-yocto] [PATCH 0/2] Intel Axxia updates to yocto-kernel-cache yocto-4.1

2015-10-09 Thread Cristian Bercaru 
This series of patches adds the config fragments needed to build the
kernel for Axxia platforms 5500 (axxiaarm) and 5600 (axxiaarm64).
Please apply them on the 'yocto-4.1' branch from
git.yoctoproject.org/yocto-kernel-cache

Thank you,
Cristian Bercaru (2):
  bsp: add config fragments for Axxia 5500
  bsp: add config fragments for Axxia 5600

 bsp/axxiaarm/axxiaarm-preempt-rt.scc |8 +
 bsp/axxiaarm/axxiaarm-standard.scc   |8 +
 bsp/axxiaarm/axxiaarm.cfg|  280 ++
 bsp/axxiaarm/axxiaarm.scc|   12 ++
 bsp/axxiaarm/edac.cfg|   20 +++
 bsp/axxiaarm/edac.scc|4 +
 bsp/axxiaarm/hardware.kcf|1 +
 bsp/axxiaarm/kvm.cfg |   19 ++
 bsp/axxiaarm/kvm.scc |4 +
 bsp/axxiaarm/rapidio.cfg |   25 +++
 bsp/axxiaarm/rapidio.scc |4 +
 bsp/axxiaarm64/axxiaarm64-preempt-rt.scc |8 +
 bsp/axxiaarm64/axxiaarm64-standard.scc   |8 +
 bsp/axxiaarm64/axxiaarm64.cfg|  239 +
 bsp/axxiaarm64/axxiaarm64.scc|6 +
 bsp/axxiaarm64/hardware.kcf  |1 +
 bsp/axxiaarm64/kvm.cfg   |   18 ++
 bsp/axxiaarm64/kvm.scc   |4 +
 18 files changed, 669 insertions(+)
 create mode 100644 bsp/axxiaarm/axxiaarm-preempt-rt.scc
 create mode 100644 bsp/axxiaarm/axxiaarm-standard.scc
 create mode 100644 bsp/axxiaarm/axxiaarm.cfg
 create mode 100644 bsp/axxiaarm/axxiaarm.scc
 create mode 100644 bsp/axxiaarm/edac.cfg
 create mode 100644 bsp/axxiaarm/edac.scc
 create mode 100644 bsp/axxiaarm/hardware.kcf
 create mode 100644 bsp/axxiaarm/kvm.cfg
 create mode 100644 bsp/axxiaarm/kvm.scc
 create mode 100644 bsp/axxiaarm/rapidio.cfg
 create mode 100644 bsp/axxiaarm/rapidio.scc
 create mode 100644 bsp/axxiaarm64/axxiaarm64-preempt-rt.scc
 create mode 100644 bsp/axxiaarm64/axxiaarm64-standard.scc
 create mode 100644 bsp/axxiaarm64/axxiaarm64.cfg
 create mode 100644 bsp/axxiaarm64/axxiaarm64.scc
 create mode 100644 bsp/axxiaarm64/hardware.kcf
 create mode 100644 bsp/axxiaarm64/kvm.cfg
 create mode 100644 bsp/axxiaarm64/kvm.scc

-- 
1.7.9.5

-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

[linux-yocto] [PATCH 2/2] bsp: add config fragments for Axxia 5600

2015-10-09 Thread Cristian Bercaru 
Add the configuration fragments needed to build the 4.1 standard and
preempt-rt linux kernel for the Axxia 5600 platform, based on the arm
64-bit architecture.

Signed-off-by: Cristian Bercaru 
---
 bsp/axxiaarm64/axxiaarm64-preempt-rt.scc |8 +
 bsp/axxiaarm64/axxiaarm64-standard.scc   |8 +
 bsp/axxiaarm64/axxiaarm64.cfg|  239 ++
 bsp/axxiaarm64/axxiaarm64.scc|6 +
 bsp/axxiaarm64/hardware.kcf  |1 +
 bsp/axxiaarm64/kvm.cfg   |   18 +++
 bsp/axxiaarm64/kvm.scc   |4 +
 7 files changed, 284 insertions(+)
 create mode 100644 bsp/axxiaarm64/axxiaarm64-preempt-rt.scc
 create mode 100644 bsp/axxiaarm64/axxiaarm64-standard.scc
 create mode 100644 bsp/axxiaarm64/axxiaarm64.cfg
 create mode 100644 bsp/axxiaarm64/axxiaarm64.scc
 create mode 100644 bsp/axxiaarm64/hardware.kcf
 create mode 100644 bsp/axxiaarm64/kvm.cfg
 create mode 100644 bsp/axxiaarm64/kvm.scc

diff --git a/bsp/axxiaarm64/axxiaarm64-preempt-rt.scc 
b/bsp/axxiaarm64/axxiaarm64-preempt-rt.scc
new file mode 100644
index 000..8f3b075
--- /dev/null
+++ b/bsp/axxiaarm64/axxiaarm64-preempt-rt.scc
@@ -0,0 +1,8 @@
+define KMACHINE axxiaarm64
+define KTYPE preempt-rt
+define KARCH arm64
+
+include ktypes/preempt-rt
+branch axxia
+
+include axxiaarm64.scc
diff --git a/bsp/axxiaarm64/axxiaarm64-standard.scc 
b/bsp/axxiaarm64/axxiaarm64-standard.scc
new file mode 100644
index 000..d9e57fe
--- /dev/null
+++ b/bsp/axxiaarm64/axxiaarm64-standard.scc
@@ -0,0 +1,8 @@
+define KMACHINE axxiaarm64
+define KTYPE standard
+define KARCH arm64
+
+include ktypes/standard
+branch axxia
+
+include axxiaarm64.scc
diff --git a/bsp/axxiaarm64/axxiaarm64.cfg b/bsp/axxiaarm64/axxiaarm64.cfg
new file mode 100644
index 000..4cabaf0
--- /dev/null
+++ b/bsp/axxiaarm64/axxiaarm64.cfg
@@ -0,0 +1,239 @@
+#.
+#WARNING
+#
+# This file is a kernel configuration fragment, and not a full kernel
+# configuration file.  The final kernel configuration is made up of
+# an assembly of processed fragments, each of which is designed to
+# capture a specific part of the final configuration (e.g. platform
+# configuration, feature configuration, and board specific hardware
+# configuration).  For more information on kernel configuration, please
+# consult the product documentation.
+#
+#.
+
+#
+# General setup
+#
+# CONFIG_FHANDLE is not set
+CONFIG_AUDIT=y
+
+#
+# Timers subsystem
+#
+CONFIG_NO_HZ_IDLE=y
+
+#
+# Platform selection
+#
+CONFIG_ARCH_AXXIA=y
+CONFIG_ARCH_THUNDER=y
+CONFIG_ARCH_VEXPRESS=y
+CONFIG_ARCH_XGENE=y
+
+#
+# Processor Features
+#
+CONFIG_ARCH_PHYS_ADDR_T_64BIT=y
+CONFIG_ARCH_DMA_ADDR_T_64BIT=y
+CONFIG_ARM_ARCH_TIMER=y
+
+#
+# Boot options
+#
+CONFIG_CMDLINE="console=ttyAMA0"
+
+#
+# Bus support
+#
+CONFIG_ARM_AMBA=y
+CONFIG_PCI=y
+CONFIG_PCI_DOMAINS=y
+CONFIG_PCI_SYSCALL=y
+CONFIG_PCI_MSI=y
+
+#
+# Kernel Features
+#
+CONFIG_SMP=y
+
+#
+# Generic Driver Options
+#
+CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
+CONFIG_FW_LOADER=y
+CONFIG_DMA_CMA=y
+
+CONFIG_MTD=y
+CONFIG_MTD_OF_PARTS=y
+
+#
+# Network testing
+#
+# CONFIG_WIRELESS is not set
+
+#
+# Generic Driver Options
+#
+CONFIG_REGMAP=y
+CONFIG_REGMAP_MMIO=y
+
+#
+# Bus devices
+#
+CONFIG_ARM_CCI=y
+
+#
+# LPDDR & LPDDR2 PCM memory drivers
+#
+CONFIG_MTD_M25P80=y
+CONFIG_MTD_SPI_NOR=y
+CONFIG_DTC=y
+CONFIG_OF=y
+
+#
+# Device Tree and Open Firmware support
+#
+CONFIG_BLK_DEV_LOOP=y
+CONFIG_BLK_DEV_RAM_SIZE=35000
+
+#
+# Misc devices
+#
+CONFIG_LSI_MTC=y
+CONFIG_ATA=y
+
+#
+# SCSI device support
+#
+# CONFIG_SCSI_PROC_FS is not set
+
+#
+# SCSI support type (disk, tape, CD-ROM)
+#
+# CONFIG_SCSI_LOWLEVEL is not set
+
+#
+# Controllers with non-SFF native interface
+#
+CONFIG_SATA_AHCI=y
+CONFIG_SATA_AHCI_PLATFORM=y
+CONFIG_AHCI_XGENE=y
+
+#
+# Hardware I/O ports
+#
+CONFIG_SERIO_AMBAKMI=y
+
+#
+# Serial drivers
+#
+CONFIG_SERIAL_8250=y
+CONFIG_SERIAL_8250_CONSOLE=y
+
+#
+# Non-8250 serial port support
+#
+CONFIG_SERIAL_AMBA_PL011=y
+CONFIG_SERIAL_AMBA_PL011_CONSOLE=y
+CONFIG_SERIAL_OF_PLATFORM=y
+CONFIG_HW_RANDOM=y
+CONFIG_HW_RANDOM_AXXIA=y
+# CONFIG_HW_RANDOM_XGENE is not set
+CONFIG_I2C=y
+CONFIG_I2C_CHARDEV=y
+CONFIG_I2C_MUX=y
+CONFIG_I2C_AXXIA=y
+
+CONFIG_SPI=y
+CONFIG_SPI_PL022=y
+CONFIG_SPI_SPIDEV=y
+
+#
+# Memory mapped GPIO drivers:
+#
+CONFIG_GPIOLIB=y
+CONFIG_GPIO_SYSFS=y
+CONFIG_GPIO_PL061=y
+CONFIG_GPIO_GENERIC_PLATFORM=y
+CONFIG_GPIO_XGENE=y
+
+#
+# Distributed Switch Architecture drivers
+#
+CONFIG_ETHERNET=y
+CONFIG_NET_XGENE=y
+# CONFIG_NET_LSI_FEMAC is not set
+CONFIG_SMC91X=y
+CONFIG_SMSC911X=y
+
+#
+# MII PHY device drivers
+#
+CONFIG_MICREL_PHY=y
+CONFIG_FIXED_PHY=y
+CONFIG_MICREL_KS8995MA=y
+# CONFIG_PPP is not set
+# CONFIG_SLIP is not set
+
+#
+# Hardware I/O ports
+#
+#

[linux-yocto] [PATCH 1/2] bsp: add config fragments for Axxia 5500

2015-10-09 Thread Cristian Bercaru 
Add the configuration fragments needed to build the 4.1 standard and
preempt-rt linux kernel for the Axxia 5500 platform, based on the arm
32-bit architecture.

Signed-off-by: Cristian Bercaru 
---
 bsp/axxiaarm/axxiaarm-preempt-rt.scc |8 +
 bsp/axxiaarm/axxiaarm-standard.scc   |8 +
 bsp/axxiaarm/axxiaarm.cfg|  280 ++
 bsp/axxiaarm/axxiaarm.scc|   12 ++
 bsp/axxiaarm/edac.cfg|   20 +++
 bsp/axxiaarm/edac.scc|4 +
 bsp/axxiaarm/hardware.kcf|1 +
 bsp/axxiaarm/kvm.cfg |   19 +++
 bsp/axxiaarm/kvm.scc |4 +
 bsp/axxiaarm/rapidio.cfg |   25 +++
 bsp/axxiaarm/rapidio.scc |4 +
 11 files changed, 385 insertions(+)
 create mode 100644 bsp/axxiaarm/axxiaarm-preempt-rt.scc
 create mode 100644 bsp/axxiaarm/axxiaarm-standard.scc
 create mode 100644 bsp/axxiaarm/axxiaarm.cfg
 create mode 100644 bsp/axxiaarm/axxiaarm.scc
 create mode 100644 bsp/axxiaarm/edac.cfg
 create mode 100644 bsp/axxiaarm/edac.scc
 create mode 100644 bsp/axxiaarm/hardware.kcf
 create mode 100644 bsp/axxiaarm/kvm.cfg
 create mode 100644 bsp/axxiaarm/kvm.scc
 create mode 100644 bsp/axxiaarm/rapidio.cfg
 create mode 100644 bsp/axxiaarm/rapidio.scc

diff --git a/bsp/axxiaarm/axxiaarm-preempt-rt.scc 
b/bsp/axxiaarm/axxiaarm-preempt-rt.scc
new file mode 100644
index 000..e1c2aec
--- /dev/null
+++ b/bsp/axxiaarm/axxiaarm-preempt-rt.scc
@@ -0,0 +1,8 @@
+define KMACHINE axxiaarm
+define KTYPE preempt-rt
+define KARCH arm
+
+include ktypes/preempt-rt
+branch axxia
+
+include axxiaarm.scc
diff --git a/bsp/axxiaarm/axxiaarm-standard.scc 
b/bsp/axxiaarm/axxiaarm-standard.scc
new file mode 100644
index 000..cc57a7e
--- /dev/null
+++ b/bsp/axxiaarm/axxiaarm-standard.scc
@@ -0,0 +1,8 @@
+define KMACHINE axxiaarm
+define KTYPE standard
+define KARCH arm
+
+include ktypes/standard
+branch axxia
+
+include axxiaarm.scc
diff --git a/bsp/axxiaarm/axxiaarm.cfg b/bsp/axxiaarm/axxiaarm.cfg
new file mode 100644
index 000..bfa0862
--- /dev/null
+++ b/bsp/axxiaarm/axxiaarm.cfg
@@ -0,0 +1,280 @@
+#.
+#WARNING
+#
+# This file is a kernel configuration fragment, and not a full kernel
+# configuration file.  The final kernel configuration is made up of
+# an assembly of processed fragments, each of which is designed to
+# capture a specific part of the final configuration (e.g. platform
+# configuration, feature configuration, and board specific hardware
+# configuration).  For more information on kernel configuration, please
+# consult the product documentation.
+#
+#.
+
+#
+# System Type
+#
+CONFIG_ARCH_AXXIA=y
+
+#
+# Axxia platform type
+#
+CONFIG_ARCH_AXXIA_GIC=y
+CONFIG_ARCH_AXXIA_DT=y
+CONFIG_ARM_TIMER_SP804=y
+
+#
+# Processor Features
+#
+CONFIG_ARM_LPAE=y
+CONFIG_ARCH_PHYS_ADDR_T_64BIT=y
+CONFIG_ARCH_DMA_ADDR_T_64BIT=y
+CONFIG_ARM_ARCH_TIMER=y
+CONFIG_ARM_THUMBEE=y
+CONFIG_OUTER_CACHE=y
+CONFIG_OUTER_CACHE_SYNC=y
+CONFIG_MIGHT_HAVE_CACHE_L2X0=y
+CONFIG_CACHE_L2X0=y
+
+CONFIG_ARM_ERRATA_430973=y
+CONFIG_ARM_ERRATA_458693=y
+CONFIG_ARM_ERRATA_460075=y
+CONFIG_ARM_ERRATA_643719=y
+CONFIG_ARM_ERRATA_742230=y
+CONFIG_ARM_ERRATA_742231=y
+CONFIG_ARM_ERRATA_720789=y
+CONFIG_ARM_ERRATA_743622=y
+CONFIG_ARM_ERRATA_751472=y
+CONFIG_ARM_ERRATA_754322=y
+CONFIG_ARM_ERRATA_754327=y
+CONFIG_ARM_ERRATA_764369=y
+CONFIG_ARM_ERRATA_775420=y
+CONFIG_ARM_ERRATA_798181=y
+CONFIG_PL310_ERRATA_588369=y
+CONFIG_PL310_ERRATA_727915=y
+CONFIG_PL310_ERRATA_753970=y
+CONFIG_PL310_ERRATA_769419=y
+
+#
+# Bus support
+#
+CONFIG_ARM_AMBA=y
+CONFIG_PCI=y
+CONFIG_PCI_DOMAINS=y
+CONFIG_PCI_SYSCALL=y
+CONFIG_PCI_MSI=y
+
+#
+# Kernel Features
+#
+CONFIG_SMP=y
+CONFIG_HAVE_ARM_ARCH_TIMER=y
+CONFIG_HIGHMEM=y
+CONFIG_NR_CPUS=16
+
+#
+# Boot options
+#
+CONFIG_USE_OF=y
+CONFIG_ARM_APPENDED_DTB=y
+CONFIG_ZBOOT_ROM_TEXT=0x0
+CONFIG_ZBOOT_ROM_BSS=0x0
+CONFIG_ARM_ATAG_DTB_COMPAT=y
+
+#
+# At least one emulation must be selected
+#
+CONFIG_VFP=y
+CONFIG_NEON=y
+
+CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
+CONFIG_FW_LOADER=y
+
+CONFIG_MTD=y
+CONFIG_MTD_CMDLINE_PARTS=y
+CONFIG_MTD_AFS_PARTS=y
+CONFIG_MTD_OF_PARTS=y
+CONFIG_MTD_PHYSMAP=y
+CONFIG_MTD_PHYSMAP_OF=y
+
+#
+# Network testing
+#
+# CONFIG_WIRELESS is not set
+
+#
+# Generic Driver Options
+#
+CONFIG_REGMAP=y
+CONFIG_REGMAP_MMIO=y
+
+#
+# Bus devices
+#
+CONFIG_ARM_CCI=y
+
+#
+# User Modules And Translation Layers
+#
+CONFIG_MTD_BLKDEVS=y
+CONFIG_MTD_BLOCK=y
+
+#
+# RAM/ROM/Flash chip drivers
+#
+CONFIG_MTD_CFI=y
+CONFIG_MTD_CFI_INTELEXT=y
+CONFIG_MTD_CFI_AMDSTD=y
+CONFIG_MTD_CFI_STAA=y
+
+#
+# Self-contained MTD device drivers
+#
+CONFIG_MTD_M25P80=y
+CONFIG_MTD_SPI_NOR=y
+
+CONFIG_DTC=y
+CONFIG_OF=y
+
+CONFIG_BLK_DEV_LOOP=y
+
+#
+# Misc devices
+#

[linux-yocto] [PATCH 0/2] Intel Axxia updates to yocto-kernel-cache yocto-3.14

2015-10-09 Thread Cristian Bercaru 
This series of patches removes unnecesary options from the
configuration fragments needed to build the kernel for Axxia platforms
5500 (axxiaarm) and 3000 (axxiapowerpc).
Please apply them on the 'yocto-3.14' branch from
git.yoctoproject.org/yocto-kernel-cache

Thank you,
Cristian Bercaru (2):
  bsp: axxiaarm: remove unnecesary options
  bsp: axxiapowerpc: remove unnecesary options

 bsp/axxiaarm/axxiaarm-standard.scc |1 -
 bsp/axxiaarm/axxiaarm.cfg  |   14 --
 bsp/axxiaarm/axxiaarm.scc  |6 ++
 bsp/axxiaarm/edac.cfg  |   13 +
 bsp/axxiaarm/kvm.cfg   |   15 +--
 bsp/axxiaarm/no-preempt.cfg|1 -
 bsp/axxiaarm/no-preempt.scc|1 -
 bsp/axxiaarm/rapidio.cfg   |   13 +
 bsp/axxiapowerpc/axxiapowerpc-standard.scc |1 -
 bsp/axxiapowerpc/axxiapowerpc.cfg  |4 +---
 bsp/axxiapowerpc/axxiapowerpc.scc  |9 +++--
 bsp/axxiapowerpc/no-preempt.cfg|1 -
 bsp/axxiapowerpc/no-preempt.scc|1 -
 bsp/axxiapowerpc/rapidio.cfg   |   13 +
 14 files changed, 58 insertions(+), 35 deletions(-)
 delete mode 100644 bsp/axxiaarm/no-preempt.cfg
 delete mode 100644 bsp/axxiaarm/no-preempt.scc
 delete mode 100644 bsp/axxiapowerpc/no-preempt.cfg
 delete mode 100644 bsp/axxiapowerpc/no-preempt.scc

-- 
1.7.9.5

-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

[linux-yocto] [PATCH 1/2] bsp: axxiaarm: remove unnecesary options

2015-10-09 Thread Cristian Bercaru 
This patch removes the unnecesary options from the Axxia 5500 config
fragments.

Signed-off-by: Cristian Bercaru 
---
 bsp/axxiaarm/axxiaarm-standard.scc |1 -
 bsp/axxiaarm/axxiaarm.cfg  |   14 --
 bsp/axxiaarm/axxiaarm.scc  |6 ++
 bsp/axxiaarm/edac.cfg  |   13 +
 bsp/axxiaarm/kvm.cfg   |   15 +--
 bsp/axxiaarm/no-preempt.cfg|1 -
 bsp/axxiaarm/no-preempt.scc|1 -
 bsp/axxiaarm/rapidio.cfg   |   13 +
 8 files changed, 41 insertions(+), 23 deletions(-)
 delete mode 100644 bsp/axxiaarm/no-preempt.cfg
 delete mode 100644 bsp/axxiaarm/no-preempt.scc

diff --git a/bsp/axxiaarm/axxiaarm-standard.scc 
b/bsp/axxiaarm/axxiaarm-standard.scc
index ab6be36..cc57a7e 100644
--- a/bsp/axxiaarm/axxiaarm-standard.scc
+++ b/bsp/axxiaarm/axxiaarm-standard.scc
@@ -6,4 +6,3 @@ include ktypes/standard
 branch axxia
 
 include axxiaarm.scc
-include no-preempt.scc
diff --git a/bsp/axxiaarm/axxiaarm.cfg b/bsp/axxiaarm/axxiaarm.cfg
index a5610d2..58b4eb7 100644
--- a/bsp/axxiaarm/axxiaarm.cfg
+++ b/bsp/axxiaarm/axxiaarm.cfg
@@ -16,7 +16,6 @@
 #
 CONFIG_ARCH_AXXIA=y
 
-
 #
 # Axxia platform type
 #
@@ -24,7 +23,6 @@ CONFIG_ARCH_AXXIA_GIC=y
 CONFIG_ARCH_AXXIA_DT=y
 CONFIG_ARM_TIMER_SP804=y
 
-
 #
 # Processor Features
 #
@@ -63,11 +61,9 @@ CONFIG_PL310_ERRATA_769419=y
 # Bus support
 #
 CONFIG_ARM_AMBA=y
-CONFIG_ARM_CCN=y
 CONFIG_PCI=y
 CONFIG_PCI_DOMAINS=y
 CONFIG_PCI_SYSCALL=y
-CONFIG_ARCH_SUPPORTS_MSI=y
 CONFIG_PCI_MSI=y
 
 #
@@ -137,7 +133,6 @@ CONFIG_MTD_CFI_STAA=y
 # Self-contained MTD device drivers
 #
 CONFIG_MTD_M25P80=y
-CONFIG_M25PXX_USE_FAST_READ=y
 
 CONFIG_DTC=y
 CONFIG_OF=y
@@ -150,10 +145,8 @@ CONFIG_BLK_DEV_LOOP=y
 #
 CONFIG_LSI_MTC=y
 CONFIG_LSI_NCR=y
-CONFIG_SCSI=y
 CONFIG_ATA=y
 
-
 #
 # EEPROM support
 #
@@ -204,11 +197,6 @@ CONFIG_WATCHDOG=y
 CONFIG_ARM_SP805_WATCHDOG=y
 
 #
-# SCSI support type (disk, tape, CD-ROM)
-#
-CONFIG_BLK_DEV_SD=y
-
-#
 # Distributed Switch Architecture drivers
 #
 CONFIG_ETHERNET=y
@@ -224,7 +212,6 @@ CONFIG_IGB_HWMON=y
 CONFIG_IGBVF=y
 CONFIG_SMC91X=y
 
-
 #
 # USB Network Adapters
 #
@@ -285,7 +272,6 @@ CONFIG_FSCACHE_OBJECT_LIST=y
 CONFIG_CACHEFILES=y
 CONFIG_CACHEFILES_HISTOGRAM=y
 
-
 #
 # MMC/SD/SDIO Card Drivers
 #
diff --git a/bsp/axxiaarm/axxiaarm.scc b/bsp/axxiaarm/axxiaarm.scc
index 6832186..dccecbf 100644
--- a/bsp/axxiaarm/axxiaarm.scc
+++ b/bsp/axxiaarm/axxiaarm.scc
@@ -1,10 +1,6 @@
 # Core arm configuation settings
 include arch/arm/arm.scc nopatch
 
-kconf hardware axxiaarm.cfg
-
-include features/profiling/profiling.scc
-include features/latencytop/latencytop.scc
 include features/usb/ehci-hcd.scc
 include cfg/usb-mass-storage.scc
 include cfg/virtio.scc
@@ -12,3 +8,5 @@ include cfg/virtio.scc
 include rapidio.scc
 include edac.scc
 include kvm.scc
+
+kconf hardware axxiaarm.cfg
diff --git a/bsp/axxiaarm/edac.cfg b/bsp/axxiaarm/edac.cfg
index 840af5d..25ad058 100644
--- a/bsp/axxiaarm/edac.cfg
+++ b/bsp/axxiaarm/edac.cfg
@@ -1,3 +1,16 @@
+#.
+#WARNING
+#
+# This file is a kernel configuration fragment, and not a full kernel
+# configuration file.  The final kernel configuration is made up of
+# an assembly of processed fragments, each of which is designed to
+# capture a specific part of the final configuration (e.g. platform
+# configuration, feature configuration, and board specific hardware
+# configuration).  For more information on kernel configuration, please
+# consult the product documentation.
+#
+#.
+
 CONFIG_EDAC=y
 CONFIG_EDAC_MM_EDAC=y
 CONFIG_EDAC_AXXIA_SYSMEM=y
diff --git a/bsp/axxiaarm/kvm.cfg b/bsp/axxiaarm/kvm.cfg
index a6003e4..146687f 100644
--- a/bsp/axxiaarm/kvm.cfg
+++ b/bsp/axxiaarm/kvm.cfg
@@ -1,7 +1,18 @@
+#.
+#WARNING
+#
+# This file is a kernel configuration fragment, and not a full kernel
+# configuration file.  The final kernel configuration is made up of
+# an assembly of processed fragments, each of which is designed to
+# capture a specific part of the final configuration (e.g. platform
+# configuration, feature configuration, and board specific hardware
+# configuration).  For more information on kernel configuration, please
+# consult the product documentation.
+#
+#.
+
 CONFIG_VIRTUALIZATION=y
 CONFIG_KVM=y
-CONFIG_KVM_ARM_HOST=y
 CONFIG_KVM_ARM_MAX_VCPUS=4
 CONFIG_KVM_ARM_VGIC=y
 CONFIG_KVM_ARM_TIMER=y
-CONFIG_KVM_MMIO=y
diff --git a/bsp/axxiaarm/no-preempt.cfg b/bsp/axxiaarm/no-preempt.cfg
deleted file mode 100644
index 0cbeb5a..000
--- a/bsp/axxiaarm/no-preempt.cfg
+++ /dev/null
@@ -1 +0,0 @@
-CONFIG_PREEMPT_NONE=y
diff

Re: [yocto] Intelligent global config files setting

2015-10-09 Thread Burton, Ross 
On 9 October 2015 at 08:38, Gilles CARRY  wrote:

> I tried to use ROOTFS_POSTPROCESS_COMMAND in c1.bb and c2.bb but this
> mechanism only seems to work in images recipes. (inherit core-image)
>
>
Use a package postinst to modify the configuration files when the rootfs is
generated?

Ross
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Intelligent global config files setting

2015-10-09 Thread Gilles CARRY 
Yes, this looks good.
I was not aware of this postinst mechanism.
Thanks for the answer.

From: Burton, Ross [mailto:ross.bur...@intel.com]
Sent: Friday, October 09, 2015 12:40 PM
To: Gilles CARRY
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Intelligent global config files setting


On 9 October 2015 at 08:38, Gilles CARRY 
> wrote:
I tried to use ROOTFS_POSTPROCESS_COMMAND in c1.bb and 
c2.bb but this mechanism only seems to work in images recipes. 
(inherit core-image)

Use a package postinst to modify the configuration files when the rootfs is 
generated?

Ross
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] VFAT patent EP 0 618 540

2015-10-09 Thread Robert Berger 
Hi,

On 10/09/2015 11:36 AM, Gorny Krystian wrote:
> Hi,
> 
> I have a question regarding the VFAT patent (EP 0 618 540) owned by
> Microsoft. It’s about common name space for long and short filenames. I
> have read that this patent was canceled by Germany / EU, but it’s still
> available in the US right? So is there a patch/option where we can
> activate to avoid this patent?

I am not a lawyer, but wouldn't it be easier not to use VFAT?
The only reason I would use it, would be because the bootloader of my
SoC would only be able to boot over FAT/FAT32 from a managed flash. A
patch will not help here as well;)

There are rumors that a fix was implemented a long time ago[1] ;)

> 
> Thanks
> 
> Krystian
> 

Regards,

Robert


[1]
http://arstechnica.com/information-technology/2009/07/vfat-linux-patch-could-circumvent-microsofts-patent-claims/

> 
> Legal information:
> Wipotec Wiege- und Positioniersysteme GmbH
> HRB 2317 Kaiserslautern, Management: T. Düppre, U. Wagner
> 
> This e-mail may contain confidential and/or privileged information.
> If you are not the intended recipient (or have received this e-mail in
> error)
> please notify the sender immediately and delete this e-mail. Any
> unauthorized
> copying, disclosure or distribution of the material in this e-mail is
> strictly
> forbidden.
> 

Since you are concerned about legal issues you might also want to remove
this footer when posting to public lists ;)

> 
> -- 
> 

..."Rules of Optimization: Rule1: Don't do it. Rule 2 (for experts
only): Don't do it yet." - M.A. Jackson (not the singer)

My public pgp key is available,at:
http://pgp.mit.edu:11371/pks/lookup?op=get=0x90320BF1


-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] VFAT patent EP 0 618 540

2015-10-09 Thread Christian Ege 
Hi,
Am 09.10.2015 8:31 nachm. schrieb "Robert Berger" <
gm...@reliableembeddedsystems.com>:
>
> Hi,
>
> On 10/09/2015 11:36 AM, Gorny Krystian wrote:
> > Hi,
> >
> > I have a question regarding the VFAT patent (EP 0 618 540) owned by
> > Microsoft. It’s about common name space for long and short filenames. I
> > have read that this patent was canceled by Germany / EU, but it’s still
> > available in the US right? So is there a patch/option where we can
> > activate to avoid this patent?
>
> I am not a lawyer, but wouldn't it be easier not to use VFAT?
> The only reason I would use it, would be because the bootloader of my
> SoC would only be able to boot over FAT/FAT32 from a managed flash. A
> patch will not help here as well;)
A decent U-Boot can load the kernel from ext4. And I do not know any ROM
loader which needs vfat, except maybe this TI SOCs...

Regards,
Christian
>
> There are rumors that a fix was implemented a long time ago[1] ;)
>
> >
> > Thanks
> >
> > Krystian
> >
>
> Regards,
>
> Robert
>
>
> [1]
>
http://arstechnica.com/information-technology/2009/07/vfat-linux-patch-could-circumvent-microsofts-patent-claims/
>
> >
> > Legal information:
> > Wipotec Wiege- und Positioniersysteme GmbH
> > HRB 2317 Kaiserslautern, Management: T. Düppre, U. Wagner
> >
> > This e-mail may contain confidential and/or privileged information.
> > If you are not the intended recipient (or have received this e-mail in
> > error)
> > please notify the sender immediately and delete this e-mail. Any
> > unauthorized
> > copying, disclosure or distribution of the material in this e-mail is
> > strictly
> > forbidden.
> >
>
> Since you are concerned about legal issues you might also want to remove
> this footer when posting to public lists ;)
>
> >
> > --
> >
>
> ..."Rules of Optimization: Rule1: Don't do it. Rule 2 (for experts
> only): Don't do it yet." - M.A. Jackson (not the singer)
>
> My public pgp key is available,at:
> http://pgp.mit.edu:11371/pks/lookup?op=get=0x90320BF1
>
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto