nanogui: Thread: NanoX/uWin on eCos

Sorry, I think this has been asked before, but does uWindows/Nano-X work
on eCos? If not, what would be needed for it to work, framebuffer
support? Would adding framebuffer support for any UNIX type OS allow uWin
to work? 

This is for a MIPS platform if it matters.


Thanks!
Vasant.

>From: Vasant Ramasubramanian ####@####.####
>To: ####@####.####
>Subject: NanoX/uWin on eCos
>Date: Sat, 3 Mar 2001 07:47:28 -0600 (CST)
>
>Sorry, I think this has been asked before, but does uWindows/Nano-X work
>on eCos? If not, what would be needed for it to work, framebuffer
>support? Would adding framebuffer support for any UNIX type OS allow uWin
>to work?
>
>This is for a MIPS platform if it matters.
>


Yes. Look at the archives of the eCos mailing-lists and you
would see the posts there.

I do not recall the guy saying that the code was available.

Rosimildo.







_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com

: Sorry, I think this has been asked before, but does uWindows/Nano-X work
: on eCos?

I have heard that it has been completed, but nobody has contributed
the changes back at this time...


 If not, what would be needed for it to work, framebuffer
: support? Would adding framebuffer support for any UNIX type OS allow uWin
: to work? 

Porting Microwindows requires writing a Microwindows screen
device driver, which isn't too much work.  If the target OS can
bring up a rudimentary linear-accessed framebuffer, and have it
mapped into the process address space, then it's very straight
forward, since all the existing 1,2,4,8,16,24,32bpp draw routines
can be used as is.

Read the Arch doc on the web site for more details.


Regards,

Greg




: 
: This is for a MIPS platform if it matters.
: 
: 
: Thanks!
: Vasant.
: 
: 
: 
: ---------------------------------------------------------------------
: To unsubscribe, e-mail: ####@####.####
: For additional commands, e-mail: ####@####.####
: 

Hi everybody!
I'm a newbie in nanogui.
In this month, I have porting the microwindows api to eCos. The cpu arch is
cirrus logic arm7500 in 50MHz.But the perform of microwin in this platform
is very slowly.
Does anybody give me some advice? How does microwindows performs in such
kind of platform?

I never use the nano-x(client-server mode),because this package must include
many files ecos doesn't have.And nano-x require sun-style tcp/ip stack.
I just use mwin api.

----- Original Message -----
From: "Mandeep Singh Chauhan" ####@####.####
To: "wangwei" ####@####.####
Sent: Thursday, March 08, 2001 3:46 PM
Subject: Re: NanoX/uWin on eCos


>
> how get the nano-X executable (server) ? i was compiling on linux using
> vga libs and the make was compiling package succ. but it was not making
> nano-X. Even srvnet.c was not being compiled. could u please either give
> me some tip for compiling this or mail me yr Makefile.rules and config
> file. it would be lot of favour to me.
> thanks
> mandeep
>
>
> On Thu, 8 Mar 2001, wangwei wrote:
>
> > Hi everybody!
> > I'm a newbie in nanogui.
> > In this month, I have porting the microwindows api to eCos. The cpu arch
is
> > cirrus logic arm7500 in 50MHz.But the perform of microwin in this
platform
> > is very slowly.
> > Does anybody give me some advice? How does microwindows performs in such
> > kind of platform?
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: ####@####.####
> > For additional commands, e-mail: ####@####.####
> >
>

On Thu, 8 Mar 2001, wangwei wrote:
> many files ecos doesn't have.And nano-x require sun-style tcp/ip stack.

No, just the BSD sockets API and some form of IPC. We use Unix domain
sockets on Linux, but you could probably implement something even simpler.
You will need a scheduler for multiple process support, but a TCP/IP stack
isn't required at all.

-- 
------- Alex Holden -------
http://www.linuxhacker.org/
 http://www.robogeeks.org/

The message would be very helpful to me .thanks!
Now I got trouble in mwin(win32 api mode).when I
run it in arm7500 paltform,50Mhz frequency,cache enable,
the window's refreshing is very slow.At that time, these isn't
any other threads except microwindow.
I had run a windows-like x in this hardware platform,the
speed of window's operation is quickly enough.
Can you tell me ,the microwindows requires what kind of
platform?
thank you very much
----- Original Message -----
From: "Alex Holden" ####@####.####
To: "wangwei" ####@####.####
Cc: "nanogui" ####@####.####
Sent: Thursday, March 08, 2001 9:52 PM
Subject: Re: NanoX/uWin on eCos


> On Thu, 8 Mar 2001, wangwei wrote:
> > many files ecos doesn't have.And nano-x require sun-style tcp/ip stack.
>
> No, just the BSD sockets API and some form of IPC. We use Unix domain
> sockets on Linux, but you could probably implement something even simpler.
> You will need a scheduler for multiple process support, but a TCP/IP stack
> isn't required at all.
>
> --
> ------- Alex Holden -------
> http://www.linuxhacker.org/
>  http://www.robogeeks.org/
>

Microwindows does not require any specific platform.  It will run on
virtually anything (even raw VGA hardware, if you are brave enough). 

You will have to give us more information about exactly what you are
doing so we can get an idea of what you are doing that is so slow.

Jordan

wangwei wrote:
> 
> The message would be very helpful to me .thanks!
> Now I got trouble in mwin(win32 api mode).when I
> run it in arm7500 paltform,50Mhz frequency,cache enable,
> the window's refreshing is very slow.At that time, these isn't
> any other threads except microwindow.
> I had run a windows-like x in this hardware platform,the
> speed of window's operation is quickly enough.
> Can you tell me ,the microwindows requires what kind of
> platform?
> thank you very much
> ----- Original Message -----
> From: "Alex Holden" ####@####.####
> To: "wangwei" ####@####.####
> Cc: "nanogui" ####@####.####
> Sent: Thursday, March 08, 2001 9:52 PM
> Subject: Re: NanoX/uWin on eCos
> 
> > On Thu, 8 Mar 2001, wangwei wrote:
> > > many files ecos doesn't have.And nano-x require sun-style tcp/ip stack.
> >
> > No, just the BSD sockets API and some form of IPC. We use Unix domain
> > sockets on Linux, but you could probably implement something even simpler.
> > You will need a scheduler for multiple process support, but a TCP/IP stack
> > isn't required at all.
> >
> > --
> > ------- Alex Holden -------
> > http://www.linuxhacker.org/
> >  http://www.robogeeks.org/
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####