Re: starting embedded linux debugging
From: Nobody Here (nobby_at_invalid.invalid)
Date: 11/23/05
- Next message: ryadav: "DVD-207 coby player"
- Previous message: Geronimo W. Christ Esq: "Re: starting embedded linux debugging"
- In reply to: Geronimo W. Christ Esq: "Re: starting embedded linux debugging"
- Next in thread: Geronimo W. Christ Esq: "Re: starting embedded linux debugging"
- Reply: Geronimo W. Christ Esq: "Re: starting embedded linux debugging"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 22 Nov 2005 23:18:25 GMT
Geronimo W. Christ Esq <thegreatsuprendo@hotmail.com> wrote:
> josimda wrote:
>
>> Half a year ago I also started my first embedded linux project. I asked
>> some suppliers of hardware and software of our company if it's
>> advisable to use Cygwin . The most said: "You will not be able to
>> compile the kernel, because Cygwin can't handle that long path names."
>
> They're not talking a lot of sense then. I have the kernel compiling
> perfectly easily under Cygwin.
>
>> or "Most of our customers have problems with that tftp server under
>> windows, it doesn't work".
>
> TFTPD32 on Windows works perfectly : http://tftpd32.jounin.net/
>
>> So i didn't try it as a development environment. One problem you will
>> have under Windows is, that if someone sends you a tarzipped archive
>> with source code and you decompress it under windows, it will overwrite
>> some files, because the file system is not case sensitive. It's a small
>> problem, but if more small problems ... bla bla you know.
>
> If you have to work a lot on both UNIX-like systems as well as Windows,
> Cygwin is possibly a useful compromise. VMWare would definitely be
> preferable, however.
>
>> The company I work for doesn't allow you to install a Linux system and
>> connect it to the network. So i decided to buy a couble of VMWare
>> licenses and every devolper installed VMWare on his computer. Everybody
>> had Debian under VMWare running. Then I had to install some packages on
>> my machine and had some programs and testcode here and there, and every
>> devolper had his own isolated system with different packages and tools
>> installed. Very bad solution, and it was also soooo slow to compile
>> under VMWare.
>
> That isn't my experience; VMWare is almost as quick as the host machine.
In fact, I use VMware every day, but the opposite way around, to use
some Windows CAD programs on a Linux machine. It's just as fast as the
host, because it's running most stuff native on the host's processor
exactly as if the host was running the embedded OS. The only performance
hit you *might* see is with screen drawing, because it's emulating a video
card on top of your native OS's graphics system. Nevertheless, the graphics
performace of the CAD stuff I use is pretty much the same as it is under
native Windows - although it's not 3d which I'm sure would suffer. Other
IO might suffer a bit too, although that's generally not much of a
problem.
Do you have the guest tools installed on your VMs? They make an
appreciable difference to graphics performance. I've not used
many linux VMs (because it's my host so I don't generally need to)
but I do use a Fedora Core 1 VM (on a FC4 host) to do some backward
compatible stuff. In that instance, though, I don't use X, and I
edit on the host, and only compile on the guest using a virtual
network connection to the host's filesystem. You could do the same
with a Windows guest - I also do that for some windows based DSP compilations
with the Analog Devices DSP compiler whose name I temporarily forget.
I wonder if the company you work for realises that a VMware hosted OS
is effecively a Linux machine, and if you've bridged it to the network
it's effectively connected to the network. If they're stupid enough to
have that policy, but still want you to develop a linux project, then
they're undoubtedly too stupid to realise that. Why on earth do they
have such a stupid policy? If they really insist on it, can't you
install some Linux machines, and run a completely separate network
with a single ethernet switch connecting them? Or get a job with
a company that's dragging itself into the last couple of decades of the
20th century, at least?
-- Nobby
- Next message: ryadav: "DVD-207 coby player"
- Previous message: Geronimo W. Christ Esq: "Re: starting embedded linux debugging"
- In reply to: Geronimo W. Christ Esq: "Re: starting embedded linux debugging"
- Next in thread: Geronimo W. Christ Esq: "Re: starting embedded linux debugging"
- Reply: Geronimo W. Christ Esq: "Re: starting embedded linux debugging"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|