Re: [yocto] VFAT patent EP 0 618 540

[Gorny Krystian]

Hi,

exactly Chris it's for sharing Data on external media like USB. I found a 
workaround in the kernel menuconfig it's working fine. The entry for the 
workaround is in the menu:

> File systems
>> DOS/FAT/NT Filesystems
>>> disable VFAT Dual names support (patent workaround)

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


_

Weigh Cells | Weighing systems

See our solutions. Visit us at our events
http://www.wipotec.com/de/aktuelles/veranstaltungen/

_

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.

-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Chris Simmonds
Sent: Sunday, October 11, 2015 3:17 PM
To: yocto@yoctoproject.org
Subject: Re: [yocto] VFAT patent EP 0 618 540

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=0x90320BF1
>
>
--
Chris Simmonds, Consultant, 2net Ltd
http://www.2net.co.uk
+44 (0)1962 869003

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

[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

[yocto] Autologin after bootup on the genericx86 machine

[Gorny Krystian]

Hi,

I'm using the fido branch and building a genericx86 machine for the 
core-image-rt image.
After my image boot up I always need to login as root first, is there a way to 
login and start my application automatically? I can't find an easy way to do 
this.

Best
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

[yocto] Kernel panic - not syncing: No working init found.

[Gorny Krystian]

Hi,

I have a problem with booting my Linux image. The boot error message is:

(...)
VFS: Mounted root (vfat filesystem) readonly on device 3:1.
Devtmpfs: error mounting -2
Freeing unused kernel memory: 636K (c1aa6000 - c1b45000)
Write protecting the kernel text: 7544k
Write protecting the kernel read-only  data: 2800k
Kernel panic - not syncing: No working init found. Try passing init= option to 
kernel. See Linux Documentation/init.txt for guidance.
CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.14.39ltsi-rt37-yocto-preempt-rt #1
(...)

I'm using the fido branch and build an core-image-rt for the genericx86 
machine. Create the yocto image works well. I have used the 
https://wiki.yoctoproject.org/wiki/How_do_I#Q:_How_do_I_put_Yocto_on_a_hard_drive.3F
 instructions to put my image to the hard drive. I use ext4 as file system. 
When I put the image to a VirtualBox hard drive the virtual machine boots 
correctly without issues. This issue occur only on my real hardware (industrial 
pc with intel atom cpu).

I already tried to put init=/sbin/init or init=/sbin/init.sysvinit to grub.cfg 
without success. Any ideas?

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]http://www.wipotec.com

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

[yocto] Kernel header missing for specific Target

[Gorny Krystian]

Hi

I try add to my core-image-rt image on a x86 arch my own IO driver. I have 
already my own recipe, for normal user space programs everything is working 
fine.
For the kernel space driver Yocto is missing at do_comile task the asm/atomic.h 
header file. I have searched for the atomic.h file and found a lot of them in 
the ./build/tmp/work folder. Yocto should use one of them for the right 
hardware architecture right? Or is the a something else I have forget to do?

Many 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]http://www.wipotec.com

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] Kernel header missing for specific Target

[Gorny Krystian]

I'm using the fido branch. My iointerrupt.bb file looks as follow:


DESCRIPTION = Simple IO-interrupt driver
SECTION = iointerrupt
LICENSE = MIT
LIC_FILES_CHKSUM = 
file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302
PR = r0

SRC_URI = file://drv_iointerrupt.c
S = ${WORKDIR}
do_compile() {
 ${CC} drv_iointerrupt.c -o iointerrupt
}
do_install() {
 install -d ${D}${bindir}
 install -m 0755 iointerrupt ${D}${bindir}
}

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


_

Weigh Cells | Weighing systems

See our solutions. Visit us at our events
http://www.wipotec.com/de/aktuelles/veranstaltungen/

_

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.

-Original Message-
From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com]
Sent: Friday, July 17, 2015 3:32 PM
To: Gorny Krystian; yocto@yoctoproject.org
Subject: Re: [yocto] Kernel header missing for specific Target

On 15-07-17 08:47 AM, Gorny Krystian wrote:
 Hi

 I try add to my core-image-rt image on a x86 arch my own IO driver. I
 have already my own recipe, for normal user space programs everything
 is working fine.

 For the kernel space driver Yocto is missing at do_comile task the
 asm/atomic.h header file. I have searched for the atomic.h file and
 found a lot of them in the ./build/tmp/work folder. Yocto should use
 one of them for the right hardware architecture right? Or is the a
 something else I have forget to do?

What Yocto branch are you using ?

atomic.h is placed in the right location by the kernel build, assuming that 
your driver recipe has the proper dependencies.  Without seeing that recipe, it 
is hard to say more.

Cheers,

Bruce


 Many 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

 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

[yocto] Creating image with genericx86 machine and RT-Preempt Patch

[Gorny Krystian]

Hi,

I try to build an image for a x86 architecture with RT-Preemtp Patch. So I use 
the genericx86 machine and try to build the core-image-rt recipe. This fails 
with the following errors:

 ERROR: Nothing PROVIDES 'linux-yocto-rt' (but 
 /media/disk/myYocto/poky/meta/recipes-rt/images/core-image-rt.bb DEPENDS on 
 or otherwise requires it)
 ERROR: linux-yocto-rt was skipped: incompatible with machine genericx86 (not 
 in COMPATIBLE_MACHINE)
 ERROR: Required build target 'core-image-rt' has no buildable providers.
 Missing or unbuildable dependency chain was: ['core-image-rt', 
 'linux-yocto-rt']

So I add the following parameter to my local.conf file:

 COMPATIBLE_MACHINE_genericx86 = genericx86
 COMPATIBLE_MACHINE_quilt-native = genericx86
 PREFERRED_PROVIDER_virtual/kernel = linux-yocto-rt

But I get this error:

 ERROR: Task 80 
 (/media/disk/myYocto/poky/meta/recipes-kernel/linux/linux-yocto-rt_3.14.bb, 
 do_compile) failed with exit code '1'

In the log.do_compile file I see:

 NOTE: make -j 4 bzImage CC=i686-poky-linux-gcc  LD=i686-poky-linux-ld.bfd
 make[3]: Nothing to be done for `all'.
   CHK include/config/kernel.release
   GEN 
 /media/disk/myYocto/poky/build/tmp/work/genericx86-poky-linux/linux-yocto-rt/3.14.36+gitAUTOINC+a996d95104_3428de7103-r0/linux-genericx86preempt-$
   CHK include/generated/uapi/linux/version.h
   CHK include/generated/utsrelease.h
   HOSTCC  scripts/conmakehash
   HOSTCC  scripts/sortextable
   CC  scripts/mod/empty.o
 /media/disk/myYocto/poky/build/tmp/work-shared/genericx86/kernel-source/scripts/mod/empty.c:1:0:
  error: code model 'kernel' not supported in the 32 bit mode
  /* empty file to figure out endianness / word size */
  ^
 /media/disk/myYocto/poky/build/tmp/work-shared/genericx86/kernel-source/scripts/mod/empty.c:1:0:
  sorry, unimplemented: 64-bit mode not compiled in
 make[4]: *** [scripts/mod/empty.o] Error 1
 make[4]: *** Waiting for unfinished jobs
   HOSTCC  scripts/mod/mk_elfconfig
 make[3]: *** [scripts/mod] Error 2
 make[3]: *** Waiting for unfinished jobs
 make[2]: *** [scripts] Error 2
 make[1]: *** [sub-make] Error 2
 make: *** [all] Error 2
 ERROR: oe_runmake failed
 WARNING: exit code 1 from a shell command.

I already tried genericx86_64 machine and it's still not working. Are the 
genericx86 machine incompatible with the core-image-rt recipy? If yes how can I 
build a x86 image with the RT patch?

Many Thanks

_

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]http://www.wipotec.com

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