What PSoCs, MCUs/MCPUs , FPGAs and IoT boards are Linux friendly?

[legacy]

In VMWare you can disable the virtual disk cache; I'd imagine VirtualBox has a similar option.

Umm, it seems it's not really possible as VirtualBox still uses disk-cache internally. Also I have experimented catastrophic disasters when Windows is used in NTFS-compression mode. A colleague wanted to have the option enabled, and on a crash he lost the whole virtual hard drive. Gone completely corrupted. So, NTFS-compression is not a bad idea, I won't recommend it.


btw, the point was: why should I have to use a virtual hard drive when I can access a physical partition which makes me able to have the same rootfs usable in dual boot?

There are programs where you want to be more comfortable or need to access the GPU, or the real hardware without having to deal with a virtualizer, therefore if you share a partition you are already ready, since you can reboot the machine into linux and files will be already there.

[legacy]

The concern is if you screwed up, you can recover a VM from a snapshot.

Recover what? Also why should I have to duplicate the rootfs, which requires effort in order to have things compiled, installed, and configured (usually also hacked) in the proper why?

No sense.

With physical drive, that's hard to do.

Code: [Select]

nc blablala | dd if=hd-image of=/dev/sda*

Does the job.

Note the physical hd-image (raw) file can stay on a remote server as well as on a USB-stick.

A VM doesn't occupy the entire allocated space.

That's another annoying problem you have with virtualdisks as "sparse" doesn't work. Also, why should I have to waste harddrive space on my Windows's partition? *WHEN* I'd better have a native linux partition on the same harddrive which
1) can be accessed more safely from the virtualizer (directly access uses the LBA api)
2) can be accessed from a linux kernel without any-software layer under the hood
3) can be accessed from another machine if I hot-swap the harddrive

Again, no sense.

For GPU passthrough, you can do that with VT-d if you have 2 GPU cards, one for host, one for VM. VMWare esxi allows you to do this, so does unraid.

On XP the GPU support sucks, and can do professional job from MobaXterm? Like video editing?

[nctnico]

The concern is if you screwed up, you can recover a VM from a snapshot.

Recover what? Also why should I have to duplicate the rootfs, which requires effort in order to have things compiled, installed, and configured (usually also hacked) in the proper why?

No sense.

It makes perfect sense. Once the system is setup you make a snapshot and do that every time you make a big change to the system. When things go bad you restore the last-known-good snapshot. Works like a charm. I'm using XP in a VM and when it starts to behave bad I simply restore the snapshot and all is well again.

[ebclr]

"My points came from my own experience, which I'm NOT a heavy user of VM."


Vmware is extremely easy to use, and very reliable, can be used in both direction Linux <> WIN , WIN <> Linux , and  if you are a MAc guy, have fusion that is the Mac version of VMware.   

Vmware is the multimeter of software, there you can make records rollback, OS, Testing in different environments, software , networks , Control versioning, is simple a mandatory tool if you are involved in TI or software development   

[ebclr]

" Linux is definitely growing for engineering use"   

From 0.2% to 0,4% market share will be doubled 

[technix]

" Linux is definitely growing for engineering use"   

From 0.2% to 0,4% market share will be doubled 

A lot of new developments of software have been done on macOS... Well it is not Linux but it is still UNIX. And things may be as simple as recompile and run from macOS code base.

[ebclr]

Same on Windows

https://sourceforge.net/projects/mingw-w64/files/External%20binary%20packages%20%28Win64%20hosted%29/MSYS%20%2832-bit%29/

[technix]

Same on Windows

https://sourceforge.net/projects/mingw-w64/files/External%20binary%20packages%20%28Win64%20hosted%29/MSYS%20%2832-bit%29/

Not quite. I have much more success trying to move code between Linux (Ubuntu) and macOS. But whenever Windows gets involved it becomes troublesome. Especially when hardware access is involved, like serial ports or USB.

[ebclr]

Are you kidding, Windows just love serial ports, just need to remember that ports in windows are COM ports like COM1 ,COM2 not files

[technix]

Are you kidding, Windows just love serial ports, just need to remember that ports in windows are COM ports like COM1 ,COM2 not files

The termios are vastly different between UNIX and Windows. And don't get me started on the access permissions. Oh and you did not solve the USB problem.

[ebclr]

What is the USB problem?

http://libusb.info/

[technix]

What is the USB problem?

http://libusb.info/

You go ahead and try get a random libusb driver signed. Keep in mind that since Windows 8 it takes the user a few hoops to disable the mandatory driver code signing.

[ebclr]

You have at least 3 easy options

1) The drivers is available and signed if the supplier is smart enough to care about 90% of the market

2) You can easily tell windows to not enforce the rule

3) You sign the driver yourself

[technix]

You have at least 3 easy options

1) The drivers is available and signed if the supplier is smart enough to care about 90% of the market

Who is the vendor in the first place? Think from an end user's point of view.

2) You can easily tell windows to not enforce the rule

Significant numbers of loops and hoops have to be through. Think from an end user's point of view.

3) You sign the driver yourself

Can an average Joe with a computer be nothered to do this? Think from an end user's point of view.

[ebclr]

You are right, will be much easier for the average Joe learn Linux, open the terminal, install the device and  the software, Linux is made for Joe six pack, Windows is for PHD's only

[technix]

You are right, will be much easier for the average Joe learn Linux, open the terminal, install the device and  the software, Linux is made for Joe six pack, Windows is for PHD's only

Wrong. Windows device driver development is for megacorporations only. For average Joe there is Android (and in some cases iOS) so you got UNIX there.

[legacy]

EagleCAD needs EC_get_builtin_curves, defined by OpenSSL, so EagleCAD depends on OpenSSL, and it makes sense.

UAU 

[legacy]

At least on Windows you can simply provide a local dll, problem solved.

On linux 

I am going to fix && recompile { dev-libs/openssl, dev-libs/openssh } ebuilds, just to include what is required by EagleCAD, with the hope (finger crosses) that it won't break something.

[nctnico]

The fault is in trying to compile from source. Just look for a pre-build binary.

[legacy]

The fault is in trying to compile from source. Just look for a pre-build binary.

Do you really think I'd waste my time compiling stuff if I was allowed to use pre-build binaries? A bit naive, don't you think?

Now there is another freaking problem: Eagle needs some potentially patent encumbered code in a library that it depends on, and I am not sure *IF* I am authorized to recompile SLL with EC 

[technix]

At least on Windows you can simply provide a local dll, problem solved.

On linux 

I am going to fix && recompile { dev-libs/openssl, dev-libs/openssh } ebuilds, just to include what is required by EagleCAD, with the hope (finger crosses) that it won't break something.

This is a trick very well documented by Apple but it works on all UNIX: rpath.

[alm]

Or do what many closed source applications do, and launch via a shell script which sets LD_LIBRARY_PATH. You can also do this if you do not have the source to the binary.

[technix]

Or do what many closed source applications do, and launch via a shell script which sets LD_LIBRARY_PATH. You can also do this if you do not have the source to the binary.

rpath is much easier to use, if you have the source to the library and binary

It is extremely well documented by Apple because of the App Store distribution model: one portable container and one portable container only, no installer or putting libraries elsewhere allowed. Here is the typical layout of an application with libraries embedded (in Apple vocabulary libraries are called Frameworks:)

Code: [Select]

/Applications/MyApp.app/
    Contents/
        MacOS/MyApp (the actual executable)
        Info.plist
        Resources/
            MainWindow.nib (resources - this is just an example)
            AppIcon.icns
        Franeworks/
            MyFramework.framework/
                MyFramework (the actual dynamic library file)
                Frameworks/ (Dynamic library files can carries even more library files this way.)
In this case, the MyApp binary links to MyFramework dynamic library using a path like this:

Code: [Select]

$rpath/../Frameworks/MyFramework.framework/MyFramework

[alm]

Absolutely, rpath is superior if you have the source. The LD_LIBRARY_PATH can trick getting help third-party stuff to run.

[legacy]

As expected I am not authorized to change ssh 

EagleCAD v6.* is not affected.
EagleCAD v7 is affected, as it requires EC

Therefore I created a local library which contains EC, then I renamed /opt/eaglecad-v7.*/bin/eagle (the binary ELF application) into eagle-app, and created a wrapper with the name /opt/eaglecad-v7.*/bin/eagle

The wrapper uses app-admin/chrpath which modifies the rpath of the ELF executable.

The local library is within the same path. Problem solved.